RE: Custom startup program -- MIDRANGE-L

Jim's point of not changing IBM supplied objects is well taken.

I suggest you rtvclsrc your startup program (check the value in the system
value QSTRUPPGM (? - I'm writing this from memory without access to a box on
a long weekend vacation in the TN mtns). I recommend that you also make a
copy of this source - call it QSTRUPORI or something and document it as PID.

Then make your CL mods and compile it to QGPL or some such...then change
your sysval to point to your new QSTRUP in whatever lib you put it.

DR2

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of franz400
Sent: Friday, September 14, 2012 10:06 PM
To: Midrange Systems Technical Discussion
Subject: Re: Custom startup program

Jerry,
IBM does not ship the source, but does make the QSYS/QSTRUP clp so that a
rtvclsrc command can retreive the source.
I would recommend to any shop that you should not alter IBM's QSYS object,
but if you do want to customize, create under a new name, and change the
system
value to point to the new pgm. Do not store in a lib that is not available
in a system
restore from backup. Do secure the object, and by default (if not modified)
it runs
under QPGMR profile - see jobd QSTRUPJD.
btw Jerry... i've never seen QSPL started first..
Jim Franz

----- Original Message -----
From: "Jerry C. Adams" <midrange@xxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, September 14, 2012 9:53 PM
Subject: RE: Custom startup program

Typically, one has to do that to even begin modifications, Don, as the
source isn't (to my knowledge) provided. That said, my guess is that
whoever retrieved and modified the original did so outside of a CMS or
didn't archive the original.

That said, and for what it's worth this late on Friday, this is the order
that subsystems were started originally on our system (B5R1, though) from
the original, archived source:

QSYS/STRSBS SBSD(QSPL)
MONMSG MSGID(CPF0000)
QSYS/STRSBS SBSD(QSERVER)
MONMSG MSGID(CPF0000)
QSYS/STRSBS SBSD(QUSRWRK)
MONMSG MSGID(CPF0000)
QSYS/RLSJOBQ JOBQ(QGPL/QS36MRT)
MONMSG MSGID(CPF0000)
QSYS/RLSJOBQ JOBQ(QGPL/QS36EVOKE)
MONMSG MSGID(CPF0000)
QSYS/STRCLNUP
MONMSG MSGID(CPF0000)
QSYS/RTVSYSVAL SYSVAL(QCTLSBSD) RTNVAR(&CTLSBSD)
IF COND((&CTLSBSD *NE 'QCTL QSYS ') *AND (&CTLSBSD *NE-
'QCTL QGPL ')) THEN(GOTO CMDLBL(DONE))
QSYS/STRSBS SBSD(QINTER)
MONMSG MSGID(CPF0000)
QSYS/STRSBS SBSD(QBATCH)
MONMSG MSGID(CPF0000)
QSYS/STRSBS SBSD(QCMN)
MONMSG MSGID(CPF0000)

The only thing after that was to start the writers (depending upon the
system value). Also, this was source I retrieved on my first day on the
job
last year (3 January). I can't verify that no one had changed it before I
got there (wanna bet that didn't happen?!), but they didn't leave any
tracks.

Jerry C. Adams
IBM i Programmer/Analyst
The largest vehicle always has the right of way.
--
A&K Wholesale
Home Office: 615-832-2730
email: midrange@xxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Don
Sent: Friday, September 14, 2012 8:02 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Custom startup program

Have you thought of doing a rtvclsrc of the original startup CL???

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