Job Management Partner 1/Software Distribution Administrator's Guide Volume 2

[Contents][Glossary][Index][Back][Next]

2.2.2 Attributes of JP1 events

The two types of attributes for JP1 events are the basic attributes and the extended attributes. Extended attribute details are reported to JP1/IM in the case of job completion reporting events, client alert events, operation-monitoring alert event for an invalid device connection, and operation-monitoring alert event for operation history deletion. You can use JP1/IM - View's Event Console window to check the details of the extended attribute reported with a send instruction end event.

Table 2-1 shows the basic attributes of JP1 events, Table 2-2 shows the extended attributes of JP1 events, Table 2-3 shows the details of the extended attributes for a send instruction end event, Table 2-4 shows the details of the extended attributes for a client alert event, Table 2-5 shows the details of the extended attributes for an operation-monitoring alert event for an invalid device connection, Table 2-6 shows the details of the extended attributes for an operation-monitoring alert event for operation history deletion, Table 2-7 shows the details of the extended attributes for an operation-monitoring alert event for software startup suppression, and Table 2-8 shows the details of the extended attributes for an operation-monitoring alert event for print suppression.

Table 2-1 Basic attributes of JP1 events

Name of JP1 event Event ID Message
Send instruction end event Normal termination 00010401 Software Distribution Manager was abnormally terminated.
Error termination 00010402 xxx command was successfully completed.
Send job end event Normal termination 00010403 xxx command was abnormally terminated.
Error termination 00010406 xxx was successfully completed.
Report when the server is down 00010407 xxx was abnormally terminated.
Report when the relay system is down 00010101 Software Distribution SubManager was abnormally terminated.
Client alert event

00010410 or 00010110# Client (xxx) is in a dangerous condition (yyy).
00010411 or 00010111# Client (xxx) posted a warning (yyy).
00010412 or 00010112# Client (xxx) was back to normal (yyy).
Operation-monitoring alert event for an invalid device connection 00010420 The client (xxx) failed to suppress an operation by the user (yyy) to insert a device (zzz) into the client computer.
00010421 The client (xxx) suppressed an operation by the user (yyy) to insert a device (zzz) into the client computer.
Operation-monitoring alert event for operation history deletion 00010422 The yyy to zzz operation history was lost because the operation history file was deleted on the client (xxx).
Operation-monitoring alert event for software startup suppression 00010423 The client (xxx) suppressed an operation by the user (yyy) to start the product (zzz).
Operation-monitoring alert event for print suppression 00010424 The client (xxx) suppressed a print operation by the user (yyy).

#: The event ID is 000104XX for JP1/Software Distribution Manager and 000101XX for JP1/Software Distribution Client (relay system). XX is a variable.


Table 2-2 Extended attributes of JP1 events

Attribute name Description Attribute value
SERVERITY Severity Severity for the system
(Emergency, Alert, Critical, Error, Warning, Notice, Information, Debug)
USER_NAME User name Executing user
JP1_SOURCEHOST Source host name Name of the host where the event resulting in issuance of the JP1 event occurred
PRODUCT_NAME PP name /HITACHI/JP1/NETMDM
OBJECT_TYPE Object type Hierarchical level at which the JP1 event occurred.
(JOB, JOBNET, ACTION, ACTIONFLOW, DMJOB, COMMAND, PACKAGE, CLIENTALERT, DM_MONITORING_ALERT)
OBJECT_NAME Object name Name of the location where JP1 event occurred (job number, instruction number, package name, alert code, user name)
ROOT_OBJECT_TYPE Type of registration name Type of registration name (same as OBJECT_TYPE)
ROOT_OBJECT_NAME Registration name Name as a registration-execution unit (job number, instruction number, package name)
OBJECT_ID Object ID Unique character string in the integrated system (job number, instruction number)
OCCURRENCE Event type Type of event that occurred
(START, END, CREATE, DESTROY, MODIFY, SUBMIT, UNSUBMIT, PAUSE, RELEASE, RESTART, EXCEPTION, ALERT, ALERT_CLEAR, SUPPRESS, etc.)
START_TIME Starting time Execution start time (number of seconds from 00:00:00 1/1/1970)
END_TIME Termination time Execution termination time (number of seconds from 00:00:00 1/1/1970)
RESULT_CODE Termination code Termination code

Table 2-3 Details information about the extended attributes for a send instruction end event

Attribute name Description
S1 Job name
S2 Job number
S3 Job type
D: Install package
M: Transfer package to relay system
G: Collect files from client
S: Collect files from client to relay system
A: Acquire collected files from relay system
J: Send package, allow client to choose
S4 Instruction number
S5 Maintenance code
S6 Route information
P1 Package name
P2 Package ID
P3 Package version
P4 Package generation number
P5 Cabinet ID
P6 Package code
D: Package from PC
C: Package from WS

Table 2-4 Detailed information about the extended attributes for a client alert event

Attribute name Description
A1 Alert code
A2 Host name
A3 IP address

Table 2-5 Detailed information about the extended attributes for an operation-monitoring alert event for an invalid device connection

Attribute name Description
O1 Execution time
O2 IP address
O3 Host name
O4 Operation monitoring policy that has been applied
O5 Version of the operation monitoring policy that has been applied
O6 Connection name
O7 Device instance ID#1
O8 Controller device instance ID#2
O9 Device type

#1
Device instance ID under the device type (such as disk drive or DVD/CD-ROM drive)

#2
Device instance ID under the device controller

Table 2-6 Detailed information about the extended attributes for an operation-monitoring alert event for operation history deletion

Attribute name Description
O1 Execution time
O2 IP address
O3 Host name
O4 Operation monitoring policy that has been applied
O5 Version of the operation monitoring policy that has been applied
O10 Start date and time of the information that was lost
O11 End date and time of the information that was lost

Table 2-7 Detailed information about the extended attributes for an operation-monitoring alert event for software startup suppression

Attribute name Description
O1 Execution time
O2 IP address
O3 Host name
O4 Operation monitoring policy that has been applied
O5 Version of the operation monitoring policy that has been applied
O12 Product name
O13 Product version
O14 File name
O15 File version
O16 Program start account

Table 2-8 Detailed information about the extended attributes for an operation-monitoring alert event for print suppression

Attribute name Description
O1 Execution time
O2 IP address
O3 Host name
O4 Operation monitoring policy that has been applied
O5 Version of the operation monitoring policy that has been applied
O17 Document name
O18 Name of printer being used