Somehow all of our job queues got released. We know that many of them had been on hold, however the one person...
who probably knew which ones were on hold and why, is no longer with our company. Is there a way to retrieve this information off of a system save or something?
You could try searching through job logs looking for the RLSJOBQ commands, but that could be a daunting task, especially is your job logging levels aren't set high enough to create a job log! The execution of the RLSJOBQ command isn't logged to the system history log either. Chances are good that you will not be able to find out how these job queues got released this time.
However, you could enable audit journaling on your system and then you would be able to track down this kind of problem quite easily in the future.
Once you have configured system auditing you would then enable command auditing for a user profile.
I audit command execution for all external contractors and any user profile that is able to work outside the boundaries of our production applications.
If you had auditing turned on you could have done a query of the journal for command executed during a certain time frame and then a simple scan of the spool file for RLSJOBQ would have shown who did it and when.
To get complete instruction on how to set up auditing on your system visit the IBM iSeries Information Center page.
Follow the navigation tree to:
>Getting started with iSeries > Managing system operations > Setting security and authorities
From here you will see a link to: Setting up auditing.
I'd highly recommend that you set up system auditing. It is the best way to track what is going on your system. Command auditing is just one thing you can log too. You'll probably be amazed at what the system audit journal is capable of keeping an eye on. It is the iSeries version of "Big Brother".
Dig Deeper on Systems Management Tools
Related Q&A from Ken Graap
The BRMS Network feature allows a BRMS system to connect to other BRMS systems via a network, and enables a user to consolidate media such as backup ... Continue Reading
The only option to correct damage preventing file journaling is to use the RCLSTG command. Continue Reading
IBM's iSeries Backup and Recovery manual answers many questions related to system backup and disaster recovery. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.