Re: SALIPL - Stand Alone Program Loader
Hi Mike, If you wanted some command to do the IPL changing the module name, have you tried = SHUTDOWN REIPL diskaddress 1 MODULE cploadname IPLPARMS CONS=address Regards Edi Lopes Alves Location: IBM Hortolândia - São Paulo - Brazil From: Mike Atkison mike.atki...@mantissa.com To: IBMVM@LISTSERV.UARK.EDU Date: 29/10/2009 13:48 Subject: SALIPL - Stand Alone Program Loader Is there a method to programmatically change the MODULE NAME in the Stand Alone Program Loader without going through the SAPL Panel? For example, if a mini-disk has two load modules, is there a method to pass a module name and bypass the SAPL Panel altogether? Thanks, Mike Atkison
Re: SALIPL - Stand Alone Program Loader
Edi, Thanks for the reply. Actually, I am attempting to ipl one of two applications that will run under VM, so shutting down is not an option. I was trying to get away with only having one SAPL on the minidisk and two applications. Thanks, Mike Atkison From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Edi Lopes Alves Sent: Sunday, November 01, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SALIPL - Stand Alone Program Loader Hi Mike, If you wanted some command to do the IPL changing the module name, have you tried = SHUTDOWN REIPL diskaddress 1 MODULE cploadname IPLPARMS CONS=address Regards Edi Lopes Alves Location: IBM Hortolândia - São Paulo - Brazil From: Mike Atkison mike.atki...@mantissa.com To: IBMVM@LISTSERV.UARK.EDU Date: 29/10/2009 13:48 Subject: SALIPL - Stand Alone Program Loader _ Is there a method to programmatically change the MODULE NAME in the Stand Alone Program Loader without going through the SAPL Panel? For example, if a mini-disk has two load modules, is there a method to pass a module name and bypass the SAPL Panel altogether? Thanks, Mike Atkison
Re: SALIPL - Stand Alone Program Loader
Thanks for all the responses on this question. Mike Atkison From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Thursday, October 29, 2009 3:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SALIPL - Stand Alone Program Loader When the menu is produced on the designated console (which is what the loadparm does), you can change the name of the module to load, the name of the CONFIG file, the location of the parm disk, and the OPERATOR console address. The changes are not permanent, reverting to their old values for the next IPL. One quirk - if you do specify cons=addr via the menu, it replaces both the OPERATOR and emergency console lists with that single address for the duration of that IPL. Regards, Richard Schuh _ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Thursday, October 29, 2009 11:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SALIPL - Stand Alone Program Loader No, there is not, the IPL LOADPARM only allows to change the console address: - rdev -- start SAPL on rdev
Re: SALIPL - Stand Alone Program Loader
Will the following procedure accomplish what you are looking for? 1) Log on to Maint 2) Link * 123 123 mw 3) Spool pun * 4) punch ipl salipl * (noh a. RDR FILE SENT FROM MAINTPUN WAS 0232 RECS 0944 CPY 001 A NOHOLD NOKEEP 5) order rdr a. Where is the spool number from the previous punch 6) Term conmode 3270 a.Receive message DMSCIT171T Permanent console error; re-IPL CMS 7) ipl 00c clear 8) Receive a blank panel similar to below. 9) Fill in the panel as follows: a. Device Number:Virtual address (123) from step 2 above. b. Module Name: Change to new default name. c. MiniDisk Offset: Enter the Starting Cylinder for MAINT's CF1 MDISK i. MDISK 0CF1 3390 039 120 520RES RR READ WRITE MULTIPLE ii. MDISK 0CF2 3390 159 120 520RES RR READ WRITE MULTIPLE iii. MDISK 0CF3 3390 279 120 520RES RR READ WRITE MULTIPLE iv. MDISK 0CF4 3390 501 120 520W03 RR READ WRITE MULTIPLE d. Load Origin: Modify appropriately 10) Hit PF10 to Write the IPL Reords 11) Hit PA1 12) IPL 190 (or IPL CMS) Thank you, Scott From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Atkison Sent: Friday, October 30, 2009 8:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SALIPL - Stand Alone Program Loader Thanks for all the responses on this question. Mike Atkison From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Thursday, October 29, 2009 3:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SALIPL - Stand Alone Program Loader When the menu is produced on the designated console (which is what the loadparm does), you can change the name of the module to load, the name of the CONFIG file, the location of the parm disk, and the OPERATOR console address. The changes are not permanent, reverting to their old values for the next IPL. One quirk - if you do specify cons=addr via the menu, it replaces both the OPERATOR and emergency console lists with that single address for the duration of that IPL. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Thursday, October 29, 2009 11:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SALIPL - Stand Alone Program Loader No, there is not, the IPL LOADPARM only allows to change the console address: - rdev -- start SAPL on rdev Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
SALIPL - Stand Alone Program Loader
Is there a method to programmatically change the MODULE NAME in the Stand Alone Program Loader without going through the SAPL Panel? For example, if a mini-disk has two load modules, is there a method to pass a module name and bypass the SAPL Panel altogether? Thanks, Mike Atkison
Re: SALIPL - Stand Alone Program Loader
try HELP SALIPL SALIPL has a ( MODULE filename option; default is (MODULE CPLOAD From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Atkison Sent: Thursday, October 29, 2009 1:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: SALIPL - Stand Alone Program Loader Is there a method to programmatically change the MODULE NAME in the Stand Alone Program Loader without going through the SAPL Panel? For example, if a mini-disk has two load modules, is there a method to pass a module name and bypass the SAPL Panel altogether? Thanks, Mike Atkison 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: SALIPL - Stand Alone Program Loader
No, there is not, the IPL LOADPARM only allows to change the console address: - rdev -- start SAPL on rdev - CONSrdev -- bypass SAPL's panel, load the CP nucleus (defined by SALIPL) and pass CONS=rdev to CP 2009/10/29 Mike Atkison mike.atki...@mantissa.com Is there a method to programmatically change the MODULE NAME in the Stand Alone Program Loader without going through the SAPL Panel? For example, if a mini-disk has two load modules, is there a method to pass a module name and bypass the SAPL Panel altogether? Thanks, Mike Atkison -- Kris Buelens, IBM Belgium, VM customer support
Re: SALIPL - Stand Alone Program Loader
ipl vdev loadp ccuu where ccuu is the vdev of your console. You can specify the module name on the display you get on the designated terminal. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Atkison Sent: Thursday, October 29, 2009 10:35 AM To: IBMVM@LISTSERV.UARK.EDU Subject: SALIPL - Stand Alone Program Loader Is there a method to programmatically change the MODULE NAME in the Stand Alone Program Loader without going through the SAPL Panel? For example, if a mini-disk has two load modules, is there a method to pass a module name and bypass the SAPL Panel altogether? Thanks, Mike Atkison
Re: SALIPL - Stand Alone Program Loader
When the menu is produced on the designated console (which is what the loadparm does), you can change the name of the module to load, the name of the CONFIG file, the location of the parm disk, and the OPERATOR console address. The changes are not permanent, reverting to their old values for the next IPL. One quirk - if you do specify cons=addr via the menu, it replaces both the OPERATOR and emergency console lists with that single address for the duration of that IPL. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Kris Buelens Sent: Thursday, October 29, 2009 11:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SALIPL - Stand Alone Program Loader No, there is not, the IPL LOADPARM only allows to change the console address: - rdev -- start SAPL on rdev
Re: SALIPL - Stand Alone Program Loader
On Thursday, 10/29/2009 at 04:08 EDT, Schuh, Richard rsc...@visa.com wrote: When the menu is produced on the designated console (which is what the loadparm does), you can change the name of the module to load, the name of the CONFIG file, the location of the parm disk, and the OPERATOR console address. The changes are not permanent, reverting to their old values for the next IPL. The request was for a method that does not require the SAPL screen. Kris was right, there is no such method. Only the filename of SYSTEM CONFIG can be specified on the LOADPARM without bringing up the SAPL screen. E.g. LOADPARM FNABC will cause FN=ABC to be added to the SAPL parms, overriding any burned-in specification. One quirk - if you do specify cons=addr via the menu, it replaces both the OPERATOR and emergency console lists with that single address for the duration of that IPL. That's correct for OPERATOR_CONSOLES, but if it's happening for the emergency console list, it's a bug. Here's what the book says: If the CONS=addr or CON=addr parameter was specified on the Stand-Alone Program Loader (SAPL) panel to specify a console address and this console address is not already specified on the EMERGENCY_MESSAGE_CONSOLES statement, it is added to the list of emergency message consoles. When you specify a console on the LOADPARM, SAPL creates a CONS=addr entry and the above rule applies. Alan Altmark z/VM Development IBM Endicott
Re: SALIPL - Stand Alone Program Loader
It happened the last time I used the menu in a virtual machine. However, that was early in my 5.3 ventures. The loader may even have been at the 5.2 level, loading a 5.3 system. I will try it when I start testing 6.1 and, if it is still doing it, I will open an incident. Regards, Richard Schuh That's correct for OPERATOR_CONSOLES, but if it's happening for the emergency console list, it's a bug. Here's what the book says: If the CONS=addr or CON=addr parameter was specified on the Stand-Alone Program Loader (SAPL) panel to specify a console address and this console address is not already specified on the EMERGENCY_MESSAGE_CONSOLES statement, it is added to the list of emergency message consoles. When you specify a console on the LOADPARM, SAPL creates a CONS=addr entry and the above rule applies. Alan Altmark z/VM Development IBM Endicott
Re: SALIPL - Stand Alone Program Loader
On Thursday, 10/29/2009 at 05:00 EDT, Schuh, Richard rsc...@visa.com wrote: It happened the last time I used the menu in a virtual machine. However, that was early in my 5.3 ventures. The loader may even have been at the 5.2 level, loading a 5.3 system. I will try it when I start testing 6.1 and, if it is still doing it, I will open an incident. The support was added to VM/ESA V1 R2.2 by APAR VM58068 to VM/ESA V2R2 wy back in 1994. Alan Altmark z/VM Development IBM Endicott
