RE: Autostart for dummies (was Re: User-Defined Subsystems)

Here is an example of one of my subsystem startups:
PGM
SBMJOB CMD(CALL PGM(SERVER/AUTODS)) JOB(AUTODS) +
JOBQ(SERVER/SERVER) USER(AUTODS) +
DSPSBMJOB(*NO) JOBD(SERVER/AUTODS)
MONMSG MSGID(CPF0000)

ENDPGM

It has several submit job commands but I did not need to list/change
them all.

The subsystem is:
Display Autostart Job Entries
System
Subsystem description: SERVER Status: ACTIVE

Job Job Description Library
SERVER SERVER SERVER

And the job description is:
Display Job Description
System:
Job description: SERVER Library: CUSTOM

User profile . . . . . . . . . . . . . . . . . . : QPGMR
CL syntax check . . . . . . . . . . . . . . . . : *NOCHK
Hold on job queue . . . . . . . . . . . . . . . : *NO
End severity . . . . . . . . . . . . . . . . . . : 30
Job date . . . . . . . . . . . . . . . . . . . . : *SYSVAL
Job switches . . . . . . . . . . . . . . . . . . : 00000000
Inquiry message reply . . . . . . . . . . . . . : *RQD
Job priority (on job queue) . . . . . . . . . . : 5
Job queue . . . . . . . . . . . . . . . . . . . : QBATCH
Library . . . . . . . . . . . . . . . . . . . : QGPL
Output priority (on output queue) . . . . . . . : 5
Printer device . . . . . . . . . . . . . . . . . : *USRPRF
Output queue . . . . . . . . . . . . . . . . . . : *USRPRF
Library . . . . . . . . . . . . . . . . . . . :
Message logging:

Level . . . . . . . . . . . . . . . . . . . . : 4

Severity . . . . . . . . . . . . . . . . . . . : 0

Text . . . . . . . . . . . . . . . . . . . . . : *NOLIST

Log CL program commands . . . . . . . . . . . . : *NO

Accounting code . . . . . . . . . . . . . . . . : *USRPRF

Print text . . . . . . . . . . . . . . . . . . . : *SYSVAL



Routing data . . . . . . . . . . . . . . . . . . : QCMDI



Request data . . . . . . . . . . . . . . . . . . : call
SERVER/CSERVER

It is not really that hard. Now you have to make sure that one the
subsystem starts it has access to all the object involved. Most of the
time the subsystem cannot access the startup job description or program
do to security restrictions. Subsystems run under QSYS so that profile
will need at least read / execute access to the objects. The subsystem
description will run the startup job under a different profile if
specified. If it does not start, check the logs for the startup job d.


Chris Bipes
Director of Information Services
CrossCheck, Inc.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H.
Lampert
Sent: Tuesday, March 24, 2009 3:15 PM
To: Midrange Systems Technical Discussion
Subject: Autostart for dummies (was Re: User-Defined Subsystems)

Chris Bipes wrote:

In my humble opinion you should create a command to start and stop

NEPS.

(Server jobs or services as windows calls them.)

Then you can use an Auto Start Job Entry in the subsystem to start the
job.

How? I tried to do that in the model I described in my last post; the
subsystem started, but the server didn't.

See my previous post for details.

Why would it not be working?

--
JHHL