|
Understood. That's why I said "normally". I've seen QCMD mentioned in
lieu of QCTL but haven't seen it in practice.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don
Sent: Friday, September 14, 2012 6:13 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Custom startup program
QCTL may never actually fire up, depending on how you're config'd...
I always use it and put it in when I found it missing, but some
systems were delivered without QCTL being the controlling sbs....
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Friday, September 14, 2012 9:06 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Custom startup program
Starting QCTL is normally what launches the startup program.
FWiW, at my previous employer, I externalized all the subsystem and
writer/remote writer startups to be table driven. Easy maintenance.
xxxStartup
===> Call xxxStrSBS
===> Call xxxStrWtr
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don
Sent: Friday, September 14, 2012 5:59 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Custom startup program
Are you using QCTL anywhere???
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Friday, September 14, 2012 5:46 PM
To: Midrange Systems Technical Discussion
Subject: Custom startup program
I was just asked to check our modified startup program (late Friday,
is there no justice?).
So, I'm definitely not the best fit for this, but here is my question:
Is there any recommended order for starting subsystems?
The startup pgm being replaced did the following as it's first four:
QSPL
QINTER
QBATCH
QCMN
Any hints, comments, or pokes welcomed...
--
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 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.