5.3 Notes on execution of service linkage jobs

• A service linkage job obtains the latest information on the JP1/AJS3 for Cloud Service Applications server. Therefore, if you change definitions used for the service linkage jobs on the JP1/AJS3 for Cloud Service Applications server, the service linkage job may not correctly operate.

  When changing definitions on the JP1/AJS3 for Cloud Service Applications server, make sure that the service linkage job operates correctly.

  If you change the definitions of AJS3 - View custom input items, you must reregister the service linkage jobs in JP1/AJS3 - View and redefine the jobs.

  Perform the following steps:

  1. Configure the service linkage job to hold (or take a similar action) to prevent it from being executed.

  2. In the Web screen of the JP1/AJS3 for Cloud Service Applications server, modify the execution definitions.

  3. In the same Web screen, output the service linkage job information file.

  4. Run the ajscsajobreg command to register the service linkage job information file from step 3 in JP1/AJS3 - View (specify the -f option to overwrite the existing definitions).

  5. Launch the Define Details - [Service Linkage Job] screen for the defined service linkage job and update the definitions.

  6. Revert the settings made in step 1 (for example, release the job from hold).

• Service linkage jobs are custom jobs. As with existing custom jobs, the return codes that can be checked with JP1/AJS3 include the return codes of service linkage jobs and the return codes set by JP1/AJS3, which is described in 7.10.3 Checking the return code of a job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

• Check in advance if a command can be executed in the environment before executing a service linkage job.

  When the command defined on the JP1/AJS3 for Cloud Service Applications server does not exist, the command defined on the JP1/AJS3 for Cloud Service Applications server ends with a return value other than 0.

• Make sure that the sizes of the standard output and standard error output of the command defined on the JP1/AJS3 for Cloud Service Applications server are not too large. We recommend that the total size of standard output and standard error output is approximately 3 MB (megabyte).

  If the size is large, the service linkage job behaves as follows:

  For Windows:

  The service linkage job ends with a return value of "100" (insufficient memory).

  For Linux:

  The process of the service linkage job is stopped by the kernel, the status of the service linkage job is "Forcibly terminated", and the return value is "-1".

• Make sure that the full unit name^# of the service linkage job does not contain the following characters (some of the symbols and characters that can be used for migration from the previous product (JP1/AJS)).

  " \

  If the full unit name^# contains any of the above characteristics, the service linkage job ends with a return value of "82".

  #

  Contains the job net name and job group name in the upper layer of the job

• When the execution host of the service linkage job is on Windows, there is a limitation on the number of characters of OS command lines. Set the number of characters of command lines (command lines after the variable replacement) defined on the JP1/AJS3 for Cloud Service Applications server to be approximately 8000. If the number of characters exceeds the limitation on OS command lines, the command defined on the JP1/AJS3 for Cloud Service Applications server ends with a value other than 0.

To Page Top