> I don't think it works for my 5.2 system Correct. The "z/VM Migration Guide" shows that the directory "COMMAND" statement made it's first (and welcome!) appearance in z/VM 5.3.
Nonetheless, it would not help since the LINK command would be failing (given the missing ATTACHed DASD) at logon, appearing in the console log started at logon. Unless you post-processed the console log from the PROFILE EXEC (or something else triggered thereafter), the message from logon won't do any good. But at least it provides footprints for later evaluation. If you want to trap the logon LINK messages, even something like 'SET OBSERVER' (followed by the AUTOLOG or XAUTOLOG) won't help since the target userid is not yet logged on. I'm afraid that PROP (or VM:Operator, or IBM's Operations Manager?) is probably your best option, with the target VM's directory entry set to display on the PROP handler's console. Note that the PROP (or other SCIF product) does NOT need to run on OPERATOR. You can set up another userid to run PROP (or other SCIF product) to handle these 'edge' situations. The AUTOLOGed machines would need to SCIF their output to that PROP handler (e.g. the directory statement something like: "CONSOLE 009 3215 C prop_target_userid" ) 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 01:26 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 Well, I tried the COMMAND statement but I don't think it works for my 5.2 system. I wanted to use an existing service machine that uses WAKEUP but if I need to use PROP then I'll do that as a last resort. Mike Horlick Conseiller CGI Gestion Intégrée des Technologies 1350 Boul. René-Lévesque Ouest Montréal, Qc, H3G 1T4 -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: March 1, 2010 2:03 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Trapping output right after LOGON In the immortal words of Ernestine the Telephone Operator (played by Lily Tomlin): "Never mind". With the COMMAND statement you will indeed "see" the logon error messages in the console log, but the VM initialization is not complete enough to trap the responses. PROP (the Programmable Operator Facility) was suggested by others. IMHO a good suggestion. 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. 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.
