![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Job Management Partner 1/Base User's Guide
The following problems might occur in Windows or UNIX.
Table 16-3 Problems common to both Windows and UNIX
No. Problem 1 Multiple JP1 events occur within a short period of time, causing a delay in registration and transfer. 2 The event database is corrupt. 3 When JP1/Base starts, the message The port ID for the SES emulator is not defined appears. 4 JP1/Base does not function as defined in a definition file.
- Organization of this subsection
- (1) Multiple JP1 events occur within a short period of time, causing a delay in registration and transfer.
- (2) The event database is corrupt.
- (3) When JP1/Base starts, the message "The port ID for the SES emulator is not defined" appears.
- (4) JP1/Base does not function as defined in a definition file.
(1) Multiple JP1 events occur within a short period of time, causing a delay in registration and transfer.
When an error generates a large number of JP1 events in quick succession, the JP1 event reporting the error might take a long time to appear in JP1/IM - View. This might delay the execution of any JP1/AJS jobs triggered by these JP1 events. Forwarding of the JP1 events being processed when the error occurs resumes when the failed host is restored and the event service restarts.
If it is essential to stop the delayed JP1 events from being sent, because of the load on the system or the effect on job processing, initialize the event database on the issuing host. If you want to save the JP1 events already registered in the event database, use the jevexport command to output the event database in CSV format before you initialize the database.
For details on the procedure to initialize the event database, see 8.2 Initializing the event database.
To prevent the generation of large numbers of JP1 events, adjust the JP1 event forwarding conditions in the forwarding setting file (forward).
(2) The event database is corrupt.
The event database might be corrupt due to the following reasons:
- Sudden loss of power because of a power outage or some other reason
- Backing up or restoring the event database by an OS command or backup software while the event service is active
- Editing the event database in a text editor
- Redirecting command output results or other information to the event database
- A hard disk error
Even if the event database is damaged, the event service will still start or continue running, and new JP1 events can still be registered or acquired as normal. However, damaged records will not be retrieved or acquired. Damaged records in the event database might also affect the performance of event searches from JP1/IM - View.
The KAJP1057-W, KAJP1058-W, or KAJP1059-E message is output to the event log, syslog, and integrated trace log when the event database is damaged. Initialize the event database if any of these messages appears.
For details on the procedure to initialize the event database, see 8.2 Initializing the event database.
(3) When JP1/Base starts, the message "The port ID for the SES emulator is not defined" appears.
The reason this message displays, and the necessary action to correct the error, are described below:
- Causes
- No port ID for SES compatibility is specified in the services file. This is not a problem if no events in JP1/SES format will be sent or received.
- Action
- If events will be forwarded to or from JP1/SES, JP1/AJS, or a program that uses the JP1/SES protocol (JP1/OJE, for example), add the JP1AutoJob specification (in Windows) or jesrd specification (in UNIX) to the services file. You can specify any port number.
(4) JP1/Base does not function as defined in a definition file.
Because some of the settings for a service running on a host do not reflect the settings in the service's definition file, the service might not function as expected. In order to determine the source of the problem, you must compare the operating information of the service that is currently running and the contents of the service's definition file.
You can use the jbsgetopinfo command to view the operating information of a service that is currently running. This command provides operating information defined in the forwarding settings file for the event service, the action definition file for the log file trap, and the action definition file for the event log trap (Windows only) for the service. Compare the operating information with the contents of each respective definition file. If there is a difference, take the necessary action to correctly incorporate the contents of the definition files. For details on the jbsgetopinfo command, see jbsgetopinfo in 13. Commands.
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.