Hi Rob
Thanks for the reply
That is what I was thinking - but this list is so amazing - I was hoping that someone had a process/routine/ work around that would give me what I am looking for
What you supplied is something I hadn't thought of - so let me give those a look see
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Monday, December 17, 2018 9:24 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: [EXTERNAL] Re: message queue for nnnnnnn/QTMHHTTP/INBNDSVR has been wrapped.
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.