OpenTP1 Version 7 Messages

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

KFCA00858-W

schedule service is delayed. server name: aa...aa, local pid: bb...bb, working pid: cc...cc, information: dd...dd, ee...ee,ff....ff,gg....gg,hh....hh,ii...ii

The schedule service is experiencing heavy load, or the schedule service processing of another process is delayed, so the processing of the schedule service is delayed on the server.
aa...aa: Name of the server where the schedule service is running (up to nine alphanumeric characters).
bb...bb: ID of the process for which the schedule service is delayed (up to five digits).
cc...cc: ID of the process executing the schedule service (up to five digits).
dd...dd: Relative address of the server management table (up to 10 hexadecimal characters).
ee...ee: ID of the thread in which the schedule service is delayed (up to 10 digits).
ff....ff: Current value for the number of concurrent services in the process that is processing the schedule service (a one-digit or two-digit number).
Depending on the process processing the schedule service, the system may be unable to display this information.
gg....gg: Peak value for the number of concurrent services in the process that is processing the schedule service (a one-digit or two-digit number).
Depending on the process processing the schedule service, the system may be unable to display this information.
hh....hh: Amount of time for which the running process is to be run on this server (up to 10 digits).
ii...ii: Peak value for the amount of time for which the start of the process at this server is delayed (up to 10 digits).
S: Continues processing. If the delay of the schedule service lasts for a long time, this message may appear more than once.
Countermeasure: If this message is output from the same process more than once and the working process ID (cc...cc) is that of the system server process of OpenTP1, contact the maintenance personnel.
If the working process ID (cc...cc) is for a user server process or a command process, forcibly terminate the process, collect the dump to a core file, and then contact the maintenance personnel.