On holding jobs rather than job queues

Several months ago, I talked about Debugging RPG Programs in Batch and said that, before you submit your job, you should first hold the job queue.

While this isn’t bad advice, exactly, it’s not what I actually do.

When I am debugging a job in batch, I will submit it with HOLD(*YES). The job then sits on the job queue while I start the service job and debug, and then I can release the job.

Holding the job rather than the job queue reduces the impact I have on other users of the system since no other jobs are waiting for the job queue to be released. It also means that I don’t have to worry about someone else noticing the job queue is held and releasing it before I’m ready to start testing.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.