CA SYSVIEW Performance Management 14.1 1 CA RS 1608 Service List Description Type 14.1 RO89702 JOBSUM/JJOBQUE display wrong status for HELD jobs PTF RO89731 Invalid data placed in conflict message output PTF RO90646 Excessive storage utilization running GSVYSTCV conversion PTF RO90759 Enqueue contention on DATALIB delays Logger start **HIPER** RO90835 COMMON/VSMTRACK ALLOC/PCT% HAS INCORRECT STATUS PTF RO90922 CICS CTRANLOG RECORD MISSING DATA SEGMENTS PTF RO91004 EXTENTS INFO FIELD BYTES SHOWS *S0C7 W/RO86633 ** PRP ** The CA RS 1608 service count for this release is 7
CA SYSVIEW Performance Management 2 CA RS 1608 Service List for CNM4E10 FMID Service Description Type CNM4E10 RO89702 JOBSUM/JJOBQUE display wrong status for HELD jobs PTF RO89731 Invalid data placed in conflict message output PTF RO90646 Excessive storage utilization running GSVYSTCV conversion PTF RO90759 Enqueue contention on DATALIB delays Logger start **HIPER** RO90835 COMMON/VSMTRACK ALLOC/PCT% HAS INCORRECT STATUS PTF RO90922 CICS CTRANLOG RECORD MISSING DATA SEGMENTS PTF RO91004 EXTENTS INFO FIELD BYTES SHOWS *S0C7 W/RO86633 ** PRP ** The CA RS 1608 service count for this FMID is 7
CA SYSVIEW Performance Management 14.1 3 CA RS 1608 - PTF RO89702 14.1 RO89702 RO89702 M.C.S. ENTRIES = ++PTF(RO89702) DESC(JOBSUM/JJOBQUE display wrong status for HELD jobs) This fix corrects a number of JOBSUM and JJOBQUE display issues. On the JOBSUM and JJOBQUE displays, some held states showed as blanks and some are incorrectly identified in the STATUS field. If a job class is held by the operator, the status for jobs in that class was HELDALL when it should have been HELDCLS. If the SplVol parameter was specified on the JOBSUM command, the SplVol field remained blank. If a job had held-class output and the job was held, the status on JOBSUM was HELDCLS and on JJOBQUE it was HELDJOB. This fix now displays HELDCLS for both. Also JJOBQUE will now allow an output queue entry that has a status of HELDJOB to be released. One reported state was the JOBSUM and JJOBQUE display showing jobs that have been held by job class as HELDALL instead of HELDCLS. The HELDALL status is only valid for z/os 1.13 when JES2 $HA command is used. For z/os 2.1 and later releases, the status for jobs held by the operator command $HA will show as HELDJOB. IMPACT: Display shows incorrect held status. None. PRE(RO87870) SUP(TSE1080).
CA SYSVIEW Performance Management 14.1 4 CA RS 1608 - PTF RO89731 14.1 RO89731 RO89731 M.C.S. ENTRIES = ++PTF(RO89731) DESC(Invalid data placed in conflict message output) If a non-zero return code is received back from the MIMQUERY call done during the CONFLICT command, invalid data is placed in the message. This fix also corrects a problem encountered where only a single answer area buffer was being displayed when there should have been additional conflict information processed. When a bad return code is received back from a MIMQUERY call, a message similar to the following may be received. GSVX529E MIMQUERY* ISGQUERY...H...h failed, rc rsn GSVX529E ISGQUERY...H...hGNR2...Q...q... failed, rc 00000004 rsn 051B0405 Where the above message displays invalid data in the message area. IMPACT: Incorrect error message produced as well as incomplete conflict information displayed. None. PRE(RO83565) SUP(TSE1082).
CA SYSVIEW Performance Management 14.1 5 CA RS 1608 - PTF RO90646 14.1 RO90646 RO90646 M.C.S. ENTRIES = ++PTF(RO90646) DESC(Excessive storage utilization running GSVYSTCV conversion) While running SYSVIEW 14.1 INST0053 install job to convert CICS States and Threshold Exceptions, storage problems may be encountered if there are a large number of converted definitions. This fix also addresses the same type of error that may be encountered with INST0052 (CICS Transaction Cancellation conversion) and INST0054 (CICS Transaction Options conversion). During the execution of INST0052, INST0053 or INST0054 storage type abends such as S878 or S40D may occur due to insufficient storage. Messages similar to the following may be observed: SYSTEM COMPLETION CODE=80A REASON CODE=00000010 TIME=13.43.58 SEQ=53794 CPU=4000 ASID=00## PSW AT TIME OF ERROR 070C1000 8161C108 ILC 2 INTC 0D NO ACTIVE MODULE FOUND IMPACT: Conversion jobs INST0052, INST0053 or INST0054 fail and no conversion is performed. Run conversion jobs with REGION=0M if possible. PRE(RO89836) SUP(TSE1102).
CA SYSVIEW Performance Management 14.1 6 CA RS 1608 - PTF RO90759 14.1 RO90759 RO90759 M.C.S. ENTRIES = ++PTF(RO90759) DESC(Enqueue contention on DATALIB delays Logger start) During initialization the CICS data collector attempts to connect to the specified CICSLOGR. If the data collector is unable to establish a connection it retries the connection every 15 seconds until successful or CICS terminates. During the connect process a shared enqueue is held on the DATALIB(CNM4BDAT) data set. This caused an exclusive enqueue issued by the DATALIB task in SYSVIEW to wait behind the shared requests. If additional regions are started, the CICS region will hang behind the exclusive request from the DATALIB task within SYSVIEW. This fix also reduces the amount of messages issued when a logger or subsystem may not be available. The shared enqueues for DATALIB result in the exclusive request from the DATALIB task from ever being satisfied until all of the loggers have initialized. This in turn causes subsequent CICS region startups to hang. IMPACT: Excessive contention for the DATALIB, delays in the DATALIB taskask processing, and CICS hang during startup. In order to eliminate the enqueue conflict that may be holding other CICS regions from completing intialization, you can manually start the CICS Logger associated to the first region holding the shared enqueue against the DATALIB. This enqueue will also be the one holding up the SYSVIEW DATALIB task. PRE(RO89162) SUP(JC83864 TSE1104). ++HOLD(RO90759) FMID(CNM4E10) SYSTEM REASON(RESTART) DATE(16188) COMMENT( CA SYSVIEW Release 14.1 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 * ************************** After applying this fix either the CICS region must be recycled to pick up the change, or the following steps can be followed to implement the change dynamically: 1. Use the GSVT (terminate) transaction to stop SYSVIEW/CICS in the CICS region.
CA SYSVIEW Performance Management 14.1 7 CA RS 1608 - PTF RO90759 2. Perform a CICS NEWCOPY for program GSVCGSVI. 3. Use the GSVS (start) transaction to bring SYSVIEW/CICS back up in the CICS region. ).
CA SYSVIEW Performance Management 14.1 8 CA RS 1608 - PTF RO90835 14.1 RO90835 RO90835 M.C.S. ENTRIES = ++PTF(RO90835) DESC(COMMON/VSMTRACK ALLOC/PCT% HAS INCORRECT STATUS) Several problems exist related to the display of MVS common storage monitoring variables/thresholds. 1. The text descriptions shown for some common storage variables say they monitor the amount of common storage allocated, when in fact they represent the amount of common storage in use. The amount of storage actually being used is typically a subset of allocated storage. 2. The Information areas of the COMMON and VSMTRACK command displays contain many fields that get color-coded (a status condition) if their value exceeds a corresponding threshold definition. The wrong fields are having this status condition applied to them if thresholds are defined for any of the following variables: STGCSA STGCSAP STGECSA STGECSAP 3. Plot members are missing from the CNM4BPLT library for the following variables: STGCSAF STGECSAF STGESQAF STGSQAF 4. The PLOT command is not displaying the TITLE value if one was specified in a CNM4BPLT plotlib member. 1. The descriptions shown on the VARS and PLOTLIST command displays for the following variables use the phrase 'xxxx storage allocated' or 'unallocated', rather than storage 'used' or 'unused': JOBCSA JOBECSA JOBESQA JOBSQA STGCSA STGCSA% STGCSAF STGECSA STGECSA% STGECSAF STGSQA STGSQA% STGSQAF STGESQA STGESQA% STGESQAF 2. The Information areas of the COMMON and VSMTRACK command displays are incorrectly showing a status condition in the Alloc/Pct% fields for the E-CSA and CSA rows, rather than the Used/Pct% fields. This is working correctly for the E-SQA and SQA rows. 3. Plots for these variables were missing from the PLOTLIST command display. Also, to plot these variables you would need to enter 'PLOT MVS varname' rather than just 'PLOT varname'. 4. When displaying a pre-defined plot, the PLOT command always shows a screen title of 'Plot member - xxxxxxx' rather than the TITLE that may have been defined in the plotlib member. IMPACT: 1. A user may create improper threshold definitions for these variables due to the allocated vs. used discrepancy. 2. The displays may be misleading by incorrectly flagging the wrong fields as having exceeded a threshold. 3. Confusing command syntax for these variables. 4. A less useful title is displayed for the plot.
CA SYSVIEW Performance Management 14.1 9 CA RS 1608 - PTF RO90835 None. SUP(TSE1105).
CA SYSVIEW Performance Management 14.1 10 CA RS 1608 - PTF RO90922 14.1 RO90922 RO90922 M.C.S. ENTRIES = ++PTF(RO90922) DESC(CICS CTRANLOG RECORD MISSING DATA SEGMENTS) Due to incorrect processing of some CICS configuration options, data segments may be erroneously missing from the CICS transaction detail records that are written to CTRANLOG and/or SMF. If any of the following CICS configuration options are set to NO then that data segment, as well as other data segments, will not be included in the CICS transaction detail record: TRANSACTION-RECORD-CSF TRANSACTION-RECORD-DB2 TRANSACTION-RECORD-DLI TRANSACTION-RECORD-EXECCICS TRANSACTION-RECORD-FILES TRANSACTION-RECORD-MEI-EVENTS TRANSACTION-RECORD-PROGRAMS TRANSACTION-RECORD-RSCEMGR TRANSACTION-RECORD-TDATA TRANSACTION-RECORD-TEMPSTG TRANSACTION-RECORD-THRESHOLDS TRANSACTION-RECORD-WEBMQ Temporarily set all TRANSACTION-RECORD-xxxxx configuration options to YES on the CCONFIG command display. SUP(TSE1107). ++HOLD(RO90922) FMID(CNM4E10) SYSTEM REASON(RESTART) DATE(16189) COMMENT( CA SYSVIEW Release 14.1 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 * ************************** Apply this fix and either recycle the CICS region, or use the GSVT (terminate) and GSVS (start) transactions to recycle SYSVIEW for CICS within the CICS region. ).
CA SYSVIEW Performance Management 14.1 11 CA RS 1608 - PTF RO91004 14.1 RO91004 RO91004 M.C.S. ENTRIES = ++PTF(RO91004) DESC(EXTENTS INFO FIELD BYTES SHOWS *S0C7 W/RO86633) The Bytes field in the Information area of the EXTENTS command display is being formatted incorrectly. This problem only occurs in SYSVIEW 14.1 if PTF RO86633 is applied. The Bytes field in the Information area of the EXTENTS command display shows a value of *S0C7. The bad PTF could be RESTOREd if desired, but it resolved an actual abend which could be more intrusive than this incorrect display field. PRE(RO86633) SUP(TSE1109 AO86633).