Hi, On 22.07.22 12:42, Paul Gevers wrote:
Yesterday, there was maintenance at Marist [1], but unfortunately our worker didn't come up after it. This apparently is just a matter of configuration. I recall we discussed this in the past and thought you configured it already to autostart. Can you (help me to) check if the settings are correct?
Finally found some time to swap my knowledge back in and check. dirm xautolog add ldebw01 DVHXMT1191I Your XAUTOLOG request has been sent for processing to DVHXMT1191I DIRMAINT at IBMISV. Ready; T=0.01/0.01 04:28:18 DVHREQ2288I Your XAUTOLOG request for LDEBW01 at * has been accepted. DVHBIU3450I The source for directory entry LDEBW01 has been updated. DVHBIU3423I The next ONLINE will take place via Diagnose 84. DVHBIU3428I Changes made to directory entry LDEBW01 have been placed DVHBIU3428I online. DVHREQ2289I Your XAUTOLOG request for LDEBW01 at * has completed; with DVHREQ2289I RC = 0.I confirmed that it wasn't enabled before (a second add fails). This logs on the VM when z/VM starts up.
dirmaint ipl ? DVHXMT1191I Your IPL request has been sent for processing to DIRMAINT at DVHXMT1191I IBMISV. Ready; T=0.01/0.01 04:31:00 DVHREQ2288I Your IPL request for LDEBW01 at * has been accepted. DVHIPL3274I The current IPL setting for LDEBW01 is CMS with PARMS of DVHIPL3274I AUTOCR DVHREQ2289I Your IPL request for LDEBW01 at * has completed; with RC = DVHREQ2289I 0. This means it's currently set to load CMS instead of Linux. dirmaint ipl 150 DVHXMT1191I Your IPL request has been sent for processing to DIRMAINT at DVHXMT1191I IBMISV. Ready; T=0.01/0.01 04:31:30 DVHREQ2288I Your IPL request for LDEBW01 at * has been accepted. DVHBIU3450I The source for directory entry LDEBW01 has been updated. DVHBIU3423I The next ONLINE will take place via Diagnose 84. DVHBIU3428I Changes made to directory entry LDEBW01 have been placed DVHBIU3428I online. DVHREQ2289I Your IPL request for LDEBW01 at * has completed; with RC = DVHREQ2289I 0. This sets the VM to boot from disk 150 on startup. LOGON LDEBW01 ENTER PASSWORD (IT WILL NOT APPEAR WHEN TYPED): 00: NIC 0340 is created; devices 0340-0342 defined 00: z/VM Version 7 Release 1.0, Service Level 2101 (64-bit), 00: built on IBM Virtualization Technology 00: There is no logmsg data 00: FILES: 0001 RDR, NO PRT, NO PUN 00: LOGON AT 04:32:31 EDT MONDAY 10/24/22 00: zIPL v2.15.1-build-20210211 interactive boot menu 00: 00: 0. default (debian) 00: 00: 1. debian 00: 2. old 00: Note: VM users please use '#cp vi vmsg <input>' 00: Please choose (default will boot in 10 seconds):So that looks good, it directly booted into Linux. But then it misses CP initialization commands like "don't wait for every page of Linux's output", so it's probably still better to boot through CMS with the drawback that to get into CMS one has to do "ACCESS (NOPROF" after "IPL CMS" to skip loading PROFILE EXEC.
dirmaint ipl cms parm autocr DVHXMT1191I Your IPL request has been sent for processing to DIRMAINT at DVHXMT1191I IBMISV. Ready; T=0.01/0.01 04:37:04 DVHREQ2288I Your IPL request for LDEBW01 at * has been accepted. DVHBIU3450I The source for directory entry LDEBW01 has been updated. DVHBIU3423I The next ONLINE will take place via Diagnose 84. DVHBIU3428I Changes made to directory entry LDEBW01 have been placed DVHBIU3428I online. DVHREQ2289I Your IPL request for LDEBW01 at * has completed; with RC = DVHREQ2289I 0. The new PROFILE EXEC: CP LINK TCPMAINT 592 592 RR ACCESS 592 T CP TERM MORE 0 0 CP SET RUN ON CP IPL 150 That seems to have done my bidding. #CP DISCONNECT Philipp Kern
Attachment:
OpenPGP_0x50C3634D3A291CF9.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature