AS/400 spool files in FIN status

120 pts.
Tags:
AS/400
AS/400 Spool Files
Is there a way to remove spool files in FIN status without ending the job that created them. I do a WRKUSRJOB USER(&USRCOD) STATUS(*ALL) OUTPUT(*PRINT) and then copy it to a file and then delete it using DLTSPLF FILE(QPDSPSBJ) SPLNBR(*LAST). It leaves the QPDSPSBJ in FIN status out there and it's causing us to reach the count max. Thanks for your help.
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 3  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.
  • GregManzo
    By 'count max' do you mean the maximum number of spooled files for a job (9999)? If so then end-of-job is about the only way. For this reason we had all 'background' tasks every few hours would submit a copy of themselves and then end quietly - prevents buildup of spooled files & locks. We also had them checking for controlled shutdown every 2 minutes (or less).
    2,960 pointsBadges:
    report
  • pdraebel
    Without knowing the purpose of Your listing the user jobs, you could try to use system API QUSLJOB to accomplish the same thing without having to go via *PRINT of the user jobs. Maybe another API will fit your goal better, but that is up to you to investigate. For Examples using the API : there are plenty on the Web.
    7,545 pointsBadges:
    report
  • ToddN2000
    Is this a new problem? If you are maxing the number of spool files then you would need to end the job or change the reporting to be a submitted job from the parent program. What type of application is this that generates that many spool files?
    132,590 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.

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

Following

Share this item with your network: