AS/400 Job Administration is Straightforward


I know that occasionally it can be a tiny confusing to realize how the operating technique handles jobs on the AS/400, iSeries or IBM i program is setup to function. But actually it is in fact straight forward when you comprehend that there are two kinds of jobs that can run. All jobs fall into one particular of two categories of either interactive or batch.

Interactive jobs are the conventional “green-screen” or terminal type jobs exactly where the user is actively using an emulator or an old fashioned terminal to interface with the program to input info such as entering in buyer details to a file. The other variety of job are batch jobs which can variety from mass update applications to long running reports.

Simply because the interactive job program is so straight forward a majority of the method administrator’s time will be spent managing the batch jobs. When you work with and administer an AS/400 try to believe of the batch processing job system in two to three components that function together to accomplish the function.

Very first up you have the job queue. This is where all the information revolving around a batch job begins out prior to coming to life. Consider of the job queue sort of like a reservation system, with all issues becoming equal the initial job into the queue is the initial job out of the queue. Now it is attainable to have a job with a distinct job priority which is sort of treating it like a VIP, that job or jobs can go to the front of the line of the queue ahead of all the other jobs with a decrease priority.

After a job has waited for it’s turn in the job queue then it gets placed into a subsystem. The subsystem is where the job is allocated technique sources such as memory and a slice of the CPU time for processing. So for example if the job is a query or an RPG plan to create a report it now begins running to develop the report. Even though a job is running in a subsystem you can see it making use of the WRKACTJOB command.

If you have never utilized WRKACTJOB before you ought to become really familiar with it considering that it is an exceptional tool for administering running jobs on your technique.

Now depending on what sort of job there could or could not be an output. And this is where I referred earlier to it becoming a two or three components. In the case of a job that generates a report, while it is becoming generated the output file, known as a spool file, is placed in an output queue determined by how the job was defined or exactly where a customers jobs are configured to print. You can also see the spool file or files a job is making by taking choice give and then choice four from the WRKACTJOB screen. Once a job is completed running, which is determined by the code or programming of the job it then ceases to exist.

Occasionally when you have a job that doesn’t develop any output like a report it can be hard to tell if it in fact ran or not. One method to see if a job ran or not is to appear through the system history log by employing the command DSPLOG. Virtuall every single tiny thing (and all job begins and ends) is logged in the technique log so be forewarned that you may possibly have to wade by way of numerous pages to discover your distinct jobs commence and finish timestamp. One more approach is to use the work with submitted jobs command WRKSBMJOB.