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

[CRPence <CRPbottle@xxxxxxxxx>]

  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 */

  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?