Re: Trapping output right after LOGON
Mikes suggestion is what I use. I place all LINK commands for VSE disks in an exec on the shared 191 disk. This is an easy solution to your problem and it makes maintenance of the VSE dasd much easier. No longer will you need to modify the directory to add a new VSE volume. Just link WR to the VSE 191 shared disk and change it. I would suggest the same for VCTCAs and such. Keep changes to the directory to the minimum. Tony Thigpen -Original Message - From: Mike Walter Sent: 03/01/2010 03:55 PM Mike, Along those lines, would it be feasible to move the CP Directory LINK statements for each guest into a CMS file where the shared PROFILE EXEC resides? There could be one file for COMMVSE CMDS containing LINK commands that every VSE guest issues. Then a separate file for each guest that has special needs (let's not go there regarding comments about how all VSE guests have special needs: - it's not Friday yet!). ;-) For example: VSE1 CMDS contains only LINK (and/or other!) commands required by that server. VSE2 CMDS contains only LINK (and/or other!) commands required by that server. And so on... The common PROFILE EXEC would issue: address CMS 'STATE COMMVSE CMDS *' If rc0 then ... report that a critical file is missing and do whatever is required... address CMS 'STATE' userid() 'CMDS *' If rc0 (and for those servers where the missing file is critical) ... report that a critical file is missing and do whatever is required... Else ... read the userid() CMDS * file, executing each command, reporting non-zero return codes as required. No PROP or other PROP-like facility would be required. Just a thought since you seemed to want to avoid PROP ... Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Horlick, Michael michael.horl...@cgi.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/01/2010 02:42 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Trapping output right after LOGON Hello Doug, I do have a shared PROFILE EXEC that sets up the environment before the IPL of z/VSE in each of the VSE users. Changing the exec to validate that each machine has the minidisks it requires is more prone to error then having CP tell me that something is amiss at LOGON time. Thanks, Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Doug Shupe Sent: March 1, 2010 3:28 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Mike, You could have one or many of your VSE guests IPL CMS in the directory and have them all point to a shared RR 191 mini disk. Then customize a PROFILE EXEC to do the CP 'whatever' and then, determine what to really IPL based on USERID. Sorry its not REXX, old stuff. PROFILE EXEC: TRACE CP SP CONSOLE START * DROPBUF BUFNO MAKEBUF BUFNO = RC EXECIO * CP ( MARGINS 1 8 STRING QUERY USERID IF RC NE 0 CALL -ERROR RC READ STRING ME IF MEEQ VSEID GOTO -VSEID CP MSG OP USER ME ATTEMPTED TO USE SHAREIPL. NOT DEFINED. GOTO -EXIT -VSEID EXEC VSEID ME GOTO -EXIT -ERROR RC = 1 READ STRING LERROR TYPE 0 PROBLEM OCCURED TRYING INQUIRY ON USERID. TYPE 0 LERROR EXIT RC -EXIT EXIT 999 VSEID EXEC: TRACE ALL ME = 1 CP SET RUN ON * * *CAUTION * THE FOLLOWING COMMAND HAS X'15' * *CAUTION * BETWEEN THE WORDS GUEST AND IPL. * *CAUTION * ISSUE THE 'SET HEX ON' COMMAND* *CAUTION * BEFORE CHANGING THIS LINE.* * * *EACH COMMAND MUST BE FOLLOWED BY A X'15'.* *TO ACCOMPLISH THIS; * *1). SET HEX ON * *2). KEY THE COMMANDS(LEAVING 2 SPACES BETWEEN EACH) ON 1 LINE* *3). BRING THE LINE JUST KEYED TO THE CURRENT LINE. * *4). CH /X'4040'/X'15'/1 N (N = THE NUMBER OF COMMANDS) * *5). FILE * * CP TERM CONM 3270 BRE GUESTIPL 1A6 CLEAR * CP TERM CONM 3270 BRE GUESTIPL 1A7 CLEAR LOADPARM T * CP TERM CONM 3270 BRE GUESTIPL 1A7 CLEAR LOADPARM . CP MSG OP IPL FAILED FOR ME RC= RC EXIT RC == Regards, Doug - Original Message - From: Horlick, Michael To: IBMVM@LISTSERV.UARK.EDU Sent: Monday, March 01, 2010 14:52 Subject: Re: Trapping output right after LOGON What do you mean by « Changing LINK to COMMAND LINK may help, that's for sure. I have MDISK statements for my VSE minidisks. Also, we run VM:Operator and not PROP. One of
Re: Trapping output right after LOGON
I wouldn't say that placing LINKs in execs/control files is that much easier that updating the CP directory. Additionally: the directory is the natural place to define virtual machine configurations. Not that I'm entirely against other solutions if they make life much easier... I also performed a test (I was right once and wrong once). - CP SET CPCONIO IUCV is indeed required to trap SCIF messages (OK by default if you use PROP, VM:Operator, Operations Manager or alike). - COMMAND SPOOL CONSOLE START doesn't help to catch device problems (LINK/MDISK/DEDICATE/...) The definiton USER EREP EREP 0008192K 0016384K FGBC * ENVIRONMENTAL RECORDING AND EDITING AND PRINTING INCLUDE GENERCMS ACCOUNT EREP C/O-8541 COMMAND SPOOL CON START TO KRIS IUCV *LOGREC CONSOLE 0009 3215 T KRIS OBS LINK MAINT 0201 0201 RR MDISK 0191 3390 228 2 VTE001 MR MDISK 3390 228 2 NODISK MR *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC19920601 CRCD[ The resulting console created by COMMAND:SPOOL ... File (none) (none) from EREP at VMKBBR01 Format is CONSOLE. * * * Top of File * * * z/VM 5.3 - 20 Jun 2008 - rsu703 HCPCRC8064I Recording data retrieval has been started; reco HCPRET8056I RECORDING RETRIEVAL DISK 88% FULL COMMAND ACCEPTED * * * End of File * * * With WAKEUP: tstrex TSTREX allows you to interactively execute REXX instructions - each instruction string is executed when you hit Enter. environment = CMS Go on - try a few... To end : PF3to dump vars: REXDUMP or DUMP v1 v2 vn or DUMP v. PF15 or EXTRACT /xedit-settings 'WAKEUP +0(IUCVMSG' R(2); TSTREX . cp set CPCONIO IUCV cp xautolog erep do until rc5;'WAKEUP +00:05(IUCVMSG QUIET';end 'PIPE STACK!CONS' *CP KRIS EREP: COMMAND ACCEPTED *CP KRIS EREP: HCPRET8056I RECORDING RETRIEVAL DISK 88% FULL *CP KRIS EREP: HCPCRC8064I Recording data retrieval has been started; recording *LOGREC for userid EREP. *CP KRIS EREP: z/VM 5.3 - 20 Jun 2008 - rsu703 *CP KRIS HCPCLS6056I XAUTOLOG information for EREP: The IPL command is verified by the IPL command processor. *CP KRIS AUTO LOGON *** EREP USERS = 7 *CP KRIS EREP: HCPLNM108E EREP not linked; volid NODISK not mounted *CP KRIS Command accepted *MSGRACFVM ICH70001I EREP LAST ACCESS AT 13:29:42 ON TUESDAY, MARCH 2 2010 R; TSTREX ... 2010/3/2 Tony Thigpen t...@vse2pdf.com Mikes suggestion is what I use. I place all LINK commands for VSE disks in an exec on the shared 191 disk. This is an easy solution to your problem and it makes maintenance of the VSE dasd much easier. No longer will you need to modify the directory to add a new VSE volume. Just link WR to the VSE 191 shared disk and change it. I would suggest the same for VCTCAs and such. Keep changes to the directory to the minimum. Tony Thigpen -Original Message - From: Mike Walter Sent: 03/01/2010 03:55 PM Mike, Along those lines, would it be feasible to move the CP Directory LINK statements for each guest into a CMS file where the shared PROFILE EXEC resides? There could be one file for COMMVSE CMDS containing LINK commands that every VSE guest issues. Then a separate file for each guest that has special needs (let's not go there regarding comments about how all VSE guests have special needs: - it's not Friday yet!). ;-) For example: VSE1 CMDS contains only LINK (and/or other!) commands required by that server. VSE2 CMDS contains only LINK (and/or other!) commands required by that server. And so on... The common PROFILE EXEC would issue: address CMS 'STATE COMMVSE CMDS *' If rc0 then ... report that a critical file is missing and do whatever is required... address CMS 'STATE' userid() 'CMDS *' If rc0 (and for those servers where the missing file is critical) ... report that a critical file is missing and do whatever is required... Else ... read the userid() CMDS * file, executing each command, reporting non-zero return codes as required. No PROP or other PROP-like facility would be required. Just a thought since you seemed to want to avoid PROP ... Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Horlick, Michael michael.horl...@cgi.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/01/2010 02:42 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Trapping output right after LOGON Hello Doug, I do have a shared PROFILE EXEC that sets up the environment before the IPL of z/VSE in each of the VSE users. Changing the exec to validate that each machine has the minidisks it requires is more prone to error then having CP tell me that something is
Re: Trapping output right after LOGON
On Tue, Mar 2, 2010 at 1:57 PM, Kris Buelens kris.buel...@gmail.com wrote: CP SET CPCONIO IUCV is indeed required to trap SCIF messages (OK by default if you use PROP, VM:Operator, Operations Manager or alike). Not unless big changes happened to CP ;-) Any IUCV handler is good to catch SCIF output (in fact, it sometimes bothers me that we don't have a SET SCIF ). Setting CPCONIO to IUCV is rather tricky because you're likely to process your own output again. PROP goes long and strange ways to associate some virtual machine output with an action routine (to send it back). pipe starmsg | cons CP Q SET MSG ON , WNG ON , EMSG ON , ACNT OFF, RUN OFF [ snip ] MIH OFF , VMCONIO OFF , CPCONIO OFF , SVCACCL OFF , CONCEAL OFF MACHINE ESA, SVC76 CP, NOPDATA OFF, IOASSIST OFF CCWTRAN ON , 370ACCOM OFF CP SET SECUSER ESAMON * HCPCFX6768I SECUSER of ESAMON initiated. CP SEND ESAMON ID 0008ESAMON ESAMON : 14:09:18 ESAMON AT RVDHEIJ VIA RSCS 0008ESAMON ESAMON : 14:09:18 Ready; T=0.01/0.01 14:09:18
Re: Trapping output right after LOGON
Hi Mike, I just found your topics and if you use VM/OPERATOR, you got the answer. When you have your VSE guest machine IPL'ed, you get all the message on the VM/OPERATOR console (if you have defined the VM/OPERATOR machine as a SECUSER for your guest). Below is the VM:OPERATOR log for a Linux machine I IPL'ed with missing dasd : 14:07:33 Z600561 VMYINI019R Enter: xautolog linux8 14:07:33 Z600561 Command accepted 14:07:33 Z600561 VMYINI006I 0.000 Ready; 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0100 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0101 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0102 not linked; volid DULX81 not mounted 4:07:33 LINUX8 *8 NIC F000 is created; devices F000-F002 defined 14:07:33 LINUX8 *8 NIC E000 is created; devices E000-E002 defined 14:07:33 LINUX8 *8 HCPNDF2787E NIC E000 not connected; LAN SYSTEM VSW1 does not exist 14:07:33 OPLINUX *3 AUTO LOGON *** LINUX8 USERS = 230 14:07:33 OPLINUX *3 HCPCLS6056I XAUTOLOG information for LINUX8: The IPL command is verified by the IPL command processor. You just have to trap the message HCPLNM108E with the VM/OPERATOR and do whatever you want. If you want any help, you can get back to me, I use VM/OPERATOR. (unfortunately for you, I go on hollidays this evening for 10 days) I can help you,it is easy. Regards :-) Laurent Dubois - Equipe VM Laurent Dubois * laurent.dub...@sncf.fr mailto:mlaurent.dub...@sncf.fr * 03 28 55 63 88 - 22 53 88 * 03 28 55 55 90 - 22 55 90 Prestataire externe SNCF - DSIV OS MM Systeme VM Tour de Lille Boulevard de Turin - 59777 EURALILLE PQüAvant d'imprimer, pensez à l'environnement De : The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] De la part de Horlick, Michael Envoyé : lundi 1 mars 2010 20:52 À : IBMVM@LISTSERV.UARK.EDU Objet : Re: Trapping output right after LOGON What do you mean by « Changing LINK to COMMAND LINK may help, that's for sure. I have MDISK statements for my VSE minidisks. Also, we run VM:Operator and not PROP. One of the guys in our automation group set up VM:Operator and I wonder if he knows how to handle output right from an XAUTOLOG of a virtual machine. Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: March 1, 2010 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Mike, I think I tried COMMAND SPOOL CONS START but COMMANDs seem to be executed after the devices are set up, hence too late to catch problems with MDISK statements. Changing LINK to COMMAND LINK may help, that's for sure. 2010/3/1 Mike Walter mike.wal...@hewitt.com Look up the directory COMMAND statement in the CP Planning and Administration manual. E.g. In the CP Directory entry for each VM userid for which you want the virtual console started as the VM is constructed the line: COMMAND SPOOL CONSOLE START Only CP commands may be entered into the CP Directory for users. You may specify any CP command argument. More details in the manual. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Horlick, Michael michael.horl...@cgi.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/01/2010 12:41 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Trapping output right after LOGON Greetings, I would like to trap all the CP console output from a virtual machine from its initial XAUTOLOG/LOGON. I have several z/VSE machines which are XAUTOLOGed on by the operator. Reason? In rare instances, maybe a pack is not attached to the system which contains some minidisks used by these machines. I know there could be a message such as: HCPLNM108E MIKE A194 not linked; volid XT160D not mounted For a test I have changed a virtual machine CONSOLE statement in its directory to CONSOLE 009 T MIKE OBS and I get all messages after the user logs on. I would like to programmatically trap these messages from a disconnected service machine so that it can be detected. Tried WAKEUP but no luck. Suggestions? Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this
Re: Trapping output right after LOGON
Kris Buelens kris.buel...@gmail.com wrote :- COMMAND SPOOL CONSOLE START doesn't help to catch device problems (LINK/MDISK/DEDICATE/...) It is just a thought but, if you change your directory entry as follows:- USER EREP EREP 0008192K 0016384K FGBC * ENVIRONMENTAL RECORDING AND EDITING AND PRINTING INCLUDE GENERCMS ACCOUNT EREP C/O-8541 COMMAND SPOOL CON START TO KRIS COMMAND LINK MAINT 0201 0201 RR IUCV *LOGREC CONSOLE 0009 3215 T KRIS OBS LINK MAINT 0201 0201 RR MDISK 0191 3390 228 2 VTE001 MR MDISK 3390 228 2 NODISK MR *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC19920601 CRCD[ You might be able to trap the result. Although I haven't tested it. Colin Allinson Amadeus Data Processing GmbH
Re: Trapping output right after LOGON
This is the first time I've seen (well, in an early post on this thread) the OBSERVER operand on the CONSOLE statement. So, I looked it up and it doesn't really explain it. Can someone enlighten me as to the purpose of the OBSERVER operand. TIA, Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Tuesday, March 02, 2010 6:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON I wouldn't say that placing LINKs in execs/control files is that much easier that updating the CP directory. Additionally: the directory is the natural place to define virtual machine configurations. Not that I'm entirely against other solutions if they make life much easier... I also performed a test (I was right once and wrong once). * CP SET CPCONIO IUCV is indeed required to trap SCIF messages (OK by default if you use PROP, VM:Operator, Operations Manager or alike). * COMMAND SPOOL CONSOLE START doesn't help to catch device problems (LINK/MDISK/DEDICATE/...) The definiton USER EREP EREP 0008192K 0016384K FGBC * ENVIRONMENTAL RECORDING AND EDITING AND PRINTING INCLUDE GENERCMS ACCOUNT EREP C/O-8541 COMMAND SPOOL CON START TO KRIS IUCV *LOGREC CONSOLE 0009 3215 T KRIS OBS LINK MAINT 0201 0201 RR MDISK 0191 3390 228 2 VTE001 MR MDISK 3390 228 2 NODISK MR *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC19920601 CRCD[ The resulting console created by COMMAND:SPOOL ... File (none) (none) from EREP at VMKBBR01 Format is CONSOLE. * * * Top of File * * * z/VM 5.3 - 20 Jun 2008 - rsu703 HCPCRC8064I Recording data retrieval has been started; reco HCPRET8056I RECORDING RETRIEVAL DISK 88% FULL COMMAND ACCEPTED * * * End of File * * * With WAKEUP: tstrex TSTREX allows you to interactively execute REXX instructions - each instruction string is executed when you hit Enter. environment = CMS Go on - try a few... To end : PF3to dump vars: REXDUMP or DUMP v1 v2 vn or DUMP v. PF15 or EXTRACT /xedit-settings 'WAKEUP +0(IUCVMSG' R(2); TSTREX . cp set CPCONIO IUCV cp xautolog erep do until rc5;'WAKEUP +00:05(IUCVMSG QUIET';end 'PIPE STACK!CONS' *CP KRIS EREP: COMMAND ACCEPTED *CP KRIS EREP: HCPRET8056I RECORDING RETRIEVAL DISK 88% FULL *CP KRIS EREP: HCPCRC8064I Recording data retrieval has been started; recording *LOGREC for userid EREP. *CP KRIS EREP: z/VM 5.3 - 20 Jun 2008 - rsu703 *CP KRIS HCPCLS6056I XAUTOLOG information for EREP: The IPL command is verified by the IPL command processor. *CP KRIS AUTO LOGON *** EREP USERS = 7 *CP KRIS EREP: HCPLNM108E EREP not linked; volid NODISK not mounted *CP KRIS Command accepted *MSGRACFVM ICH70001I EREP LAST ACCESS AT 13:29:42 ON TUESDAY, MARCH 2 2010 R; TSTREX ... 2010/3/2 Tony Thigpen t...@vse2pdf.com Mikes suggestion is what I use. I place all LINK commands for VSE disks in an exec on the shared 191 disk. This is an easy solution to your problem and it makes maintenance of the VSE dasd much easier. No longer will you need to modify the directory to add a new VSE volume. Just link WR to the VSE 191 shared disk and change it. I would suggest the same for VCTCAs and such. Keep changes to the directory to the minimum. Tony Thigpen -Original Message - From: Mike Walter Sent: 03/01/2010 03:55 PM Mike, Along those lines, would it be feasible to move the CP Directory LINK statements for each guest into a CMS file where the shared PROFILE EXEC resides? There could be one file for COMMVSE CMDS containing LINK commands that every VSE guest issues. Then a separate file for each guest that has special needs (let's not go there regarding comments about how all VSE guests have special needs: - it's not Friday yet!). ;-) For example: VSE1 CMDS contains only LINK (and/or other!) commands required by that server. VSE2 CMDS contains only LINK (and/or other!) commands required by that server. And so on... The common PROFILE EXEC would issue: address CMS 'STATE COMMVSE CMDS *' If rc0 then ... report that a critical file is missing and do whatever is required... address CMS 'STATE' userid() 'CMDS *' If rc0 (and for those servers where the missing file is critical) ... report that a critical file is missing and do whatever is required... Else ... read the userid() CMDS * file, executing each command, reporting non-zero return codes as required. No PROP or other PROP-like facility would be required. Just a thought since you seemed to want to
Re: Trapping output right after LOGON
Mike, I tried my idea and it is too late in the process. Ivan suggested the secondary user, is that available at 5.2? xautolog pcpc Command accepted Ready; T=0.01/0.01 16:51:01 PCPC: HCPLNM108E PCPC ABCD not linked; volid NOTFND not mounted PCPC: HCPLNM053E DOCO not in CP directory AUTO LOGON *** PCPC USERS = 23 HCPCLS6056I XAUTOLOG information for PCPC: The IPL command is verified by the IPL command processor. PCPC: z/VM V5.4.0 PCPC: DMSACP113S B(169) not attached or invalid device address PCPC: RDR FILE 0028 SENT FROM PCPC CON WAS 0028 RECS 0001 CPY 001 T NOHOLD NOKEEP PCPC: Ready; T=0.01/0.01 16:51:01 HCPQCS150A User PCPC has issued a VM read - Original Message - From: Horlick, Michael To: IBMVM@LISTSERV.UARK.EDU Sent: Monday, March 01, 2010 15:42 Subject: Re: Trapping output right after LOGON Hello Doug, I do have a shared PROFILE EXEC that sets up the environment before the IPL of z/VSE in each of the VSE users. Changing the exec to validate that each machine has the minidisks it requires is more prone to error then having CP tell me that something is amiss at LOGON time. Thanks, Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 -- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Doug Shupe Sent: March 1, 2010 3:28 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Mike, You could have one or many of your VSE guests IPL CMS in the directory and have them all point to a shared RR 191 mini disk. Then customize a PROFILE EXEC to do the CP 'whatever' and then, determine what to really IPL based on USERID. Sorry its not REXX, old stuff. PROFILE EXEC: TRACE CP SP CONSOLE START * DROPBUF BUFNO MAKEBUF BUFNO = RC EXECIO * CP ( MARGINS 1 8 STRING QUERY USERID IF RC NE 0 CALL -ERROR RC READ STRING ME IF MEEQ VSEID GOTO -VSEID CP MSG OP USER ME ATTEMPTED TO USE SHAREIPL. NOT DEFINED. GOTO -EXIT -VSEID EXEC VSEID ME GOTO -EXIT -ERROR RC = 1 READ STRING LERROR TYPE 0 PROBLEM OCCURED TRYING INQUIRY ON USERID. TYPE 0 LERROR EXIT RC -EXIT EXIT 999 VSEID EXEC: TRACE ALL ME = 1 CP SET RUN ON * * *CAUTION * THE FOLLOWING COMMAND HAS X'15' * *CAUTION * BETWEEN THE WORDS GUEST AND IPL. * *CAUTION * ISSUE THE 'SET HEX ON' COMMAND* *CAUTION * BEFORE CHANGING THIS LINE.* * * *EACH COMMAND MUST BE FOLLOWED BY A X'15'.* *TO ACCOMPLISH THIS; * *1). SET HEX ON * *2). KEY THE COMMANDS(LEAVING 2 SPACES BETWEEN EACH) ON 1 LINE* *3). BRING THE LINE JUST KEYED TO THE CURRENT LINE. * *4). CH /X'4040'/X'15'/1 N (N = THE NUMBER OF COMMANDS) * *5). FILE * * CP TERM CONM 3270 BRE GUESTIPL 1A6 CLEAR * CP TERM CONM 3270 BRE GUESTIPL 1A7
Re: Trapping output right after LOGON
On Tuesday, 03/02/2010 at 08:50 EST, Frank M. Ramaekers framaek...@ailife.com wrote: This is the first time I?ve seen (well, in an early post on this thread) the OBSERVER operand on the CONSOLE statement. So, I looked it up and it doesn?t really explain it. Can someone enlighten me as to the purpose of the OBSERVER operand. So that you get the equivalent of SET OBSERVER instead of SET SECUSER. Alan Altmark z/VM Development IBM Endicott
Re: Trapping output right after LOGON
I wouldn't say that placing LINKs in execs/control files is that much easier that updating the CP directory. Additionally: the directory is the natural place to define virtual machine configurations. Not that I'm entirely against other solutions if they make life much easier... I just like to have only one person modifying the directory. (That way somebody does not load a new directory not knowing someone else changed something, but never loaded it.) Having them elsewhere also allows others to modify them without giving them access to MAINT. Easier? Flip a coin. Safer? I think so. Easier than making all the changes you are considering based on other emails in this thread? Much easier. :-) Tony Thigpen -Original Message - From: Kris Buelens Sent: 03/02/2010 07:57 AM I wouldn't say that placing LINKs in execs/control files is that much easier that updating the CP directory. Additionally: the directory is the natural place to define virtual machine configurations. Not that I'm entirely against other solutions if they make life much easier... I also performed a test (I was right once and wrong once). * CP SET CPCONIO IUCV is indeed required to trap SCIF messages (OK by default if you use PROP, VM:Operator, Operations Manager or alike). * COMMAND SPOOL CONSOLE START doesn't help to catch device problems (LINK/MDISK/DEDICATE/...) The definiton USER EREP EREP 0008192K 0016384K FGBC * ENVIRONMENTAL RECORDING AND EDITING AND PRINTING INCLUDE GENERCMS ACCOUNT EREP C/O-8541 COMMAND SPOOL CON START TO KRIS IUCV *LOGREC CONSOLE 0009 3215 T KRIS OBS LINK MAINT 0201 0201 RR MDISK 0191 3390 228 2 VTE001 MR MDISK 3390 228 2 NODISK MR *DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC19920601 CRCD[ The resulting console created by COMMAND:SPOOL ... File (none) (none) from EREP at VMKBBR01 Format is CONSOLE. * * * Top of File * * * z/VM 5.3 - 20 Jun 2008 - rsu703 HCPCRC8064I Recording data retrieval has been started; reco HCPRET8056I RECORDING RETRIEVAL DISK 88% FULL COMMAND ACCEPTED * * * End of File * * * With WAKEUP: tstrex TSTREX allows you to interactively execute REXX instructions - each instruction string is executed when you hit Enter. environment = CMS Go on - try a few... To end : PF3to dump vars: REXDUMP or DUMP v1 v2 vn or DUMP v. PF15 or EXTRACT /xedit-settings 'WAKEUP +0(IUCVMSG' R(2); TSTREX . cp set CPCONIO IUCV cp xautolog erep do until rc5;'WAKEUP +00:05(IUCVMSG QUIET';end 'PIPE STACK!CONS' *CP KRIS EREP: COMMAND ACCEPTED *CP KRIS EREP: HCPRET8056I RECORDING RETRIEVAL DISK 88% FULL *CP KRIS EREP: HCPCRC8064I Recording data retrieval has been started; recording *LOGREC for userid EREP. *CP KRIS EREP: z/VM 5.3 - 20 Jun 2008 - rsu703 *CP KRIS HCPCLS6056I XAUTOLOG information for EREP: The IPL command is verified by the IPL command processor. *CP KRIS AUTO LOGON *** EREP USERS = 7 *CP KRIS EREP: HCPLNM108E EREP not linked; volid NODISK not mounted *CP KRIS Command accepted *MSGRACFVM ICH70001I EREP LAST ACCESS AT 13:29:42 ON TUESDAY, MARCH 2 2010 R; TSTREX ... 2010/3/2 Tony Thigpen t...@vse2pdf.com mailto:t...@vse2pdf.com Mikes suggestion is what I use. I place all LINK commands for VSE disks in an exec on the shared 191 disk. This is an easy solution to your problem and it makes maintenance of the VSE dasd much easier. No longer will you need to modify the directory to add a new VSE volume. Just link WR to the VSE 191 shared disk and change it. I would suggest the same for VCTCAs and such. Keep changes to the directory to the minimum. Tony Thigpen -Original Message - From: Mike Walter Sent: 03/01/2010 03:55 PM Mike, Along those lines, would it be feasible to move the CP Directory LINK statements for each guest into a CMS file where the shared PROFILE EXEC resides? There could be one file for COMMVSE CMDS containing LINK commands that every VSE guest issues. Then a separate file for each guest that has special needs (let's not go there regarding comments about how all VSE guests have special needs: - it's not Friday yet!). ;-) For example: VSE1 CMDS contains only LINK (and/or other!) commands required by that server. VSE2 CMDS contains only LINK (and/or other!) commands required by that server. And so on... The common PROFILE EXEC would issue: address CMS 'STATE COMMVSE CMDS *'
Re: Trapping output right after LOGON
Hello Laurent, I think I will go with your approach. I will contact our automation group and see if they can handle it. Thanks for your interest and your offer of assistance. Thanks to the rest of the list for their interest as well. Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of DUBOIS Laurent (EXT DUBOIS) Sent: March 2, 2010 8:12 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Hi Mike, I just found your topics and if you use VM/OPERATOR, you got the answer. When you have your VSE guest machine IPL'ed, you get all the message on the VM/OPERATOR console (if you have defined the VM/OPERATOR machine as a SECUSER for your guest). Below is the VM:OPERATOR log for a Linux machine I IPL'ed with missing dasd : 14:07:33 Z600561 VMYINI019R Enter: xautolog linux8 14:07:33 Z600561 Command accepted 14:07:33 Z600561 VMYINI006I 0.000 Ready; 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0100 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0101 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0102 not linked; volid DULX81 not mounted 4:07:33 LINUX8 *8 NIC F000 is created; devices F000-F002 defined 14:07:33 LINUX8 *8 NIC E000 is created; devices E000-E002 defined 14:07:33 LINUX8 *8 HCPNDF2787E NIC E000 not connected; LAN SYSTEM VSW1 does not exist 14:07:33 OPLINUX *3 AUTO LOGON *** LINUX8 USERS = 230 14:07:33 OPLINUX *3 HCPCLS6056I XAUTOLOG information for LINUX8: The IPL command is verified by the IPL command processor. You just have to trap the message HCPLNM108E with the VM/OPERATOR and do whatever you want. If you want any help, you can get back to me, I use VM/OPERATOR. (unfortunately for you, I go on hollidays this evening for 10 days) I can help you,it is easy. Regards :-) Laurent Dubois - Equipe VM Laurent Dubois * laurent.dub...@sncf.fr mailto:mlaurent.dub...@sncf.fr * 03 28 55 63 88 - 22 53 88 * 03 28 55 55 90 - 22 55 90 Prestataire externe SNCF - DSIV OS MM Systeme VM Tour de Lille Boulevard de Turin - 59777 EURALILLE PQ*Avant d'imprimer, pensez à l'environnement De : The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] De la part de Horlick, Michael Envoyé : lundi 1 mars 2010 20:52 À : IBMVM@LISTSERV.UARK.EDU Objet : Re: Trapping output right after LOGON What do you mean by « Changing LINK to COMMAND LINK may help, that's for sure. I have MDISK statements for my VSE minidisks. Also, we run VM:Operator and not PROP. One of the guys in our automation group set up VM:Operator and I wonder if he knows how to handle output right from an XAUTOLOG of a virtual machine. Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: March 1, 2010 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Mike, I think I tried COMMAND SPOOL CONS START but COMMANDs seem to be executed after the devices are set up, hence too late to catch problems with MDISK statements. Changing LINK to COMMAND LINK may help, that's for sure. 2010/3/1 Mike Walter mike.wal...@hewitt.com Look up the directory COMMAND statement in the CP Planning and Administration manual. E.g. In the CP Directory entry for each VM userid for which you want the virtual console started as the VM is constructed the line: COMMAND SPOOL CONSOLE START Only CP commands may be entered into the CP Directory for users. You may specify any CP command argument. More details in the manual. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Horlick, Michael michael.horl...@cgi.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/01/2010 12:41 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Trapping output right after LOGON Greetings, I would like to trap all the CP console output from a virtual machine from its initial XAUTOLOG/LOGON. I have several z/VSE machines which are XAUTOLOGed on by the operator. Reason? In rare instances, maybe a pack is not attached to the system which contains some minidisks used by these machines. I know there could be a message such as: HCPLNM108E MIKE A194 not linked; volid XT160D not
Re: VM-L Online
http://listserv.uark.edu/archives/ibmvm.html John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Tim Joyce Sent: Tuesday, March 02, 2010 8:47 AM To: IBMVM@LISTSERV.UARK.EDU Subject: VM-L Online Hey Guys, Is there a web address that can be used to search past VM posts online? Tim Tim Joyce Sr. Systems Programmer / Project Leader Alex Lee, Inc. Email : tim.jo...@alexlee.com Phone: (828) 725-4448
Bob Crofoot passed away 2/25/2010
I suspect that Bob was not widely known outside of IBM Endicott. I'm not sure he ever attended a SHARE, for example. But he was a wonderful person and I wanted to let people know who were at IBM Endicott at one time but may not be aware of his passing. His wife, Kay, was manager of the REXX development group at the time of my disability retirement in Jan. 1991. I am including the obituary from today's [Binghamton, NY] Press Sun Bulletin below. Kent Taylor Jon Robert Bob Crofoot of Tucson, AZ Jon Robert Bob Crofoot, 74 years old, passed away peacefully February 25, 2010 in Tucson, AZ. Bob was born September 27, 1935 in Auburn, NY. He was the son of the late Neal Page Crofoot and Helen McCue Crofoot. Bob grew up in Syracuse, NY and graduated from the SUNY College of Environmental Science and Forestry and Syracuse University. On July 18, 1970 Bob married Kathryn Kay Krueger of Bad Axe, MI. They lived for many years in Newark Valley, NY and Endicott, NY, where Bob was a computer programmer and technical writer for IBM. They became full time residents of SaddleBrooke, AZ in 2007. Known for his colorful personality, Bob was at heart a very kind and gentle man and extremely witty. He enjoyed reading about the latest scientific developments, particularly in space exploration and astronomy. He was a member and former secretary of the SaddleBrooke Skygazers (he called them the Skygeezers), and a past president of the IBM Personal Computer Club in Endicott. Bob had a wide range of interests in such diverse fields as painting and drawing, woodworking, rock collecting and geology, cooking, pottery, linguistics, welding, photography, travel, and genealogy. He had an inquiring and creative mind, liked to experiment, and was always thinking of new things to try. Despite serious health problems in recent years, he was able to pursue many of his favorite activities until the end of his life. Bob is survived by his wife Kay and a sister-in-law, Barbara A. Krueger, of Saginaw, Michigan. A memorial service will be held at 3 p.m. Tuesday, March 2, at Vistoso Funeral Home, 2285 E. Rancho Vistoso Blvd., Oro Valley, AZ. Memorials may be made to the American Lung Association. To leave an online condolence please visit www.vistosofuneralhome.com 544-2285
Re: Trapping output right after LOGON
Actually I tried it with WAKEUP and it's working with RC=5. Will still go with VM:Operator, I think. Thanks, Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of dshupe Sent: March 2, 2010 10:10 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Mike, Glad you got an answer. The 'WAKEUP' answer from Kris B (RC=5 from wakeup) - Have coded a working model if you want it. I plan to use it to capture z/Linux NIC errors when a GRANT has been missed, for starters. Regards, Doug From: Horlick, Michael michael.horl...@cgi.com To: IBMVM@LISTSERV.UARK.EDU Sent: Tue, March 2, 2010 9:50:31 AM Subject: Re: Trapping output right after LOGON Hello Laurent, I think I will go with your approach. I will contact our automation group and see if they can handle it. Thanks for your interest and your offer of assistance. Thanks to the rest of the list for their interest as well. Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of DUBOIS Laurent (EXT DUBOIS) Sent: March 2, 2010 8:12 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Hi Mike, I just found your topics and if you use VM/OPERATOR, you got the answer. When you have your VSE guest machine IPL'ed, you get all the message on the VM/OPERATOR console (if you have defined the VM/OPERATOR machine as a SECUSER for your guest). Below is the VM:OPERATOR log for a Linux machine I IPL'ed with missing dasd : 14:07:33 Z600561 VMYINI019R Enter: xautolog linux8 14:07:33 Z600561 Command accepted 14:07:33 Z600561 VMYINI006I 0.000 Ready; 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0100 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0101 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0102 not linked; volid DULX81 not mounted 4:07:33 LINUX8 *8 NIC F000 is created; devices F000-F002 defined 14:07:33 LINUX8 *8 NIC E000 is created; devices E000-E002 defined 14:07:33 LINUX8 *8 HCPNDF2787E NIC E000 not connected; LAN SYSTEM VSW1 does not exist 14:07:33 OPLINUX *3 AUTO LOGON *** LINUX8 USERS = 230 14:07:33 OPLINUX *3 HCPCLS6056I XAUTOLOG information for LINUX8: The IPL command is verified by the IPL command processor. You just have to trap the message HCPLNM108E with the VM/OPERATOR and do whatever you want. If you want any help, you can get back to me, I use VM/OPERATOR. (unfortunately for you, I go on hollidays this evening for 10 days) I can help you,it is easy. Regards :-) Laurent Dubois - Equipe VM Laurent Dubois * laurent.dub...@sncf.fr mailto:mlaurent.dub...@sncf.fr * 03 28 55 63 88 - 22 53 88 * 03 28 55 55 90 - 22 55 90 Prestataire externe SNCF - DSIV OS MM Systeme VM Tour de Lille Boulevard de Turin - 59777 EURALILLE PQ*Avant d'imprimer, pensez à l'environnement De : The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] De la part de Horlick, Michael Envoyé : lundi 1 mars 2010 20:52 À : IBMVM@LISTSERV.UARK.EDU Objet : Re: Trapping output right after LOGON What do you mean by « Changing LINK to COMMAND LINK may help, that's for sure. I have MDISK statements for my VSE minidisks. Also, we run VM:Operator and not PROP. One of the guys in our automation group set up VM:Operator and I wonder if he knows how to handle output right from an XAUTOLOG of a virtual machine. Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc , H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: March 1, 2010 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Mike, I think I tried COMMAND SPOOL CONS START but COMMANDs seem to be executed after the devices are set up, hence too late to catch problems with MDISK statements. Changing LINK to COMMAND LINK may help, that's for sure. 2010/3/1 Mike Walter mike.wal...@hewitt.com Look up the directory COMMAND statement in the CP Planning and Administration manual. E.g. In the CP Directory entry for each VM userid for which you want the virtual console started as the VM is constructed the line: COMMAND SPOOL CONSOLE START Only CP commands
AUTO: Nik Johnston/UK/IBM is away from the office (returning 09/03/2010)
I am out of the office until 09/03/2010. I am currently out of the office on annual leave. If it is urgent then please contact Rachel Hill for all ITS Server Managed Services or Dan Murphy of the ITS SDCoE for related matters. Note: This is an automated response to your message Re: Trapping output right after LOGON sent on 2/3/10 11:35:12. This is the only notification you will receive while this person is away.
Re: VM-L Online
Try this. http://listserv.uark.edu/archives/ibmvm.html You might have to signon using an id that was supplied when you subscribed to IBMVM Billy On 2 Mar 2010 at 9:46, Tim Joyce wrote: Hey Guys, Is there a web address that can be used to search past VM posts online? Tim Tim Joyce Sr. Systems Programmer / Project Leader Alex Lee, Inc. Email : tim.jo...@alexlee.com Phone: (828) 725-4448
Re: Trapping output right after LOGON
On Tue, Mar 2, 2010 at 9:01 AM, Alan Altmark alan_altm...@us.ibm.comwrote: So that you get the equivalent of SET OBSERVER instead of SET SECUSER. I think he meant, What use is it? The answer is that it's (sort of) a R/O SECUSER: you see the output but you can't do a CP SEND back. And OBSERVER output isn't quite tagged the same as SECUSER output (which I discovered to my frustration when it first came out).
Re: Trapping output right after LOGON
On Tue, Mar 2, 2010 at 12:32 PM, Alan Altmark alan_altm...@us.ibm.comwrote: Off the top of my head: Secondary user - Can use CP SEND to the primary - Only sees console output of primary when primary is disconnected - Class G secondary can SEND only when primary is disconnected - Class C secondary can SEND at any time - Traffic to primary's *MSG connection is stopped while secondary is logged on Observer - Cannot SEND to the observed virtual machine (observee) - Sees all console traffic without regard to connect/disconnect status of the observee - Does not interfere with observee's *MSG traffic And as you note, the programming characteristics via *MSG are different for the observer and the secondary user. Thanks. I hope it didn't sound like I thought OBSERVER was broken -- my post was just to hopefully help others not make the same assumption I did, that it was JUST a R/O SECUSER. It's a nice facility. -- zMan -- I've got a mainframe and I'm not afraid to use it
3590E Tapes
How would I go about getting the type of cartridge (J or K) loaded on the 3590E tape unit attached to my CMS userid by using a bit of software? IThanks. Jim Hughes 603-271-5586 It is fun to do the impossible.
Re: 3590E Tapes
Using the bit of software called: TELL (or CP MSG): TELL OPERATOR Hey! Is that a type J or K cart on the 3590E drive? ;-) It's a long way to Friday... :-( Hughes, Jim jim.hug...@doit.nh.gov Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/02/2010 01:00 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject 3590E Tapes How would I go about getting the type of cartridge (J or K) loaded on the 3590E tape unit attached to my CMS userid by using a bit of software? IThanks. Jim Hughes 603-271-5586 It is fun to do the impossible. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: 3590E Tapes
I tried that. They can't see the letters once it's in the drive. Jim Hughes 603-271-5586 It is fun to do the impossible. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Tuesday, March 02, 2010 2:04 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: 3590E Tapes Using the bit of software called: TELL (or CP MSG): TELL OPERATOR Hey! Is that a type J or K cart on the 3590E drive? ;-) It's a long way to Friday... :-( Hughes, Jim jim.hug...@doit.nh.gov Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/02/2010 01:00 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject 3590E Tapes How would I go about getting the type of cartridge (J or K) loaded on the 3590E tape unit attached to my CMS userid by using a bit of software? IThanks. Jim Hughes 603-271-5586 It is fun to do the impossible. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Trapping output right after LOGON
Well , I told me my automation guy to use VMOPER to trap messages starting with 'HCP' and ending with an 'E' and I got an unexpected side effect. After XAUTOLOGing the user, It did trap the HCPLNM108E message that indicates the minidisk was not linked but it also trapped some other messages at IPL CMS time. The SYSPROF EXEC invokes another EXEC that does a bunch of accesses. Now some of those minidisk don't exist (it's an old EXEC). I see on VM:Operator console: 14:17:24 VSEMAINTB*8 Mdisk 31B accessed as H/H SYSCOR Technical Minidisk. 14:17:24 VSEMAINTB*8 Mdisk 49E accessed as I/I SYSCOR Disk 1. 14:17:24 VSEMAINTB*8 Mdisk 59E accessed as J/J SYSCOR Disk 2. 14:17:24 VSEMAINTB*8 Mdisk 491 accessed as K/K SYSCOR Production JCL. 14:17:25 VSEMAINTB*8 Mdisk 317 accessed as N/N DITTO for VSE and VM. 14:17:25 VSEMAINT *8 HCPQVD040E Device 0318 does not exist 14:17:25 VSEMAINTB*8 Mdisk 319 accessed as P/P Program Products. 14:17:25 VSEMAINTB*8 Mdisk 219 accessed as Q/Q Program Products (old). 14:17:25 VSEMAINTB*8 Mdisk 31D accessed as U/U SYSCOR OEM Programs. 14:17:25 VSEMAINTB*8 Mdisk 31C accessed as V/V SYSCOR Operations. 14:17:25 VSEMAINTB*8 Mdisk 31A accessed as X/X SYSCOR User Installed Applicat 14:17:25 VSEMAINT *8 HCPQVD040E Device 031E does not exist Those HCLQVD040E messages got trapped. Now, if I logoff that user and actually logon to user, I don't see the HCPQVD040E messages?? Now, I'm debating to just trap the HCPLNM108E, but will I miss out on any other error messages that could appear right after LOGON? Maybe I should create dummy 318/31E to get rid of problem? Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Horlick, Michael Sent: March 2, 2010 10:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Actually I tried it with WAKEUP and it's working with RC=5. Will still go with VM:Operator, I think. Thanks, Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of dshupe Sent: March 2, 2010 10:10 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Mike, Glad you got an answer. The 'WAKEUP' answer from Kris B (RC=5 from wakeup) - Have coded a working model if you want it. I plan to use it to capture z/Linux NIC errors when a GRANT has been missed, for starters. Regards, Doug From: Horlick, Michael michael.horl...@cgi.com To: IBMVM@LISTSERV.UARK.EDU Sent: Tue, March 2, 2010 9:50:31 AM Subject: Re: Trapping output right after LOGON Hello Laurent, I think I will go with your approach. I will contact our automation group and see if they can handle it. Thanks for your interest and your offer of assistance. Thanks to the rest of the list for their interest as well. Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of DUBOIS Laurent (EXT DUBOIS) Sent: March 2, 2010 8:12 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON Hi Mike, I just found your topics and if you use VM/OPERATOR, you got the answer. When you have your VSE guest machine IPL'ed, you get all the message on the VM/OPERATOR console (if you have defined the VM/OPERATOR machine as a SECUSER for your guest). Below is the VM:OPERATOR log for a Linux machine I IPL'ed with missing dasd : 14:07:33 Z600561 VMYINI019R Enter: xautolog linux8 14:07:33 Z600561 Command accepted 14:07:33 Z600561 VMYINI006I 0.000 Ready; 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0100 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0101 not linked; volid DULX80 not mounted 14:07:33 LINUX8 *8 HCPLNM108E LINUX8 0102 not linked; volid DULX81 not mounted 4:07:33 LINUX8 *8 NIC F000 is created; devices F000-F002 defined 14:07:33 LINUX8 *8 NIC E000 is created; devices E000-E002 defined 14:07:33 LINUX8 *8 HCPNDF2787E NIC E000 not connected; LAN SYSTEM VSW1 does not exist 14:07:33 OPLINUX *3 AUTO LOGON *** LINUX8 USERS = 230 14:07:33 OPLINUX *3 HCPCLS6056I XAUTOLOG information for LINUX8: The IPL command is verified by the
Re: 3590E Tapes
If you have DITTO try TB (tape browse), I think it shows some cartridge attributes in the line under the drive's attributes From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Hughes, Jim Sent: Tuesday, March 02, 2010 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: 3590E Tapes How would I go about getting the type of cartridge (J or K) loaded on the 3590E tape unit attached to my CMS userid by using a bit of software? IThanks. Jim Hughes 603-271-5586 It is fun to do the impossible. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
Re: Trapping output right after LOGON
On Tue, Mar 2, 2010 at 2:44 PM, Horlick, Michael michael.horl...@cgi.comwrote: Well , I told me my automation guy to use VMOPER to trap messages starting with ‘HCP’ and ending with an ‘E’ and I got an unexpected side effect. After XAUTOLOGing the user, It did trap the HCPLNM108E message that indicates the minidisk was not linked but it also trapped some other messages at IPL CMS time. The SYSPROF EXEC invokes another EXEC that does a bunch of accesses. Now some of those minidisk don’t exist (it’s an old EXEC). I see on VM:Operator console: 14:17:24 VSEMAINTB*8 Mdisk 31B accessed as H/H SYSCOR Technical Minidisk. 14:17:24 VSEMAINTB*8 Mdisk 49E accessed as I/I SYSCOR Disk 1. 14:17:24 VSEMAINTB*8 Mdisk 59E accessed as J/J SYSCOR Disk 2. 14:17:24 VSEMAINTB*8 Mdisk 491 accessed as K/K SYSCOR Production JCL. 14:17:25 VSEMAINTB*8 Mdisk 317 accessed as N/N DITTO for VSE and VM. 14:17:25 VSEMAINT *8 HCPQVD040E Device 0318 does not exist 14:17:25 VSEMAINTB*8 Mdisk 319 accessed as P/P Program Products. 14:17:25 VSEMAINTB*8 Mdisk 219 accessed as Q/Q Program Products (old). 14:17:25 VSEMAINTB*8 Mdisk 31D accessed as U/U SYSCOR OEM Programs. 14:17:25 VSEMAINTB*8 Mdisk 31C accessed as V/V SYSCOR Operations. 14:17:25 VSEMAINTB*8 Mdisk 31A accessed as X/X SYSCOR User Installed Applicat 14:17:25 VSEMAINT *8 HCPQVD040E Device 031E does not exist Those HCLQVD040E messages got trapped. Now, if I logoff that user and actually logon to user, I don’t see the HCPQVD040E messages?? Now, I’m debating to just trap the HCPLNM108E, but will I miss out on any other error messages that could appear right after LOGON? Maybe I should create dummy 318/31E to get rid of problem? You did notice that the HCPQVD msgs were from VEMAINT, NOT VSEMAINTB?
Re: Trapping output right after LOGON
The user I played with was user VSEMAINT. I changed the CONSOLE statement to CONSOLE 0009 3215 T VMOPER and then I XAUTOLOGED user VSEMAINT on. I chose this user because all the VSEs have a R/O LINK to its 191 disk. Inside the PROFILE EXEC it checks userid and then IPL's off VSE SYSRES pack Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of zMan Sent: March 2, 2010 2:56 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON On Tue, Mar 2, 2010 at 2:44 PM, Horlick, Michael michael.horl...@cgi.com wrote: Well , I told me my automation guy to use VMOPER to trap messages starting with 'HCP' and ending with an 'E' and I got an unexpected side effect. After XAUTOLOGing the user, It did trap the HCPLNM108E message that indicates the minidisk was not linked but it also trapped some other messages at IPL CMS time. The SYSPROF EXEC invokes another EXEC that does a bunch of accesses. Now some of those minidisk don't exist (it's an old EXEC). I see on VM:Operator console: 14:17:24 VSEMAINTB*8 Mdisk 31B accessed as H/H SYSCOR Technical Minidisk. 14:17:24 VSEMAINTB*8 Mdisk 49E accessed as I/I SYSCOR Disk 1. 14:17:24 VSEMAINTB*8 Mdisk 59E accessed as J/J SYSCOR Disk 2. 14:17:24 VSEMAINTB*8 Mdisk 491 accessed as K/K SYSCOR Production JCL. 14:17:25 VSEMAINTB*8 Mdisk 317 accessed as N/N DITTO for VSE and VM. 14:17:25 VSEMAINT *8 HCPQVD040E Device 0318 does not exist 14:17:25 VSEMAINTB*8 Mdisk 319 accessed as P/P Program Products. 14:17:25 VSEMAINTB*8 Mdisk 219 accessed as Q/Q Program Products (old). 14:17:25 VSEMAINTB*8 Mdisk 31D accessed as U/U SYSCOR OEM Programs. 14:17:25 VSEMAINTB*8 Mdisk 31C accessed as V/V SYSCOR Operations. 14:17:25 VSEMAINTB*8 Mdisk 31A accessed as X/X SYSCOR User Installed Applicat 14:17:25 VSEMAINT *8 HCPQVD040E Device 031E does not exist Those HCLQVD040E messages got trapped. Now, if I logoff that user and actually logon to user, I don't see the HCPQVD040E messages?? Now, I'm debating to just trap the HCPLNM108E, but will I miss out on any other error messages that could appear right after LOGON? Maybe I should create dummy 318/31E to get rid of problem? You did notice that the HCPQVD msgs were from VEMAINT, NOT VSEMAINTB?
Re: Trapping output right after LOGON
On Tue, Mar 2, 2010 at 3:05 PM, Horlick, Michael michael.horl...@cgi.comwrote: The user I played with was user VSEMAINT. I changed the CONSOLE statement to CONSOLE 0009 3215 T VMOPER and then I XAUTOLOGED user VSEMAINT on. I chose this user because all the VSEs have a R/O LINK to its 191 disk. Inside the PROFILE EXEC it checks userid and then IPL’s off VSE SYSRES pack Ah, right, notwithstanding my typo, VSEMAINTB would be 9 bytes. Hard to tell what it did remotely, though!
SPXTAPE
Hi If I use SPXTAPE to DUMP my spool volumes can I load them back to spool volumes with different names? Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191
Re: SPXTAPE
Absolutely: YES! Just be 100% certain that you get the somewhat arcane SPXTAPE syntax exactly correct. Check the reader files that come back to be sure that you did not miss critical SDF's (i.e. IMG, NSS, UCR, TRF and NLS files that are stored on SPOOL) during the SPXTAPE DUMP. If you don't get the syntax right on the SPXTAPE LOAD you can always to it again (being careful not to re-load files a second time, of course). I prefer a 'CP Q FILES' and 'CP Q SDF' from a class 'D' (spooling) userid just before the SPXTAPE DUMP, and then again on the target system after the SPXTAPE LOAD. Should be pretty close numbers (there may be a few rdr/prt/pun file differences, but the SDFs should match exactly). Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 03/02/2010 03:33 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject SPXTAPE Hi If I use SPXTAPE to DUMP my spool volumes can I load them back to spool volumes with different names? Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
New paper Sharing and Maintaining SLES 11 Linux under z/VM using DCSSs and an NSS
There is a new paper, Sharing and Maintaining SLES 11 Linux under z/VM using DCSSs and an NSS, available on a new Web page at: http://www.vm.ibm.com/linux/dcss/ In 2007, there was collaboration between IBM and Nationwide insurance that resulted in the Redpaper Sharing and maintaining Linux under z/VM, published in Feb of '08, on the Web at http://www.redbooks.ibm.com/abstracts/redp4322.html . This introduced the concept of read-only-root. Thanks to many, especially Steve Womer and Rick Troth on that paper. In 2009, there was collaboration between, Penn State, IBM, and later Red Hat to publish two papers, Sharing and maintaining SLES 10 SP2 Linux under z/VM and Sharing and maintaining RHEL 5.3 Linux under z/VM . They are near the top of http://linuxvm.org/present/ . These papers expounded upon the maintenance part of the title and upgraded to both SLES and RHEL current releases. Thanks to many again, especially Brian France, Kyle Black, and Brad Hinson on those papers. At a meeting in Endicott when the previous papers were kicked-off, a z/VM developer asked why we were using read-only LINKs to minidisks and not DCSSs. After the two papers in '09 were completed, and with help from Carlos Ordonez and Vic Cross of IBM, I have been working on the subject paper to answer the question of the Endicott developer. Thanks to the many listed in the paper. It was a challenging paper to complete, and it's not simple to implement. It does have two sections that show how to go from a conventional read-write gold master to a read-only counterpart - one shows the manual steps to convey an understanding of the process, and the other shows an automated step, with an associated bash script, to improve the speed and reliability of the process. I asked a person, for whom I have a lot of respect, to review it. He looked at it briefly and wrote: ... it is rather complicated matter, yet some of the instructions suggest that you could leave it to the novice Linux admin to follow the recipe I would be interested to see someone demonstrate it is worth the trouble... So, you've been warned :)) Enjoy reading, and try to implement if you have access to the resources and you dare :)) Still, perhaps it will help us mainframers blaze a trail for Linux as a whole, using some of the tried and tested techniques that *have* proven to be worth the trouble... Of course, feedback is welcome. Mike MacIsaac mike...@us.ibm.com (845) 433-7061
Re: SPXTAPE
Yes, you restore spool files,not spool packs. 2010/3/2 Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov Hi If I use SPXTAPE to DUMP my spool volumes can I load them back to spool volumes with different names? *Thank You,* * * *Terry Martin* *Lockheed Martin - Citic* *z/OS and z/VM Performance Tuning and Operating Systems Support* *Office - 443 348-2102* *Cell - 443 632-4191* -- Kris Buelens, IBM Belgium, VM customer support
Re: SPXTAPE
If you don't get the syntax right on the SPXTAPE LOAD you can always to it again (being careful not to re-load files a second time, of course). You can use the NODUP operand on SPXTAPE LOAD to prevent loading of the same files more than once. John Franciscovich z/VM Development
Re: Trapping output right after LOGON
We've seen these additional differences between SECUSER and OBSERVER processing - Secondary user sees message HCP150A when the primary is disconnected and VM or CP read is issued, observer does not. It doesn't appear that an OBSERVER, even with class C SEND, can satisfy a VM read issued by a disconnected user. On our system, the SEND is honored, but everything is processed by CP on the target user, whereas with SECUSER, the input is passed to the guest unless sent with SEND CP. I know that's poorly worded. Example: USERA has USERB as SECUSER, is disconnected, RUN ON, and issues a VM READ. USERB (with or without class C) does SEND USERA Q DISK and sees the normal CMS Q DISK output. USERA has USERB as OBSERVER, is disconnected, RUN ON, and issues a VM READ. USERB (who has class C) does SEND USERA Q DISK and sees HCPCQV003E Invalid Option - DISK. Steve On Tue, 2 Mar 2010, Alan Altmark wrote: Off the top of my head: Secondary user - Can use CP SEND to the primary - Only sees console output of primary when primary is disconnected - Class G secondary can SEND only when primary is disconnected - Class C secondary can SEND at any time - Traffic to primary's *MSG connection is stopped while secondary is logged on Observer - Cannot SEND to the observed virtual machine (observee) - Sees all console traffic without regard to connect/disconnect status of the observee - Does not interfere with observee's *MSG traffic And as you note, the programming characteristics via *MSG are different for the observer and the secondary user. -- Steve Marak -- sama...@gizmoworks.com
Re: Trapping output right after LOGON
On Wednesday, 03/03/2010 at 12:04 EST, Steve Marak sama...@gizmoworks.com wrote: We've seen these additional differences between SECUSER and OBSERVER processing - Secondary user sees message HCP150A when the primary is disconnected and VM or CP read is issued, observer does not. It doesn't appear that an OBSERVER, even with class C SEND, can satisfy a VM read issued by a disconnected user. On our system, the SEND is honored, but everything is processed by CP on the target user, whereas with SECUSER, the input is passed to the guest unless sent with SEND CP. I know that's poorly worded. Example: USERA has USERB as SECUSER, is disconnected, RUN ON, and issues a VM READ. USERB (with or without class C) does SEND USERA Q DISK and sees the normal CMS Q DISK output. USERA has USERB as OBSERVER, is disconnected, RUN ON, and issues a VM READ. USERB (who has class C) does SEND USERA Q DISK and sees HCPCQV003E Invalid Option - DISK. On my system, I don't get any output at all; the command simply goes into the target user's console input buffer. Subsequent SENDs get RC=36 console input waiting (aka NOT ACCEPTED) and I have to SEND CP USERA ATTN to the guest to process the command QUERY DISK. (I don't get HCP003E, implying equivalent of TERM MODE CP on the target.) It all works fine with SECUSER, though I get the same no-output problem on the first SEND after I turn off OBSERVER and turn on SECUSER. As far as failing to get HCP150A, that is somewhat ambiguous. As with SET OBSERVER, the SET SECUSER command does not document that one could expect to get HCP150A, but it is mentioned on CP SEND as the impetus to issue the SEND. It gets a little stranger since OBSERVER works with a connected user, but HCP150A is issued only when the primary is disconnected. I think a call to the Support Center is in order. IMO: - HCP150A should be sent to an observer as well as to a secondary user - HCP150A should be send to an observer even if the primary is logged on - The results of a class C SEND should be the same whether you are observer or secuser Alan Altmark z/VM Development IBM Endicott
