IRX0406E and REXX007E RC 20 using command XTSO under ISPF
Article ID: 36155
Updated On:
Products
Issue/Introduction
When entering SYSVIEW command XTSO under ISPF seeing messages:
IRX0406E REXX exec load file SYSEXEC does not contain exec member GSVXXTSO.
and/or
REXX007E GSVXXTSO failed, rc 20
This error was also seen when entering command IPUSER:
REXX exec load file SYSEXEC does not contain exec member GSVN0004.
The REXX exec cannot be interpreted.
The REXX exec cannot be loaded.
REXX exec load file SYSEXEC does not contain exec member GSVN0004.
The REXX exec cannot be interpreted.
The REXX exec cannot be loaded.
REXX exec load file SYSEXEC does not contain exec member GSVN0004.
The REXX exec cannot be interpreted.
The REXX exec cannot be loaded.
Cause
This has to do with the SYSVIEW CNM4BREX REXX data set, which must be available in the SYSEXEC DD concatentation.
If the sysview.CNM4BREX data set is not preallocated in the user's TSO logon proc, then SYSVIEW will attempt to dynamically add it to the SYSEXEC DD during session initialization of the ISPF or TSO interfaces. If a REXX exec that resides in the SYSEXEC DD is being used to invoke SYSVIEW, the attempt to concatenate CNM4BREX to the SYSEXEC DD will fail because SYSEXEC is open.
For one customer, the SYSVREXX exec used to get into SYSVIEW was in a library that was in the SYSEXEC concatenation. The solution was to move the SYSVREXX exec into a library in their SYSPROC concatenation.
Resolution
There are three different ways that could resolve this situation:
1. Add the SYSVIEW CNM4BREX data set to the SYSEXEC DD in the TSO logon procedure.
2. Invoke SYSVIEW via CLIST, as SYSEXEC would not be open and the dynamic concatenation will succeed.
3. Move the REXX exec being used to invoke SYSVIEW from a data set in the SYSEXEC DD concatenation to the SYSPROC DD concatenation.
Feedback
