CA SYSVIEW Performance Management 13.7 1 CA RS · PDF file13.7 RO54175 Correct CCI time outs and return ... RO59346 XSCONN command fails from ISPF interface ... RO56815 Incorrect Parms

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





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





RO57739 GSV3650E/IXL013I IXLCONN request failed for CTSQUEUE cmd

RO57926 U2999-1101 U0017 Abend, COMMON command looping









RO58618 USTOPPED/PSTOPPED status handled incorrectly for IMS commands














RO60879 TSD5229 PROBLEMS WITH ALERT ACTIONS AND RELATED ONLINE HELP

RO61838 Contain incorrect prereq PTF number W/RO60879






13.0 RO49909 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$










RO58949 GSVX451E Abend S0C4-10 when issuing MIBWALK or MIBBROWSE cmd



RO59390 ABEND S0C4-11 IN GSVPDB91 ISSUING IMSPSBS COMMAND



RO59562 ESRT014E ADD FAILED WHEN ATTEMPTING TO ADD AN EXTENDED SVC




RO60387 Missing IMS transactions from IMS Connect







12.7 RO49053 Loop in OUTPUT command followed by abend U0017-001

RO50182 ABEND S0C7 GSVKSPAC issuing SPACE for EAV volumes






RO56828 ASRESUME command not working against an unquiesced job





RO58978 GSVX451E Abend S0C4-10 when issuing MIBWALK and MIBBROWSE cmd

RO59191 JES command display not updating properly when PREFIX changed




RO60328 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$


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






RO56828 ASRESUME command not working against an unquiesced job





RO58978 GSVX451E Abend S0C4-10 when issuing MIBWALK and MIBBROWSE cmd

RO59191 JES command display not updating properly when PREFIX changed




RO60328 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$

The CA RS 1309 service count for this FMID is 18


CA RS 1309 Service List for CNM4D00CA SYSVIEW Performance Management 6

CA RS 1309 Service List for CNM4D00


CNM4D00 RO49909 Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$










RO58949 GSVX451E Abend S0C4-10 when issuing MIBWALK or MIBBROWSE cmd



RO59390 ABEND S0C4-11 IN GSVPDB91 ISSUING IMSPSBS COMMAND



RO59562 ESRT014E ADD FAILED WHEN ATTEMPTING TO ADD AN EXTENDED SVC




RO60387 Missing IMS transactions from IMS Connect







CNM4D50 RO49066 GSVX031E & abend S306-0C when SCSQLOAD not APF auth'ed


RO56326 Incorrect Parms passed to Trap & Capture for CICS threshold



RO56815 Incorrect Parms passed to OPSMVS when CICS threshold triggers

RO57081 JOBCLASS missing entries





RO57739 GSV3650E/IXL013I IXLCONN request failed for CTSQUEUE cmd
























RO60879 TSD5229 PROBLEMS WITH ALERT ACTIONS AND RELATED ONLINE HELP

RO61838 Contain incorrect prereq PTF number W/RO60879






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



RO57265 IMSRACT INCORRECT FIELDS FOR NON-FASTPATH REGION


RO57386 GSV2570E running installation conversion jobs



RO57768 Profile conversion problem for several JES commands

RO57923 U2999-1101 Abend, COMMON command looping






RO58543 JES SPOOL USED PERCENTAGE CALCULATED INCORRECTLY



RO58670 IMSTRANS not showing USTOPPED status for transactions

RO58800 Fields not populated in IMSIMTR transaction record DSECT






RO59445 Abend S0C4 dumping address in PAGES or SEGMENTS display




RO59735 PERFORMANCE IMPROVEMENT FOR IMSOVER COMMAND


RO59859 GSVX554E WHEN XSYS CMD W/ NOXSDATA BUT XSYSTEM IS DISABLED

RO59920 CICSOPTS option MONITOR-RESTORE-SETTINGS handled incorrectly



RO60173 TSUMRATE always displays zeros in CSTATUS



RO61542 GSVX753I ALET ADD MESSAGE LOGGING ON W/RO61045



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).





DESC(VARIOUS PROBLEMS RELATED TO CA CHORUS R3 TSF)

/*


This addresses several problems related to the SYSVIEW integration

with CA Chorus r3 and Time Series Facility (TSF).

1. IMS and/or WebSphere MQ metric resource data may be sent to TSF

for an IMS or MQ queue manager for which it was not requested,

resulting in errors in the SYSVIEW STC.

2. The SYSVIEW CICS Option data collection metric TDATTIME is not

defined correctly making it unable to be sent to TSF.

3. The SYSVIEW CICS Option GSVCTSFT subtask is not performing lookups

of TSF-eligible data collection metrics as efficiently as it could.

4. The online help for the TSFLOGR command was missing data fields

TCPData and TCPMetrics.

5. The common storage tracking/usage data returned to Chorus is in a

detailed format rather than a summary version. The $CHXAPI profile

in SYSVIEW specifies OPTIONS DETAIL rather than OPTIONS SUMMARY for

the VSMTRACK command.

6. Variables that had a collected value of zero for the collection

interval were not being sent to TSF.

7. Values for the CPUPLPAR variable for all processors were being

added into the IIP processor collection bucket in the TSF database.

This fix is also providing an updated SYSVTSF dashboard and help,

a new CHORUS dashboard, as well as two additional diagnostic

capture members DIAGCHOR and DIAGTSF.

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 STARTPD STPD9004

TCP$004E EZASMI TYPE=WRITE failed, Connection is broken


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:



Release Service DetailsNone.

PRODUCTS AFFECTED:

CA SYSVIEW r13.7

*/.


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.

).





DESC(JJOBQUE/JOUTQUE/JHELDQUE No jobs displayed if PREFIX)

/*


If a PREFIX or OWNER value is defined and no parameters are entered

with the JOUTQUE or JJOBQUE commands, no jobs are displayed.

If a PREFIX or OWNER value is defined and no parameters are entered

on the JHELDQUE command, it is possible that no jobs will be

displayed.

If output classes are specified with the JHELDQUE command that cause

no jobs to be displayed, and then the JHELDQUE command is entered from

the JHELDQUE display with no parameters, no jobs will be displayed.

The output classes entered with the previous JHELDQUE command were

not being cleared.

On a JES3 system, JHELDQUE, JOUTQUE, or JJOBQUE commands will encounter

S0C4-04 abend when issued for an unsupported version of JES3 such

as 1.12 and lower.

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

*/.


PRE(RO55171)

SUP(TSD7078).





DESC(JOBCLASS missing entries or Abend S0C4 U299-802)

/*


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

*/.


SUP(TSD7081).





DESC(JES3 long response time when displaying many jobs)

/*


In JES3 environments, the following command displays may experience long

response times when displaying a relatively large number of jobs:

JHELDQUE, JJOBBQUE, JOBSUM, JOUTQUE

This problem will only occur when running SYSVIEW in a JES3 environment.

In addition, this problem will only occur when issuing the commands

listed above with either the subcommand OPTIONS DETAIL in effect, or

with the DETAIL command parameter in effect.

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

*/.


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.

).





DESC(ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS)

/*


Abend S0C4-3B can occur in SYSVIEW/CICS module GSVCMSCR due to the

high halves of 64-bit registers not being restored.

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

*/.


SUP(TSD7083).


SYSTEM

REASON(RESTART)

DATE(13095)

COMMENT(




).





DESC(MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS.)

/*


When a connection can not be made to a WebSphere MQ queue

manager, there may be an excessive amount of 'GSVX702I

connecting' errors followed by 'GSVX998E failed' error messages

which are issued from the MQSDATA subtask during every data

collection interval.

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

*/.


SUP(TSD7084)

PRE(RO55339).


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.



The default value will be 2 minutes and may be adjusted as

necessary.

).





DESC(IMSRACT INCORRECT FIELDS FOR NON-FASTPATH REGION)

/*


Several fields on the IMSRACT display, which is invoked by issuing

the Select line command from the IMSREGNS command display, may be

blank or contain garbage for non-Fast Path IMS regions.

Additionally, the Database Status section on IMSRACT only shows the

address of the SSA (Segment Search Argument) and IO Area (DB record

area), so this is being enhanced to also include a partial dump of

the real time data for each of these areas.

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

*/.


PRE(RO53671)

SUP(TSD7085).


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.

).





DESC(ROSC011W Timeout waiting for ROSCOE job to respond)

/*


The ROSACT command produces the following error message:

ROSC011W Timeout waiting for ROSCOE job jjjjjjjj to respond

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:


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).


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.

).





DESC(GSV2570E running installation conversion jobs)

/*


Running the Security Conversion, INST0050, or the Profile Conversion,

INST0051, installation jobs may result in an error which causes the

conversion to fail. This problem will only occur if all of the following

conditions are true:

The Security Conversion or the Profile Conversion is used to convert

a prior release configuration.

Neither the SYSVIEW main address space nor the SYSVIEW user address for

SYSVIEW 13.5 or SYSVIEW 13.7 have been started on the LPAR where the

conversion job is being run.

The Dynamic Install program, GSVXINST, which is part of install step

INST0100 and included in the SYSVIEW/SYSVUSER PROC by default, has not

been run for SYSVIEW 13.5 or SYSVIEW 13.7 on the LPAR where the

conversion job is being run.

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

*/.


SUP(TSD7087).





DESC(INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM)

/*


New CICS configuration option PERFORMANCE-DATA-SEGLIMIT-DB2 was

introduced in the CICSOPTS parmlib member in SYSVIEW 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

*/.


PRE(RO56237)

SUP(TSD7088).


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.




).





DESC(GSVC015I Message contains incorrect jobname)

/*


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

*/.


SUP(TSD7089).


SYSTEM

REASON(ACTION)

DATE(13102)

COMMENT(




).





DESC(Profile conversion problem for several JES commands)

/*


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

*/.


SUP(TSD7091).





DESC(U2999-1101 Abend, COMMON command looping)

/*


The COMMON command encountered error and continue to loop until exceeded

the CPU time limit which caused user address space to abend with the

following code:

Release AbendCode ReasonCode

12.7 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

*/.


SUP(TSD7093).





DESC(AUDIT/IMS reports and FROM/TO commands showing wrong times)

/*


Two problems exist related to timestamps and intervals of records

returned on reports:

1. Running a report may result in incorrect timestamps on the returned

report data. Specifically, the timestamps on a report are shifted by the

local time zone offset from GMT. This problem occurs only for SYSVIEW

AUDIT reports and SYSVIEW IMS transaction reports.

2. Running a report using relative dates and times with the FROM and

TO commands may result in records being falsely included or excluded

from a report. For example:

FROM -1 DAYS AT 00:00:00

TO -1 DAYS AT 23:59:59

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:


TO -0 DAYS AT 00:00:24

PRODUCTS AFFECTED:

CA EXPLORE Report Writer 13.7

*/.


PRE(RO56233)

SUP(TSD7094).





DESC(CSTATES SYSTEM command orphans storage)

/*


Issuing the CSTATES SYSTEM command can causes memory leaks, where

duplicate buffers of data are being created with only one getting freed.

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

*/.


SUP(TSD7096).





DESC(ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS)

/*


Abend S0C4 is possible in any address space making WebSphere MQ

requests if parameter MONITOR-MQS-REQUESTS is set to YES in the

MQSDATA parmlib member. The abend occurs in module GSVSHnnn,

where nnn = the MQ version (GSVSH600, GSVSH700, GSVSH710).

This specific problem was related to an incorrect handle specified

on an MQ request.

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

*/.


SUP(TSD7097).





DESC(XMDR002W NRAS buffer max of 256K reached)

/*


When issuing the ASLIST or ASLOST command it is possible the command

may produce error messages indicating the 256K buffer max has been

reached.

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

*/.


SUP(TSD7098)

PRE(RO52763).


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.

).





DESC(MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E)

/*


A timing-related issue exists during the startup of SYSVIEW and

SYSVUSER, where it is possible for user sessions to erroneously

think the SYSVIEW STC is not active.

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

*/.


SUP(TSD7099).





DESC(JES SPOOL USED PERCENTAGE CALCULATED INCORRECTLY)

/*


The SPOOL space used percent was not being calculated correctly. It

was including INACTIVE spool volumes in the calculation.

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

*/.


SUP(TSD7100)

PRE(RO56990).





DESC(IMS DLI variable totals display incorrectly greater than 2G)

/*


Certain IMS DLI variables (SMF type 255 subtype 33 & 35 records) displayed

by Report Writer may be inaccurate. This problem occurs when the

accumulated totals exceed a value of 2,147,483,647 (2G-1)

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:


*/.


PRE(RO55807,RO56233)

SUP(TSD7101).





DESC(compatibility support for future XSYSTEM changes)

/*


During cross system commands, the receiving system validates the

data by checking it's identifier and length. If the identifier

or length was not equal to what was expected then the data is

considered invalid.

This change modifies the validation procedure from an exact

comparison to a check against a minimum length. To allow for

future changes to the format of the returned data.

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

*/.


SUP(TSD7102).





DESC(IMSTRANS not showing USTOPPED status for transactions)

/*


This fix will address the following IMS problems:

1. The IMSTRANS command display is not showing a USTOPPED/PSTOPPED status

for transactions that are in the USTOPPED/PSTOPPED state.

2. The PSTOPPED and USTOPPED IMS exception alerts are not being triggered

for the IMTSSTOP state exceptions.

3. The PTran column on the IMSOVER display is not counting any USTOPPED

transactions.

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

*/.


PRE(RO55087)

SUP(TSD7103).





DESC(Fields not populated in IMSIMTR transaction record DSECT)

/*


The distributed IMSIMTR macro, which can be used to map the SYSVIEW

for IMS transaction records that are shown on the IMSTLOG command

display, contains fields related to IMS Fast Path transactions that are

not populated in the IMTR_CLK segment.

In addition, a new field will be added for IMS Fast Path transactions

to specify the start time of a transaction in store clock format in the

IMTR_CLK segment.

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

*/.


PRE(RO55627 RO55929)

SUP(TSD7105).


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

).





DESC(Display does not update properly when PREFIX values changed)

/*


The display does not update properly when the PREFIX values changed

for the following JES commands:

JJOBQUE, JHELDQUE, JOUTQUE, JTRANQUE, JOBSUM, LISTINP, and ACTIVITY

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

*/.


PRE(RO56491, RO56369)

SUP(TSD7107).





DESC(IMTSQUE threshold not working for IMS shared queues)

/*


In an IMS shared queue environment, the IMTSQUE variable threshold may

not trigger alerts. The Queue field on the IMSOVER and IMSTRANS command

display may also only reflect the transaction counts queued from the

target ASID IMS.

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

*/.


PRE(RO55339)

SUP(TSD7108).





DESC(XSCONN command fails from ISPF interface)

/*


Issuing the XSCONN command to connect to another instance of SYSVIEW

from the ISPF interface will fail, if the SYSVIEW release in LINKLIST

does not match the release that the user is currently running and a

STEPLIB does not exist in the user's address space.

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

*/.


PRE(RO58616)

SUP(TSD7109).





DESC(Abend S0F8-04 issuing LOGREC CLEAR subcommand)

/*


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



GSVX457I Psw 078C1000 address1 Ilc 2 Intc 2A


GSVX458I Module GSVKLOGC Addr address2 Offset <offset>


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

*/.






DESC(JOBNAME and SYSID ID Options return incorrect data)

/*


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:


*/.


SUP(TSD7111).





DESC(Abend S0C4 dumping address in PAGES or SEGMENTS display)

/*


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


GSVX458I Module GSVKPAGE Addr 3B43A6D8 Offset 00000F92


GSVX473I Routne REFR$$ Addr 3B43B5D0 Offset 0000009A

GSVX459I Data at PSW addr 3B43B664

GSVX460I 12FFA774 0023BF1F 10201A31


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


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

*/.


SUP(TSD7112).





DESC(LGCONN/LGJOBS cmds not showing data with IBM zAware)

/*


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

*/.


SUP(TSD7114).





DESC(IMS Transaction missing from IMSTLOG)

/*


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

*/.


PRE(RO58800)

SUP(TSD7115).





DESC(JCOPYOUT abend S002-18 / record length incorrect)

/*


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

*/.


SUP(TSD7116).





DESC(PERFORMANCE IMPROVEMENT FOR IMSOVER COMMAND)

/*


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

*/.


PRE(RO53671 RO58670)

SUP(RO52603 RO54305 TSD7118).





DESC(ASLIST MAXUSER counts and %-ages do not add up)

/*


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

*/.


PRE(RO54995) SUP(TSD7119).





DESC(GSVX554E WHEN XSYS CMD W/ NOXSDATA BUT XSYSTEM IS DISABLED)

/*


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

*/.


PRE(RO59346)

SUP(TSD7120).





DESC(CICSOPTS option MONITOR-RESTORE-SETTINGS handled incorrectly)

/*


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

*/.


PRE(RO57495)

SUP(TSD7121).


SYSTEM

REASON(ACTION)

DATE(13163)

COMMENT(




).





DESC(Abend S0C4 in Data Collection or IMSLOCKS command)

/*


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.


or IMSRACT commands, the user's session will abend and need to be

restarted.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.7

*/.







DESC(SELECT with CW and NW not supporting multiple operands)

/*


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

*/.


PRE(RO54185)

SUP(TSD7125).





DESC(TSUMRATE always displays zeros in CSTATUS)

/*


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

*/.


SUP(TSD7126).


SYSTEM

REASON(ACTION)

DATE(13171)

COMMENT(




).





DESC(IMSTLOG abended transactions not showing correct tran type)

/*


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

*/.


PRE(RO59631)

SUP(TSD7127).


SYSTEM

REASON(DYNACT)

DATE(13175)

COMMENT(



member IMSDATA:





).





DESC(Possible looping in dependent region during shutdown)

/*


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

*/.


SUP(TSD7133 AR60832)

PRE(RO60200).


SYSTEM

REASON(DYNACT)

DATE(13190)

COMMENT(



member IMSDATA:





).





DESC(GSVX753I ALET ADD MESSAGE LOGGING ON W/RO61045)

/*


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

*/.


PRE(RO61045)

SUP(AR61045 TSD7147).





DESC(GSVX031E & abend S306-0C when SCSQLOAD not APF auth'ed)

/*


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

*/.







DESC(CPROGRAM size field is zero after NEWCOPY or PHASEIN linecmd)

/*


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

*/.


SUP(TSD5179).





DESC(Incorrect Parms passed to Trap & Capture for CICS threshold)

/*


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

*/.


PRE(RO55535)

SUP(TSD5184).





DESC(JES3 JOBSUM command not returning all requested jobs)

/*


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

*/.


PRE(RO55441)

SUP(TSD5185).





DESC(DEST command not working properly for JES3)

/*


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

*/.


PRE(RO43574,RO56427)

SUP(TSD5186).





DESC(Incorrect Parms passed to OPSMVS when CICS threshold triggers)

/*


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

*/.


SUP(TSD5190).


SYSTEM

REASON(ACTION)

DATE(13086)

COMMENT(

To implement updated modules:




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



Release Service Detailsdetail parameters format.

).





DESC(JOBCLASS missing entries)

/*


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

*/.


PRE(RO45843)

SUP(TSD5192).





DESC(ABEND S0C4-3B IN MODULE GSVCMSCR IN CICS)

/*


Abend S0C4-3B can occur in SYSVIEW/CICS module GSVCMSCR due to the

high halves of 64-bit registers not being restored.

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

*/.


PRE(RO42952)

SUP(TSD5193).


SYSTEM

REASON(RESTART)

DATE(13095)

COMMENT(




).






/*




SYMPTOMS:





message:


IMPACT:





CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.



SYSTEM

REASON(RESTART)

DATE(13101)

COMMENT(




the ROSCOE region.

).





DESC(INCREASE CICS PERFORMANCE-DATA-SEGLIMIT-DB2 MAXIMUM)

/*


New CICS configuration option PERFORMANCE-DATA-SEGLIMIT-DB2 was

introduced in the CICSOPTS parmlib member in SYSVIEW 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

*/.


SUP(TSD5195).


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.




).





DESC(GSVC015I Message contains incorrect jobname)

/*


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

*/.


SUP(TSD5196).


SYSTEM

REASON(ACTION)

DATE(13102)

COMMENT(




).





DESC(GSV3650E/IXL013I IXLCONN request failed for CTSQUEUE cmd)

/*


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

*/.


SUP(TSD5197).





DESC(U2999-1101 U0017 Abend, COMMON command looping)

/*




following code:


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


executed again:


IMPACT:

User session terminates with U2999-1101 or U0017-001 abend.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


SUP(TSD5198).






/*





SYMPTOMS:







IMPACT:


values exceed 2,147,483,647 (2G-1).

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


*/.


PRE(RO56000,RO55742)

SUP(TSD5200).






/*












TO -1 DAYS AT 23:59:59

SYMPTOMS:












IMPACT:




commands.

CIRCUMVENTION:

1. None.






TO -0 DAYS AT 00:00:24

PRODUCTS AFFECTED:


*/.


PRE(RO47847 RO55742)

SUP(TSD5201).





DESC(ABEND S0C4 IN JOB MAKING WEBSPHERE MQ REQUESTS)

/*


Abend S0C4 is possible in any address space making WebSphere MQ

requests if parameter MONITOR-MQS-REQUESTS is set to YES in the

MQSDATA parmlib member. The abend occurs in module GSVSHnnn,

where nnn = the MQ version (GSVSH600, GSVSH700, GSVSH710).

This specific problem was related to an incorrect handle specified

on an MQ request.

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

*/.


SUP(TSD5202).





DESC(MQSDATA EXCESSIVE GSVX998E & GSVX702I FAILED MSGS.)

/*


When a connection can not be made to a WebSphere MQ queue

manager, there may be an excessive amount of 'GSVX702I

connecting' errors followed by 'GSVX998E failed' error messages

which are issued from the MQSDATA subtask during every data

collection interval.

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:



IMPACT:

Excessive amount of error messages issued to the console.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


SUP(TSD5203)

PRE(RO49066,RO55263).


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.



The default value will be 2 minutes and may be adjusted as

necessary.

).






/*


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:



been exceeded:


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

*/.


PRE(RO45009)

SUP(TSD5204).





DESC(XMDR002W NRAS buffer max of 256K reached)

/*


When issuing the ASLIST or ASLOST command it is possible the command

may produce error messages indicating the 256K buffer max has been

reached.

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

*/.


SUP(TSD5205)

PRE(RO52625).


SYSTEM

REASON(DYNACT)

DATE(13137)

COMMENT(





1. Apply the fix.



).





DESC(compatibility support for future XSYSTEM changes)

/*


During cross system commands, the receiving system validates the

data by checking it's identifier and length. If the identifier

or length was not equal to what was expected then the data is

considered invalid.

This change modifies the validation procedure from an exact

comparison to a check against a minimum length. To allow for

future changes to the format of the returned data.

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

*/.


PRE(RO44979, RO47747)

SUP(TSD5206).





DESC(MENU SHOWS MAIN SERVICES INACTIVE / GSVX340E)

/*


A timing-related issue exists during the startup of SYSVIEW and

SYSVUSER, where it is possible for user sessions to erroneously

think the SYSVIEW STC is not active.

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

*/.


SUP(TSD5207).





DESC(USTOPPED/PSTOPPED status handled incorrectly for IMS commands)

/*








transactions.

SYMPTOMS:





IMPACT:




IMSALERT display.


IMSOVER display.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


PRE(RO53884)

SUP(TSD5208).






/*




JTRANQUE, JOBSUM, LISTINP, and ACTIVITY

SYMPTOMS:



IMPACT:


CIRCUMVENTION:


PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


PRE(RO51780, RO56619)

SUP(TSD5211).






/*





target ASID IMS.

SYMPTOMS:



IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


PRE(RO45326, RO55263)

SUP(TSD5212).





DESC(Abend S0F8-04 issuing LOGREC CLEAR subcommand)

/*


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



GSVX457I Psw 078C1000 address1 Ilc 2 Intc 2A


GSVX458I Module GSVKLOGC Addr address2 Offset <offset>


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

*/.






DESC(XSCONN command fails from ISPF interface)

/*


Issuing the XSCONN command to connect to another instance of SYSVIEW

from the ISPF interface will fail, if the SYSVIEW release in LINKLIST

does not match the release that the user is currently running and a

STEPLIB does not exist in the user's address space.

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

*/.


PRE(RO58500)

SUP(TSD5214).






/*







SYMPTOMS:






output:


IMPACT:




CIRCUMVENTION:





PRODUCTS AFFECTED:


*/.


PRE(RO45533)

SUP(TSD5215).





DESC(IMS Transaction missing from IMSTLOG)

/*


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

*/.


PRE(RO55226)

SUP(TSD5216).





DESC(JCOPYOUT abend S002-18 / record length incorrect)

/*


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

*/.


PRE(RO48686)

SUP(TSD5218).






/*





SYMPTOMS:






any data.

IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


SUP(TSD5219).





DESC(ASLIST MAXUSER counts and %-ages do not add up)

/*


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

*/.








/*




SYMPTOMS:



display.

IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


PRE(RO59526)

SUP(TSD5223).


SYSTEM

REASON(DYNACT)

DATE(13172)

COMMENT(



member IMSDATA:





).






/*



SYMPTOMS:











commands:

IMSOVER

IMSRACT















Note: The 'xx' in GSVPDBxx can be 10, 11, or 12,







the following:




IMPACT:








restarted.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.








/*




SYMPTOMS:



operand.

For example, issuing the following command in the LISTJOBS command display:

SELECT queue cw exec or stat eq hldc


- 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


IMPACT:


CIRCUMVENTION:



PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.


PRE(RO54184)

SUP(TSD5225).






/*



IMS dependent region that is being monitored by SYSVIEW. This

problem results in the region entering a loop and not terminating.

SYMPTOMS:




IMPACT:



CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.5

*/.



PRE(RO59965).


SYSTEM

REASON(DYNACT)

DATE(13190)

COMMENT(



member IMSDATA:





).





DESC(PROBLEMS WITH ALERT ACTIONS AND RELATED ONLINE HELP)

/*


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

*/.


PRE(RO56815 RO55950 RO47437)

SUP(TSD5229).





DESC(Contain incorrect prereq PTF number W/RO60879)

/*


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

*/.


PRE(RO56815 RO56326 RO47437)

SUP(RO60879 AR60879 TSD5238).





DESC(Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$)

/*


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



GSVX457I Psw 078C1000 88AE7092 Ilc 4 Intc 11


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


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


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

*/.


SUP(TSD0215)

PRE(RO34022).






/*





SYMPTOMS:



IMPACT:



CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW r13.0

*/.


SUP(TSD0274).






/*




SYMPTOMS:




IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW r13.0

*/.


PRE(RO43685)

SUP(TSD0280).






/*




SYMPTOMS:


JOBSUM

LISTINP




IMPACT:


commands.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW r13.0

*/.


PRE(RO32650)

SUP(TSD0281).






/*




SYMPTOMS:





message:


IMPACT:





CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.



SYSTEM

REASON(RESTART)

DATE(13101)

COMMENT(




the ROSCOE region.

).






/*




following code:


12.7 U0017 001

13.0 U0017 001

13.5 U2999 1101

13.7 U2999 1101

SYMPTOMS:



executed again:


IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


SUP(TSD0286).






/*












TO -1 DAYS AT 23:59:59

SYMPTOMS:












IMPACT:




commands.

CIRCUMVENTION:

1. None.






TO -0 DAYS AT 00:00:24

PRODUCTS AFFECTED:


*/.


PRE(RO47848 RO56234)

SUP(TSD0288).






/*





SYMPTOMS:



been exceeded:


IMPACT:

Once private storage for the user is exhausted, all subsequent SYSVIEW

commands from the user will fail.

CIRCUMVENTION:



PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


PRE(RO44929)

SUP(TSD0289).






/*





SYMPTOMS:







IMPACT:


values exceed 2,147,483,647 (2G-1).

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


*/.


PRE(RO56003,RO56234)

SUP(TSD0290).






/*








transactions.

SYMPTOMS:





IMPACT:




IMSALERT display.


IMSOVER display.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


PRE(RO34390,RO55204,RO59390)

SUP(TSD0291).





DESC(GSVX451E Abend S0C4-10 when issuing MIBWALK or MIBBROWSE cmd)

/*


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


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

*/.


SUP(TSD0292).






/*




JTRANQUE, JOBSUM, LISTINP, and ACTIVITY

SYMPTOMS:



IMPACT:


CIRCUMVENTION:


PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


PRE(RO51781, RO56620)

SUP(TSD0293).






/*





target ASID IMS.

SYMPTOMS:



IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


PRE(RO45327)

SUP(TSD0294).





DESC(ABEND S0C4-11 IN GSVPDB91 ISSUING IMSPSBS COMMAND)

/*


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

*/.


SUP(TSD0295)

PRE(RO53886).






/*







SYMPTOMS:






output:


IMPACT:




CIRCUMVENTION:





PRODUCTS AFFECTED:


*/.


PRE(RO45534)

SUP(TSD0296).






/*





SYMPTOMS:






any data.

IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


SUP(TSD0297).





DESC(ESRT014E ADD FAILED WHEN ATTEMPTING TO ADD AN EXTENDED SVC)

/*


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

*/.


SUP(TSD0298)

PRE(RO52762).


SYSTEM

REASON(DYNACT)

DATE(13164)

COMMENT(





1. Apply the fix.



).






/*



SYMPTOMS:











commands:

IMSOVER

IMSRACT






















the following:




IMPACT:








restarted.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.








/*




SYMPTOMS:



operand.

For example, issuing the following command in the LISTJOBS command display:

SELECT queue cw exec or stat eq hldc


- 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


IMPACT:


CIRCUMVENTION:



PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


PRE(RO54183)

SUP(TSD0300).






/*




SYMPTOMS:



display.

IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.


PRE(RO55460,RO60387)

SUP(TSD0301).


SYSTEM

REASON(DYNACT)

DATE(13176)

COMMENT(



member IMSDATA:





).





DESC(Missing IMS transactions from IMS Connect)

/*


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

*/.


SUP(TSD0302)

PRE(RO48405,RO41710).


SYSTEM

REASON(DYNACT)

DATE(13177)

COMMENT(



member IMSDATA:





).






/*



IMS dependent region that is being monitored by SYSVIEW.

This problem results in the region entering

a loop and not terminating.

SYMPTOMS:




IMPACT:



CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 13.0

*/.



PRE(RO60201).


SYSTEM

REASON(DYNACT)

DATE(13190)

COMMENT(



member IMSDATA:





).





DESC(Loop in OUTPUT command followed by abend U0017-001)

/*


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).





DESC(ABEND S0C7 GSVKSPAC issuing SPACE for EAV volumes)

/*


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


GSVX458I Module GSVKSPAC Addr 19845000 Offset 000031AA

GSVX473I Routne FALL$$ Addr 198480C0 Offset 000000EA


GSVX460I FC73910C 9024F877 93E8910C


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


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

*/.


SUP(TSC7332)

PRE(RO25152).






/*




SYMPTOMS:





message:


IMPACT:





CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 12.7

*/.

++VER(Z038) FMID(CNM4C70) SUP(TSC7354).

++HOLD(RO53318) FMID(CNM4C70)

SYSTEM

REASON(RESTART)

DATE(13101)

COMMENT(




the ROSCOE region.

).






/*





SYMPTOMS:



IMPACT:



CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW r12.7

*/.


SUP(TSC7365).






/*





SYMPTOMS:







IMPACT:


values exceed 2,147,483,647 (2G-1).

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


*/.


PRE(RO56036,RO30663)

SUP(TSC7368).






/*




SYMPTOMS:




IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW r12.7

*/.


PRE(RO43686)

SUP(TSC7369).






/*




SYMPTOMS:


JOBSUM

LISTINP




IMPACT:


commands.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW r12.7

*/.


PRE(RO26596,RO26400)

SUP(TSC7370).





DESC(ASRESUME command not working against an unquiesced job)

/*


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

*/.


PRE(RO31271)

SUP(TSC7371).






/*




following code:


12.7 U0017 001

13.0 U0017 001

13.5 U2999 1101

13.7 U2999 1101

SYMPTOMS:



executed again:


IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 12.7

*/.


SUP(TSC7372).






/*












TO -1 DAYS AT 23:59:59

SYMPTOMS:












IMPACT:




commands.

CIRCUMVENTION:

1. None.






TO -0 DAYS AT 00:00:24

PRODUCTS AFFECTED:


*/.


PRE(RO47849)

SUP(TSC7373).






/*





SYMPTOMS:



been exceeded:


IMPACT:

Once private storage for the user is exhausted, all subsequent SYSVIEW

commands from the user will fail.

CIRCUMVENTION:



PRODUCTS AFFECTED:

CA SYSVIEW 12.7

*/.


PRE(RO45035)

SUP(TSC7374).






/*








transactions.

SYMPTOMS:





IMPACT:




IMSALERT display.


IMSOVER display.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 12.7

*/.


PRE(RO34102,RO53887)

SUP(TSC7375).





DESC(GSVX451E Abend S0C4-10 when issuing MIBWALK and MIBBROWSE cmd)

/*


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


GSVX463I No active load module found


GSVX460I 00000000 00000000 00000000


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

*/.


SUP(TSC7376).





DESC(JES command display not updating properly when PREFIX changed)

/*




JOBSUM, LISTINP, and ACTIVITY

SYMPTOMS:



IMPACT:


CIRCUMVENTION:


PRODUCTS AFFECTED:

CA SYSVIEW 12.7

*/.


PRE(RO51782, RO56621)

SUP(TSC7377).






/*





target ASID IMS.

SYMPTOMS:



IMPACT:


CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 12.7

*/.


PRE(RO45328, RO25395)

SUP(TSC7378).






/*







SYMPTOMS:






output:


IMPACT:




CIRCUMVENTION:





PRODUCTS AFFECTED:


*/.


PRE(RO33994 RO45535)

SUP(TSC7379).






/*



SYMPTOMS:











commands:

IMSOVER

IMSRACT






















the following:




IMPACT:








restarted.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA SYSVIEW 12.7

*/.


PRE(RO58678) SUP(TSC7380).





DESC(Abend S0C4-11 Mod GSVXFLDR Rtn FINT$$)

/*


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



GSVX457I Psw 078C1000 88AE7092 Ilc 4 Intc 11


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


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


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

*/.


SUP(TSC7381)

PRE(RO25393,RO28518,RO30244).

Documents

CA SYSVIEW Performance Management 13.7 1 CA RS · PDF file13.7 RO54175 Correct CCI time outs and return ... RO59346 XSCONN command fails from ISPF interface ... RO56815 Incorrect Parms