GVB119I ddname LSR SETUP ERROR RC=3 - USING NSR (R15 = 00000004)

Document ID : KB000017718
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

When executing a batch job you may have a job that does not fail but Hyperbuf will generate this message in the joblog.

GVB119I ddname LSR SETUP ERROR RC=3 - USING NSR (R15 = 00000004)

Solution:

When executing a batch job you may have a job that does not fail but Hyperbuf will generate this message in the joblog.

GVB119I ddname LSR SETUP ERROR RC=3 - USING NSR (R15 = 00000004)

This message is "informational" only and is advising the customer that a particular program could not process VSAM data from clusters moved to LSR (Local Shared Resources). Hypebrbuf automatically adjusted the LSR setting to NSR (Non-Shared Resources) setting to avoid job failure.

The manual references Hiperspace data failure. Under z/OS this is no longer the issue. Traditionally, this is an LSR vs NSR issue.

From the Hyperbuf Messages Guide and some notes for these messages to aid in ascertaining the correct diagnostic path

RC=1 Error in UPDTURP routine          Rarely occurs and should be reported to CA Technical Support
RC=2 DDE not found                            Rarely occurs and should be reported to CA Technical Support
RC=3 Hiperspace failure - Data component             User program unable to process data from a cluster that resides in an LSR space, auto change to NSR
RC=4 Hiperspace failure - Index Component           User program unable to process data from a cluster that resides in an LSR space, auto change to NSR