Unsolved
This post is more than 5 years old
24 Posts
0
788
November 6th, 2008 12:00
Performance Essential - LSR / NSR info
What is an LSR/NSR non-transparency issue?
LSR (Local Shared Resources) and NSR (Non-Shared Resources) are different processing environments. Programs which process fine under NSR may experience problems under LSR. Under NSR when a second request would result in an exclusive control conflict, VSAM provides a copy of the record. While under LSR, VSAM issues a RPLRTNCD=x¿14¿. Under NSR when a second request would result in an addressing problem (the RBA of the next record would change), VSAM again provides a copy of the record. While under LSR, VSAM places the second string in a wait. In an online environment the wait would cause no problem as the second request would continue once the first is complete. In a batch environment the wait often results in a wait time out because the program is waiting on itself. When subtasking or multiple programs are involved these differences can also be seen as missing updates or missing records.
PSP can detect the RPLRTNCD=x¿14¿ and the 522 abend. When PSP detects a symptom of LSR/NSR transparency, PSP creates a control repository record forcing NSR using the jobname VRPLRC20. PSP does not interpret a cancelled job as having timed out. ENQUEUEs should be displayed and examined for jobs which appear to be running too long; and, if the job is waiting on itself, a control repository record forcing NSR should be created.
Attempts to circumvent the transparency problem by putting an open and close within the processing loop can encounter other processing errors such as CSV002I module xxxxx exceeded max use count and PSP1003I (xxxx) Error Loading Module. z/OS permits modules to be loaded 32K times; attempts to load modules more times than that result in messages PSP1003I and CSV002I. As part of getting control, PSP must load modules at open time. These problems will not be apparent unless sufficient opens and close are done to cause a module to be loaded more than 32K times.
The knowledgebase entry for LSR/NSR non-Transparency issues is
http://csgateway.emc.com/primus.asp?id=emc93376
The knowledgebase entry for messages PSP1003I and CSV002I is
http://csgateway.emc.com/primus.asp?id=emc81689
The Performance Essential User Guide has more detailed information on LSR/NSR non-Transparency issues: http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-001-877.pdf
Message was edited by:
The Benevolent Host S/W & Mainframe Forum Moderator
David Yates
LSR (Local Shared Resources) and NSR (Non-Shared Resources) are different processing environments. Programs which process fine under NSR may experience problems under LSR. Under NSR when a second request would result in an exclusive control conflict, VSAM provides a copy of the record. While under LSR, VSAM issues a RPLRTNCD=x¿14¿. Under NSR when a second request would result in an addressing problem (the RBA of the next record would change), VSAM again provides a copy of the record. While under LSR, VSAM places the second string in a wait. In an online environment the wait would cause no problem as the second request would continue once the first is complete. In a batch environment the wait often results in a wait time out because the program is waiting on itself. When subtasking or multiple programs are involved these differences can also be seen as missing updates or missing records.
PSP can detect the RPLRTNCD=x¿14¿ and the 522 abend. When PSP detects a symptom of LSR/NSR transparency, PSP creates a control repository record forcing NSR using the jobname VRPLRC20. PSP does not interpret a cancelled job as having timed out. ENQUEUEs should be displayed and examined for jobs which appear to be running too long; and, if the job is waiting on itself, a control repository record forcing NSR should be created.
Attempts to circumvent the transparency problem by putting an open and close within the processing loop can encounter other processing errors such as CSV002I module xxxxx exceeded max use count and PSP1003I (xxxx) Error Loading Module. z/OS permits modules to be loaded 32K times; attempts to load modules more times than that result in messages PSP1003I and CSV002I. As part of getting control, PSP must load modules at open time. These problems will not be apparent unless sufficient opens and close are done to cause a module to be loaded more than 32K times.
The knowledgebase entry for LSR/NSR non-Transparency issues is
http://csgateway.emc.com/primus.asp?id=emc93376
The knowledgebase entry for messages PSP1003I and CSV002I is
http://csgateway.emc.com/primus.asp?id=emc81689
The Performance Essential User Guide has more detailed information on LSR/NSR non-Transparency issues: http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-001-877.pdf
Message was edited by:
The Benevolent Host S/W & Mainframe Forum Moderator
David Yates
No Events found!