Question on Startup Job, QSPL and Writers...

Hi Folks,

Our startup job is a clone of the IBM version. It contains basically
what they had plus some stuff "unique" to us or missing in our
situation.

My question(s) is on QSPL and writers...

The start of subsystem QSPL is the FIRST executable statement in the CL
after the DCL's.

After that there are the various other things and then there is the
section that retrieves the QSTRPRTWTR system value and checks it to see
if it is "0" (don't start). Ours is set to "1". If it is equal to "1" it
NORMALLY executes
CALL PARM(QSYS/QWCSWTRS). I have this commented out and our own start
printer writers program is called (because it sets certain FORMTYPEs for
certain printers, etc.).

I end up with a BUNCH of printers with MSGW status and the "Device not
available" messages. The reason is that QSPL has not STARTED when this
executes (it is in the process). This all takes place over a VERY short
period of time. I know I can put a DLYJOB in the CL but I hate to do
stuff like that if it isn't necessary. Does the IBM program do something
to wait or something ? I can retrieve the source for it but am not clear
on this.

TIA,

Chuck

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---