RTP3 entry for RTP PAB dispatch (Part 3)

This trace record is a continuation of the RTP entry.

Byte (hex)

Contents

00–03

Record ID: C"RTP3"

04–05

Multinode persistent sessions (MNPS) flags:

Byte 1

Bit: Meaning
1... ....: This end of the RTP connection is associated with an MNPS application.
.1.. ....: The partner endpoint is associated with an MNPS application.
..1. ....: MNPS endpoint path switch is in progress.
...1 ....: Incoming data should be discarded until MNPS recovery is complete.
.... 1...: MNPS enhanced path switch processing is in progress.
.... .1..: This RTP connection maintains a real connection path that is different from its computed session path.
.... ..1.: MNPS coupling facility structure data needs to be repopulated.
.... ...x: Unused; available

Byte 2

Bit: Meaning
1... ....: MNPS recovery is underway.
.x.. ....: Unused; available
..1. ....: The recovery PAB has given permission to delete the RPNCB.
...1 ....: A request to delete the RPNCB has been queued to the recovery PAB by RTP context manager.
.... 1...: Recovery is being terminated, but RCM is waiting for completion of ALS processing before continuing.
.... .1..: This recovery PAB is chained on the ATCVT list of recovery PABs.
.... ..1.: PU termination processing is waiting for RTP connection cleanup.
.... ...1: Route setup processing is required during RTP recovery.

06–07

Unused, available

08–0B

Highest contiguous inbound NLP sequence number acknowledged by this endpoint.

0C–0F

Sequence number associated with the first NLP pending notification from TSC that the data can be acknowledged to a partner endpoint

10–13

14–17

18–1B

1C–1F