Re: a/s 400 subsystem doesn't start automatically

CRPence wrote:

My prior reply made reference to QWDAJPGM, but more appropriately should have stated QSTRUPJD. Given that, and the quoted text from Gary, a quick way to review for that information [presuming no customization from system defaults] is via:
WRKSPLF (QPGMR *N *N QSTRUPJD) /* 5=Display on the recent QPJOBLOG */

And just for those very few unusual cases in Chuck's "customization" thought...

First, verify that the subsystem that is named in the QCTLSBSD system value has an auto-start job entry. And verify that that AJE names the startup job QSTRUPJD and references a job description named QSTRUPJD in library QSYS. And verify that the QSYS/QSTRUPJD job description refers to user profile QPGMR and has request data to call program QWDAJPGM in QSYS. And verify that the QSTRUPPGM system value names a program and library that both exist.

If any of those have been changed from the IBM-supplied defaults, then follow along the path of the changed values.

It's possible that the QSTRUPPGM system value isn't even used on your system, for example, if the job description doesn't request program QSYS/QWDAJPGM.

Tom Liotta

If the job is actually in MSGW status [or some other status that is preventing it from reaching the STRSBS requests], then the WRKACTJOB I suggested would show that. For the MSGW case a 7=Display_Message or 5=WrkJob & 10=DspJobLog of the active job would troubleshoot; i.e. if it were not ended with a spooled joblog, as researched in the WRKSPLF request noted above.

Regards, Chuck

Gary Monnier wrote:

Does the startup program's joblog give any indication as to why the
subsystem did not start?

rod aguila wrote:

is there anybody know, why the as 400 v4r5 subsystem does not start
automatically after normal ipl?