RE: Not Using QSTRUPPGM (was RE: QTEMP not in library list)

Hi Charles

I ran a system that used this technique and even used it myself for a while
on various systems I ran.

It's just a matter of using a shutdown process that submits a start-up
process to JOBQ QCTL after issuing the PWRDWNSYS command. When the system is
re-started the job in the QCTL jobq starts up. It can be handy for
controlling the kind of restart you want but it is not exactly obvious to
the uninitiated.

Being able to use a SBMJOB was a bit more flexible and predictable than
trying to communicate across an IPL via a data area or similar mechanism
IMHO.

I eventually dropped this approach, not because it didn't work, but because
it wasn't obvious enough without explanation.

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Tuesday, 15 January 2008 10:28 a.m.
To: Midrange Systems Technical Discussion
Subject: Not Using QSTRUPPGM (was RE: QTEMP not in library list)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Tom Liotta
Sent: Monday, January 14, 2008 4:19 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: QTEMP not in library list

<snip>

I once ran across a customer who didn't use the QSTRUPPGM system
value. THAT threw a nasty little twist into an installation routine!
(But I learned a LOT along the way about what that system value
really did.)

Tom, I'm curious about this...care to expand?

I assume this means the had QSTRUPPGM as *NONE.

So how did they handle startup?

Charles