64 Application Call Processing Engine Log Messages (9442)
TOPS VSN Log and alarm messages
Description:
The ACPE could not determine the locality treatment for the
current call because the Locality Database is either a new set of locality prompts,
or a new set of locality prompts is being saved. This call will be handled
according to the datafill of parameters Locality_Check and Loc_Default_Prompt
in table User Interaction.
Action:
No immediate action is required because the ACPE continues to
process calls,(at a diminished capacity).
0003/0017
Message:
no locality call processing for current call.
Description:
The ACPE could not determine the locality treatment for the
current call because the Locality Database is not in the Working state. This call
will be handled according to the datafill of parameters Locality_Check and
Loc_Default_Prompt in table User Interaction.
Action:
No action is required because the ACPE continues to process
calls,(at a diminished capacity).
0003/001A
Message:
[PRU_NAME], error. An invalid name plus locality mode, <invalid
mode>, has been found in table "LOC_SCREEN_CODES". As a result ACPEs
will not load.
Description:
This log indicates that the valid values for the name plus locality
mode field are given in the help information in the table editor.
Action:
The table must be corrected before the ACPEs will load.
0003/0018
Message:
ACPE failed to communicate with the Locality Database.
Description:
This call will be handled according to datafill of the parameters
Locality_Check and Loc_Default_Prompt in table User Interaction. Debugging
information is provided.
Action:
No action is required because the ACPE continues to process
calls,(at a diminished capacity).
0003/0200
Message:
State table log
Description:
This is a log that is generated by the state table for application
TABS. Two lines of state data are provided.
Action:
Action as indicated in the message.
0003/0201
Message:
Log generated by state table for application <TABS>. [Call
abnormally terminated. See trace back for detail.]
Current state : <state code> via input: <event #>
Called from : <state code> via input: <event #>
Status
Description:
This log is generated by the state table when it encounters an
error during an event sequence.
Action:
Contact NT immediately. Record the state and event codes listed in
the log and report them to the NT representative.