2.6.2 JP1/AJS3 database configuration

The following figure shows the JP1/AJS3 database configuration.

Figure 2‒56: JP1/AJS3 database configuration

The following table lists the types of JP1/AJS3 databases and the information stored in each type.

Table 2‒47: JP1/AJS3 database types and stored information

Database type	Information stored in the database
Scheduler database	Definition information for: - Jobs and jobnets - Calendars and schedules Execution results and execution statuses (jobs and jobnets)
Agent management database	Definition information for: - Execution agents - Execution agent groups
Database for QUEUE jobs and submit jobs#	Execution results and execution statuses for: - Jobs submitted by the jpqjobsub command - QUEUE jobs requested for execution by a scheduler service Configuration definition information for agents, queues, and resources that can be locked for exclusive use

#

Use an ISAM database. ISAM is supplied as standard with JP1/Base.

JP1/AJS3 incorporates a range of functions that request job execution (execution of PC jobs, Unix jobs, and QUEUE jobs). These functions include scheduler services, and commands such as the jpqjobsub command for controlling submit job execution.

For jobs executed from a scheduler service, the jobnet definition information, execution statuses, and execution results are managed in a scheduler database. To execute a job in a jobnet (PC job, Unix job, or QUEUE job), the scheduler service sends a job execution request to the job execution control. The job's execution status and result are managed in the scheduler database (for QUEUE jobs, the job status and execution result are also managed in the database for QUEUE jobs and submit jobs). The scheduler database is updated when the job's status changes.

When the jpqjobsub command is used to request job execution, the request is sent directly to the submit job control without going through a scheduler service. The job's execution status and result, together with configuration definition information about the agent, queue, and execution-locked resources, are managed in the database for QUEUE jobs and submit jobs. For details about this database, see 7.1.3 Database for QUEUE jobs and submit jobs.

To Page Top