DFHXG6491 applid Logic error during session tracking. REASON rcode terminal/session event
Explanation
XRF session tracking encountered an unexpected circumstance probably due to a design error. The reason code (rcode) is one of the following.
- 1
-
POST called but no pending action for terminal or session.
Inserts:
-
name of terminal or session.
-
- 2
-
DFHZXST called with bad request value.
- 3
-
XRF-capable session lacks a correlation id.
Inserts:
-
name of terminal or session,
-
code for event being tracked.
The following are valid for DFHSUSX only.
-
X'01'?Send sign on data
-
X'02'?Send sign on data (catchup)
-
X'03'?Receive sign on data
The following are valid for DFHZXST only.
-
X'F1'?BIND
-
X'F2'?Free LOGON data
-
X'F3'?UNBIND
-
- 4
-
Could not get key to build tracking message.
Inserts:
-
name of terminal or session
-
code for event being tracked (see 3 above)
-
- 5
-
Could not get send tracking message.
Inserts:
-
name of terminal or session
-
code for event being tracked (see 3 above)
-
- 6
-
Could not find session named in tracking message.
Inserts:
-
name of terminal or session
-
code for event being tracked (see 3 above)
-
- 7
-
Illegal entry named in tracking message.
Inserts:
-
name of terminal or session
-
code for event being tracked (see 3 above)
-
- 8
-
Bad request code in tracking message.
Inserts:
-
name of terminal or session
-
bad request code (see 3 above for valid DFHZXST codes)
-
- 9
-
Correlator in tracking message is longer than 8.
Insert:
-
name of terminal or session
-
- 10
-
Unable to schedule standby BIND.
Insert:
-
name of terminal or session.
-
System action
Normal processing continues.
User response
Note the message. Resources and states may be incorrect should the backup take over. If many of these messages are issued, then it is likely that there is a more general problem.
Module
XMEOUT parameters/Message inserts
- applid
- rcode
- terminal/session
- event
Destination
Console