It is conceivable to manage more than one system/lpar at a time, yes. While I cannot provide detailed specifics (company secrets and all), "proxy" Application resources (APLs) representing LPARs can be defined on the "SysOps" side of SA. So when an Operator wants to shutdown and re-IPL a system, the proxy application is stopped, with RESTART=YES provided on the request. Omit the RESTART option to leave the LPAR "Not operating".
Extending the "Image/LPAR" proxy concept to the CEC level doesn't seem out of the question, with HASPARENT relationships built between CEC and LPAR proxy applications. So stopping (proxy) "CEC1" would entail *SA* first stopping all (proxy) children systems, including a ISQCCMD DEACTIVATE command once the system is varied out of the 'plex, It also seems possible to build SERVER Application Groups to logically group proxy systems, and just manage the APG when the time comes. When it comes to Batch/JCL, you can use Command Receiver (CMDRCVR) functionality to issue commands in batch as if you were entering them at an NCCF terminal: https://www.ibm.com/docs/en/z-system-automation/4.2.0?topic=programming-command-receiver On Wed, Apr 6, 2022 at 8:38 PM Jason Cai <[email protected]> wrote: > Hello Steve > > Thanks for your help! > > We have other three questions : > > Q1. Could we load all z/OS LPARs at the same time? > > Q2.If the anwser to Q1 is no, how to load the lpar one by one in one > script/jcl? > > Thanks a lot! > > Jason Cai > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
