How many jobs are using particular jobd in AS/400

2460 pts.
Tags:
AS 400
AS/400 jobs
Hi,
How to make a list how many jobs are using particular Jobd In AS/400?
Thanks!
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: 4  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.
  • azohawk
    There may be an API that I am not aware of, but if this is a one shot deal, I would use the display user profile command and dump the information to a file, then use a query tool to extract the data from the file.
    4,055 pointsBadges:
    report
  • Splat
    I'd suggest you also scan your source for any job submissions with the JOBD specified.

    Don't forget to review scheduled jobs also.
    12,865 pointsBadges:
    report
  • ToddN2000
    As far as I know there is no easy way. There may be some 3rd party tool that can do it. Other than that it's like the others said, dump the user profiles to see which in using the JOBD in question. Then check the log to see what jobs that user is running. You would also nee to scan any CL to see if the jobs are being submitted with an overridden JOBD. Dump the jobs found in the WRKJOBSCDE as well. It will take a little work to and you could still miss a few.. Is there a reason for the request? There may be alternative to prevent you having to do this again in the future.
    131,645 pointsBadges:
    report
  • TheRealRaven
    The question isn't clear. To find which jobs are running under a specific *JOBD, use the List Job (QUSLJOB) or the Open List of Jobs (QGYOLJOB) API to list the set of jobs you're interested in. Then loop through the list and select those that note the desired *JOBD.

    Of course, that only covers jobs that exist at the time the list is generated. It won't tell you anything about a job that only runs at end-of-week, end-of-month, end-of-year or any other widely separated future times. Any job that ran without leaving items on the system such as spooled files will also be missing from the list.

    Scanning source will likely catch most instances, but can't guarantee complete coverage. Names of objects such as *JOBDs might be stored externally in configuration files, *DTAARAs or other objects. That can allow changes without needing to recompile. And source scans won't see it.
    34,485 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: