× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2015

RE: Active subsystems

I used to drive the whole QSTRUP job from files. Subsystems, Writers, NEP's. Had all the parms including delays and sequence.


Made the startup program pretty small and I never had to answer to auditors about changes to it.



Roger Harman


COMMON Certified Application Developer – ILE RPG on IBM i on Power

OCEAN User Grouphttp://www.ocean400.org



----------------------------------------
From: PSteinmetz@xxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Active subsystems
Date: Fri, 23 Jan 2015 18:02:13 +0000


Several reasons I would not depend a file to start susbsystems in QSTRUP.
1) There could be instances where the file is not accurate.
2) The order in which subsystems start is sometimes important.
3) Some subsystem starts may need to be followed by a delay

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Friday, January 23, 2015 12:49 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Active subsystems

I caught that when I reviewed the programmer's first pass at the program(s).
:-)

We agreed to add a scheduler job to populate the active subsystem file every day at noon. The boot programs read that file.

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 Steinmetz, Paul
Sent: Friday, January 23, 2015 11:35 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Active subsystems

Paul,

How does your QSTRUP program know which subsystems to start.
None will be active following an IPL, so QSCLASBS would return an empty list.
Am I missing something here?

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Friday, January 23, 2015 12:12 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Active subsystems

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.

--
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.


--
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.

--
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.


--
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.

--
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.