I'm pleased to report that QWCLASBS is the way to go. We wrote a routine
that runs in the job scheduler at noon every day.
The boot programs read that file twice, starting the IBM subsystems first,
followed by the other subsystems.
Using that file sure simplifies the boot programs.
Thanks, all.
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary
Thompson
Sent: Tuesday, January 20, 2015 7:50 AM
To: Midrange Systems Technical Discussion
Subject: RE: Active subsystems
Maybe some info from QWCLASBS - List Active Subsystems ?
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul
Nelson
Sent: Tuesday, January 20, 2015 6:45 AM
To: 'Midrange Systems Technical Discussion'
Subject: Active subsystems
List,
I'm working on a project for a client to build a utility to bring their IPL
programs (32 of them) under change control. Each program will be named the
same as the box and deployed from Aldon to make the auditors happy. I don't
want to have to sift through 32 different programs to determine the
subsystems that need to be started during a reboot.
I know that TAATOOL has some commands allowing one to retrieve the status of
a subsystem and the library from which it's started, but not all systems
have that product.
Has anybody figured out a way using the standard OS to be able to write the
active subsystem information to a file and have the IPL program read that?
Thanks
Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
