DFHZC0155 date time applid sysid termid Error occurred during processing of session state data returned after restart of persisting session. sense ((instance) Module name: {DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS | DFHZXPS})

Explanation

The VTAM APPC session sysid termid persisted during a CICS persistent session restart, but an error occurred while processing the session state data returned by VTAM following an OPNDST OPTCD=RESTORE.

If the error needs further investigation, a dump is taken.

No dump is taken if one has already been taken for an earlier problem, or if the problem is known as one for which a session cannot be allowed to persist. An example of this is bind security processing not completing for this session when CICS terminated.

The reason and the corresponding AP exception trace entry are indicated by the instance in the message.

Instance

Point ID and Explanation

1

X'FBFD'

During reject attach processing a call was made to DFHZGDA but DFHZGDA rejected the call with invalid format or invalid function.

2

X'FBFD'

An error occurred during reject attach processing. The session is in an unknown state.

3

X'FBD2'

The TCTE_PRSS status byte was set to 0 but reject attach processing was not taking place. This session state is not valid for entry to DFHZXPS.

4

X'FBE4'

An error occurred during DEALLOCATE ABEND processing. This will have been handled by DFHZGDA so no dump is taken but the session is terminated.

5

X'FBD2'

The TCTE_PRSS byte (persistent sessions status byte) contained an unknown value on entry to DFHZXPS.

6

X'FBE6'

The TCTE_PRSS_CV29_PTR (pointer to data returned by VTAM) contained zeroes on entry to DFHZXPS.

7

X'FBD3'

The CV29 data returned from VTAM had a zero length on entry to DFHZXPS.

8

X'FBD4'

The BIS flow data returned by VTAM showed BIS RQE1 received but the outbound BIS flow was not consistent with this.

9

X'FBD4'

The BIS flow data returned by VTAM showed BIS RQE3 received but the outbound BIS flow was not consistent with this.

10

X'FBD4'

The BIS flow data returned by VTAM showed that no BIS flow had been received but the outbound BIS flow was not consistent with this.

11

X'FBD4'

The BIS flow data returned from VTAM was not recognized.

12

X'FBD5'

The bid flow data returned by VTAM showed a request that was not recognized where this session is the contention winner.

13

X'FBD5'

The bid flow data returned by VTAM showed that a negative X'088B' response had been sent but there was nothing to indicate that the session was closing down. This session is the contention winner.

14

X'FBD5'

The bid flow data returned by VTAM contained a response that was not recognized where this session is the contention winner.

15

X'FBD5'

The bid flow data returned by VTAM was not recognized. This session is the contention winner.

16

X'FBD5'

The bid flow data returned by VTAM contained a request that was not recognized where this session is the contention loser.

17

X'FBD5'

The bid flow data returned by VTAM contained a negative X'088B' response but there was nothing to indicate that the session was closing down. This session is the contention loser.

18

X'FBD5'

The bid flow data returned by VTAM contained a response that was not recognized where this session is the contention loser.

19

X'FBD5'

The bid flow data returned by VTAM was not recognized. This session is the contention loser.

20

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the primary and the last flow was an outbound request).

21

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the primary and the last flow was an inbound request).

22

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the primary and the last flow was an outbound response.)

23

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the primary and the last flow was an inbound response).

24

X'FBD9'

DFHZXPS could not determine the direction of the last flow from the CV29 data returned by VTAM. (This session was the primary).

25

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the secondary and the last flow was an inbound request.)

26

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the secondary and the last flow was an outbound request.)

27

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the secondary and the last flow was an inbound response).

28

X'FBD8'

The RU category returned by VTAM in the CV29 data was not valid for LU6.2. (This session was the secondary and the last flow was an outbound response).

29

X'FBD9'

CICS could not determine the direction of the last flow from the CV29 data returned by VTAM. (This session was the secondary.)

30

X'FBD9'

The last_thing_to_flow byte contained an invalid value. This indicates a logic error in DFHZXPS.

31

X'FBDA'

The last inbound flow was a response that was not for the previous request.

32

X'FBDA'

A negative response was received that was not for a command and was not a X'0846' negative response.

33

X'FBDA'

The last inbound flow was a response that was not for this bracket. (This session is the primary and started the current bracket).

34

X'FBDA'

The last inbound flow was a response that was not for this bracket. (This session is the secondary and started the current bracket.

35

X'FBDA'

The last inbound flow was a response that was not for this bracket. (This session is the primary and did not start the current bracket).

36

X'FBDA'

The last inbound flow was a response that was not for this bracket. (This session is the secondary and did not start the current bracket).

37

X'FBDA'

The last flow was a positive response outbound and was not for the previous request.

38

X'FBDB'

The last flow was an inbound LUSTAT command that could not be identified.

39

X'FBDB'

The last flow was an inbound RTR that was not processed by the bid analysis routine.

40

X'FBDB'

The last flow was an inbound command that could not be identified.

41

X'FBDB'

The last flow was an outbound LUSTAT command that could not be identified.

42

X'FBDB'

The last flow was an outbound RTR request that was not processed by the bid analysis routine.

43

X'FEDB'

The last flow was an outbound command request that could not be identified.

44

X'FBDC'

The last flow was an inbound response to BIS that was not processed with the BIS flow data.

45

X'FBDD'

The last flow was an inbound positive response to a command that could not be identified.

46

X'FBDA'

The last flow was an inbound response to an LUSTAT command but there was no corresponding outbound request.

47

X'FBDA'

The last flow was an inbound negative response to an LUSTAT request which could not be identified.

48

X'FBDC'

The last flow was a negative response inbound to a BIS request that did not show up in the BIS flow data.

49

X'FBDD'

The last flow was a negative response inbound to a command that could not be identified.

50

X'FBDC'

The last flow was a positive response outbound to BIS that was not consistent with the BIS flow data.

51

X'FBDD'

The last flow was a positive response outbound to a command that could not be identified.

52

X'FBDC'

The last flow was a negative response outbound to BIS that was not consistent with the BIS flow data.

53

X'FBDD'

The last flow was an outbound negative response to a command that could not be identified.

54

X'FBE1'

The last request to flow was SIGNAL (expedited flow) but no normal flow data appears in the CV29 normal flow data area.

55

X'FBE1'

The last flow was a SIGNAL request (expedited flow). However analysis of the normal flow data shows both sides sending which is not possible. (Outbound flow was with EC.)

56

X'FBE1'

The last flow was a SIGNAL request (expedited flow). However analysis of the normal flow data shows both sides sending which is not possible. (Outbound flow was in chain.)

57

X'FBD5'

The tctewin/tctelse bits in the TCTTE have not been set correctly.

58

X'FBDF'

The session is not in CS mode when analysis of the CV29 data shows that a call to DFHZGDA to ABEND the current transaction is required.

59

X'FBE7'

A SEND_FMH7 call to DFHZGDA was rejected with invalid_format or invalid_function.

60

X'FBE7'

A SEND_FMH7 call to DFHZGDA was rejected because of a disastrous error in DFHZGDA.

61

X'FBE7'

A RECEIVE_FMH7 call to DFHZGDA was rejected with invalid_format or invalid_function.

62

X'FBE7'

A RECEIVE_FMH7 call to DFHZGDA was rejected because of a disastrous error in DFHZGDA.

63

X'FBE0'

Internal DFHZXPS logic error. The input parameters are invalid when a call is about to be made to DFHZGDA.

64

X'FBE5'

An invalid return code was received from a call to DFHTCPCL with ENTRY=DFHZRST1.

65

X'FBDE'

The tcte_bid_status byte contained an unrecognized value.