(1) .-DLURSAW--=--YES-----. >>-+---------------------+------------------------------------->< '-DLURSAW--=--+-YES-+-' '-NO--'
Notes:
- DLURSAW is meaningful only if the NODETYPE=NN start option is also used.
Specifies whether there will be an NLDM application started that needs to receive information about any RTP path switches involving a DLUR that is the end point of an RTP pipe. This process is to update the NLDM of RSCV updates when the DLUR's pipe is path switched. The endpoint of the HPR pipe that path switched, is not this VTAM®. By default this capability will be enabled in the host. Whether path switch updates are actually received by NLDM also depends on the capability and configuration of the DLUR.
Note: If SAVERSCV=NO is coded, then the session RSCV portion
of the DLUR session awareness data is freed when the session is active.
Thus, if NLDM is not active at the time, the session RSCV is not available
at NLDM warm start. Conversely, if SAVERSCV=YES is specified, then
the session RSCV is saved for NLDM warm start, at a cost of increased z/OS® storage
utilization. SAVERSCV has no influence on z/OS saving
the HPR session awareness data that the DLUR supplied. It is maintained
as long as a single dependent LU has a session that had been reported
as being associated with that HPR pipe.
- DLURSAW=NO
- Specifies that DLUS/R function will not report the RSCV updates
to NLDM when the DLUR's pipe is path switched. Note: This could result in NLDM not getting RSCV updates and the DISPLAY SESSIONS PATHINFO=YES display would be incomplete.
- DLURSAW=YES
- Specifies that DLUS/R function will report the RSCV updates to NLDM when the DLUR's pipe is path switched, if the DLUR is capable of reporting this information and is configured to do so.