Re: MORE... time during IPL
Mike Walter [EMAIL PROTECTED] wrote: snip 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. I've always wanted this, but it's important to realize that it's not as simple as adding a card to the directory and a call to HCPCMDxx (I think; it's been a while!) to LOGON processing. There would have to be some restrictions on that commands you can issue -- SHUTDOWN would be, like, bad. SAVESYS? IPL? Do these directory commands come before or after the IPL that's already in the directory? Etc., etc., etc. (No, you can't just restrict it to Class G commands -- someone will make SAVESYS or SHUTDOWN a Class G command. Yeah, your gun your foot, but an *unintuitive* gun and foot, and this is VM, not some other OS). So while I'd love to see it, I understand why it hasn't happened in over 30 years of VM. Maybe some day... ...phsiii
Re: MORE... time during IPL
On 11/22/06, Mike Walter [EMAIL PROTECTED] wrote: 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? Something we did was a mod to pick one spool class as our 'autospool' which meant that when the virtual console device was created at logon with that class (as assigned in the directory) it would issue a SPOOL CON START TO xxx (where xxx was our central spool file collection server). I think we even planned to have a list of classes with target userid, but not sure that ever got done. I don't have the code, but if there's interest I could try and find it again. Rob
Re: MORE... time during IPL
On 23 Nov 2006 at 8:51, Phil Smith III wrote: I've always wanted this, but it's important to realize that it's not as simple as adding a card to the directory and a call to HCPCMDxx (I think; it's been a while!) to LOGON processing. There would have to be some restrictions on that commands you can issue -- SHUTDOWN would be, like, bad. SAVESYS? IPL? Do these directory commands come before or after the IPL that's already in the directory? Etc., etc., etc. (No, you can't just restrict it to Class G commands -- someone will make SAVESYS or SHUTDOWN a Class G command. Yeah, your gun your foot, but an *unintuitive* gun and foot, and this is VM, not some other OS). So while I'd love to see it, I understand why it hasn't happened in over 30 years of VM. Maybe some day... I think spooled console is the function I have seen mentioned most in this context. Would it be so difficult to take the CONSOLE statement and add 2 items? CONSOLE vdev devtype [class [userid [OBSERVER] ] ] [START [recipient] ] START would be a keyword, not necessitating all the previous optional positionals, optionally followed by a userid. This would result in a SPOOL CON START [userid] being the first effective command run by the logging-on virtual machine, so that ALL activity would be caught in the spool. Not a general 'do a CP command', no worries about shutdown, just spooled console *from the start*. Shimon -- ** ** Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 530-9877 fax: 530-9308 ** **
Re: MORE... time during IPL
On: Thu, Nov 23, 2006 at 08:51:13AM -0500,Phil Smith III Wrote: } Mike Walter [EMAIL PROTECTED] wrote: } snip } 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. } } I've always wanted this, but it's important to realize that it's not as simple as adding a card to the directory and a call to HCPCMDxx (I think; it's been a while!) to LOGON processing. There would have to be some restrictions on that commands you can issue -- SHUTDOWN would be, like, bad. SAVESYS? IPL? Do these directory commands come before or after the IPL that's already in the directory? Etc., etc., etc. (No, you can't just restrict it to Class G commands -- someone will make SAVESYS or SHUTDOWN a Class G command. Yeah, your gun your foot, but an *unintuitive* gun and foot, and this is VM, not some other OS). If I were doing it at IBM, I would add an extra operand to the directory SPOOL statement such as: SPOOL 009 . . . . . AUTOstart [to userid|*] and logon would simply do a bit more upon creating the vdev. -- 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: MORE... time during IPL
On 11/23/06, Rich Greenberg [EMAIL PROTECTED] wrote: If I were doing it at IBM, I would add an extra operand to the directory SPOOL statement such as: Anything you change in the directory will also need changes in DirMaint and DIRECTXA, and whatever obligations IBM may have towards an ISV that provides a product in that area. That's why we came up with something that exploits the current directory statements. Rob
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
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 IBMVM@LISTSERV.UARK.EDU 11/22/2006 07:29 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU 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.
MORE... time during IPL
Hi folks, Is there a way to set the MORE time for the operator's console at IPL of z/VM? I've set 'CP TERM MORE 0 1 HOLD OFF' in OPERATOR's PROFILE EXEC, but this does not seem to come into play until near the end of the IPL, long after AUTOLOG1 starts linux guests etc. This is inconvenient for our operators, as we use the Integrated 3270 console on the HMC and they have to manually select Keys Clear from the toolbar of the window to scroll to the next screen, or wait for the MORE time to expire. Thanks in advance, Fred Schmidt Department of Corporate and Information Services (DCIS) Data Centre Services (DCS) Northern Territory Government
