CA SYSVIEW Performance Management CA RS 1501 Service List

Transcription

1 CA SYSVIEW Performance Management CA RS 1501 Service List Description Type 14.0 RO70574 MQ Data Collection task not running - ENQ lockout PTF RO74916 ALERTSUM CICS TASKS AND OTHER STATISTICS INCORRECT PTF RO75937 Performance problem when ziipenable set to NO ** PRP ** RO76171 SET ROWS Causes XSSystem column to disappear PTF RO76269 SelectParm SortParms not cleared in PROFILE FORMAT PTF RO76365 TRACE ASID (4) using lots of real and/or aux storage PTF RO76504 Report Writer S0C4 when using range command PTF RO76806 Error when using OSCMDRSP REXX function PTF RO77079 PERIOD parameter ignored on all log stream command displays PTF RO77255 GSVX206E Nucleus initialization fail upon cancelled logon PTF The CA RS 1501 service count for this release is 10

2 CA SYSVIEW Performance Management CA RS 1501 Service List Description Type 13.9 RO70573 MQ Data Collection task not running - ENQ lockout PTF RO74757 ALERTSUM CICS TASKS AND OTHER STATISTICS INCORRECT PTF RO76172 SET ROWS Causes XSSystem column to disappear PTF RO76364 TRACE ASID (4) using lots of real and/or aux storage PTF RO76405 SelectParm SortParms not cleared in PROFILE format PTF RO76503 Report Writer S0C4 when using range command PTF The CA RS 1501 service count for this release is 6

3 CA SYSVIEW Performance Management CA RS 1501 Service List Description Type 13.7 RO70572 ENQ on GSVXQNAM / QMRIT not released after abend PTF The CA RS 1501 service count for this release is 1

4 CA SYSVIEW Performance Management CA RS 1501 Service List Description Type 13.5 RO70571 MQ Data Collection task not running - ENQ lockout PTF The CA RS 1501 service count for this release is 1

5 CA SYSVIEW Performance Management 5 CA RS 1501 Service List for CNM4D50 FMID Service Description Type CNM4D50 RO70571 MQ Data Collection task not running - ENQ lockout PTF The CA RS 1501 service count for this FMID is 1

6 CA SYSVIEW Performance Management 6 CA RS 1501 Service List for CNM4D70 FMID Service Description Type CNM4D70 RO70572 ENQ on GSVXQNAM / QMRIT not released after abend PTF The CA RS 1501 service count for this FMID is 1

7 CA SYSVIEW Performance Management 7 CA RS 1501 Service List for CNM4D90 FMID Service Description Type CNM4D90 RO70573 MQ Data Collection task not running - ENQ lockout PTF RO74757 ALERTSUM CICS TASKS AND OTHER STATISTICS INCORRECT PTF RO76172 SET ROWS Causes XSSystem column to disappear PTF RO76364 TRACE ASID (4) using lots of real and/or aux storage PTF RO76405 SelectParm SortParms not cleared in PROFILE format PTF RO76503 Report Writer S0C4 when using range command PTF The CA RS 1501 service count for this FMID is 6

8 CA SYSVIEW Performance Management 8 CA RS 1501 Service List for CNM4E00 FMID Service Description Type CNM4E00 RO70574 MQ Data Collection task not running - ENQ lockout PTF RO74916 ALERTSUM CICS TASKS AND OTHER STATISTICS INCORRECT PTF RO75937 Performance problem when ziipenable set to NO ** PRP ** RO76171 SET ROWS Causes XSSystem column to disappear PTF RO76269 SelectParm SortParms not cleared in PROFILE FORMAT PTF RO76365 TRACE ASID (4) using lots of real and/or aux storage PTF RO76504 Report Writer S0C4 when using range command PTF RO76806 Error when using OSCMDRSP REXX function PTF RO77079 PERIOD parameter ignored on all log stream command displays PTF RO77255 GSVX206E Nucleus initialization fail upon cancelled logon PTF The CA RS 1501 service count for this FMID is 10

9 CA SYSVIEW Performance Management CA RS PTF RO RO70574 RO70574 M.C.S. ENTRIES = ++PTF(RO70574) DESC(MQ Data Collection task not running - ENQ lockout) When an abend occurs in either the MQRJOB or MQROBJ commands, a SHR ENQ for resource GSVXQNAM / QMRIT may still be held and not released until the user who experienced the abend presses Enter on their terminal. This can only occur when the user's SYSVIEW session is entered via the TSO or ISPF interfaces. If MQ Data Collection is scheduled to run before the user presses Enter, that Data Collection (subtask MQSDATA, program GSVSDTCL in the SYSVIEW main address space) will be held up waiting to get an EXCL ENQ for resource GSVXQNAM / QMRIT until the user presses Enter on their terminal, thus releasing their SHR ENQ. Data Collection will be delayed until the user presses Enter on their terminal. None (other than for the user to press Enter on their terminal) CA SYSVIEW VER(Z038) FMID(CNM4E00) SUP(TSE0011).

10 CA SYSVIEW Performance Management CA RS PTF RO RO74916 RO74916 M.C.S. ENTRIES = ++PTF(RO74916) DESC(ALERTSUM CICS TASKS AND OTHER STATISTICS INCORRECT) The statistics shown on the ALERTSUM CICS command display can be out of sync with the actual alerts shown on the CALERTS display. The entry for CICS TASKS may have incorrect counts for any of the statuses, where the numbers are typically much higher than what is shown on the CALERTS display. This in turn could cause counts for other CICS resource entries to be incorrectly smaller than what they should be. Incorrect/misleading summarization of currently outstanding CICS alerts. None. CA SYSVIEW VER(Z038) FMID(CNM4E00) PRE(RO70540) SUP(TSE0052).

11 CA SYSVIEW Performance Management CA RS PTF RO RO75937 RO75937 M.C.S. ENTRIES = ++PTF(RO75937) DESC(Performance problem when ziipenable set to NO) After the application of PTF RO72153 (SYSVIEW 13.9) or PTF RO72154 (SYSVIEW 14.0), the following situation may occur when accessing SYSVIEW via its TSO or ISPF interfaces: When SYSVIEW's ziip option is NOT enabled, certain SYSVIEW commands that operate on JES2 data will use more CPU than they should and the elapsed time to process the commands will be longer than it should be. Note that this refers ONLY to the ziipenable option in the OPTIONS member of parmlib being set to NO and does NOT refer to the ZIIP-ENABLE option in the CICSOPTS member of parmlib. Both the elapsed time and the CPU time for the following three SYSVIEW commands will be greater than expected: JCOPYOUT OUTPUT STEPSUM The CPU time consumed by the above three commands will be greater than expected and the elapsed time for those three commands will be elongated. Set the ziipenable option in the OPTIONS member of parmlib to YES. CA SYSVIEW VER(Z038) FMID(CNM4E00) PRE(RO72154) SUP(AO72154 TSE0060).

12 CA SYSVIEW Performance Management CA RS PTF RO RO76171 RO76171 M.C.S. ENTRIES = ++PTF(RO76171) DESC(SET ROWS Causes XSSystem column to disappear) Improper formating is displayed under certain circumstances for data rows based on the profile setting for XSDATA in all XSystem commands that accept the XSDATA/NOXSDATA options when invoked. When any XSystem capable command that accepts the XSDATA or NOXSDATA parameter is issued and then followed by a SET command that alters the row format,such as SET ROWS or SET FORMAT, the XSSystem field may appear od disappear from the display erroneously. For example, if your profile has XSDATA NO for the MQLIST command, And you enter MQLIST XSDATA, you will see cross-system data rows And the XSSystem column will appear on the display. If you then issue SET ROWS ON you will still see the cross-system data But the XSSystem column will disappear. The opposite would be true if the profile has XSDATA YES and you Specified the NOXSDATA parameter on the command. This can cause data to be displayed in the improper format Instead of using the XSDATA/NOXSDATA option instead use the SET XSDATA ON/OFF to view/ignore XSystem data like the following example using MQLIST Issue the following commands: MQLIST SET XSDATA ON/OFF SET ROWS ON CA SYSVIEW VER(Z038) FMID(CNM4E00) PRE(RO71580) SUP(TSE0063).

13 CA SYSVIEW Performance Management CA RS PTF RO RO76269 RO76269 M.C.S. ENTRIES = ++PTF(RO76269) DESC(SelectParm SortParms not cleared in PROFILE FORMAT) If the SortParms or SelectParms fields have been updated for a display format in the profile, they can not be cleared at a later time. SortParms and SelectParms are cleared but the previous value is put back after exiting and re-entering the Profile format. Unable to clear SortParms or SelectParms. None. CA SYSVIEW VER(Z038) FMID(CNM4E00) SUP(TSE0064).

14 CA SYSVIEW Performance Management CA RS PTF RO RO76365 RO76365 M.C.S. ENTRIES = ++PTF(RO76365) DESC(TRACE ASID (4) using lots of real and/or aux storage) The SYSVIEW TRACE command is getting storage in IBM's TRACE address space, but not freeing it. The storage will not be freed until the user's address space terminates (if entry to SYSVIEW was via the TSO or ISPF interfaces) or until the SYSVUSER address space is shut down (if entry to SYSVIEW was via the VTAM interface). Shortage of Real Storage and/or Auxiliary Storage. Messages which might be seen are: IRA200E AUXILIARY STORAGE SHORTAGE IRA201E CRITICAL AUXILIARY STORAGE SHORTAGE IRA203I nn% AUXILIARY STORAGE ALLOCATED TO uuu IRA204E nn% AUXILIARY STORAGE ALLOCATED TO uuu IRA206I uuuuuuuu ASID aaaa FRAMES ffffffffff SLOTS ssssssssss % OF AUX nn.n IRA220I CRITICAL AUXILIARY SHORTAGE IRA400E return-code, PAGEABLE STORAGE SHORTAGE IRA401E return-code,critical PAGEABLE STORAGE SHORTAGE IRA405I return code, nn% OF THE REAL STORAGE FRAMES ARE FIXED IRA420I CRITICAL STORAGE SHORTAGE return-code System performance may be impacted during the storage shortage (real or auxiliary). - Users' jobs may run slowly. - Jobs and or Started Tasks may not be able to start running. Issue the USERS command and check the LISTLOGs for every user until the one issuing the TRACE commands is found. - If the TRACE command is being issued from a TSO session, ask the user to log off or cancel the user. - If the the TRACE command is being issued from a VTAM session, recycle the SYSVUSER address space at the earliest convenient time. - If the TRACE command is being issued from a CAPTURE, modify the CAPTURE member so it no longer issues the TRACE command; also recycle the SYSVUSER address space at the earliest convenient time. CA SYSVIEW r VER(Z038) FMID(CNM4E00) SUP(TSE0066).

15 CA SYSVIEW Performance Management CA RS PTF RO RO76504 RO76504 M.C.S. ENTRIES = ++PTF(RO76504) DESC(Report Writer S0C4 when using range command) Abend S0C4 may occur when using the RANGE command in the report control input. The problem is most likely occur when reporting on records that contain a data section close to 4096 bytes in size. Messages similar to the following may be observed in the report job log: IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0C4 REASON CODE= TIME= SEQ=47364 CPU=0000 ASID=0280 PSW AT TIME OF ERROR 078D2000 B3D1F91C ILC 4 INTC 04 NO ACTIVE MODULE FOUND NAME=UNKNOWN DATA AT PSW 33D1F BF8F CDB0074E AR/GR 0: /CDF1C091_33D : /C9CC9A58_ : FFFFFFFF/FFFFFFFF_ : FFFFFFFF/FFFFFFFF_33D1F77C 4: FFFFFFFF/FFFFFFFF_33DA7624 5: FFFFFFFF/FFFFFFFF_33D1F098 6: FFFFFFFF/FFFFFFFF_B3D : FFFFFFFF/FFFFFFFF_000123F8 8: FFFFFFFF/FFFFFFFF_000019B8 9: FFFFFFFF/FFFFFFFF_00000FF0 A: FFFFFFFF/FFFFFFFF_33D1F918 B: FFFFFFFF/FFFFFFFF_33D02248 C: FFFFFFFF/FFFFFFFF_8000D000 D: FFFFFFFF/ _ E: / _33D0261C F: / _33D025CE END OF SYMPTOM DUMP Unable to use the RANGE commands in the Report Writer report control input without abend. Remove all RANGE commands in the report control input. CA EXPLORE Report Writer VER(Z038) FMID(CNM4E00) SUP(TSE0068).

16 CA SYSVIEW Performance Management CA RS PTF RO RO76806 RO76806 M.C.S. ENTRIES = ++PTF(RO76806) DESC(Error when using OSCMDRSP REXX function) Executing a REXX exec that contains OSCMDRSP REXX function may encounter a problem where the OSCMDRSP function fails OSCMDRSP REXX function fails with return code 8 with the following message being displayed in user's LISTLOG. MVS$001E Command parameter required by cmdname command Unable to use OSCMDRSP REXX function. Add a dummy parameter when executing the REXX. exec using RXDISP or RXEXEC. For example, instead of "RXDISP RexxName" issue "RXDISP RexxName dummy". CA SYSVIEW VER(Z038) FMID(CNM4E00) SUP(TSE0069).

17 CA SYSVIEW Performance Management CA RS PTF RO RO77079 RO77079 M.C.S. ENTRIES = ++PTF(RO77079) DESC(PERIOD parameter ignored on all log stream command displays) The PERIOD parameter, when used with a DATE and/or TIME parameter, is ignored on all of the following log stream browsing command displays: AUDITLOG, CSYSDATA, CTRANLOG, CTRANSUM, HCLOG, IMSOMAT, IMSRSLOG, IMSTLOG, LGBROWSE, MQRLOG, OPERLOG, PLOTLOG, SMFLOG, XLOG A command similar to the following results in log stream data being returned from the start DATE and TIME to the end of the log stream without stopping the return of data when the PERIOD had been reached. CTRANLOG DATE 12/23/14 TIME 07:30:00 PERIOD 1HOUR Unable to use the PERIOD parameter to restrict the amount of data returned by log stream browsing command displays which may result in longer than anticipated command response and unwanted data. None. CA SYSVIEW VER(Z038) FMID(CNM4E00) SUP(TSE0073).

18 CA SYSVIEW Performance Management CA RS PTF RO RO77255 RO77255 M.C.S. ENTRIES = ++PTF(RO77255) DESC(GSVX206E Nucleus initialization fail upon cancelled logon) A GSVX206E error message is displayed in the SYSVUSER job log when a user presses PF3 (END) on the logon screen without entering a username. If a user enters the VTAM or CICS interface of SYSVIEW, is prompted with the logon screen and presses PF3 (END) before successfully completing the logon, the following message is observed in the SYSVUSER job log: GSVX206E Nucleus initialization failed Unnecessary messages logged in the SYSVUSER job log. None. CA SYSVIEW VER(Z038) FMID(CNM4E00) SUP(TSE0075).

19 CA SYSVIEW Performance Management CA RS PTF RO RO70573 RO70573 M.C.S. ENTRIES = ++PTF(RO70573) DESC(MQ Data Collection task not running - ENQ lockout) When an abend occurs in either the MQRJOB or MQROBJ commands, a SHR ENQ for resource GSVXQNAM / QMRIT may still be held and not released until the user who experienced the abend presses Enter on their terminal. This can only occur when the user's SYSVIEW session is entered via the TSO or ISPF interfaces. If MQ Data Collection is scheduled to run before the user presses Enter, that Data Collection (subtask MQSDATA, program GSVSDTCL in the SYSVIEW main address space) will be held up waiting to get an EXCL ENQ for resource GSVXQNAM / QMRIT until the user presses Enter on their terminal, thus releasing their SHR ENQ. Data Collection will be delayed until the user presses Enter on their terminal. None (other than for the user to press Enter on their terminal) CA SYSVIEW VER(Z038) FMID(CNM4D90) SUP(TSD9144).

20 CA SYSVIEW Performance Management CA RS PTF RO RO74757 RO74757 M.C.S. ENTRIES = ++PTF(RO74757) DESC(ALERTSUM CICS TASKS AND OTHER STATISTICS INCORRECT) The statistics shown on the ALERTSUM CICS command display can be out of sync with the actual alerts shown on the CALERTS display. The entry for CICS TASKS may have incorrect counts for any of the statuses, where the numbers are typically much higher than what is shown on the CALERTS display. This in turn could cause counts for other CICS resource entries to be incorrectly smaller than what they should be. Incorrect/misleading summarization of currently outstanding CICS alerts. None. CA SYSVIEW VER(Z038) FMID(CNM4D90) PRE(RO70538) SUP(TSD9171).

21 CA SYSVIEW Performance Management CA RS PTF RO RO76172 RO76172 M.C.S. ENTRIES = ++PTF(RO76172) DESC(SET ROWS Causes XSSystem column to disappear) Improper formating is displayed under certain circumstances for data rows based on the profile setting for XSDATA in all XSystem commands that accept the XSDATA/NOXSDATA options when invoked. When any XSystem capable command that accepts the XSDATA or NOXSDATA parameter is issued and then followed by a SET command that alters the row format,such as SET ROWS or SET FORMAT, the XSSystem field may appear od disappear from the display erroneously. For example, if your profile has XSDATA NO for the MQLIST command, And you enter MQLIST XSDATA, you will see cross-system data rows And the XSSystem column will appear on the display. If you then issue SET ROWS ON you will still see the cross-system data But the XSSystem column will disappear. The opposite would be true if the profile has XSDATA YES and you Specified the NOXSDATA parameter on the command. This can cause data to be displayed in the improper format Instead of using the XSDATA/NOXSDATA option instead use the SET XSDATA ON/OFF to view/ignore XSystem data like the following example using MQLIST Issue the following commands: MQLIST SET XSDATA ON/OFF SET ROWS ON CA SYSVIEW VER(Z038) FMID(CNM4D90) PRE(RO71579) SUP(TSD9181).

22 CA SYSVIEW Performance Management CA RS PTF RO RO76364 RO76364 M.C.S. ENTRIES = ++PTF(RO76364) DESC(TRACE ASID (4) using lots of real and/or aux storage) The SYSVIEW TRACE command is getting storage in IBM's TRACE address space, but not freeing it. The storage will not be freed until the user's address space terminates (if entry to SYSVIEW was via the TSO or ISPF interfaces) or until the SYSVUSER address space is shut down (if entry to SYSVIEW was via the VTAM interface). Shortage of Real Storage and/or Auxiliary Storage. Messages which might be seen are: IRA200E AUXILIARY STORAGE SHORTAGE IRA201E CRITICAL AUXILIARY STORAGE SHORTAGE IRA203I nn% AUXILIARY STORAGE ALLOCATED TO uuu IRA204E nn% AUXILIARY STORAGE ALLOCATED TO uuu IRA206I uuuuuuuu ASID aaaa FRAMES ffffffffff SLOTS ssssssssss % OF AUX nn.n IRA220I CRITICAL AUXILIARY SHORTAGE IRA400E return-code, PAGEABLE STORAGE SHORTAGE IRA401E return-code,critical PAGEABLE STORAGE SHORTAGE IRA405I return code, nn% OF THE REAL STORAGE FRAMES ARE FIXED IRA420I CRITICAL STORAGE SHORTAGE return-code System performance may be impacted during the storage shortage (real or auxiliary). - Users' jobs may run slowly. - Jobs and or Started Tasks may not be able to start running. Issue the USERS command and check the LISTLOGs for every user until the one issuing the TRACE commands is found. - If the TRACE command is being issued from a TSO session, ask the user to log off or cancel the user. - If the the TRACE command is being issued from a VTAM session, recycle the SYSVUSER address space at the earliest convenient time. - If the TRACE command is being issued from a CAPTURE, modify the CAPTURE member so it no longer issues the TRACE command; also recycle the SYSVUSER address space at the earliest convenient time. CA SYSVIEW r VER(Z038) FMID(CNM4D90) PRE(RO63197) SUP(TSD9184).

23 CA SYSVIEW Performance Management CA RS PTF RO RO76405 RO76405 M.C.S. ENTRIES = ++PTF(RO76405) DESC(SelectParm SortParms not cleared in PROFILE format) If the SortParms or SelectParms fields have been updated for a display format in the profile, they can not be cleared at a later time. SortParms and SelectParms are cleared but the previous value is put back after exiting and re-entering the Profile format. Unable to clear SortParms or SelectParms. None. CA SYSVIEW VER(Z038) FMID(CNM4D90) SUP(TSD9185).

24 CA SYSVIEW Performance Management CA RS PTF RO RO76503 RO76503 M.C.S. ENTRIES = ++PTF(RO76503) DESC(Report Writer S0C4 when using range command) Abend S0C4 may occur when using the RANGE command in the report control input. The problem is most likely occur when reporting on records that contain a data section close to 4096 bytes in size. Messages similar to the following may be observed in the report job log: IEA995I SYMPTOM DUMP OUTPUT SYSTEM COMPLETION CODE=0C4 REASON CODE= TIME= SEQ=47364 CPU=0000 ASID=0280 PSW AT TIME OF ERROR 078D2000 B3D1F91C ILC 4 INTC 04 NO ACTIVE MODULE FOUND NAME=UNKNOWN DATA AT PSW 33D1F BF8F CDB0074E AR/GR 0: /CDF1C091_33D : /C9CC9A58_ : FFFFFFFF/FFFFFFFF_ : FFFFFFFF/FFFFFFFF_33D1F77C 4: FFFFFFFF/FFFFFFFF_33DA7624 5: FFFFFFFF/FFFFFFFF_33D1F098 6: FFFFFFFF/FFFFFFFF_B3D : FFFFFFFF/FFFFFFFF_000123F8 8: FFFFFFFF/FFFFFFFF_000019B8 9: FFFFFFFF/FFFFFFFF_00000FF0 A: FFFFFFFF/FFFFFFFF_33D1F918 B: FFFFFFFF/FFFFFFFF_33D02248 C: FFFFFFFF/FFFFFFFF_8000D000 D: FFFFFFFF/ _ E: / _33D0261C F: / _33D025CE END OF SYMPTOM DUMP Unable to use the RANGE commands in the Report Writer report control input without abend. Remove all RANGE commands in the report control input. CA EXPLORE Report Writer VER(Z038) FMID(CNM4D90) PRE(RO67986) SUP(TSD9186).

25 CA SYSVIEW Performance Management CA RS PTF RO RO70572 RO70572 M.C.S. ENTRIES = ++PTF(RO70572) DESC(ENQ on GSVXQNAM / QMRIT not released after abend) When an abend occurs in either the MQRJOB or MQROBJ commands, a SHR ENQ for resource GSVXQNAM / QMRIT may still be held and not released until the user who experienced the abend presses Enter on their terminal. This can only occur when the user's SYSVIEW session is entered via the TSO or ISPF interfaces. If MQ Data Collection is scheduled to run before the user presses Enter, that Data Collection (subtask MQSDATA, program GSVSDTCL in the SYSVIEW main address space) will be held up waiting to get an EXCL ENQ for resource GSVXQNAM / QMRIT until the user presses Enter on their terminal, thus releasing their SHR ENQ. Data Collection will be delayed until the user presses Enter on their terminal. None (other than for the user to press Enter on their terminal) CA SYSVIEW VER(Z038) FMID(CNM4D70) SUP(TSD7256).

26 CA SYSVIEW Performance Management CA RS PTF RO RO70571 RO70571 M.C.S. ENTRIES = ++PTF(RO70571) DESC(MQ Data Collection task not running - ENQ lockout) When an abend occurs in either the MQRJOB or MQROBJ commands, a SHR ENQ for resource GSVXQNAM / QMRIT may still be held and not released until the user who experienced the abend presses Enter on their terminal. This can only occur when the user's SYSVIEW session is entered via the TSO or ISPF interfaces. If MQ Data Collection is scheduled to run before the user presses Enter, that Data Collection (subtask MQSDATA, program GSVSDTCL in the SYSVIEW main address space) will be held up waiting to get an EXCL ENQ for resource GSVXQNAM / QMRIT until the user presses Enter on their terminal, thus releasing their SHR ENQ. Data Collection will be delayed until the user presses Enter on their terminal. None (other than for the user to press Enter on their terminal) CA SYSVIEW VER(Z038) FMID(CNM4D50) SUP(TSD5315).