![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide
Because there are many different types of jobs, you must order the jobs that you are defining according to the type of process required. JP1/AJS3 provides the following job types:
- Standard job
- OR job
- Judgment job
- Event job
- Action job
- Custom job
The characteristics of each type of job are described below.
(a) Standard job
This type of job executes processing by specifying an executable file. The following table lists the types of executable files that can be specified in each type of standard job.
Table 2-2 Executable files specifiable in a standard job
No. Job type Description Specifiable executable files 1 Unix job Process executed on a UNIX host.
- Executable file
- Shell script
2 PC job Process executed on a Windows host.
- .exe file
- .com file
- .cmd file
- .pif file
- .bat file
- .spt file# (script file created with JP1/Script)
- Data file that has a file type (extension) associated with the application
3 QUEUE job Process executed by submitting a job to a specified queue.
This job type is used for linking with other systems (such as JP1/NQSEXEC).
- Executable file
- Shell script
- .exe file
- .com file
- .cmd file
- .pif file
- .bat file
- .spt file# (script file created with JP1/Script)
- Data file that has a file type (extension) associated with the application
- #
- To execute an .spt file, JP1/Script must also be installed on the host running the job.
(b) OR job
For an OR job, you define a number of jobs (event jobs) which will monitor the system for a specific event. You define these event jobs as the preceding jobs of the OR job. If any one of the monitored events occurs, the OR job executes its succeeding job.
For details, see 3.1.1(1)(b) OR job in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.
(c) Judgment job
A judgment job checks whether a given condition is satisfied.
The judgment can be based on the following conditions:
- The return code of the preceding job
- Whether a specific file exists
- The result of a comparison between variables
For details, see 3.1.1(1)(c) Judgment job in the manual Job Management Partner 1/Automatic Job Management System 3 Overview.
(d) Event job
An event job monitors an event occurring in the system. You can define an event job as the start condition for a job flow or jobnet, so that the particular job or jobnet will be executed only when the monitored event occurs.
The following table describes each event job.
Table 2-3 Types of event jobs
No. Event job name Description 1 Receive JP1 event job This job terminates when it receives a specific event from JP1/Base. 2 Monitoring files job This job terminates when a specific file is created, deleted, or updated. 3 Receive mail job This job terminates when it receives a specific email. 4 Monitoring log files job This job is linked with the log file trapping of JP1/Base, and terminates when specific information is written to the specified log file. 5 Monitoring event log job This job is linked with the log file trapping of JP1/Base, and terminates when specific information is written to the Windows event log file. 6 Interval control job This job terminates when the specified time period elapses. 7 Receive MQ message job This job terminates when it receives a specific message from TP1/Message Queue or MQSeries. 8 Receive MSMQ message job This job terminates when it receives a specific message from MSMQ.
- Note
- JP1/AJS3 must be linked with the appropriate program to use a Receive mail job, Receive MQ message job, or Receive MSMQ message job. For details, see the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
Operation of event jobs is independent of JP1 user permissions and the authority level defined for the job (by owner, JP1 resource group, or by the user executing the job). In Windows, because event job operation is governed by the account rights to the JP1/AJS3 service, JP1/AJS3 service rights must be set in advance.
(e) Action job
An action job executes a specific process. You can combine an action job with an event job to execute a process (action) when an event occurs. Typical actions might be to send a JP1 event, an email message, or a status notification.
The following table describes each action job.
Table 2-4 Types of action jobs
No. Action job name Description 1 Send JP1 event job Sends a JP1 event to the event service of JP1/Base. 2 Send mail job Sends an email message. 3 OpenView Status Report job Sends a status to HP NNM. 4 Send MQ message job Sends a message to TP1/Message Queue or MQSeries. 5 Send MSMQ message job Sends a message to MSMQ.
- Note
- JP1/AJS3 must be linked with the appropriate program to use a Send mail job, Send MQ message job, Send MSMQ message job, or OpenView Status Report job. For details on program linkage, see the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
(f) Custom job
A custom job is used to link an external program with JP1/AJS3 to execute processing.
For details, see 3. Adding Custom Jobs in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.