4.6.2 Details of the unit definition parameters of service linkage monitoring jobs
This section describes the details of the unit definition parameters of service linkage monitoring jobs. For parameters other than those listed below, see the description on the creation of information definition files in the manual JP1/Automatic Job Management System 3 Command Reference.
- cety="CE_service-linkage-monitoring-job-type_monitoring-job-name";
-
This is a parameter for defining the information used to identify which program is linked with the custom event job. In a service linkage monitoring job of JP1/AJS3 for Cloud Service Applications, you can define an identifier that denotes the type of the service linkage monitoring job listed in the following table.
Table 4‒7: List of service linkage monitoring job types that can be specified Type of monitoring job
Value to be specified for service linkage monitoring job type
Service linkage objects monitoring job
COBM
Specify a string that begins with CE_, followed by the job type listed in the above table, like CE_service-linkage-monitoring-job-type_, and followed by a monitoring job name.
- jpoif="macro-variable-name:passing-information-name";
-
For specifications such as macro variable names and the maximum allowed sizes of parameters, see the description on the creation of information definition files in the manual JP1/Automatic Job Management System 3 Command Reference.
The values available for the name of passing information are CMTMOUT and OBJECT01 to OBJECT10. OBJECT01 to OBJECT10 will store the value configured in the monitoring definition. For details, see the description about the passing information of monitoring jobs for each monitored service in Chapter 6.
- cprm="definition-parameter";
-
Different monitoring job types have different definitions. The following table shows the format and parameter value for each type.
Table 4‒8: Definition parameters of service linkage objects monitoring jobs No.
Item
Format#1
Value#1, #2
1
Authentication definition name
AJS_CSA_AUTHINFNAME=value
Specify any character string of between 0 and 64 bytes.
Optional.
2
Monitoring job name
AJS_CSA_MONDEFINFNAME=value
Specify any character string of between 2 and 31 bytes.
3
Parameter (optional definition item)
AJS_CSA_ENV_variable-value=value
Specify any character string of between 0 and 12,000 bytes.
You can define up to 10 instances of this parameter.
Optional.
Note that the variable-value part can accept a character string consisting of A to Z and 0 to 9 within 58 bytes.
4
Name of the object to be monitored
AJS_CSA_OBJWF=value
Specify any character string of between 1 and 3,072 bytes.
5
Monitoring options
AJS_CSA_OBJWC=value
Specify one of the following characters strings:
-
c: Monitors creation of an object.
-
d: Monitors deletion of an object.
-
u: Monitors object updates.
These character strings can be specified together and concatenated to create a string of maximum of 3 bytes.
- Example:
-
cd: Monitors creation and deletion.
If multiple character strings are specified, their order does not matter but each character string can be used only once.
6
Monitoring interval
AJS_CSA_OBJWI=value
Specify a numeric value from 10 to 600 of between 2 and 3 bytes (the unit is second).
Any 0s that precede the value are ignored.
7
Operation settings during creation monitoring
AJS_CSA_OBJWCO=value
Specify either of the following character strings:
-
y: Indicates that the monitoring condition is considered to be met if an object already exists when monitoring is started.
-
n: Indicates that the monitoring condition is considered to be met if an object is detected after monitoring is started.
This option is independent of what is specified in the Monitoring options parameter. (An error does not occur if this option is enabled when a value other than c is specified in the Monitoring options parameter.)
Optional. If omitted, this parameter assumes n.
8
Operation settings during deletion monitoring
AJS_CSA_OBJWDO=value
Specify either of the following character strings:
-
y: Indicates that the monitoring condition is considered to be met if an object does not exist when monitoring is started.
-
n: Indicates that the monitoring condition is considered to be met if deletion is detected after monitoring is started.
This option is independent of what is specified in the Monitoring options parameter. (An error does not occur if this option is enabled when a value other than d is specified in the Monitoring options parameter.)
Optional. If omitted, this parameter assumes n.
- #1
-
If a particular format is specified twice (the first and second ones have the same value in their left-hand side), the value of the second one (defined later) has the precedence over the first.
- #2
-
An optional item can be omitted by:
- Omitting the entire string in the Format column
- Omitting only the value part of the string in the Format column
-
Note that if the value specified for the definition parameter in the above table is invalid, an error is detected when the monitoring job is executed, not when the definition is registered using ajsdefine.