Implementing IBM I job management with IBM Java Toolbox for I (i)

In layman's terms, IBM I job management is responsible for handling system requests submitted by users or programs, which is one of the basic functions of the IBM I platform. Unlike Windows and UNIX, there are more concepts around IBM I job management, such as jobs, job descriptors, job queues, subsystems, subsystem descriptors, memory pools, output queues, and so on. The goal of this article is: Around IBM i job management concepts, to guide readers how to use IBM Java Toolbox for I implementation of IBM I job management programming support. For a basic knowledge of IBM Java Toolbox for I, see another technical document "Toolbox for Java and Jtopen."

From the content, this article mainly divides into 5 most. The 1th part, we focus on the job, focused on IBM Java Toolbox for I to IBM I job-related programming support. The 2nd part, mainly introduces IBM Java Toolbox for I to IBM I subsystem related programming support. Part 3rd, describes IBM Java Toolbox for I programming support for IBM I Memory pools, Part 4, which provides an overview of IBM Java Toolbox for I programming support for IBM I output queues. The last part is the summary.

IBM Java Toolbox for I programming support for IBM I jobs

Job is the basic unit of IBM I management of work, and the basic unit of system allocation resources. In this sense, IBM I's jobs are equivalent to processes in other operating systems.

How the IBM I job works

From the perspective of job interaction, IBM I job can be divided into two kinds of user interaction and batch processing. Below, we separate the principles of how they work.

Interactive jobs are simple to work with, and typically run as follows:

Life cycle begins with user login;

For interactive jobs, IBM I immediately responds and runs;

In the case of data printing, output the data to an offline print file (called spooled file) in the output queue, waiting for the print job in the queue to finish, and start printing the file;

Life cycle ends with user logoff.

The batch job works a little more complex than the following, as shown in Figure 1.

Figure 1. How the batch job works