CA SYSVIEW Performance Management CA RS 1309 Service List

Transcription

1 CA SYSVIEW Performance Management CA RS 1309 Service List Description Hiper 13.7 RO54175 Correct CCI time outs and return code processing RO54429 VARIOUS PROBLEMS RELATED TO CA CHORUS R3 TSF RO56491 JJOBQUE/JOUTQUE/JHELDQUE No jobs displayed if PREFIX RO56990 JOBCLASS missing entries or Abend S0C4 U RO57184 JES3 long response time when displaying many jobs RO57212 ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS RO57260 MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS. RO57265 IMSRACT INCORRECT FIELDS FOR NON-FASTPATH REGION RO57318 ROSC011W Timeout waiting for ROSCOE job to respond RO57386 GSV2570E running installation conversion jobs RO57495 INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM RO57534 GSVC015I Message contains incorrect jobname RO57768 Profile conversion problem for several JES commands RO57923 U Abend, COMMON command looping RO58129 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58356 CSTATES SYSTEM command orphans storage RO58431 ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS RO58486 XMDR002W NRAS buffer max of 256K reached RO58501 MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E RO58543 JES SPOOL USED PERCENTAGE CALCULATED INCORRECTLY RO58589 IMS DLI variable totals display incorrectly greater than 2G RO58616 compatibility support for future XSYSTEM changes RO58670 IMSTRANS not showing USTOPPED status for transactions RO58800 Fields not populated in IMSIMTR transaction record DSECT RO59009 Display does not update properly when PREFIX values changed RO59084 IMTSQUE threshold not working for IMS shared queues RO59346 XSCONN command fails from ISPF interface RO59417 Abend S0F8-04 issuing LOGREC CLEAR subcommand RO59437 JOBNAME and SYSID ID Options return incorrect data RO59445 Abend S0C4 dumping address in PAGES or SEGMENTS display RO59628 LGCONN/LGJOBS cmds not showing data with IBM zaware RO59631 IMS Transaction missing from IMSTLOG RO59673 JCOPYOUT abend S / record length incorrect RO59735 PERFORMANCE IMPROVEMENT FOR IMSOVER COMMAND RO59843 ASLIST MAXUSER counts and %-ages do not add up RO59859 GSVX554E WHEN XSYS CMD W/ NOXSDATA BUT XSYSTEM IS DISABLED RO59920 CICSOPTS option MONITOR-RESTORE-SETTINGS handled incorrectly RO59976 Abend S0C4 in Data Collection or IMSLOCKS command RO60141 SELECT with CW and NW not supporting multiple operands RO60173 TSUMRATE always displays zeros in CSTATUS RO60200 IMSTLOG abended transactions not showing correct tran type RO60780 Possible looping in dependent region during shutdown **HIPER** RO61542 GSVX753I ALET ADD MESSAGE LOGGING ON W/RO61045 The CA RS 1309 service count for this release is 43

2 CA SYSVIEW Performance Management CA RS 1309 Service List Description Hiper 13.5 RO49066 GSVX031E & abend S306-0C when SCSQLOAD not APF auth'ed RO55670 CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd RO56326 Incorrect Parms passed to Trap & Capture for CICS threshold RO56427 JES3 JOBSUM command not returning all requested jobs RO56619 DEST command not working properly for JES3 RO56815 Incorrect Parms passed to OPSMVS when CICS threshold triggers RO57081 JOBCLASS missing entries RO57228 ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS RO57317 ROSC011W Timeout waiting for ROSCOE job to respond RO57473 INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM RO57542 GSVC015I Message contains incorrect jobname RO57739 GSV3650E/IXL013I IXLCONN request failed for CTSQUEUE cmd RO57926 U U0017 Abend, COMMON command looping RO58096 IMS DLI variable totals display incorrectly greater than 2G RO58130 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58296 ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS RO58350 MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS. RO58393 CSTATES SYSTEM command orphans storage RO58485 XMDR002W NRAS buffer max of 256K reached RO58500 compatibility support for future XSYSTEM changes RO58553 MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E RO58618 USTOPPED/PSTOPPED status handled incorrectly for IMS commands RO59143 Display does not update properly when PREFIX values changed RO59193 IMTSQUE threshold not working for IMS shared queues RO59416 Abend S0F8-04 issuing LOGREC CLEAR subcommand RO59427 XSCONN command fails from ISPF interface RO59438 JOBNAME and SYSID ID Options return incorrect data RO59526 IMS Transaction missing from IMSTLOG RO59674 JCOPYOUT abend S / record length incorrect RO59724 LGCONN/LGJOBS cmds not showing data with IBM zaware RO59842 ASLIST MAXUSER counts and %-ages do not add up RO59965 IMSTLOG abended transactions not showing correct tran type RO59975 Abend S0C4 in Data Collection or IMSLOCKS command RO60170 SELECT with CW and NW not supporting multiple operands RO60779 Possible looping in dependent region during shutdown **HIPER** RO60879 TSD5229 PROBLEMS WITH ALERT ACTIONS AND RELATED ONLINE HELP RO61838 Contain incorrect prereq PTF number W/RO60879 The CA RS 1309 service count for this release is 37

3 CA SYSVIEW Performance Management CA RS 1309 Service List Description Hiper 13.0 RO49909 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$ RO55354 CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd RO56428 JES3 JOBSUM command not returning all requested jobs RO56620 DEST command not working properly for JES3 RO57316 ROSC011W Timeout waiting for ROSCOE job to respond RO57998 U U0017 Abend, COMMON command looping RO58131 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58396 CSTATES SYSTEM command orphans storage RO58590 IMS DLI variable totals display incorrectly greater than 2G RO58676 USTOPPED/PSTOPPED status handled incorrectly for IMS commands RO58949 GSVX451E Abend S0C4-10 when issuing MIBWALK or MIBBROWSE cmd RO59168 Display does not update properly when PREFIX values changed RO59279 IMTSQUE threshold not working for IMS shared queues RO59390 ABEND S0C4-11 IN GSVPDB91 ISSUING IMSPSBS COMMAND RO59439 JOBNAME and SYSID ID Options return incorrect data RO59450 LGCONN/LGJOBS cmds not showing data with IBM zaware RO59562 ESRT014E ADD FAILED WHEN ATTEMPTING TO ADD AN EXTENDED SVC RO59974 Abend S0C4 in Data Collection or IMSLOCKS command RO60175 SELECT with CW and NW not supporting multiple operands RO60201 IMSTLOG abended transactions not showing correct tran type RO60387 Missing IMS transactions from IMS Connect RO60784 Possible looping in dependent region during shutdown **HIPER** The CA RS 1309 service count for this release is 22

4 CA SYSVIEW Performance Management CA RS 1309 Service List Description Hiper 12.7 RO49053 Loop in OUTPUT command followed by abend U RO50182 ABEND S0C7 GSVKSPAC issuing SPACE for EAV volumes RO53318 ROSC011W Timeout waiting for ROSCOE job to respond RO55668 CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd RO56235 IMS DLI variable totals display incorrectly greater than 2G RO56429 JES3 JOBSUM command not returning all requested jobs RO56621 DEST command not working properly for JES3 RO56828 ASRESUME command not working against an unquiesced job RO58006 U U0017 Abend, COMMON command looping RO58132 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58397 CSTATES SYSTEM command orphans storage RO58678 USTOPPED/PSTOPPED status handled incorrectly for IMS commands RO58978 GSVX451E Abend S0C4-10 when issuing MIBWALK and MIBBROWSE cmd RO59191 JES command display not updating properly when PREFIX changed RO59310 IMTSQUE threshold not working for IMS shared queues RO59440 JOBNAME and SYSID ID Options return incorrect data RO59973 Abend S0C4 in Data Collection or IMSLOCKS command RO60328 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$ The CA RS 1309 service count for this release is 18

5 CA SYSVIEW Performance Management 5 CA RS 1309 Service List for CNM4C70 FMID Service Description Hiper CNM4C70 RO49053 Loop in OUTPUT command followed by abend U RO50182 ABEND S0C7 GSVKSPAC issuing SPACE for EAV volumes RO53318 ROSC011W Timeout waiting for ROSCOE job to respond RO55668 CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd RO56235 IMS DLI variable totals display incorrectly greater than 2G RO56429 JES3 JOBSUM command not returning all requested jobs RO56621 DEST command not working properly for JES3 RO56828 ASRESUME command not working against an unquiesced job RO58006 U U0017 Abend, COMMON command looping RO58132 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58397 CSTATES SYSTEM command orphans storage RO58678 USTOPPED/PSTOPPED status handled incorrectly for IMS commands RO58978 GSVX451E Abend S0C4-10 when issuing MIBWALK and MIBBROWSE cmd RO59191 JES command display not updating properly when PREFIX changed RO59310 IMTSQUE threshold not working for IMS shared queues RO59440 JOBNAME and SYSID ID Options return incorrect data RO59973 Abend S0C4 in Data Collection or IMSLOCKS command RO60328 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$ The CA RS 1309 service count for this FMID is 18

6 CA SYSVIEW Performance Management 6 CA RS 1309 Service List for CNM4D00 FMID Service Description Hiper CNM4D00 RO49909 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$ RO55354 CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd RO56428 JES3 JOBSUM command not returning all requested jobs RO56620 DEST command not working properly for JES3 RO57316 ROSC011W Timeout waiting for ROSCOE job to respond RO57998 U U0017 Abend, COMMON command looping RO58131 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58396 CSTATES SYSTEM command orphans storage RO58590 IMS DLI variable totals display incorrectly greater than 2G RO58676 USTOPPED/PSTOPPED status handled incorrectly for IMS commands RO58949 GSVX451E Abend S0C4-10 when issuing MIBWALK or MIBBROWSE cmd RO59168 Display does not update properly when PREFIX values changed RO59279 IMTSQUE threshold not working for IMS shared queues RO59390 ABEND S0C4-11 IN GSVPDB91 ISSUING IMSPSBS COMMAND RO59439 JOBNAME and SYSID ID Options return incorrect data RO59450 LGCONN/LGJOBS cmds not showing data with IBM zaware RO59562 ESRT014E ADD FAILED WHEN ATTEMPTING TO ADD AN EXTENDED SVC RO59974 Abend S0C4 in Data Collection or IMSLOCKS command RO60175 SELECT with CW and NW not supporting multiple operands RO60201 IMSTLOG abended transactions not showing correct tran type RO60387 Missing IMS transactions from IMS Connect RO60784 Possible looping in dependent region during shutdown **HIPER** The CA RS 1309 service count for this FMID is 22

7 CA SYSVIEW Performance Management 7 CA RS 1309 Service List for CNM4D50 FMID Service Description Hiper CNM4D50 RO49066 GSVX031E & abend S306-0C when SCSQLOAD not APF auth'ed RO55670 CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd RO56326 Incorrect Parms passed to Trap & Capture for CICS threshold RO56427 JES3 JOBSUM command not returning all requested jobs RO56619 DEST command not working properly for JES3 RO56815 Incorrect Parms passed to OPSMVS when CICS threshold triggers RO57081 JOBCLASS missing entries RO57228 ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS RO57317 ROSC011W Timeout waiting for ROSCOE job to respond RO57473 INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM RO57542 GSVC015I Message contains incorrect jobname RO57739 GSV3650E/IXL013I IXLCONN request failed for CTSQUEUE cmd RO57926 U U0017 Abend, COMMON command looping RO58096 IMS DLI variable totals display incorrectly greater than 2G RO58130 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58296 ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS RO58350 MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS. RO58393 CSTATES SYSTEM command orphans storage RO58485 XMDR002W NRAS buffer max of 256K reached RO58500 compatibility support for future XSYSTEM changes RO58553 MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E RO58618 USTOPPED/PSTOPPED status handled incorrectly for IMS commands RO59143 Display does not update properly when PREFIX values changed RO59193 IMTSQUE threshold not working for IMS shared queues RO59416 Abend S0F8-04 issuing LOGREC CLEAR subcommand RO59427 XSCONN command fails from ISPF interface RO59438 JOBNAME and SYSID ID Options return incorrect data RO59526 IMS Transaction missing from IMSTLOG RO59674 JCOPYOUT abend S / record length incorrect RO59724 LGCONN/LGJOBS cmds not showing data with IBM zaware RO59842 ASLIST MAXUSER counts and %-ages do not add up RO59965 IMSTLOG abended transactions not showing correct tran type RO59975 Abend S0C4 in Data Collection or IMSLOCKS command RO60170 SELECT with CW and NW not supporting multiple operands RO60779 Possible looping in dependent region during shutdown **HIPER** RO60879 TSD5229 PROBLEMS WITH ALERT ACTIONS AND RELATED ONLINE HELP RO61838 Contain incorrect prereq PTF number W/RO60879 The CA RS 1309 service count for this FMID is 37

8 CA SYSVIEW Performance Management 8 CA RS 1309 Service List for CNM4D70 FMID Service Description Hiper CNM4D70 RO54175 Correct CCI time outs and return code processing RO54429 VARIOUS PROBLEMS RELATED TO CA CHORUS R3 TSF RO56491 JJOBQUE/JOUTQUE/JHELDQUE No jobs displayed if PREFIX RO56990 JOBCLASS missing entries or Abend S0C4 U RO57184 JES3 long response time when displaying many jobs RO57212 ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS RO57260 MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS. RO57265 IMSRACT INCORRECT FIELDS FOR NON-FASTPATH REGION RO57318 ROSC011W Timeout waiting for ROSCOE job to respond RO57386 GSV2570E running installation conversion jobs RO57495 INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM RO57534 GSVC015I Message contains incorrect jobname RO57768 Profile conversion problem for several JES commands RO57923 U Abend, COMMON command looping RO58129 AUDIT/IMS reports and FROM/TO commands showing wrong times RO58356 CSTATES SYSTEM command orphans storage RO58431 ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS RO58486 XMDR002W NRAS buffer max of 256K reached RO58501 MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E RO58543 JES SPOOL USED PERCENTAGE CALCULATED INCORRECTLY RO58589 IMS DLI variable totals display incorrectly greater than 2G RO58616 compatibility support for future XSYSTEM changes RO58670 IMSTRANS not showing USTOPPED status for transactions RO58800 Fields not populated in IMSIMTR transaction record DSECT RO59009 Display does not update properly when PREFIX values changed RO59084 IMTSQUE threshold not working for IMS shared queues RO59346 XSCONN command fails from ISPF interface RO59417 Abend S0F8-04 issuing LOGREC CLEAR subcommand RO59437 JOBNAME and SYSID ID Options return incorrect data RO59445 Abend S0C4 dumping address in PAGES or SEGMENTS display RO59628 LGCONN/LGJOBS cmds not showing data with IBM zaware RO59631 IMS Transaction missing from IMSTLOG RO59673 JCOPYOUT abend S / record length incorrect RO59735 PERFORMANCE IMPROVEMENT FOR IMSOVER COMMAND RO59843 ASLIST MAXUSER counts and %-ages do not add up RO59859 GSVX554E WHEN XSYS CMD W/ NOXSDATA BUT XSYSTEM IS DISABLED RO59920 CICSOPTS option MONITOR-RESTORE-SETTINGS handled incorrectly RO59976 Abend S0C4 in Data Collection or IMSLOCKS command RO60141 SELECT with CW and NW not supporting multiple operands RO60173 TSUMRATE always displays zeros in CSTATUS RO60200 IMSTLOG abended transactions not showing correct tran type RO60780 Possible looping in dependent region during shutdown **HIPER** RO61542 GSVX753I ALET ADD MESSAGE LOGGING ON W/RO61045 The CA RS 1309 service count for this FMID is 43

9 CA SYSVIEW Performance Management CA RS PTF RO RO54175 RO54175 M.C.S. ENTRIES = ++PTF(RO54175) DESC(Correct CCI time outs and return code processing) When a CCI timeout occurs it can result in an incorrect message being produced. Along with the incorrect messaging it was found that return codes and reason codes from CCI were being incorrectly formatted resulting in both bad codes and bad descriptions. This problem can be seen when problems are encountered with applications using the XAPI interface like CA CE APM (Wily) or CA VANTAGE GMI. As an example, CCI timeout errors would show "com.ca.sysview.xapi.xapignrlnocapturefeature" instead of "com.ca.sysview.xapi.xapignrlrequesttimeout". The error messages would be seen in the effected applications log. Following are two messages showing the current incorrect message followed by the correct messages: 01/15/ :56:42 544BC D4AC8 C 001/000-FDBKError GSV3516E send_request: CCI Error R=8 RC= XRC= descr= ND 01/15/ :56:43 544BC D 001/000-GSV_InitReq GSV3590I Exit Exception=2235 CCI Error: R=8 RC= XRC = Descr= ND The correct messages would appear as: 01/15/ :54:13 516EA D4AC8 C 001/000-FDBKError GSV3516E send_request: CCI Error R=8 RC= XRC= descr=receiver NOT FOUND 01/15/ :54:13 516EA D 001/000-GSV_InitReq GSV3590I Exit Exception=2235: CCI Error R=8 RC= XRC = descr=receiver NOT FOUND Incorrect codes and descriptions causing delays in diagnosing the root problems. CA SYSVIEW r VER(Z038) FMID(CNM4D70) SUP(TSD7034).

10 CA SYSVIEW Performance Management CA RS PTF RO RO54429 RO54429 M.C.S. ENTRIES = ++PTF(RO54429) DESC(VARIOUS PROBLEMS RELATED TO CA CHORUS R3 TSF) This addresses several problems related to the SYSVIEW integration with CA Chorus r3 and Time Series Facility (TSF). 1. IMS and/or WebSphere MQ metric resource data may be sent to TSF for an IMS or MQ queue manager for which it was not requested, resulting in errors in the SYSVIEW STC. 2. The SYSVIEW CICS Option data collection metric TDATTIME is not defined correctly making it unable to be sent to TSF. 3. The SYSVIEW CICS Option GSVCTSFT subtask is not performing lookups of TSF-eligible data collection metrics as efficiently as it could. 4. The online help for the TSFLOGR command was missing data fields TCPData and TCPMetrics. 5. The common storage tracking/usage data returned to Chorus is in a detailed format rather than a summary version. The $CHXAPI profile in SYSVIEW specifies OPTIONS DETAIL rather than OPTIONS SUMMARY for the VSMTRACK command. 6. Variables that had a collected value of zero for the collection interval were not being sent to TSF. 7. Values for the CPUPLPAR variable for all processors were being added into the IIP processor collection bucket in the TSF database. This fix is also providing an updated SYSVTSF dashboard and help, a new CHORUS dashboard, as well as two additional diagnostic capture members DIAGCHOR and DIAGTSF. 1. Error messages similar to the following may be observed. In the SYSVIEW STC joblog: GSVX998E (TSFMQS) TCP$004E EZASMI TYPE=WRITE failed, Connection is broken GSVX998I (TSFMQS) TCP$006I Socket closed 0 GSVX998I (TSFMQS) TCP$031I Connection established. IPVersion IPV4 Port Socket 0 Address LOCALHOST GSVX998E (TSFIMS) TCP$004E EZASMI TYPE=READ failed, ECONNRESET GSVX998I (TSFIMS) TCP$006I Socket closed 0 GSVX998I (TSFIMS) TCP$031I Connection established. IPVersion IPV4 Port Socket 0 Address LOCALHOST In the LISTLOG for the TSFIMS and/or TSFMQS logger tasks: GSV4133E GSVXTSFS GETACK GETA9020 RC= 0024 GSV4133E GSVXTSFS ENDPD ENDP9012 GSV4133E GSVXTSFS STARTPD STPD9004 TCP$004E EZASMI TYPE=READ failed, ECONNRESET GSV4133E GSVXTSFS GETACK GETA9004 GSV4133E GSVXTSFS ENDPD ENDP9012 GSV4133E GSVXTSFS STARTPD STPD9004 TCP$004E EZASMI TYPE=WRITE failed, Connection is broken GSV4133E GSVXTSFS ENDPD ENDP9008 In the TSF STC LOG1 DD if tracing is turned on in TSF: ETJTS206W TSF PDAPI protocol violation: SetEKey entity level violation, current level 2 new level 4 (entity 7 QUEUE) ( ) 2. CICS data collection metric TDATTIME will not be sent to TSF. 3. The SYSVIEW CICS subtask GSVCTSFT may use more CPU than necessary. 4. No help available for the TCPData and TCPMetrics fields on the TSFLOGR command display. 5. The following errors may appear in the Investigator UI and/or the Chorus server log file server.log: ETJSV008E XAPI Error occurred ETJSV016E Request field with key: 15 not returned from SYSVIEW 6. When viewing variable graphs in the Investigator UI there may be gaps in the graph due to the missing zero values. 7. Very large values show for the CPUPLPAR variable of type IIP in the Investigator UI. Unnecessary errors, CPU usage, and missing help.

11 CA SYSVIEW Performance Management CA RS PTF RO54429 CA SYSVIEW r VER(Z038) FMID(CNM4D70) SUP(RO52684 TSD7041). ++HOLD(RO54429) FMID(CNM4D70) SYSTEM REASON(RESTART) DATE(13024) COMMENT( Apply this fix and either recycle the CICS region, or use the GSVT (terminate) and GSVS (start) transactions to recycle SYSVIEW/CICS within the CICS region. Also recycle SYSVIEW. ).

12 CA SYSVIEW Performance Management CA RS PTF RO RO56491 RO56491 M.C.S. ENTRIES = ++PTF(RO56491) DESC(JJOBQUE/JOUTQUE/JHELDQUE No jobs displayed if PREFIX) If a PREFIX or OWNER value is defined and no parameters are entered with the JOUTQUE or JJOBQUE commands, no jobs are displayed. If a PREFIX or OWNER value is defined and no parameters are entered on the JHELDQUE command, it is possible that no jobs will be displayed. If output classes are specified with the JHELDQUE command that cause no jobs to be displayed, and then the JHELDQUE command is entered from the JHELDQUE display with no parameters, no jobs will be displayed. The output classes entered with the previous JHELDQUE command were not being cleared. On a JES3 system, JHELDQUE, JOUTQUE, or JJOBQUE commands will encounter S0C4-04 abend when issued for an unsupported version of JES3 such as 1.12 and lower. No jobs are displayed for JOUTQUE, JJOBQUE, or JHELDQUE when PREFIX or OWNER value is defined and the command is issued without a parameter. In JES3 system: Messages similar to the following appear in SYSVUSER joblog: GSVX451E Abend S0C4-04 in JJOBQUE command GSVX452I SYSVIEW SRB in control at entry to abend GSVX453I Diagnostics for SRB in control at entry to abend GSVX457I Psw 078C0001 8B33946E Ilc 6 Intc 04 GSVX477I Key 8 State SUP Am 64 Asc PRI GSVX458I Module GSVXNUC Addr 0AF13000 Offset E GSVX458I NucMod GSVXFLDR Addr 0B335A88 Offset E6 GSVX450I FixLvl BASE GSVX473I Routne FMDT$$ Addr 0B3391E8 Offset GSVX459I Data at PSW addr 0B GSVX460I D B CA7F4 GSVX455I General registers at entry to abend GSVX467I R0-R _ _ GSVX467I R2-R _ _0B33E4D8 GSVX467I R4-R _ _ GSVX467I R6-R _ _0BB6C000 GSVX467I R8-R _0BC0D _0BBC4B10 GSVX467I R10-R _0B33E0C _0BB64000 GSVX467I R12-R _0B3391E _0BB72C48 GSVX467I R14-R _0B _ GSVX475I Access registers at entry to abend GSVX461I AR0-AR3 007D65C GSVX461I AR4-AR GSVX461I AR8-AR GSVX461I AR12-AR Unable to monitor jobs with LISTJOBS or LISTHELD commands. S0C4-04 abend for JES3 system. Issue JOUTQUE, JJOBQUE, or JHELDQUE command with parameter(s). CA SYSVIEW r VER(Z038) FMID(CNM4D70) PRE(RO55171) SUP(TSD7078).

13 CA SYSVIEW Performance Management CA RS PTF RO RO56990 RO56990 M.C.S. ENTRIES = ++PTF(RO56990) DESC(JOBCLASS missing entries or Abend S0C4 U ) The JOBCLASS command may not display all job classes in 13.5 and Modifying field(s) in JOBCLASS display may cause S0C4 or U abend in Job class missing on the JOBCLASS command display in 13.5 and S0C4 or U abend when modifying field(s) in JOBCLASS display in Missing job class in 13.5 and S0C4 or U abend in CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7081).

14 CA SYSVIEW Performance Management CA RS PTF RO RO57184 RO57184 M.C.S. ENTRIES = ++PTF(RO57184) DESC(JES3 long response time when displaying many jobs) In JES3 environments, the following command displays may experience long response times when displaying a relatively large number of jobs: JHELDQUE, JJOBBQUE, JOBSUM, JOUTQUE This problem will only occur when running SYSVIEW in a JES3 environment. In addition, this problem will only occur when issuing the commands listed above with either the subcommand OPTIONS DETAIL in effect, or with the DETAIL command parameter in effect. When viewing a relatively large number of jobs on JES3 spool, the command response time can be much longer than expected. In observed instances, response times were as long as several minutes. This problem becomes more apparent as the number of jobs returned for viewing increases. Long response times are most evident when using PREFIX and/or masking characters to return many jobs. Unable to view detailed information on a relatively large number of jobs without long command response times. Issue the affected command displays with the subcommand OPTIONS NODETAIL in effect, or with the NODETAIL command parameter. CA SYSVIEW VER(Z038) FMID(CNM4D70) PRE(RO52865 RO52953) SUP(TSD7082). ++HOLD(TSD7082) FMID(CNM4D70) SYSTEM REASON(ENH) DATE(13095) COMMENT( This fix enables the JOBS task, which runs in the SYSVIEW main address space, when SYSVIEW is running in a JES3 environment. This was previously enabled only when the SYSVIEW main address space was running in a JES2 environment. The JOBS task improves command response time when viewing a relatively large number of jobs on spool. It is not a requirement to run the JOBS task, but command response time may be longer than desired without it for the following commands: JHELDQUE, JJOBBQUE, JOBSUM, JOUTQUE By default, the SYSVIEW parmlib member is configured to start the JOBS task when the SYSVIEW main address space is started with the following parameter: START JOBS,INTERVAL=30 Start JOBS task */ To enable the JOBS task when the SYSVIEW main address space is started, ensure the parameter above is not commented out and is above the logical EOF in the SYSVIEW parmlib member. After the fix has been applied and the contents of the SYSVIEW parmlib member have been verified, restart the SYSVIEW main address space. ).

15 CA SYSVIEW Performance Management CA RS PTF RO RO57212 RO57212 M.C.S. ENTRIES = ++PTF(RO57212) DESC(ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS) Abend S0C4-3B can occur in SYSVIEW/CICS module GSVCMSCR due to the high halves of 64-bit registers not being restored. Abend messages similar to the following appear in the CICS job log: GSVC990E (TPPT) CA SYSVIEW for CICS r13.7 Abend information GSVC991E (TPPT) Task GSVCTPPT Module GSVCMSCR Offset GSVC992E (TPPT) Abend S0C4 PSW 078C3001 A Ilc 4 Intc 3B GSVC996E (TPPT) Registers at entry to abend GSVC995E (TPPT) AR/GR 00: _ : / _24FB8698 GSVC995E (TPPT) AR/GR 02: _24CBDB30 03: / _24CBD038 GSVC995E (TPPT) AR/GR 04: _ : / _ GSVC995E (TPPT) AR/GR 06: _24B243B4 07: / _40E7BBE0 GSVC995E (TPPT) AR/GR 08: _24B2C768 09: / _24C7B000 GSVC995E (TPPT) AR/GR 10: _ : / _ GSVC995E (TPPT) AR/GR 12: _24FB : / _ GSVC995E (TPPT) AR/GR 14: _ : / _ GSVC998E (TPPT) End of symptom dump A dump is taken and the subtask that incurred the abend (GSVCTPPT in the reported case) restarts. CA SYSVIEW r VER(Z038) FMID(CNM4D70) SUP(TSD7083). ++HOLD(RO57212) FMID(CNM4D70) SYSTEM REASON(RESTART) DATE(13095) COMMENT( Apply this fix and either recycle the CICS region, or use the GSVT (terminate) and GSVS (start) transactions to recycle SYSVIEW/CICS within the CICS region. ).

16 CA SYSVIEW Performance Management CA RS PTF RO RO57260 RO57260 M.C.S. ENTRIES = ++PTF(RO57260) DESC(MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS.) When a connection can not be made to a WebSphere MQ queue manager, there may be an excessive amount of 'GSVX702I connecting' errors followed by 'GSVX998E failed' error messages which are issued from the MQSDATA subtask during every data collection interval. Numerous GSVX702I and GSVX998E (MQSDATA) messages issued when SYSVIEW MQ data collector is unable to connect to a WebSphere MQ queue manager. The message may look similar to the following: GSVX702I (MQSDATA) WebSphere MQ monitoring for Qmgr???? connecting GSVX998E (MQSDATA) MQSR002E???? MQCONN failed, Excessive amount of error messages issued to the console. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7084) PRE(RO55339). ++HOLD(RO57260) FMID(CNM4D70) SYSTEM REASON(ENH) DATE(13141) COMMENT( The following new option and default value being added to the MQSDATA parmlib member: QMGR-ERROR-NOTIFY-INTERVAL 00:02:00 The option allows for extending the time between GSVX998E messages when a WebSphere MQ queue manager can not connect. Currently the GSVX998E is issued several times each minute for each queue manager. GSVX702I (MQSDATA) WebSphere MQ monitoring for Qmgr???? connecting GSVX998E (MQSDATA) MQSR002E???? MQCONN failed, The default value will be 2 minutes and may be adjusted as necessary. ).

17 CA SYSVIEW Performance Management CA RS PTF RO RO57265 RO57265 M.C.S. ENTRIES = ++PTF(RO57265) DESC(IMSRACT INCORRECT FIELDS FOR NON-FASTPATH REGION) Several fields on the IMSRACT display, which is invoked by issuing the Select line command from the IMSREGNS command display, may be blank or contain garbage for non-fast Path IMS regions. Additionally, the Database Status section on IMSRACT only shows the address of the SSA (Segment Search Argument) and IO Area (DB record area), so this is being enhanced to also include a partial dump of the real time data for each of these areas. The following fields on the IMSRACT display may be blank or contain garbage for non-fast Path IMS regions: Region Type Last Call DB Record Last Status Incorrect data may hinder debugging efforts. CA SYSVIEW r VER(Z038) FMID(CNM4D70) PRE(RO53671) SUP(TSD7085). ++HOLD(RO57265) FMID(CNM4D70) SYSTEM REASON(ENH) DATE(13098) COMMENT( The format of the IMSRACT display is being enhanced to include a partial dump of the SSA and I/O areas, which will result in the reorganization of a few existing fields in the Database Status section. ).

18 CA SYSVIEW Performance Management CA RS PTF RO RO57318 RO57318 M.C.S. ENTRIES = ++PTF(RO57318) DESC(ROSC011W Timeout waiting for ROSCOE job to respond) The ROSACT command produces the following error message: ROSC011W Timeout waiting for ROSCOE job jjjjjjjj to respond The ROSACT command, which displays information about wait conditions and CPU activity for logged on users, does not function correctly. Instead, it waits for whatever interval is defined or defaulted to (usually 60 seconds) and then issues message: ROSC011W Timeout waiting for ROSCOE job jjjjjjjj to respond Unable to determine: - Which users are logged on to ROSCOE. - Which users logged on to ROSCOE are waiting. - Which users logged on to ROSCOE are consuming CPU. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7086). ++HOLD(RO57318) FMID(CNM4D70) SYSTEM REASON(RESTART) DATE(13099) COMMENT( Apply this fix and either recycle the ROSCOE region, or use the GSV STOP (terminate monitoring) and GSV START (start monitoring) transactions to recycle SYSVIEW/ROSCOE within the ROSCOE region. ).

19 CA SYSVIEW Performance Management CA RS PTF RO RO57386 RO57386 M.C.S. ENTRIES = ++PTF(RO57386) DESC(GSV2570E running installation conversion jobs) Running the Security Conversion, INST0050, or the Profile Conversion, INST0051, installation jobs may result in an error which causes the conversion to fail. This problem will only occur if all of the following conditions are true: The Security Conversion or the Profile Conversion is used to convert a prior release configuration. Neither the SYSVIEW main address space nor the SYSVIEW user address for SYSVIEW 13.5 or SYSVIEW 13.7 have been started on the LPAR where the conversion job is being run. The Dynamic Install program, GSVXINST, which is part of install step INST0100 and included in the SYSVIEW/SYSVUSER PROC by default, has not been run for SYSVIEW 13.5 or SYSVIEW 13.7 on the LPAR where the conversion job is being run. The following error message is generated in the output of the Security Conversion, INST0050, or the Profile Conversion, INST0051: GSV2570E SVC processing failed, SGAT block not found or invalid Unable to run the Security Conversion or the Profile Conversion without an error. Run the Dynamic Install, INST0100, or start either the SYSVIEW or the SYSVUSER address space for SYSVIEW 13.5 or SYSVIEW CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7087).

20 CA SYSVIEW Performance Management CA RS PTF RO RO57495 RO57495 M.C.S. ENTRIES = ++PTF(RO57495) DESC(INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM) New CICS configuration option PERFORMANCE-DATA-SEGLIMIT-DB2 was introduced in the CICSOPTS parmlib member in SYSVIEW It's purpose was to reduce collection overhead involved in searching and maintaining possibly very long lists of DB2 calls made by a transaction. This option defaults to collecting 25 unique DB2 segments, and can be increased to collect 100 segments. Some customers feel the maximum limit of 100 segments can curtail debugging efforts, so the maximum limit is being increased to This limit typically only matters if configuration option PERFORMANCE-DATA-DB2-BY-PROGRAM is set to YES. Once the PERFORMANCE-DATA-SEGLIMIT-DB2 value has been reached, all additional unique DB2 calls will be collected in a generic segment with a Program and Statement Type of *. Reduced DB2 program call details may hinder debugging efforts. CA SYSVIEW VER(Z038) FMID(CNM4D70) PRE(RO56237) SUP(TSD7088). ++HOLD(RO57495) FMID(CNM4D70) SYSTEM REASON(ENH) DATE(13102) COMMENT( This fix increases the maximum allowed value on the PERFORMANCE-DATA-SEGLIMIT-DB2 configuration option in the CICSOPTS parmlib member to Apply this fix and either recycle the CICS region, or use the GSVT (terminate) and GSVS (start) transactions to recycle SYSVIEW/CICS within the CICS region. ).

21 CA SYSVIEW Performance Management CA RS PTF RO RO57534 RO57534 M.C.S. ENTRIES = ++PTF(RO57534) DESC(GSVC015I Message contains incorrect jobname) Message GSVC015I in CICS JOBLOG displayed incorrect Jobname. Message GSVC015I displayed CICS's job name instead of the jobname of the connected CICSLOGR, which is typically SYSVIEW. Incorrect Jobname displayed. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7089). ++HOLD(TSD7089) FMID(CNM4D70) SYSTEM REASON(ACTION) DATE(13102) COMMENT( Apply this fix and either recycle the CICS region, or use the GSVT (terminate) and GSVS (start) transactions to recycle SYSVIEW/CICS within the CICS region. ).

22 CA SYSVIEW Performance Management CA RS PTF RO RO57768 RO57768 M.C.S. ENTRIES = ++PTF(RO57768) DESC(Profile conversion problem for several JES commands) Several fields were renamed on the JJOBQUE, JHELDQUE and JOUTQUE command displays in The profile conversion (install job INST0051) attempts to rename these fields automatically if they exist in any user-defined display Formats for these commands but fell short; in some cases the old field names still existed in the converted profile and caused errors on these displays. The SPOOLS command was also renamed to JSPOOLS in 13.7, and any display Formats for the SPOOLS command in the prior release were not converted properly. The conversion problem may occur for the following renamed data fields for the JJOBQUE, JHELDQUE, and JOUTQUE commands: New Field Old Field Account Acct InpCnt Cards Flash Flsh InpSys Isys MsgClass Mc ASys Osys InpDate Rdr-Date InpTime Rdr-Time TotPages Tot-Pges The following error messages will appear when these commands are entered If the old field names were not converted to the new names: SELE003E Field 'oldname' not found SORT017E Field 'oldname' not found Unable to successfully convert profiles for these JES commands. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7091).

23 CA SYSVIEW Performance Management CA RS PTF RO RO57923 RO57923 M.C.S. ENTRIES = ++PTF(RO57923) DESC(U Abend, COMMON command looping) The COMMON command encountered error and continue to loop until exceeded the CPU time limit which caused user address space to abend with the following code: Release AbendCode ReasonCode 12.7 U U U U The COMMON command U Abended and the LISTLOG showed a loop where the following error got issued then COMMON got executed again: GSVX078E Error occurred scanning VSM control blocks, SQA data is incomplete User session terminates with U abend. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7093).

24 CA SYSVIEW Performance Management CA RS PTF RO RO58129 RO58129 M.C.S. ENTRIES = ++PTF(RO58129) DESC(AUDIT/IMS reports and FROM/TO commands showing wrong times) Two problems exist related to timestamps and intervals of records returned on reports: 1. Running a report may result in incorrect timestamps on the returned report data. Specifically, the timestamps on a report are shifted by the local time zone offset from GMT. This problem occurs only for SYSVIEW AUDIT reports and SYSVIEW IMS transaction reports. 2. Running a report using relative dates and times with the FROM and TO commands may result in records being falsely included or excluded from a report. For example: FROM -1 DAYS AT 00:00:00 TO -1 DAYS AT 23:59:59 1. Running a SYSVIEW AUDIT report or a SYSVIEW IMS transaction report results in the returned report data being shifted by the local time zone offset from GMT. For example, a SYSVIEW IMS transaction record that was created at 09:00 (GMT-4) will be displayed on the report with a timestamp of 05:00 (GMT-8). 2. When using the relative date and time format on a FROM or TO command some records may be falsely included or excluded. Specifically, the FROM command incorrectly includes records that were written up to the current number of leap seconds before the specified time value. The TO command incorrectly excludes records that were written up to the current number of leap seconds before the specified time value. 1. Unable to run a SYSVIEW AUDIT report or a SYSVIEW IMS report with accurate timestamps. 2. Unable to obtain a specific range of records with the FROM and TO commands Specify both the FROM and TO commands with a time that is later by the current number of leap seconds. The following example will return records from 00:00:00 to 23:59:59 of the previous day, assuming a leap second offset of 25 seconds: FROM -1 DAYS AT 00:00:25 TO -0 DAYS AT 00:00:24 CA EXPLORE Report Writer VER(Z038) FMID(CNM4D70) PRE(RO56233) SUP(TSD7094).

25 CA SYSVIEW Performance Management CA RS PTF RO RO58356 RO58356 M.C.S. ENTRIES = ++PTF(RO58356) DESC(CSTATES SYSTEM command orphans storage) Issuing the CSTATES SYSTEM command can causes memory leaks, where duplicate buffers of data are being created with only one getting freed. An error message similar to the following can be observed in the user's joblog when the allowed memory usage for the SYSVIEW user's session has been exceeded: GSV2574E Storage limit of 32M exceeded, new level creation not allowed. Unable to allocate any additional private storage when the storage limit is exceeded. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7096).

26 CA SYSVIEW Performance Management CA RS PTF RO RO58431 RO58431 M.C.S. ENTRIES = ++PTF(RO58431) DESC(ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS) Abend S0C4 is possible in any address space making WebSphere MQ requests if parameter MONITOR-MQS-REQUESTS is set to YES in the MQSDATA parmlib member. The abend occurs in module GSVSHnnn, where nnn = the MQ version (GSVSH600, GSVSH700, GSVSH710). This specific problem was related to an incorrect handle specified on an MQ request. The MQRSTAT command display will show a value of ABENDED in the Status field for the queue manager, and no new request statistics will be reflected on the display. The MQRSUMM command fails with message: MQSR178W No monitored qmgr found The MQRTRACE command fails with message: MQSR176E Request monitoring not active for qmgr In the reported case the MQ request being monitored by SYSVIEW came from a CICS region, so there was a LOGREC record for the CICS job showing abend S0C4 with the PSW pointing to SYSVIEW module GSVSH700 residing in E-CSA. No further monitoring of MQ requests will be performed. Specify MONITOR-MQS-REQUESTS NO in the MQSDATA parmlib member to disable MQ request monitoring. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7097).

27 CA SYSVIEW Performance Management CA RS PTF RO RO58486 RO58486 M.C.S. ENTRIES = ++PTF(RO58486) DESC(XMDR002W NRAS buffer max of 256K reached) When issuing the ASLIST or ASLOST command it is possible the command may produce error messages indicating the 256K buffer max has been reached. In the reported incident ASLIST was being issued via DASHBOARD OVERVIEW which internally issues an ASLIST command similar to the following: RXDISP UNIQFLDS TYPE 'ASLIST : SELECT TYPE NB' When the above command was issued, it invoked the UNIQFLDS REXX execute in SYSVIEW.CNM4BREX(UNIQFLDS). If the total number of address spaces on the ASLIST or ASLOST command exceeded the NRAS buffer max of 256K, then message XMDR002W would be issued. XMDR002W NRAS buffer max of 256K reached for ASID #### job???????? No results produced by command. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7098) PRE(RO52763). ++HOLD(RO58486) FMID(CNM4D70) SYSTEM REASON(DYNACT) DATE(13161) COMMENT( This fix must either be implemented via an IPL, since module GSVXXMDS resides in E-CSA, or the following steps can be followed to implement it dynamically. Using the dynamic method will cause a small amount of E-CSA to be orphaned. 1. Apply the fix. 2. Recycle the SYSVIEW STC's, GSSA, and any user sessions. 3. Enter command "NEWCOPY XMDS" from a SYSVIEW session. ).

28 CA SYSVIEW Performance Management CA RS PTF RO RO58501 RO58501 M.C.S. ENTRIES = ++PTF(RO58501) DESC(MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E) A timing-related issue exists during the startup of SYSVIEW and SYSVUSER, where it is possible for user sessions to erroneously think the SYSVIEW STC is not active. In the reported case both SYSVIEW and SYSVUSER were started independently during the IPL process. Once they initialized and a user logged on via the VTAM interface, the main menu showed the following in the Information line: Main Services INACTIVE User Interface ACTIVE The following error message was received when entering commands such as ACTSUM which display data collected by a data collection task that executes in the SYSVIEW STC: GSVX340E Unable to connect to the data store MSDC Unable to execute functions that require the Main Services (SYSVIEW) address space. Use the STARTCMD parmlib member to have SYSVIEW issue the START SYSVUSER command to remove the timing issue. If the problem has already occurred a recycle of both STCs should clear it up. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7099).

29 CA SYSVIEW Performance Management CA RS PTF RO RO58543 RO58543 M.C.S. ENTRIES = ++PTF(RO58543) DESC(JES SPOOL USED PERCENTAGE CALCULATED INCORRECTLY) The SPOOL space used percent was not being calculated correctly. It was including INACTIVE spool volumes in the calculation. Incorrect SPOOL space used percentage shown on JSPOOLS, JRESOURC, and SYSTEMS command displays. Incorrect used SPOOL percentage shown. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7100) PRE(RO56990).

30 CA SYSVIEW Performance Management CA RS PTF RO RO58589 RO58589 M.C.S. ENTRIES = ++PTF(RO58589) DESC(IMS DLI variable totals display incorrectly greater than 2G) Certain IMS DLI variables (SMF type 255 subtype 33 & 35 records) displayed by Report Writer may be inaccurate. This problem occurs when the accumulated totals exceed a value of 2,147,483,647 (2G-1) The problem can occur when the following IMS DLI variables are defined in the report control cards: IMS SUM DLI DB-READS - Number of DL/I database reads IMS SUM DLI DB-WRITES - Number of DL/I database writes IMS SUM DLI DB-CALLS - Number of DL/I database requests IMS SUM DLI TOTALIO - Total number VSAM+OSAM DL/I I/O operations Unable to accurately display IMS DLI variable metrics when the total values exceed 2,147,483,647 (2G-1). CA EXPLORE Report Writer VER(Z038) FMID(CNM4D70) PRE(RO55807,RO56233) SUP(TSD7101).

31 CA SYSVIEW Performance Management CA RS PTF RO RO58616 RO58616 M.C.S. ENTRIES = ++PTF(RO58616) DESC(compatibility support for future XSYSTEM changes) During cross system commands, the receiving system validates the data by checking it's identifier and length. If the identifier or length was not equal to what was expected then the data is considered invalid. This change modifies the validation procedure from an exact comparison to a check against a minimum length. To allow for future changes to the format of the returned data. When SYSVIEW requests cross-system data from a future release of SYSVIEW beyond 13.7, it could be possible for the command display to be missing data from the target system or show an error. Possibly unable to gather cross-system data between mixed releases of SYSVIEW. CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7102).

32 CA SYSVIEW Performance Management CA RS PTF RO RO58670 RO58670 M.C.S. ENTRIES = ++PTF(RO58670) DESC(IMSTRANS not showing USTOPPED status for transactions) This fix will address the following IMS problems: 1. The IMSTRANS command display is not showing a USTOPPED/PSTOPPED status for transactions that are in the USTOPPED/PSTOPPED state. 2. The PSTOPPED and USTOPPED IMS exception alerts are not being triggered for the IMTSSTOP state exceptions. 3. The PTran column on the IMSOVER display is not counting any USTOPPED transactions. The "USTOPPED" or "PSTOPPED" state is not indicated in the Stopped column on the IMSTRANS display. The IMTSSTOP state exceptions are being processed incorrectly for the PSTOPPED and USTOPPED states. 1. Unable to determine whether an IMS transaction is in the USTOPPED or PSTOPPED state for the IMSTRANS display. 2. Unable to trigger the PSTOPPED and USTOPPED exception alerts on the IMSALERT display. 3. Unable to display the correct number of stopped transactions on the IMSOVER display. CA SYSVIEW VER(Z038) FMID(CNM4D70) PRE(RO55087) SUP(TSD7103).

33 CA SYSVIEW Performance Management CA RS PTF RO RO58800 RO58800 M.C.S. ENTRIES = ++PTF(RO58800) DESC(Fields not populated in IMSIMTR transaction record DSECT) The distributed IMSIMTR macro, which can be used to map the SYSVIEW for IMS transaction records that are shown on the IMSTLOG command display, contains fields related to IMS Fast Path transactions that are not populated in the IMTR_CLK segment. In addition, a new field will be added for IMS Fast Path transactions to specify the start time of a transaction in store clock format in the IMTR_CLK segment. IMTR_CLK DSECT fields related to IMS Fast Path transactions are not populated for type 'F' (Fast Path) IMS transaction records. Specifically, the following fields are not populated: IMTR_CLK_FLIMIQTM IMTR_CLK_FLOMPRTM IMTR_CLK_SYNCPRTM IMTR_CLK_FLDQOTIM IMTR_CLK_SYNCDATE IMTR_CLK_SYNCTIME Could cause errors in user-written batch reports. CA SYSVIEW VER(Z038) FMID(CNM4D70) PRE(RO55627 RO55929) SUP(TSD7105). ++HOLD(TSD7105) FMID(CNM4D70) SYSTEM REASON(DYNACT) DATE(13134) COMMENT( To dynamically install this correction: 1. Temporarily set the following option in SYSVIEW parmlib member IMSDATA: IMS-LOGGER-COMMON-REUSE NO 2. STOP/START the IMSDATA task from the ASADMIN display. 3. Change the IMSDATA parmlib member option back to: IMS-LOGGER-COMMON-REUSE YES ).

34 CA SYSVIEW Performance Management CA RS PTF RO RO59009 RO59009 M.C.S. ENTRIES = ++PTF(RO59009) DESC(Display does not update properly when PREFIX values changed) The display does not update properly when the PREFIX values changed for the following JES commands: JJOBQUE, JHELDQUE, JOUTQUE, JTRANQUE, JOBSUM, LISTINP, and ACTIVITY Changing PREFIX values may cause JES command display to update with incompleted or no data. Incorrect information displayed. Switch to a different display and back. CA SYSVIEW VER(Z038) FMID(CNM4D70) PRE(RO56491, RO56369) SUP(TSD7107).

35 CA SYSVIEW Performance Management CA RS PTF RO RO59084 RO59084 M.C.S. ENTRIES = ++PTF(RO59084) DESC(IMTSQUE threshold not working for IMS shared queues) In an IMS shared queue environment, the IMTSQUE variable threshold may not trigger alerts. The Queue field on the IMSOVER and IMSTRANS command display may also only reflect the transaction counts queued from the target ASID IMS. When IMTSQUE variable is used to monitor the depth of IMS shared queue, no alert is generated when the queue depth exceeds the threshold value. Unable to monitor IMS message queue depth in shared queue environment. CA SYSVIEW VER(Z038) FMID(CNM4D70) PRE(RO55339) SUP(TSD7108).

36 CA SYSVIEW Performance Management CA RS PTF RO RO59346 RO59346 M.C.S. ENTRIES = ++PTF(RO59346) DESC(XSCONN command fails from ISPF interface) Issuing the XSCONN command to connect to another instance of SYSVIEW from the ISPF interface will fail, if the SYSVIEW release in LINKLIST does not match the release that the user is currently running and a STEPLIB does not exist in the user's address space. Either of the following error messages may be received when attempting to connect to another instance of SYSVIEW: XSYS024I XSystem session ended, system xxxx job zzzzzzzz GSVX058E Invalid release for module xxxxxxxx Unable to connect to a different instance of SYSVIEW from the ISPF interface when issuing the XSCONN command. Issue the XSCONN command from the TSO or VTAM interface. CA SYSVIEW VER(Z038) FMID(CNM4D70) PRE(RO58616) SUP(TSD7109).