Hitachi

JP1 Version 13 JP1/Automatic Job Management System 3 for Cloud Service Applications


6.2.7 Return codes of service linkage objects monitoring jobs

The following table shows return codes when service linkage objects monitoring jobs are executed.

Table 6‒6: Return codes of service linkage objects monitoring jobs

Return code

Content

Corresponding messages

0

The monitoring condition is met.

--

101 to 150

This is the return code set according to the definitions, if any, on the JP1/AJS3 for Cloud Service Applications server.

KNBB6310-E

151

The definition of the service linkage objects monitoring job contains an error.

KNBB6102-E

152

  • In the agent host, the manager host name specified as the server host name for the JP1 user is incorrect.

  • In the user mapping definition of the agent host, the applicable JP1 user is not registered.

  • In the user mapping definition of the agent host, an OS user that does not exist is registered.

  • In the user mapping definition of the agent host, an incorrect OS user password is registered (Windows only).

  • A JP1 user with the same name as that of the OS user who executed the ajsentry command is not found.

  • The owner JP1 user is different from the JP1 user who performed the execution registration.

  • There is an ongoing memory shortage.

  • When Owner user is specified in Executed by and Owner is empty in the detailed definition of the job, the name of the OS user who is not registered as a JP1 user is set for the startup account of the JP1/AJS3 service on the manager host.

KNBB6309-E

153

Failed to read the connection configuration file.

KNBB6200-E

154

The syntax in the connection configuration file has an error.

KNBB6201-E

155

Failed to resolve the name (IP address resolution) of the JP1/AJS3 for Cloud Service Applications server.

KNBB6204-E

156

An error occurred during access to the temporary file.

KNBB6449-E

170

Failed to connect to the JP1/AJS3 for Cloud Service Applications server.

KNBB6202-E

171

An error occurred in communication with the JP1/AJS3 for Cloud Service Applications server.

KNBB6203-E

172

The information obtained from the JP1/AJS3 for Cloud Service Applications server contains an error.

KNBB6300-E

173

A definition item for JP1/AJS3 for Cloud Service Applications has one of the following errors:

  • The mandatory item is left blank.

  • Number of characters

  • Format of the value

KNBB6100-E

175

A definition of the service linkage objects monitoring job is inconsistent with the one on the JP1/AJS3 for Cloud Service Applications server.

  • Although the Update option is selected in the Monitoring options in the definition of the service linkage objects monitoring job, any update monitoring target is not specified in the definition on the JP1/AJS3 for Cloud Service Applications server.

KNBB6103-E

176

An error occurred in the extraction processing of information from the execution result of the object list information acquisition command according to the JMESPath query syntax.

KNBB6105-E

177

The result extracted from the object list information is incorrect.

KNBB6106-E

178

The update monitoring target data extracted from the object list information is in valid format.

KNBB6107-E

180

Failed to obtain an environment variable.

KNBB6400-E

181

An error occurred in the command executed by the service linkage objects monitoring job.

KNBB6311-E

182

The command executed by the service linkage objects monitoring job has received a signal and ended.

KNBB6312-E

183

The size of the standard output for the command executed by the service linkage objects monitoring job exceeded the value of the LimitObjMonStdOutSize environment setting parameter.

KNBB6306-E

190

A memory shortage occurred.

KNBB6450-E

191

System error occurred.

KNBB6451-E

192

An unexpected error occurred.

KNBB6452-E

Note

If you work with the entire start condition (when the start condition is forcibly terminated, for example) or if an error related to the entire start condition occurs, the return code of each event of the entire start condition is set to 0 (zero). On the other hand, if an error on a particular event occurs (when an error occurs due to an incorrect definition, for example), the return code shown in the table is set.