CA SYSVIEW Performance Management CA RS 1510 Service List

Transcription

1 CA SYSVIEW Performance Management CA RS 1510 Service List Description Type 14.1 RO83108 RC=16 running EASYTRIEVE reports PTF RO83242 CTHRESH Add line command changes type values to * PTF RO83350 GSV2328E READ SCFGLIB FAILED RUNNING GSVXSECL PTF RO83378 GSVX205E REASON 29 STARTING SYSVIEW / SYSVUSER PTF RO83390 STEPSUM displays incorrect stepname when symbolics PTF RO83565 S0C4 abend in GSVKCNFL issuing CONFLICT command PTF RO83683 LISTCONS DEACTIV LINE COMMAND FAILS WITH IEE313I PTF RO83807 ABEND S S40D SYSVIEW STC STORAGE CREEP **HIPER** RO83836 Abend S05B/U in MVSDATA-DEVICES starting SYSVIEW PTF RO83888 Abend S0C4-04 GSVUSAFE When User Command Groups Defined PTF RO83889 CEITRACE DATA AND RECORDS NOT GETTING LOGGED PTF RO83922 Abend U Mod GSVXSTGR Rtn GET$$$ in SYSVUSER **HIPER** RO84161 SMFRPT shifted output with FORMAT & DUMP on user formatter PTF RO84599 PCLIST may display incorrect module name PTF The CA RS 1510 service count for this release is 14

2 CA SYSVIEW Performance Management 2 CA RS 1510 Service List for CNM4E10 FMID Service Description Type CNM4E10 RO83108 RC=16 running EASYTRIEVE reports PTF RO83242 CTHRESH Add line command changes type values to * PTF RO83350 GSV2328E READ SCFGLIB FAILED RUNNING GSVXSECL PTF RO83378 GSVX205E REASON 29 STARTING SYSVIEW / SYSVUSER PTF RO83390 STEPSUM displays incorrect stepname when symbolics PTF RO83565 S0C4 abend in GSVKCNFL issuing CONFLICT command PTF RO83683 LISTCONS DEACTIV LINE COMMAND FAILS WITH IEE313I PTF RO83807 ABEND S S40D SYSVIEW STC STORAGE CREEP **HIPER** RO83836 Abend S05B/U in MVSDATA-DEVICES starting SYSVIEW PTF RO83888 Abend S0C4-04 GSVUSAFE When User Command Groups Defined PTF RO83889 CEITRACE DATA AND RECORDS NOT GETTING LOGGED PTF RO83922 Abend U Mod GSVXSTGR Rtn GET$$$ in SYSVUSER **HIPER** RO84161 SMFRPT shifted output with FORMAT & DUMP on user formatter PTF RO84599 PCLIST may display incorrect module name PTF The CA RS 1510 service count for this FMID is 14

3 CA SYSVIEW Performance Management CA RS PTF RO RO83108 RO83108 M.C.S. ENTRIES = ++PTF(RO83108) DESC(RC=16 running EASYTRIEVE reports) RC=16 is received when running CA Easytrieve reports due to incorrect definitions in SYSVIEW report macros CSMF027 and IMSIMTR. CA Easytrieve reports fail with RC=16 due to incorrect definitions added in SYSVIEW The following are some of the messages that appear in the joblog. EZTC0227E >>> $ must be from 1 to 4 EZTC0034E >>> $ already defined in file SMFIN EZTC0227E >>> $ must be from 1 to 4 EZTC0034E >>> $ already defined in file SMFIN EZTC0125E >>> fieldname not defined $ EZTC0108E >>> field attributes expected $ EZTC0125E >>> $ fieldname not de EZTC0034E >>> $ already defined in CSMF027.mac: Line 621 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 624 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 625 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 629 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 684 Col 1: E34: already defined in file SMFIN CSMF027.mac: Line 927 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 928 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 929 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 930 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 931 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 933 Col 38: E227: must be from 1 to 4 CSMF027.mac: Line 974 Col 1: E34: already defined in file SMFIN IMSIMTR.mac: Line 109 Col 51: E125: fieldname not defined IMSIMTR.mac: Line 109 Col 55: E108: field attributes expected IMSIMTR.mac: Line 110 Col 49: E125: fieldname not defined IMSIMTR.mac: Line 110 Col 53: E108: field attributes expected IMSIMTR.mac: Line 111 Col 48: E125: fieldname not defined IMSIMTR.mac: Line 111 Col 51: E125: fieldname not defined IMSIMTR.mac: Line 112 Col 48: E125: fieldname not defined IMSIMTR.mac: Line 112 Col 53: E125: fieldname not defined IMSIMTR.mac: Line 112 Col 45: E34: already defined in file WORK Reports are not produced. Use SYSVIEW Release 14.0 CNM4ZMAC library to run the batch reports. SUP(TSE1001).

4 CA SYSVIEW Performance Management CA RS PTF RO RO83242 RO83242 M.C.S. ENTRIES = ++PTF(RO83242) DESC(CTHRESH Add line command changes type values to *) When creating a new threshold definition utilizing the Add line command on the CTHRESH display, the value entered in the "Type" field is changed to a value of "*". Ultimately, the user is unable to use types SYSTEM, TIMER, TRANS, or TRANSUMM when utilizing the dummy input line to add a new threshold definition. This is due to an improper translation of the entered value. When utilizing the Add line command to create a new threshold definition, the value in the "Type" field will be saved as a "*" regardless of the value entered by the user. User's will be unable to create threshold definitions utilizing the Add line command with a value other than "*" in the "Type" field. If the user is unaware their threshold definition has been saved differently than what they were expecting, their threshold will not function as intended. The Add subcommand functions properly and can be used in place of the Add line command. SUP(TSE1002).

5 CA SYSVIEW Performance Management CA RS PTF RO RO83350 RO83350 M.C.S. ENTRIES = ++PTF(RO83350) DESC(GSV2328E READ SCFGLIB FAILED RUNNING GSVXSECL) The sample batch security report JCL is missing a //GSVXSCFG DD statement which causes the job to fail with RC=12. Online help topic TOPIC049 'Library concatenation - USER, SITE and SYSTEM' contains outdated references to the system configuration options member needing to reside in the system parmlib data set concatenation. Starting in SYSVIEW 14.1 this member must be located in the data set referenced by the new DDname GSVXSCFG. Running the sample security report in data set CNM4BSAM(EXECSECL) fails with the following errors: GSV2328E (UTILITY.GSVXSECL) Read SCFGLIB member GSVXssid failed. Dsn allocation failed GSVX205E (UTILITY.GSVXSECL) Nucleus load failed, reason 23 read failed for system configuration SECL001I Security report ended - completion code=12 Unable to run a security report. Add the following DD to the JCL, pointing to the data set that contains the System Configuration Options member GSVXssid: //GSVXSCFG DD DISP=SHR,DSN=sysview.CNM4SCFG SUP(TSE1003).

6 CA SYSVIEW Performance Management CA RS PTF RO RO83378 RO83378 M.C.S. ENTRIES = ++PTF(RO83378) DESC(GSVX205E REASON 29 STARTING SYSVIEW / SYSVUSER) The SSID=xxxx value specified in the SYSVIEW STC proc is not being passed on to the new SERVER subtask. Likewise, the SSID=xxxx value in the SYSVUSER STC proc is not being passed on to the new SERVSEC subtask. If this SSID=xxxx value differs from the default SSID assembled into the GSVBSSID module, initialization of the SERVER and SERVSEC subtasks may fail with an error. The SERVER and SERVSEC subtasks fail to initialize with the following error messages during startup of SYSVIEW and SYSVUSER: In SYSVIEW STC: GSVX205E (SERVER) Nucleus load failed, reason 29 subsystem is not initialized. Start SYSVIEW GSVX572E (SERVER) SRV00001 task initialization failed In SYSVUSER STC: GSVX205E (SERVSEC) Nucleus load failed, reason 29 subsystem is not initialized. Start SYSVIEW GSVX572E (SERVSEC) SRV00001 task initialization failed Error message is issued and subtask initialization fails but there is no overall functionality loss; services provided by these tasks will continue to occur within other tasks. If applicable to your environment, change the default SSID in the GSVBSSID load module to match what is specified on the SSID=xxxx parameter in the STC procs. This can be done using the supplied USERMOD JCL in data set SAMPJCL(USRM0001). SUP(TSE1004).

7 CA SYSVIEW Performance Management CA RS PTF RO RO83390 RO83390 M.C.S. ENTRIES = ++PTF(RO83390) DESC(STEPSUM displays incorrect stepname when symbolics) The STEPSUM command display would in some cases display the incorrect step name for a job step when the procedure name uses a symbolic reference. This only occurs before or during the execution of the job step. In some cases when a procedure name on an EXEC statement uses a symbolic reference, and the symbolic reference was greater than 8 characters, the prior step name would be incorrectly repeated on the STEPSUM command display. Once the step has completed execution the step name properly resolves on the STEPSUM command display. An incorrect step name could be displayed for a step prior to the step being executed. Keeping the length of the symbolic reference below a length of 8 characters will allow the step name to correctly resolve on the STEPSUM command display. SUP(TSE1005).

8 CA SYSVIEW Performance Management CA RS PTF RO RO83565 RO83565 M.C.S. ENTRIES = ++PTF(RO83565) DESC(S0C4 abend in GSVKCNFL issuing CONFLICT command) An S0C4-11 maybe encountered issuing the CONFLICT command due to an invalid check for acceptable return and reason codes. When issuing the CONFLICT command and no resources are found, a check is done to confirm the return code and reason code are acceptable. Due to an incorrect definition to detect the end of the table, an S0C4 is received because the area being compared is out of the acceptable storage area. Abend messages similar to the following would be seen: GSVX451E Abend S0C4-11 in CONFLICT command GSVX472I Userid GSVVCAPI Terminal UNKNOWN Interface CAPTURE GSVX457I Psw 078C2000 A491008A Ilc 6 Intc 11 GSVX477I Key 8 State SUP Am 31 Asc PRI GSVX458I Module GSVKCNFL Addr 2490F000 Offset A GSVX450I FixLvl BASE GSVX473I Routne FMT$$$ Addr 2490FC20 Offset A GSVX459I Data at PSW addr GSVX460I 000B D503 A GSVX455I General registers at entry to abend GSVX467I R0-R _ _248DB740 GSVX467I R2-R _ _ GSVX467I R4-R _24A _ GSVX467I R6-R _249A5C _249A5C90 GSVX467I R8-R _248A4EE _248DB060 GSVX467I R10-R _249108E _23B89000 GSVX467I R12-R _2490FC _248DA130 GSVX467I R14-R _248DB7C _ GSVX475I Access registers at entry to abend GSVX461I AR0-AR GSVX461I AR4-AR GSVX461I AR8-AR GSVX461I AR12-AR GSVX462I End of symptom dump GSVX950I SVCDUMP requested GSVX458I Module GSVKCNFL Addr 2490F000 Offset A GSVX450I FixLvl BASE GSVX473I Routne FMT$$$ Addr 2490FC20 Offset A GSVX954I Issuing SDUMPX to capture SVC dump Abend generated when issuing the CONFLICT command when no resources are found. None. SUP(TSE1006).

9 CA SYSVIEW Performance Management CA RS PTF RO RO83683 RO83683 M.C.S. ENTRIES = ++PTF(RO83683) DESC(LISTCONS DEACTIV LINE COMMAND FAILS WITH IEE313I) When issuing a Deactivate for an SMCS console from the LISTCONS command display, an incorrect Vary command is issued for the console. Issuing a Deactivate line command from the LISTCONS display results in the following message and the console is not deactivated. IEE313I xxxxxxxx UNIT REF. INVALID Console is not deactivated by line command. Issue MVS command 'V consolename,offline' to deactivate the console. SUP(TSE1007).

10 CA SYSVIEW Performance Management CA RS PTF RO RO83807 RO83807 M.C.S. ENTRIES = ++PTF(RO83807) DESC(ABEND S S40D SYSVIEW STC STORAGE CREEP) A routine that gathers IP-related statistics is not freeing a work buffer. Repeated invocations of this routine causes a storage creep in Subpool 0 Key 8 E-PVT storage. The users of this routine are the TCPDATA subtask in the SYSVIEW main services address space (SYSVIEW STC) and the IPSTATS command. The most likely symptom is the SYSVIEW STC, if left running long enough, will run out of storage and crash with abends such as S878-10, S40D. This is due to the TCPDATA subtask monitoring IP statistics on an interval basis. The same symptom can occur in SYSVUSER and/or other address spaces such as TSO users if the IPSTATS command is issued frequently from a SYSVIEW user session. The effected address space abends and terminates due to running out of storage and must be restarted. Do not issue the IPSTATS command, and use the DISable line command on the SCHEDULE command display to temporarily turn off data collection for the TCP-SYSTEM entry under Group TCPDATA until the PTF can be implemented. SUP(TSE1008 AC83864).

11 CA SYSVIEW Performance Management CA RS PTF RO RO83836 RO83836 M.C.S. ENTRIES = ++PTF(RO83836) DESC(Abend S05B/U in MVSDATA-DEVICES starting SYSVIEW) Abend S05B or U is possible when the MVSDATA subtask of the SYSVIEW main address space is processing the MVSDATA-DEVICES schedule event. This problem typically occurs the first time the MVSDATA-DEVICES event is processed, which by default, will occur within the first few minutes after SYSVIEW is started. This problem is more likely to occur on systems with a relatively large number of SMS managed direct access storage devices (DASD). The MVSDATA-DEVICES schedule event must be enabled for this problem to occur. Note that abend S0B5 and U are both CPU timeout abends that are taken by SYSVIEW when a task has used five minutes of uninterrupted CPU. Abend S05B is taken when SYSVIEW has used five minutes of uninterrupted SRB (ziip enabled) CPU. Abend U is taken when SYSVIEW has used five minutes of uninterrupted TCB (non-ziip enabled) CPU. If SYSVIEW is running ziip enabled, abend S05B is most likely to be observed. If SYSVIEW is not running ziip enabled, abend U will be observed. Messages similar to the following may be observed in the SYSVIEW job log shortly after the MVSDATA-DEVICES schedule event runs for the first time: GSVX971I (MVSDATA) SRB CPU limit exceeded (00:05:00) GSVX451E (MVSDATA) Abend S05B in MVS data collector GSVX452I (MVSDATA) SYSVIEW SRB in control at entry to abend GSVX453I (MVSDATA) Diagnostics for SRB in control at entry to abend GSVX457I (MVSDATA) Psw 078C2000 A6C374FE Ilc 0 Intc 00 GSVX477I (MVSDATA) Key 8 State SUP Am 31 Asc PRI GSVX458I (MVSDATA) Module GSVXNUC Addr 26C14000 Offset FE GSVX458I (MVSDATA) NucMod GSVZSDCR Addr 26C31FF8 Offset GSVX473I (MVSDATA) Routne DEVNSMSI Addr 26C37458 Offset A6 GSVX459I (MVSDATA) Data at PSW addr 26C374F8 GSVX460I (MVSDATA) D C0BC5E50 GSVX455I (MVSDATA) General registers at entry to abend GSVX467I (MVSDATA) R0-R _ _2A5728C0 GSVX467I (MVSDATA) R2-R _1E _2A5728C0 GSVX467I (MVSDATA) R4-R _2A6E3B _2BAC2CB0 GSVX467I (MVSDATA) R6-R _026F9B _02B4DDD0 GSVX467I (MVSDATA) R8-R _1E89B _28A81300 GSVX467I (MVSDATA) R10-R _26C _27CF5000 GSVX467I (MVSDATA) R12-R _26C _27CFD428 GSVX467I (MVSDATA) R14-R _00002C3F _2A6E3B80 Unable to monitor devices without abend. Disable the MVSDATA-DEVICES schedule event from the SCHEDULE command display (warm start) or in the SCHDMVS parmlib member (cold start). After the event has been disabled, restart SYSVIEW. SUP(TSE1009).

12 CA SYSVIEW Performance Management CA RS PTF RO RO83888 RO83888 M.C.S. ENTRIES = ++PTF(RO83888) DESC(Abend S0C4-04 GSVUSAFE When User Command Groups Defined) The GSVUSAFE SAF generator utility produces an S0C4-04 abend at offset 3E50 in the GSVUSAFE module. This occurs when there are user defined Command Groups and either the RACF or TOPS options are selected for p1 parameter in the utility. The GSVUSAFE job abends and does not contain all of the expected security statements. The GSVUSAFE utility is not useable. None. SUP(TSE1010).

13 CA SYSVIEW Performance Management CA RS PTF RO RO83889 RO83889 M.C.S. ENTRIES = ++PTF(RO83889) DESC(CEITRACE DATA AND RECORDS NOT GETTING LOGGED) Multiple problems exist regarding the CICS Exec Interface Trace (CEITRACE) functionality. 1. If CICS configuration option LOG-TRANSACTIONS NO is specified in the CICSOPTS parmlib member, CEITRACE records will never be written to the CEITLOG (EITL) log stream. 2. CICS configuration option TRANSACTION-DATA-EXECCICS YES is not working; EXEC CICS data is only being collected if this option is set to CEITRACE and a CEITRACE definition matches the tranid. 3. The information in online help TOPIC057 titled 'CICS Transaction Data Collection' regarding option TRANSACTION-DATA-EXECCICS incorrectly lists the valid options as SUMMARY / DETAIL, rather than NO / YES / CEITRACE. The documentation for this option in the CCONFIG online help is correct. 1. In the reported case the following CICSOPTS configuration options were specified: LOG-TRANSACTIONS NO TRANSACTION-DATA-EXECCICS CEITRACE A CEITRACE definition was enabled to trace a transaction but the transaction detail record was never written to CEITLOG. 2. The following CICSOPTS configuration option is not causing collection, and thus optional logging, of EXEC CICS requests: TRANSACTION-DATA-EXECCICS YES The CTRANLOG record does not contain an EXEC CICS Interface section. Unable to obtain CICS transaction records that contain EXEC CICS trace information. 1. On the CCONFIG command display temporarily specify LOG-TRANSACTIONS YES until the desired transaction records are obtained. SUP(TSE1011). ++HOLD(RO83889) FMID(CNM4E10) SYSTEM REASON(RESTART) DATE(15233) COMMENT( CA SYSVIEW Release SEQUENCE Before Restart PURPOSE To implement the fix USERS All users of SYSVIEW for CICS. AFFECTED KNOWLEDGE Product Administration REQUIRED CICS Systems Programming ACCESS Product libraries REQUIRED Ability to run SYSVIEW for CICS transactions ************************** * STEPS TO PERFORM *

14 CA SYSVIEW Performance Management CA RS PTF RO83889 ************************** 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. ).

15 CA SYSVIEW Performance Management CA RS PTF RO RO83922 RO83922 M.C.S. ENTRIES = ++PTF(RO83922) DESC(Abend U Mod GSVXSTGR Rtn GET$$$ in SYSVUSER) Abend U in the SYSVUSER address space is possible after a large number of cross system (xsystem) data requests from multiple users. This problem is caused by the XSDS (XSys Data Server) task switching from one user's security context to the next when serving the xsystem requests, but failing to free some of the control blocks from the previous security context. The result is orphaned storage which may continue to grow over time based on the number of security context switches are required as a result of the xsystem data requests. In addition, security settings for xsystem data requests may be observed to be inconsistent from incorrect reuse of some settings from one request to the next. In the reported case, several users had XSDATA turned on for commands which caused the XSDS task to perform several security context switches. This caused high usage of subpool 0 key 8 E-PVT storage. Abend messages similar to the following may be observed from SYSVUSER: GSVX004E (XSDS) GETMAIN for workarea failed. Routine GBUF$$ 00CA GSVX451E (XSDS) Abend U in XSys data server GSVX457I (XSDS) Psw 078C0000 A86C9052 Ilc 2 Intc 0D GSVX477I (XSDS) Key 8 State SUP Am 31 Asc PRI GSVX458I (XSDS) Module GSVXNUC Addr Offset 000B5052 GSVX458I (XSDS) NucMod GSVXSTGR Addr 286C7508 Offset 00001B4A GSVX450I (XSDS) FixLvl RO79207 GSVX473I (XSDS) Routne GET$$$ Addr 286C8780 Offset D2 GSVX459I (XSDS) Data at PSW addr 286C904C GSVX460I (XSDS) A7F A0DA A7F4 GSVX455I (XSDS) General registers at entry to abend GSVX467I (XSDS) R0-R _ _04000BB7 GSVX467I (XSDS) R2-R _000000CA _286649C0 GSVX467I (XSDS) R4-R _ C _290AD470 GSVX467I (XSDS) R6-R _2A _2A GSVX467I (XSDS) R8-R _ _29055A40 GSVX467I (XSDS) R10-R _286CBE _2905E000 GSVX467I (XSDS) R12-R _286C _29F58358 GSVX467I (XSDS) R14-R _A86C _ In addition to abend U , other storage related abends may be observed such as S878-10, S80A, etc. The SYSVUSER address space may become unstable and abend, or may require to be stopped and restarted. A periodic recycle of the SYSVUSER address space will free the orphaned storage, thus relieving the address space storage constraint. SUP(TSE1012 BC83864).

16 CA SYSVIEW Performance Management CA RS PTF RO RO84161 RO84161 M.C.S. ENTRIES = ++PTF(RO84161) DESC(SMFRPT shifted output with FORMAT & DUMP on user formatter) The output of the SMFRPT command when using the FORMAT and DUMP parameters with a user written formatting program results in the dump section displaying data rows that are incorrectly shifted. Specifically the first row of data is shifted by 1 byte, the second row is shifted by 2 bytes, the third row is shifted by 3 bytes, and so on. Note that the SD (Select and Dump) line command on many log stream browse commands issues the SMFRPT command with both the FORMAT and DUMP parameters. Output similar to the following from the SMFRPT command with the FORMAT and DUMP parameters is observed when formatting an SMF record with a user written SMF formatting program: Section: Common Jobname UID Data Set Name Volume IXGLOGR LOGGER.SYSVDEV.SMFDATA.SMFD.CA31.A SMS008 Offset C E A FC3C1 * CA * F3F1C9E7 C7D3D6C7 D C60115 * 31IXGLOGR...F.. * F D3D6C7C7 *...LOGG * C5D94BE2 E8E2E5C4 C5E54BE2 D4C6C4C1 * ER.SYSVDEV.SMFDA * E3C14BE2 D4C6C44B C3C1F3F1 4BC1F0F0 * TA.SMFD.CA31.A00 * F3F7F5F5 F64BC E2D4 * D...SM * E2F0F0F8 * S008 * Unable to correctly format and dump the contents of an SMF record at the same time. Issuing the SMFRPT command with the FORMAT parameter and not the DUMP parameter displays the correct format section of the output. Issuing the SMFRPT command with the DUMP parameter and not the FORMAT parameter displays the correct dump section of the output. Note that the S (Select) and D (Dump) line commands on many log stream browse commands issue the SMFRPT command with FORMAT and DUMP parameters respectively. SUP(TSE1014).

17 CA SYSVIEW Performance Management CA RS PTF RO RO84599 RO84599 M.C.S. ENTRIES = ++PTF(RO84599) DESC(PCLIST may display incorrect module name) When the PCLIST command display is invoked, some PC routines may display an incorrect module name and offset. This occurs for any non-space switching PCs in which the EPAddr resides in a PVT/EPVT/GPVT region. The PCLIST command display may display the incorrect module and offset for any non-space switching PCs that reside in a PVT/EPVT/GPVT region. The EPAddr for PC routines that do not have an XAID/XJobnam are being looked up in ASID 0001 *MASTER* rather than in the current ASID. Incorrect module information may be displayed for the corresponding PC. None. SUP(TSE1018).