I second having HCPLNM108E messages come to the System Operator or
trapped in a SPOOLed CONSOLE without having the id SCIFed.
-----Original Message-----
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter
Sent: Wednesday, November 22, 2006 11:42 AM
To: [email protected]
Subject: Re: "MORE..." time during IPL
That's the same way VM:Secure works; AUTOLOG1 does minimal setup
work and AUTOLOGs VMSECURE; VMSECURE then starts up and then AUTOLOGs
AUTOLOG2 which brings up the "usual suspects".
I have written some code that runs in VMSECURE "PROFILE EXEC"
which keeps checking for VM:Operator (could be PROP) to start up before
VM:Secure begins. That permits VM:Operator (again, could be PROP) to
properly handle any ESM error messages right from the start.
It would be really nice if we could issue some CP commands (such
as starting the virtual console SPOOLing) from the user's directory
entry so that missing devices error messages and such at logon and such
could be logged. Maybe IBM could deliver such a present (going back to
VMSHARE's "NOTE XMASGIFT") in a future z/VM release?
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not
necessarily represent the opinions or policies of Hewitt Associates.
"Colin Allinson" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System" <[email protected]>
11/22/2006 07:29 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>
To
[email protected]
cc
Subject
Re: "MORE..." time during IPL
Sorry for the late append on this subject but I have been away
for the last week.
In this shop we use an ESS (RACF) and take the view that the
sole job of AUTOLOG1 is to start up the ESS - nothing else.
In the way we work OPERATOR has code in it's profile to wait
until either the ESS is available or a set amount of time since the
system IPL has expired.
All of the servers are started by AUTOLOG2 which is autologged
by OPERATOR when it is happy that the time is right, (there are various
checks to ensure that this is only done after an IPL and to allow
AUTOLOG2 processing to be bypassed when this is what we want).
Even though you may not have an ESS there is no reason why you
could not take this approach with AUTOLOG1 setting some value (or
switch) on which OPERATOR could work.
Regards
Colin Allinson
Amadeus Data Processing
_____
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.
--------------------------------------------------------
If you are not an intended recipient of this e-mail, please notify the sender,
delete it and do not read, act upon, print, disclose, copy, retain or
redistribute it. Click here for important additional terms relating to this
e-mail. http://www.ml.com/email_terms/
--------------------------------------------------------
