SYSVIEW | TRX Causes REXX SYSEXEC Error

Products

SYSVIEW Performance Management

Issue/Introduction

In the case observed, the site uses Tone Software TRX TSO Performance Manager (TRX); a "comprehensive TSO management solution that reduces TSO resource consumption, makes TSO more useful, and enhances TSO performance..." (Tone Software site). A TRX profile was not defined for SYSVIEW and the customer noticed the following error when accessing MENU NETWORK from the main SYSVIEW panel:

REXX exec load file SYSEXEC does not contain exec member GSVN0004.

The REXX exec cannot be interpreted.
The REXX exec cannot be loaded.
***

Upon entering the panel, the following warning is also observed before returning to the panel:

REXX007E GSVN0004 failed, rc 20

Review of CLIST

The suite calls SYSVIEW via the default supplied CLIST (SYSVCLIST)

Review of REXX Libraries

The SYSVIEW REXX libraries (CMN4BREX) are dynamically allocated via the SYSVIEW PROC SYSEXEC DD statements; both datasets are populated with the default install members, which does include the member GSVN0004 mentioned in the error:

Dsn-Site-REXXLIB                 SYSP.SYSVIEW.V16.ZOS25.SITE.CNM4BREX
Dsn-System-REXXLIB               SYSP.SYSVIEW.V16.ZOS25.CNM4BREX

Warning Message Observations

With the CLIST, the REXXLIB SYSEXEC DD datasets are being called/allocated dynamically when SYSVIEW is launched
The warning doesn't occur when TRX is told to allocate the SYSVIEW.CNM4BREX dataset to the user TSO profile

Review of the TRX.VIOLIB dataset identifies all SYSVIEW.CMN4BREX members but displays the text "NO DATA" next to it; potentially identifying issue pulling or reading the data:

SYSS E    SYSP.TRX.SK.VIOLIB
Name     Prompt   Lib    Size
. ACKCLR              -
. ADDTOGRP *No Data   -
. APIDIAG  *No Data   -
. APIDIAGI *No Data   -
. DASHBORD *No Data   -
. DLDELETE *No Data   -
. DLLIBV   *No Data   -
. DSATTR   *No Data   -
. FILELIST *No Data   -
...

Environment

Release: 17.0; 16.0; 15.0 -- All Supported Releases --

Component: SYSVIEW

Cause

The issue observed identifies the issue with TRX. It was identified the PROC starting the SYSVIEW application does allocate the CNM4BREX dataset; however, when a USER calls the SYSVIEW panels and attempts to interact, the CLIST/REXX SYSVCLST/SYSVREXX does not allocate the CNM4BREX dataset to the USER, resulting in the error and subsequent warning message.

Resolution

Top resolve, a SYSVIEW profile was created in TRX that allocates the proper SYSVIEW datasets when called by a USER, bypassing the calling of SYSVIEW via the SYSVREXX but instead from a custom profile in TRX.