Default output queue for Dumps

995 pts.
Tags:
i520
iseries v5r4
QEZDEBUG
Hi anyone, We just changed over to a new i520, V5R4. Systems dumps used to go to a queue called QEZDEBUG. But in the new system it defaulto the user queue..and obviously prints! Is there a setting somewhre to direct these things to one of the Q...queues?

Answer Wiki

Thanks. We'll let you know when a new response is added.

ANSWER
Tjgm88 | Feb 2 2009 9:41PM GMT

We finally found the problem which caused this in the first place, after contacting IBM.
It appears that on the old system, the system printer files were directed to the various out queues. When we went to the new machine, no one knew that this had to be done. So the following printer files require changes:
CHGPRTF FILE(QSYS/QPJOBLOG) OUTQ(QUSRSYS/QEZJOBLOG)
CHGPRTF FILE(QSYS/QPSRVDMP) OUTQ(QUSRSYS/QEZDEBUG)
CHGPRTF FILE(QSYS/QPDSPJOB) OUTQ(QUSRSYS/QEZDEBUG)
CHGPRTF FILE(QSYS/QPCSMPRT) OUTQ(QUSRSYS/QEZDEBUG)

This should help if anyone else encounters the same problem in the future.
Cheers.
GM

________________________________________________________________________________
Perhaps the problem is that you’re dumping more than you did in the past. What gets dumped :
The service dump QSRVDMP system value allows you to control whether the “Dump in Progress” message on line 24 of the screen is seen or not.

• *NONE—No dumps in any jobs
• *DMPSYSJOB—Service dumps for only system jobs
• *DMPUSRJOB—Service dumps for only user jobs
• *DMPALLJOB—Service dumps for all jobs The QSTSMSG system value determines whether status messages, which also appear on line 24 of the display, are displayed.

• *NORMAL—Display
• *NONE—Do not display

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • tjgm88
    We finally found the problem which caused this in the first place, after contacting IBM. It appears that on the old system, the system printer files were directed to the various out queues. When we went to the new machine, no one knew that this had to be done. So the following printer files require changes: CHGPRTF FILE(QSYS/QPJOBLOG) OUTQ(QUSRSYS/QEZJOBLOG) CHGPRTF FILE(QSYS/QPSRVDMP) OUTQ(QUSRSYS/QEZDEBUG) CHGPRTF FILE(QSYS/QPDSPJOB) OUTQ(QUSRSYS/QEZDEBUG) CHGPRTF FILE(QSYS/QPCSMPRT) OUTQ(QUSRSYS/QEZDEBUG) This should help if anyone else encounters the same problem in the future. Cheers. GM
    995 pointsBadges:
    report
  • TomLiotta
    Run GO CLEANUP and take option 1=Change cleanup options. View the help text for the 'Job logs and other system output' item and scroll to the bottom. At the bottom, tab to the "Job log cleanup details" and press {Enter}. The detail help explains that activating cleanup for those spooled files causes them to be redirected to the QEZ* *OUTQs. When you upgraded, the new printer files restored the original settings. If you went back through CLEANUP and set the options again, all of the printer files would be changed to QEZ* again automatically. The *OUTQs exist for CLEANUP. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following