AUTO: Mark Woodruff/Jefferson City/IBM is out of the office. (returning 05/27/2008)
I am out of the office until 05/27/2008. I will respond to your message when I return. Note: This is an automated response to your message IBMVM Digest - 17 May 2008 to 18 May 2008 (#2008-53) sent on 5/18/08 23:02:02. This is the only notification you will receive while this person is away.
Re: Lasting Globalv
Thanks all,I'll execute your suggestions and that should fit the bill.--- On Sun, 5/18/08, Rick Troth [EMAIL PROTECTED] wrote:From: Rick Troth [EMAIL PROTECTED]Subject: Re: Lasting GlobalvTo: IBMVM@LISTSERV.UARK.EDUDate: Sunday, May 18, 2008, 3:35 PMHoward ...The PF key settings are usually established in PROFILE EXECfor your regular CMS session and in PROFILE XEDIT for editor work.There is no automatic connection with GLOBALV, but you can issue'GLOBALV GET' commands to set variables (within each profilesince they are usually written in REXX) and then issue theappropriate key setting commands.For example commands, I use this in PROFILE EXEC 'CP SET PF1 RET'and this in PROFILE XEDIT 'SET PF1 BEFORE ?'Both have the same effect of setting PF1 to be a retrieve key.You could yank settings from GLOBALV with something like /* in PROFILE EXEC */ 'GLOBALV SELECT MAINKEYS GET PF1' 'CP SET PF1' pf1 /* in PROFILE XEDIT */ Address "COMMAND" 'GLOBALV SELECT EDITKEYS GET PF1' 'SET PF1' pf1(And *setting* the global variables I will leave to later discussionif this has hit the mark at all.) I hope this helps.-- R;
Re: mixed case messages
Shimon Lebowitz wrote: CP MSG target variable_with_mixedcase_text What have I missed? Thanks! Shimon Try this: Address command CP MSG target variable_with_mixedcase_text Ray
Re: mixed case messages
In my experience, you've got to *always* drive 'CP MSG' from the Diag() function or DiagRC() function in REXX, or some equivalent. Going through normal CMS command processing performs an up-case on the command so that CMS can remain case insensitive. On Mon, May 19, 2008 at 7:37 AM, Shimon Lebowitz [EMAIL PROTECTED] wrote: Hi, I was under the impression that a CP message/smsg could be mixed case, as long as it was sent directly from an EXEC or other program (and not from the command line which would uppercase all the console input). 1) Is this in fact true? (documented?) 2) IF it's true, what could be causing my messages/smsgs to be arriving in all uppercase? This is a serious problem, because I have a server virtual machine to which I need to periodically send a bit of *non-printable-character* data. I ran this data through a 64ENCODE pipe stage before SMSGing it, with the server using 64DECODE on the received data. Unfortunately, with the SMSG arriving uppercased, my data gets klobbered. I checked this with MSG to a spooled console and also see arriving data in uppercase, even though the message was sent from an exec with: CP MSG target variable_with_mixedcase_text What have I missed? Thanks! Shimon -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 -- -- R;
set conceal
Friends, Why doesn't my SET CONCEAL do what I expected ? I have SET CONCEAL ON but when the program gets a program check, it just drops in VM READ after a DMSABE141T and nothing else... Rob
Re: mixed case messages
Ray and Richard, Thanks to you both for jiggling my partial memory! :-) Shimon
Re: mixed case messages
In a similiar vein, how can I get the lower case information which may be returned from querying the rdr. RDRLIST does it, at least it displays the lower case names in the User at Node columns. I believe that I could stop 99.9% of the spam that enters the system with an SMTP exit that would check for a lower or mixed case user or node name. I know I could read the RDRLIST code, but if someone has a QD answer, I'd appreciate it. Would a REXX DIAG 0 function do it with the output being still lower or mixed case in the output variable? Jim Ray Mansell wrote: Try this: Address command CP MSG target variable_with_mixedcase_text Ray -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Extension of MAINT 190 (S-DISK)
Dear all, What is the correct procedure for extending the MAINT 190 (S-Disk)? My MA INT 190 is 82% full and I would like to prepare myself for the case of extend ing it. It can be that we install some products (like DCF) that reside on the S-Disk. Is allocation of a new mini disk and a DDR to that enough or do I have to make a CMS format and a copy of all files to that new disk? Please advise on this. Thank you very much in advance. Best regards, Fox
Re: mixed case messages
Hi Folks, You should always use ADDRESS COMMAND in your CMS REXX EXECs (unless they are addressing some other environment, like GCS). The default is to ADDRESS CMS, which means any host commands your REXX EXEC passes to the subcommand environment are handled by the CMS command processor, just as if they were entered from the CMS command line. Commands are uppercased, synonyms and abbreviations are resolved, etc. etc. - with all of the associated overhead. Moreover, it allows sloppy programming, I can't tell you how many times I've been called in to fix sloppy REXX EXECs that are loaded with abbreviations - try finding ALL /FILEDEF/ using XEDIT when the programmer abbreviated the FILEDEF command .. Or try and locate all calls to the SENDFILE EXEC when the programmer has it coded as 'SF' (or anything else they may want, since synonyms can be used). ADDRESS COMMAND improves performanc AND imposes a bit of discipline on the programmer. In response to your specific requirement Jim, your best approach is PIPE CP QUERY READER * ALL | STEM RDR. - PIPE will respect the case of the responses it receives. Of course DIAG() will also yield unmodified results, but you can do so much more with PIPE :) -Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack Sent: Monday, May 19, 2008 8:29 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: mixed case messages In a similiar vein, how can I get the lower case information which may be returned from querying the rdr. RDRLIST does it, at least it displays the lower case names in the User at Node columns. I believe that I could stop 99.9% of the spam that enters the system with an SMTP exit that would check for a lower or mixed case user or node name. I know I could read the RDRLIST code, but if someone has a QD answer, I'd appreciate it. Would a REXX DIAG 0 function do it with the output being still lower or mixed case in the output variable? Jim Ray Mansell wrote: Try this: Address command CP MSG target variable_with_mixedcase_text Ray -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: mixed case messages
Pipelines can certainly do that (as well as diag and EXECIO). This is very quick dirty to get the spool file numbers of any file with lower case in its name. /* R E X X */ Address Command 'PIPE cp Q RDR * ALL', '| drop 1', '| xlate 54-71 a-z a', '| locate 54-71 a', '| spec w2 1', '| stem files.' On Mon, May 19, 2008 at 8:28 AM, Jim Bohnsack [EMAIL PROTECTED] wrote: In a similiar vein, how can I get the lower case information which may be returned from querying the rdr. RDRLIST does it, at least it displays the lower case names in the User at Node columns. I believe that I could stop 99.9% of the spam that enters the system with an SMTP exit that would check for a lower or mixed case user or node name. I know I could read the RDRLIST code, but if someone has a QD answer, I'd appreciate it. Would a REXX DIAG 0 function do it with the output being still lower or mixed case in the output variable? Jim -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED] -- Bruce Hayden Linux on System z Advanced Technical Support IBM, Endicott, NY
Re: Extension of MAINT 190 (S-DISK)
On Mon, 19 May 2008 14:43:09 +0200, Rob van der Heij [EMAIL PROTECTED] wrote: OK thank you, correct. But then I would like to extend the question with regard of the Y-Disk. Is a simple CMS copy enough or is special attention needed. Fox On Mon, May 19, 2008 at 2:38 PM, Fox Blue [EMAIL PROTECTED] wrote : it. It can be that we install some products (like DCF) that reside on the S-Disk. One does not normally install those on the S-disk but on the Y-disk. (the S-disk is being DDR-ed from the 490) Rob
Re: Extension of MAINT 190 (S-DISK)
Extending the S-disk is seldom done, because not that easy. Most people would place extra products on the Y-disk (19E), or yet another disks, accessed by SYSPROF. But, if you insist: - FORMAT the new minidisk e.g. as B - FORMAT newcuu B nnn (RECOMP makes room for the CMS nucleus, nnn is the size of the new minidisk minus 7 cylinders (a CMS nuclues is supposed to take at most 7 cylinders nowadays) - update DMSNGP, adapt CYLADDR=100 to CYLADDR=nnn regenerate DMSNGP - VMFBLD PPF ZVM CMS CMSLOAD (ALL to build the new nucleus load deck in your reader - DET 190 #DEF newcuu 190#IPL 00C CLEAR As this is not for dummies, I explained briefly. Kris 2008/5/19, Fox Blue [EMAIL PROTECTED]: Dear all, What is the correct procedure for extending the MAINT 190 (S-Disk)? My MA INT 190 is 82% full and I would like to prepare myself for the case of extend ing it. It can be that we install some products (like DCF) that reside on the S-Disk. Is allocation of a new mini disk and a DDR to that enough or do I have to make a CMS format and a copy of all files to that new disk? Please advise on this. Thank you very much in advance. Best regards, Fox -- Kris Buelens, IBM Belgium, VM customer support
Re: mixed case messages
The telecourse TCVM1 -HTML selfstudy, on VM's download lib- has a whole chapter devoted to ADDRESS COMMAND and PIPE COMMAND as opposed to ADDRESS CMS and PIPE CMS. Kris 2008/5/19, Michael Coffin [EMAIL PROTECTED]: Hi Folks, You should always use ADDRESS COMMAND in your CMS REXX EXECs (unless they are addressing some other environment, like GCS). The default is to ADDRESS CMS, which means any host commands your REXX EXEC passes to the subcommand environment are handled by the CMS command processor, just as if they were entered from the CMS command line. Commands are uppercased, synonyms and abbreviations are resolved, etc. etc. - with all of the associated overhead. Moreover, it allows sloppy programming, I can't tell you how many times I've been called in to fix sloppy REXX EXECs that are loaded with abbreviations - try finding ALL /FILEDEF/ using XEDIT when the programmer abbreviated the FILEDEF command .. Or try and locate all calls to the SENDFILE EXEC when the programmer has it coded as 'SF' (or anything else they may want, since synonyms can be used). ADDRESS COMMAND improves performanc AND imposes a bit of discipline on the programmer. In response to your specific requirement Jim, your best approach is PIPE CP QUERY READER * ALL | STEM RDR. - PIPE will respect the case of the responses it receives. Of course DIAG() will also yield unmodified results, but you can do so much more with PIPE :) -Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack Sent: Monday, May 19, 2008 8:29 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: mixed case messages In a similiar vein, how can I get the lower case information which may be returned from querying the rdr. RDRLIST does it, at least it displays the lower case names in the User at Node columns. I believe that I could stop 99.9% of the spam that enters the system with an SMTP exit that would check for a lower or mixed case user or node name. I know I could read the RDRLIST code, but if someone has a QD answer, I'd appreciate it. Would a REXX DIAG 0 function do it with the output being still lower or mixed case in the output variable? Jim Ray Mansell wrote: Try this: Address command CP MSG target variable_with_mixedcase_text Ray -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED] -- Kris Buelens, IBM Belgium, VM customer support
Re: Extension of MAINT 190 (S-DISK)
On Mon, May 19, 2008 at 2:38 PM, Fox Blue [EMAIL PROTECTED] wrote: it. It can be that we install some products (like DCF) that reside on the S-Disk. One does not normally install those on the S-disk but on the Y-disk. (the S-disk is being DDR-ed from the 490) Rob
Re: set conceal
Rob, I think that CONCEAL on acts upon disabled waits, hence CP READs... Kris 2008/5/19, Rob van der Heij [EMAIL PROTECTED]: Friends, Why doesn't my SET CONCEAL do what I expected ? I have SET CONCEAL ON but when the program gets a program check, it just drops in VM READ after a DMSABE141T and nothing else... Rob -- Kris Buelens, IBM Belgium, VM customer support
Re: Extension of MAINT 190 (S-DISK)
Kris, thank you very much for the info. Focusing now on Y-DISK. Is a simple cop y of the files enough after formating the new Y-DISK or are there onher pit falls? Fox Extending the S-disk is seldom done, because not that easy. Most people would place extra products on the Y-disk (19E), or yet another disks, accessed by SYSPROF. But, if you insist: - FORMAT the new minidisk e.g. as B - FORMAT newcuu B nnn (RECOMP makes room for the CMS nucleus, nnn is the size of the new minidisk minus 7 cylinders (a CMS nuclues is supposed to take at most 7 cylinders nowadays) - update DMSNGP, adapt CYLADDR=100 to CYLADDR=nnn regenerate DMSNGP - VMFBLD PPF ZVM CMS CMSLOAD (ALL to build the new nucleus load deck in your reader - DET 190 #DEF newcuu 190#IPL 00C CLEAR As this is not for dummies, I explained briefly. Kris -- Kris Buelens, IBM Belgium, VM customer support =
Re: Extension of MAINT 190 (S-DISK)
The 19E Y disk can be changed and the files copied without a problem. It is a little more work than adding a new public disk that everyone accesses. Once the disk is moved, a new Y-stat not available error message starts appearing after IPLing CMS. To resolve that, do the SAMPNSS CMS from MAINT, then IPL 190 PARM SAVESYS CMS. Bob Bates Enterprise Hosting Services - Enterprise Virtualization - z/VM and z/Linux w. (469)892-6660 c. (214) 907-5071 This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Fox Blue Sent: Monday, May 19, 2008 8:00 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Extension of MAINT 190 (S-DISK) Kris, thank you very much for the info. Focusing now on Y-DISK. Is a simple cop= y of the files enough after formating the new Y-DISK or are there onher pit= falls? Fox Extending the S-disk is seldom done, because not that easy. Most people would place extra products on the Y-disk (19E), or yet another disks, accessed by SYSPROF. But, if you insist: - FORMAT the new minidisk e.g. as B - FORMAT newcuu B nnn (RECOMP makes room for the CMS nucleus, nnn is the size of the new minidisk minus 7 cylinders (a CMS nuclues is supposed to take at most 7 cylinders nowadays) - update DMSNGP, adapt CYLADDR=100 to CYLADDR=nnn regenerate DMSNGP - VMFBLD PPF ZVM CMS CMSLOAD (ALL to build the new nucleus load deck in your reader - DET 190 #DEF newcuu 190#IPL 00C CLEAR As this is not for dummies, I explained briefly. Kris -- Kris Buelens, IBM Belgium, VM customer support = ==
Re: set conceal
On Monday, 05/19/2008 at 08:42 EDT, Kris Buelens [EMAIL PROTECTED] wrote: Rob, I think that CONCEAL on acts upon disabled waits, hence CP READs... Correct, as usual, Kris. A VM READ will not trigger CONCEAL processing. DMS141T indicates that a program, not CMS itself, abended. DMS143T indicates a CMS abend, which will load a disabled wait and trigger a re-IPL. Alan Altmark z/VM Development IBM Endicott
Re: Extension of MAINT 190 (S-DISK)
On Mon, May 19, 2008 at 2:47 PM, Fox Blue [EMAIL PROTECTED] wrote: OK thank you, correct. But then I would like to extend the question with regard of the Y-Disk. Is a simple CMS copy enough or is special attention Since the Y-disk FST's are also kept in the CMS NSS, you need to save CMS again when you modify the 19E disk. PS I believe other installations have also concluded that flexibility with the 19E is more important than saving a few bytes on FST's and modified SYSPROF not to complain about the non-shared YSTAT. When you frequently change things on the 19E and have to save CMS often as well, you end up with more pending purge copies of the NSS and that cost is not justified by the savings. Rob
Re: Extension of MAINT 190 (S-DISK)
FWIW, I try to keep both the 190 and 19E pretty much as shipped by IBM. All public programs and files (i.e. other vendor products, locally developed programs and files, etc. etc.) all go on a disk accessed by all users via an exit in the SYSPROF EXEC (i.e. in my case they live on PUBLIC 191). This way you don't have to worry about trivial file changes making a LOT more work for you. Don't forget, in order to change a file on either the 190 or 19E you are SUPPOSED to make the changes to the 490 or 49E, test them, and then promote the changes to the 190 or 19E. If you skip this and make your changes directly to the 190/19E they could be OVERLAID (or lost) the next time you do any kind of service that does PUT2PROD and copies the 490/49E to 190/19E. Consider a local PUBLIC disk and save your self the grief of resizing CMS system minidisks, keeping test/prod CMS disks in synch, and constantly resaving the CMS minidisk FST's in NSS. -Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Monday, May 19, 2008 9:17 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Extension of MAINT 190 (S-DISK) On Mon, May 19, 2008 at 2:47 PM, Fox Blue [EMAIL PROTECTED] wrote: OK thank you, correct. But then I would like to extend the question with regard of the Y-Disk. Is a simple CMS copy enough or is special attention Since the Y-disk FST's are also kept in the CMS NSS, you need to save CMS again when you modify the 19E disk. PS I believe other installations have also concluded that flexibility with the 19E is more important than saving a few bytes on FST's and modified SYSPROF not to complain about the non-shared YSTAT. When you frequently change things on the 19E and have to save CMS often as well, you end up with more pending purge copies of the NSS and that cost is not justified by the savings. Rob
Re: set conceal
On Mon, May 19, 2008 at 3:23 PM, Alan Altmark [EMAIL PROTECTED] wrote: DMS141T indicates that a program, not CMS itself, abended. DMS143T indicates a CMS abend, which will load a disabled wait and trigger a re-IPL. So my expectations were the problem (as with many performance issues). CMS is friendly enough to do AUTODUMP for me on the program check. When CONCEAL is on, what's the value of CMS dropping the user in VM READ ? Rob
Re: Extension of MAINT 190 (S-DISK)
Hi Mike, Thank you for this hint. Well I am also much more in favour to do the installation on a separate disks, however in my case IBM install instructions of the SDO (Semi-VMSES/E Licenced Products) tell to install it on MAINT 19E. Therefore I do it in the recommended way but only for IBM products ;-) Regards, Fox On Mon, 19 May 2008 09:28:11 -0400, Michael Coffin [EMAIL PROTECTED] om wrote: FWIW, I try to keep both the 190 and 19E pretty much as shipped by IBM. All public programs and files (i.e. other vendor products, locally developed programs and files, etc. etc.) all go on a disk accessed by all users via an exit in the SYSPROF EXEC (i.e. in my case they live on PUBLIC 191). This way you don't have to worry about trivial file changes making a LOT more work for you. Don't forget, in order to change a file on either the 190 or 19E you are SUPPOSED to make the changes to the 490 or 49E, test them, and then promote the changes to the 190 or 19E. If you skip this and make your changes directly to the 190/19E they could be OVERLAID (or lost) the next time you do any kind of service that does PUT2PROD and copies the 490/49E to 190/19E. Consider a local PUBLIC disk and save your self the grief of resizing CMS system minidisks, keeping test/prod CMS disks in synch, and constantly resaving the CMS minidisk FST's in NSS. -Mike
Re: Extension of MAINT 190 (S-DISK)
Don't forget to do all this for your 490 minidisk as well, as there are several processes that assume that 490 and 190 are very similar -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 5/19/08 7:50 AM, Kris Buelens [EMAIL PROTECTED] wrote: Extending the S-disk is seldom done, because not that easy. Most people would place extra products on the Y-disk (19E), or yet another disks, accessed by SYSPROF. But, if you insist: - FORMAT the new minidisk e.g. as B - FORMAT newcuu B nnn (RECOMP makes room for the CMS nucleus, nnn is the size of the new minidisk minus 7 cylinders (a CMS nuclues is supposed to take at most 7 cylinders nowadays) - update DMSNGP, adapt CYLADDR=100 to CYLADDR=nnn regenerate DMSNGP - VMFBLD PPF ZVM CMS CMSLOAD (ALL to build the new nucleus load deck in your reader - DET 190 #DEF newcuu 190#IPL 00C CLEAR As this is not for dummies, I explained briefly. Kris 2008/5/19, Fox Blue [EMAIL PROTECTED]: Dear all, What is the correct procedure for extending the MAINT 190 (S-Disk)? My MA INT 190 is 82% full and I would like to prepare myself for the case of extend ing it. It can be that we install some products (like DCF) that reside on the S-Disk. Is allocation of a new mini disk and a DDR to that enough or do I have to make a CMS format and a copy of all files to that new disk? Please advise on this. Thank you very much in advance. Best regards, Fox
Re: Extension of MAINT 190 (S-DISK)
Thank you for this hint. Well I am also much more in favour to do the installation on a separate disks, however in my case IBM install instructions of the SDO (Semi-VMSES/E Licenced Products) tell to install it on MAINT 19E. Save yourself a lot of pain. Don't. Mixing stuff up on the 19E is just a recipe for a lot of heartache when you have to upgrade. We recommend using a separate minidisk for each product and using VMLINK with a shared NAMES file to access them as needed. Lets you do indirection and gets you a way to easily catalog who is using which product and how often it's used. At this point, the small real storage savings is unlikely to outweigh the amount of time it takes to sort out what files you need when you do an upgrade. Therefore I do it in the recommended way but only for IBM products ;-) If there's a feedback form, submit it with the comment that this is a REALLY bad idea.
Re: Extension of MAINT 190 (S-DISK)
We remove the Shared S or Y-stat not available messages for all end-users; as sysprogs, we still see them. Futhermore, our saved segment managing machine checks daily for unshared S- or Y-stat too and -if unshared- it will resave CMS when there are fewer than 4 copies of the CMS NSS. Similar: the state of the shared FST's for the help disk (MAINT 19D) is checked; it is resaved if less than 6 copies of the HELP segment exist. Kris 2008/5/19, RPN01 [EMAIL PROTECTED]: Don't forget to do all this for your 490 minidisk as well, as there are several processes that assume that 490 and 190 are very similar -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 5/19/08 7:50 AM, Kris Buelens [EMAIL PROTECTED] wrote: Extending the S-disk is seldom done, because not that easy. Most people would place extra products on the Y-disk (19E), or yet another disks, accessed by SYSPROF. But, if you insist: - FORMAT the new minidisk e.g. as B - FORMAT newcuu B nnn (RECOMP makes room for the CMS nucleus, nnn is the size of the new minidisk minus 7 cylinders (a CMS nuclues is supposed to take at most 7 cylinders nowadays) - update DMSNGP, adapt CYLADDR=100 to CYLADDR=nnn regenerate DMSNGP - VMFBLD PPF ZVM CMS CMSLOAD (ALL to build the new nucleus load deck in your reader - DET 190 #DEF newcuu 190#IPL 00C CLEAR As this is not for dummies, I explained briefly. Kris 2008/5/19, Fox Blue [EMAIL PROTECTED]: Dear all, What is the correct procedure for extending the MAINT 190 (S-Disk)? My MA INT 190 is 82% full and I would like to prepare myself for the case of extend ing it. It can be that we install some products (like DCF) that reside on the S-Disk. Is allocation of a new mini disk and a DDR to that enough or do I have to make a CMS format and a copy of all files to that new disk? Please advise on this. Thank you very much in advance. Best regards, Fox -- Kris Buelens, IBM Belgium, VM customer support
Re: Extension of MAINT 190 (S-DISK)
You forget the VMSES PARTCAT: I've got entries in VMSES PARTCAT for all the things I store on 19E, even y own code gets a dummy prodid. VMFCOPY can then be used to copy all files of a prodid. And, I wouldn't be me if I hadn't coded an exec to help with the task: my SESCOMP first compares VMSES PARTCAT with LISTFILE and helps you to add missing entries in VMSES PARTCAT. You do that for the old and new disk. The you can tell SESCOMP to compare the PARTCATs of two minidisks; it produces a list prodids and number of files; PF-keys allow to copy or FILELIST files of a prodid. This way, merging two minidisks is quickly done. Ask and you shall be given. Good idea. The setup I described is one I've been using for decades (way, way pre-SES) and I never bothered to change it once things got SES-ified. I wish I understood SES better. I'll have a peek (btw, you want somewhere to post all these goodies you've got squirreled away? Let's talk offlist.)
Re: Mystery paging
The dataspace usage is certainly a good thing to check, but there are at least a couple of other possibilities: The paging rate numbers are across time, whereas the Q ALLOC PAGE output is instantaneous. It could be that there's a low volume of paging to/from p aging DASD going on, but the pages that are read in are immediately changed, wh ich would cause CP to discard the copy out on paging DASD when CP notices the page change. So it needn't be the same page read 13 times a second, it could be a bunch of different pages which are then immediately changed, for which CP then discards the paging DASD copy. I'd have to check, but it seems possible that demand paging of spool page s from (and even possibly to) spool volumes could account for this, I'd hav e to check how those get counted. In particular, if you have a very lightly u sed NSS or DCSS, that only tends to be loaded by one user at a time, and it i s frequently purged and then reloaded, the initial page fault block reads f rom spool might show up like this. - Bill Holder z/VM development, IBM
Re: 'GSKKM error 146'
Thanks, Alan. I have contacted IBM. Suleiman Shahin Date: Sun, 18 May 2008 23:35:20 -0500 From: [EMAIL PROTECTED] Subject: Re: 'GSKKM error 146' To: IBMVM@LISTSERV.UARK.EDU Unfortunately, there is no 146 in that table. There are two 'nnn' entries= . Both tell you to contact IBM support. | nnn | | Internal SSL error = = = = | Explanation: An internal SSL error has occurred. = = = | System Programmer Response: Make a note of the error number | and contact the IBM Support Center for assistance. | nnn | | Unexpected SSL Server return code = = = | Explanation: The return code cited in the message is one for | which a corresponding TCP/IP server action has not | been defined. = = = | System Programmer Response: Identify the client and server | applications that pertain to the issuance of this | message. Collect console files for each, as well | as those for the TCP/IP and SSL servers. Contact | your IBM Support Center for assistance. = Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com _ Give to a good cause with every e-mail. Join the i’m Initiative from Microsoft. http://im.live.com/Messenger/IM/Join/Default.aspx?souce=EML_WL_ GoodCause
zVM and the SPOOL file
How does zVM store data in it's spool file? More specifically, in VSE/Power, a decision had to be made as to the block size of the Power data file (spool file). If you made the block size small, you utilized space better for small entries but you'd get an increase in I/O. If you used large block sizes, you reduced I/O but lost space. For example, if you submitted JCL, say 3 or 4 cards, they would occupy a whole block. A small report or items in the punch queue worked the same way. (I haven't worked with VSE in a loonnngg time so this may have changed.) I was wondering how zVM stored data in it's spool file. I don't recall specifying a block size specifically for the spool size. Thanks, Steve
Re: zVM and the SPOOL file
-Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen Sent: Monday, May 19, 2008 12:44 PM To: IBMVM@LISTSERV.UARK.EDU Subject: zVM and the SPOOL file How does zVM store data in it's spool file? More specifically, in VSE/Power, a decision had to be made as to the block size of the Power data file (spool file). If you made the block size small, you utilized space better for small entries but you'd get an increase in I/O. If you used large block sizes, you reduced I/O but lost space. For example, if you submitted JCL, say 3 or 4 cards, they would occupy a whole block. A small report or items in the punch queue worked the same way. (I haven't worked with VSE in a loonnngg time so this may have changed.) I was wondering how zVM stored data in it's spool file. I don't recall specifying a block size specifically for the spool size. Thanks, Steve IIRC, it uses 4K pages just like the paging subsystem. In fact, it may use the same logic. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it.
Re: zVM and the SPOOL file
CP speaks in 4K blocks...CMS mostly too, but if you insist you can format CMS minidisks with 512, 1K or 2K blocksizes too. 2008/5/19 Gentry, Stephen [EMAIL PROTECTED]: How does zVM store data in it's spool file? More specifically, in VSE/Power, a decision had to be made as to the block size of the Power data file (spool file). If you made the block size small, you utilized space better for small entries but you'd get an increase in I/O. If you used large block sizes, you reduced I/O but lost space. For example, if you submitted JCL, say 3 or 4 cards, they would occupy a whole block. A small report or items in the punch queue worked the same way. (I haven't worked with VSE in a loonnngg time so this may have changed.) I was wondering how zVM stored data in it's spool file. I don't recall specifying a block size specifically for the spool size. Thanks, Steve -- Kris Buelens, IBM Belgium, VM customer support
Re: Extension of MAINT 190 (S-DISK)
In a previous life, we consistenly modified SYSPROF EXEC to conditionally access 319 and 31A (and 19F). If they were missing: no prob, and no error. But most users got them. We then plunked various third party packages (or stubs) onto these disks. The value of this was that users might trash their PROFILE EXEC (which users are prone to do on any platform) and still get our standard disks, and yet these standard disks were not in DCSS so that small changes were much easier, as Mike Coffin suggested. -- R;
Re: zVM and the SPOOL file
On: Mon, May 19, 2008 at 01:43:33PM -0400,Gentry, Stephen Wrote: } How does zVM store data in it's spool file? More specifically, Others have mentioned that the spool system, as is most CP data, is made up of 4k blocks.. A bit more detail: The data in the 4k blocks consists of CCWs that when executed will write the data. A typical layout might be: CCW1 with a data address of data1 and a length of data1 TIC (transfer in channel, i.e. a branch to CCW2 DATA1 consisting of the first data record CCW2 with a data address of data2 and a length of data2 TIC to CCW3 DATA2 second data record CCW3 etc etc until the 4k block is filled. When printing or punching, the 4k block is read in, the address portions of the CCWs is relocated to the actual address in storage, and the i/o is started pointing to CCW1. NB: The above is somewhat simplified. -- Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 Eastern time. N6LRT I speak for myself my dogs only.VM'er since CP-67 Canines:Val, Red, Shasta Casey (RIP), Red Zero, Siberians Owner:Chinook-L Retired at the beach Asst Owner:Sibernet-L
Re: VM - Network best practices
We need to put together something approaching a production network environment for Windows(r) under z/VM testing. We don't believe a 500 seat environment would generate any more network traffic or for that matter be any more complex than the network definitions for a z/VM Linux server colony. In theory, no, but Windows uses many more broadcast and directed unicast/multicast protocols than Linux does, so the traffic patterns will be different. To be a realistic test, you'll need at least three layer 2 network segments, separated by layer 3 routers. The reason you need this kind of thing is to be able to test the hacks that Windows uses to bridge broadcast protocols across layer 3 networks (eg, WINS, etc). Has anyone put together a fairly complex multi-guest VM network using VSWITCH? If so, can you point me to any VM definitions that may have been shared on this list? Think of it as: segment 1 Router1 segment 2 Router2 ---segment 3 - Your Windows guests go on segments 1 and 3. DEFINE VSWITCH TYPE ETHERNET for each segment and define 3 NICs on each router virtual machine (I'd use Linux, but you will want to test Windows packet forwarding as well(). On router 1, couple one NIC to seg 1, one NIC to seg 2, and the 3rd NIC to a VSW that has exterior access (lets you log into the routers and collect data/change configuration). On router2, couple one NIC to seg 2, one NIC to seg 3, and the third NIC to the outside segment. You can then define your Windows guests and couple them to seg 1 or 3 (or 2 if you really want). That should give you a fairly realistic idea of how the Windows setup will work. You can also use the router virtual machines to give connectivity to the outside if you so desire by setting the default route in the router machines to the outside world.
Re: Mystery paging
Kris, NOMAD servers are not listed in QUERY RESOURCES. After thinking about it some more, I seriously doubt they use dataspaces. Most of the NOMAD code predates the existence of dataspaces. Bill Holder's explanation is more likely. The workload on the system is CMS, so I'm sure there's a fair amount of segment usage. It's not a problem, just curiosity, so I won't worry too much about it. Dennis O'Brien Elected office holds more perks than Elvis' nightstand. -- Dennis Miller -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Saturday, May 17, 2008 13:57 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Mystery paging Maybe Q RESOURCES will reveal the userids of the NOMAD servers, then Q SPACES USER will show some dataspaces. 2008/5/17 O'Brien, Dennis L Dennis.L.O'[EMAIL PROTECTED]: Kris, Thanks. That's interesting reading. The system in question does not have DB2/VM, and the 3 SFS filepools have no directories eligible for dataspaces. Any other ideas? Do NOMAD2 Shared Databases use dataspaces? I know this system has NOMAD2 Shared Databases, but as we're just getting familiar with it, I don't know their userids. I don't think there's anything wrong with the system, it's just curiosity, so it's not worth any great effort. Dennis O'Brien Elected office holds more perks than Elvis' nightstand. -- Dennis Miller -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Saturday, May 17, 2008 11:52 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Mystery paging Are dataspaces being used? DB2 and SFS are the the most common examples. With dataspaces (mapped to minidisks), the application simply reference the storage, CP will page-in what is referenced, and that is counted as paging. CP's Q SPACES and IND SPACE commands can help you. On VM's web-site, there is a document were I describe this in more detail: http://www.vm.ibm.com/perf/tips/dim.html http://www.vm.ibm.com/perf/tips/vmdspage.html 2008/5/17 O'Brien, Dennis L Dennis.L.O'[EMAIL PROTECTED]: We recently inherited responsibility for a z/VM 5.2 system that had been maintained by another group. They had a DR test today, and I logged on and looked around. The LPAR is configured with 3G central storage and no expanded storage. I issued the following commands: q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- VMPG00 8719 1 1000 18 1 1 1% VMPG01 871A 1 1000 18 0 0 0% VMPG02 871B 1 1000 18 0 0 0% VMPG03 871C 1 1000 18 0 0 0% -- -- SUMMARY 72 1 1% USABLE72 1 1% Ready; ind AVGPROC-003% 01 MDC READS-000112/SEC WRITES-03/SEC HIT RATIO-093% PAGING-13/SEC STEAL-000% Q0-3(0) DORMANT-00141 Q1-0(0) E1-0(0) Q2-1(0) EXPAN-001 E2-0(0) Q3-0(0) EXPAN-001 E3-0(0) PROC -003% LIMITED-0 Ready; q xstor Expanded storage is not available within this hardware configuration. Ready(01401); Since there's no expanded storage, where are those 13 pages/second going? Is the system reading the one page that's out on DASD 13 times a second? I did another Q ALLOC PAGE after the IND, and there's still only one page out there. Dennis O'Brien Elected office holds more perks than Elvis' nightstand. -- Dennis Miller -- Kris Buelens, IBM Belgium, VM customer support -- Kris Buelens, IBM Belgium, VM customer support
Re: Mystery paging
Dennis, NOMAD Shared Databases can utilize dataspaces. It's implemented by merely adding a LOOKUP DATASPACE clause to the desired MASTER definitions, then issuing a SCHEMA CHECK command. No application code need change to take advantage of the facility. So it's conceivable a DBA implemented dataspace use at the database level, with the unmodified application code transparently benefiting from this database enhancement. Regards, Tom Ramsberger Select Business Solutions Kris, NOMAD servers are not listed in QUERY RESOURCES. After thinking about it some more, I seriously doubt they use dataspaces. Most of the NOMAD code predates the existence of dataspaces. Bill Holder's explanation is more likely. The workload on the system is CMS, so I'm sure there's a fair amount of segment usage. It's not a problem, just curiosity, so I won't worry too much about it. Dennis O'Brien Elected office holds more perks than Elvis' nightstand. -- Dennis Miller -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Saturday, May 17, 2008 13:57 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Mystery paging Maybe Q RESOURCES will reveal the userids of the NOMAD servers, then Q SPACES USER will show some dataspaces. 2008/5/17 O'Brien, Dennis L Dennis.L.O'[EMAIL PROTECTED]: Kris, Thanks. That's interesting reading. The system in question does not have DB2/VM, and the 3 SFS filepools have no directories eligible for dataspaces. Any other ideas? Do NOMAD2 Shared Databases use dataspaces? I know this system has NOMAD2 Shared Databases, but as we're just getting familiar with it, I don't know their userids. I don't think there's anything wrong with the system, it's just curiosity, so it's not worth any great effort. Dennis O'Brien Elected office holds more perks than Elvis' nightstand. -- Dennis Miller -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Saturday, May 17, 2008 11:52 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Mystery paging Are dataspaces being used? DB2 and SFS are the the most common examples. With dataspaces (mapped to minidisks), the application simply reference the storage, CP will page-in what is referenced, and that is counted as paging. CP's Q SPACES and IND SPACE commands can help you. On VM's web-site, there is a document were I describe this in more detail: http://www.vm.ibm.com/perf/tips/dim.html http://www.vm.ibm.com/perf/tips/vmdspage.html 2008/5/17 O'Brien, Dennis L Dennis.L.O'[EMAIL PROTECTED]: We recently inherited responsibility for a z/VM 5.2 system that had been maintained by another group. They had a DR test today, and I logged on and looked around. The LPAR is configured with 3G central storage and no expanded storage. I issued the following commands: q alloc page EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- VMPG00 8719 1 1000 18 1 1 1% VMPG01 871A 1 1000 18 0 0 0% VMPG02 871B 1 1000 18 0 0 0% VMPG03 871C 1 1000 18 0 0 0% -- -- SUMMARY 72 1 1% USABLE72 1 1% Ready; ind AVGPROC-003% 01 MDC READS-000112/SEC WRITES-03/SEC HIT RATIO-093% PAGING-13/SEC STEAL-000% Q0-3(0) DORMANT-00141 Q1-0(0) E1-0(0) Q2-1(0) EXPAN-001 E2-0(0) Q3-0(0) EXPAN-001 E3-0(0) PROC -003% LIMITED-0 Ready; q xstor Expanded storage is not available within this hardware configuration. Ready(01401); Since there's no expanded storage, where are those 13 pages/second going? Is the system reading the one page that's out on DASD 13 times a second? I did another Q ALLOC PAGE after the IND, and there's still only one page out there. Dennis O'Brien Elected office holds more perks than Elvis' nightstand. -- Dennis Miller -- Kris Buelens, IBM Belgium, VM customer support -- Kris Buelens, IBM Belgium, VM customer support
