IBM Support

IV70565: RMSTDLIST ABENDS DUE TO HANDLES ON OLD LOGS. JOBMON RUNNING FROM DATE OF OLD LOGS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Our Cleanup job (running the standard rmstdlist command) is
    abending because there are handles in currently running jobs and
    in JOBMON to logs that are due to be deleted. JOBMON is running
    still from the date that the log is from. Jobs have been
    running every day during SWITCHPLAN which apparently keeps
    JOBMON from recycling.
    
    Logs are not being removed per their retention schedule, abends
    are requiring time to investigate that could be spent doing
    other things.
    
    My concern here is 3 fold:
    
    
    1)  abending due to "normal" behavior causes us to have to spend
    time troubleshooting that could be avoided
    
    2)  abending and not deleting the rest of the files that are due
    to be deleted means that this normal behavior is causing
    abnormal retention of logs that are due to be deleted
    
    3)  deleting the logs held by JOBMON depending on when they were
    created rather than when they were last updated can cause the
    data at the end of the log to be deleted before the standard 15
    days retention (as soon and rmstdlist is run after JOBMON
    recycles)
    

Local fix

  • Hi L2, let me explain that if a Job stays in EXEC for multiple
    times JOBMON process will be up and running during the days
    using the stdlist for example of the days before when the jobs
    started to be executed.
    
    So the stdlist files that cannot be removed will be there still
    since JOBMON stays up and running across the days and these
    files will be naturally removed when the JOBS will complete
    successfully for these days.
    
    The "rmstdlist" cannot delete the stdlist used by JobMon when
    it is up and running but what we can evaluate "improvement" that
    rmstdlist can avoid to generate the ABEND on the customer
    job that run the rmstdlist.
    

Problem summary

  •  see apar description.
    

Problem conclusion

  •  This apar will be fixed into
    8.5.1 fp6,92 fp2, 91 fp3,86 fp4.
    This apar will fix these 2 scenarios:
    1)  abending due to "normal" behavior causes us to have to spend
    time
    troubleshooting that could be avoided
    
      >> Job that run rmstdlist will not abend when not able to
    remove a stdlist file. Rmstdlist needs to be modified.
    
    2)  abending and not deleting the rest of the files that are due
    to be
    deleted means that this normal behavior is causing abnormal
    retention of
    logs that are due to be deleted
    >>rmstdlist command will needs to continue the work and try to
    delete any files even if one of them
    cannot be deleted since it could be locked. The rmstdlist should
    continyue the processing of files deletion.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV70565

  • Reported component name

    TIV WKLD SCHDL

  • Reported component ID

    5698WKB85

  • Reported release

    8T5

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-06

  • Closed date

    2015-05-21

  • Last modified date

    2015-05-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TIV WKLD SCHDL

  • Fixed component ID

    5698WKB85

Applicable component levels

  • R8A5 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGSPN","label":"IBM Workload Scheduler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8T5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
21 May 2015