TRANSFER Installation and Management Guide

TSCHED Output File Error Messages
Error Messages
B–50 13198 Tandem Computers Incorporated
[ nn ]:Could not obtain configured name for:
[ nn ]: xxxxxxxxxxxxxxxxxxxxxxxx
[ nn ]:UOW xxx failure: nnnn/snnnn in xxxx
[ nn ]:*ERROR* will DELAY and retry
Cause. The TAREQ encountered an unexpected error while trying to obtain needed
information about your configuration via the GET-CONFIG-NAME UOW. The
second line of this message indicates the value the TAREQ supplied in the ENTITY-
NAME field of that UOW; the number in the third line is the value the TAREQ found
in the RETN-CODE field.
Effect. The TAREQ executes the EXIT program. If the TAREQ has a current
assignment, that assignment is made available for processing by other TAREQs.
Recovery. Correct the indicated TRANSFER error.
[ nn ]:*ERROR* Could not start session for:
[ nn ]: xxxxxxxxxxxxxxxxxxxxxxxx (correspondent name)
[ nn ]:UOW xxx failure: nnnn/snnnn in xxxx
[ nn ]:*ERROR* will DELAY and retry
Cause. The TAREQ was unable to start a local session for itself either at its startup or
after having its existing session become invalid. The indicated number is the value the
TAREQ found in the RETN-CODE field of the START-SESSION UOW.
Effect. The TAREQ executes the EXIT program.
Recovery. Correct the indicated TRANSFER error.
[ nn ]:IPC header problem
[ nn ]:IPC error: snnnn/snnnn/snnnn
Cause. The TAREQ received an unexpected error indication in an IPC header from the
local TISERV-ASYNC or TWORK.
Effect. If the problem is an invalid session ID, the TAREQ attempts to start a new
session and then resumes processing its current assignment at an appropriate point.
For any other problem, the TAREQ releases the current assignment, which might be
placed in the hold state, and asks TSCHED for a new assignment.
Recovery. See the indicated numbers in the discussion of request and reply headers in
the TRANSFER Reference Manual.