By treating the work units which operate on the PowerAIM business system as jobs, it is possible to integrate the job nets consisting of work units and monitor or operate them in the Jobscheduler.
When operating jobs with the PowerAIM attribute, note the following.
Registering jobs with the PowerAIM attribute
To use the job nets with the PowerAIM attribute, PowerAIM must have been installed.
The job system name and the work unit name can be registered as a job with the PowerAIM attribute. Note that there are the following restrictions.
Online work units cannot be used.
Work unit list cannot be used.
Remote job system cannot be used.
The Jobscheduler sends a request to the PowerAIM to execute the work units in the specified job system environment.
Recognizing status in the Jobscheduler
When any one of the jobs in the job net with the PowerAIM attribute is submitted, the job net status will be indicated as "executing." The status of the job is "start-delayed" when the job is submitted to PowerAIM, and will change to "executing" when the actual execution of the job is started. The execution time of the job net is from when the first job of the job net is requested for execution and to when the last job is completed.
Completion code
The completion codes of the advanced programs in the work units are from 00000000 to 0xffffffff. When the completion code is 256 or higher, the Jobscheduler treat it as 255, and the actual completion code will be output to the job history. However, do not use the value between 201 and 256 as they are reserved by the Jobscheduler. For details on the completion codes to be used by the Jobscheduler, see "Jobscheduler Completion Codes" in the Systemwalker Operation Manager Reference Guide.
Solution when the execution request fails
When the execution request of a work unit to PowerAIM fails, the Jobscheduler will treat it as the completion code is 243. For details on the causes of the execution request failure, the Job Output Info window provides the completion information of the execution request API.
If an error occurs at the work unit startup, the Job Output Info window may output an error message.
Handling work units
The Jobscheduler cannot monitor the work units executed anywhere other than the Jobscheduler.
Difference in log outputs
In the process group number area of the job nets with the PowerAIM attribute, the job net numbers managed by the Jobscheduler are displayed. They are displayed in the form on "AIMxxxxx", where "xxxxx" is a value between 0 and 99999.
Completion exit of job nets and jobs
When using job nets with the PowerAIM attribute, do not execute any process which takes long in the exit routine at completion of job net in the Jobscheduler (jobsch.exit.normal or jobsch.exit) or the exit routine at completion of job (jobsch.job.exit). Executing a process which takes long may stop the other processes of the Jobscheduler since the process is not returned to the Jobscheduler server.
If it is necessary to execute any process which takes long in the job net completion exit or the job completion exit, execute that process as another process so that the completion routine itself does not take long.
Relationship with the PowerAIM commands
When the job (Work unit) with the PowerAIM attribute executed in the Jobscheduler is cancelled by the PowerAIM command, the Jobscheduler will consider it to be cancelled.
When the Jobscheduler instructs all the job nets to cancel executions, cancellation of all the executing work units will be requested to PowerAIM.
Job status when PowerAIM operation is stopped or when the Jobscheduler server is stopped
If PowerAIM operation is stopped after the Jobscheduler requests execution of the job with the PowerAIM attribute, the Jobscheduler will consider it to be cancelled.
If the Jobscheduler server is stopped after the Jobscheduler requests execution of the job with the PowerAIM attribute, it will be recognized to be abended at the next Jobscheduler server startup, even if the job has been normally completed by PowerAIM.
Job status at the system down
When the PowerAIM system is stopped during work unit execution due to the system down, it is possible to define so that the stopped work units will be restarted at the PowerAIM system restart (automatic restart of work units). However, if requested by the Jobscheduler, the Jobscheduler cannot recognize the restart. Therefore do not define the automatic restart for work units to be registered in the Jobscheduler.
