CA SYSVIEW Performance Management 13.7 1
CA RS 1309 Service ListCA SYSVIEW Performance Management 13.7 1
CA RS 1309 Service List
Release Service 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 U299-802
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 U2999-1101 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 S002-18 / 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
CA SYSVIEW Performance Management 13.5 2
CA RS 1309 Service ListCA SYSVIEW Performance Management 13.5 2
CA RS 1309 Service List
Release Service 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 U2999-1101 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 S002-18 / 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
CA SYSVIEW Performance Management 13.0 3
CA RS 1309 Service ListCA SYSVIEW Performance Management 13.0 3
CA RS 1309 Service List
Release Service 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 U2999-1101 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
CA SYSVIEW Performance Management 12.7 4
CA RS 1309 Service ListCA SYSVIEW Performance Management 12.7 4
CA RS 1309 Service List
Release Service Description Hiper
12.7 RO49053 Loop in OUTPUT command followed by abend U0017-001
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 U2999-1101 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
CA SYSVIEW Performance Management 5
CA RS 1309 Service List for CNM4C70CA SYSVIEW Performance Management 5
CA RS 1309 Service List for CNM4C70
FMID Service Description Hiper
CNM4C70 RO49053 Loop in OUTPUT command followed by abend U0017-001
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 U2999-1101 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
CA SYSVIEW Performance Management 6
CA RS 1309 Service List for CNM4D00CA 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 U2999-1101 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
CA SYSVIEW Performance Management 7
CA RS 1309 Service List for CNM4D50CA 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 U2999-1101 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 S002-18 / 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
CA SYSVIEW Performance Management 8
CA RS 1309 Service List for CNM4D70CA 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 U299-802
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 U2999-1101 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 S002-18 / 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
CA SYSVIEW Performance Management 13.7 9
CA RS 1309 - PTF RO54175 DetailsCA SYSVIEW Performance Management 13.7 9
CA RS 1309 - PTF RO54175 Details
Release Service Details13.7 RO54175 RO54175 M.C.S. ENTRIES = ++PTF(RO54175)
DESC(Correct CCI time outs and return code processing)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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/2013 11:56:42 544BC70000000000 007D4AC8 C 001/000-FDBKError
GSV3516E send_request: CCI Error R=8 RC=09410000 XRC=000000
00 descr= ND
01/15/2013 11:56:43 544BC70000000000 00000000 D 001/000-GSV_InitReq
GSV3590I Exit Exception=2235 CCI Error: R=8 RC=00000000 XRC
=00000040 Descr= ND
The correct messages would appear as:
01/15/2013 09:54:13 516EA00000000000 007D4AC8 C 001/000-FDBKError
GSV3516E send_request: CCI Error R=8 RC=06110000 XRC=001100
00 descr=RECEIVER NOT FOUND
01/15/2013 09:54:13 516EA00000000000 00000000 D 001/000-GSV_InitReq
GSV3590I Exit Exception=2235: CCI Error R=8 RC=06110000 XRC
=00110000 descr=RECEIVER NOT FOUND
IMPACT:
Incorrect codes and descriptions causing delays in diagnosing the
root problems.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7034).
CA SYSVIEW Performance Management 13.7 10
CA RS 1309 - PTF RO54429 DetailsCA SYSVIEW Performance Management 13.7 10
CA RS 1309 - PTF RO54429 Details
Release Service Details13.7 RO54429 RO54429 M.C.S. ENTRIES = ++PTF(RO54429)
DESC(VARIOUS PROBLEMS RELATED TO CA CHORUS R3 TSF)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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 21150 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 21150 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) (127.0.0.1 29336)
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.
IMPACT:
Unnecessary errors, CPU usage, and missing help.
CIRCUMVENTION:
CA SYSVIEW Performance Management 13.7 11
CA RS 1309 - PTF RO54429 Details
Release Service DetailsNone.
PRODUCTS AFFECTED:
CA SYSVIEW r13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 12
CA RS 1309 - PTF RO56491 DetailsCA SYSVIEW Performance Management 13.7 12
CA RS 1309 - PTF RO56491 Details
Release Service Details13.7 RO56491 RO56491 M.C.S. ENTRIES = ++PTF(RO56491)
DESC(JJOBQUE/JOUTQUE/JHELDQUE No jobs displayed if PREFIX)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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 0042646E
GSVX458I NucMod GSVXFLDR Addr 0B335A88 Offset 000039E6
GSVX450I FixLvl BASE
GSVX473I Routne FMDT$$ Addr 0B3391E8 Offset 00000286
GSVX459I Data at PSW addr 0B339468
GSVX460I D2076014 B8409200 600CA7F4
GSVX455I General registers at entry to abend
GSVX467I R0-R1 00000000_00000000 00000000_00000000
GSVX467I R2-R3 00000000_00000000 00000000_0B33E4D8
GSVX467I R4-R5 00000000_00000090 00000000_00000000
GSVX467I R6-R7 00000000_00000000 00000000_0BB6C000
GSVX467I R8-R9 00000000_0BC0D000 00000000_0BBC4B10
GSVX467I R10-R11 00000000_0B33E0C8 00000000_0BB64000
GSVX467I R12-R13 00000000_0B3391E8 00000000_0BB72C48
GSVX467I R14-R15 00000000_0B339442 00000000_00000000
GSVX475I Access registers at entry to abend
GSVX461I AR0-AR3 007D65C8 00000000 00000000 00000000
GSVX461I AR4-AR7 00000000 00000000 00000000 00000000
GSVX461I AR8-AR11 00000000 00000000 00000000 00000000
GSVX461I AR12-AR15 00000000 00000000 00000000 00000000
IMPACT:
Unable to monitor jobs with LISTJOBS or LISTHELD commands.
S0C4-04 abend for JES3 system.
CIRCUMVENTION:
Issue JOUTQUE, JJOBQUE, or JHELDQUE command with parameter(s).
PRODUCTS AFFECTED:
CA SYSVIEW r13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO55171)
SUP(TSD7078).
CA SYSVIEW Performance Management 13.7 13
CA RS 1309 - PTF RO56990 DetailsCA SYSVIEW Performance Management 13.7 13
CA RS 1309 - PTF RO56990 Details
Release Service Details13.7 RO56990 RO56990 M.C.S. ENTRIES = ++PTF(RO56990)
DESC(JOBCLASS missing entries or Abend S0C4 U299-802)
/*
PROBLEM DESCRIPTION:
The JOBCLASS command may not display all job classes in 13.5 and 13.7.
Modifying field(s) in JOBCLASS display may cause S0C4 or U2999-802 abend
in 13.7.
SYMPTOMS:
Job class missing on the JOBCLASS command display in 13.5 and 13.7.
S0C4 or U2999-802 abend when modifying field(s) in JOBCLASS display in
13.7.
IMPACT:
Missing job class in 13.5 and 13.7.
S0C4 or U2999-802 abend in 13.7.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7081).
CA SYSVIEW Performance Management 13.7 14
CA RS 1309 - PTF RO57184 DetailsCA SYSVIEW Performance Management 13.7 14
CA RS 1309 - PTF RO57184 Details
Release Service Details13.7 RO57184 RO57184 M.C.S. ENTRIES = ++PTF(RO57184)
DESC(JES3 long response time when displaying many jobs)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
Unable to view detailed information on a relatively large number of jobs
without long command response times.
CIRCUMVENTION:
Issue the affected command displays with the subcommand OPTIONS NODETAIL
in effect, or with the NODETAIL command parameter.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 15
CA RS 1309 - PTF RO57212 DetailsCA SYSVIEW Performance Management 13.7 15
CA RS 1309 - PTF RO57212 Details
Release Service Details13.7 RO57212 RO57212 M.C.S. ENTRIES = ++PTF(RO57212)
DESC(ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS)
/*
PROBLEM DESCRIPTION:
Abend S0C4-3B can occur in SYSVIEW/CICS module GSVCMSCR due to the
high halves of 64-bit registers not being restored.
SYMPTOMS:
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 00004723
GSVC992E (TPPT) Abend S0C4 PSW 078C3001 A4984723 Ilc 4 Intc 3B
GSVC996E (TPPT) Registers at entry to abend
GSVC995E (TPPT) AR/GR 00:00000002_00000008 01:00000000/00000000_24FB8698
GSVC995E (TPPT) AR/GR 02:00000000_24CBDB30 03:00000000/00000000_24CBD038
GSVC995E (TPPT) AR/GR 04:00000000_00000000 05:00000000/00000000_00000000
GSVC995E (TPPT) AR/GR 06:00000000_24B243B4 07:00000000/00000000_40E7BBE0
GSVC995E (TPPT) AR/GR 08:00000000_24B2C768 09:00000000/00000000_24C7B000
GSVC995E (TPPT) AR/GR 10:00000000_24985070 11:00000000/00000003_24984588
GSVC995E (TPPT) AR/GR 12:00000000_24FB8000 13:00000000/00000000_00016528
GSVC995E (TPPT) AR/GR 14:00000000_24980203 15:00000000/00000003_24984588
GSVC998E (TPPT) End of symptom dump
IMPACT:
A dump is taken and the subtask that incurred the abend (GSVCTPPT in
the reported case) restarts.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 16
CA RS 1309 - PTF RO57260 DetailsCA SYSVIEW Performance Management 13.7 16
CA RS 1309 - PTF RO57260 Details
Release Service Details13.7 RO57260 RO57260 M.C.S. ENTRIES = ++PTF(RO57260)
DESC(MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS.)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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,
IMPACT:
Excessive amount of error messages issued to the console.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 17
CA RS 1309 - PTF RO57265 DetailsCA SYSVIEW Performance Management 13.7 17
CA RS 1309 - PTF RO57265 Details
Release Service Details13.7 RO57265 RO57265 M.C.S. ENTRIES = ++PTF(RO57265)
DESC(IMSRACT INCORRECT FIELDS FOR NON-FASTPATH REGION)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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
IMPACT:
Incorrect data may hinder debugging efforts.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 18
CA RS 1309 - PTF RO57318 DetailsCA SYSVIEW Performance Management 13.7 18
CA RS 1309 - PTF RO57318 Details
Release Service Details13.7 RO57318 RO57318 M.C.S. ENTRIES = ++PTF(RO57318)
DESC(ROSC011W Timeout waiting for ROSCOE job to respond)
/*
PROBLEM DESCRIPTION:
The ROSACT command produces the following error message:
ROSC011W Timeout waiting for ROSCOE job jjjjjjjj to respond
SYMPTOMS:
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
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 19
CA RS 1309 - PTF RO57386 DetailsCA SYSVIEW Performance Management 13.7 19
CA RS 1309 - PTF RO57386 Details
Release Service Details13.7 RO57386 RO57386 M.C.S. ENTRIES = ++PTF(RO57386)
DESC(GSV2570E running installation conversion jobs)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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
IMPACT:
Unable to run the Security Conversion or the Profile Conversion without
an error.
CIRCUMVENTION:
Run the Dynamic Install, INST0100, or start either the SYSVIEW or
the SYSVUSER address space for SYSVIEW 13.5 or SYSVIEW 13.7.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7087).
CA SYSVIEW Performance Management 13.7 20
CA RS 1309 - PTF RO57495 DetailsCA SYSVIEW Performance Management 13.7 20
CA RS 1309 - PTF RO57495 Details
Release Service Details13.7 RO57495 RO57495 M.C.S. ENTRIES = ++PTF(RO57495)
DESC(INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM)
/*
PROBLEM DESCRIPTION:
New CICS configuration option PERFORMANCE-DATA-SEGLIMIT-DB2 was
introduced in the CICSOPTS parmlib member in SYSVIEW 13.5. 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 1000.
This limit typically only matters if configuration option
PERFORMANCE-DATA-DB2-BY-PROGRAM is set to YES.
SYMPTOMS:
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 *.
IMPACT:
Reduced DB2 program call details may hinder debugging efforts.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++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 1000.
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.
).
CA SYSVIEW Performance Management 13.7 21
CA RS 1309 - PTF RO57534 DetailsCA SYSVIEW Performance Management 13.7 21
CA RS 1309 - PTF RO57534 Details
Release Service Details13.7 RO57534 RO57534 M.C.S. ENTRIES = ++PTF(RO57534)
DESC(GSVC015I Message contains incorrect jobname)
/*
PROBLEM DESCRIPTION:
Message GSVC015I in CICS JOBLOG displayed incorrect Jobname.
SYMPTOMS:
Message GSVC015I displayed CICS's job name instead of the jobname of
the connected CICSLOGR, which is typically SYSVIEW.
IMPACT:
Incorrect Jobname displayed.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 22
CA RS 1309 - PTF RO57768 DetailsCA SYSVIEW Performance Management 13.7 22
CA RS 1309 - PTF RO57768 Details
Release Service Details13.7 RO57768 RO57768 M.C.S. ENTRIES = ++PTF(RO57768)
DESC(Profile conversion problem for several JES commands)
/*
PROBLEM DESCRIPTION:
Several fields were renamed on the JJOBQUE, JHELDQUE and JOUTQUE command
displays in 13.7. 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.
SYMPTOMS:
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
IMPACT:
Unable to successfully convert profiles for these JES commands.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7091).
CA SYSVIEW Performance Management 13.7 23
CA RS 1309 - PTF RO57923 DetailsCA SYSVIEW Performance Management 13.7 23
CA RS 1309 - PTF RO57923 Details
Release Service Details13.7 RO57923 RO57923 M.C.S. ENTRIES = ++PTF(RO57923)
DESC(U2999-1101 Abend, COMMON command looping)
/*
PROBLEM DESCRIPTION:
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 U0017 001
13.0 U0017 001
13.5 U2999 1101
13.7 U2999 1101
SYMPTOMS:
The COMMON command U2999-1101 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
IMPACT:
User session terminates with U2999-1101 abend.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7093).
CA SYSVIEW Performance Management 13.7 24
CA RS 1309 - PTF RO58129 DetailsCA SYSVIEW Performance Management 13.7 24
CA RS 1309 - PTF RO58129 Details
Release Service Details13.7 RO58129 RO58129 M.C.S. ENTRIES = ++PTF(RO58129)
DESC(AUDIT/IMS reports and FROM/TO commands showing wrong times)
/*
PROBLEM DESCRIPTION:
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
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
1. None.
2. 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
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO56233)
SUP(TSD7094).
CA SYSVIEW Performance Management 13.7 25
CA RS 1309 - PTF RO58356 DetailsCA SYSVIEW Performance Management 13.7 25
CA RS 1309 - PTF RO58356 Details
Release Service Details13.7 RO58356 RO58356 M.C.S. ENTRIES = ++PTF(RO58356)
DESC(CSTATES SYSTEM command orphans storage)
/*
PROBLEM DESCRIPTION:
Issuing the CSTATES SYSTEM command can causes memory leaks, where
duplicate buffers of data are being created with only one getting freed.
SYMPTOMS:
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.
IMPACT:
Unable to allocate any additional private storage when the storage limit
is exceeded.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7096).
CA SYSVIEW Performance Management 13.7 26
CA RS 1309 - PTF RO58431 DetailsCA SYSVIEW Performance Management 13.7 26
CA RS 1309 - PTF RO58431 Details
Release Service Details13.7 RO58431 RO58431 M.C.S. ENTRIES = ++PTF(RO58431)
DESC(ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
No further monitoring of MQ requests will be performed.
CIRCUMVENTION:
Specify MONITOR-MQS-REQUESTS NO in the MQSDATA parmlib member
to disable MQ request monitoring.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7097).
CA SYSVIEW Performance Management 13.7 27
CA RS 1309 - PTF RO58486 DetailsCA SYSVIEW Performance Management 13.7 27
CA RS 1309 - PTF RO58486 Details
Release Service Details13.7 RO58486 RO58486 M.C.S. ENTRIES = ++PTF(RO58486)
DESC(XMDR002W NRAS buffer max of 256K reached)
/*
PROBLEM DESCRIPTION:
When issuing the ASLIST or ASLOST command it is possible the command
may produce error messages indicating the 256K buffer max has been
reached.
SYMPTOMS:
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 ????????
IMPACT:
No results produced by command.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++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.
).
CA SYSVIEW Performance Management 13.7 28
CA RS 1309 - PTF RO58501 DetailsCA SYSVIEW Performance Management 13.7 28
CA RS 1309 - PTF RO58501 Details
Release Service Details13.7 RO58501 RO58501 M.C.S. ENTRIES = ++PTF(RO58501)
DESC(MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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
IMPACT:
Unable to execute functions that require the Main Services
(SYSVIEW) address space.
CIRCUMVENTION:
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.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7099).
CA SYSVIEW Performance Management 13.7 29
CA RS 1309 - PTF RO58543 DetailsCA SYSVIEW Performance Management 13.7 29
CA RS 1309 - PTF RO58543 Details
Release Service Details13.7 RO58543 RO58543 M.C.S. ENTRIES = ++PTF(RO58543)
DESC(JES SPOOL USED PERCENTAGE CALCULATED INCORRECTLY)
/*
PROBLEM DESCRIPTION:
The SPOOL space used percent was not being calculated correctly. It
was including INACTIVE spool volumes in the calculation.
SYMPTOMS:
Incorrect SPOOL space used percentage shown on JSPOOLS, JRESOURC, and
SYSTEMS command displays.
IMPACT:
Incorrect used SPOOL percentage shown.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7100)
PRE(RO56990).
CA SYSVIEW Performance Management 13.7 30
CA RS 1309 - PTF RO58589 DetailsCA SYSVIEW Performance Management 13.7 30
CA RS 1309 - PTF RO58589 Details
Release Service Details13.7 RO58589 RO58589 M.C.S. ENTRIES = ++PTF(RO58589)
DESC(IMS DLI variable totals display incorrectly greater than 2G)
/*
PROBLEM DESCRIPTION:
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)
SYMPTOMS:
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
IMPACT:
Unable to accurately display IMS DLI variable metrics when the total
values exceed 2,147,483,647 (2G-1).
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO55807,RO56233)
SUP(TSD7101).
CA SYSVIEW Performance Management 13.7 31
CA RS 1309 - PTF RO58616 DetailsCA SYSVIEW Performance Management 13.7 31
CA RS 1309 - PTF RO58616 Details
Release Service Details13.7 RO58616 RO58616 M.C.S. ENTRIES = ++PTF(RO58616)
DESC(compatibility support for future XSYSTEM changes)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
Possibly unable to gather cross-system data between mixed releases
of SYSVIEW.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7102).
CA SYSVIEW Performance Management 13.7 32
CA RS 1309 - PTF RO58670 DetailsCA SYSVIEW Performance Management 13.7 32
CA RS 1309 - PTF RO58670 Details
Release Service Details13.7 RO58670 RO58670 M.C.S. ENTRIES = ++PTF(RO58670)
DESC(IMSTRANS not showing USTOPPED status for transactions)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO55087)
SUP(TSD7103).
CA SYSVIEW Performance Management 13.7 33
CA RS 1309 - PTF RO58800 DetailsCA SYSVIEW Performance Management 13.7 33
CA RS 1309 - PTF RO58800 Details
Release Service Details13.7 RO58800 RO58800 M.C.S. ENTRIES = ++PTF(RO58800)
DESC(Fields not populated in IMSIMTR transaction record DSECT)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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
IMPACT:
Could cause errors in user-written batch reports.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++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
).
CA SYSVIEW Performance Management 13.7 34
CA RS 1309 - PTF RO59009 DetailsCA SYSVIEW Performance Management 13.7 34
CA RS 1309 - PTF RO59009 Details
Release Service Details13.7 RO59009 RO59009 M.C.S. ENTRIES = ++PTF(RO59009)
DESC(Display does not update properly when PREFIX values changed)
/*
PROBLEM DESCRIPTION:
The display does not update properly when the PREFIX values changed
for the following JES commands:
JJOBQUE, JHELDQUE, JOUTQUE, JTRANQUE, JOBSUM, LISTINP, and ACTIVITY
SYMPTOMS:
Changing PREFIX values may cause JES command display to update with
incompleted or no data.
IMPACT:
Incorrect information displayed.
CIRCUMVENTION:
Switch to a different display and back.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO56491, RO56369)
SUP(TSD7107).
CA SYSVIEW Performance Management 13.7 35
CA RS 1309 - PTF RO59084 DetailsCA SYSVIEW Performance Management 13.7 35
CA RS 1309 - PTF RO59084 Details
Release Service Details13.7 RO59084 RO59084 M.C.S. ENTRIES = ++PTF(RO59084)
DESC(IMTSQUE threshold not working for IMS shared queues)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
Unable to monitor IMS message queue depth in shared queue environment.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO55339)
SUP(TSD7108).
CA SYSVIEW Performance Management 13.7 36
CA RS 1309 - PTF RO59346 DetailsCA SYSVIEW Performance Management 13.7 36
CA RS 1309 - PTF RO59346 Details
Release Service Details13.7 RO59346 RO59346 M.C.S. ENTRIES = ++PTF(RO59346)
DESC(XSCONN command fails from ISPF interface)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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
IMPACT:
Unable to connect to a different instance of SYSVIEW from the ISPF
interface when issuing the XSCONN command.
CIRCUMVENTION:
Issue the XSCONN command from the TSO or VTAM interface.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO58616)
SUP(TSD7109).
CA SYSVIEW Performance Management 13.7 37
CA RS 1309 - PTF RO59417 DetailsCA SYSVIEW Performance Management 13.7 37
CA RS 1309 - PTF RO59417 Details
Release Service Details13.7 RO59417 RO59417 M.C.S. ENTRIES = ++PTF(RO59417)
DESC(Abend S0F8-04 issuing LOGREC CLEAR subcommand)
/*
PROBLEM DESCRIPTION:
The CLEAR subcommand of the LOGREC command results in an
abend S0F8-04 when running in zIIP mode.
SYMPTOMS:
Issuing the CLEAR subcommand from the LOGREC display
results in an abend S0F8-04.
The following messages will be seen in the JES job log
of the user's session:
GSVX451E Abend S0F8-04 in LOGREC/CLEAR command
GSVX472I Userid userid Terminal terminal Interface intf
GSVX452I SYSVIEW SRB in control at entry to abend
GSVX453I Diagnostics for SRB in control at entry to abend
GSVX457I Psw 078C1000 address1 Ilc 2 Intc 2A
GSVX477I Key 8 State SUP Am 31 Asc PRI
GSVX458I Module GSVKLOGC Addr address2 Offset <offset>
GSVX450I FixLvl BASE
GSVX473I Routne CALL$$ Addr address3 Offset 0000009E
<offset> = 000004DE at SYSVIEW 13.5.
<offset> = 00000536 at SYSVIEW 13.7.
IMPACT:
1. The user's SYSVIEW session will abend and need to be
restarted ... AND ...
2. It is not possible to use SYSVIEW to clear the
SYS1.LOGREC data set.
CIRCUMVENTION:
1. Use IBM's IFCDIP00 program to clear the SYS1.LOGREC
data set ... OR ...
2. Set zIIPEnable in the OPTIONS member of parmlib to
NO and recycle your SYSVIEW session.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70) SUP(TSD7110).
CA SYSVIEW Performance Management 13.7 38
CA RS 1309 - PTF RO59437 DetailsCA SYSVIEW Performance Management 13.7 38
CA RS 1309 - PTF RO59437 Details
Release Service Details13.7 RO59437 RO59437 M.C.S. ENTRIES = ++PTF(RO59437)
DESC(JOBNAME and SYSID ID Options return incorrect data)
/*
PROBLEM DESCRIPTION:
Two problems exist related to EXPLORE Report Writer ID Options.
1. The JOBNAME ID Option does not filter SYSVIEW/CICS System Interval
SMF records (subtype 28) when used with the SELECT command.
2. The SYSID ID option does not allow any records to be returned on a
report when used with the SELECT command.
SYMPTOMS:
1. When using the JOBNAME ID Option to filter SYSVIEW/CICS System
Interval SMF records (subtype 28), it appears that no filtering on the
JOBNAME has taken place when the report is ran.
2. When using the SYSID ID Option to filter SMF records, no records are
returned on the report. The following message may be seen in the report
output:
ERPT221E NO MATCHING DATA
IMPACT:
1. Unable to filter SYSVIEW/CICS System Interval SMF records
(subtype 28) with the JOBNAME ID Option.
2. Unable to filter SMF records with the SYSID ID Option.
CIRCUMVENTION:
1. Use the JOBID ID Option in place of the JOBNAME ID Option.
2. Specify an asterisk (*) after the system name parameter desired. For
example, if the system name desired is 'SYSA', then specify the ID
Option as 'SYSID(SYSA*)'.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7111).
CA SYSVIEW Performance Management 13.7 39
CA RS 1309 - PTF RO59445 DetailsCA SYSVIEW Performance Management 13.7 39
CA RS 1309 - PTF RO59445 Details
Release Service Details13.7 RO59445 RO59445 M.C.S. ENTRIES = ++PTF(RO59445)
DESC(Abend S0C4 dumping address in PAGES or SEGMENTS display)
/*
PROBLEM DESCRIPTION:
Abend S0C4-10 occurs when attempting to dump storage from the PAGES or
SEGMENTS command displays. This is done by placing the cursor within
the Status field area and hitting enter to dump that page or segment.
SYMPTOMS:
User session gets abend S0C4-10 with messages similar to the following:
GSVX451E Abend S0C4-10 in PAGES/REFRESH command
GSVX472I Userid userid Terminal A55TG001 Interface VTAM
GSVX457I Psw 078C0000 BB43B66A Ilc 4 Intc 10
GSVX477I Key 8 State SUP Am 31 Asc PRI
GSVX458I Module GSVKPAGE Addr 3B43A6D8 Offset 00000F92
GSVX450I FixLvl BASE
GSVX473I Routne REFR$$ Addr 3B43B5D0 Offset 0000009A
GSVX459I Data at PSW addr 3B43B664
GSVX460I 12FFA774 0023BF1F 10201A31
GSVX455I General registers at entry to abend
GSVX467I R0-R1 00000000_00000075 00000050_805B2EFF
GSVX467I R2-R3 00000000_00000000 00000000_00002000
GSVX467I R4-R5 00000000_00000018 00000000_0000004F
GSVX467I R6-R7 00000000_3BFC7C50 00000000_00000000
GSVX467I R8-R9 00000000_3BC73B80 00000000_3BA8A9B0
GSVX467I R10-R11 00000000_3B43B730 00000000_3B623000
GSVX467I R12-R13 00000000_3B43B5D0 00000000_3B3C0130
GSVX467I R14-R15 00000000_BB43B664 00000000_00000000
GSVX475I Access registers at entry to abend
GSVX461I AR0-AR3 00000000 00000000 00000000 00000000
GSVX461I AR4-AR7 00000000 00000000 00000000 00000000
GSVX461I AR8-AR11 00000000 00000000 00000000 00000000
GSVX461I AR12-AR15 00000000 00000000 00000000 00000000
GSVX462I End of symptom dump
GSVX950I SVCDUMP requested
GSVX954I Issuing SDUMPX to capture SVC dump
GSVX959I SDUMPX complete, SVC dump captured
IMPACT:
User section abend abends and terminates.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7112).
CA SYSVIEW Performance Management 13.7 40
CA RS 1309 - PTF RO59628 DetailsCA SYSVIEW Performance Management 13.7 40
CA RS 1309 - PTF RO59628 Details
Release Service Details13.7 RO59628 RO59628 M.C.S. ENTRIES = ++PTF(RO59628)
DESC(LGCONN/LGJOBS cmds not showing data with IBM zAware)
/*
PROBLEM DESCRIPTION:
The LGCONN and LGJOBS commands will not display any data when issued on
a system running z/OS 1.13 which contains support for the z/OS IBM
zAware log stream client as described in IBM APAR OA38747.
SYMPTOMS:
The activation of zAware will cause the output of the following MVS
display commands to generate new data:
DISPLAY LOGGER,CONNECTION,LSNAME=*,DETAIL LGCONN
DISPLAY LOGGER,CONNECTION,JOBNAME=*,DETAIL LGJOBS
This essentially causes the LGCONN and LGJOBS commands to not display
any data.
IMPACT:
Unable to display any data on the LGCONN and LGLOGS command displays.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7114).
CA SYSVIEW Performance Management 13.7 41
CA RS 1309 - PTF RO59631 DetailsCA SYSVIEW Performance Management 13.7 41
CA RS 1309 - PTF RO59631 Details
Release Service Details13.7 RO59631 RO59631 M.C.S. ENTRIES = ++PTF(RO59631)
DESC(IMS Transaction missing from IMSTLOG)
/*
PROBLEM DESCRIPTION:
A transaction sends out secondary requests to non-LTERM devices. These
requests are treated as transaction responses which causes the transaction
to be queued in the IMSLOGR dataspace waiting for the transactions output
to be read which will never occur.
SYMPTOMS:
IMS transaction does not show up in IMSTLOG. It is queued in the IMSLOGR
dataspace waiting for output messages.
IMPACT:
Unable to monitor IMS transaction.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO58800)
SUP(TSD7115).
CA SYSVIEW Performance Management 13.7 42
CA RS 1309 - PTF RO59673 DetailsCA SYSVIEW Performance Management 13.7 42
CA RS 1309 - PTF RO59673 Details
Release Service Details13.7 RO59673 RO59673 M.C.S. ENTRIES = ++PTF(RO59673)
DESC(JCOPYOUT abend S002-18 / record length incorrect)
/*
PROBLEM DESCRIPTION:
Two problems exist related to the JCOPYOUT command.
1. Abend S002-18 is possible when using the JCOPYOUT command. This
problem will occur if the record length field is either blank (null)
or less than 5 when the copy request is submitted.
2. When using the JCOPYOUT command, the record length of the source
data set may be incorrectly increased by 4 bytes in the target data
set. This problem will only occur when copying a variable record
length data set to another variable record length data set.
SYMPTOMS:
1. When using the JCOPYOUT command, the following message may be
displayed in the message area:
OSRV005E OS services module abended S002-18
After the abend S002-18 occurs, other subsequent abends may follow.
One or more of following messages may appear in the user's job log
indicating those abends:
GSVX451E Abend S0C6-06 in TERMINAT command
GSVX451E Abend S0C4-3B in TERMINAT command
GSVX451E Abend U2999-802 in JCOPYOUT command
2. After using the JCOPYOUT command to copy a variable record length
data set to another variable record length data set, the record
length of the target data set is 4 bytes longer than the record
length of the source data set.
IMPACT:
1. Possible abends using JCOPYOUT command.
2. Unable to prevent the record length of a data set from increasing
when using the JCOPYOUT command to copy a variable record length
data set to another.
CIRCUMVENTION:
1. Specify a valid record length greater than 4 when using the
JCOPYOUT command.
2. None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7116).
CA SYSVIEW Performance Management 13.7 43
CA RS 1309 - PTF RO59735 DetailsCA SYSVIEW Performance Management 13.7 43
CA RS 1309 - PTF RO59735 Details
Release Service Details13.7 RO59735 RO59735 M.C.S. ENTRIES = ++PTF(RO59735)
DESC(PERFORMANCE IMPROVEMENT FOR IMSOVER COMMAND)
/*
PROBLEM DESCRIPTION:
The IMSOVER command provides a summary of many IMS resources such as
databases, PSBs, transactions and locks. When an IMS has many
instances of a resource (tens of thousands) the IMSOVER command can
take a while to complete and uses more CPU. The IMSDATA collector
subtask is also subject to more CPU usage for those resources it is
monitoring. Additionally, CA Cross Enterprise APM issues the
SYSVIEW IMSOVER command periodically for it's dashboards, and this
request from CE APM has been seen to occasionally time out.
This fix will make code changes to streamline the gathering of
summary data for databases and PSBs, which will improve performance
of the IMSOVER command and the IMSDATA subtask.
SYMPTOMS:
In the reported case the following errors were occurring in the
WILYZOS job log due to IMSOVER taking too long to return:
5/07/13 11:48:25 AM EDT ÝERROR¨ Ýcom.wily.powerpack.sysview.metrics.
SysviewXAPIWrapper¨ The XAPI facility of SYSVIEW had a problem
causing an internal exception. Reason: req.initreq XapiReason
exception=1781 XAPI RC=8, RSN=29, Text=SYSV_XAPI_GNRL_REQUEST_TIMEOUT
5/07/13 11:48:25 AM EDT ÝERROR¨ Ýcom.wily.powerpack.sysview.metrics.
SysviewXAPIWrapper¨ The SYSVIEW command that failed was: ÝIMSOVER¨
IMPACT:
Unnecessary overhead in the SYSVUSER STC when using Cross Enterprise
(CE) APM for IMS, or the above timeout condition would result in
missing data in the APM dashboard.
Unnecessary overhead in the SYSVIEW STC for the IMSDATA subtask.
Unnecessary overhead in a SYSVIEW user session when issuing the
IMSOVER command.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO53671 RO58670)
SUP(RO52603 RO54305 TSD7118).
CA SYSVIEW Performance Management 13.7 44
CA RS 1309 - PTF RO59843 DetailsCA SYSVIEW Performance Management 13.7 44
CA RS 1309 - PTF RO59843 Details
Release Service Details13.7 RO59843 RO59843 M.C.S. ENTRIES = ++PTF(RO59843)
DESC(ASLIST MAXUSER counts and %-ages do not add up)
/*
PROBLEM DESCRIPTION:
The counts and percentages shown on the MAXUSER line of the
ASLIST command display may not add up correctly.
SYMPTOMS:
When address spaces are lost and replaced by reserved address
spaces, the counts and percentages on the MAXUSER line of the
ASLIST display may not add up correctly. This will be
especially noticeable when the number of "Lost" address
spaces is high. For example:
Jobname SYSVUSER ASID 049C Jobid STC37943
Queue Count Used/Pct% Free/Pct% Lost/Pct%
MAXUSER 1500 568 37% 1116 74% 952 63% <====
RSVSTRT 20 0 0% 20 100% 0 0%
RSVNONR 1000 952 95% 48 5% 0 0%
The number of Lost address spaces will be correct.
The number of Used and Free address spaces will be
incorrect, and the percentages shown for all three
will also be incorrect.
Address spaces may be lost due to a job ending with outstanding
cross-memory binds or LX Table entries.
IMPACT:
The user will be unable to determine the number of Used or
Free address spaces.
CIRCUMVENTION:
The correct count of Used address spaces may be obtained by
issuing an ACTIVITY command with no filtering.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO54995) SUP(TSD7119).
CA SYSVIEW Performance Management 13.7 45
CA RS 1309 - PTF RO59859 DetailsCA SYSVIEW Performance Management 13.7 45
CA RS 1309 - PTF RO59859 Details
Release Service Details13.7 RO59859 RO59859 M.C.S. ENTRIES = ++PTF(RO59859)
DESC(GSVX554E WHEN XSYS CMD W/ NOXSDATA BUT XSYSTEM IS DISABLED)
/*
PROBLEM DESCRIPTION:
Issuing a cross system command with the NOXSDATA parameter specified when
the XSYSTEM feature is disabled may cause an error message to be generated.
SYMPTOMS:
The following error message may appear when a cross-system capable
command is issued with the NOXSDATA option and the XSYSTEM feature is
already disabled.
GSVX554E MXSCR SET_XSDATA_OFF failed, The XSYS feature is not enabled
IMPACT:
None.
CIRCUMVENTION:
Issue the commands without NOXSDATA or enable the XSYSTEM feature in
the systems configuration parmlib member.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO59346)
SUP(TSD7120).
CA SYSVIEW Performance Management 13.7 46
CA RS 1309 - PTF RO59920 DetailsCA SYSVIEW Performance Management 13.7 46
CA RS 1309 - PTF RO59920 Details
Release Service Details13.7 RO59920 RO59920 M.C.S. ENTRIES = ++PTF(RO59920)
DESC(CICSOPTS option MONITOR-RESTORE-SETTINGS handled incorrectly)
/*
PROBLEM DESCRIPTION:
When the MONITOR-RESTORE-SETTINGS option is explicitly set in the CICS
configuration parmlib member (CICSOPTS), it behaves the opposite of how
it is documented to function.
SYMPTOMS:
Setting the MONITOR-RESTORE-SETTINGS option to NO works as though
the option were set to YES.
Setting the MONITOR-RESTORE-SETTINGS option to YES works as though
the option were set to NO.
Note: If the MONITOR-RESTORE-SETTINGS option is not explicitly set in
the CICSOPTS member, but is allowed to default to YES, the option
functions correctly.
IMPACT:
Example 1:
----------
With the following settings:
- The MNEXC option in the CICS system initialization table (SIT)
Is set to NO.
- The MONITOR-EXCEPTIONS option in the CICSOPTS parmlib member
is set to CICS.
- The MONITOR-RESTORE-SETTINGS option in the CICSOPTS parmlib
member is set to NO.
The result is:
After SYSVIEW monitoring in the CICS address space has been stopped,
CICS exception records will continue to be suppressed. This will be
true even if SYSVIEW monitoring in the CICS address space is
subsequently restarted.
Example 2:
----------
With the following settings:
- The MNEXC option in the CICS system initialization table (SIT)
is set to NO.
- The MONITOR-EXCEPTIONS option in the CICSOPTS parmlib member
is set to CICS.
- The MONITOR-RESTORE-SETTINGS option in the CICSOPTS parmlib
member is set to YES.
The result is:
After SYSVIEW monitoring in the CICS address space has been stopped,
CICS exception records will no longer be suppressed. This will be
true even if SYSVIEW monitoring in the CICS address space is
subsequently restarted.
CIRCUMVENTION:
If the desired setting of the MONITOR-RESTORE-SETTINGS option is YES,
then remove the explicit specification from the parmlib member and
allow it to default to YES.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO57495)
SUP(TSD7121).
++HOLD(RO59920) FMID(CNM4D70)
SYSTEM
REASON(ACTION)
DATE(13163)
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.
).
CA SYSVIEW Performance Management 13.7 47
CA RS 1309 - PTF RO59976 DetailsCA SYSVIEW Performance Management 13.7 47
CA RS 1309 - PTF RO59976 Details
Release Service Details13.7 RO59976 RO59976 M.C.S. ENTRIES = ++PTF(RO59976)
DESC(Abend S0C4 in Data Collection or IMSLOCKS command)
/*
PROBLEM DESCRIPTION:
Abend S0C4 when running the IMS Lock chain.
SYMPTOMS:
The IMSLOCKS command scans through some IMS-related control
blocks which can change while SYSVIEW is looking at them.
This requires that SYSVIEW code be protected by an ESTAE so
it can recover from any abends. It was found that no such
protection was in place when running the IMS Lock chain.
The IMSLOCKS command may be issued:
- Directly by the user,
- Indirectly ("under the covers") by the SYSVIEW internal
Data Collection function.
- Indirectly ("under the covers") by two SYSVIEW IMS-related
commands:
IMSOVER
IMSRACT
If the abend occurs during IMS Data Collection, the following
messages will be seen on the SYSVIEW job log:
GSVX451E (IMSDATA) Abend S0C4-nn in IMS data collector
GSVX452I (IMSDATA) SYSVIEW SRB in control at entry to abend
GSVX453I (IMSDATA) Diagnostics for SRB in control at entry to abend
GSVX457I (IMSDATA) Psw 070C6001 <address1> Ilc 6 Intc 38
GSVX477I (IMSDATA) Key 0 State SUP Am 64 Asc AR
GSVX458I (IMSDATA) Module GSVPDBxx Addr <address2> Offset <offset1>
GSVX450I (IMSDATA) FixLvl <rmid>
GSVX473I (IMSDATA) Routne LKyy$$ Addr <address3> Offset <offset2>
GSVX459I (IMSDATA) Data at PSW addr <address4>
GSVX460I (IMSDATA) E34092A0 0024E310 40200004
GSVX594I (MAIN) IMSDATA task abended, completion code S0C4-nn
GSVX574I (MAIN) IMSDATA task termination complete
GSVX592W (MAIN) RESTART IMSDATA not supported
Note: The 'xx' in GSVPDBxx can be 10, 11, 12, or 13,
depending on the release of IMS being used.
Note: The 'yy' in LKyy$$ can be 31 or 64, depending on
whether the locks are in 31 bit or 64 bit storage.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, messages similar to the above will be seen
on the user's terminal, but the GSVX451E message will be one of
the following:
GSVX451E Abend S0C4-nn in IMSLOCKS command
GSVX451E Abend S0C4-nn in IMSOVER command
GSVX451E Abend S0C4-nn in IMSRACT command
IMPACT:
If the abend occurs during IMS Data Collection, the IMSDATA task
will abend. Since an automatic restart of the IMSDATA task is
not allowed, IMS data collection will cease and no further IMS
monitoring will be done until the IMSDATA task is manually
restarted from the ASADMIN command display.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, the user's session will abend and need to be
restarted.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO58670) SUP(TSD7122).
CA SYSVIEW Performance Management 13.7 48
CA RS 1309 - PTF RO60141 DetailsCA SYSVIEW Performance Management 13.7 48
CA RS 1309 - PTF RO60141 Details
Release Service Details13.7 RO60141 RO60141 M.C.S. ENTRIES = ++PTF(RO60141)
DESC(SELECT with CW and NW not supporting multiple operands)
/*
PROBLEM DESCRIPTION:
The SELECT command may not work correctly when using the CW or NW operands,
followed by another operand.
SYMPTOMS:
The SELECT command displays incorrect information when used with the
CW (Contains Word) or NW (Not contains Word) operands, followed by another
operand.
For example, issuing the following command in the JJOBQUE command display:
SELECT queue cw execute or status eq heldcls
results in the following:
- The JJOBQUE display is filtered using only the CW operand
("queue CW execute").
- The EQ operand ("status EQ heldcls") is ignored.
- All jobs with a Queue field of "execute" are displayed, regardless of the
value in the Status field.
IMPACT:
Users are unable to select correctly using the CW and NW operands.
CIRCUMVENTION:
Do not use the CW or NW operands in a SELECT command unless they are the
final operands in the command.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO54185)
SUP(TSD7125).
CA SYSVIEW Performance Management 13.7 49
CA RS 1309 - PTF RO60173 DetailsCA SYSVIEW Performance Management 13.7 49
CA RS 1309 - PTF RO60173 Details
Release Service Details13.7 RO60173 RO60173 M.C.S. ENTRIES = ++PTF(RO60173)
DESC(TSUMRATE always displays zeros in CSTATUS)
/*
PROBLEM DESCRIPTION:
The CICS metric TSUMRATE is not being populated, which results in the
metric always displaying a value of zeros on the CSTATUS command display.
SYMPTOMS:
The status of the TSUMRATE metric will remain as NORMAL on the CSTATUS
display, which will cause the TSUMRATE threshold exception to never get
triggered.
IMPACT:
Unable to correctly display TSUMRATE values on the CSTATUS display.
Unable to trigger a TSUMRATE threshold exception.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7126).
++HOLD(RO60173) FMID(CNM4D70)
SYSTEM
REASON(ACTION)
DATE(13171)
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.
).
CA SYSVIEW Performance Management 13.7 50
CA RS 1309 - PTF RO60200 DetailsCA SYSVIEW Performance Management 13.7 50
CA RS 1309 - PTF RO60200 Details
Release Service Details13.7 RO60200 RO60200 M.C.S. ENTRIES = ++PTF(RO60200)
DESC(IMSTLOG abended transactions not showing correct tran type)
/*
PROBLEM DESCRIPTION:
IMS transactions that have abended may be showing the incorrect
transaction types on the IMSTLOG command display.
SYMPTOMS:
An abended IMS transaction should be indicated by a value of A (Program
abend or unconnected transaction) as the transaction type on IMSTLOG
display.
IMPACT:
Unable to determine if an IMS transaction has abended or not.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO59631)
SUP(TSD7127).
++HOLD(RO60200) FMID(CNM4D70)
SYSTEM
REASON(DYNACT)
DATE(13175)
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
).
CA SYSVIEW Performance Management 13.7 51
CA RS 1309 - PTF RO60780 DetailsCA SYSVIEW Performance Management 13.7 51
CA RS 1309 - PTF RO60780 Details
Release Service Details13.7 RO60780 RO60780 M.C.S. ENTRIES = ++PTF(RO60780)
DESC(Possible looping in dependent region during shutdown)
/*
PROBLEM DESCRIPTION:
A possible looping condition exists during the termination of an
IMS dependent region that is being monitored by SYSVIEW. This
problem results in the region entering a loop and not terminating.
SYMPTOMS:
The dependent region does not shut down and enters a loop. Review
of a dump for the region would show continuous looping condition in
GSVXPLnn (where nn may be 10, 11, 12, or 13).
IMPACT:
IMS dependent region outage as a result of the looping condition
and may need cancelled in order to shut down.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
SUP(TSD7133 AR60832)
PRE(RO60200).
++HOLD(RO60780) FMID(CNM4D70)
SYSTEM
REASON(DYNACT)
DATE(13190)
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
).
CA SYSVIEW Performance Management 13.7 52
CA RS 1309 - PTF RO61542 DetailsCA SYSVIEW Performance Management 13.7 52
CA RS 1309 - PTF RO61542 Details
Release Service Details13.7 RO61542 RO61542 M.C.S. ENTRIES = ++PTF(RO61542)
DESC(GSVX753I ALET ADD MESSAGE LOGGING ON W/RO61045)
/*
PROBLEM DESCRIPTION:
Message GSVX753I message is erroneously displayed to the user when
logging on to SYSVIEW as well as being issued to SYSVIEW JOBLOG and
SYSLOG after applying PTF RO61045.
SYMPTOMS:
GSVX753I message is received when initially logging on to SYSVIEW,
JOBLOG, and SYSLOG instead of only being sent to LISTLOG.
GSVX753I*ALET ADD TCB 007EDA28 ASCB 00EF7400 SToken 00000E9C00000B0E
ALET 001D0004
IMPACT:
Message sent to wrong destination.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.7
*/.
++VER(Z038) FMID(CNM4D70)
PRE(RO61045)
SUP(AR61045 TSD7147).
CA SYSVIEW Performance Management 13.5 53
CA RS 1309 - PTF RO49066 DetailsCA SYSVIEW Performance Management 13.5 53
CA RS 1309 - PTF RO49066 Details
Release Service Details13.5 RO49066 RO49066 M.C.S. ENTRIES = ++PTF(RO49066)
DESC(GSVX031E & abend S306-0C when SCSQLOAD not APF auth'ed)
/*
PROBLEM DESCRIPTION:
The following message will be issued if the IBM WebSphere
MQ SCSQLOAD data set is not APF authorized:
GSVX031E*LOAD failed for module CSQBBACK, abend S306-0C
SYMPTOMS:
When a SYSVIEW MQ command is entered, message GSVX031E detailing
an abend S306-0C will be received by the issuer of the MQ command.
The user's session will not abend, but it will not be possible for
them to enter any MQ-related commands.
Also, any services in the SYSVIEW address space which require MQ
commands will receive the following error messages, which will
appear in the SYSVIEW job log:
GSVX998E MQSR001E Load for WebSphere MQ interface module
CSQBBACK failed
GSVX998E MQSR002E UNKNOWN command failed, MQ services
initialization failed
IMPACT:
Unable to enter any of SYSVIEW's MQ commands.
CIRCUMVENTION:
APF authorize MQ's SCSQLOAD data set.
PRODUCTS AFFECTED:
CA SYSVIEW r13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO44329) SUP(TSD5100).
CA SYSVIEW Performance Management 13.5 54
CA RS 1309 - PTF RO55670 DetailsCA SYSVIEW Performance Management 13.5 54
CA RS 1309 - PTF RO55670 Details
Release Service Details13.5 RO55670 RO55670 M.C.S. ENTRIES = ++PTF(RO55670)
DESC(CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd)
/*
PROBLEM DESCRIPTION:
On the CPROGRAM command display, issuing a NEWCOPY or PHASEIN line
command against a CICS program that is currently not in use causes
the program size field to be zero.
SYMPTOMS:
After a CICS program has been PHASED-in or NEWCOPY'd, the program
size will display a zero or blanks until the next program is invoked.
IMPACT:
Unable to display the program size after a NEWCOPY or PHASEIN line
command is issued against a CICS program that is not in use.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5179).
CA SYSVIEW Performance Management 13.5 55
CA RS 1309 - PTF RO56326 DetailsCA SYSVIEW Performance Management 13.5 55
CA RS 1309 - PTF RO56326 Details
Release Service Details13.5 RO56326 RO56326 M.C.S. ENTRIES = ++PTF(RO56326)
DESC(Incorrect Parms passed to Trap & Capture for CICS threshold)
/*
PROBLEM DESCRIPTION:
In r13.5, terminal id and userid were removed from the the list
of parameters passed to message text of SNMP trap or capture data
when a CICS theshold is triggered.
SYMPTOMS:
Missing terminal ID and userID in message text of SNMP trap and
capture data.
IMPACT:
Missing CICS information in SNMP trap and capture data.
CIRCUMVENTION:
None
PRODUCTS AFFECTED:
CA SYSVIEW r13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO55535)
SUP(TSD5184).
CA SYSVIEW Performance Management 13.5 56
CA RS 1309 - PTF RO56427 DetailsCA SYSVIEW Performance Management 13.5 56
CA RS 1309 - PTF RO56427 Details
Release Service Details13.5 RO56427 RO56427 M.C.S. ENTRIES = ++PTF(RO56427)
DESC(JES3 JOBSUM command not returning all requested jobs)
/*
PROBLEM DESCRIPTION:
The JOBSUM command display may not display the actual number of jobs
available. This problem occurs only on JES3 systems.
SYMPTOMS:
On JES3 systems, the JOBSUM command display may return a lower number of
jobs than available. The number of jobs returned may vary by a
significant number by refreshing the display.
IMPACT:
Unable to retrieve consistent job information on JES3 systems.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO55441)
SUP(TSD5185).
CA SYSVIEW Performance Management 13.5 57
CA RS 1309 - PTF RO56619 DetailsCA SYSVIEW Performance Management 13.5 57
CA RS 1309 - PTF RO56619 Details
Release Service Details13.5 RO56619 RO56619 M.C.S. ENTRIES = ++PTF(RO56619)
DESC(DEST command not working properly for JES3)
/*
PROBLEM DESCRIPTION:
Using DEST command to filter jobs or devices to be displayed is working
improperly for JES3.
SYMPTOMS:
The DEST command is not working for the following SYSVIEW commands:
JOBSUM
LISTINP
An error message similar to the following can be observed when issuing the
DEST command in the above command displays for JES3:
GSV3725W xxxxxx command not supported for JES3
IMPACT:
Unable to use the DEST command to filter jobs or devices for the above
commands.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO43574,RO56427)
SUP(TSD5186).
CA SYSVIEW Performance Management 13.5 58
CA RS 1309 - PTF RO56815 DetailsCA SYSVIEW Performance Management 13.5 58
CA RS 1309 - PTF RO56815 Details
Release Service Details13.5 RO56815 RO56815 M.C.S. ENTRIES = ++PTF(RO56815)
DESC(Incorrect Parms passed to OPSMVS when CICS threshold triggers)
/*
PROBLEM DESCRIPTION:
In r13.5, terminal id and userid were removed from the list of
parameters passed as message text on OPS/MVS event when a CICS
threshold is triggered.
There are also several sample GSS IMODs that parse the provided
parameters when a threshold is triggered, and the list of parms
in the IMODs was outdated. This fix provides corrections to the
following IMODs:
ACTION_CANCEL
THR_IMS
THR_JOB
THR_JOBCPU%
THR_MQS
THR_MVS
THR_TCP
This fix also provides an updated GSVXMIB that describes the SNMP
trap data.
SYMPTOMS:
Missing terminal ID and userID in message text of OPS/MVS event.
IMPACT:
Missing CICS information in OPS/MVS.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5190).
++HOLD(RO56815) FMID(CNM4D50)
SYSTEM
REASON(ACTION)
DATE(13086)
COMMENT(
To implement updated modules:
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.
To implement updated IMODs:
1. Apply this fix to update the IMOD source library CNM4BISR.
2. Use the sample IMODLOAD batch job, which can be found in the
SAMPJCL and/or CNM4BSAM library, to load the new IMOD source
into the ISET and compile it.
Specify the following control statements in the IMODLOAD JCL:
//SYSIN DD *
PDSLOAD MEMBER IMOD0013 TO OUT FROM IN REPLACE IMOD ACTION_CANCEL
PDSLOAD MEMBER IMOD0125 TO OUT FROM IN REPLACE IMOD THR_IMS
PDSLOAD MEMBER IMOD0126 TO OUT FROM IN REPLACE IMOD THR_JOB
PDSLOAD MEMBER IMOD0127 TO OUT FROM IN REPLACE IMOD THR_JOBCPU%
PDSLOAD MEMBER IMOD0128 TO OUT FROM IN REPLACE IMOD THR_MQS
PDSLOAD MEMBER IMOD0129 TO OUT FROM IN REPLACE IMOD THR_MVS
PDSLOAD MEMBER IMOD0130 TO OUT FROM IN REPLACE IMOD THR_TCP
COMPILE IMOD ACTION_CANCEL IN OUT STATUS PROD
COMPILE IMOD THR_IMS IN OUT STATUS PROD
COMPILE IMOD THR_JOB IN OUT STATUS TEST
COMPILE IMOD THR_JOBCPU% IN OUT STATUS TEST
COMPILE IMOD THR_MQS IN OUT STATUS PROD
COMPILE IMOD THR_MVS IN OUT STATUS PROD
COMPILE IMOD THR_TCP IN OUT STATUS PROD
3. Recycle CA GSS to pick up these changes.
Updated Capture, SNMP Trap, and OPS/MVS Event data:
This fix adds Terminal ID and User ID parameters to be passed to external
handlers during CICS threshold processing. See HOWTO027 in TOPICS for
CA SYSVIEW Performance Management 13.5 59
CA RS 1309 - PTF RO56815 Details
Release Service Detailsdetail parameters format.
).
CA SYSVIEW Performance Management 13.5 60
CA RS 1309 - PTF RO57081 DetailsCA SYSVIEW Performance Management 13.5 60
CA RS 1309 - PTF RO57081 Details
Release Service Details13.5 RO57081 RO57081 M.C.S. ENTRIES = ++PTF(RO57081)
DESC(JOBCLASS missing entries)
/*
PROBLEM DESCRIPTION:
The JOBCLASS command may not display all job classes in 13.5 and 13.7.
SYMPTOMS:
Job class missing on the JOBCLASS command display in 13.5 and 13.7.
IMPACT:
Missing job class in 13.5 and 13.7.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO45843)
SUP(TSD5192).
CA SYSVIEW Performance Management 13.5 61
CA RS 1309 - PTF RO57228 DetailsCA SYSVIEW Performance Management 13.5 61
CA RS 1309 - PTF RO57228 Details
Release Service Details13.5 RO57228 RO57228 M.C.S. ENTRIES = ++PTF(RO57228)
DESC(ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS)
/*
PROBLEM DESCRIPTION:
Abend S0C4-3B can occur in SYSVIEW/CICS module GSVCMSCR due to the
high halves of 64-bit registers not being restored.
SYMPTOMS:
Abend messages similar to the following appear in the CICS job log:
GSVC990E (TPPT) CA SYSVIEW for CICS r13.5 Abend information
GSVC991E (TPPT) Task GSVCTPPT Module GSVCMSCR Offset 00004723
GSVC992E (TPPT) Abend S0C4 PSW 078C3001 A4984723 Ilc 4 Intc 3B
GSVC996E (TPPT) Registers at entry to abend
GSVC995E (TPPT) AR/GR 00:00000002_00000008 01:00000000/00000000_24FB8698
GSVC995E (TPPT) AR/GR 02:00000000_24CBDB30 03:00000000/00000000_24CBD038
GSVC995E (TPPT) AR/GR 04:00000000_00000000 05:00000000/00000000_00000000
GSVC995E (TPPT) AR/GR 06:00000000_24B243B4 07:00000000/00000000_40E7BBE0
GSVC995E (TPPT) AR/GR 08:00000000_24B2C768 09:00000000/00000000_24C7B000
GSVC995E (TPPT) AR/GR 10:00000000_24985070 11:00000000/00000003_24984588
GSVC995E (TPPT) AR/GR 12:00000000_24FB8000 13:00000000/00000000_00016528
GSVC995E (TPPT) AR/GR 14:00000000_24980203 15:00000000/00000003_24984588
GSVC998E (TPPT) End of symptom dump
IMPACT:
A dump is taken and the subtask that incurred the abend (GSVCTPPT in
the reported case) restarts.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO42952)
SUP(TSD5193).
++HOLD(RO57228) FMID(CNM4D50)
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.
).
CA SYSVIEW Performance Management 13.5 62
CA RS 1309 - PTF RO57317 DetailsCA SYSVIEW Performance Management 13.5 62
CA RS 1309 - PTF RO57317 Details
Release Service Details13.5 RO57317 RO57317 M.C.S. ENTRIES = ++PTF(RO57317)
DESC(ROSC011W Timeout waiting for ROSCOE job to respond)
/*
PROBLEM DESCRIPTION:
The ROSACT command produces the following error message:
ROSC011W Timeout waiting for ROSCOE job jjjjjjjj to respond
SYMPTOMS:
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
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50) SUP(TSD5194).
++HOLD(RO57317) FMID(CNM4D50)
SYSTEM
REASON(RESTART)
DATE(13101)
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.
).
CA SYSVIEW Performance Management 13.5 63
CA RS 1309 - PTF RO57473 DetailsCA SYSVIEW Performance Management 13.5 63
CA RS 1309 - PTF RO57473 Details
Release Service Details13.5 RO57473 RO57473 M.C.S. ENTRIES = ++PTF(RO57473)
DESC(INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM)
/*
PROBLEM DESCRIPTION:
New CICS configuration option PERFORMANCE-DATA-SEGLIMIT-DB2 was
introduced in the CICSOPTS parmlib member in SYSVIEW 13.5. 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 1000.
This limit typically only matters if configuration option
PERFORMANCE-DATA-DB2-BY-PROGRAM is set to YES.
SYMPTOMS:
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 *.
IMPACT:
Reduced DB2 program call details may hinder debugging efforts.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5195).
++HOLD(RO57473) FMID(CNM4D50)
SYSTEM
REASON(ENH)
DATE(13101)
COMMENT(
This fix increases the maximum allowed value on the
PERFORMANCE-DATA-SEGLIMIT-DB2 configuration option in the
CICSOPTS parmlib member to 1000.
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.
).
CA SYSVIEW Performance Management 13.5 64
CA RS 1309 - PTF RO57542 DetailsCA SYSVIEW Performance Management 13.5 64
CA RS 1309 - PTF RO57542 Details
Release Service Details13.5 RO57542 RO57542 M.C.S. ENTRIES = ++PTF(RO57542)
DESC(GSVC015I Message contains incorrect jobname)
/*
PROBLEM DESCRIPTION:
Message GSVC015I in CICS JOBLOG displayed incorrect Jobname.
SYMPTOMS:
Message GSVC015I displayed CICS's job name instead of the jobname of
the connected CICSLOGR, which is typically SYSVIEW.
IMPACT:
Incorrect Jobname displayed.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5196).
++HOLD(TSD5196) FMID(CNM4D50)
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.
).
CA SYSVIEW Performance Management 13.5 65
CA RS 1309 - PTF RO57739 DetailsCA SYSVIEW Performance Management 13.5 65
CA RS 1309 - PTF RO57739 Details
Release Service Details13.5 RO57739 RO57739 M.C.S. ENTRIES = ++PTF(RO57739)
DESC(GSV3650E/IXL013I IXLCONN request failed for CTSQUEUE cmd)
/*
PROBLEM DESCRIPTION:
The CTSQUEUE command will fail if running in zIIP mode and trying
to retrieve CICS shared temporary storage queues from the coupling
facility.
SYMPTOMS:
The following error message can be observed in LISTLOG when issuing
the CTSQUEUE command:
GSV3650E IXLCONN request failed. RC=00000008 RS=02010806 DIAG0=00000000
DIAG1=00000000 DIAG2=00000000
Also error messages similar to the following will be produced in the
joblog where the user session is executing:
IXL013I IXLCONN REQUEST FOR STRUCTURE ................ FAILED. 526
JOBNAME: xxxxxxxx ASID: 0718 CONNECTOR NAME: N/A
IXLCONN RETURN CODE: 00000008, REASON CODE: 02010806
IXLCONN PARAMETER ERROR
IMPACT:
Unable to obtain any of the queues when issuing the CTSQUEUE command.
CIRCUMVENTION:
Temporarily specify the following parameter in the OPTIONS parmlib member:
zIIPEnable NO
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5197).
CA SYSVIEW Performance Management 13.5 66
CA RS 1309 - PTF RO57926 DetailsCA SYSVIEW Performance Management 13.5 66
CA RS 1309 - PTF RO57926 Details
Release Service Details13.5 RO57926 RO57926 M.C.S. ENTRIES = ++PTF(RO57926)
DESC(U2999-1101 U0017 Abend, COMMON command looping)
/*
PROBLEM DESCRIPTION:
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 U0017 001
13.0 U0017 001
13.5 U2999 1101
13.7 U2999 1101
SYMPTOMS:
The COMMON command U2999-1101 or U0017-001 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
IMPACT:
User session terminates with U2999-1101 or U0017-001 abend.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5198).
CA SYSVIEW Performance Management 13.5 67
CA RS 1309 - PTF RO58096 DetailsCA SYSVIEW Performance Management 13.5 67
CA RS 1309 - PTF RO58096 Details
Release Service Details13.5 RO58096 RO58096 M.C.S. ENTRIES = ++PTF(RO58096)
DESC(IMS DLI variable totals display incorrectly greater than 2G)
/*
PROBLEM DESCRIPTION:
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)
SYMPTOMS:
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
IMPACT:
Unable to accurately display IMS DLI variable metrics when the total
values exceed 2,147,483,647 (2G-1).
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO56000,RO55742)
SUP(TSD5200).
CA SYSVIEW Performance Management 13.5 68
CA RS 1309 - PTF RO58130 DetailsCA SYSVIEW Performance Management 13.5 68
CA RS 1309 - PTF RO58130 Details
Release Service Details13.5 RO58130 RO58130 M.C.S. ENTRIES = ++PTF(RO58130)
DESC(AUDIT/IMS reports and FROM/TO commands showing wrong times)
/*
PROBLEM DESCRIPTION:
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
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
1. None.
2. 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
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO47847 RO55742)
SUP(TSD5201).
CA SYSVIEW Performance Management 13.5 69
CA RS 1309 - PTF RO58296 DetailsCA SYSVIEW Performance Management 13.5 69
CA RS 1309 - PTF RO58296 Details
Release Service Details13.5 RO58296 RO58296 M.C.S. ENTRIES = ++PTF(RO58296)
DESC(ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
No further monitoring of MQ requests will be performed.
CIRCUMVENTION:
Specify MONITOR-MQS-REQUESTS NO in the MQSDATA parmlib member
to disable MQ request monitoring.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5202).
CA SYSVIEW Performance Management 13.5 70
CA RS 1309 - PTF RO58350 DetailsCA SYSVIEW Performance Management 13.5 70
CA RS 1309 - PTF RO58350 Details
Release Service Details13.5 RO58350 RO58350 M.C.S. ENTRIES = ++PTF(RO58350)
DESC(MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS.)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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,
IMPACT:
Excessive amount of error messages issued to the console.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5203)
PRE(RO49066,RO55263).
++HOLD(RO58350) FMID(CNM4D70)
SYSTEM
REASON(ENH)
DATE(13143)
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.
).
CA SYSVIEW Performance Management 13.5 71
CA RS 1309 - PTF RO58393 DetailsCA SYSVIEW Performance Management 13.5 71
CA RS 1309 - PTF RO58393 Details
Release Service Details13.5 RO58393 RO58393 M.C.S. ENTRIES = ++PTF(RO58393)
DESC(CSTATES SYSTEM command orphans storage)
/*
PROBLEM DESCRIPTION:
Issuing the CSTATES SYSTEM command causes memory leaks in storage USR
subpool 0 key 8, where duplicate buffers of data are being created
with only one getting freed.
SYMPTOMS:
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.
IMPACT:
Unable to allocate any additional private storage when the storage limit
is exceeded, which causes the command issued to fail.
CIRCUMVENTION:
Issue the CSTATES command without stating the SYSTEM parameter. If the
problem does occur, recycle user's SYSVIEW session.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO45009)
SUP(TSD5204).
CA SYSVIEW Performance Management 13.5 72
CA RS 1309 - PTF RO58485 DetailsCA SYSVIEW Performance Management 13.5 72
CA RS 1309 - PTF RO58485 Details
Release Service Details13.5 RO58485 RO58485 M.C.S. ENTRIES = ++PTF(RO58485)
DESC(XMDR002W NRAS buffer max of 256K reached)
/*
PROBLEM DESCRIPTION:
When issuing the ASLIST or ASLOST command it is possible the command
may produce error messages indicating the 256K buffer max has been
reached.
SYMPTOMS:
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 ????????
IMPACT:
No results produced by command.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5205)
PRE(RO52625).
++HOLD(RO58485) FMID(CNM4D50)
SYSTEM
REASON(DYNACT)
DATE(13137)
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.
).
CA SYSVIEW Performance Management 13.5 73
CA RS 1309 - PTF RO58500 DetailsCA SYSVIEW Performance Management 13.5 73
CA RS 1309 - PTF RO58500 Details
Release Service Details13.5 RO58500 RO58500 M.C.S. ENTRIES = ++PTF(RO58500)
DESC(compatibility support for future XSYSTEM changes)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
Possibly unable to gather cross-system data between mixed releases
of SYSVIEW.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO44979, RO47747)
SUP(TSD5206).
CA SYSVIEW Performance Management 13.5 74
CA RS 1309 - PTF RO58553 DetailsCA SYSVIEW Performance Management 13.5 74
CA RS 1309 - PTF RO58553 Details
Release Service Details13.5 RO58553 RO58553 M.C.S. ENTRIES = ++PTF(RO58553)
DESC(MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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
IMPACT:
Unable to execute functions that require the Main Services
(SYSVIEW) address space.
CIRCUMVENTION:
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.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5207).
CA SYSVIEW Performance Management 13.5 75
CA RS 1309 - PTF RO58618 DetailsCA SYSVIEW Performance Management 13.5 75
CA RS 1309 - PTF RO58618 Details
Release Service Details13.5 RO58618 RO58618 M.C.S. ENTRIES = ++PTF(RO58618)
DESC(USTOPPED/PSTOPPED status handled incorrectly for IMS commands)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO53884)
SUP(TSD5208).
CA SYSVIEW Performance Management 13.5 76
CA RS 1309 - PTF RO59143 DetailsCA SYSVIEW Performance Management 13.5 76
CA RS 1309 - PTF RO59143 Details
Release Service Details13.5 RO59143 RO59143 M.C.S. ENTRIES = ++PTF(RO59143)
DESC(Display does not update properly when PREFIX values changed)
/*
PROBLEM DESCRIPTION:
The display does not update properly when the PREFIX values changed
for the following JES commands:
JTRANQUE, JOBSUM, LISTINP, and ACTIVITY
SYMPTOMS:
Changing PREFIX values may cause JES command display to update with
incompleted or no data.
IMPACT:
Incorrect information displayed.
CIRCUMVENTION:
Switch to a different display and back.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO51780, RO56619)
SUP(TSD5211).
CA SYSVIEW Performance Management 13.5 77
CA RS 1309 - PTF RO59193 DetailsCA SYSVIEW Performance Management 13.5 77
CA RS 1309 - PTF RO59193 Details
Release Service Details13.5 RO59193 RO59193 M.C.S. ENTRIES = ++PTF(RO59193)
DESC(IMTSQUE threshold not working for IMS shared queues)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
Unable to monitor IMS message queue depth in shared queue environment.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO45326, RO55263)
SUP(TSD5212).
CA SYSVIEW Performance Management 13.5 78
CA RS 1309 - PTF RO59416 DetailsCA SYSVIEW Performance Management 13.5 78
CA RS 1309 - PTF RO59416 Details
Release Service Details13.5 RO59416 RO59416 M.C.S. ENTRIES = ++PTF(RO59416)
DESC(Abend S0F8-04 issuing LOGREC CLEAR subcommand)
/*
PROBLEM DESCRIPTION:
The CLEAR subcommand of the LOGREC command results in an
abend S0F8-04 when running in zIIP mode.
SYMPTOMS:
Issuing the CLEAR subcommand from the LOGREC display
results in an abend S0F8-04.
The following messages will be seen in the JES job log
of the user's session:
GSVX451E Abend S0F8-04 in LOGREC/CLEAR command
GSVX472I Userid userid Terminal terminal Interface intf
GSVX452I SYSVIEW SRB in control at entry to abend
GSVX453I Diagnostics for SRB in control at entry to abend
GSVX457I Psw 078C1000 address1 Ilc 2 Intc 2A
GSVX477I Key 8 State SUP Am 31 Asc PRI
GSVX458I Module GSVKLOGC Addr address2 Offset <offset>
GSVX450I FixLvl BASE
GSVX473I Routne CALL$$ Addr address3 Offset 0000009E
<offset> = 000004DE at SYSVIEW 13.5.
<offset> = 00000536 at SYSVIEW 13.7.
IMPACT:
1. The user's SYSVIEW session will abend and need to be
restarted ... AND ...
2. It is not possible to use SYSVIEW to clear the
SYS1.LOGREC data set.
CIRCUMVENTION:
1. Use IBM's IFCDIP00 program to clear the SYS1.LOGREC
data set ... OR ...
2. Set zIIPEnable in the OPTIONS member of parmlib to
NO and recycle your SYSVIEW session.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50) SUP(TSD5213).
CA SYSVIEW Performance Management 13.5 79
CA RS 1309 - PTF RO59427 DetailsCA SYSVIEW Performance Management 13.5 79
CA RS 1309 - PTF RO59427 Details
Release Service Details13.5 RO59427 RO59427 M.C.S. ENTRIES = ++PTF(RO59427)
DESC(XSCONN command fails from ISPF interface)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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
IMPACT:
Unable to connect to a different instance of SYSVIEW from the ISPF
interface when issuing the XSCONN command.
CIRCUMVENTION:
Issue the XSCONN command from the TSO or VTAM interface.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO58500)
SUP(TSD5214).
CA SYSVIEW Performance Management 13.5 80
CA RS 1309 - PTF RO59438 DetailsCA SYSVIEW Performance Management 13.5 80
CA RS 1309 - PTF RO59438 Details
Release Service Details13.5 RO59438 RO59438 M.C.S. ENTRIES = ++PTF(RO59438)
DESC(JOBNAME and SYSID ID Options return incorrect data)
/*
PROBLEM DESCRIPTION:
Two problems exist related to EXPLORE Report Writer ID Options.
1. The JOBNAME ID Option does not filter SYSVIEW/CICS System Interval
SMF records (subtype 28) when used with the SELECT command.
2. The SYSID ID option does not allow any records to be returned on a
report when used with the SELECT command.
SYMPTOMS:
1. When using the JOBNAME ID Option to filter SYSVIEW/CICS System
Interval SMF records (subtype 28), it appears that no filtering on the
JOBNAME has taken place when the report is ran.
2. When using the SYSID ID Option to filter SMF records, no records are
returned on the report. The following message may be seen in the report
output:
ERPT221E NO MATCHING DATA
IMPACT:
1. Unable to filter SYSVIEW/CICS System Interval SMF records
(subtype 28) with the JOBNAME ID Option.
2. Unable to filter SMF records with the SYSID ID Option.
CIRCUMVENTION:
1. Use the JOBID ID Option in place of the JOBNAME ID Option.
2. Specify an asterisk (*) after the system name parameter desired. For
example, if the system name desired is 'SYSA', then specify the ID
Option as 'SYSID(SYSA*)'.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO45533)
SUP(TSD5215).
CA SYSVIEW Performance Management 13.5 81
CA RS 1309 - PTF RO59526 DetailsCA SYSVIEW Performance Management 13.5 81
CA RS 1309 - PTF RO59526 Details
Release Service Details13.5 RO59526 RO59526 M.C.S. ENTRIES = ++PTF(RO59526)
DESC(IMS Transaction missing from IMSTLOG)
/*
PROBLEM DESCRIPTION:
A transaction sends out secondary requests to non-LTERM devices. These
requests are treated as transaction responses which causes the transaction
to be queued in the IMSLOGR dataspace waiting for the transactions output
to be read which will never occur.
SYMPTOMS:
IMS transaction does not show up in IMSTLOG. It is queued in the IMSLOGR
dataspace waiting for output messages.
IMPACT:
Unable to monitor IMS transaction.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO55226)
SUP(TSD5216).
CA SYSVIEW Performance Management 13.5 82
CA RS 1309 - PTF RO59674 DetailsCA SYSVIEW Performance Management 13.5 82
CA RS 1309 - PTF RO59674 Details
Release Service Details13.5 RO59674 RO59674 M.C.S. ENTRIES = ++PTF(RO59674)
DESC(JCOPYOUT abend S002-18 / record length incorrect)
/*
PROBLEM DESCRIPTION:
Two problems exist related to the JCOPYOUT command.
1. Abend S002-18 is possible when using the JCOPYOUT command. This
problem will occur if the record length field is either blank (null)
or less than 5 when the copy request is submitted.
2. When using the JCOPYOUT command, the record length of the source
data set may be incorrectly increased by 4 bytes in the target data
set. This problem will only occur when copying a variable record
length data set to another variable record length data set.
SYMPTOMS:
1. When using the JCOPYOUT command, the following message may be
displayed in the message area:
OSRV005E OS services module abended S002-18
After the abend S002-18 occurs, other subsequent abends may follow.
One or more of following messages may appear in the user's job log
indicating those abends:
GSVX451E Abend S0C6-06 in TERMINAT command
GSVX451E Abend S0C4-3B in TERMINAT command
GSVX451E Abend U2999-802 in JCOPYOUT command
2. After using the JCOPYOUT command to copy a variable record length
data set to another variable record length data set, the record
length of the target data set is 4 bytes longer than the record
length of the source data set.
IMPACT:
1. Possible abends using JCOPYOUT command.
2. Unable to prevent the record length of a data set from increasing
when using the JCOPYOUT command to copy a variable record length
data set to another.
CIRCUMVENTION:
1. Specify a valid record length greater than 4 when using the
JCOPYOUT command.
2. None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO48686)
SUP(TSD5218).
CA SYSVIEW Performance Management 13.5 83
CA RS 1309 - PTF RO59724 DetailsCA SYSVIEW Performance Management 13.5 83
CA RS 1309 - PTF RO59724 Details
Release Service Details13.5 RO59724 RO59724 M.C.S. ENTRIES = ++PTF(RO59724)
DESC(LGCONN/LGJOBS cmds not showing data with IBM zAware)
/*
PROBLEM DESCRIPTION:
The LGCONN and LGJOBS commands will not display any data when issued on
a system running z/OS 1.13 which contains support for the z/OS IBM
zAware log stream client as described in IBM APAR OA38747.
SYMPTOMS:
The activation of zAware will cause the output of the following MVS
display commands to generate new data:
DISPLAY LOGGER,CONNECTION,LSNAME=*,DETAIL LGCONN
DISPLAY LOGGER,CONNECTION,JOBNAME=*,DETAIL LGJOBS
This essentially causes the LGCONN and LGJOBS commands to not display
any data.
IMPACT:
Unable to display any data on the LGCONN and LGLOGS command displays.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5219).
CA SYSVIEW Performance Management 13.5 84
CA RS 1309 - PTF RO59842 DetailsCA SYSVIEW Performance Management 13.5 84
CA RS 1309 - PTF RO59842 Details
Release Service Details13.5 RO59842 RO59842 M.C.S. ENTRIES = ++PTF(RO59842)
DESC(ASLIST MAXUSER counts and %-ages do not add up)
/*
PROBLEM DESCRIPTION:
The counts and percentages shown on the MAXUSER line of the
ASLIST command display may not add up correctly.
SYMPTOMS:
When address spaces are lost and replaced by reserved address
spaces, the counts and percentages on the MAXUSER line of the
ASLIST display may not add up correctly. This will be
especially noticeable when the number of "Lost" address
spaces is high. For example:
Jobname SYSVUSER ASID 049C Jobid STC37943
Queue Count Used/Pct% Free/Pct% Lost/Pct%
MAXUSER 1500 568 37% 1116 74% 952 63% <====
RSVSTRT 20 0 0% 20 100% 0 0%
RSVNONR 1000 952 95% 48 5% 0 0%
The number of Lost address spaces will be correct.
The number of Used and Free address spaces will be
incorrect, and the percentages shown for all three
will also be incorrect.
Address spaces may be lost due to a job ending with outstanding
cross-memory binds or LX Table entries.
IMPACT:
The user will be unable to determine the number of Used or
Free address spaces.
CIRCUMVENTION:
The correct count of Used address spaces may be obtained by
issuing an ACTIVITY command with no filtering.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO52625) SUP(TSD5221).
CA SYSVIEW Performance Management 13.5 85
CA RS 1309 - PTF RO59965 DetailsCA SYSVIEW Performance Management 13.5 85
CA RS 1309 - PTF RO59965 Details
Release Service Details13.5 RO59965 RO59965 M.C.S. ENTRIES = ++PTF(RO59965)
DESC(IMSTLOG abended transactions not showing correct tran type)
/*
PROBLEM DESCRIPTION:
IMS transactions that have abended may be showing the incorrect
transaction types on the IMSTLOG command display.
SYMPTOMS:
An abended IMS transaction should be indicated by a value of A (Program
abend or unconnected transaction) as the transaction type on IMSTLOG
display.
IMPACT:
Unable to determine if an IMS transaction has abended or not.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO59526)
SUP(TSD5223).
++HOLD(RO59965) FMID(CNM4D50)
SYSTEM
REASON(DYNACT)
DATE(13172)
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
).
CA SYSVIEW Performance Management 13.5 86
CA RS 1309 - PTF RO59975 DetailsCA SYSVIEW Performance Management 13.5 86
CA RS 1309 - PTF RO59975 Details
Release Service Details13.5 RO59975 RO59975 M.C.S. ENTRIES = ++PTF(RO59975)
DESC(Abend S0C4 in Data Collection or IMSLOCKS command)
/*
PROBLEM DESCRIPTION:
Abend S0C4 when running the IMS Lock chain.
SYMPTOMS:
The IMSLOCKS command scans through some IMS-related control
blocks which can change while SYSVIEW is looking at them.
This requires that SYSVIEW code be protected by an ESTAE so
it can recover from any abends. It was found that no such
protection was in place when running the IMS Lock chain.
The IMSLOCKS command may be issued:
- Directly by the user,
- Indirectly ("under the covers") by the SYSVIEW internal
Data Collection function.
- Indirectly ("under the covers") by two SYSVIEW IMS-related
commands:
IMSOVER
IMSRACT
If the abend occurs during IMS Data Collection, the following
messages will be seen on the SYSVIEW job log:
GSVX451E (IMSDATA) Abend S0C4-nn in IMS data collector
GSVX452I (IMSDATA) SYSVIEW SRB in control at entry to abend
GSVX453I (IMSDATA) Diagnostics for SRB in control at entry to abend
GSVX457I (IMSDATA) Psw 070C6001 <address1> Ilc 6 Intc 38
GSVX477I (IMSDATA) Key 0 State SUP Am 64 Asc AR
GSVX458I (IMSDATA) Module GSVPDBxx Addr <address2> Offset <offset1>
GSVX473I (IMSDATA) Routne LKyy$$ Addr <address3> Offset <offset2>
GSVX459I (IMSDATA) Data at PSW addr <address4>
GSVX460I (IMSDATA) E34092A0 0024E310 40200004
GSVX594I (MAIN) IMSDATA task abended, completion code S0C4-nn
GSVX574I (MAIN) IMSDATA task termination complete
GSVX592W (MAIN) RESTART IMSDATA not supported
Note: The 'xx' in GSVPDBxx can be 10, 11, or 12,
depending on the release of IMS being used.
Note: The 'yy' in LKyy$$ can be 31 or 64, depending on
whether the locks are in 31 bit or 64 bit storage.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, messages similar to the above will be seen
on the user's terminal, but the GSVX451E message will be one of
the following:
GSVX451E Abend S0C4-nn in IMSLOCKS command
GSVX451E Abend S0C4-nn in IMSOVER command
GSVX451E Abend S0C4-nn in IMSRACT command
IMPACT:
If the abend occurs during IMS Data Collection, the IMSDATA task
will abend. Since an automatic restart of the IMSDATA task is
not allowed, IMS data collection will cease and no further IMS
monitoring will be done until the IMSDATA task is manually
restarted from the ASADMIN command display.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, the user's session will abend and need to be
restarted.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO58618) SUP(TSD5224).
CA SYSVIEW Performance Management 13.5 87
CA RS 1309 - PTF RO60170 DetailsCA SYSVIEW Performance Management 13.5 87
CA RS 1309 - PTF RO60170 Details
Release Service Details13.5 RO60170 RO60170 M.C.S. ENTRIES = ++PTF(RO60170)
DESC(SELECT with CW and NW not supporting multiple operands)
/*
PROBLEM DESCRIPTION:
The SELECT command may not work correctly when using the CW or NW operands,
followed by another operand.
SYMPTOMS:
The SELECT command displays incorrect information when used with the
CW (Contains Word) or NW (Not contains Word) operands, followed by another
operand.
For example, issuing the following command in the LISTJOBS command display:
SELECT queue cw exec or stat eq hldc
results in the following:
- The LISTJOBS display is filtered using only the CW operand
("queue CW exec").
- The EQ operand ("stat EQ hldc") is ignored.
- All jobs with a Queue field of "exec" are displayed, regardless of the
value in the Status field.
IMPACT:
Users are unable to select correctly using the CW and NW operands.
CIRCUMVENTION:
Do not use the CW or NW operands in a SELECT command unless they are the
final operands in the command.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO54184)
SUP(TSD5225).
CA SYSVIEW Performance Management 13.5 88
CA RS 1309 - PTF RO60779 DetailsCA SYSVIEW Performance Management 13.5 88
CA RS 1309 - PTF RO60779 Details
Release Service Details13.5 RO60779 RO60779 M.C.S. ENTRIES = ++PTF(RO60779)
DESC(Possible looping in dependent region during shutdown)
/*
PROBLEM DESCRIPTION:
A possible looping condition exists during the termination of an
IMS dependent region that is being monitored by SYSVIEW. This
problem results in the region entering a loop and not terminating.
SYMPTOMS:
The dependent region does not shut down and enters a loop. Review
of a dump for the region would show continuous looping condition in
GSVXPLnn (where nn may be 10, 11, 12, or 13).
IMPACT:
IMS dependent region outage as a result of the looping condition
and may need cancelled in order to shut down.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
SUP(TSD5228 AR60830)
PRE(RO59965).
++HOLD(RO60779) FMID(CNM4D50)
SYSTEM
REASON(DYNACT)
DATE(13190)
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
).
CA SYSVIEW Performance Management 13.5 89
CA RS 1309 - PTF RO60879 DetailsCA SYSVIEW Performance Management 13.5 89
CA RS 1309 - PTF RO60879 Details
Release Service Details13.5 RO60879 RO60879 M.C.S. ENTRIES = ++PTF(RO60879)
DESC(PROBLEMS WITH ALERT ACTIONS AND RELATED ONLINE HELP)
/*
PROBLEM DESCRIPTION:
Several problems exist related to actions that can be triggered from
a threshold definition:
The subgroup was not being populated in the API.TEXT variable for an
OPS/MVS Event when an MVS, MQ, TCP, or IMS alert triggered. This caused
all parameters listed after subgroup to shift up by 1 and become
misaligned with the documented format.
When an MVS, MQ, TCP, or IMS alert issues an action to drive a GSS
IMOD, the parameters (or text message) passed to the IMOD is incorrect
for state exceptions.
The related documentation for parameters passed to trigger actions in
online help topics is also incorrect:
HOWTO027:
Incorrect max length for rule type for all OPS/MVS exception events.
HOWTO028 and GSVXMIB Samplib:
Incorrect location for 'Exception rule type' for MVS, MQ, IMS,
and TCP SNMP trap alert format.
HOWTO046:
Missing policy parameter for all WTO messages format.
Missing description parameter for MVS, MQ, IMS, and TCP
WTO messages format.
HOWTO047:
Missing policy parameter for all Log message format.
CICS Log message format does not actually contain 'V=', 'W=', 'P=',
or 'Desc=' strings.
HOWTO034:
Adding online help topic for Audit Event Notification for OPS/MVS.
The online help for messages GSVX321W, GSVX326W, and GSVC100W are
missing Policy parameter.
SYMPTOMS:
Parsing of the API.TEXT for variable will result in incorrect values
being picked up based on the documentation.
Incorrect message format similar to the following data is is passed
to the IMOD when any MVS, MQ, TCP, or IMS State alert triggers:
CAGSVX03PLEXC1 CA11 MQSERIESCSQ6 * * MQSTATE QMGR
IMPACT:
Unable to perform OPS/MVS automation task due to misaligned
API.TEXT messages.
Unable to run IMOD from state exceptions.
Incorrect parsing of OPS/MVS, SNMP Trap, WTO, or log message parameters
using information in help topic.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO56815 RO55950 RO47437)
SUP(TSD5229).
CA SYSVIEW Performance Management 13.5 90
CA RS 1309 - PTF RO61838 DetailsCA SYSVIEW Performance Management 13.5 90
CA RS 1309 - PTF RO61838 Details
Release Service Details13.5 RO61838 RO61838 M.C.S. ENTRIES = ++PTF(RO61838)
DESC(Contain incorrect prereq PTF number W/RO60879)
/*
PROBLEM DESCRIPTION:
Published PTF RO60879 contains incorrect PTF number RO55950 as a
prerequisite causing the SMP/E APPLY job to fail with return code 12.
SYMPTOMS:
Applying RO60879 will result in return code 12 and the following
messages are displayed in the job output:
GIM30209E ** APPLY PROCESSING FAILED FOR SYSMOD RO60879. REQUIRED
SYSMODS FAILED OR WERE MISSING.
GIM35901I ERROR HOLD AR60879 WAS NOT RESOLVED.
GIM35904I PREREQUISITE SYSMOD RO55950 WAS MISSING.
IMPACT:
Unable to apply PTF RO60879.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.5
*/.
++VER(Z038) FMID(CNM4D50)
PRE(RO56815 RO56326 RO47437)
SUP(RO60879 AR60879 TSD5238).
CA SYSVIEW Performance Management 13.0 91
CA RS 1309 - PTF RO49909 DetailsCA SYSVIEW Performance Management 13.0 91
CA RS 1309 - PTF RO49909 Details
Release Service Details13.0 RO49909 RO49909 M.C.S. ENTRIES = ++PTF(RO49909)
DESC(Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$)
/*
PROBLEM DESCRIPTION:
Possible abend S0C4-11 Mod GSVXFLDR Rtn FINT$$ when
trying to view capture data sets created
by a release beyond r13.5 from a r13.5 or lower release.
SYMPTOMS:
Possible abend messages include:
GSVX451E Abend S0C4-11 in MTT command
GSVX472I Userid DOSDA01 Terminal A55TG005 Interface VTAM
GSVX452I SYSVIEW SRB in control at entry to abend
GSVX453I Diagnostics for SRB in control at entry to abend
GSVX457I Psw 078C1000 88AE7092 Ilc 4 Intc 11
GSVX477I Key 8 State SUP Am 31 Asc PRI
GSVX458I Module GSVXNUC Addr 0883D000 Offset 002AA092
GSVX458I NucMod GSVXFLDR Addr 08AE6180 Offset 00000F12
GSVX473I Routne FINT$$ Addr 08AE6BF0 Offset 000004A2
GSVX459I Data at PSW addr 08AE708C
GSVX460I A1CCA784 00349110 8027A7E4
GSVX455I General registers at entry to abend
GSVX467I R0-R1 00000000_00000040 00000000_00000000
GSVX467I R2-R3 00000000_35EB32C4 00000000_000007F6
GSVX467I R4-R5 00000000_0005E288 00000000_00000A7D
GSVX467I R6-R7 00000000_00131BC4 00000000_0000307B
GSVX467I R8-R9 00000000_35F6BFEC 00000000_339E2520
GSVX467I R10-R11 00000000_08AED650 00000000_33687000
GSVX467I R12-R13 00000000_08AE6BF0 00000000_3395B900
GSVX467I R14-R15 00000000_88AE6C88 00000000_00000000
GSVX475I Access registers at entry to abend
IMPACT:
From a prior release, you are unable to view capture files created
by a release beyond r13.5.
CIRCUMVENTION:
View the capture data from the release it was created from.
PRODUCTS AFFECTED:
CA SYSVIEW r13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0215)
PRE(RO34022).
CA SYSVIEW Performance Management 13.0 92
CA RS 1309 - PTF RO55354 DetailsCA SYSVIEW Performance Management 13.0 92
CA RS 1309 - PTF RO55354 Details
Release Service Details13.0 RO55354 RO55354 M.C.S. ENTRIES = ++PTF(RO55354)
DESC(CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd)
/*
PROBLEM DESCRIPTION:
On the CPROGRAM command display, issuing a NEWCOPY or PHASEIN line
command against a CICS program that is currently not in use causes
the program size field to be zero.
SYMPTOMS:
After a CICS program has been PHASED-in or NEWCOPY'd, the program
size will display a zero or blanks until the next program is invoked.
IMPACT:
Unable to display the program size after a NEWCOPY or PHASEIN line
command is issued against a CICS program that is not in use.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0274).
CA SYSVIEW Performance Management 13.0 93
CA RS 1309 - PTF RO56428 DetailsCA SYSVIEW Performance Management 13.0 93
CA RS 1309 - PTF RO56428 Details
Release Service Details13.0 RO56428 RO56428 M.C.S. ENTRIES = ++PTF(RO56428)
DESC(JES3 JOBSUM command not returning all requested jobs)
/*
PROBLEM DESCRIPTION:
The JOBSUM command display may not display the actual number of jobs
available. This problem occurs only on JES3 systems.
SYMPTOMS:
On JES3 systems, the JOBSUM command display may return a lower number of
jobs than available. The number of jobs returned may vary by a
significant number by refreshing the display.
IMPACT:
Unable to retrieve consistent job information on JES3 systems.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO43685)
SUP(TSD0280).
CA SYSVIEW Performance Management 13.0 94
CA RS 1309 - PTF RO56620 DetailsCA SYSVIEW Performance Management 13.0 94
CA RS 1309 - PTF RO56620 Details
Release Service Details13.0 RO56620 RO56620 M.C.S. ENTRIES = ++PTF(RO56620)
DESC(DEST command not working properly for JES3)
/*
PROBLEM DESCRIPTION:
Using DEST command to filter jobs or devices to be displayed is working
improperly for JES3.
SYMPTOMS:
The DEST command is not working for the following SYSVIEW commands:
JOBSUM
LISTINP
An error message similar to the following can be observed when issuing the
DEST command in the above command displays for JES3:
GSV3725W xxxxxx command not supported for JES3
IMPACT:
Unable to use the DEST command to filter jobs or devices for the above
commands.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO32650)
SUP(TSD0281).
CA SYSVIEW Performance Management 13.0 95
CA RS 1309 - PTF RO57316 DetailsCA SYSVIEW Performance Management 13.0 95
CA RS 1309 - PTF RO57316 Details
Release Service Details13.0 RO57316 RO57316 M.C.S. ENTRIES = ++PTF(RO57316)
DESC(ROSC011W Timeout waiting for ROSCOE job to respond)
/*
PROBLEM DESCRIPTION:
The ROSACT command produces the following error message:
ROSC011W Timeout waiting for ROSCOE job jjjjjjjj to respond
SYMPTOMS:
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
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00) SUP(TSD0285).
++HOLD(RO57316) FMID(CNM4D00)
SYSTEM
REASON(RESTART)
DATE(13101)
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.
).
CA SYSVIEW Performance Management 13.0 96
CA RS 1309 - PTF RO57998 DetailsCA SYSVIEW Performance Management 13.0 96
CA RS 1309 - PTF RO57998 Details
Release Service Details13.0 RO57998 RO57998 M.C.S. ENTRIES = ++PTF(RO57998)
DESC(U2999-1101 U0017 Abend, COMMON command looping)
/*
PROBLEM DESCRIPTION:
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 U0017 001
13.0 U0017 001
13.5 U2999 1101
13.7 U2999 1101
SYMPTOMS:
The COMMON command U2999-1101 or U0017-001 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
IMPACT:
User session terminates with U2999-1101 or U0017-001 abend.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0286).
CA SYSVIEW Performance Management 13.0 97
CA RS 1309 - PTF RO58131 DetailsCA SYSVIEW Performance Management 13.0 97
CA RS 1309 - PTF RO58131 Details
Release Service Details13.0 RO58131 RO58131 M.C.S. ENTRIES = ++PTF(RO58131)
DESC(AUDIT/IMS reports and FROM/TO commands showing wrong times)
/*
PROBLEM DESCRIPTION:
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
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
1. None.
2. 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
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO47848 RO56234)
SUP(TSD0288).
CA SYSVIEW Performance Management 13.0 98
CA RS 1309 - PTF RO58396 DetailsCA SYSVIEW Performance Management 13.0 98
CA RS 1309 - PTF RO58396 Details
Release Service Details13.0 RO58396 RO58396 M.C.S. ENTRIES = ++PTF(RO58396)
DESC(CSTATES SYSTEM command orphans storage)
/*
PROBLEM DESCRIPTION:
Issuing the CSTATES SYSTEM command causes memory leaks in storage USR
subpool 0 key 8, where duplicate buffers of data are being created
with only one getting freed.
SYMPTOMS:
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.
IMPACT:
Once private storage for the user is exhausted, all subsequent SYSVIEW
commands from the user will fail.
CIRCUMVENTION:
Issue the CSTATES command without stating the SYSTEM parameter. If the
problem does occur, recycle user's SYSVIEW session.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO44929)
SUP(TSD0289).
CA SYSVIEW Performance Management 13.0 99
CA RS 1309 - PTF RO58590 DetailsCA SYSVIEW Performance Management 13.0 99
CA RS 1309 - PTF RO58590 Details
Release Service Details13.0 RO58590 RO58590 M.C.S. ENTRIES = ++PTF(RO58590)
DESC(IMS DLI variable totals display incorrectly greater than 2G)
/*
PROBLEM DESCRIPTION:
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)
SYMPTOMS:
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
IMPACT:
Unable to accurately display IMS DLI variable metrics when the total
values exceed 2,147,483,647 (2G-1).
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO56003,RO56234)
SUP(TSD0290).
CA SYSVIEW Performance Management 13.0 100
CA RS 1309 - PTF RO58676 DetailsCA SYSVIEW Performance Management 13.0 100
CA RS 1309 - PTF RO58676 Details
Release Service Details13.0 RO58676 RO58676 M.C.S. ENTRIES = ++PTF(RO58676)
DESC(USTOPPED/PSTOPPED status handled incorrectly for IMS commands)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO34390,RO55204,RO59390)
SUP(TSD0291).
CA SYSVIEW Performance Management 13.0 101
CA RS 1309 - PTF RO58949 DetailsCA SYSVIEW Performance Management 13.0 101
CA RS 1309 - PTF RO58949 Details
Release Service Details13.0 RO58949 RO58949 M.C.S. ENTRIES = ++PTF(RO58949)
DESC(GSVX451E Abend S0C4-10 when issuing MIBWALK or MIBBROWSE cmd)
/*
PROBLEM DESCRIPTION:
S0C4-10 abend when issuing the MIBWALK or MIBBROWSE command.
SYMPTOMS:
Abend messages similar to the following will be issued:
GSVX451E Abend S0C4-10 in MIBWALK command
GSVX472I Userid userid Terminal A55TU067 Interface VTAM
GSVX457I Psw 078D1000 0045A94C Ilc 2 Intc 10
GSVX477I Key 8 State PROB Am 24 Asc PRI
GSVX463I No active load module found
GSVX459I Data at PSW addr 0045A946
GSVX460I 00000000 00000000 00000000
GSVX455I General registers at entry to abend
GSVX467I R0-R1 00000000_3A45A94C 00000000_3B7DEF70
GSVX467I R2-R3 00000000_3B825C6C 00000000_3B3D9A18
GSVX467I R4-R5 3B7DEFFC_00000010 3B7DF014_00000001
GSVX467I R6-R7 FFFFFFFF_3B8231A8 FFFFFFFF_3B5211E8
GSVX467I R8-R9 00000005_3B8231A8 00000002_3B7DEF60
GSVX467I R10-R11 3B7DF004_3A46A3A0 3B7DF056_3B3D9000
GSVX467I R12-R13 3B823478_3A45A630 00000000_3B444690
GSVX467I R14-R15 00000000_3B7DF048 00000000_3A45A94C
IMPACT:
The user session terminates.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0292).
CA SYSVIEW Performance Management 13.0 102
CA RS 1309 - PTF RO59168 DetailsCA SYSVIEW Performance Management 13.0 102
CA RS 1309 - PTF RO59168 Details
Release Service Details13.0 RO59168 RO59168 M.C.S. ENTRIES = ++PTF(RO59168)
DESC(Display does not update properly when PREFIX values changed)
/*
PROBLEM DESCRIPTION:
The display does not update properly when the PREFIX values changed
for the following JES commands:
JTRANQUE, JOBSUM, LISTINP, and ACTIVITY
SYMPTOMS:
Changing PREFIX values may cause JES command display to update with
incompleted or no data.
IMPACT:
Incorrect information displayed.
CIRCUMVENTION:
Switch to a different display and back.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO51781, RO56620)
SUP(TSD0293).
CA SYSVIEW Performance Management 13.0 103
CA RS 1309 - PTF RO59279 DetailsCA SYSVIEW Performance Management 13.0 103
CA RS 1309 - PTF RO59279 Details
Release Service Details13.0 RO59279 RO59279 M.C.S. ENTRIES = ++PTF(RO59279)
DESC(IMTSQUE threshold not working for IMS shared queues)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
Unable to monitor IMS message queue depth in shared queue environment.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO45327)
SUP(TSD0294).
CA SYSVIEW Performance Management 13.0 104
CA RS 1309 - PTF RO59390 DetailsCA SYSVIEW Performance Management 13.0 104
CA RS 1309 - PTF RO59390 Details
Release Service Details13.0 RO59390 RO59390 M.C.S. ENTRIES = ++PTF(RO59390)
DESC(ABEND S0C4-11 IN GSVPDB91 ISSUING IMSPSBS COMMAND)
/*
PROBLEM DESCRIPTION:
The IMSPSBS command may result in an S0C4-11 abend in module
GSVPDB91. Previous PTF RO55204 addressed this problem in
IMS 10, 11, and 12 releases but did not include the release 9.
This PTF specifically addresses the IMS release 9 level.
SYMPTOMS:
S0C4-11 in module GSVPDB91 after issuing the IMSPSBS command
which generates an SVC dump.
A message similar to the following will be seen in the joblog
where the users session was executing.
IEA794I SVC DUMP HAS CAPTURED: 301
DUMPID=581 REQUESTED BY JOB (SYSVUSER)
DUMP TITLE=CA SYSVIEW 13.0 0720 - Job SYSVUSER Asid 0130 Abend
S0C4-11 Mod ***NA*** Rtn ***NA***
IMPACT:
SVC dump captured for the S0C4-11.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0295)
PRE(RO53886).
CA SYSVIEW Performance Management 13.0 105
CA RS 1309 - PTF RO59439 DetailsCA SYSVIEW Performance Management 13.0 105
CA RS 1309 - PTF RO59439 Details
Release Service Details13.0 RO59439 RO59439 M.C.S. ENTRIES = ++PTF(RO59439)
DESC(JOBNAME and SYSID ID Options return incorrect data)
/*
PROBLEM DESCRIPTION:
Two problems exist related to EXPLORE Report Writer ID Options.
1. The JOBNAME ID Option does not filter SYSVIEW/CICS System Interval
SMF records (subtype 28) when used with the SELECT command.
2. The SYSID ID option does not allow any records to be returned on a
report when used with the SELECT command.
SYMPTOMS:
1. When using the JOBNAME ID Option to filter SYSVIEW/CICS System
Interval SMF records (subtype 28), it appears that no filtering on the
JOBNAME has taken place when the report is ran.
2. When using the SYSID ID Option to filter SMF records, no records are
returned on the report. The following message may be seen in the report
output:
ERPT221E NO MATCHING DATA
IMPACT:
1. Unable to filter SYSVIEW/CICS System Interval SMF records
(subtype 28) with the JOBNAME ID Option.
2. Unable to filter SMF records with the SYSID ID Option.
CIRCUMVENTION:
1. Use the JOBID ID Option in place of the JOBNAME ID Option.
2. Specify an asterisk (*) after the system name parameter desired. For
example, if the system name desired is 'SYSA', then specify the ID
Option as 'SYSID(SYSA*)'.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO45534)
SUP(TSD0296).
CA SYSVIEW Performance Management 13.0 106
CA RS 1309 - PTF RO59450 DetailsCA SYSVIEW Performance Management 13.0 106
CA RS 1309 - PTF RO59450 Details
Release Service Details13.0 RO59450 RO59450 M.C.S. ENTRIES = ++PTF(RO59450)
DESC(LGCONN/LGJOBS cmds not showing data with IBM zAware)
/*
PROBLEM DESCRIPTION:
The LGCONN and LGJOBS commands will not display any data when issued on
a system running z/OS 1.13 which contains support for the z/OS IBM
zAware log stream client as described in IBM APAR OA38747.
SYMPTOMS:
The activation of zAware will cause the output of the following MVS
display commands to generate new data:
DISPLAY LOGGER,CONNECTION,LSNAME=*,DETAIL LGCONN
DISPLAY LOGGER,CONNECTION,JOBNAME=*,DETAIL LGJOBS
This essentially causes the LGCONN and LGJOBS commands to not display
any data.
IMPACT:
Unable to display any data on the LGCONN and LGLOGS command displays.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0297).
CA SYSVIEW Performance Management 13.0 107
CA RS 1309 - PTF RO59562 DetailsCA SYSVIEW Performance Management 13.0 107
CA RS 1309 - PTF RO59562 Details
Release Service Details13.0 RO59562 RO59562 M.C.S. ENTRIES = ++PTF(RO59562)
DESC(ESRT014E ADD FAILED WHEN ATTEMPTING TO ADD AN EXTENDED SVC)
/*
PROBLEM DESCRIPTION:
At z/OS 1.12 and above, when attempting to dynamically add an SVC to
the ESRTABLE it results in error "ESRT014E ADD failed" and the SVC
does not get added. The SVC table, and the ESR tables pointed to by
the ESR entries in the SVC table, reside in E-RONUC (Extended Read
Only Nucleus) storage.
At z/OS 1.12 the E-RONUC began using large pages and the segments
now reside in segment protected storage.
SYMPTOMS:
When attempting to dynamically add the SVC to the extended SVC table,
the following error is received in z/OS 1.12 and above environments.
ESRT014E ADD failed - rc 08 rs 0C ec 00C40004 00000000
IMPACT:
The extended SVC is not dynamically added.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0298)
PRE(RO52762).
++HOLD(RO59562) FMID(CNM4D00)
SYSTEM
REASON(DYNACT)
DATE(13164)
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.
).
CA SYSVIEW Performance Management 13.0 108
CA RS 1309 - PTF RO59974 DetailsCA SYSVIEW Performance Management 13.0 108
CA RS 1309 - PTF RO59974 Details
Release Service Details13.0 RO59974 RO59974 M.C.S. ENTRIES = ++PTF(RO59974)
DESC(Abend S0C4 in Data Collection or IMSLOCKS command)
/*
PROBLEM DESCRIPTION:
Abend S0C4 when running the IMS Lock chain.
SYMPTOMS:
The IMSLOCKS command scans through some IMS-related control
blocks which can change while SYSVIEW is looking at them.
This requires that SYSVIEW code be protected by an ESTAE so
it can recover from any abends. It was found that no such
protection was in place when running the IMS Lock chain.
The IMSLOCKS command may be issued:
- Directly by the user,
- Indirectly ("under the covers") by the SYSVIEW internal
Data Collection function.
- Indirectly ("under the covers") by two SYSVIEW IMS-related
commands:
IMSOVER
IMSRACT
If the abend occurs during IMS Data Collection, the following
messages will be seen on the SYSVIEW job log:
GSVX451E (IMSDATA) Abend S0C4-nn in IMS data collector
GSVX452I (IMSDATA) SYSVIEW SRB in control at entry to abend
GSVX453I (IMSDATA) Diagnostics for SRB in control at entry to abend
GSVX457I (IMSDATA) Psw 070C6001 <address1> Ilc 6 Intc 38
GSVX477I (IMSDATA) Key 0 State SUP Am 64 Asc AR
GSVX458I (IMSDATA) Module GSVPDBxx Addr <address2> Offset <offset1>
GSVX473I (IMSDATA) Routne LKyy$$ Addr <address3> Offset <offset2>
GSVX459I (IMSDATA) Data at PSW addr <address4>
GSVX460I (IMSDATA) E34092A0 0024E310 40200004
GSVX594I (MAIN) IMSDATA task abended, completion code S0C4-nn
GSVX574I (MAIN) IMSDATA task termination complete
GSVX592W (MAIN) RESTART IMSDATA not supported
Note: The 'xx' in GSVPDBxx can be 91, 10, 11, or 12,
depending on the release of IMS being used.
Note: The 'yy' in LKyy$$ can be 31 or 64, depending on
whether the locks are in 31 bit or 64 bit storage.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, messages similar to the above will be seen
on the user's terminal, but the GSVX451E message will be one of
the following:
GSVX451E Abend S0C4-nn in IMSLOCKS command
GSVX451E Abend S0C4-nn in IMSOVER command
GSVX451E Abend S0C4-nn in IMSRACT command
IMPACT:
If the abend occurs during IMS Data Collection, the IMSDATA task
will abend. Since an automatic restart of the IMSDATA task is
not allowed, IMS data collection will cease and no further IMS
monitoring will be done until the IMSDATA task is manually
restarted from the ASADMIN command display.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, the user's session will abend and need to be
restarted.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO58676) SUP(TSD0299).
CA SYSVIEW Performance Management 13.0 109
CA RS 1309 - PTF RO60175 DetailsCA SYSVIEW Performance Management 13.0 109
CA RS 1309 - PTF RO60175 Details
Release Service Details13.0 RO60175 RO60175 M.C.S. ENTRIES = ++PTF(RO60175)
DESC(SELECT with CW and NW not supporting multiple operands)
/*
PROBLEM DESCRIPTION:
The SELECT command may not work correctly when using the CW or NW operands,
followed by another operand.
SYMPTOMS:
The SELECT command displays incorrect information when used with the
CW (Contains Word) or NW (Not contains Word) operands, followed by another
operand.
For example, issuing the following command in the LISTJOBS command display:
SELECT queue cw exec or stat eq hldc
results in the following:
- The LISTJOBS display is filtered using only the CW operand
("queue CW exec").
- The EQ operand ("stat EQ hldc") is ignored.
- All jobs with a Queue field of "exec" are displayed, regardless of the
value in the Status field.
IMPACT:
Users are unable to select correctly using the CW and NW operands.
CIRCUMVENTION:
Do not use the CW or NW operands in a SELECT command unless they are the
final operands in the command.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO54183)
SUP(TSD0300).
CA SYSVIEW Performance Management 13.0 110
CA RS 1309 - PTF RO60201 DetailsCA SYSVIEW Performance Management 13.0 110
CA RS 1309 - PTF RO60201 Details
Release Service Details13.0 RO60201 RO60201 M.C.S. ENTRIES = ++PTF(RO60201)
DESC(IMSTLOG abended transactions not showing correct tran type)
/*
PROBLEM DESCRIPTION:
IMS transactions that have abended may be showing the incorrect
transaction types on the IMSTLOG command display.
SYMPTOMS:
An abended IMS transaction should be indicated by a value of A (Program
abend or unconnected transaction) as the transaction type on IMSTLOG
display.
IMPACT:
Unable to determine if an IMS transaction has abended or not.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
PRE(RO55460,RO60387)
SUP(TSD0301).
++HOLD(RO60201) FMID(CNM4D00)
SYSTEM
REASON(DYNACT)
DATE(13176)
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
).
CA SYSVIEW Performance Management 13.0 111
CA RS 1309 - PTF RO60387 DetailsCA SYSVIEW Performance Management 13.0 111
CA RS 1309 - PTF RO60387 Details
Release Service Details13.0 RO60387 RO60387 M.C.S. ENTRIES = ++PTF(RO60387)
DESC(Missing IMS transactions from IMS Connect)
/*
PROBLEM DESCRIPTION:
Transactions missing on multiple IMS displays that came from IMS
Connect. Previous PTF RO55460 addressed this problem in IMS 10,
11, and 12 releases but did not include the release 9. This PTF
specifically addresses the IMS release 9 level.
SYMPTOMS:
Transactions entering IMS from IMS Connect may not appear on the
IMSTIMES, IMSDAILY, IMSWAITS and IMSTLOG display.
IMPACT:
Unable to view IMS transactions from IMS Connect.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0302)
PRE(RO48405,RO41710).
++HOLD(RO60387) FMID(CNM4D00)
SYSTEM
REASON(DYNACT)
DATE(13177)
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
).
CA SYSVIEW Performance Management 13.0 112
CA RS 1309 - PTF RO60784 DetailsCA SYSVIEW Performance Management 13.0 112
CA RS 1309 - PTF RO60784 Details
Release Service Details13.0 RO60784 RO60784 M.C.S. ENTRIES = ++PTF(RO60784)
DESC(Possible looping in dependent region during shutdown)
/*
PROBLEM DESCRIPTION:
A possible looping condition exists during the termination of an
IMS dependent region that is being monitored by SYSVIEW.
This problem results in the region entering
a loop and not terminating.
SYMPTOMS:
The dependent region does not shut down and enters a loop. Review
of a dump for the region would show continuous looping condition in
GSVXPLnn (where nn may be 91, 10, 11, or 12).
IMPACT:
IMS dependent region outage as a result of the looping condition
and may need cancelled in order to shut down.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 13.0
*/.
++VER(Z038) FMID(CNM4D00)
SUP(TSD0303 AR60834)
PRE(RO60201).
++HOLD(RO60784) FMID(CNM4D00)
SYSTEM
REASON(DYNACT)
DATE(13190)
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
).
CA SYSVIEW Performance Management 12.7 113
CA RS 1309 - PTF RO49053 DetailsCA SYSVIEW Performance Management 12.7 113
CA RS 1309 - PTF RO49053 Details
Release Service Details12.7 RO49053 RO49053 M.C.S. ENTRIES = ++PTF(RO49053)
DESC(Loop in OUTPUT command followed by abend U0017-001)
/*
PROBLEM DESCRIPTION:
Possible loop in OUTPUT command followed by abend U0017-001
SYMPTOMS:
When scrolling down through an executing job's JES output file,
trying to stay at the very bottom of the data being produced,
a loop in module GSVJ2011 is possible if the job gets moved to
the OUTPUT queue while the user is still looking at it. The
user's session will be terminated by an abend U0017-001 after
approximately 5 minutes, when SYSVIEW's internal timer expires.
GSVX971I TASK CPU LIMIT EXCEEDED (00:05:00)
GSVX451E ABEND U0017-001 IN OUTPUT/DOWN COMMAND
GSVX472I USERID userid TERMINAL termname INTERFACE intf
GSVX452I SYSVIEW TCB/RB NOT IN CONTROL AT ENTRY TO ABEND
GSVX453I DIAGNOSTICS FOR TCB/RB IN CONTROL AT ENTRY TO ABEND
GSVX457I PSW 078C2000 address1 ILC 2 INTC 0D
GSVX477I KEY 8 STATE SUP AM 31 ASC PRI
GSVX458I MODULE GSVXNUC ADDR address2 OFFSET offset1
GSVX458I NUCMOD GSVXCPUR ADDR address3 OFFSET offset2
GSVX450I FIXLVL BASE
GSVX473I ROUTNE XCTM$$ ADDR address4 OFFSET offset3
IMPACT:
The user's session will "lock up" while the loop is in progress,
and will terminate and need to be restarted after the abend.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO37729) SUP(TSC7327).
CA SYSVIEW Performance Management 12.7 114
CA RS 1309 - PTF RO50182 DetailsCA SYSVIEW Performance Management 12.7 114
CA RS 1309 - PTF RO50182 Details
Release Service Details12.7 RO50182 RO50182 M.C.S. ENTRIES = ++PTF(RO50182)
DESC(ABEND S0C7 GSVKSPAC issuing SPACE for EAV volumes)
/*
PROBLEM DESCRIPTION:
Abend S0C7 may be experienced using the SPACE command when EAV
volumes exist that have been defined with a size greater than
666,666 cylinders.
SYMPTOMS:
The S0C7 is encountered in module GSVKSPAC with messages similar to
the following, and the session terminates.
GSVX451E Abend S0C7-00 in SPACE command
GSVX472I Userid nnnnnnn Terminal ######## Interface ISPF
GSVX457I Psw 078D2000 998481AA Ilc 6 Intc 07
GSVX477I Key 8 State PROB Am 31 Asc PRI
GSVX458I Module GSVKSPAC Addr 19845000 Offset 000031AA
GSVX473I Routne FALL$$ Addr 198480C0 Offset 000000EA
GSVX459I Data at PSW addr 198481A4
GSVX460I FC73910C 9024F877 93E8910C
GSVX455I General registers at entry to abend
GSVX467I R0-R1 00000000_00DC19A0 00000000_0000E5A2
GSVX467I R2-R3 00000000_00DC19A0 00000000_00000000
GSVX467I R4-R5 00000000_0000000C 00000000_0000004F
GSVX467I R6-R7 00000000_197AC510 00000000_026829A0
GSVX467I R8-R9 00000000_19842F48 00000000_198B58F8
GSVX467I R10-R11 00000000_1984A110 00000000_19053000
GSVX467I R12-R13 00000000_198480C0 00000000_198B4CE8
GSVX467I R14-R15 00000000_99848192 00000000_00000000
GSVX475I Access registers at entry to abend
GSVX461I AR0-AR3 00000000 00000000 00000000 00000000
GSVX461I AR4-AR7 00000000 00000000 00000000 00000000
GSVX461I AR8-AR11 00000000 00000000 00000000 00000000
GSVX461I AR12-AR15 00000000 00000000 00000000 00000000
GSVX462I End of symptom dump
GSVX950I SVCDUMP requested
SVX954I Issuing SDUMPX to capture SVC dump
IMPACT:
Session terminates and needs restarted after the S0C7.
CIRCUMVENTION:
Do not issue the SPACE command where volumes currently exist that
are defined with greater than 666,666 cylinders.
PRODUCTS AFFECTED:
CA SYSVIEW r12.7
*/.
++VER(Z038) FMID(CNM4C70)
SUP(TSC7332)
PRE(RO25152).
CA SYSVIEW Performance Management 12.7 115
CA RS 1309 - PTF RO53318 DetailsCA SYSVIEW Performance Management 12.7 115
CA RS 1309 - PTF RO53318 Details
Release Service Details12.7 RO53318 RO53318 M.C.S. ENTRIES = ++PTF(RO53318)
DESC(ROSC011W Timeout waiting for ROSCOE job to respond)
/*
PROBLEM DESCRIPTION:
The ROSACT command produces the following error message:
ROSC011W Timeout waiting for ROSCOE job jjjjjjjj to respond
SYMPTOMS:
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
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70) SUP(TSC7354).
++HOLD(RO53318) FMID(CNM4C70)
SYSTEM
REASON(RESTART)
DATE(13101)
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.
).
CA SYSVIEW Performance Management 12.7 116
CA RS 1309 - PTF RO55668 DetailsCA SYSVIEW Performance Management 12.7 116
CA RS 1309 - PTF RO55668 Details
Release Service Details12.7 RO55668 RO55668 M.C.S. ENTRIES = ++PTF(RO55668)
DESC(CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd)
/*
PROBLEM DESCRIPTION:
On the CPROGRAM command display, issuing a NEWCOPY or PHASEIN line
command against a CICS program that is currently not in use causes
the program size field to be zero.
SYMPTOMS:
After a CICS program has been PHASED-in or NEWCOPY'd, the program
size will display a zero or blanks until the next program is invoked.
IMPACT:
Unable to display the program size after a NEWCOPY or PHASEIN line
command is issued against a CICS program that is not in use.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r12.7
*/.
++VER(Z038) FMID(CNM4C70)
SUP(TSC7365).
CA SYSVIEW Performance Management 12.7 117
CA RS 1309 - PTF RO56235 DetailsCA SYSVIEW Performance Management 12.7 117
CA RS 1309 - PTF RO56235 Details
Release Service Details12.7 RO56235 RO56235 M.C.S. ENTRIES = ++PTF(RO56235)
DESC(IMS DLI variable totals display incorrectly greater than 2G)
/*
PROBLEM DESCRIPTION:
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)
SYMPTOMS:
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
IMPACT:
Unable to accurately display IMS DLI variable metrics when the total
values exceed 2,147,483,647 (2G-1).
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO56036,RO30663)
SUP(TSC7368).
CA SYSVIEW Performance Management 12.7 118
CA RS 1309 - PTF RO56429 DetailsCA SYSVIEW Performance Management 12.7 118
CA RS 1309 - PTF RO56429 Details
Release Service Details12.7 RO56429 RO56429 M.C.S. ENTRIES = ++PTF(RO56429)
DESC(JES3 JOBSUM command not returning all requested jobs)
/*
PROBLEM DESCRIPTION:
The JOBSUM command display may not display the actual number of jobs
available. This problem occurs only on JES3 systems.
SYMPTOMS:
On JES3 systems, the JOBSUM command display may return a lower number of
jobs than available. The number of jobs returned may vary by a
significant number by refreshing the display.
IMPACT:
Unable to retrieve consistent job information on JES3 systems.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO43686)
SUP(TSC7369).
CA SYSVIEW Performance Management 12.7 119
CA RS 1309 - PTF RO56621 DetailsCA SYSVIEW Performance Management 12.7 119
CA RS 1309 - PTF RO56621 Details
Release Service Details12.7 RO56621 RO56621 M.C.S. ENTRIES = ++PTF(RO56621)
DESC(DEST command not working properly for JES3)
/*
PROBLEM DESCRIPTION:
Using DEST command to filter jobs or devices to be displayed is working
improperly for JES3.
SYMPTOMS:
The DEST command is not working for the following SYSVIEW commands:
JOBSUM
LISTINP
An error message similar to the following can be observed when issuing the
DEST command in the above command displays for JES3:
GSV3725W xxxxxx command not supported for JES3
IMPACT:
Unable to use the DEST command to filter jobs or devices for the above
commands.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW r12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO26596,RO26400)
SUP(TSC7370).
CA SYSVIEW Performance Management 12.7 120
CA RS 1309 - PTF RO56828 DetailsCA SYSVIEW Performance Management 12.7 120
CA RS 1309 - PTF RO56828 Details
Release Service Details12.7 RO56828 RO56828 M.C.S. ENTRIES = ++PTF(RO56828)
DESC(ASRESUME command not working against an unquiesced job)
/*
PROBLEM DESCRIPTION:
The ASRESUME command currently does not have the ability to reset a job
to its service class defined by the service policy when issued against a
job that is not quiesced.
SYMPTOMS:
A warning message similar to the following can be observed when issuing
the ASRESUME command against an unquiesced job:
ASID038W ASRESUME invalid, ASID xxxx not quiesced
IMPACT:
Unable to reclassify work currently in execution according to the service
policy in effect.
CIRCUMVENTION:
Issue MVS command "RESET jobname,RESUME" to reset a job to its service
class defined by the service policy in effect.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO31271)
SUP(TSC7371).
CA SYSVIEW Performance Management 12.7 121
CA RS 1309 - PTF RO58006 DetailsCA SYSVIEW Performance Management 12.7 121
CA RS 1309 - PTF RO58006 Details
Release Service Details12.7 RO58006 RO58006 M.C.S. ENTRIES = ++PTF(RO58006)
DESC(U2999-1101 U0017 Abend, COMMON command looping)
/*
PROBLEM DESCRIPTION:
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 U0017 001
13.0 U0017 001
13.5 U2999 1101
13.7 U2999 1101
SYMPTOMS:
The COMMON command U2999-1101 or U0017-001 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
IMPACT:
User session terminates with U2999-1101 or U0017-001 abend.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
SUP(TSC7372).
CA SYSVIEW Performance Management 12.7 122
CA RS 1309 - PTF RO58132 DetailsCA SYSVIEW Performance Management 12.7 122
CA RS 1309 - PTF RO58132 Details
Release Service Details12.7 RO58132 RO58132 M.C.S. ENTRIES = ++PTF(RO58132)
DESC(AUDIT/IMS reports and FROM/TO commands showing wrong times)
/*
PROBLEM DESCRIPTION:
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
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
1. None.
2. 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
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO47849)
SUP(TSC7373).
CA SYSVIEW Performance Management 12.7 123
CA RS 1309 - PTF RO58397 DetailsCA SYSVIEW Performance Management 12.7 123
CA RS 1309 - PTF RO58397 Details
Release Service Details12.7 RO58397 RO58397 M.C.S. ENTRIES = ++PTF(RO58397)
DESC(CSTATES SYSTEM command orphans storage)
/*
PROBLEM DESCRIPTION:
Issuing the CSTATES SYSTEM command causes memory leaks in storage USR
subpool 0 key 8, where duplicate buffers of data are being created
with only one getting freed.
SYMPTOMS:
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.
IMPACT:
Once private storage for the user is exhausted, all subsequent SYSVIEW
commands from the user will fail.
CIRCUMVENTION:
Issue the CSTATES command without stating the SYSTEM parameter. If the
problem does occur, recycle user's SYSVIEW session.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO45035)
SUP(TSC7374).
CA SYSVIEW Performance Management 12.7 124
CA RS 1309 - PTF RO58678 DetailsCA SYSVIEW Performance Management 12.7 124
CA RS 1309 - PTF RO58678 Details
Release Service Details12.7 RO58678 RO58678 M.C.S. ENTRIES = ++PTF(RO58678)
DESC(USTOPPED/PSTOPPED status handled incorrectly for IMS commands)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
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.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO34102,RO53887)
SUP(TSC7375).
CA SYSVIEW Performance Management 12.7 125
CA RS 1309 - PTF RO58978 DetailsCA SYSVIEW Performance Management 12.7 125
CA RS 1309 - PTF RO58978 Details
Release Service Details12.7 RO58978 RO58978 M.C.S. ENTRIES = ++PTF(RO58978)
DESC(GSVX451E Abend S0C4-10 when issuing MIBWALK and MIBBROWSE cmd)
/*
PROBLEM DESCRIPTION:
S0C4-10 abend when issuing the MIBWALK or MIBBROWSE command.
SYMPTOMS:
Abend messages similar to the following will be issued:
GSVX451E Abend S0C4-10 in MIBWALK command
GSVX472I Userid userid Terminal A55TU067 Interface VTAM
GSVX457I Psw 078D1000 0045A94C Ilc 2 Intc 10
GSVX477I Key 8 State PROB Am 24 Asc PRI
GSVX463I No active load module found
GSVX459I Data at PSW addr 0045A946
GSVX460I 00000000 00000000 00000000
GSVX455I General registers at entry to abend
GSVX467I R0-R1 00000000_3A45A94C 00000000_3B7DEF70
GSVX467I R2-R3 00000000_3B825C6C 00000000_3B3D9A18
GSVX467I R4-R5 3B7DEFFC_00000010 3B7DF014_00000001
GSVX467I R6-R7 FFFFFFFF_3B8231A8 FFFFFFFF_3B5211E8
GSVX467I R8-R9 00000005_3B8231A8 00000002_3B7DEF60
GSVX467I R10-R11 3B7DF004_3A46A3A0 3B7DF056_3B3D9000
GSVX467I R12-R13 3B823478_3A45A630 00000000_3B444690
GSVX467I R14-R15 00000000_3B7DF048 00000000_3A45A94C
IMPACT:
The user session terminates.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
SUP(TSC7376).
CA SYSVIEW Performance Management 12.7 126
CA RS 1309 - PTF RO59191 DetailsCA SYSVIEW Performance Management 12.7 126
CA RS 1309 - PTF RO59191 Details
Release Service Details12.7 RO59191 RO59191 M.C.S. ENTRIES = ++PTF(RO59191)
DESC(JES command display not updating properly when PREFIX changed)
/*
PROBLEM DESCRIPTION:
The display does not update properly when the PREFIX values changed
for the following JES commands:
JOBSUM, LISTINP, and ACTIVITY
SYMPTOMS:
Changing PREFIX values may cause JES command display to update with
incompleted or no data.
IMPACT:
Incorrect information displayed.
CIRCUMVENTION:
Switch to a different display and back.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO51782, RO56621)
SUP(TSC7377).
CA SYSVIEW Performance Management 12.7 127
CA RS 1309 - PTF RO59310 DetailsCA SYSVIEW Performance Management 12.7 127
CA RS 1309 - PTF RO59310 Details
Release Service Details12.7 RO59310 RO59310 M.C.S. ENTRIES = ++PTF(RO59310)
DESC(IMTSQUE threshold not working for IMS shared queues)
/*
PROBLEM DESCRIPTION:
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.
SYMPTOMS:
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.
IMPACT:
Unable to monitor IMS message queue depth in shared queue environment.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO45328, RO25395)
SUP(TSC7378).
CA SYSVIEW Performance Management 12.7 128
CA RS 1309 - PTF RO59440 DetailsCA SYSVIEW Performance Management 12.7 128
CA RS 1309 - PTF RO59440 Details
Release Service Details12.7 RO59440 RO59440 M.C.S. ENTRIES = ++PTF(RO59440)
DESC(JOBNAME and SYSID ID Options return incorrect data)
/*
PROBLEM DESCRIPTION:
Two problems exist related to EXPLORE Report Writer ID Options.
1. The JOBNAME ID Option does not filter SYSVIEW/CICS System Interval
SMF records (subtype 28) when used with the SELECT command.
2. The SYSID ID option does not allow any records to be returned on a
report when used with the SELECT command.
SYMPTOMS:
1. When using the JOBNAME ID Option to filter SYSVIEW/CICS System
Interval SMF records (subtype 28), it appears that no filtering on the
JOBNAME has taken place when the report is ran.
2. When using the SYSID ID Option to filter SMF records, no records are
returned on the report. The following message may be seen in the report
output:
ERPT221E NO MATCHING DATA
IMPACT:
1. Unable to filter SYSVIEW/CICS System Interval SMF records
(subtype 28) with the JOBNAME ID Option.
2. Unable to filter SMF records with the SYSID ID Option.
CIRCUMVENTION:
1. Use the JOBID ID Option in place of the JOBNAME ID Option.
2. Specify an asterisk (*) after the system name parameter desired. For
example, if the system name desired is 'SYSA', then specify the ID
Option as 'SYSID(SYSA*)'.
PRODUCTS AFFECTED:
CA EXPLORE Report Writer 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO33994 RO45535)
SUP(TSC7379).
CA SYSVIEW Performance Management 12.7 129
CA RS 1309 - PTF RO59973 DetailsCA SYSVIEW Performance Management 12.7 129
CA RS 1309 - PTF RO59973 Details
Release Service Details12.7 RO59973 RO59973 M.C.S. ENTRIES = ++PTF(RO59973)
DESC(Abend S0C4 in Data Collection or IMSLOCKS command)
/*
PROBLEM DESCRIPTION:
Abend S0C4 when running the IMS Lock chain.
SYMPTOMS:
The IMSLOCKS command scans through some IMS-related control
blocks which can change while SYSVIEW is looking at them.
This requires that SYSVIEW code be protected by an ESTAE so
it can recover from any abends. It was found that no such
protection was in place when running the IMS Lock chain.
The IMSLOCKS command may be issued:
- Directly by the user,
- Indirectly ("under the covers") by the SYSVIEW internal
Data Collection function.
- Indirectly ("under the covers") by two SYSVIEW IMS-related
commands:
IMSOVER
IMSRACT
If the abend occurs during IMS Data Collection, the following
messages will be seen on the SYSVIEW job log:
GSVX451E (IMSDATA) Abend S0C4-nn in IMS data collector
GSVX452I (IMSDATA) SYSVIEW SRB in control at entry to abend
GSVX453I (IMSDATA) Diagnostics for SRB in control at entry to abend
GSVX457I (IMSDATA) Psw 070C6001 <address1> Ilc 6 Intc 38
GSVX477I (IMSDATA) Key 0 State SUP Am 64 Asc AR
GSVX458I (IMSDATA) Module GSVPDBxx Addr <address2> Offset <offset1>
GSVX473I (IMSDATA) Routne LKyy$$ Addr <address3> Offset <offset2>
GSVX459I (IMSDATA) Data at PSW addr <address4>
GSVX460I (IMSDATA) E34092A0 0024E310 40200004
GSVX594I (MAIN) IMSDATA task abended, completion code S0C4-nn
GSVX574I (MAIN) IMSDATA task termination complete
GSVX592W (MAIN) RESTART IMSDATA not supported
Note: The 'xx' in GSVPDBxx can be 81, 91, 10, or 11,
depending on the release of IMS being used.
Note: The 'yy' in LKyy$$ can be 31 or 64, depending on
whether the locks are in 31 bit or 64 bit storage.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, messages similar to the above will be seen
on the user's terminal, but the GSVX451E message will be one of
the following:
GSVX451E Abend S0C4-nn in IMSLOCKS command
GSVX451E Abend S0C4-nn in IMSOVER command
GSVX451E Abend S0C4-nn in IMSRACT command
IMPACT:
If the abend occurs during IMS Data Collection, the IMSDATA task
will abend. Since an automatic restart of the IMSDATA task is
not allowed, IMS data collection will cease and no further IMS
monitoring will be done until the IMSDATA task is manually
restarted from the ASADMIN command display.
If the abend occurs due to a user issuing the IMSLOCKS, IMSOVER,
or IMSRACT commands, the user's session will abend and need to be
restarted.
CIRCUMVENTION:
None.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
PRE(RO58678) SUP(TSC7380).
CA SYSVIEW Performance Management 12.7 130
CA RS 1309 - PTF RO60328 DetailsCA SYSVIEW Performance Management 12.7 130
CA RS 1309 - PTF RO60328 Details
Release Service Details12.7 RO60328 RO60328 M.C.S. ENTRIES = ++PTF(RO60328)
DESC(Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$)
/*
PROBLEM DESCRIPTION:
Possible abend S0C4-11 Mod GSVXFLDR Rtn FINT$$ when
trying to view capture data sets created
by a release beyond r13.5 from a r13.5 or lower release.
SYMPTOMS:
Possible abend messages include:
GSVX451E Abend S0C4-11 in MTT command
GSVX472I Userid DOSDA01 Terminal A55TG005 Interface VTAM
GSVX452I SYSVIEW SRB in control at entry to abend
GSVX453I Diagnostics for SRB in control at entry to abend
GSVX457I Psw 078C1000 88AE7092 Ilc 4 Intc 11
GSVX477I Key 8 State SUP Am 31 Asc PRI
GSVX458I Module GSVXNUC Addr 0883D000 Offset 002AA092
GSVX458I NucMod GSVXFLDR Addr 08AE6180 Offset 00000F12
GSVX473I Routne FINT$$ Addr 08AE6BF0 Offset 000004A2
GSVX459I Data at PSW addr 08AE708C
GSVX460I A1CCA784 00349110 8027A7E4
GSVX455I General registers at entry to abend
GSVX467I R0-R1 00000000_00000040 00000000_00000000
GSVX467I R2-R3 00000000_35EB32C4 00000000_000007F6
GSVX467I R4-R5 00000000_0005E288 00000000_00000A7D
GSVX467I R6-R7 00000000_00131BC4 00000000_0000307B
GSVX467I R8-R9 00000000_35F6BFEC 00000000_339E2520
GSVX467I R10-R11 00000000_08AED650 00000000_33687000
GSVX467I R12-R13 00000000_08AE6BF0 00000000_3395B900
GSVX467I R14-R15 00000000_88AE6C88 00000000_00000000
GSVX475I Access registers at entry to abend
IMPACT:
From a prior release, you are unable to view capture files created
by a release beyond r13.5.
CIRCUMVENTION:
View the capture data from the release it was created from.
PRODUCTS AFFECTED:
CA SYSVIEW 12.7
*/.
++VER(Z038) FMID(CNM4C70)
SUP(TSC7381)
PRE(RO25393,RO28518,RO30244).
Top Related