×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
