5.1.2 List of events
The events issued by JP1/AJS3 for EAP are listed below for each category.
- Organization of this subsection
(1) Events related to the environment setup (common to all functions) for JP1/AJS3 for EAP
|
Event ID |
Event name |
When event issued |
Maintenance information |
|---|---|---|---|
|
0x2100 |
Environment setup file (invalid key/invalid section) warning |
An environment setup file key name (key) or section name (section) is invalid |
No |
|
0x2101 |
Invalid environment setup file (key value illegality) warning |
An invalid value (string) was specified for an environment setup file key. |
No |
|
0x2102 |
Invalid environment setup file (duplicate keys or sections) warning |
An environment setup file key name (key) or section name (section) was duplicated. |
No |
|
0x2103 |
Invalid environment setup file (invalid character string used) warning |
The environment setup file contains an invalid character string. |
No |
|
0x2104 |
Invalid environment setup file (environment setup file inaccessible) warning |
The environment setup file cannot be accessed. |
No |
|
0x2105 |
Invalid parameter (trace file inaccessibility) warning |
The trace file cannot be accessed because of an invalid parameter. |
No |
|
0x2106 |
Invalid parameter (unable to create/extend trace file) warning |
The trace file cannot be created or extended because of an invalid parameter. |
No |
(2) Events related to job control function
|
Event ID |
Event name |
When event issued |
Maintenance information |
|---|---|---|---|
|
0x3000 |
Job creation |
R/3 job creation was successful. |
Yes |
|
0x3100 |
Job creation failure |
R/3 job creation failed. |
Yes |
|
0x3400 |
Job release |
R/3 job release was successful. |
Yes |
|
0x3500 |
Job release failure |
R/3 job release failed. |
Yes |
|
0x3600 |
Job termination |
R/3 job termination was successful. |
Yes |
|
0x3700 |
Job termination failure |
R/3 job termination failed. |
Yes |
|
0x3800 |
Job deletion |
R/3 job deletion was successful. |
Yes |
|
0x3900 |
Job deletion failure |
R/3 job deletion failed. |
Yes |
|
0x3901 |
Incomplete-job deletion failure |
An incomplete R/3 job failed to be deleted. |
Yes |
|
0x3A00 |
Job completion monitoring success (when a job has ended normally) |
R/3 job completion monitoring was successful when the job has ended normally. |
Yes |
|
0x3A01 |
Job completion monitoring success (when a job has been terminated) |
R/3 job completion monitoring was successful when the job has been terminated. |
Yes |
|
0x3B00 |
Job completion monitoring timeout |
An R/3 job completion monitoring timeout occurred. |
Yes |
|
0x3C00 |
Job completion monitoring failure |
R/3 job completion monitoring failed. |
Yes |
|
0x3C01 |
Job completion monitoring failure because of reconnection timeout |
R/3 job completion monitoring failed because reconnection timeout occurs. |
Yes |
|
0x3D00 |
XMI interface session audit level change failure |
An XMI interface session audit level change failed. |
Yes |
|
0x3E00 |
R/3 job log acquisition failure |
R/3 job log acquisition failed. |
Yes |
|
0x3F00 |
Job interrupt detection |
An R/3 job interruption was detected. |
Yes |
|
0x3F01 |
Detection of a job without confirmation of completion (job deletion) |
An R/3 job without completion confirmation was detected (since the job to be monitored was deleted). |
Yes |
|
0x3F02 |
Detection of a job without confirmation of completion (child job detection failure) |
An R/3 job without completion confirmation was detected (since the job was deleted before any child job was detected). |
Yes |
|
0x3F03 |
Detection of a job without confirmation of completion (number of jobs to be monitored exceeded the maximum limit) |
An R/3 job without completion confirmation was detected (since the number of jobs to be monitored exceeded the maximum limit). |
Yes |
|
0x3F04 |
Unreleased-job detection |
An unreleased job was detected. |
Yes |
(3) Events related to the InfoPackage control function
|
Event ID |
Event name |
When event issued |
Maintenance information |
|---|---|---|---|
|
0x4000 |
InfoPackage startup |
InfoPackage startup was successful. |
Yes |
|
0x4100 |
InfoPackage startup failure |
InfoPackage startup failed. |
Yes |
|
0x4200 |
InfoPackage completion monitoring success (when InfoPackage has ended normally) |
InfoPackage completion monitoring was successful when InfoPackage has ended normally. |
Yes |
|
0x4201 |
InfoPackage completion monitoring success (when InfoPackage has ended abnormally) |
InfoPackage completion monitoring was successful when InfoPackage has ended abnormally. |
Yes |
|
0x4300 |
InfoPackage completion monitoring timeout |
An InfoPackage completion monitoring timeout occurred. |
Yes |
|
0x4400 |
InfoPackage completion monitoring failure |
InfoPackage completion monitoring failed. |
Yes |
|
0x4500 |
InfoPackage completion monitoring failure because of reconnection timeout |
InfoPackage completion monitoring failed because reconnection timeout occurred. |
Yes |
(4) Events related to the process chain control function
|
Event ID |
Event name |
When event issued |
Maintenance information |
|---|---|---|---|
|
0x5000 |
Process chain startup |
Process chain startup was successful. |
Yes |
|
0x5100 |
Process chain startup failure |
Process chain startup failed. |
Yes |
|
0x5200 |
Process chain completion monitoring success (when the process chain ended normally) |
Process chain completion monitoring was successful when the process chain ended normally. |
Yes |
|
0x5201 |
Process chain completion monitoring success (when the process chain ended abnormally) |
Process chain completion monitoring was successful when the process chain ended abnormally. |
Yes |
|
0x5300 |
Process chain completion monitoring timeout |
A process chain completion monitoring timeout occurred. |
Yes |
|
0x5400 |
Process chain completion monitoring failure |
Process chain completion monitoring failed. |
Yes |
|
0x5500 |
Process chain completion monitoring failure because of a reconnection timeout |
Process chain completion monitoring failed because a reconnection timeout occurred. |
Yes |