B.1 Revisions in 13-10

A custom event job that links with a non-JP1/AJS3 program to monitor events was added.

Linkage with JP1/AJS3 for Cloud Service Applications is now supported as a custom event job.

A function to communicate with environments that need to communicate by using different port numbers for each container was added. Also, the container environment now supports a logical host configuration (non-clustered logical host) in which no physical host is activated.

The following functions were added to the Web GUI:

• A function (of Management Portal) that checks the operational status of the JP1/AJS3 system

• A function (of Management Portal) that allows the user to identify which root jobnets with start conditions are retained

• A function (of Management Portal) that sets the frequency of automatically refreshing the screen

• A function (of Job Portal) that allows the user to monitor the execution generations of a root jobnet and stop all of them

A function was added that early detects communication failures continuously occurring during execution of a standard job or event job to localize the impact of the failures.

A custom event job that links with a non-JP1/AJS3 program to monitor events was added.

Linkage with JP1/AJS3 for Cloud Service Applications is now supported as a custom event job.

A function to communicate with environments that need to communicate by using different port numbers for each container was added. Also, the container environment now supports a logical host configuration (non-clustered logical host) in which no physical host is activated.

A function was added that early detects communication failures continuously occurring during execution of a standard job or event job to localize the impact of the failures.

A custom event job that links with a non-JP1/AJS3 program to monitor events was added.

Linkage with JP1/AJS3 for Cloud Service Applications is now supported as a custom event job.