GSVX737E after applying some of prevention PTFs

Products

• SYSVIEW Performance Management

Issue/Introduction

GSVX737E message after applying z/OS v2.5 compatible PTFs and their prerequisite PTFs

The customer applied z/OS v2.5 compliant PTFs and their prerequisite PTFs.
Subsequently, multiple GSVX737E messages were output.

GSVX737E (MAIN) XMDS req 0164 failed in ASID 00B0, rc 00000010 rs 00000018 ec 00000000 00000000
GSVX737E (MAIN) XMDS req 050D failed in ASID n/a, rc 00000010 rs 00000034 ec 00000000 00000000

GSVX894I (MAIN) Module update detected for GSVXXMDS, it will be reloaded in CSA

SYSVIEW itself starts up normally, the monitoring functions, etc. work normally, and there are no problems with the operation of the SYSVIEW screen.

Environment

Release : 16.0

Resolution

(1) When r16.0 is first run after the PTF is applied, the new functionality is called from the updated module GSVXXMDS.

(2) GSVXXMDS that has been in CSA since the previous run (no PTF applied) does not contain the functionality added by the PTF. Therefore, GSVX737E messages are output.

(3) Immediately after (2), GSVX894I is output and the updated GSVXXMDS is reloaded into CSA.
　Thus, the process proceeds normally thereafter.
　(The phenomenon occurs only once, and after the module is reloaded in CSA, the contents of CSA are automatically modified.)

(4) When r16.0 is stopped and started again, the updated GSVXXMDS is already in CSA and the error does not recur because it is the same module.

In addition, if r16.0 with PTF applied is started after IPL, there is no need to reload and the error does not occur because GSVXXMDS has not been loaded beforehand.