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 Z6005 61 VMYINI019R Enter: xautolog linux8 14:07:33 Z6005 61 Command accepted 14:07:33 Z6005 61 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 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. -- Kris Buelens, IBM Belgium, VM customer support ------- Ce message et toutes les pièces jointes sont établis à l'intention exclusive de ses destinataires et sont confidentiels. L'intégrité de ce message n'étant pas assurée sur Internet, la SNCF ne peut être tenue responsable des altérations qui pourraient se produire sur son contenu. Toute publication, utilisation, reproduction, ou diffusion, même partielle, non autorisée préalablement par la SNCF, est strictement interdite. Si vous n'êtes pas le destinataire de ce message, merci d'en avertir immédiatement l'expéditeur et de le détruire. ------- This message and any attachments are intended solely for the addressees and are confidential. SNCF may not be held responsible for their contents whose accuracy and completeness cannot be guaranteed over the Internet. Unauthorized use, disclosure, distribution, copying, or any part thereof is strictly prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete it.
