Once it has wrapped,
and it's gone from
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.JOBLOG_INFO()%20UDTF
,
then it's gone.
Short term corrective actions include:
Looking to see if the message is duplicated in QSYSOPR. You can use
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.MESSAGE_QUEUE_INFO%20View
Looking to see if it is in the history log via
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.HISTORY_LOG_INFO%20UDTF
Looking to see if the joblog is set to *WRAP or *PRTWRAP and then look at
the spool file. But spool file joblogs are like using stone knives and
bear skins.
Long term corrective actions include:
- Increasing the size of the joblog by changing the job description
CHGJOBD JOBD(X) JOBMSGQMX(64)
- Change the job description to print the joblog before wrapping it:
CHGJOBD JOBD(X) JOBMSGQFL(*PRTWRAP)
- Log such messages to something more robust than the joblog
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.