Sysview Install ENU

CA SYSVIEW Performance
Management
Installation Guide
Version 14.0
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to
as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without
the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed
by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing
your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and
CA.
Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may
print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your
employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced
copy.
The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable
license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to
certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY
KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE,
DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST
INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE
POSSIBILITY OF SUCH LOSS OR DAMAGE.
The use of any software product referenced in the Documentation is governed by the applicable license agreement and such
license agreement is not modified in any way by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions
set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or
their successors.
Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to
their respective companies.
CA Technologies Product References
This document references the following CA products:
CA Datacom/DB (CA Datacom/DB)
CA Datacom CICS Services (CA Datacom CICS Services)
CA Insight Database Performance Monitor for DB2 for z/OS (CA Insight for DB2)
CA Chorus Software Manager (CA MSM)
CA Chorus (CA Chorus)
CA Roscoe Interactive Environment (CA Roscoe)
CA Common Services (CCS)
CA ACF2 for z/OS
CA Top Secret for z/OS (CA Top Secret for z/OS)
(
CA Easytrieve Report Generator (CA Easytrieve RG)

CA SYSVIEW Performance Management (CA SYSVIEW PM)
CA SYSVIEW Performance Management CA Datacom Option (CA SYSVIEW PM CA
Datacom Option)
CA SYSVIEW Performance Management Option for CICS (CA SYSVIEW PM Option
for CICS)
CA SYSVIEW Performance Management Option for IMS (CA SYSVIEW PM Option
for IMS)
CA SYSVIEW Performance Management Option for TCP/IP (CA SYSVIEW PM Option
for TCP/IP)
CA SYSVIEW Performance Management for CA APM (CA SYSVIEW for CA APM)
CA MIM Resource Sharing (CA MIM RS)
CA NSM
CA Service Desk (CA SD)
CA SymDump System (CA SymDump)
Contact CA Technologies
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
Online and telephone contact information for technical assistance and customer
services
Information about user communities and forums
Product and documentation downloads
CA Support policies and guidelines
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
If you have comments or questions about CA Technologies product documentation, you

can send a message to [email protected].
To provide feedback about CA Technologies product documentation, complete our

short customer survey which is available on the CA Support website at
http://ca.com/docs.
Documentation Changes
The following documentation updates have been made since the last release of this
documentation:
How the Installation Process Works (see page 15): Updated the topic.
Integration with Other CA Products: (see page 16) Updated the CA APM topic to
include IMS Transaction Tracing.
Installation Preparation (see page 19):
Added CA Master to the list of CA Common Services for z/OS components and
features.
Changed CA Health Checker to CA Health Checker Common Service.
Software Requirements: (see page 20) Updated the topic.
CA Common Services Requirements (see page 22): Added CA Master.
CA Insight for DB2 (see page 22): Added two bullets for XNET and PassTickets.
Concurrent Releases (see page 24): Removed the SVC information.
Available Components (see page 26): Updated CA Insight for DB2.
CA Common Services for z/OS Components (see page 28): Added CA Master
Installing Your Product Using CA CSM (see page 35): Updated the chapter.
Unload the Installation Library (see page 50): Updated step 1.
Modify and Run the Job INSTALL (see page 51):
Removed the SVC number reference.
HQL requirement changed from 20 characters to 24 characters.
Updated SITEDSN to include <dsn_hlq>.
Added IDMS.
Updated (Optional) Create Run-Time SITE Libraries (INST0005) (see page 68).
Apply IBM APARs (see page 75): Updated the topic.
How to Deploy Without CA CSM (see page 76): Removed CAI.SYSVIEW.CNM4BLPA.
GSVIINST Macro - Set INSTALL Parameters (see page 81):
Removed the SVC information.
Removed the AUTHLIB information.
Updated SITEDSN to include <dsn_hlq>.
Added IDMS.
HQL requirement changed from 20 characters to 24 characters.
Output from INSTALL (see page 93):
Removed the Job INST0100.
Run the System Information Utility GSVCUTIL (INST0010) (see page 96): Removed
the SVC information.
System Configuration Options (see page 98):
Updated Security-Validation to include USERDEF.
Update the CICS JCL (see page 150): Removed the LPA reference.
Prepare to Start Your Product (see page 151): Removed the SVC information.
Post-Installation Considerations (see page 155): Removed the SVC information.
Dynamic Installation of CA SYSVIEW (see page 158): New Migration Information
topic.
User Supervisor Call (SVC) Removal (see page 159): New Migration Information
topic.
LPA Load Library Data Set Removal: (see page 159) New Migration Information
topic.
Anchor Address Space Removal (see page 160): New Migration Information topic.
Configuration Options Member - OPTIONS (see page 163): New Migration
Information topic.
External Security (see page 164): New Migration Information topic.
Event Scheduler: (see page 164) New migration topic.
Configuration Options - Parmlib Member CICSOPTS (see page 165): New Migration
Information topic.
Logical Group Definitions Removed - Parmlib Member CICSGRPS (see page 165):
New Migration Information topic.
Logical Groups Overview (see page 165) - New logical groups migration section.
How to Use Logical Groups
Migrating Logical Group Definitions
Use the Warm Start Method
Use the Cold Start Method
Conversion Utility - GSVYLGCV
IMS Dependent Regions - Data Collection (see page 176): New Migration
Information topic.
FMIDs (see page 177): Removed references to unsupported releases.
CAMASTER Services (see page 178): New topic containing FMIDs.
Topics Removed
Run the Dynamic Installation Utility (INST0100)
How the Dynamic Installation Utility Works
Add the LPA Module to the System (Optional)
Contents
Chapter 1: Overview 13
CA SYSVIEW Overview ................................................................................................................................................ 13
CA SYSVIEW Server Overview..................................................................................................................................... 14
Audience .................................................................................................................................................................... 14
How the Installation Process Works........................................................................................................................... 15
Integration with Other CA Products ........................................................................................................................... 16
Chapter 2: Preparing for Installation 19

Installation Preparation.............................................................................................................................................. 19
Software Requirements ............................................................................................................................................. 20
CA Common Services Requirements .......................................................................................................................... 22
CA Insight for DB2 ...................................................................................................................................................... 22
GMI Software Requirements ...................................................................................................................................... 23
IBM REXX Library Requirements ................................................................................................................................ 23
Security Requirements ............................................................................................................................................... 23
Storage Requirements ................................................................................................................................................ 24
Concurrent Releases .................................................................................................................................................. 24
Memory Requirements .............................................................................................................................................. 24
Available Options ....................................................................................................................................................... 25
Available Components ............................................................................................................................................... 26
IBM RMF ..................................................................................................................................................................... 27
Access and Invoke the IMS APIs ................................................................................................................................. 27
Access the MVS/QuickRef Interface ........................................................................................................................... 28
CA Common Services for z/OS Components .............................................................................................................. 28
License the Product ............................................................................................................................................. 31
KEYS MemberAdd Execution Key .................................................................................................................... 31
How Components and Options Are Enabled .............................................................................................................. 34
Chapter 3: Installing Your Products Using CA CSM 35
Chapter 4: Installing Your Product Using Pax ESD or DVD 37

How to Install Your Product Using a Pax File.............................................................................................................. 37
USS Environment Setup ...................................................................................................................................... 38
Allocate and Mount a File System .............................................................................................................................. 39
Acquire the Product Pax Files ..................................................................................................................................... 41
Contents 9
Download Files to a PC Using Pax ESD ................................................................................................................ 42
Download Using Batch JCL .................................................................................................................................. 43
Download Files to Mainframe through a PC ....................................................................................................... 46
Create a Product Directory from the Pax File ............................................................................................................ 47
Example: JCL File, Unpackage.txt, to Customize ................................................................................................. 48
Copy Installation Files to z/OS Data Sets .................................................................................................................... 48
Unload the Installation Library ................................................................................................................................... 50
Modify and Run the Job INSTALL ............................................................................................................................... 51
GSVIINST MacroSet INSTALL Parameters ........................................................................................................ 53
Output from ESD or DVD Install .......................................................................................................................... 65
Delete, Allocate, and Initialize Libraries (INST0001) .................................................................................................. 65
Allocate and Mount the z/FS Release Dependent Data Set (INST0002) .................................................................... 66
Receive, Apply, and Accept SMP/E Functions (INST0003) ......................................................................................... 67
Create Run-Time Libraries (INST0004) ....................................................................................................................... 67
Create Run-Time SITE Libraries (INST0005)................................................................................................................ 68
Clean Up the USS Directory ........................................................................................................................................ 68
Apply Preventive Maintenance .................................................................................................................................. 69
HOLDDATA .......................................................................................................................................................... 71
Chapter 5: Starting Your Product 75

How to Prepare for Deployment ................................................................................................................................ 75
Apply IBM APARs................................................................................................................................................. 75
Run Any Other Jobs ............................................................................................................................................. 75
How to Complete Deployment With CA CSM ............................................................................................................ 75
Startup JCL Procedures Customized by CA CSM ................................................................................................. 76
How to Deploy Without CA CSM ................................................................................................................................ 76
How to Complete Configuration With CA CSM .......................................................................................................... 77
How to Configure Without CA CSM ........................................................................................................................... 78
Sample JCL for Product Configuration ................................................................................................................ 79
Modify and Run the Job INSTALL ........................................................................................................................ 80
Create Run-Time Libraries (INST0004) ................................................................................................................ 95
Create Run-Time SITE Libraries (INST0005) ........................................................................................................ 95
Run the System Information Utility GSVCUTIL (INST0010) ................................................................................. 96
Copy System Configuration Options to System PARMLIB (INST0011) ................................................................ 97
Assemble the MVS Control Block Maps (INST0013) ......................................................................................... 110
Update the JES Configuration Names Table ...................................................................................................... 111
Assemble and Link the JES Configuration Modules (INST0020) ........................................................................ 115
Assemble the JES Control Block Maps (INST0021) ............................................................................................ 116
Initialize the Event Capture Index Data Set (INST0030) .................................................................................... 117
Define and Load the IMOD Data Set (INST0031 - INST0032) ............................................................................ 118
Define Log Streams (INST0040 - INST0046) ...................................................................................................... 118
10 Installation Guide
Convert the Security Data Set (INST0050) ........................................................................................................ 139
Convert the Profile Data Set (INST0051) ........................................................................................................... 141
Update the CICS Tables (INST0060) .................................................................................................................. 143
Link Edit the CICS Object Members (INST0061) ................................................................................................ 149
Update the CICS JCL .......................................................................................................................................... 150
Copy the Installation Members to a Sample Library (INST0110) ...................................................................... 150
Assemble and Link the Default SSID (USRM0001) ................................................................................................... 151
Prepare to Start Your Product .................................................................................................................................. 151
Increase ASIDs (Optional) .................................................................................................................................. 151
APF-Authorize the Load Library ........................................................................................................................ 153
Set Up the LOGR Exit and Linklist ...................................................................................................................... 153
Add Startup Procedure to System Procedure Library ....................................................................................... 153
Start Your Product .................................................................................................................................................... 154
Post-Installation Considerations .............................................................................................................................. 155
Chapter 6: Migration Information 157

Update the INSTALL Job ........................................................................................................................................... 157
Dynamic Installation of CA SYSVIEW ........................................................................................................................ 158
User Supervisor Call (SVC) Removal ......................................................................................................................... 159
LPA Load Library Data Set Removal.......................................................................................................................... 159
Anchor Address Space Removal ............................................................................................................................... 160
Library Concatenation .............................................................................................................................................. 161
Data Sets Eligible for Library Concatenation ..................................................................................................... 162
JES Definitions .......................................................................................................................................................... 163
Configuration Options Member - OPTIONS ............................................................................................................. 163
External Security ...................................................................................................................................................... 164
Event Scheduler........................................................................................................................................................ 164
Configuration Options - Parmlib Member CICSOPTS ............................................................................................... 165
Logical Group Definitions Removed - Parmlib Member CICSGRPS .......................................................................... 165
Logical Groups Overview ................................................................................................................................... 165
How to Use Logical Groups ............................................................................................................................... 166
Migrating Logical Group Definitions ................................................................................................................. 168
Conversion Utility - GSVYLGCV .......................................................................................................................... 172
IMS Dependent Regions - Data Collection ............................................................................................................... 176
Appendix A: CCS for z/OS Component Requirements 177

FMIDs ....................................................................................................................................................................... 177
CA LMP (License Management Program).......................................................................................................... 177
CA MASTER........................................................................................................................................................ 178
Interface to IBM Health Checker ....................................................................................................................... 178
CA zIIP Enablement Services ............................................................................................................................. 178
Contents 11
Appendix B: Interface Options 181
TSO and CA Roscoe/ETSO Interface Support ........................................................................................................... 181
Access CA SYSVIEW from CA Roscoe/ETSO ....................................................................................................... 181
ISPF Interface Support .............................................................................................................................................. 182
Install ISPF Support Permanently ...................................................................................................................... 182
Install ISPF Support Dynamically ....................................................................................................................... 183
VTAM Interface Support .......................................................................................................................................... 183
Install VTAM Support ........................................................................................................................................ 183
CICS Interface Support ............................................................................................................................................. 184
CICS User ID Exit Routine .................................................................................................................................. 185
Modify the Exit to Use Your Security System .................................................................................................... 185
CICS Transaction Termination Exit Routine ....................................................................................................... 185
Modify the Transaction Termination Exit ......................................................................................................... 186
Console Interface Support........................................................................................................................................ 186
How CA GSS Communicates with CA SYSVIEW ................................................................................................. 186
Enabling the Console Interface ......................................................................................................................... 187
Customize the Console Interface ...................................................................................................................... 187
Local 3270 Device Interface Support ....................................................................................................................... 188
Batch Interface Support ........................................................................................................................................... 188
Index 189
Chapter 1: Overview
This guide describes how to install and implement CA SYSVIEW.
This section contains the following topics:

CA SYSVIEW Overview (see page 13)
CA SYSVIEW Server Overview (see page 14)
Audience (see page 14)
How the Installation Process Works (see page 15)
Integration with Other CA Products (see page 16)
CA SYSVIEW Overview
CA SYSVIEW is a performance monitoring and management tool for your z/OS system
environment. Operators, systems programmers, performance analysts, and end users
can use it to monitor and manage the following resources:
z/OS
JES2
JES3
DB2
CICS
IMS
CA Datacom/DB
TCP/IP
WebSphere MQ
Note: For more information about product components and options, see the CA
SYSVIEW online help. For other questions, visit http://ca.com/support, and search for
SYSVIEW, or navigate to Solutions, Product Solutions, Enterprise Systems Management,
Server Management, Systems Management for z/OS.
CA SYSVIEW Server Overview
CA SYSVIEW Server Overview

CA SYSVIEW Server is designed to provide data to other CA software products. All
customers are eligible to run the CA SYSVIEW Server.
The SYSVIEW 3270 interfaces are available for use by the CA SYSVIEW Server only
customer. Functionality is limited.
The CA SYSVIEW Server functionality is automatically available when you are running CA
SYSVIEW with any of the licensed options. Multiple copies of CA SYSVIEW are not
required.
Licensed Options:
CA SYSVIEW CA Datacom Option
CA SYSVIEW Option for CICS
CA SYSVIEW Option for IMS
CA SYSVIEW Option for TCP/IP
CA SYSVIEW for CA APM
Event Capture
WebSphere MQ
z/OS
Audience
Readers of this book need knowledge in the following areas:
JCL
TSO/ISPF
z/OS environment and installing software in this environment
Your IT environment, enterprise structure, and region structure
Consult with the following personnel, as required:

Systems programmer for z/OS and VTAM definitions
Storage administrator, for DASD allocations
How the Installation Process Works
How the Installation Process Works

CA Technologies has standardized product installations across all mainframe products.
Installation uses the following process:
AcquisitionTransports the software to your z/OS system.
Installation using SMP/ECreates an SMP/E environment and runs the RECEIVE,
APPLY, and ACCEPT steps. The software is untailored.
(For CA CSM Release 5.1 and earlier only) DeploymentCopies the target libraries
to another system or LPAR.
Note: This step is optional for CA CSM Version 6.0. For more information, see the
scenario Configuring Products Using CA CSM that is available in the CA CSM Version
6.0 bookshelf at http://ca.com/support.
ConfigurationCreates customized load modules, bringing the software to an
executable state.
(For staging system configurations in CA CSM Version 6.0 only)
DeploymentMakes configured run-time libraries available to a remote location
where that software can be activated, bringing it to an executable state.
CA Chorus Software Manager (CA CSM) - formerly known as CA Mainframe Software

Manager (CA MSM) - is an intuitive web-based tool that can automate and simplify
many CA Technologies product installation activities on z/OS systems. This application
also makes obtaining and applying corrective and recommended maintenance easier. A
web-based interface enables you to install and maintain your products faster and with
less chance of error. As a best practice, we recommend that you install mainframe
products and maintenance using CA CSM. Using CA CSM, someone with limited
knowledge of JCL and SMP/E can install a product.
Note: If you do not have CA CSM, you can download it from the Download Center at
http://ca.com/support. Follow the installation instructions in the CA Chorus Software
Manager documentation bookshelf on the CA Chorus Software Manager product page.
You can also complete the standardized installation process manually using pax files
that are downloaded from http://ca.com/support or a product DVD.
Integration with Other CA Products
To install your product, do the following tasks:

1. Prepare for the installation by confirming that your site meets all installation
requirements (see page 19).
2. Verify that you acquired the product using one of the following methods:
Download the software from http://ca.com/support using CA CSM.
Download the software from http://ca.com/support using Pax-Enhanced
Electronic Software Delivery (Pax ESD).
Order a product DVD. To do so, contact your account manager or a CA
Technologies Support representative.
3. Perform an SMP/E installation using one of the following methods:
If you used CA CSM to acquire the product, start the installation process from
the SMP/E Environments tab in CA CSM.
If you used Pax ESD to acquire the product, you can install the product in the
following ways:
Install the product manually.
Complete the SMP/E installation using the Add Product option in CA CSM.
If you used a DVD, install the product manually.
Note: If a CA Recommended Service (CA RS) package is published for your product,
install it before proceeding.
4. (For CA CSM Release 5.1 and earlier only) Deploy the target libraries.
Note: This step is optional for CA CSM Version 6.0. For more information, see the
scenario Configuring Products Using CA CSM that is available in the CA CSM Version
6.0 bookshelf at http://ca.com/support.
5. Configure your product using CA CSM or manually.
6. (For staging system configurations in CA CSM Version 6.0 only) Deploy configured
run-time libraries, and activate your product.
Note: Configuration is considered part of starting your product.

The following CA products integrate with CA SYSVIEW:
CA NSM
Through an interface with CA NSM, you can use the CA SYSVIEW data collection
function. This interface uses TCP/IP communication technology.
CA Service Desk
When CA Service Desk is installed, you can allow CA SYSVIEW to open CA Service
Desk requests for unexpected product ABENDs. This capability provides your
organization with an immediately recorded notification of the identified problem.
You can then address the situation before it causes more serious problems with CA
SYSVIEW that could affect the ability to monitor the system performance.
Note: For more information, see the CA Service Desk documentation.
CA OPS/MVS
When CA OPS/MVS is installed, CA SYSVIEW can send event notifications to CA
OPS/MVS.
CA SymDump System
CA SymDump System uses the CA SYSVIEW technology to generate diagnostic
reports during a dump capture. Output from any CA SYSVIEW command can be
captured and written to the dump data set for later viewing. Using report control
statements in the CA SymDump System library, you can control exactly which
reports are produced for each type of dump. CA SymDump System communicates
with CA SYSVIEW using the GSS component of CA Common Services for z/OS. Install
GSS before capturing or viewing dumps.
CA APM
CA SYSVIEW integration with CA APM provides the following features:
CICS Transaction Tracing
CA SYSVIEW extends CA APM Transaction Tracing into CICS. This increases
end-to-end visibility for quickly isolating transaction performance problems.
IMS Transaction Tracing
CA SYSVIEW extends CA APM Transaction Tracing into CA SYSVIEW PM Option
for IMS. This increases end-to-end visibility for quickly isolating transaction
performance problems.
Introscope Dashboards
The Dashboard integration between CA SYSVIEW and CA APM brings
mainframe statistics and metrics into the CA APM bus. Dashboards enable a
side-by-side view of data from the mainframe and other managed platforms.
Chapter 2: Preparing for Installation
This section describes what you need to know and do before you install the product.

Installation Preparation (see page 19)
Software Requirements (see page 20)
CA Common Services Requirements (see page 22)
CA Insight for DB2 (see page 22)
GMI Software Requirements (see page 23)
IBM REXX Library Requirements (see page 23)
Security Requirements (see page 23)
Storage Requirements (see page 24)
Concurrent Releases (see page 24)
Memory Requirements (see page 24)
Available Options (see page 25)
Available Components (see page 26)
IBM RMF (see page 27)
Access and Invoke the IMS APIs (see page 27)
Access the MVS/QuickRef Interface (see page 28)
CA Common Services for z/OS Components (see page 28)
How Components and Options Are Enabled (see page 34)
Installation Preparation
Before you begin the installation steps, review the following items:
To understand the new features and the enhancements that have been made after
the previous release, read the Release Notes.
As a precaution, use a test environment to install and perform the initial
evaluations of the product and its components. This testing lets you detect any
possible conflicts with other vendor products.
Decide which options and components you want to install and enable.
Be sure that all prerequisites and system requirements are met.
The IBM Resource Management Facility (RMF) must be installed for the CA SYSVIEW
RMF component to work properly. The RMF component displays data from RMF.

Software Requirements
IBM REXX Library:

The SYSLOG, OUTPUT, IPCONFIG, IPSTATS, and IPDEVICE commands, and the
DASHBOARD objects, use compiled REXX programs, which require one of the
following libraries:
Library for REXX on zSeries
Alternate Library for REXX
The Alternate Library for REXX is free and lets you run REXX compiled code without
having to purchase the Library for REXX on zSeries. The Alternate Library for REXX is
included with z/OS V1R9, or you can access it from the following link:
http://www-01.ibm.com/support/Alternate REXX Library
To use CA Common Services for z/OS components and features, be sure that the
requirements that apply to the following components are met:
CAIRIM
CA LMP of CAIRIM
CAICCI
CA GSS
CA Health Checker Common Service
CA zIIP Enablement Services of CAIRIM
CA Master
During or after each IPL, be sure that the SYSVIEW main address started task
procedure is started before CA GSS.
SMP/E is the tool for installing, maintaining, and servicing CA SYSVIEW. SMP/E
selects the proper levels of installed elements, calls system utility programs to
install changes, and keeps records of these changes.
Before CA SYSVIEW can start, use the CA LMP facility of CAIRIM to code the CA LMP
statements for your product license authorization.
The following software is required for CA SYSVIEW:
Option/Component Product Supported Releases Dropped

Base z/OS 1.12, 1.13, 2.1 None
JES2 1.12, 1.13, 2.1 None
JES3 1.12, 1.13, 2.1 None
Option/Component Product Supported Releases Dropped

CICS (CA SYSVIEW Option for CICS Transaction Server 3.1, 3.2, 4.1, 4.2, 5.1, 5.2 None
CICS)
DATACOM (CA SYSVIEW CA CA Datacom 12.0, 14.0, 15.0 None
Datacom Option)
CA Datacom CICS Services 11.0, 14.0 None
DB2 (CA SYSVIEW component Database 2 9.1, 10.1, 11.1 None
for CA Insight for DB2)
Requires the following 15.0, 16.0, 17.0 14.0, 14.5

products:
CA Insight for DB2
CA DB2 Tools Xmanager
CA DB2 Tools Xnet
IDMS (CA SYSVIEW for IDMS IDMS 17.0.0, 17.0.1, 18.0.0, None
component) 18.5.0
Requires the following:
CA IDMS Performance 18.5.0
Monitor
IMS (CA SYSVIEW Option for IMS 11.1, 12.1, 13.1 None
IMS)
MQ (Option for WebSphere Websphere MQ for z/OS 7.0.1, 7.1, 8.0.0 None
MQ)

CA Common Services Requirements
CA Common Services Requirements

The following CA Common Services are used with CA SYSVIEW:
CAICCI
CAIRIM
CA LMP of CAIRIM
CAISSF of CAIRIM
CA GSS
CA zIIP Enablement Services of CAIRIM
CA Master
Note: If other CA products are installed at your site, some of these services may already
be installed.
CA Insight for DB2

To use the component CA SYSVIEW for CA Insight for DB2, do the following checks:
The following products are installed on your system:
CA Insight for DB2 Version 14.0.0 or above
CA DB2 Tools Xmanager Version 14.0.0 or above
CA DB2 Tools Xnet Version 14.0.0 or above
The XNET agent is configured to start.
The XNET agent is configured to use PassTickets
PassTickets are configured with the external security package.
For more information, see Interfacing with External Security in the Security Guide.
GMI Software Requirements
GMI Software Requirements

To use the CA SYSVIEW CA Vantage GMI component, be sure that the following products
are installed on your system:
CA Vantage Client Release 12.5.0 and above
CA Vantage Release 12.6.0 and above
CA SYSVIEW User Address Space:
XSystem eXternal Session Server
This session server provides CA Vantage GMI access to CA SYSVIEW using the
external server for establishing the user sessions.
CAICCI
This service provides the communications protocol.
Note: For more information, see the Administration Guide.
IBM REXX Library is required for the SYSLOG and OUTPUT objects.
IBM REXX Library Requirements

The REXX library is required for:
The IPCONFIG, IPSTATS, and IPDEVICE commands
The DASHBOARD command
The SYSLOG and OUTPUT objects under GMI
Note: The Alternate Library for REXX is free and lets you run REXX compiled code
without having to purchase the Library for REXX on zSeries. The Alternate Library for
REXX is included with z/OS V1R9, or you can access it from the following link:
http://www-01.ibm.com/support/Alternate REXX Library
Security Requirements
CA SYSVIEW internal security provides and controls the user access to CA SYSVIEW and
CA SYSVIEW commands and command groups.
Note: For detailed security requirements, see the Security Guide.

Storage Requirements
Storage Requirements
Verify that you have the following storage available:
For an ESD installation, 30 cylinders for the download of the CA SYSVIEW product
package.
For the installation and setup:
Installation = 372 cylinders
SMP/E temporary libraries = 372 cylinders
Concurrent Releases
You can install the current release of CA SYSVIEW and can continue to use an older
release for your production environment. If you plan to continue to run a previous
release, consider the following points:
When installing into an existing SMP/E environment, this installation deletes
previous releases.
When you acquire your product with ESD:
Select a different target zone from your currently installed release.
Select a different distribution zone from your currently installed release.
The new zones use different libraries than your current release.
Note: CA CSM installs the product into a new CSI by default.
Define the DDDEF entries in your new zones to point SMP/E to the proper
installation libraries. Be sure that they point to the new release libraries.
Memory Requirements
Ensure that you have the following memory available:
1208 KB of private area storage with all options active.
Most of this storage is allocated above the 16-MB line. Maximum storage
requirements depend upon which of the product commands is entered. You can
reduce private area storage requirements by placing reentrant CA SYSVIEW
modules in the pageable link pack area.
1 KB of common storage area (CSA)
500 KB of extended CSA with all options active on a permanent basis for all users.
More extended CSA is required for short periods (less than one second) to transfer
data from other address spaces to the CA SYSVIEW address space.
Available Options
Available Options
The CA SYSVIEW options that you want to install are listed in the following table. After
an option is installed, you can decide whether to enable it. The table includes the LMP
codes and OPTIONS values you specify during the installation to enable an option. The
table also includes installation and customization requirements for each option.
Options OPTIONS Value LMP Code Installation and Customization Requirements

Base (z/OS) MVS FU Complete the installation process. No additional
installation or customization is required.
CA SYSVIEW Option for CICS CICS FV Complete the installation process. Complete the
installation steps for CA SYSVIEW Option for CICS.
CA SYSVIEW CA Datacom DATACOM FW Complete the installation process. No additional
Option installation or customization is required.
Note: For information about defining the CA
SYSVIEW CA Datacom Option address spaces, see
the Administration Guide.
TCP/IP TCPIP JD Complete the installation process. No additional
CA SYSVIEW Option for IMS IMS PH Complete the installation process. No additional
CA SYSVIEW Option for MQSERIES JE Complete the installation process. No additional
WebSphere MQ installation or customization is required.
CA SYSVIEW Event Capture CAPTURE 2G Complete the installation process. No additional
Option installation or customization is required.
CA Cross Enterprise APM CEAPM 11 Complete the installation process. Additional

steps are required.
More information:

Available Components
Available Components
The CA SYSVIEW components that you want to install are listed in the following table.
After a component is installed, enable it as a COMPONENT value. The table includes the
LMP codes and COMPONENT values you specify during the installation to enable a
component. The table also includes installation and customization requirements for
each component.
Note: To customize components, follow the procedures in the Administration Guide.
Component COMPONENT LMP Code Installation and Customization Requirements

Value
CA MIM MIM FU Complete the installation process. No additional
CA Roscoe ROSCOE FU Complete the installation process.
Note: For information about installing the CA Roscoe
monitor, see the Administration Guide.
CA SYSVIEW for CA DB2 IE Complete the installation process. Additional external
Insight for DB2 security setup is required for PassTickets.
Note: For information about configuring the component
CA SYSVIEW for CA Insight for DB2, see the Administration
Guide.
Note: For information about the required PassTicket
setup, see the Security Guide.
Cross-System XSYSTEM FU Review the XSYSTEM and SYSNAMES parmlib members
and complete the installation process. No additional
Note: For the list of parmlib members and components
for which they are valid, see the Administration Guide.
USS USS FU Complete the installation process. No additional
IBM Health HCHECK FU No additional installation or customization is required.
Checker
More information:
IBM RMF
IBM RMF
CA SYSVIEW uses the data IBM Resource Measurement Facility (RMF) provides for the
CA SYSVIEW RMF displays. RMF and RMF Monitor III must be active to gather the data
for the CA SYSVIEW displays.
Access and Invoke the IMS APIs

Some IMS commands gather statistic by invoking IMS APIs that are distributed with the
IBM IMS libraries.
The following procedure guides you through accessing and invoking the IMS APIs.
Follow these steps:

1. Add the IMS RESLIB to the SYSVIEW STEPLIB.
The API modules reside in the IMS RESLIB.
2. If you invoke CA SYSVIEW from TSO, add the RESLIB to the USER address space and
the user TSO logon procedure STEPLIB.
3. Invoke the IMS APIs using the following commands:
IMSSPOC
Invokes the Common Service Layer API.
IMSSLOGS
Invokes the IMS DBRC API.
IMSQSTAT
Invokes the Common Queue Server API.
IMSQSUM
IMSQTRAN
The IMS APIs are invoked and you can use the IMS commands to gather statistics.
Note: For more information in the IBM IMS APIs, see The IMS System Programming API
Reference.

Access the MVS/QuickRef Interface
Access the MVS/QuickRef Interface

The Chicago-Soft MVS/QuickRef product interface provides access to CA SYSVIEW
product messages.
Follow these steps:

1. Issue the QUICKREF command.
A direct program call is made that queries the MVS/QuickRef database. The
QUICKREF command requires that the MVS/QuickRef load modules be available,
using the standard search order for loading modules. If the MVS/QuickRef load
library is not part of the LNKLST concatenation, proceed to step 2.
2. Add the MVS/QuickRef load library in the STEPLIB or TASKLIB.
MVS/QuickRef access must be made available to both the CA SYSVIEW User
Interface address space (SYSVUSER) and the TSO user address space.
CA Common Services for z/OS Components

The required CA Common Services for z/OS components for licensing this product are
described in the following list.
Note: For more information about CA Common Services for z/OS components, see the
CA Common Services for z/OS documentation on the Technical Support website (see
page 4).
CAIRIM
Prepares your operating system environment for all CA applications and starts
them. The common driver for a collection of dynamic initialization routines
eliminates the need for user SVCs, SMF exits, subsystems, and other installation
requirements commonly encountered when installing systems applications.
Integral parts of CAIRIM are CAISSF, CA LMP, and CA zIIP Enablement Services.
CAISSF
Provides an external security mechanism for controlling and monitoring access
to all system and application resource processes. CAISSF is integrated into
many CA enterprise applications and is also used by other CCS for z/OS
services. CAISSF provides security services for user logon, resource access
control, process use control, and recording and monitoring of violation activity.
CA LMP
Provides a standardized and automated approach to the tracking of licensed
software and is provided as an integral part of CAIRIM. After CAIRIM is
installed, you have access to Technical Support for all CA LMP-supported
products.
CA zIIP Enablement Services
Provides a common service for CA products to allow their code to run on zIIP
processors, if available.
CAICCI
Provides CA enterprise applications with a common communications software layer
that insulates the applications from dealing with protocol specifics, error recovery,
and system connection establishment.
CA GSS
CA GSS is part of CA Common Services for z/OS and is installed with it.
To make full use of some of your product features, you must have CA GSS installed
at your site. CA GSS is required for the following features:
System Condition Monitor (SCM)
Console Interface
Information modules (IMOD) to provide automation for system monitoring
when thresholds are exceeded
Note: For information about customizing CA GSS, see the Administration Guide.


Provides a simple and consistent method for CA products to create health checks to
run under the IBM Health Checker for z/OS. The IBM Health Checker for z/OS helps
you identify potential problems in your z/OS environment by checking system or
product parameters and system status against recommended settings. CA has
joined other vendors in creating checks for CA z/OS products. CA SYSVIEW health
checks are automatically activated on the target system when the product is started
on a system where the following components are installed and configured:
IBM Health Checker for z/OS
For more information about installing the CA Health Checker Common Service, see
the CA Common Service Installation Guide.
For more information about the IBM Health Checker for z/OS, see the IBM Health
Checker for z/OS User Guide.
CA Master
The CAMASTER address space is an early IPL, limited function, permanent system
address space. CAMASTER provides a set of operating system level services that any
CA Technologies product can use.
CAMASTER provides the capability for privileged CA Technologies components to:
1. Register the non-space switch PC function routines that can be used instead of
SVC routines, or to provide persistent access to component-specific function
routines through the hardware assisted program-call mechanism.
2. Use persistent private storage that the CAMASTER address space provides to
eliminate the need for using z/OS common storage resources such as ESQA or
ECSA. This private storage is provided through CAMASTER space switch PC
storage management services or explicit STORAGE OBTAIN using the
CAMASTER ALET in AR ASC mode.
3. Provide a CA Technologies owned permanent system address space from which
to anchor CA Technologies product objects, such as public access data spaces.
In short, CAMASTER can help CA Technologies products reduce their ECSA usage,
avoid using user SVCs, and avoid using the IBM *MASTER* address space.
License the Product

You code CA Common Services CA License Management Program (LMP) statements to
license this product on each system that uses this product.
Follow these steps:

1. Ensure that CA Common Services CA Resource Initialization Manager (CAIRIM) is
installed on the system.
2. Add product license LMP codes from the product's Key Certificate as CA LMP
statements in the CAIRIM KEYS member.
Note: For more information, see the CA Common Services for z/OS Administration
Guide.
3. Start the CAS9 procedure at the next IPL. Alternatively, if you do not want to wait
for the next IPL, do the following:
a. Create a special CAS9 procedure under a different name with the following
settings:
PARMLIB and AUTOCMDS DD statements set to DUMMY
KEYS DD statement set to the KEYS member with the newly added LMP key
statements
b. Start the special procedure.
The product is licensed on the system.
KEYS MemberAdd Execution Key

Add the CA LMP execution key, provided on your product key certificate, to the CAIRIM
parameters. This execution key ensures the proper initialization.
To define a CA LMP execution key to the CAIRIM parameters, modify the KEYS member.
This sample parameter structure for the KEYS member has the following format:
PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss)

LMPCODE(kkkkkkkkkkkkkkkk)
The parameter definitions are as follows:

PROD(pp)
Specifies the two-character product code. This code agrees with the product code
already in use by the CAIRIM initialization parameters for any earlier releases (if
applicable).

Values for pp are as follows:

FU
Indicates CA SYSVIEW
FV
Indicates CA SYSVIEW Option for CICS
FW
Indicates CA SYSVIEW CA Datacom Option
2G
Indicates CA SYSVIEW Event Capture Option
IE
Indicates CA Insight for DB2
JE
Indicates CA SYSVIEW Option for WebSphere MQ
PH
Indicates CA SYSVIEW Option for IMS
JD
Indicates CA SYSVIEW Option for TCP/IP
11
Indicates CA SYSVIEW for CA APM
DATE(ddmmmyy)
Specifies the CA LMP licensing agreement expiration date, for example, 13MAR12.
CPU(tttt-mmmm/ssssss)
tttt
Specifies the CPU type on which CA LMP is to run, for example, 3090.
-mmmm
Specifies the CPU model on which CA LMP is to run, for example, 600.
Note: If the CPU type and or model require fewer than four characters, blank
spaces are inserted for the unused characters.
/ssssss
Specifies the serial number of the CPU on which CA LMP is to run.
LMPCODE(kkkkkkkkkkkkkkkk)
Specifies the execution key (kkkkkkkkkkkkkkkk) needed to run CA LMP. The key
certificate shipped with each CA LMP software solution provides this CA LMP
execution key.
Example: Add CA LMP Execution Key
The following example shows a control statement for the CA LMP execution software
parameter:
PROD(FU) DATE(27JUN12) CPU(2097-E26 /370623)

LMPCODE(52H2K06130Z7RZD6)
In this example, with your product running on the specified CPU, the CA LMP licensing
agreement will expire on June 27, 2012. The product code and execution key values are
different when you install your product at your site.
Note: See the CA Common Services for z/OS Administration Guide for:
The procedure for defining the CA LMP execution key to the CAIRIM parameters
Details about the features and associated utilities of CAIRIM
CA LMP Key Certificate
Examine the CA License Managed Program (CA LMP) key certificate. Your certificate
contains the following information:
Product Name
Defines the trademarked or registered name of your product as licensed for the
designated site and CPUs.
Product Code
Defines a two-character code that corresponds to the product.
Supplement
Defines the reference number of your license for a particular facility and has the
following format:
nnnnnn-nnn
This format differs slightly inside and outside North America and, in some cases, the
reference number may not be provided at all.

How Components and Options Are Enabled
CPU ID
Defines the code that identifies the specific CPU for which installation of this
product is valid.
Execution Key
Defines an encrypted code required by CA LMP for installing your product. During
installation, it is referred to as the LMP code.
Expiration Date
Defines the date your license expires and has the following format:
ddmmmyy
Example: 21Mar12
Technical Contact
Defines the name of the designated technical contact at your site who is
responsible for the installation and maintenance of your product. CA addresses all
CA LMP correspondence to this person.
MIS Director
Defines the name of the Director of MIS or the person who performs such a
function at your site. If the title but not the name of the individual is indicated on
the certificate, supply the actual name when correcting and verifying the certificate.
CPU Location
Defines the address of the building in which the CPU is installed.
How Components and Options Are Enabled

Enabling components and options means that you can use their respective commands
and, by default, gain access to them from the CA SYSVIEW main menu.
During installation, you specify a COMPONENTS and OPTIONS value for each component
and option. (COMPONENTS and OPTIONS are modifiable GSVIINST parameters.) After
the installation completes, the COMPONENTS and OPTIONS values let you enable those
components and options that you plan to use.
More information:
Available Components (see page 26)

Available Options (see page 25)
Chapter 3: Installing Your Products Using
CA CSM
As a system programmer, your responsibilities include acquiring, installing, maintaining,
deploying, and configuring CA Technologies mainframe products on your system.
CA CSM is an application that simplifies and unifies the management of your CA

Technologies mainframe products on z/OS systems. As products adopt the CA CSM
services, you can install your products in a common way according to industry best
practices.
If you do not have CA CSM installed, download it from the Download Center at
http://ca.com/support. This web page also contains links to the complete
documentation for CA CSM.
You can use the following scenarios to guide you through the product installation
process (see page 15) using CA CSM:
Acquiring Products Using CA CSM
Installing Products Using CA CSM
Maintaining Products Using CA CSM
Configuring Product Using CA CSM
These scenarios are available in the CA CSM Version 6.0 bookshelf at

http://ca.com/support. For additional information about how to use CA CSM, use the
online help.
Chapter 3: Installing Your Products Using CA CSM 35

Chapter 4: Installing Your Product Using
Pax ESD or DVD
How to Install Your Product Using a Pax File (see page 37)
Allocate and Mount a File System (see page 39)
Acquire the Product Pax Files (see page 41)
Create a Product Directory from the Pax File (see page 47)
Copy Installation Files to z/OS Data Sets (see page 48)
Unload the Installation Library (see page 50)
Modify and Run the Job INSTALL (see page 51)
Delete, Allocate, and Initialize Libraries (INST0001) (see page 65)
Allocate and Mount the z/FS Release Dependent Data Set (INST0002) (see page 66)
Receive, Apply, and Accept SMP/E Functions (INST0003) (see page 67)
Create Run-Time Libraries (INST0004) (see page 67)
Create Run-Time SITE Libraries (INST0005) (see page 68)
Clean Up the USS Directory (see page 68)
Apply Preventive Maintenance (see page 69)
How to Install Your Product Using a Pax File

As a system programmer, your responsibilities include installing products on your
mainframe system. With this option, you acquire a product pax file from
http://ca.com/support or from a product DVD.
The DVD contains a folder that includes the pax file for the product. Product updates
may have occurred after you acquired the product DVD. The files on the online site
always have the most current product updates. To determine if you have the latest
updates, go to http://ca.com/support and click Download Center.

How to Install Your Product Using a Pax File
You perform the following tasks to install a product with a pax file:
1. Allocate and mount the file system (see page 39).

2. Acquire the product pax files (see page 41).
3. Create a product directory from the pax file (see page 47).
4. Copy the installation files to z/OS data sets (see page 48).
5. Prepare the SMP/E environment for a pax installation.
6. Run the installation jobs for a pax installation.
7. (Optional) Clean up the USS directory (see page 68).
8. Apply preventive maintenance.
USS Environment Setup

You need a UNIX System Services (USS) directory and a file system with adequate space
to perform the following tasks:
Receive product pax files from http://ca.com/support.
Perform utility functions to unpack the pax file into MVS data sets that you can use
to complete the product installation.
We recommend that you allocate and mount a file system that is dedicated to Pax ESD.
The amount of space that you need for the file system depends on the following
variables:
The size of the pax files that you intend to download.
Whether you plan to keep the pax files after unpacking them. We do not
recommend this practice.
Allocate and Mount a File System
We recommend that you use one directory for downloading and unpacking pax files.
Reusing the same directory minimizes USS setup. You need to complete the USS setup
only one time. You reuse the same directory for subsequent downloads. Alternatively,
you can create a directory for each pax download.
Important! Downloading pax files for the SMP/E installation as part of the Pax ESD
process requires write authority to the UNIX System Services (USS) directories that are
used for the Pax ESD process. In the file system that contains the Pax ESD directories,
you also need free space approximately 3.5 times the pax file size to download the pax
file and unpack its contents. For example, to download and unpack a 14 MB pax file, you
need approximately 49 MB of free space in the file system hosting your Pax ESD
directory.

The product installation process requires a USS directory to receive the pax file and to
perform the unpack steps. We recommend that you allocate and mount a file system
that is dedicated to the product acquisition and create the directory in this file system.
You can use the zSeries File System (zFS) or hierarchical file system (HFS) for product
downloads.
This procedure describes how to perform the following tasks:

Allocate a zFS or an HFS.
Create a mount point in an existing maintenance USS directory of your choice.
Mount the file system on the newly created mount point.
Note: You must have either SUPERUSER authority, or the required SAF profile
setting to allow you to issue the USS mount command for the file system.
Optionally, permit write access to anyone in the same group as the person who
created the directory.
Important! USS commands are case-sensitive.

Follow these steps:

1. Allocate the file system by customizing one of the following samples to your site
requirements:
On a zFS, use the following sample:
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//AMSDUMP DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER ( +
NAME(your_zFS_data_set_name) +
STORAGECLASS(class) +
LINEAR +
CYL(primary secondary) +
SHAREOPTIONS(3,3) +
)
/*
//FORMAT EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate your_zFS_data_set_name -compat')
//SYSUDUMP DD SYSOUT=*
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//*
On an HFS, use the following sample:

//ALCHFS EXEC PGM=IEFBR14
//CAPAX DD DSN=yourHFS_data_set_name,
// DISP=(NEW,CATLG,DELETE),UNIT=3390,
// DSNTYPE=HFS,SPACE=(CYL,(primary,secondary,1))
The file system is allocated.

Note: Ensure that the zFS or HFS data set name that you use conforms to your data
set naming conventions for USS file systems. If the allocation of the file system data
set fails, it is because of environmental settings not allowing for the allocation. On
an HFS, try using the ISPF 3.2 Data Set Utility to allocate your HFS data set.
Acquire the Product Pax Files
2. Create a mount point for the file system. This example shows how to create a
/CA/CAPAX directory in an existing directory, /u/maint. From the TSO OMVS shell,
enter the following commands:
cd /u/maint/
mkdir CA
cd CA
mkdir CAPAX
Note: This document refers to this structure as yourUSSpaxdirectory.

The mount point is created.
3. Mount the file system by customizing one of the following samples to your site
requirements:
On a zFS, use the following sample:
MOUNT FILESYSTEM('your_zFS_data_set_name')
MOUNTPOINT('yourUSSpaxdirectory')
TYPE(ZFS) MODE(RDWR)
PARM(AGGRGROW)
On an HFS, use the following sample:

MOUNT FILESYSTEM('your_HFS_data_set_name')
MOUNTPOINT('yourUSSpaxdirectory')
TYPE(HFS) MODE(RDWR)
The file system is mounted.

4. (Optional) Set security permissions for the directory. You can use the chmod
command to let other users access the Pax ESD directory and its files. For example,
to allow write access to the Pax ESD directory for other users in your USS group,
from the TSO OMVS shell, enter the following command:
chmod -R 775 /yourUSSpaxdirectory/
Write access is granted.

Note: For more information about the chmod command, see the IBM z/OS UNIX
System Services User Guide (SA22-7802).

To begin the CA Technologies product installation procedure, copy the product pax file
into the USS directory that you set up.
Important! Downloading pax files for the SMP/E installation as part of the Pax ESD
process requires write authority to the UNIX System Services (USS) directories that are
used for the Pax ESD process. Also, you must have available USS file space before you
start the procedures in this guide.

Use one of the following methods:

Download the product pax file from http://ca.com/support to your PC (see
page 42), and then upload it to your USS file system.
If you download a zip file, you must unzip it before uploading to your USS file
system.
Download the pax files from http://ca.com/support directly to your USS file system
(see page 43).
Download the pax file from the product DVD to your PC, and then upload the pax
files to your USS file system. (see page 46)
This section includes the following information:

A sample batch job to download a product pax file from the CA Support Online FTP
server directly to a USS directory on your z/OS system
Sample commands to upload a pax file from your PC to a USS directory on your
z/OS system
Important! The FTP procedures vary due to local firewall and other security settings.
Consult your local network administrators to determine the appropriate FTP procedure
to use at your site.
Ensure that sufficient free space is available in the USS file system that you are using to
hold the product pax file. If you do not have sufficient free space, error messages similar
to the following appear:
EZA1490I Error writing to data set

EZA2606W File I/O error 133
When the download finishes, the pax file size in your USS directory matches the value in
the Size column for the corresponding pax file on the CA Technologies Products
Download window.
Download Files to a PC Using Pax ESD

You can download product installation files from http://ca.com/support to your PC.
Follow these steps:

1. Log in to http://ca.com/support, and click Download Center.
The Download Center web page appears.
2. Under Download Center, select Products from the first drop-down list, and specify
the product, release, and gen level (if applicable), and click Go.
The CA Product Download window appears.
3. Download an entire CA Technologies product software package or individual pax

files to your PC. If you download a zip file, you must unzip it before continuing.
Note: For traditional installation downloads, see the Traditional ESD User Guide. For
information about download methods, see the Download Methods and Locations
article. Go to http://ca.com/support, log in, and click Download Center. Links to the
guide and the article appear under the Download Help heading.
Download Using Batch JCL

You download a pax file from http://ca.com/support by running batch JCL on the
mainframe. Use the sample JCL attached to the PDF file as CAtoMainframe.txt (see
page 45) to perform the download.
Important! The PDF version of this guide includes sample JCL jobs that you can copy
directly to the mainframe. To access these jobs, click the paper clip icon at the left of the
PDF reader. A window displaying attachments opens. Double-click a file to view a
sample JCL. We recommend that you use the latest version of Adobe Reader for viewing
PDF files.
Note: We recommend that you follow the preferred download method as described on
http://ca.com/support. This JCL procedure is our preferred download method for users
who do not use CA CSM. We also include the procedure to download to the mainframe
through a PC in the next section.
Follow these steps:

1. Replace ACCOUNTNO with a valid JOB statement.
2. Replace yourTCPIP.PROFILE.dataset with the name of the TCP/IP profile data set for
your system. Consult your local network administrators, if necessary.
The job points to your profile.
3. Replace YourEmailAddress with your email address.
The job points to your email address.
4. Replace yourUSSpaxdirectory with the name of the USS directory that you use for
Pax ESD downloads.
The job points to your USS directory.
5. Locate the product component to download on the CA Support Product Download
window.
You have identified the product component to download.
6. Click Download for the applicable file.
Note: For multiple downloads, add files to a cart.
The Download Method window opens.

7. Click FTP Request.

The Review Download Requests window displays any files that you have requested
to download.
Note: We send you an email when the file is ready to download or a link appears in
this window when the file is available.
8. Select one of the following methods:
Preferred FTP
Uses CA Technologies worldwide content delivery network (CDN). If you cannot
download using this method, review the security restrictions for servers that
company employees can download from that are outside your corporate
network.
Host Name: ftp://ftpdownloads.ca.com
Alternate FTP
Uses the original download servers that are based on Long Island, New York.
Host Name: ftp://scftpd.ca.com for product files and download cart files and
ftp://ftp.ca.com for individual solution files.
Both methods display the host, user name, password, and FTP location, which you
then can copy into the sample JCL.
Note: The following links provide details regarding FTP: the FTP Help document link
in the Review Download Requests window and the Learn More link available in the
Download Methods window.
9. Submit the job.
Important! If your FTP commands are incorrect, it is possible for this job to fail and
still return a zero condition code. Read the messages in the job DDNAME SYSPRINT
to verify the FTP succeeded.
After you run the JCL job, the pax file resides in the mainframe USS directory that
you supplied.
Example: CAtoMainframe.txt, JCL
The following text appears in the attached CAtoMainframe.txt JCL file:
//GETPAX JOB (ACCOUNTNO),'FTP GET PAX ESD PACKAGE',

// MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID
//*********************************************************************
//* This sample job can be used to download a pax file directly from *
//* CA Support Online to a USS directory on your z/OS system. *
//* *
//* When editing the JCL ensure that you do not have sequence numbers *
//* turned on. *
//* *
//* This job must be customized as follows: *
//* 1. Supply a valid JOB statement. *
//* 2. The SYSTCPD and SYSFTPD JCL DD statements in this JCL may be *
//* optional at your site. Remove the statements that are not *
//* required. For the required statements, update the data set *
//* names with the correct site-specific data set names. *
//* 3. Replace "Host" based on the type of download method. *
//* 4. Replace "YourEmailAddress" with your email address. *
//* 5. Replace "yourUSSpaxdirectory" with the name of the USS *
//* directory used on your system for Pax ESD downloads. *
//* 6. Replace "FTP Location" with the complete path *
//* and name of the pax file obtained from the FTP location *
//* of the product download page. *
//*********************************************************************
//GETPAX EXEC PGM=FTP,PARM='(EXIT TIMEOUT 120',REGION=0M
//SYSTCPD DD DSN=yourTCPIP.PROFILE.dataset,DISP=SHR
//SYSFTPD DD DSN=yourFTP.DATA.dataset,DISP=SHR
//OUTPUT DD SYSOUT=*
//INPUT DD *
Host
anonymous YourEmailAddress
lcd yourUSSpaxdirectory
binary
get FTP_location
quit
/*

Download Files to Mainframe through a PC

You download the product installation files to your PC and transfer them to your USS
system.
Follow these steps:

1. Download the product file to your PC using one of the following methods:
Pax ESD (see page 42). If you downloaded a zip file, first unzip the file to use
the product pax files.
DVD. Copy the entire product software package (or individual pax files) to your
PC.
The pax file resides on your PC.
Note: Do not change the format of the pax.Z.
2. Open a Windows command prompt.
The command prompt appears.
3. Customize and enter the following FTP commands:
FTP mainframe
userid
password
bin
lcd C:\PC\folder\for\thePAXfile
cd /yourUSSpaxdirectory/
put paxfile.pax.Z
quit
exit
mainframe
Specifies the z/OS system IP address or DNS name.
userid
Specifies your z/OS user ID.
password
Specifies your z/OS password.
C:\PC\folder\for\thePAXfile
Specifies the location of the pax file on your PC.
Note: If you specify a location that has blanks or special characters in the path
name, enclose that value in double quotation marks.
Create a Product Directory from the Pax File
yourUSSpaxdirectory
Specifies the name of the USS directory that you use for Pax ESD downloads.
paxfile.pax.Z
Specifies the name of the pax file to upload.
The pax file is transferred to the mainframe.
Create a Product Directory from the Pax File

The pax command performs the following actions:
Extracts the files and directories that are packaged within the pax file.
Creates a USS directory in the same directory structure where the pax file resides.
Automatically generates a product and level-specific directory name.
Set the current working directory to the directory containing the pax file, and create a
directory in your USS directory by entering the following command:
pax -rvf pax-filename
Use the sample JCL that is attached to the PDF file as Unpackage.txt (see page 48) to
extract the product pax file into a product installation directory.
Important! The PDF version of this guide includes sample JCL jobs that you can copy
directly to the mainframe. To access these jobs, click the paper clip icon at the left of the
PDF reader. A window displaying attachments opens. Double-click a file to view a
sample JCL. We recommend that you use the latest version of Adobe Reader for viewing
PDF files.
Follow these steps:

1. Replace ACCOUNTNO with a valid JOB statement.
2. Replace yourUSSpaxdirectory with the name of the USS directory that you use for
product downloads.
The job points to your specific directory.
3. Replace paxfile.pax.Z with the name of the pax file.
The job points to your specific pax file.
4. Submit the job.
The job creates the product directory.
Note: If the PARM= statement exceeds 71 characters, uncomment and use the second
form of UNPAXDIR instead. This sample job uses an X in column 72 to continue the
PARM= parameters to a second line.

Copy Installation Files to z/OS Data Sets
Example: JCL File, Unpackage.txt, to Customize

The following text appears in the attached Unpackage.txt JCL file:
//ESDUNPAX JOB (ACCOUNTNO),'UNPAX PAX ESD PACKAGE',

// MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID
//*********************************************************************
//* This sample job can be used to invoke the pax command to create *
//* the product-specific installation directory. *
//* *
//* This job must be customized as follows: *
//* 1. Supply a valid JOB statement. *
//* 2. Replace "yourUSSpaxdirectory" with the name of the USS *
//* directory used on your system for Pax ESD downloads. *
//* 3. Replace "paxfile.pax.Z" with the name of the pax file. *
//* NOTE: If you continue the PARM= statement on a second line, *
//* start entering characters in column 16 and make sure *
//* the 'X' continuation character is in column 72. *
//*********************************************************************
//UNPAXDIR EXEC PGM=BPXBATCH,
// PARM='sh cd /yourUSSpaxdirectory/; pax -rvf paxfile.pax.Z'
//*UNPAXDIR EXEC PGM=BPXBATCH,
//* PARM='sh cd /yourUSSpaxdirectory/; pax X
//* -rvf paxfile.pax.Z'
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*

Use this procedure to invoke the SMP/E GIMUNZIP utility to create MVS data sets from
the files in the product-specific directory.
The file UNZIPJCL in the product directory contains a sample job to GIMUNZIP the
installation package. You edit and submit the UNZIPJCL job to create z/OS data sets.
Follow these steps:

1. Locate and read the product readme file or installation notes, if applicable, which
resides in the product-specific directory that the pax command created. This file
contains the product-specific details that you require to complete the installation
procedure.
You have identified the product-specific installation details.
2. Use ISPF EDIT or TSO ISHELL to edit the UNZIPJCL sample job. You can perform this
step in one of the following ways:
Use ISPF EDIT. Specify the full path name of the UNZIPJCL file.
Use TSO ISHELL. Navigate to the UNZIPJCL file and use the E line command to
edit the file.
The job is edited.
3. Change the SMPDIR DD PATH to the product-specific directory created by the pax
command.
Your view is of the product-specific directory.
4. If ICSF is not active, perform the following steps:
a. Change the SMPJHOME DD PATH to your Java runtime directory. This directory
varies from system to system.
b. Perform one of the following steps:
Change the SMPCPATH DD PATH to your SMP/E Java application classes
directory, typically /usr/lpp/smp/classes/.
Change HASH=YES to HASH=NO on the GIMUNZIP parameter.
One of the following occurs: ICSF is active or you are using Java.
5. Change all occurrences of yourHLQ to the high-level qualifier (HLQ) for z/OS data
sets that the installation process uses. We suggest that you use a unique HLQ for
each expanded pax file to identify uniquely the package. Do not remove CAI after
yourHLQ. Do not use the same value for yourHLQ as you use for the SMP/E
RELFILEs.
All occurrences of yourHLQ are set to your high-level qualifier for z/OS data sets.
6. Submit the UNZIPJCL job.
The UNZIPJCL job completes with a zero return code. Messages GIM69158I and
GIM48101I in the output and IKJ56228I in the JES log are acceptable.
GIMUNZIP creates z/OS data sets with the high-level qualifier that you specified in
the UNZIPJCL job. You use these data sets to perform the product installation. The
pax file and product-specific directory are no longer needed.
Note: For more information, see the IBM SMP/E for z/OS Reference (SA22-7772).

Unload the Installation Library
Unload the Installation Library

To copy the installation library from an ESD created DASD-based product distribution
file, use the following procedure.
Follow these steps:

1. Modify the sample JCL to the specification of your site.
A copy of the sample JCL can be obtained from yourHLQ.CAI.CNM4E00.F1(ESDJCL)
that the UNZIPJCL created.
2. Modify the job stream to your site by replacing the following lowercase, italicized
items in the sample JCL with the information described here.
volume
Specifies the volume serial number where the installation library is to reside.
yourHLQ
Specifies the HLQ used during the UNZIP step of the ESD process.
Modify and Run the Job INSTALL
The job stream to modify follows:

//ESDINST JOB (0000)
//*
//*==================================================================*
//* *
//* Sample job to create the sysview.SAMPJCL data set *
//* *
//*==================================================================*
//*
// SET HLQ='yourHLQ'
// SET VOLUME=volume
//*
//COPY EXEC PGM=IEBCOPY
//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))
//*
//IN DD DISP=SHR,DSN=&HLQ..CAI.CNM4D50.F1
//*
//SAMPJCL DD DSN=&HLQ..SAMPJCL,
// DISP=(NEW,CATLG,DELETE),
// UNIT=SYSDA,
// VOL=SER=&VOLUME,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(CYL,(05,02,45))
//*
//SYSIN DD DISP=SHR,DSN=&HLQ..CAI.CNM4D50.F1(SAMPJCL)
3. Submit the modified sample JCL.
The installation library (SAMPJCL) is copied from the DASD-based SMP/E RELFILE that
the UNZIP step of the ESD process created.

The job INSTALL in the installation library SAMPJCL generates the JCL stream necessary
to install CA SYSVIEW.
This step contains instructions for modifying the job INSTALL to meet the needs of your
site.
Before you begin this step, have the following information available:
The high-level qualifier (HLQ), which must be 24 characters or fewer.

Follow these steps:

1. Modify the following JOB statement in INSTALL to the requirements of your site:
//INSTALL JOB (00000000),'SYSVIEW',CLASS=A
2. Modify the following SYSLIB statement in INSTALL to replace the high-level qualifier
of sysview with the qualifier you chose when you downloaded the installation
library:
//SYSLIB DD DISP=SHR,DSN=sysview.SAMPJCL
3. Modify the GSVIINST macro parameters in INSTALL.

The INSTALL job stream contains the parameters for the macro GSVIINST. The
values that are assigned to these parameters determine how CA SYSVIEW is
installed. You can change these values in the generated job stream before the step
where they are used.
4. Submit the job INSTALL.
The job is submitted to the internal reader, and the job stream is generated.
The job name that you specified on the JOBNAME parameter is the output from the
assembly. If you did not specify a job name, the job output is INST0000.
Important! Your TSO enqueues on the sysview.SAMPJCL while members are edited.
Therefore, end the edit session to release this data set so the job executes.
More information:
GSVIINST MacroSet INSTALL Parameters (see page 81)
GSVIINST MacroSet INSTALL Parameters

Set the GSVIINST macro parameters before you submit the job INSTALL. The following
example shows the default parameter values that appear in the job INSTALL.
These parameters have the following syntax:

//*
//*----------------------------------------------------------------------------*
//* CA SYSVIEW *
//* Installation generator *
//* *
//* This job will dynamically build the other jobs that are *
//* required to complete the installation. *
//* *
//* *--------------------* Important Notice *-------------------* *
//* *
//* CA Mainframe Software Manager *
//* *
//* If you have used CA Mainframe Software Manager *
//* to perform the installation of the product, *
//* this step is required. *
//* *
//* Step: Required *
//* *
//*----------------------------------------------------------------------------*
//ASM EXEC PGM=ASMA90,REGION=1024K,PARM='NOTERM,LIST,DECK,NOOBJECT'
//*
//SYSUT1 DD UNIT=SYSDA,SPACE=(1700,(600,100))
//SYSPUNCH DD SYSOUT=(*,INTRDR),DCB=(RECFM=FB,LRECL=80,BLKSIZE=2000)
//*----------------------------------------------------------------------------*
//* The data set defined to the DDNAME SYSLIB should also *
//* be coded as the data set name on the GSVIINST option *
//* INSTLIB=. *
//* *
//* The options that require modification or inspection *
//* for specific site installation needs are marked with *
//* a "<---". *
//*----------------------------------------------------------------------------*
//*
//SYSLIB DD DISP=SHR,DSN=sysview.SAMPJCL <---INSTLIB
//*
//*
//* Note: When modifying the macro below, remember to include
//* the continuation character "X" in column 72 for all

//* lines except the last line containing the DUMMY=

//* parameter.
//*
//*.+....1....+....2....+....3....+....4....+....5....+....6....+....7.X
//SYSIN DD *
*
PRINT NOGEN
GSVIINST X
, *----------------------------------------------------* X
, * Installation data set name * X
, * This is the data set name that you are * X
, * editing now. * X
, *----------------------------------------------------* X
INSTLIB=sysview.SAMPJCL, <--- X
, *----------------------------------------------------* X
, * System parmlib data set * X
, *----------------------------------------------------* X
SYSPLIB=SYS1.PARMLIB, <--- X
, *----------------------------------------------------* X
, * Source installation Media * X
, * ESD - ESD file on DASD * X
, * DVD - Contains PAX file * X
, *----------------------------------------------------* X
SOURCE=ESD, ESD | DVD <--- X
, *----------------------------------------------------* X
, * High-level qualifier used when the ESD file * X
, * was UNZIPPED. * X
, *--------------------------------------------------- * X
ESDHLQ=yourHLQ, ESD HLQ <--- X
, *----------------------------------------------------* X
, * Data set allocation * X
, *----------------------------------------------------* X
PREFIX=sysview, <--- X
SITEDSN=YES, <--- X
DELETE=YES, X
DASDVOL=volume, <--- X
SMS=NO, X
SMSVOL=, X
STORCLAS=, X
DSKUNIT=SYSDA, X
WRKUNIT=SYSDA, X
PROFTYPE=PDS, X
, *----------------------------------------------------* X
, * Data set blocksizes * X
, *----------------------------------------------------* X
BLKSZU=6144, X
BLKSZFB=3200, X
BLKSZVB=25600, X
, *----------------------------------------------------* X
, * z/FS data set allocation * X

, *----------------------------------------------------* X
ZFSHLQ=OMVS.SYSVIEW, <--- X
PATHPREFIX=, X
, *----------------------------------------------------* X
, * SMP/E * X
, *----------------------------------------------------* X
SMPEHLQ=, X
SMPETZ=CAIT, X
SMPEDZ=CAID, X
SMPEVOL=volume, <--- X
DLIBVOL=volume, <--- X
SMPEUNIT=SYSDA, X
DLIBUNIT=SYSDA, X
, *----------------------------------------------------* X
, * Data set and high level qualifiers * X
, *----------------------------------------------------* X
CEEHLQ=CEE, <--- X
IMSHLQ=ims, <--- X
MQSHLQ=mqseries, <--- X
SYSTCPD=TCPIP.TCPIP.DATA, <--- X
TCPMBR=, X
, *----------------------------------------------------* X
, * CA SYSVIEW Options * X
, *----------------------------------------------------* X
OPTIONS=(, Begin option list X
NOCAPTURE, ...option X
NOCICS, ...option X
NODATACOM, ...option X
NOIMS, ...option X
NOMVS, ...option X
NOMQSERIES, ...option X
NOTCPIP, ...option X
NOCEAPM, ...option X
NOCHORUS, ...option X
), End option list X
, *----------------------------------------------------* X
, * CA SYSVIEW Components * X
, *----------------------------------------------------* X
COMPONENTS=(, Begin component list X
DB2 ...component X
HCHECK, ...component X
MIM, ...component X
ROSCOE, ...component X
IDMS, ...component X
USS, ...component X
XSYSTEM, ...component X
), End component list X
, *----------------------------------------------------* X

, * CA SYSVIEW GEN parameters * X

, *----------------------------------------------------* X
SUBSYS=GSVX, X
, *----------------------------------------------------* X
, * The CA customer siteid. * X
, * The siteid will be used to assist technical * X
, * support with diagnostics. This is used when * X
, * FTPing information to CA. (optional) * X
, *----------------------------------------------------* X
SITEID=siteid, <--- X
, *----------------------------------------------------* X
, * Jobcard/JCL creation * X
, *----------------------------------------------------* X
JOBNAME=, X
NAME='PROGRAMMER NAME', <--- X
ACCT=(000000000), X
NOTIFY=NO, X
CLASS=A, X
MSGCLASS=A, X
MSGLEVEL=(1,1), X
ROUTE=NO, X
SYSAFF=NO, X
OUTC=*, X
, *----------------------------------------------------* X
, * Assemble and Link edit * X
, *--------------------------------------------------- * X
ASMPGM=ASMA90, X
LINKPGM=IEWL, X
, *----------------------------------------------------* X
, * End of Macro * X
, *----------------------------------------------------* X
DUMMY=DUMMY
*
* Do not remove the following line.
*
END
/*
You can modify the following GSVIINST parameters:

INSTLIB
Names the current installation library data set. Be sure that you use the same
high-level qualifier you used in the SYSLIB statement. See the step Modify and Run
the Job INSTALL.
Default: sysview.SAMPJCL
SYSPLIB
Specifies the system parameter library that contains the system configuration
options member.
Default: SYS1.PARMLIB
SOURCE=source
Specifies the source installation media type.
Valid Values:
ESDProvides the Electronic Software Delivery DASD file.
DVDContains a folder that includes the pax file for the product.
ESDHLQ=yourHLQ
This parameter is only used and required if SOURCE=ESD.
Specifies the high-level qualifier that is used when unzipping the ESD files to z/OS
data sets. UNZIPJCL performs this job.
The UNZIPJCL job references the high-level qualifier as yourHLQ. Use the same
value for the ESDHLQ= value.
PREFIX
Specifies the prefix for allocating data sets.
Limit: The length of PREFIX and SUFFIX must not exceed 24 characters.
Default: PREFIX=sysview

SITEDSN
Specifies whether to use a set of site libraries for maintaining your customized
library members.
The site data sets can be reused and carried forward when you migrate or update
to a new release of CA SYSVIEW.
Valid Values:
YES
Generates the sample job INST0006. This job creates a set of site libraries and
updates the sample GSVX* System configuration member accordingly.
NO
The sample job INST0006 is not generated.
<dsn_hlq>
Specify the high-level qualifier for an existing set of site libraries.
The low-level qualifier of CNM4Bnnn will be appended to the <dsn_hlq>
specified. The INST0005 job is not generated and the sample GSVX* System
configuration member is updated using the existing site HLQ.
Default: SITEDSN=YES
DELETE
Specifies the parameter for indicating whether to generate a DELETE request for
each new library before allocation. Specify YES or NO. If you are reinstalling to an
existing set of libraries, specify DELETE=NO.
Default: DELETE=YES
DASDVOL
Specifies the volume serial number (volser) of the volume on which to allocate data
sets.
SMS
Specifies the parameter for defining whether SMS is used for the data set
allocation. Specify YES or NO. If you specify YES, specify an SMS storage class on the
STORCLAS parameter.
Default: SMS=NO
SMSVOL
Specifies the volume serial number (volser) of the volume that is used to allocate
the SMS data sets.
Note: Some sites do not allow the volser to be specified for SMS.
STORCLAS
Specifies the SMS storage class that is used when you have specified YES on the
SMS parameter.
DSKUNIT
Specifies the disk unit type.
Default: DSKUNIT=SYSDA
WRKUNIT
Specifies the disk work unit type.
Default: WRKUNIT=SYSDA

PROFTYPE
Specifies the profile data set type that you want to allocate.
Valid Values:
PDS
Allocates the PDS profile data set, which is shared across multiple sysplexes.
LIBRARY
Allocates the profile PDSE data set, which can only be shared within a single
sysplex. If your configuration contains more than one sysplex, for each sysplex
allocate a unique data set.
Default: PDS
BLKSZU
Specifies the block size that is used when allocating data sets with an undefined
record length. Use this parameter for allocating the load library data sets.
Default: BLKSZU=6144
BLKSZFB
Specifies the block size that is used when allocating fixed block data sets.
Default: BLKSZFB=3200
BLKSZVB
Specifies the block size that is used when allocating variable block data sets.
Default: BLKSZVB=25600
ZFSHLQ
Specifies the high-level qualifier for the z/FS data set created during the installation
process:
zfshlq.ZFS
fmid
Contains the CA SYSVIEW SMP/E fmid.
Default: ZFSHLQ=OMVS.SYSVIEW
PATHPREFIX
Specifies the pathname prefix for the mount point of the z/FS data sets.
Default: PATHPREFIX=,
Example:
PATHPREFIX=/instpath
Resolves to the following mount points:

instpath/usr/lpp/sysview
instpath/usr/lpp/sysview/fmid
fmid
SMPEHLQ
Specifies the HLQ for the SMP/E libraries. Specifying a value for SMP/E HLQ
generates an extra sample job (INST0004). This job creates a set of run-time
libraries using the PREFIX specified HLQ.
SMPETZ
Specifies the SMP/E target zone.
Default: SMPETZ=CAIT
SMPEDZ
Specifies the SMP/E distribution zone.
Default: SMPEDZ=CAID
SMPEVOL
Specifies the volume where you allocated the internal SMP/E and target data sets.
DLIBVOL
Specifies the volume where you allocate the SMP/E distribution data sets.
SMPEUNIT
Specifies the unit type for the SMPEVOL specified volume.
DLIBUNIT
Specifies the unit type for the DLIBVOL specified volume.
CEEHLQ
Specifies the C language environment high-level qualifier at your site.

IMSHLQ
Specifies the IMS high-level qualifier for your site. If multiple releases of IMS are
being used, specify the highest level. This high-level qualifier is used to generate the
DD statements for the following data sets:
DD DSN=imshlq.SDFSRESL
MQSHLQ
Specifies WebSphere MQ high-level qualifier for your site. If multiple releases of
WebSphere MQ are being used, specify the highest level. This high-level qualifier is
used to generate the DD statements for the following data sets:
DD DSN=mqshlq.SCSQAUTH
DD DSN=mqshlq.SCSQLOAD
DD DSN=mqshlq.SCSQANLE
SYSTCPD
Specifies the name of the system TCP/IP configuration file. This parameter can also
be coded as a Hierarchical File System (HFS) path.
Default: TCPIP.TCPIP.DATA
TCPMBR
Specifies the member name from the TCP/IP data set (if any).
Note: This parameter is required only if the data set specified on the SYSTCPD
parameter is a PDS.
Default: None
OPTIONS
Specifies to enable those options that are licensed to the customer. The options
include the base product. Specifying an option value lets you use the option
commands. By default, you can access commands for the option from the CA
SYSVIEW main menu.
Note: Specify at least one option.
Values for the options parameter include:
CAPTURE|NOCAPTUREEvent Capture Option
CICS|NOCICSCA SYSVIEW Option for CICS
DATACOM|NODATACOMCA SYSVIEW CA Datacom Option
IMS|NOIMSCA SYSVIEW Option for IMS
MVS|NOMVSCA SYSVIEW Option for z/OS
MQSERIES|NOMQSERIESCA SYSVIEW Option for WebSphere MQ
TCPIP|NOTCPIPCA SYSVIEW Option for TCP/IP

CEAPM|NOCEAPMCA Cross Enterprise APM
CHORUS|NOCHORUSCA Chorus
COMPONENTS
Specifies the CA SYSVIEW components that you want enabled. Specifying a
component value lets you use the component commands. By default, you can
access commands for the component from the CA SYSVIEW main menu.
Note: DB2 is a new component and requires a license LMP key for CA Insight for
DB2.
Values for the components parameter include:
DB2|NODB2CA Insight for DB2
HCHECK|NOHCHECKIBM Health Checker
MIM|NOMIMCA MIM Resource Sharing for z/OS
ROSCOE|NOROSCOECA Roscoe
IDMS|NOIDMS
USS|NOUSSUNIX System Services
XSYSTEM|NOXSYSTEMThe Cross-system component
Note: Complete the CA SYSVIEW installation before installing or customizing some
of these components and options.
SUBSYS
Specifies the suffix for the System Configuration Options member name in the
system parameter library. Use GSVX if it is not already in use by another product.
The same subsystem can share multiple releases of CA SYSVIEW.
Default: SUBSYS=GSVX
SITEID=siteid
Specifies the CA customer site ID used when contacting technical support. Use this
site ID to FTP information to CA.
JOBNAME
Specifies the job name that is used when creating a JOB statement for installation
jobs. If no parameter is specified, the name of the installation member is used.
NAME
Specifies the programmer name that is specified on the JOB statement.
ACCT
Specifies the account number when it is necessary to build a JOB statement.
Default: ACCT=(00000000)

NOTIFY
Specifies the user ID that is notified when the job completes. If NO is specified, this
parameter is not generated on the JOB statement.
Default: NOTIFY=NO
CLASS
Specifies the job class for use on the JOB statement.
Default: CLASS=A
MSGCLASS
Specifies the message class for use on the JOB statement.
Default: MSGCLASS=A
MSGLEVEL
Specifies the message level for use on the JOB statement.
Default: MSGLEVEL=(1,1)
ROUTE
Generates the following route statement:
/*ROUTE PRINT userid
If NO is specified, this statement is not generated.

Default: ROUTE=NO
SYSAFF
Generates the following system affinity statement:
/*JOBPARM SYSAFF=sysname

Default: SYSAFF=NO
OUTC
Specifies the output class for use with SYSOUT.
Default: OUTC=*
ASMPGM
Specifies the name of the program that is used to assemble modules. Possible
values are IEV90 and ASMA90.
Default: ASMPGM=ASMA90
LINKPGM
Specifies the name of the program that is used to link-edit modules.
Default: LINKPGM=IEWL
Delete, Allocate, and Initialize Libraries (INST0001)
More information:
Output from ESD or DVD Install

The following table shows the members that are created during the installation.
Job/Procedure SAMPLIB Purpose

INST0001 None Deletes, allocates, and initializes the data sets.
INST0002 None Allocates and mounts the z/FS release dependent data set.
INST0003 None Performs the SMP/E functions RECEIVE, APPLY, and
ACCEPT.
INST0004 None Creates a set of run-time libraries.
INST0005 None Creates an empty set of site libraries.
Delete, Allocate, and Initialize Libraries (INST0001)

This step deletes, allocates, and initializes the CA SYSVIEW and SMP/E libraries, which
must be done before the libraries can be populated.
Follow these steps:

1. Review the INST0001 member in the sysview.SAMPJCL data set to ensure all of the
files that are referenced in the job are correct.
2. Submit the member INST0001.
When the job ends with a condition code of 0, the libraries are successfully
allocated and ready to be populated.

Allocate and Mount the z/FS Release Dependent Data Set (INST0002)
Allocate and Mount the z/FS Release Dependent Data Set

(INST0002)
Job INST002 creates the z/FS data set, directories, and mount-point for the new release
of CA SYSVIEW. This job is required each time that you install a new release of CA
SYSVIEW.
Important: Keep the file systems mounted and permanently available.
This procedure guides you through allocating and mounting the z/FS release dependent
data set.
Follow these steps:

names and parameters are correct.
2. Specify the allocation type:
Set ZFS='TRUE' for the z/FS files
Set ZFS='FALSE' for the HFS files
3. Submit the member INST0002
This member contains and runs the following steps. Each step must complete with a
return code of zero:
UNMOUNT
Unmounts an existing z/FS.
This step lets you execute the job again. The return code is forced to zero.
DELDIR
Deletes the specific release directory.
DELZFS
Deletes the z/FS.
ALLOCZFS
Allocates the z/FS data set.
FORMAT
Formats the z/FS data set.
MAKEDIR
Creates the required directory structure.
Receive, Apply, and Accept SMP/E Functions (INST0003)
MOUNT
Mounts the z/FS data set at the specified directory.
When the job ends with a return code of 0, the z/FS release dependent data set is
successfully allocated and mounted.
Receive, Apply, and Accept SMP/E Functions (INST0003)

This step performs the SMP/E RECEIVE, APPLY, and ACCEPT functions.
Follow these steps:

files that the job references are correct.
When the job ends with a condition code of 4 or less, the RECEIVE, APPLY, and
ACCEPT functions have been performed.
Create Run-Time Libraries (INST0004)

This optional step creates a set of run-time libraries for your environment.
Follow these steps:

1. Code a value for SMPEHLQ and specify a different HLQ for the SMP/E libraries.
The sample JCL member INST0004 is generated to create a set of run-time libraries.
2. Copy the SMP/E target libraries that are coded in the System Configuration Options
member.
The run-time libraries are created.
Note: INST0004 JCL is not generated when you eliminate the value for SMPEHLQ, or
SMPEHLQ has the same value as PREFIX.

Create Run-Time SITE Libraries (INST0005)

This optional step creates a set of run-time SITE libraries for your environment using the
same HLQ as the SYSTEM run-time libraries. The qualifier ".SITE" is appended before the
low-level data set qualifier to differentiate the SITE libraries from the SYSTEM libraries.
Follow these steps:

1. Code a value for SMPEHLQ to specify a different HLQ for the SMP/E libraries. This
step allows the coded value for PREFIX to be used as the HLQ for both the SYSTEM
and SITE run-time libraries.
The sample JCL member INST0005 is generated to create a set of SITE run-time
libraries.
2. Copy the members that were configured from the run-time libraries of your prior
version of CA SYSVIEW into the SITE libraries.
The SITE run-time libraries are created.
Note: INST0005 JCL is not generated when you specify SITEDSN=NO, or you specify a
high-level qualifier for SITEDSN to carry an existing set of SITE libraries forward from a
prior release. If you specified SITEDSN=YES, then run INST0005 to allocate the libraries.
If you do not run INST0005, then reset the "Dsn-Site" values in the sample System
Configuration member back to NONE.
Clean Up the USS Directory

Important! This procedure is optional. Do not use this procedure until you complete the
entire installation process.
To free file system disk space for subsequent downloads after downloading and
processing the pax files for your CA Technologies product, we recommend removing the
files from your USS directory and deleting unnecessary MVS data sets. You can delete
the following items:
Pax file
Product-specific directory that the pax command created and all of the files in it
SMP/E RELFILEs, SMPMCS, and HOLDDATA MVS data sets
These data sets have the HLQ that you assigned in the UNZIPJCL job.
Note: Retain non-SMP/E installation data sets such as yourHLQ.INSTALL.NOTES for

future reference.
Apply Preventive Maintenance
Follow these steps:

1. Navigate to your Pax ESD USS directory.
Your view is of the applicable USS directory.
2. Delete the pax file by entering the following command:
rm paxfile
paxfile
Specifies the name of the CA Technologies pax file that you downloaded.
The pax file is deleted.
3. Delete the product-specific directory by entering the following command:
rm -r product-specific_directory
product-specific_directory
Specifies the product-specific directory that the pax command created.
The product-specific directory is deleted.
Note: You can also use TSO ISHELL to navigate to the pax file and product-specific
directory, and delete them using the D line command.

Important! We strongly recommend that you use CA CSM to maintain your CA
Technologies z/OS-based products. The procedure that is discussed in this section is fully
automated when you use CA CSM.
CA Support Online at http://ca.com/support has the maintenance and HOLDDATA

published after the installation data was created. After the maintenance process
completes, the product is ready to deploy.
Use this procedure during the product installation and for ongoing preventive
maintenance in noninstallation use cases according to your maintenance strategy.
Note: To review the CA Technologies mainframe maintenance philosophy, see your Best
Practices Guide or visit the CA Next-Generation Mainframe Management page.
This procedure directs you to use the CAUNZIP utility. The CAUNZIP utility processes ZIP
packages directly on z/OS without the need for an intermediate platform, such as a
Microsoft Windows workstation. If you are not familiar with this utility, see the CA
Common Services for z/OS Administration Guide. This guide includes an overview and
sample batch jobs. To use this utility, you must be running CA Common Services for z/OS
Version 14.0 with PTF RO54887 or CA Common Services for z/OS Release 14.1 with PTF
RO54635.

Follow these steps:

1. Check the Download Center at http://ca.com/support for PTFs that have been
published after this release was created. A recently created base release has no
published PTFs. When PTFs exist, add published solutions for your product to your
Download Cart and click Checkout.
2. Specify that you want a complete package.
When the processing completes, a link appears on the Review Download Requests
page. You also receive an email notification.
3. Click the Alternate FTP link for your order to obtain the FTP login information and
the ZIP file location. Download the ZIP file into a USS directory on your z/OS system.
4. Run the CAUNZIP utility.
CAUNZIP unzips the package of published solutions and creates the SMPNTS file
structure that the SMP/E RECEIVE FROMNTS command can process. For the sample
JCL to run the utility that is located in yourHLQ.CAW0JCL(CAUNZIP), see the CA
Common Services for z/OS CAUNZIP Administration Guide. After the execution
completes, the ZIPRPT data set contains the summary report. The summary report
provides the following information:
Summarizes the content of the product order ZIP file.
Details the content of each data set and the z/OS UNIX files produced.
Provides a sample job for receiving the PTFs in your order.
5. Review the sample job that is provided in the CAUNZIP output ZIPRPT file.
To receive the PTFs in your order:
a. Cut and paste the JCL into a data set.
b. Specify your SMP/E CSI on the SMPCSI DD statement.
c. Submit the job.
6. Submit the SAMPJCL member NM41HOLD.
The job downloads the external HOLDDATA file.
7. Submit the SAMPJCL member NM47RECH.
The job receives the external HOLDDATA file.
8. Submit the SAMPJCL member NM48APYP.
The PTFs are applied.
9. (Optional) Submit the SAMPJCL member NM49ACCP.
The PTFs are accepted.
Note: You do not have to submit the job now. You can accept the PTFs according to
your site policy.
HOLDDATA
When you apply maintenance, you typically encounter SMP/E HOLDDATA. We use
HOLDDATA to notify your SMP/E system of SYSMODs that have errors or special
conditions. We support system and external HOLDDATA.
System HOLDDATA
System HOLDDATA indicates data that is an in-stream part of the SYSMOD, informing
you of special conditions. The following reasons are used with SYSTEM HOLDDATA for
your product:
ACTION
Indicates that you must perform special processing before or after you apply this
SYSMOD.
AO
Affects automated operations. It changes either the message identifier or the
displacement of a field inside the message.
DDDEF
Indicates that data sets and DDDEFs are being added or modified.
DELETE
Deletes the SYSMOD load module. You cannot reverse this type of SYSMOD with
the SMP/E RESTORE command.
DEP
Indicates a dependency for this SYSMOD that you must externally verify.
DOC
Indicates a documentation change with this SYSMOD.
DYNACT
Describes the steps to dynamically activate this fix without performing an IPL.
ENH
Introduces a small programming enhancement. The hold contains the instructions
to implement the enhancement. If no action is needed to implement the
enhancement, give a summary of the enhancement.
EXIT
Indicates that changes delivered by this SYSMOD require reassembly of user exits.
EXRF
Indicates that the SYSMOD must be installed in both the Active and Alternate
Extended Recovery Facility Systems.

MULTSYS
Apply this SYSMOD to multiple systems for either pre-conditioning, coexistence, or
exploitation.
RESTART
Indicates that after applying this SYSMOD, the site must perform a special restart as
opposed to a routine restart.
SYSMOD
Indicates that some or all of the elements that this SYSMOD delivers are to be
downloaded to a workstation.
Code a bypass operand on your APPLY command to install SYSMODs that have internal
holds. Code the bypass operand only after you have performed the required action, or if
you are performing the action after the APPLY, if that is appropriate.
External HOLDDATA
External HOLDDATA is not part of the PTF. The HOLDDATA resides in a separate file and
contains both error and FIXCAT HOLDDATA. The error HOLDDATA is commonly used for
SYSMODs that have been distributed and later are discovered to cause problems. The
FIXCAT HOLDDATA helps identify maintenance that is required to support a particular
hardware device, software, or function.
Download the external HOLDDATA from http://ca.com/support to a DASD file, and

allocate the file to the SMPHOLD DD statement. To take care of the external HOLDDATA,
receive it into your SMP/E environment. SMP/E receives the HOLDDATA from
CA-supplied jobs.
You can find JCL to download the external HOLDDATA in your SAMPJCL member. Open
NM41HOLD in an edit session and execute the NM4SEDIT macro on the command line.
Then, submit the JCL.
Error HOLDDATA
If a SYSMOD has an unresolved hold error, SMP/E does not install it unless you add a
bypass to your APPLY command. You can bypass an error hold in situations that are not
applicable to you. Error holds that are not applicable to you can include a problem that
happens only with a hardware device that you do not have or in a product feature that
you do not use.
When CA Technologies publishes a SYSMOD that resolves the hold, the resolving
SYSMOD supersedes the hold error. This action lets you apply the original SYSMOD in
conjunction with the fixing SYSMOD.
A special HOLDDATA class that is called ERREL exists. We have determined that the
problem fixed by the SYSMOD is more important than the one that it causes. We
recommend that you apply these SYSMODs.
The only manual task is running a REPORT ERRSYSMODS. This report identifies the
following:
Any held SYSMODs already applied to your system
Any resolving SYSMODs that are in RECEIVE status
SMP/E identifies the SYSMOD to apply to correct the situation.
FIXCAT HOLDDATA
CA Technologies provides FIXCAT HOLDDATA to help identify maintenance that is

required to support a particular hardware device, software, or function. Fix categories
are supplied as SMP/E FIXCAT HOLDDATA statements. Each FIXCAT HOLDDATA
statement associates an APAR and its related fixing PTF to one or more fix categories.

Chapter 5: Starting Your Product
How to Prepare for Deployment (see page 75)
How to Complete Deployment With CA CSM (see page 75)
How to Deploy Without CA CSM (see page 76)
How to Complete Configuration With CA CSM (see page 77)
How to Configure Without CA CSM (see page 78)
Assemble and Link the Default SSID (USRM0001) (see page 151)
Prepare to Start Your Product (see page 151)
Start Your Product (see page 154)
Post-Installation Considerations (see page 155)
How to Prepare for Deployment

This section contains topics that describe the manual tasks you need to perform before
beginning the deployment process.
Apply IBM APARs

CA Support identifies any IBM APARs that impact the operation or performance of your
product and makes them available in the UPGRADE solution record. We recommend
that you review our current list of IBM APARs and apply only those that are appropriate
to your environment.
Note: For a current list of IBM APARs, read the UPGRAD solution record for SYSVW.
Run Any Other Jobs

Before deployment and configuration, the following tasks must be performed.
How to Complete Deployment With CA CSM

The topics in this section describe the manual tasks you perform when deploying your
product using CA CSM.

How to Deploy Without CA CSM
Startup JCL Procedures Customized by CA CSM

Use CA CSM to deploy a copy of all CA SYSVIEW SMP/E installed target libraries to any
systems defined in the CA CSM system registry, including:
Non-sysplex systems
Sysplexes
Shared DASD Clusters
Staging systems
How to Deploy Without CA CSM

The topics in this section describe the manual tasks you perform if you are not deploying
your product using CA CSM.
How to Complete Configuration With CA CSM
Note: We recommend that you do not use SMP/E target libraries for runtime.
See install job INST0005 in the topic Output from INSTALL (see page 93).
Deploy a runtime copy of the following CA SYSVIEW SMP/E-installed target libraries:

CAI.SYSVIEW.CNM4BLOD
CAI.SYSVIEW.CNM4BCAP
CAI.SYSVIEW.CNM4BCLS
CAI.SYSVIEW.CNM4BDAT
CAI.SYSVIEW.CNM4BHLP
CAI.SYSVIEW.CNM4BISP
CAI.SYSVIEW.CNM4BMAP
CAI.SYSVIEW.CNM4BMIB
CAI.SYSVIEW.CNM4BPLT
CAI.SYSVIEW.CNM4BPNL
CAI.SYSVIEW.CNM4BPRF
CAI.SYSVIEW.CNM4BPRM
CAI.SYSVIEW.CNM4BREX
CAI.SYSVIEW.CNM4BSAM
CAI.SYSVIEW.CNM4BSEC
CAI.SYSVIEW.CNM4BTMP
You can provide access to these libraries using one of the following methods:
Allocate a single copy of these libraries on shared DASD that is accessible to all
systems.
Allocate a unique copy of these libraries on each system.
How to Complete Configuration With CA CSM

The topics in this section describe the manual tasks you perform when configuring your
product using CA CSM.
The operational narratives in the CA CSM user interface guide you through the
configuration.

How to Configure Without CA CSM

The topics in this section describe the manual tasks you perform if you are not
configuring your product using CA CSM.
The SAMPJCL data set is required to complete the configuration steps. If you installed
using the ESD method, the SAMPJCL data set has already been created. If you installed
using CA CSM, the sample JCL to allocate the SAMPJCL data set is in the member
MSMJCL of the CNM4BSAM SMP/E target library.
If you installed using the ESD method, continue with the section titled Output from
Install (see page 93).
Sample JCL for Product Configuration

Complete the configuration steps using the following JCL.
//MSMINST JOB (0000)

//*
//*==================================================================*
//* *
//* Sample job to create the sysview.SAMPJCL data set. *
//* *
//* PREFIX = the dataset HLQ used for the SMP/E target *
//* zone when the MSM install was performed. *
//* VOLUME = DASD volume *
//* *
//*==================================================================*
//*
// SET PREFIX=sysview
// SET VOLUME=volume
//*
//COPY EXEC PGM=IEBCOPY
//*
//IN DD DISP=SHR,DSN=&PREFIX..CNM4BSAM
//*
//SAMPJCL DD DSN=&PREFIX..SAMPJCL,
// DISP=(NEW,CATLG,DELETE),
// UNIT=SYSDA,
// VOL=SER=&VOLUME,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(CYL,(05,02,45))
//*
//SYSIN DD DISP=SHR,DSN=&PREFIX..CNM4BSAM(SAMPJCL)
//*
Note: For CA CSM information, see the CA Chorus Software Manager documentation
bookshelf on the CA Chorus Software Manager product page.


The job INSTALL in the installation library SAMPJCL generates the JCL stream necessary
to install CA SYSVIEW.
This step contains instructions for modifying the job INSTALL to meet the needs of your
site.
Before you begin this step, have the following information available:
The high-level qualifier (HLQ), which must be 24 characters or fewer.
Follow these steps:

1. Modify the following JOB statement in INSTALL to the requirements of your site:
2. Modify the following SYSLIB statement in INSTALL to replace the high-level qualifier
of sysview with the qualifier you chose when you downloaded the installation
library:
//SYSLIB DD DISP=SHR,DSN=sysview.SAMPJCL
3. Modify the GSVIINST macro parameters in INSTALL.

The INSTALL job stream contains the parameters for the macro GSVIINST. The
values that are assigned to these parameters determine how CA SYSVIEW is
installed. You can change these values in the generated job stream before the step
where they are used.
4. Submit the job INSTALL.
The job is submitted to the internal reader, and the job stream is generated.
The job name that you specified on the JOBNAME parameter is the output from the
assembly. If you did not specify a job name, the job output is INST0000.
Important! Your TSO enqueues on the sysview.SAMPJCL while members are edited.
Therefore, end the edit session to release this data set so the job executes.
More information:
GSVIINST MacroSet INSTALL Parameters (see page 81)
GSVIINST MacroSet INSTALL Parameters
Set the parameters for the GSVIINST macro before you submit the job INSTALL. The
following example shows the default parameter values that appear in the job INSTALL.
These parameters have the following syntax:

//*
//*----------------------------------------------------------------------------*
//* CA SYSVIEW *
//* Installation generator *
//* *
//* This job will dynamically build the other jobs that are *
//* required to complete the installation. *
//* *
//* *--------------------* Important Notice *-------------------* *
//* *
//* CA Mainframe Software Manager *
//* *
//* If you have used CA Mainframe Software Manager *
//* to perform the installation of the product, *
//* this step is required. *
//* *
//* Step: Required *
//* *
//*----------------------------------------------------------------------------*
//ASM EXEC PGM=ASMA90,REGION=1024K,PARM='NOTERM,LIST,DECK,NOOBJECT'
//*
//SYSPUNCH DD SYSOUT=(*,INTRDR),DCB=(RECFM=FB,LRECL=80,BLKSIZE=2000)
//*----------------------------------------------------------------------------*
//* The data set defined to the DDNAME SYSLIB should also *
//* be coded as the data set name on the GSVIINST option *
//* INSTLIB=. *
//* *
//* The options that require modification or inspection *
//* for specific site installation needs are marked with *
//* a "<---". *
//*----------------------------------------------------------------------------*
//*
//SYSLIB DD DISP=SHR,DSN=sysview.SAMPJCL <---INSTLIB
//*
//*
//* Note: When modifying the macro below, remember to include
//* the continuation character "X" in column 72 for all
//* lines except the last line containing the DUMMY=

//* parameter.
//*
//*.+....1....+....2....+....3....+....4....+....5....+....6....+....7.X
//SYSIN DD *
*
PRINT NOGEN
GSVIINST X
, *---------------------------------------------------* X
, * Installation data set name * X
, * This is the data set name that you are * X
, * editing now. * X
, *---------------------------------------------------* X
INSTLIB=sysview.SAMPJCL, <--- X
, *------------------------------------------- -------* X
, * System parmlib data set * X
, *---------------------------------------------------* X
SYSPLIB=SYS1.PARMLIB, <--- X
, *---------------------------------------------------* X
, * Source installation Media * X
, * ESD - ESD file on DASD * X
, *---------------------------------------------------* X
SOURCE=ESD, ESD|DVD <--- X
, *---------------------------------------------------* X
, * High-level qualifier used when the ESD file * X
, * was UNZIPPED. * X
, *---------------------------------------------------* X
ESDHLQ=yourHLQ, ESD HLQ <--- X
, *---------------------------------------------------* X
, * Data set allocation * X
, *---------------------------------------------------* X
PREFIX=sysview, <--- X
SITEDSN=YES, <--- X
DELETE=YES, X
DASDVOL=volume, <--- X
SMS=NO, X
SMSVOL=, X
STORCLAS=, X
DSKUNIT=SYSDA, X
WRKUNIT=SYSDA, X
PROFTYPE=PDS, X
, *---------------------------------------------------* X
, * Data set blocksizes * X
, *---------------------------------------------------* X
BLKSZU=6144, X
BLKSZFB=3200, X
BLKSZVB=25600, X
, *---------------------------------------------------* X
, * z/FS data set allocation * X
, *---------------------------------------------------* X
ZFSHLQ=OMVS.SYSVIEW, <--- X
PATHPREFIX=, X
, *---------------------------------------------------* X
, * SMP/E * X
, *---------------------------------------------------* X
SMPEHLQ=, X
SMPETZ=CAIT, X
SMPEHLQ= X
SMPEDZ=CAID, X
SMPEVOL=volume, <--- X
DLIBVOL=volume, <--- X
SMPEUNIT=SYSDA, X
DLIBUNIT=SYSDA, X
, *---------------------------------------------------* X
, * Data set and high level qualifiers * X
, *---------------------------------------------------* X
CEEHLQ=CEE, <--- X
IMSHLQ=ims, <--- X
MQSHLQ=mqseries, <--- X
SYSTCPD=TCPIP.TCPIP.DATA, <--- X
TCPMBR=, X
, *---------------------------------------------------* X
, * CA SYSVIEW Options * X
, *---------------------------------------------------* X
OPTIONS=(, Begin option list X
NOCAPTURE, ...option X
NOCICS, ...option X
NODATACOM, ...option X
NOIMS, ...option X
NOMVS, ...option X
NOMQSERIES, ...option X
NOTCPIP, ...option X
NOCEAPM, ...option X
NOCHORUS, ...option X
), End option list X
, *---------------------------------------------------* X
, * CA SYSVIEW Components * X
, *---------------------------------------------------* X
COMPONENTS=(, Begin component list X
DB2, ...component X
HCHECK, ...component X
MIM, ...component X
ROSCOE, ...component X
IDMS, ...component X
USS, ...component X
XSYSTEM, ...component X
), End component list X
, *---------------------------------------------------* X
, * CA SYSVIEW GEN parameters * X

, *---------------------------------------------------* X
SUBSYS=GSVX, X
, *---------------------------------------------------* X
, * The CA customer siteid. * X
, * The siteid will be used to assist technical * X
, * support with diagnostics. This is used when * X
, * FTPing information to CA. (optional) * X
, *---------------------------------------------------* X
SITEID=siteid, <--- X
, *---------------------------------------------------* X
, * Jobcard/JCL creation * X
, *---------------------------------------------------* X
JOBNAME=, X
NAME='PROGRAMMER NAME', <--- X
ACCT=(000000000), X
NOTIFY=NO, X
CLASS=A, X
MSGCLASS=A, X
MSGLEVEL=(1,1), X
ROUTE=NO, X
SYSAFF=NO, X
OUTC=*, X
, *---------------------------------------------------* X
, * Assemble and Link edit * X
, *---------------------------------------------------* X
ASMPGM=ASMA90, X
LINKPGM=IEWL, X
, *---------------------------------------------------* X
, * End of Macro * X
, *---------------------------------------------------* X
DUMMY=DUMMY
*
* Do not remove the following line.
*
END
/*
You can modify the following GSVIINST parameters:

INSTLIB
Names the current installation library data set. Ensure that you use the same
high-level qualifier that you used in the SYSLIB statement in the step Modify and
Run the Job INSTALL.
Default: sysview.SAMPJCL
SYSPLIB
Specifies the system parameter library that contains the system configuration
options member.
Default: SYS1.PARMLIB
SOURCE=source
Specifies the source installation media type.
Valid Values:
ESDSpecifies the electronic software delivery DASD file, use SOURCE=ESD if
you installed using MSM.
DVDContains a folder that includes the pax file for the product.
ESDHLQ=yourHLQ
This parameter is only used and required if SOURCE=ESD.
Specifies the high-level qualifier for unzipping the ESD files to z/OS data sets.
UNZIPJCL performs this job.
Specifies the high-level qualifier for unzipping the ESD files to z/OS data sets.
UNZIPJCL performs this job.
The UNZIPJCL job references the high-level qualifier as yourHLQ. Use this same
value for the ESDHLQ= value.
PREFIX
Specifies the prefix that is used for allocating data sets.
Limit: The length of PREFIX and SUFFIX must not exceed 24 characters.
Default: PREFIX=sysview

SITEDSN
Specifies whether to use a set of site libraries for maintaining your customized
library members.
The site data sets can be reused and carried forward when you migrate or update
to a new release of CA SYSVIEW.
Valid Values:
YES
Generates the sample job INST0005. This job creates a set of site libraries and
updates the sample GSVX* System configuration member accordingly.
NO
The sample job INST0005 is not generated.
<dsn_hlq>
Specify a data set HLQ for an existing set of SITE libraries.
The low-level qualifier of CNM4Bnnn will be appended to the <dsn_hlq>
specified. The INST0005 job is not generated and the sample GSVX* System
configuration member is updated using the existing site HLQ.
Default: SITEDSN=YES
DELETE
Specifies the parameter that is used to indicate whether to generate a DELETE
request for each new library before allocation. Specify YES or NO. If you are
reinstalling to an existing set of libraries, specify DELETE=NO.
Default: DELETE=YES
DASDVOL
Specifies the volume serial number (volser) of the volume on which to allocate data
sets.
SMS
Specifies the parameter that is used to define whether SMS is used for the data set
allocation. Specify YES or NO. If you specify YES, then specify an SMS storage class
on the STORCLAS parameter.
Default: SMS=NO
SMSVOL
Specifies the volume serial number (volser) of the volume for allocating the SMS
data sets.
Note: Some sites do not allow the volser to be specified for SMS.
STORCLAS
Specifies the SMS storage class that you use when you specify YES on the SMS
parameter.
DSKUNIT
Specifies the disk unit type.
Default: DSKUNIT=SYSDA
WRKUNIT
Specifies the disk work unit type.
Default: WRKUNIT=SYSDA

PROFTYPE
Specifies the profile data set type that you want to allocate.
Valid Values:
PDS
Allocates the PDS profile data set. One PDS is shared across multiple sysplexes.
LIBRARY
Allocates a PDSE profile data set, which can only be shared within a single
sysplex. If your configuration contains more than one sysplex, each sysplex
requires a unique data set allocated.
Default: PDS
BLKSZU
Specifies the block size when allocating data sets with an undefined record length.
Use this parameter for allocating the load library data sets.
Default: BLKSZU=6144
BLKSZFB
Specifies the block size when allocating fixed block data sets.
Default: BLKSZFB=3200
BLKSZVB
Specifies the block size when allocating variable block data sets.
Default: BLKSZVB=25600
ZFSHLQ
Specifies the high-level qualifier for the z/FS data set created during the installation
process:
zfshlq.ZFS
fmid
Default: ZFSHLQ=OMVS.SYSVIEW
PATHPREFIX
Specifies the pathname prefix for the mount point of the z/FS data sets.
Default: PATHPREFIX=,
Example:
PATHPREFIX=/instpath
This prefix resolves to the following mount points:

instpath/usr/lpp/sysview
instpath/usr/lpp/sysview/fmid
fmid
SMPEHLQ
Specifies the HLQ for the SMP/E libraries. Specifying a value for the SMP/E HLQ
generates an extra sample job (INST0004). This job creates a set of run-time
libraries using the HLQ specified with PREFIX.
SMPETZ
Specifies the SMP/E target zone.
Default: SMPETZ=CAIT
SMPEDZ
Specifies the SMP/E distribution zone.
Default: SMPEDZ=CAID
SMPEVOL
Specifies the volume where you allocated the internal SMP/E and target data sets.
DLIBVOL
Specifies the volume where you allocate the SMP/E distribution data sets.
SMPEUNIT
Specifies the unit type for the SMPEVOL specified volume.
DLIBUNIT
Specifies the unit type for the DLIBVOL specified volume.
CEEHLQ
Specifies your site C language environment high-level qualifier.

IMSHLQ
Specifies your site IMS high-level qualifier. If multiple releases of IMS are being
used, specify the highest level. This high-level qualifier is used to generate the DD
statements for the following data sets:
DD DSN=imshlq.SDFSRESL
MQSHLQ
Specifies your site WebSphere MQ high-level qualifier. If multiple releases of
WebSphere MQ are being used, specify the highest level. This high-level qualifier is
used to generate the DD statements for the following data sets:
DD DSN=mqshlq.SCSQAUTH
DD DSN=mqshlq.SCSQLOAD
DD DSN=mqshlq.SCSQANLE
SYSTCPD
Specifies the name of the system TCP/IP configuration file. You can also code this
parameter as a Hierarchical File System (HFS) path.
Default: TCPIP.TCPIP.DATA
TCPMBR
Specifies the member name from the TCP/IP data set (if any).
Note: This parameter is required only if the data set specified on the SYSTCPD
parameter is a PDS.
Default: None
OPTIONS
Enables those options that are licensed to the customer. The options include the
base product. Specifying an option value lets you use the option commands. By
default, you can access commands for the option from the CA SYSVIEW main menu.
Note: Specify at least one option.
Values for this parameter include:
CAPTURE|NOCAPTUREEvent Capture Option
CICS|NOCICSCA SYSVIEW Option for CICS
DATACOM|NODATACOMCA SYSVIEW CA Datacom Option
IMS|NOIMSCA SYSVIEW Option for IMS
MVS|NOMVSCA SYSVIEW Option for z/OS
MQSERIES|NOMQSERIESCA SYSVIEW Option for WebSphere MQ
TCPIP|NOTCPIPCA SYSVIEW Option for TCP/IP
CEAPM|NOCEAPMCA SYSVIEW for CA APM
CHORUS|NOCHORUSCA Chorus
COMPONENTS
Specifies the CA SYSVIEW components that you want to enable. Specifying a
component value lets you use the component commands. By default, you can
access commands for the component from the CA SYSVIEW main menu.
Note: DB2 is a new component and requires a license, LMP key, for CA Insight for
DB2.
This parameter includes the following values:
DB2|NODB2CA Insight for the DB2
HCHECK|NOHCHECKIBM Health Checker
MIM|NOMIMCA MIM Resource Sharing for the z/OS
ROSCOE|NOROSCOECA Roscoe
IDMS|NOIDMS
USS|NOUSSUNIX System Services
XSYSTEM|NOXSYSTEMThe Cross-system component
Note: Perform extra installation or customization for some of these components
and options after completing this installation of CA SYSVIEW.
SUBSYS
Specifies the suffix for the System Configuration Options member name in the
system parameter library. Use GSVX if it is not already in use by another product.
The same subsystem can share multiple releases of CA SYSVIEW.
Default: SUBSYS=GSVX
SITEID=siteid
Specifies the CA customer site ID for contacting technical support. Use this site ID to
FTP information to CA.
JOBNAME
Specifies the job name that you use to create a JOB statement for installation jobs.
If no parameter is specified, the name of the installation member is used.
NAME
Specifies the programmer name from the JOB statement.
ACCT
Specifies the account number when it is necessary to build a JOB statement.
Default: ACCT=(00000000)

NOTIFY
Specifies the user ID that is notified when the job completes. If NO is specified, this
parameter is not generated on the JOB statement.
Default: NOTIFY=NO
CLASS
Specifies the job class that is used on the JOB statement.
Default: CLASS=A
MSGCLASS
Specifies the message class that is used on the JOB statement.
Default: MSGCLASS=A
MSGLEVEL
Specifies the message level that is used on the JOB statement.
Default: MSGLEVEL=(1,1)
ROUTE
Generates the following route statement:
/*ROUTE PRINT userid

Default: ROUTE=NO
SYSAFF
Generates the following system affinity statement: /*JOBPARM SYSAFF=sysname. If
NO is specified, this statement is not generated.
Default: SYSAFF=NO
OUTC
Specifies the output class for use with SYSOUT.
Default: OUTC=*
ASMPGM
Specifies the name of the program that is used to assemble modules. Possible
values are IEV90 and ASMA90.
Default: ASMPGM=ASMA90
LINKPGM
Specifies the name of the program that is used to link-edit modules.
Default: LINKPGM=IEWL
More information:
Output from INSTALL
During the installation, the job INST0110 copies selected members from the INSTLIB to
the sysview.CNM4BSAM. The copied members are shown with a member name in the
SAMPLIB column.
The following table shows the members that are created during the installation.

INST0004 None Creates a set of run-time libraries when SMPEHLQ is coded.
INST0005 None Creates the run-time site libraries.
INST0010 None Specifies the system information utility, GSVCUTIL.
INST0011 GSVXGSVX Copies System Configuration Options member to the
system PARMLIB.
INST0013 MVSMAPS Assembles the MVS DSECT maps.
INST0020 ASMJES Assembles and links the JES configuration module.
INST0021 JESMAPS Assembles the JES DSECT maps.
INST0030 CAPINDEX Initializes the Event Capture index data set.
INST0031 None Defines the CA GSS IMOD library.
INST0032 None Loads and compiles IMOD source modules into the CA GSS
IMOD library.
INST0040 LOGRADTT Allocates log stream Audit.
INST0041 LOGRPLOT Allocates log stream Plot.
INST0042 LOGRXLOG Allocates log stream Xlog.
INST0043 LOGRSMFD Allocates log stream SMFD.
INST0044 LOGRCICS Allocates log stream CICS.
INST0045 LOGRIMTR Allocates log stream IMS.
INST0046 LOGRMQHR Allocates log stream MQ.
INST0050 CNVTSECU Converts the security data set.
INST0051 CNVTPROF Converts the profile data set.
INST0060 CSDUTIL Defines the CICS CSD objects.


INST0061 None Link edits CICS object members to create a load module to
format the CICS internal trace table entries.
INST0110 None Copies sample members to specific libraries for future use.
USRM0001 None USERMOD to assemble and link the default substem ID
(SSID).
IVPnnnnn None Verifies the installation.
Note: This set of installation verification programs can be
executed when the installation is complete and CA
SYSVIEW is started.
ASMCMDX ASMCMDX Assembles the command exit.
ASMSDSFX ASMSDSFX Assembles the SDSF command exit.
CICSJCL CICSJCL Indicates sample CICS JCL statements.
CICSMAPS CICSMAPS Assembles the CICS DSECT maps.
EXPRPT EXPRPT Sample job for EXPLORE Report Writer.
FTPCA FTPCA Sample JCL to FTP data sets to CA support.
IMODLOAD IMODLOAD Utility job to copy and compile IMODS into the CA SYSVIEW
IMOD library.
IMSMAPS IMSMAPS Assembles the IMS DSECT maps.
MIBCOMP MIBCOMP Indicates the MIB compiler.
SYSVIEW SYSVIEW Indicates the CA SYSVIEW main services startup procedure.
SYSVLCL SYSVLCL Indicates the CA SYSVIEW local 3270 interface startup
procedure.
SYSVUSER SYSVUSER Indicates the CA SYSVIEW user address space startup
procedure.
SYSVAUX SYSVAUX Indicates the CA SYSVIEW auxiliary services startup
procedure.
EZREPORT EZREPORT Indicates the sample CA Easytrieve report JCL.
SMPPTF None Applies individual test APARs and published PTFs.
NM41HOLD None FTP download SMP/E ERROR HOLDDATA
NM47RECH None SMP/E Receive HOLDDATA
NM47RECP None SMP/E Receive SYSMODS
NM48APYP None SMP/E Apply PTFS
NM49ACCP None SMP/E Accept PTFS
Create Run-Time Libraries (INST0004)

This optional step creates a set of run-time libraries for your environment.
Follow these steps:

1. Code a value for SMPEHLQ and specify a different HLQ for the SMP/E libraries.
The sample JCL member INST0004 is generated to create a set of run-time libraries.
2. Copy the SMP/E target libraries that are coded in the System Configuration Options
member.
The run-time libraries are created.
Note: INST0004 JCL is not generated when you eliminate the value for SMPEHLQ, or
SMPEHLQ has the same value as PREFIX.

This optional step creates a set of run-time SITE libraries for your environment using the
same HLQ as the SYSTEM run-time libraries. The qualifier ".SITE" is appended before the
low-level data set qualifier to differentiate the SITE libraries from the SYSTEM libraries.
Follow these steps:

1. Code a value for SMPEHLQ to specify a different HLQ for the SMP/E libraries. This
step allows the coded value for PREFIX to be used as the HLQ for both the SYSTEM
and SITE run-time libraries.
The sample JCL member INST0005 is generated to create a set of SITE run-time
libraries.
2. Copy the members that were configured from the run-time libraries of your prior
version of CA SYSVIEW into the SITE libraries.
The SITE run-time libraries are created.
Note: INST0005 JCL is not generated when you specify SITEDSN=NO, or you specify a
high-level qualifier for SITEDSN to carry an existing set of SITE libraries forward from a
prior release. If you specified SITEDSN=YES, then run INST0005 to allocate the libraries.
If you do not run INST0005, then reset the "Dsn-Site" values in the sample System
Configuration member back to NONE.

Run the System Information Utility GSVCUTIL (INST0010)

The system information utility GSVCUTIL provides you with a report showing your
system during the installation. After you run this utility, use the information to verify
your GSVIINST parameter values.
Follow these steps:

1. Review the INST0010 member in the data set sysview.SAMPJCL and verify the files
that are referenced in the job are correct.
You receive a report with the following information when this job ends with a
condition code of 0:
z/OS system
Subsystem
Authorized Program Facility (APF) list
The SYSVIEW LMP keys
3. Verify parameter values.
a. Review the report information.
b. Compare the parameter values shown on the report with the values you
entered to modify and run the INSTALL job.
c. Modify parameter values if the information is incorrect.
If the information is correct, the installation can continue.
Copy System Configuration Options to System PARMLIB (INST0011)

The System Configuration Options member is used to set configuration options during
the initialization of CA SYSVIEW.
Follow these steps:

1. Review the INST0011 member in the sysview.SAMPJCL data set.
The SAMPJCL SMP/E target library contains the sample GSVXGSVX member.
INST0011 copies the System Configuration Options member to the System
PARMLIB that was defined in the INSTALL job.
The member name is based on the SUBSYS that was specified in INSTALL and
has the following format:
GSVX<subsys>
subsys
The System Configuration Options member name. The default value for
subsys is GSVX, so the default System Configuration Options member name
is GSVXGSVX.
The INSTALL job generates a System Configuration Options member in the
SAMPJCL using the SUBSYS suffix from INSTALL. INST0011 copies this member
into the System PARMLIB.

System Configuration Options
The system configuration options are set during the CA SYSVIEW initialization. They are
not case-sensitive. Review the following options before running job INST0011.
Administrator-Userid
Define at least one administrator using this option. You can code this option
multiple times to specify more administrators.
Note: You can also use the CA SYSVIEW SECURITY command to define more
administrators.
Valid Values: Any valid user ID
Default: None
CA-Customer-SiteID
Specifies the CA customer site ID that you use to contact technical support. Use the
site ID to FTP information to CA.
Valid Values: Seven-digit numeric value
Default: 0000000
Company-Name
Specifies a company name to be associated with this installation. The company
name is included in Event Captures.
Valid Values: A string of 1 to 32 characters. If the name includes embedded blanks,
enclose the name in single quotes.
Default: ' '
Component-DB2
Specifies whether to activate the component CA SYSVIEW for CA Insight DPM for
DB2. The DB2 component requires the product CA Insight DPM for DB2.
Valid Values: Yes, No
Default: No
Component-Health-Check
Specifies whether to activate the CA SYSVIEW Health Check. The Health Check
component is included as a subcomponent of the option CA SYSVIEW for MVS.
Default: No
Component-MIM
Specifies whether to activate the component CA SYSVIEW for CA MIM Resource
Sharing for z/OS. The CA MIM component is included as a subcomponent of the
option CA SYSVIEW for MVS.
Default: No
Component-ROSCOE
Specifies whether to activate the component CA SYSVIEW for CA Roscoe. The CA
Roscoe component is included as a subcomponent of the option CA SYSVIEW for
MVS.
Default: No
Component-USS
Specifies whether to activate CA SYSVIEW for UNIX System Services (USS). The USS
component is included as a subcomponent of the option CA SYSVIEW for MVS.
Default: No
Component-XSYSTEM
Specifies whether to activate the CA SYSVIEW Cross-System component. The cross
system component is included as a subcomponent of the option CA SYSVIEW for
MVS.
Default: No
Dsn-Site-CAPLIB
Specifies the data set name of the site Event Capture library. Members in the Event
Capture library define a list of instructions to process when an Event Capture
occurs.
Valid Values: Any valid data set name.
Default: NONE
Sharing: This data set can be shared with multiple instances of CA SYSVIEW and
across systems.
Security: All users can have read access to the data set but not required. The user
ID assigned to the SYSVIEW User Interfaces address space must have read access to
the data set.
Dsn-Site-CLISTLIB
Specifies the data set name of the site command list library.
Default: NONE
across systems.
Security: All users must have read access to the data set.

Dsn-Site-HELPLIB
Specifies the data set name of the site online help library.
Default: NONE
across systems.
Dsn-Site-MAPLIB
Specifies the data set name of the site MAP library.
Default: NONE
across systems.
Dsn-Site-MIBLIB
Specifies the data set name of the site MIB library.
Default: NONE
across systems.
Dsn-Site-PANELLIB
Specifies the data set name of the site panel library. The panel library contains
MENU definitions for online CA SYSVIEW displays.
Default: NONE
across systems.
Dsn-Site-PARMLIB
Specifies the data set name of the site parameter library.
Default: NONE
across systems.

Dsn-Site-PLOTLIB
Specifies the data set name of the site plot definition library.
Default: NONE
across systems.
Dsn-Site-REXXLIB
Specifies the data set name of the site REXX exec library. This data set contains text
and compiled REXX execs that CA SYSVIEW uses.
This library is dynamically concatenated to the SYSEXEC DD when you log in to the
TSO/ISPF interface.
Default: NONE
across systems.
Dsn-Site-TEMPLATE
Specifies the data set name of the site template library.
Default: NONE
Sharing: This data set can be shared with multiple instances of SYSVIEW and across
systems.
Dsn-System-CAPDATA-HLQ
Specifies the high-level qualifier (HLQ) for the Event Capture library data sets. When
a capture is taken, CA SYSVIEW uses the HLQ to allocate a new data set. A time and
date suffix are added to the HLQ to create the full data set name.
Time and date suffix = Thhmmss.Dyymmdd
Valid Values: Any valid data set name. Limit the HLQ to 28 characters so that the
time and date can be added as a suffix.
Example: SYSVIEW.CAPDATA
Default: NOT.DEFINED.SYSVIEW.CAPDATA
Dsn-System-CAPINDEX

Specifies the name of the Event Capture index data set. A unique data set can be
created for each system, or the index can be shared across systems.
Symbolic substitution variables can be used to make definitions easier.
Examples:
SYSVIEW.CAPINDEX.PROD
SYSVIEW.CAPINDEX.TEST
SYSVIEW.CAPINDEX.&SYSNAME
Default: NOT.DEFINED.SYSVIEW.CAPINDEX.SYSNAME
across systems.
Dsn-System-CAPINDEX-HLQ
Specifies the high-level qualifier (HLQ) for the Event Capture index data sets. The CA
SYSVIEW online commands use the HLQ to reference multiple Event Capture index
data sets.
Example: SYSVIEW.CAPINDEX
Default: NOT.DEFINED.SYSVIEW.CAPINDEX
Dsn-System-CAPLIB
Specifies the data set name of the system Event Capture library. Members in the
Event Capture library define a list of instructions to process when an Event Capture
occurs.
Default: NOT.DEFINED.SYSVIEW.CNM4BCAP
across systems.
Security: All users can have read access to the data set but not required. The user
ID assigned to the SYSVIEW User Interfaces address space must have read access to
the data set.
Dsn-System-CLISTLIB
Specifies the data set name of the command list library.
Default: NOT.DEFINED.SYSVIEW.CNM4BCLS
across systems.
Dsn-System-DATALIB

Specifies the data set name of the persistent data store or data library. This data set
can be reused when migrating or updating CA SYSVIEW releases.
Default: NOT.DEFINED.SYSVIEW.CNM4BDAT
across systems. The data set is allocated as a PDSE and therefore can only be shared
within a single sysplex.
Security: All users must have read access to the data set. The user ID assigned to
the SYSVIEW Main Services address space must have Update access to the data set.
Dsn-System-HELPLIB
Specifies the data set name of the online help library.
Default: NOT.DEFINED.SYSVIEW.CNM4BHLP
across systems.
Dsn-System-MAPLIB
Specifies the data set name of the system MAP library.
Default: NOT.DEFINED.SYSVIEW.CNM4BMAP
across systems.
Dsn-System-MIBLIB
Specifies the data set name of the system MIB library.
Default: NOT.DEFINED.SYSVIEW.CNM4BMIB
across systems.
Dsn-System-PANELLIB
Specifies the data set name of the panel library. The panel library contains MENU
definitions for online CA SYSVIEW displays.
Default: NOT.DEFINED.SYSVIEW.CNM4BPNL

across systems.
Dsn-System-PARMLIB
Specifies the data set name of the parameter library.
Default: NOT.DEFINED.SYSVIEW.CNM4BPRM
across systems.
Dsn-System-PLOTLIB
Specifies the data set name of the plot definition library.
Default: NOT.DEFINED.SYSVIEW.CNM4BPLT
across systems.
Dsn-System-PROFILE
Specifies the data set name of the profile library.
Default: NOT.DEFINED.SYSVIEW.CNM4BPRF
across systems. If profile data set is allocated as a PDS, it can be shared across
multiple sysplexes. If profile data set is allocated as a PDSE, it can only be shared
within a single sysplex.
Security: All users must have read access to the data set. Users can change profile
settings while in an online session. Users must have Update access to the data set
to harden the user settings.
Dsn-System-REXXLIB
Specifies the data set name of the REXX exec library. This data set contains text and
compiled REXX execs that CA SYSVIEW uses.
This library is dynamically concatenated to the SYSEXEC DD when you log in to the
TSO/ISPF interface.
The library is installed as a RECFM=F data set. If your installation uses a RECFM=V
for the SYSEXEC DD, then copy and convert the SYSVIEW REXX library to a RECFM=V
data set.

The compiled REXX execs cannot simply be copied from a RECFM=F to a RECFM=V
data set. They also need converted.
CA SYSVIEW supplies GSVUCFV1 and GSVUCFV2 REXX utility execs to copy and
convert SYSVIEW REXX execs:
GSVUCFV1 uses the ISPF library management services to copy one or more
REXX execs from a RECFM=F to a RECFM=V data set. This exec can also call the
GSVUCFV2 exec to convert any copied complied REXX execs.
GSVUCFV2 uses the ISPF library management services to convert a single
complied REXX exec from a RECFM=F to RECFM=V data set.
CA SYSVIEW supplies to the REXXFTOV job in the SAMPLIB data set to copy and
convert the REXX execs.
The REXXFTOV SAMPLIB JCL member invokes:
1. GSVUCFV1 to copy all REXX execs from a RECFM=F to a RECFM=V data set.
2. GSVUCFV2 to convert any compiled REXX execs that were copied.
The Dsn-System-REXXLIB option must specify the data set name of the converted
RECFM=V data set.
Default: NOT.DEFINED.SYSVIEW.CNM4BREX
across systems.
Dsn-System-SAMPLIB
Specifies the data set name of the sample library.
Default: NOT.DEFINED.SYSVIEW.CNM4BSAM
across systems.
Security: All users can have read access to the data set but not required.
Dsn-System-SECURITY
Specifies the data set name of the security library.
Default: NOT.DEFINED.SYSVIEW.CNM4BSEC
across systems.
Security: All users must have read access to the data set. Administrators need
update access.

Dsn-System-TEMPLATE
Specifies the data set name of the template library.
Default: NOT.DEFINED.SYSVIEW.CNM4BTMP
Sharing: This data set can be shared with multiple instances of SYSVIEW and across
systems.
Dump-Destination
Specifies the output destination that is used when CA SYSVIEW allocates a dump
data set. Specify a value when allocating a dump data set or no destination is used.
Use this parameter option with the parameter Dump-Remote-Userid for routing a
dump to a specific user.
Valid Values: Any valid destination.
Default: None
Dump-Remote-Userid
Specifies the remote user ID that is used when CA SYSVIEW allocates a dump data
set. Supply a value when allocating a dump data set or no remote user ID is used.
Any value that is specified for this parameter is ignored if a value was not also
specified for the parameter Dump-Destination.
Valid Values: Any valid user ID.
Default: None
Dump-SYSOUT-Class
Specifies the SYSOUT class that is used when CA SYSVIEW allocates a dump data set.
User ID is used when allocating a dump data set.
Valid Values: Any valid class.
Default: A
Exit-Module-Command
Specifies the command exit module name.
Valid Values: Any valid member name.
Default: GSVXCMDX
Exit-Module-SDSF
Specifies the SDSF command exit module name.
Default: GSVXSDSX
JES-Name

(Optional) Specifies the default JES subsystem name. If this optional parameter is
not specified, the primary JES subsystem is used. Using CA SYSVIEW with a
secondary JES2 subsystem requires that you code the subsystem name of the
secondary JES2 subsystem for this parameter.
Valid Values: Any valid JES subsystem name.
Default: None
Map-Member-System
Defines the name of the assembled z/OS control block maps member.
Valid Values: Any valid member name that is located in the maps library.
Default: GSVXMAPS
Option-CICS
Specifies whether to activate CA SYSVIEW for CICS.
Default: No
Option-DATACOM
Specifies whether to activate CA SYSVIEW for DATACOM.
Default: No
Option-Event-Capture
Specifies whether to activate CA SYSVIEW Event Capture.
Default: No
Option-MVS
Specifies whether to activate CA SYSVIEW for MVS.
Default: No
Option-IMS
Specifies whether to activate CA SYSVIEW for IMS.
Default: No
Option-TCPIP
Specifies whether to activate CA SYSVIEW for TCP/IP.
Default: No

Option-WebSphereMQ
Specifies whether to activate CA SYSVIEW for WebSphere MQ.
Default: No
Option-CEAPM
Specifies whether to activate CA Cross Enterprise APM.
Default: No
Route-Code
Specifies the console route codes that you use for all WTO and WTOR macros that
CA SYSVIEW issues. The route codes are specified as decimal numbers. The
parameter Route-Code can be specified multiple times when more than one route
code is desired. Each specification contains one route code.
Examples:
Route-Code 2
Route-Code 11
Valid Values: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16

Default: 2, 11
Security-Validation
Specifies how to perform the security verification and validation.
Valid Values:
USER specifies the System Authorization Facility (SAF) to use to validate user
IDs and passwords at session logon to the following interfaces: CICS, VTAM,
and local 3270. For other interfaces such as TSO, ISPF, and CA Roscoe, only the
user ID is validated.
GROUP specifies the assigned group name to the user ID from the external
security product. This group name is used to determine which internal CA
SYSVIEW security group to use. If the user ID belongs to multiple groups, the
default group (DFLTGRP) is used. The GROUP option includes all USER option
functionality.
USERDEF specifies that a user-defined field in the external security product is
used to set the internal CA SYSVIEW security group. For more details, see the
following members in the CNM4BSAM target library:
GSVUDEFA for CA ACF2
GSVUDEFR for RACF
GSVUDEFT for CA TopSecret
The USERDEF option includes all USER option functionality.

NO specifies that user ID validation is not performed when logging on to the

CICS, VTAM, or Local 3270 interface.
Default: USER
SYSOUT-Class
Specifies the default SYSOUT class for dynamically allocated files.
Valid Values: Any valid class
Default: '*'
TCP-SYSTCPD-Dsn
Specifies the name of the system TCP/IP configuration file. This name can be
specified as a Hierarchical File System (HFS) path.
Valid Values: Any valid data set or path name
Default: VTAM.TCPIP.TCPIP.DATA
TCP-SYSTCPD-Member
Specifies the member name that you use (if any) for the TCP/IP data set. This
parameter is required only if the data set specified in the TCP-SYSTCPD-Dsn
parameter is a PDS.
The member parameter supports the use of system symbols. The supplied string for
the TCP-SYSTCPD-Member parameter can be up to 24 bytes long. Anything longer
than 24 bytes is truncated. When the symbols in the string are resolved, the final
member name consists of the first 8 bytes of the TCP-SYSTCPD-Member value.
Anything longer than 8 bytes is truncated and ignored.
Default: None
User-Abend-Code
Specifies the ABEND code that you use for all user abends issued. Unique reason
codes are used to identify the reason for the ABEND.
Valid Values: A number from 0 to 4095
Default: 2999
VTAM-Applid
Specifies the VTAM APPL name that the CA SYSVIEW VTAM interface uses.
Override this parameter with the APPLID parameter of the START command that
starts the CA SYSVIEW VTAM interface.
Valid Values: Any valid application ID name.
Default: None
VTAM-SPO-Applid

Specifies a value that overrides the default VTAM APPL name that the CA SYSVIEW
VTAM command uses. The specified value must be from three to eight characters
long and end with two numeric digits.
If you specify a value for this parameter, change the corresponding APPL names in
the SYSVAPPL member in the sysview.CNM4BSAM data set.
The first name that is coded in the SYSVAPPL member matches the
VTAM-SPO-Applid parameter value. You can specify more APPL names by
incrementing the numeric suffix by one. The numeric suffix does not need to start
at 00, but only numbers that are consecutive with the initial value are used.
Valid Values: Three to eight characters, ending with two numeric digits.
Default: None
Assemble the MVS Control Block Maps (INST0013)

The MAP command of CA SYSVIEW provides a facility to display any system or
user-defined control block in virtual storage. Assemble the control block maps so that
DSECTs or control block structures are created with the software releases you are using.
Follow these steps:

When the job ends with a condition code of 0, the control block maps are assembled
successfully.
Maintenance Considerations When Assembling the Control Block Maps
Consider the following points when you apply the maintenance to your system:
Reassemble the GSVXMAPS object after applying maintenance to z/OS.
Include the SYS1.SMPMTS data set in the SYSLIB concatenation when:
You have applied maintenance to the system that is not accepted.
The current system is running with the maintenance.

Update the JES Configuration Names Table

The JES parmlib member is used to specify the JES subsystems and the associated JES
configuration modules and map module names that CA SYSVIEW uses.
Create a JES configuration module for each system where CA SYSVIEW is used.
To Update the JES Configuration Name Table

1. Access the JES parmlib member in the sysview.CNM4BPRM data set.
The JES parmlib member contains the JES configuration names table.
2. Modify the JES configuration names table in the JES parmlib member by entering
the appropriate information in the supplied table.
The table entries are coded in columns in the following table:
Keyword Column Description

SysName 01-08 Defines the z/OS system name. Specify the
keyword ANY to match any system name.
JES 10-17 Defines the JES subsystem ID.
Module 19-26 Defines the JES configuration module name for
the subsystem.
Maps 28-35 Defines the JES control block maps member.

How the JES Configuration Names Table Works
When a CA SYSVIEW session initializes, it searches the JES parmlib member to find a
matching OS system name in the SysName column. This match to the JES subsystem
provides access to JES-related commands.
Matches are made as follows:

The value for the JES-name parameter that you specified in the System
Configuration Option member is compared with the JES subsystem ID specified in
the JES column.
If it matches, the following actions occur:
1. The JES configuration module is loaded. The module is specified in the Module
column.
2. The JES product level and service level are compared with the product and
service level of the JES subsystem.
If they match, the search is complete.
If they do not match, the search continues for another matching system
name in the SysNames column.
Note: The product and service level are assembled into the JES configuration
module.
A search of the entire JES parmlib member finds a match on the JES product level
but the service levels do not match:
The matching JES configuration module is used and a warning message is
displayed saying the service levels do not match.
The maintenance has been applied.
The JES configuration module must be reassembled.
A match cannot be found for a JES configuration module:
The JES services initialization terminates.
The JES-related commands cannot be used.
You can use the ANY system name to match any system name. However, the JES
configuration module product and service levels must match the running JES
subsystem.
The generic wildcard matching is not performed on any column in the JES parmlib
member.

Naming Conventions for JES Configuration Modules
The following recommended naming conventions are based on either the JES version or
the z/OS SMF ID:
Base the names of the modules and maps on the JES version
Module Name: JESnvrrq
Maps: MAPnvrrq
n
Specifies the JES system. Possible values are:
2 if JES2
3 if JES3
v
Specifies the JES version.
rr
Specifies the JES release.
q
Specifies the qualifier. That is, if a qualifier is needed.
Base the names of the modules and maps on the z/OS SMF ID
Module: JESnsmf
Maps: MAPnsmf
n
Specifies the JES system. Possible values are:
2 if JES2
3 if JES3
smf
Specifies the z/OS SMF ID (up to four characters).

Example: Add Entries to the JES Configuration Names Table.
The following examples use the JES version naming convention.

*....+....1....+....2....+....3....+....4....+....5....+....6....+....7
*=====================================================================*
* System name SY01 is running JES2. *
* The associated JES Configuration module is JES2111. *
* The DSECT maps for JES2 have been assembled into member MAP2111. *
*=====================================================================*
*SysName JES Module Maps
*------- -------- -------- --------
SY01 JES2 JES2111 MAP2111
*=====================================================================*
* System name SY02 is running JES3. *
*=====================================================================*
*------- -------- -------- --------
SY02 JES3 JES3111 MAP3111
*=====================================================================*
* This is a "Catch-All" entry that will match all system names *
* running JES2. *
*=====================================================================*
*------- -------- -------- --------
ANY JES2 JES2109 MAP2109
*=====================================================================*
* This is a "Catch-All" entry that will match all system names *
* running JES3. *
*=====================================================================*
*------- -------- -------- --------
ANY JES3 JES3110 MAP3110

Assemble and Link the JES Configuration Modules (INST0020)

The JES Configuration module contains release specific information about both JES2 and
JES3. This information is used to obtain JES data.
Assemble and link a JES Configuration module for each system where CA SYSVIEW is
used.
The need to run this job multiple times depends on the combination of systems, and
versions of JES2 and JES3. A system with different maintenance levels is considered a
unique or different version.
Follow these steps:

2. Create JES2 and JES3 configuration modules by changing the SET statements.
To create the JES2 Configuration module, change the following SET statements:
SET JES=JES2
SET MODULE=JES2vrrq
To create the JES3 Configuration module, change the following SET statements:
SET JES=JES3
SET MODULE=JES3vrrq
The name that you specified on the SET MODULE= statement must match the name
in the PARMLIB member JES (JES Configuration Names Table).
3. Submit the INST0020 job.
When all steps in the INST0020 job complete with a condition code of 0, the system
has successfully assembled and linked the JES Configuration module.
Note: If any assembly errors occur, contact Technical Support at http://ca.com/support.

To see the lines in error, try specifying LIST=YES on the JOFFT macro in the source
member.
Important! When running this job at a different operating system level than the target
system, modify the SYSLIB concatenation to add volume references to the target
SYSRES.

Maintenance Considerations When Assembling and Linking the JES Configuration Modules
Consider the following steps when applying the maintenance to your system or to the
CA SYSVIEW product.
Reassemble the JES Configuration module after applying maintenance to JES (JES2
or JES3) and when there is a new release of CA SYSVIEW.
Include the SYS1.SMPMTS data set in the SYSLIB concatenation when the following
conditions are true:
Maintenance is applied to the system that is not accepted.
Assemble the JES Control Block Maps (INST0021)

The MAP command of CA SYSVIEW provides a facility to display any system or
user-defined control block in virtual storage. Assemble the control block maps so that
DSECTs or control block structures are created with the software releases you are using.
Follow these steps:

2. Set the MAPIN and MAPOUT values.
To create the JES2 map module, change the following SET statements:
SET MAPIN=JES2MAPS
SET MAPOUT=MAP2vrrq
To create the JES3 map module, change the following SET statements:
SET MAPIN=JES3MAPS
SET MAPOUT=MAP3vrrq
The name that you specified on the SET MAPOUT= statement must match the name
in the PARMLIB member JES (JES Configuration Names Table).
When the job ends with a condition code of 0, the control block maps are
assembled successfully.

Maintenance Considerations When Assembling the Control Block Maps
Consider the following steps when applying the maintenance to your system:
Reassemble the JES map object after applying maintenance to JES (JES2 or JES3).
Include the SYS1.SMPMTS data set in the SYSLIB concatenation when the following
conditions are true:
Maintenance is applied to the system that is not accepted.
Initialize the Event Capture Index Data Set (INST0030)

You initialize the Event Capture index data sets to catalog a list of captured events. The
Event Capture index is used even if the Event Capture option is not available. You can
take and send event captures to CA for diagnostic purposes.
Note: If you are upgrading and reusing the index data set from the prior release, you
can skip this step.
A common or shared index data set can be used for all systems when the data set is
allocated on shared DASD. A separate index data set can also be used for each system.
This index file is defined as a VSAM KSDS (key-sequenced data set). If separate index
data sets are used, the high-level qualifier you specified for the index data sets must
contain the system name. Specify the system name using the &SYSNAME symbolic
parameter.
Follow these steps:

When the job ends with a condition code of 0, the Event Capture index data sets
are successfully initialized.

Define and Load the IMOD Data Set (INST0031 - INST0032)

The source members that are used for the information modules (IMODs) are distributed
in the PDS data set sysview.CNM4BISR. The IMOD source members are loaded and
compiled into a CA GSS IMODLIB VSAM data set.
Follow these steps:

1. Modify the JCL in the INST0031 and INST0032 members of the sysview.SAMPJCL
data set.
This job defines the IMOD VSAM data set.
This job performs the following functions:
a. Loads the source IMOD REXX EXECs from the source IMOD PDS into the VSAM
IMOD data set.
b. Compiles the IMODs in the VSAM data set.
Define Log Streams (INST0040 - INST0046)

Note: If you are upgrading and already have the log streams defined, you can reuse
those log streams.
Note: For information about log stream size, see the Administration Guide.
Log streams must be defined before you can view the following types of collected data
online:
Historical Audit Event data records
Historical Plot data records
Monitored data records
Exception Records
Note: Before you run INST0040 through INST0046, activate the z/OS system logger
services and define a LOGR policy on the system.

Follow these steps:

1. Review the INST0040 through INST0046 members in the sysview.SAMPJCL data set
to ensure all of the files that the jobs are referencing are correct.
2. Define the log stream as shown in the following sample definition. The JCL defines a
DASD-only log stream and lists the characteristics of the log stream:
//INST004* JOB (09900000),'PROGRAMMER NAME',
REGION=0M,
MSGCLASS=A,
CLASS=A,
MSGLEVEL=(1,1)
//DEFINE EXEC PGM=IXCMIAPU,REGION=0M

//SYSIN DD *
DATA TYPE(LOGR) REPORT(NO)
DEFINE LOGSTREAM
NAME(ssidrrm.taskname.type.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(....16chars.....)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(7)
STG_SIZE(750)
LIST LOGSTREAM
NAME(ssidrrm.taskname.type.smfi)
DETAIL(YES)
3. Submit the appropriate jobs that define the z/OS log streams needed on each
system.
After the job ends with a condition code of 0, you can view the log streams online.
The records that are written to these log streams are in SMF format.

Log Stream Guidelines
Defining log streams requires that you follow these guidelines:

SMS must manage your log stream data sets.
The SMS data class must support data compression.
Observe the log stream naming conventions.
Note: If you are upgrading and already have log streams defined, you can reuse
those log streams.
Use the available log data types.
The available log data types are as follows:
ADTT
Indicates Audit Event records
IMRS
Indicates IMS region summary records
IMTR
Indicates IMS transaction records
MQHR
Indicates MQ historic requests
PLOT
Indicates historical plot records
SMFD
Indicates SMF data records
TRAN
Indicates CICS detailed transaction records
TSUM
Indicates CICS transaction summary records
SYSD
Indicates CICS system interval data records
XLOG
Indicates exception records for all components
Note: Although multiple log data types can share a log stream, we do not
recommend sharing log streams that contain the SMFD and TRAN data types. The
volume of data records being written to these logs is much greater than the volume
being written to the other types.

Observe the LOGSTREAM description.

The LOGSTREAM description is 16 characters and cannot contain blanks.
Log Stream Naming Conventions
Log stream naming conventions let you define log streams for online viewing.
Note: The parmlib members for specifying log stream names are located in the
sysview.CNM4BPRM data set.
We suggest the following naming convention, which adheres to the 26-character

restriction:
ssidrrm.taskname.type.smfi
ssid
Specifies the SYSVIEW subsystem ID
rrm.
Specifies the release number plus separator character
taskname.
Specifies the owning SYSVIEW task plus separator character
type.
Specifies the log data type qualifier plus separator character
smfi
Specifies the SMF ID
Limits: 26 characters for the log stream name; the name must be unique across a
SYSPLEX. (Any naming convention that provides a unique log stream name across the
SYSPLEX is acceptable.)
Example: Log Stream Naming Convention
The following table shows examples of the suggested naming convention for the log
stream name:
Taskname.Type Log Stream Name

AUDIT.ADTT GSVX130.AUDIT.ADTT.smfid
IMSLOGR.IMRS GSVX130.IMSLOGR.IMRS.smfid
IMSLOGR.IMTR GSVX130.IMSLOGR.IMTR.smfid
MQSDATA.MQHR GSVX130.MQSDATA.MQHR.smfid

Taskname.Type Log Stream Name

SMFDATA.PLOT GSVX130.SYSDATA.PLOT.smfid
SYSDATA.SMFD GSVX130.SMFDATA.SMFD.smfid
SYSDATA.XLOG GSVX130.SMFDATA.XLOG.smfid
CICSLOGR.TRAN GSVX130.CICSLOGR.TRAN.smfid
CICSLOGR.TSUM GSVX130.CICSLOGR.TSUM.smfid
CICSLOGR.SYSD GSVX130.CICSLOGR.SYSD.smfid
CICSLOGR.XLOG GSVX130.CICSLOGR.XLOG.smfid
Step 1: Define a Log Stream for Audit Events (INST0040)
This step defines a set of log streams to contain historical audit event data records.
A unique log stream must be created for each audit event data record that has been
defined on each system.
Follow these steps:

1. Specify the log stream as shown in the example that follows this procedure.
2. Specify the name of the defined log stream in the following parmlib members:
AUDIT
LOGSTREAM-AUDIT-NAME logstream.name
If the audit logging function is not going to be used or the log stream has not
been defined, set the following options:
LOGSTREAM-AUDIT-NAME NONE
LGLOOKUP
Sysname Logname......LogStream-Name
sysname AUDIT logstream.name
The log stream for the historical audit event data records is defined, and the contents of
the log stream can be viewed online.

Example: Define a DASD-Only Audit Log Stream.
This example defines a DASD-only audit log stream for collecting historical audit event
data records:

DEFINE LOGSTREAM
NAME(GSVX130.AUDIT.ADTT.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(AUDIT_LOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(5000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(7)
STG_SIZE(3500)
View Log Stream Online for Audit Events
After you have defined the log stream containing records created by the audit events
data loggers, you can view the log stream online.
Use the following command to view the log stream:

AUDITLOG
Displays the audit event data collection logs.
The log stream is displayed for viewing.

Step 2: Define a Log Stream for Historical Plot Data Records (INST0041)
To view online historical plot data records created by the data collectors, define a log
stream that contains those records.
Create a unique log stream on each system.
Follow these steps:

SYSDATA
LOGSTREAM-PLOTLOG-NAME logstream.name
If the plot logging function is not going to be used or the log stream has not
LOG-PLOT-RECORDS NO
LOGSTREAM-PLOTLOG-NAME NONE
LGLOOKUP
Sysname Logname......LogStream-Name
sysname PLOTLOG logstream.name

The log stream for the historical plot data records is defined, and the contents of
the log stream can be viewed online.

Example: Define a DASD-Only Log Stream
This example defines a DASD-only log stream for collecting historical plot data records:

DEFINE LOGSTREAM
NAME(GSVX130.SYSDATA.PLOT.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(PLOT_LOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(30)
STG_SIZE(750)
View Historical Plot Data Records Online
After you have defined the log stream containing historical plot data records created by
the data collectors, you can view the log stream online.
Use the following commands to view the log stream:

LGLOGS
Displays the data collection logs.
PLOTLOG
Displays the historical plot log.
Step 3: Define a Log Stream for XLOG Log Stream (INST0042)
This step defines a log stream to contain the exception records that the following data
collectors create:
IMS
MVS
TCP/IP
WebSphere MQ

A unique log stream must be created on each system.
Follow these steps:

2. Specify the name of the log stream that this step defines in the following parmlib
members:
SYSDATA:
LOGSTREAM-XLOG-NAME logstream.name
If the exception records are not going to be used or the log stream has not
LOG-XLOG-RECORDS NO
LOGSTREAM-XLOG-NAME NONE
LGLOOKUP:
Sysname Logname......LogStream-Name..
sysname XLOG logstream.name
3. Submit the INST0042 JOB.

The log stream for the XLOG state exception records is defined.
Example: Define the XLOG Log Stream
This example defines an XLOG log stream for collecting exception records.

DEFINE LOGSTREAM
NAME(GSVX130.SYSDATA.XLOG.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(XLOG_LOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1500)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(14)
STG_SIZE(1000)

View XLOG State Exception Data Records Online
After you have defined the log stream containing XLOG state exception records, you can
view the collected data online.

LGLOGS
Displays data collection logs specified in parmlib member LGLOOKUP.
XLOG
Displays threshold and state exception records for all CA SYSVIEW components.
Step 4: (Optional) Define a Log Stream in Event Capture Option (INST0043)
This step is required only if you are running the CA SYSVIEW Event Capture Option.
Define a log stream that contains the SMF records that the SMFDATA task collected.
SMF data collection is a component of the CA SYSVIEW Event Capture Option.
Note: For more information about the SMF Event Capture setup, see the chapter
"Starting the Subtasks" in the Administration Guide.
A unique log stream must be created on each system.
Follow these steps:

1. Specify the log stream as shown in the Define a DASD-Only Log Stream example
that follows this procedure.
SMFDATA
LOGSTREAM-SMFDATA-NAME logstream.name
If the SMF logging function is not going to be used or the log stream has not
LOGSTREAM-SMFDATA-NAME NONE
In addition, do not start the SMFDATA task in the SYSVIEW parmlib member.
LGLOOKUP
Sysname Logname...... LogStream-Name
sysname SMFDATA logstream.name


The log stream for the Event Capture Option is defined, and the collected data can
be viewed online.
Example: Define a DASD-Only Log Stream
This example shows a DASD-only log stream:
DEFINE LOGSTREAM
NAME(GSVX130.SMFDATA.SMFD.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(SMF_LOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(15000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(5)
STG_SIZE(10000)
View Log Stream Online for Event Capture Option
After you have defined the log stream containing SMF records collected by the
SMFDATA task, you can view the log stream online.

LGLOGS
Displays the data collection logs
SMFLOG
Displays the SMF logs

Step 5: (Optional) Define a Set of Log Streams for CICS Option (INST0044)
This step is required only if you are running the CA SYSVIEW Option for CICS.
This step defines a set of log streams to contain records that the CICS data collectors
created.
The CICS data collectors route the records through a specified CICS logger running in the
CA SYSVIEW main address space. Multiple CICS loggers can be defined.
A unique log stream must be created for each CICS logger that has been defined on each
system.
Follow these steps:

1. Specify the log streams as shown in the examples that follow this procedure. You
can define 1- to 4-log streams.
The suggested naming convention for the log stream is as follows:
ssidrrm.cicslogr.TRAN.smfi
ssidrrm.cicslogr.TSUM.smfi
ssidrrm.cicslogr.SYSD.smfi
ssidrrm.cicslogr.XLOG.smfi
ssid
Specifies the CA SYSVIEW subsystem ID
rrm
Specifies the release number
cicslogr
Names the CICS logger
smfi
The log data types are as follows:
TRAN
Specifies the CICS transaction log
TSUM
Specifies the CICS transaction summary
SYSD
Specifies the CICS system data

XLOG
Specifies the CICS exception log
Important! Multiple log data types can share a log stream. Sharing the log stream
that is defined to contain the CICS transaction log record is not recommended. The
volume of data in this log is much greater than other log types.
2. Specify the name of the log stream that is defined in this step in the following
parmlib members:
CICSLOGR
Provides default configuration options for the CICS Data Logger function.
If a log stream is not going to be used or has not been defined, set the
appropriate option value to NONE.
LOGSTREAM-CICSTRAN-NAME NONE
LOGSTREAM-CICSTSUM-NAME NONE
LOGSTREAM-CICSSYSD-NAME NONE
LOGSTREAM-CICSXLOG-NAME NONE
LGLOOKUP
Associates a log name that is defined in this member with a log stream name.
Sysname Logname......... LogStream-Name
Sysname CICSLOGR.TRAN... logstream.name
Sysname CICSLOGR.TSUM... logstream.name
Sysname CICSLOGR.SYSD... logstream.name
Sysname CICSLOGR.XLOG... logstream.name

The log streams for the CICS option are defined, and the contents of CA SYSVIEW
maintained log streams can be viewed online.

Example: Define a TRAN Log Stream
This example shows a CICS transaction log stream:
DEFINE LOGSTREAM
NAME(GSVX130.CICSLOGR.TRAN.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(CICS_TRANLOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(20000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(5)
STG_SIZE(15000)
Example: Define a TRANSUMM Log Stream
This example shows a CICS transaction summary log stream:
DEFINE LOGSTREAM
NAME(GSVX130.CICSLOGR.TSUM.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(CICS_TRANSUMM)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(30)
STG_SIZE(750)

Example: Define a SYSD Log Stream
This example shows a CICS data log stream:
DEFINE LOGSTREAM
NAME(GSVX130.CICSLOGR.SYSD.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(CICS_SYSDATA)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(90)
STG_SIZE(750)
Example: Define an XLOG Log Stream
This example shows a CICS exception log stream:
DEFINE LOGSTREAM
NAME(GSVX130.CICSLOGR.XLOG.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(CICS_XLOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(30)
STG_SIZE(750)

View Log Streams Online for CICS Option
After you have defined the log streams containing records created by the CICS data
collectors, you can view the log streams online.
Use the following commands to view the log streams:

CSYSDATA
Displays the CICS system interval analysis
CTRANLOG
Displays the CICS transaction log summary
CTRANSUM
Displays the CICS transaction intervals
LGLOGS
XLOG
Displays the CICS exception log
The log streams are displayed for viewing.
Step 6: (Optional) Define a Log Stream for IMS Option (INST0045)
This step is required only if you are running the CA SYSVIEW Option for IMS.
This step defines a set of log streams to contain records the IMS transaction data
loggers created.
The IMS transaction data loggers create records that are logged through a task running
in the CA SYSVIEW main address space. When multiple IMS loggers are running, each
logger can share a specific log stream or can define a specific log stream for its use.
Note: Multiple loggers and types can share a log stream. However, sharing the log
stream containing IMS transaction log records is not recommended. The volume of data
in this log is greater than in other log types.

Follow these steps:

1. Specify a log stream as shown in the examples that follow this procedure.
The following naming convention for the log stream is suggested:
ssidrrm.IMSLOGR.IMRS.smfi
ssidrrm.IMSLOGR.IMTR.smfi
or
ssidrrm.IMSssid.IMRS.smfi
ssidrrm.IMSssid.IMTR.smfi
ssid
Specifies the SYSVIEW subsystem ID
rrm
Specifies the release number
IMS
Specifies the IMS logger name
ssid
Specifies the IMS subsystem
IMRS
Specifies the log data type for the IMS region summary records
IMTR
Specifies the log data type for the IMS transactions
smfi
IMSLOGR
Provides default configuration options for the IMS Data Logger function.
LOGSTREAM-IMSREGN-NAME logstream.name
LOGSTREAM-IMSTRAN-NAME logstream.name
If a log stream is not going to be used or has not been defined, set the
appropriate option value to NONE.
LOGSTREAM-IMSREGN-NAME NONE
LOGSTREAM-IMSTRAN-NAME NONE

LGLOOKUP
Sysname Logname......... LogStream-Name
Sysname IMSLOGR.IMRS logstream.name
Sysname IMSLOGR.IMTR logstream.name
or
Sysname IMSssid.IMRS logstream.name
Sysname IMSssid.IMTR logstream.name

The log stream for the IMS option is defined, and the collected data can be viewed
online.
Example: Define an IMRS Log Stream
This example shows an IMS region summary data log stream:

DEFINE LOGSTREAM
NAME(GSVX130.IMSLOGR.IMRS.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(IMS_RSUMLOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(14)
STG_SIZE(750)

Example: Define an IMTR Log Stream
This example shows an IMS transaction data log stream:

DEFINE LOGSTREAM
NAME(GSVX130.IMSLOGR.IMTR.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(IMS_TRANLOG)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(5000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(5)
STG_SIZE(4000)
View Log Stream Online for IMS Option
After you have defined the log stream containing records created by the IMS data
loggers, you can view the log stream online.

LGLOGS
IMSRSLOG
Displays the collection data online
IMSTLOG
Displays the IMST log

Step 7: (Optional) Define a Log Stream for WebSphere MQ Option (INST0046)
This step is required only if you are running the CA SYSVIEW Option for WebSphere MQ.
This step defines a log stream to contain the WebSphere MQ data collector created
records. A unique log stream must be created on each system.
Follow these steps:

2. Specify the name of the log stream that this step defined in the following parmlib
members:
MQSDATA
Provides default configuration options for the WebSphere MQ Data Collector
function.
LOGSTREAM-MQSDATA-NAME logstream.name
If the logging function is not going to be used or the log stream has not been
defined, set the following option:
LOGSTREAM-MQSDATA-NAME NONE
LGLOOKUP
Sysname Logname.......LogStream-Name
Sysname MQSDATA.MQHR logstream.name

The log stream for WebSphere MQ Option is defined and the collected data can be
viewed online.

Example: Define an MQHR Log Stream
This example shows an MQ log stream:
//MQS EXEC PGM=IXCMIAPU,REGION=0M

//SYSIN DD *
DEFINE LOGSTREAM
NAME(GSVX130.MQSDATA.MQHR.smfi)
AUTODELETE(YES)
DASDONLY(YES)
DESCRIPTION(MQS_MQHR)
DIAG(NO)
EHLQ(LOGGER)
HIGHOFFLOAD(70)
LOWOFFLOAD(0)
LS_SIZE(1000)
MAXBUFSIZE(32767)
MODEL(NO)
OFFLOADRECALL(YES)
RETPD(5)
STG_SIZE(750)
View Log Stream Online for CA SYSVIEW Option for WebSphere MQ
After you have defined the log stream containing records created by the CA SYSVIEW
Option for WebSphere MQ data collector, you can view the log stream online.

LGLOGS
Displays the data collection logs.
MQRLOG
Displays the MQR log.

Convert the Security Data Set (INST0050)

If you are installing CA SYSVIEW for the first time, skip this step. If CA SYSVIEW is already
installed, complete this installation step to convert your existing security data set to the
new format for this release.
Follow these steps:

1. Modify the JCL in the INST0050 member, which is in the sysview.SAMPJCL data set.
2. Edit the SYSUT1 DD statement to specify the existing security data set.
4. Update the security authorization for all new command and display fields after you
initialize the CA SYSVIEW product.
Note: For more information, see the Security Guide.
When the job ends with a condition code of 0, the security data set successfully
converted to the new format.
Important: Executing this job to convert your existing security file marks the security
authorization as FAILED for all new commands in this release.
JCL Statements (INST0050)
The following ddnames and descriptions are in the JCL for the GSVXCNVS program:
STEPLIB
Points to the new CA SYSVIEW load library.
SYSPRINT
Displays messages produced by the conversion process.
SYSUT1
Points to the security data set used with the previous release of CA SYSVIEW. This
data set is input to the conversion process and is not modified.
SYSUT2
Points to the security data set to be used with the new release of CA SYSVIEW. This
data set is the output from the conversion process and is modified. This data set
name should match the data set name specified on the Dsn-System-SECURITY
parameter of the System Configuration Options member.

Condition Codes
INST0050 and INST0051 convert an existing data set to the new format. Job INST0050
converts the security data set; job INST0051 converts the profile data set. Either job can
return the following condition codes:
0
The conversion process completed successfully.
4
The GETMAIN for the initial work area failed. Increase the region size of the job.
8
The GSVXCOMM module could not be loaded. Review the job log for the reason the
load failed.
12
The GSVXNUC module could not be loaded. Review the job log for the reason the
load failed.
16
An error occurred during initialization processing. Review the output from the
SYSPRINT DD statement for the reason initialization failed.
20
The Open for the SYSUT1 DD statement failed. Be sure that the SYSUT1 DD
statement is specified in the JCL.
24
A Write to the SYSPRINT DD statement failed. Be sure that the SYSPRINT DD
28
The profile data set release is not supported. The data set supplied with the SYSUT1
DD statement is for a release that is no longer supported. Contact Technical
Support at http://ca.com/support.

Convert the Profile Data Set (INST0051)

If CA SYSVIEW is already installed, complete this step to convert your existing profile
data set to the new format.
If you are installing CA SYSVIEW for the first time, skip this step.
Note: When someone is using the new release of CA SYSVIEW during the profile
conversion process, the profile of that user is not converted.
Follow these steps:

1. Modify the JCL in the INST0051 member, which is in the sysview.SAMPJCL data set.
2. Edit the SYSUT1 DD statement by providing the existing profile data set used with
the previous release in the SET OLD= parameter.
The SET NEW= parameter is filled in for you with new profile data set to be used
with this new release. You can modify this value.
Example: Data set variable names
SET OLD='old.profile.dataset'
SET NEW='new.profile.dataset'
OLD
Specifies the data set name of the existing profile to convert.
NEW
Specifies the data set name of the new profile data set that was distributed
with the new release.
3. Submit the INST0051 member.
The job converts the existing profile data set to the current release using the
following two steps:
a. Initializes the new or output profile data set with members from the
distribution profile.
b. Converts the profile data set from a prior release into the new profile data set.
The profile data set is converted.
More information
JCL Statements (INST0051) (see page 142)

JCL Statements (INST0051)
The following ddnames and descriptions are in the JCL for the GSVXPROC program:
STEPLIB
Points to the new CA SYSVIEW load library.
SYSPRINT
Displays messages produced by the conversion process.
SYSUT1
Points to the profile data set used with the previous release of CA SYSVIEW. This
data set is input to the conversion process and is not modified.
SYSUT2
Points to the profile data set to be used with the new release of CA SYSVIEW. This
data set is the output from the conversion process and is modified. This data set
name should match the data set name specified on the Dsn-System-PROFILE
parameter of the System Configuration Options member.
Condition Codes
INST0050 and INST0051 convert an existing data set to the new format. Job INST0050
converts the security data set; job INST0051 converts the profile data set. Either job can
return the following condition codes:
0
The conversion process completed successfully.
4
The GETMAIN for the initial work area failed. Increase the region size of the job.
8
The GSVXCOMM module could not be loaded. Review the job log for the reason the
load failed.
12
The GSVXNUC module could not be loaded. Review the job log for the reason the
load failed.
16
An error occurred during initialization processing. Review the output from the
SYSPRINT DD statement for the reason initialization failed.
20
The Open for the SYSUT1 DD statement failed. Be sure that the SYSUT1 DD

24
A Write to the SYSPRINT DD statement failed. Be sure that the SYSPRINT DD
28
The profile data set release is not supported. The data set supplied with the SYSUT1
DD statement is for a release that is no longer supported. Contact Technical
Support at http://ca.com/support.
Update the CICS Tables (INST0060)

Complete the following steps to update your CICS tables:
Step 1: Define Program and Transaction Entries
Step 2: Add Entries to the PLTPI
Step 3: (Optional) Add Entries to the PLTSD
Step 4: Start the CICS Data Collector Automatically
Step 1: Define Program, Transaction, and Library Entries
Define program and transaction entries by updating the CICS tables.
Before you begin defining program and transaction entries, be sure that the following
assigned values meet your site requirements:
The input statements to the CICS system definition file utility program DFHCSDUP:
sysview.CNM4BSAM(CICSCSD)
The sample JCL for the system definition file utility program in the member CSDUTIL
of SAMPLIB (after job INST0110 is executed, which involves copying installation
members to a sample library (see page 150))
Follow these steps:

1. Modify the INST0060 member in the sysview.SAMPJCL data set to the standards of
your site.
When the job ends with a condition code of 0, the following CICS transactions have
been defined:
Transaction Use
GSVS Starts the CICS Data Collector manually.
This transaction requires the CA SYSVIEW Option for CICS.

Transaction Use
GSVT Terminates the CICS Data Collector manually.
GSVI Identifies the CICS Data Collector that uses this transaction as an
internal transaction to the function requests. The transaction
cannot be executed directly. It is started internally by the GSVS
transaction.
SYSV Identifies the CA SYSVIEW online interface.
This transaction does not require the CA SYSVIEW Option for
CICS.
Note: For more information about the CICS system definition file utility program, see
the IBM CICS Resource Definition Guide or the IBM CICS Operations and Utilities Guide.
CICS Dynamic Library Definition
Starting at CICS TS 3.2, CICS provides the ability to use a dynamic library definition to
dynamically allocate and concatenate the load library data sets to the ddname DFHRPL.
You can dynamically add definitions to the CICS CSD file using the CICS DFHCSDUP
utility.
The following sample definition, which is available in the CICSCSD member of the
sample library (CNM4BSAM) data set, defines the CA SYSVIEW loadlib data set:
DEFINE LIBRARY(SYSVIEW)
RANKING(50)
CRITICAL(NO)
STATUS(ENABLED)
DSNAME01(sysview.CNM4BLOD)
GROUP(SYSVIEW)
CA SYSVIEW no longer requires any JCL updates to a CICS job stream. You can perform
installation and maintenance to an active CICS region.
All data set allocation is performed dynamically. The CA SYSVIEW loadlib

(sysview.CNM4BLOD) must be accessible through STEPLIB or link list. If the loadlib is in
the link list, then no JCL changes are required.

Step 2: Add Entries to the PLTPI
Update the CICS tables by adding entries to the PLTPI.
Follow these steps:
Note: If you do not use a PLTPI table, skip this step.

1. Change the PLTPI for each CICS system being monitored.
2. If you are using a PLTPI table, add the following entry to the table:
DFHPLT TYPE=ENTRY,PROGRAM=GSVCGSVS
The entry is added to the PLTPI.
Example: PLTPI (initialization) module

DFHPLT TYPE=INITIAL,SUFFIX=PI
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
DFHPLT TYPE=ENTRY,PROGRAM=GSVCGSVS
DFHPLT TYPE=FINAL
END DFHPLTBA

Step 3: (Optional) Add Entries to the PLTSD
You control termination by the placement of the termination program GSVCGSVT for CA
SYSVIEW for CICS within the CICS PLTSD shutdown module.
Adding the GSVCGSVT entry to the PLTSD is optional. By default, the data collector for
CA SYSVIEW for CICS terminates during the Stage 2 portion of a normal CICS shutdown.
Follow these steps:
The options for entries to add to the PLTSD are shown in the samples that follow:
Request STAGE 1 shutdown:
Add GSVCGSVT before DFHDELIM entry.
Request STAGE 2 shutdown:
Add GSVCGSVT after DFHDELIM entry.
The chosen entry is added to the PLTSD.
Example: PLT - Stage 2 Shutdown
PRINT GEN
DFHPLT TYPE=INITIAL,SUFFIX=SD
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
DFHPLT TYPE=ENTRY,PROGRAM=GSVCGSVT
DFHPLT TYPE=FINAL
END DFHPLTBA
Step 4: Start the CICS Data Collector Automatically
A post-initialization table that overrides the default system initialization table (SIT) is
required if you want to start the CICS Data Collector automatically during CICS
initialization. The post-initialization table name is DFHPLTxx, where xx is the suffix
specified by the SIT parameter PLTPI.
To have CICS use the DFHPLTPI table during post-initialization processing, code PLTPI=PI
in the SIT. Code for DFHPLTPI has been supplied in the SAMPLIB member CICSPLT.
Note: If you are not currently using a PLTPI table, you can obtain one by specifying
PLTPI=PI in the SIT override.

CICS Data Collection Start Modes
The CA SYSVIEW for the CICS data collector requires the configuration information
during the initialization. The original or initial configuration definitions are stored in
various PARMLIB members.
During the termination of the CICS data collector, configuration information is saved.
The configuration information can then be persistent.
The initial or startup configurations are always obtained from the PARMLIB member
CICSOPTS.
You can specify the following start modes:

COLD
Retrieves the configuration information from the PARMLIB member. Configuration
data from the previous session is not restored.
WARM
Retrieves the configuration information from the persistent data store.
Configuration data from the previous session is restored.
If the object does not exist, the data is retrieved from the associated PARMLIB
member.
How to Specify the Start Mode
You can specify the start mode using two methods. Use the following matrix to help you
understand the resulting mode when more than one method is used simultaneously.
Define a CICS System Initialization Table (SIT) INITPARM for the program GSVCGSVS
by adding the following SIT parameter:
INITPARM=(GSVCGSVS='GSVI=tran,USERID=userid,START=start,SSID=ssid')
tran
Specifies the transaction that was defined with the initial program GSVCGSVI.
By Default, the transaction ID is GSVI. Specifying an asterisk (*) causes the use
of the transaction ID GSVI.
userid
Specifies the user ID to be associated with the GSVI transaction. Specifying an
asterisk (*) causes the transaction ID GSVI to start without a specific user ID.

start
Specifies the start type for the CICS data collector.
Valid Values:
Asterisk (*) indicates a warm start.
WARM indicates a warm start.
COLD indicates a cold start.
ssid
Specifies the subsystem ID that the initial program GSVCGSVI connects to.
Specifying an asterisk (*) causes the use of the default subsystem ID defined in
module GSVBSSID.
Manually enter the start mode as a parameter to the start transaction GSVS as
follows:
Syntax:
GSVS <START=mode>
mode
* | WARM | COLD
Start Mode Matrix Table
The following table shows how the start mode specified using the CICS SIT INITPARM
and GSVS START= affects the resulting start mode.
CICS SIT INITPARM GSVS START= Resulting Mode
none none WARM
none * WARM
none COLD COLD
none WARM WARM
* none WARM
* * WARM
* COLD COLD
** WARM WARM
COLD none COLD
COLD * WARM
COLD COLD COLD
COLD WARM WARM

WARM none WARM

WARM * WARM
WARM COLD COLD
WARM WARM WARM
Link Edit the CICS Object Members (INST0061)

This step link edits your CICS object members. The link edit creates a load module for
formatting CICS internal trace table entries that display when you issue the CTRACE
command.
Note: If multiple releases of CICS are in use, specify the library using the highest
available CICS release.
Follow these steps:

1. Modify the SYSLIB DD statement in the INST0061 member of the sysview.SAMPJCL
data set to use the correct CICS library.
A sample SYSLIB DD statement follows:
//SYSLIB DD DSN=cics.ADFHMOD

When the job ends with a condition code of 0, the link edit of the CICS object
members completed.

Update the CICS JCL

Enable the CICS Data Collector and online interface by updating the CICS JCL. Sample JCL
is found in sysview.SAMPJCL(CICSJCL). Perform this procedure for each CICS system
being monitored.
Follow these steps:

1. Add a DD statement for the load library to your CICS job stream DFHRPL and
STEPLIB DD statements, as shown:
//STEPLIB DD DSN=...
// DD DSN=sysview.CNM4BLOD
//DFHRPL DD DSN=...
// DD DSN=sysview.CNM4BLOD
Note: Replace the high-level qualifier with the one you assigned to the CA SYSVIEW
load library.
2. Make the CNM4BLOD data set accessible through the STEPLIB DDname or the
linklist.
Starting at CICS TS 3.2, CICS provides Dynamic Program Library Management. The
CNM4BLOD data set can be dynamically added to CICS and made accessible using a
LIBRARY resource definition. This step can be done in place of adding the data set
DFHRPL ddname.
The CICS JCL is now updated for each CICS system being monitored.
Copy the Installation Members to a Sample Library (INST0110)

The created and used jobs during the installation are copied to the sysview.CNM4BSAM
data set. To run one of these jobs in the future, use the copy in the SAMPLIB data set to
avoid altering the original installation jobs.
Follow these steps:

1. Review the INST0110 member in the sysview.CNM4BSAM data set to ensure all of
the files that are referenced in the job are correct.
When the job ends with a condition code of 0, the members reside in the sample
library.

Assemble and Link the Default SSID (USRM0001)
Assemble and Link the Default SSID (USRM0001)

CA SYSVIEW requires a Subsystem Identifier (SSID) to determine which System
Configuration Options member to use from the System PARMLIB. If you are using the
default SSID of GSVX, then the USERMOD is not required.
If you are not using the default SSID of GSVX, review these steps.
Follow these steps:

1. Review the sample JCL in USRM0001.
2. Submit member USRM0001.
a. The sample JCL creates the SMP/E USERMOD.
b. The SMP/E USERMOD assembles and links the default SSID into the load
module GSVBSSID.
Prepare to Start Your Product

When the following procedures are complete, the subsystem and APF load libraries are
installed; CA SYSVIEW is installed on your system after the IPL completes.
Increase ASIDs (Optional)

When the CA SYSVIEW main address space is stopped multiple times, and you are not
using ASID reuse:
You can run out of address space identifiers (ASIDs).
You would need to IPL your system to obtain additional ASIDs.
To avoid having to IPL your system, use the following procedure to increase the number
of ASIDs.
Follow these steps:

1. Access the RSVNONR in the member IEASYSxx of SYS1.PARMLIB.
2. Increase the RSVNONR size to accommodate the number of times you could start
and stop address spaces that define a system linkage index (System LX) within the
life of an IPL.
Note: When you run out of ASIDs, messages alert you of the failed address space
creation and to IPL to obtain additional ASIDs.

System Linkage Index and ASID Reuse

System Linkage Index
A linkage index is reserved as a reusable System LX when the ASN and LX reuse
facility is installed.
If the ASN and LX reuse facility is installed, the reusable System LX can be reserved.
When the SYSVIEW Main Address Space is stopped, the system can reuse the
System LX.
If the ASN and LX reuse facility is not installed and the SYSVIEW Main Address Space
stops, the System LX becomes dormant. When the SYSVIEW Main Address Space is
restarted, CA SYSVIEW reclaims the previously used System LX.
Note: Parameter NSYSLX specifies the number of linkage indexes, LXs, to be
reserved. However, because the product reuses the System LX, you do not need to
increase this number.
Reusable ASIDs
When the SYSVIEW Main Address Space is terminated, the ASID can become
unavailable for use due to a System LX being reserved. The ASID can be reused
when all the following conditions are true:
1. ASN and LX reuse facility is installed.
2. REUSASID(YES) is specified in the DIAGxx member of the SYS1.PARMLIB.
3. The SYSVIEW Main Address Space started task is started with the parameter
REUSASID=YES:
S SYSVIEW,REUSASID=YES
4. The WebSphere MQ data collection task, MQSDATA, uses the WebSphere MQ

MQI to gather MQ performance data.
WebSphere MQ does not support address spaces that are started in the
SYSVIEW Main Address Space with REUSASID=YES. Using this method causes an
abend with an S0D3 abend code.
5. The IMS Common Queue Server task, IMSCQS, uses the IMS Common Queue
Server APIs to gather IMS Shared Message Queue performance data.
The IMS CQS address space APIs do not support clients that are started in the
SYSVIEW Main Address Space with REUSASID=YES. Using this method causes an
abend with an S0D3 abend code.

APF-Authorize the Load Library

Authorize the load library to make it available.
Follow these steps:
Add the following command to the PROGxx member in SYS1.PARMLIB:
APF ADD DSNAME(sysview.CNM4BLOD) VOLUME(volume)
After you add the DSNAME and VOLUME to the PROGxx member, the load library is
APF-authorized. If the runtime load library is SMS managed, use 'xxxxxx' for volume.
Set Up the LOGR Exit and Linklist

The provided LOGR subsystem exit lets you use any z/OS log stream as an input file to a
batch program. The LOGR subsystem exit must reside in a linklist data set.
Follow these steps:

If you have defined the data set sysview.CNM4BLOD to the linklist, no other steps
are required.
If you have not defined the data set sysview.CNM4BLOD to the linklist, copy the
following modules to an existing linklist data set:
GSVXLGEX
GSVXLGXG (alias of GSVXLGEX)
After the modules are copied, the LOGR subsystem exit resides in a linklist data set.
Add Startup Procedure to System Procedure Library

Note: If you configured CA SYSVIEW using MSM, the system procedures were already
copied to the library specified during the configuration.
Update the startup procedures and add them to one of the system procedure libraries.
The CA SYSVIEW main address space performs the data collection for z/OS, JES2, CICS,
IMS, WebSphere MQ, and TCP/IP.
You can start the CICS and VTAM interfaces from:

The CA SYSVIEW user interface address space.
The SYSVUSER parameter library member that contains default startup options.

Start Your Product
This procedure guides you through adding a startup procedure to a system procedure
library.
Follow these steps:

1. Copy the PROC from the data set sysview.SAMPJCL into one of your system
procedure libraries.
SYSVIEW PROC Member
Contains the JCL used to start the CA SYSVIEW main services address space.
MEM Keyword Default: SYSVIEW
COMMNDxx Member Entry: COM='S SYSVIEW,REUSASID=YES'
SYSVUSER PROC Member
Provides the list of default CA SYSVIEW functions and tasks that are started
during the initialization.
MEM Keyword Default: SYSVUSER
COMMNDxx Member Entry: COM='S SYSVUSER'
2. Point the MEM keyword on the PROC statement to a member in the

sysview.CNM4BPRM data set that contains initialization parameters for the address
space.
Note: For more information about the CA SYSVIEW address space, see the
Administration Guide.
3. Review the initialization parameters before you start the address space.
4. If you want to start the address space automatically at IPL, add the start command
to the COMMNDxx member in SYS1.PARMLIB.
Note: For more information about the COMMNDxx member in SYS1.PARMLIB, see
the appropriate IBM guide.
The initialization (startup) procedures are added to the system procedure library.
Start Your Product

To use CA SYSVIEW, start the main address space.
Follow these steps:

1. Verify that the CA LMP codes are defined according to your specifications.
2. Start SYSVIEW to initialize the main services address space. Start SYSVUSER to start
the user address space.
After the LMP codes are correctly defined and these procedures have run, the main
address space is started.

Post-Installation Considerations
Post-Installation Considerations
The installation verification program (IVP) can be executed when the installation is
completed and CA SYSVIEW is started. IVP can also be executed any time that you want
to verify your installation.
IVP provides the following programs:

GSVCUTIL
Provides functions that let you review the settings of your installation parameters.
GSVXBAT
Executes in batch any valid CA SYSVIEW command so that you can exercise
components in CA SYSVIEW.
To verify your installation using the program GSVCUTIL:

1. Submit member IVP00001.
The resulting IVP report provides the installation settings for the following
functions:
z/OS system
Subsystem
Authorized Program Facility (APF) list
SYSVIEW LMP keys
2. Review the report and verify your settings.
To verify your installation using the program GSVXBAT:

1. Submit member IVP00002.
The output from the CA SYSVIEW command is returned to the SYSPRINT ddname
where the settings can be verified.
2. Review for messages in the SYSPRINT output.
Whether commands return data depends on the installed or active components.
For example, the IMSLIST command display is empty when IMS is inactive.
Note: For a sample job, see the SAMPLIB member EXECBAT. For more information
about the GSVXBAT program, see the Administration Guide.

Chapter 6: Migration Information
Update the INSTALL Job (see page 157)
Dynamic Installation of CA SYSVIEW (see page 158)
User Supervisor Call (SVC) Removal (see page 159)
LPA Load Library Data Set Removal (see page 159)
Anchor Address Space Removal (see page 160)
Library Concatenation (see page 161)
JES Definitions (see page 163)
Configuration Options Member - OPTIONS (see page 163)
External Security (see page 164)
Event Scheduler (see page 164)
Configuration Options - Parmlib Member CICSOPTS (see page 165)
Logical Group Definitions Removed - Parmlib Member CICSGRPS (see page 165)
IMS Dependent Regions - Data Collection (see page 176)
Update the INSTALL Job

The member INSTALL found in the installation data set sysview.SAMPJCL is used to
create dynamically all of the other installation members.
The following entry generates a step to allocate a set of SITE libraries:
SITEDSN=YES
The generated GSVXgsvx system configuration options member includes the definitions
for site libraries.

Dynamic Installation of CA SYSVIEW
Dynamic Installation of CA SYSVIEW

The steps that are required to install and dynamically configure CA SYSVIEW have been
simplified.
For CA SYSVIEW Version 14.0
Starting in Version 14.0, CA SYSVIEW does not provide or require the execution of a
dynamic installation job or step. The DYNAMIC job step was removed from the JCL for
the CA SYSVIEW started tasks. The installation provides updated JCL for the started
tasks.
Note: The job fails when you use the old JCL without removing the DYNAMIC job or
step. The execute program, GSVXINST, no longer exists.
The SYSVIEW load library data set must be APF authorized before starting CA SYSVIEW.
For previous releases of CA SYSVIEW
In releases before Version 14.0, CA SYSVIEW required the following system resources to
be defined:
User SVC
The existing SVC definitions can be removed when prior releases are no longer
used.
SYS1.PARMLIB(IEASVCnn)
SVCPARM nnn,REPLACE,TYPE(3),APF(NO),EPNAME(GSVXSVC)
LPA Modules
The existing LPA definitions can be removed when prior releases are no longer
used.
SYS1.PARMLIB(IEALPAnn)
INCLUDE LIBRARY(sysview.CNM4BLPA)
MODULES(GSVXSVC,GSVXAAST,CAIXNM4$)
The APF authorization of SYSVIEW load library data set

The APF authorization is still required.
SYS1.PARMLIB(PROGxx)
APF ADD DSNAME(sysview.CNM4BLOD) VOLUME(volume)
The required system resources could have been defined using one of the following
methods:
1. Providing manual definitions in the SYS1.PARMLIB members
SVC - SYS1.PARMLIB(IEASVCnn)
LPA - SYS1.PARMLIB(IEALPAnn)
2. Execution of a stand-alone dynamic install job

User Supervisor Call (SVC) Removal
sysview.SAMPJCL(INST0100) or
sysview.CNM4SAM(DYNMINST)
3. The following CA SYSVIEW Services started task contained a job or step DYNAMIC
that was used to install dynamically the required resources. The step could be run
even if the resources had been manually defined.
SYSVIEW - Main Services Address Space
SYSVUSER - User Interface Address Space
User Supervisor Call (SVC) Removal

In releases before Version 14.0, you defined a user SVC in the CA SYSVIEW System
Configuration Options member GSVXGSVX. This member resides in the system parmlib
concatenation.
Starting at Version 14.0, remove the following obsolete System Configuration Option
from any options member:
SVC-Number
If you do not remove this option, the CA SYSVIEW initialization continues while issuing
the following series of warning messages:
GSV445W Configuration member: GSVXGSVX
GSV446W Configuration option: SVC-Number nnn
GSV447W Configuration error: Option name is obsolete.
LPA Load Library Data Set Removal

The installation of CA SYSVIEW no longer requires a separate data set to contain the
required LPA load modules.
The following data set is no longer distributed:
sysview.CNM4BLPA

Anchor Address Space Removal
Anchor Address Space Removal

CA SYSVIEW Version 14.0 utilizes the CA Common Services CAMASTER address space to
anchor any required resources.
In releases before CA SYSVIEW Version 14.0
CA SYSVIEW utilized an anchor address space:
SYSVAAST - Anchor Address Space (prior to r14.0)
The purpose of the anchor address space was to anchor data spaces that CA SYSVIEW
services created and used.
The anchor address space:

Did not execute any code or programs.
Was defined as non-cancelable and non-memtermable
Was created automatically at initialization by the main services address space
Remained and was reused through the life of an IPL.

Library Concatenation
A CA SYSVIEW installation is comprised of several types of libraries or data sets designed
to contain a specific type of data. This library is referred to as a library type(libtype).
A library type can consist of multiple data sets. These data sets dynamically concatenate
when a read request is made for the specified library type.
Only one data set can be defined for each data set type. Therefore, a maximum of three
data sets can be concatenated.
If defined, the data sets are concatenated in the following order:
libtype DD DISP=SHR,DSN=user.data.set
DD DISP=SHR,DSN=site.data.set
DD DISP=SHR,DSN=system.data.set
The possible data set types are:

User (Optional)
The optional user-defined data sets contain definitions or overrides to site or
system definitions.
The users define and maintain the user data set names in their CA SYSVIEW profile.
Site (Optional)
The optional site defined data sets contain definitions or overrides to system
definitions.
The site data set names are defined in the CA SYSVIEW System Configuration
Options member: GSVXGSVX
The system configuration options member must be located in the concatenation of
the z/OS system parmlib data sets.
Example: SYS1.PARMLIB
System
The required system defined data sets contain definitions or configuration options.
The set of system data sets contains the original members the product installation
delivered. The system data set names are defined in the CA SYSVIEW System
Configuration Options member: GSVXGSVX.
The system configuration options member must be located in the concatenation of
the z/OS system parmlib data sets.
Example: SYS1.PARMLIB
For more information, see the following help topic: Library concatenation - USER, SITE,
and SYSTEM.

Data Sets Eligible for Library Concatenation

A SYSTEM data set is required for all library types. USER and SITE data sets are not
required. The definition of USER and SITE data sets are always optional.
USER and SITE data sets are not eligible for all library types.
The following table shows data set eligibility by library type:
Library Type DSN Suffix User Data Set Site Data Set System Data Set
CAPLIB CNM4BCAP n/a Site System
CLISTLIB CNM4BCLS User Site System
DATALIB CNM4BDAT n/a n/a System
HELPLIB CNM4BHLP User Site System
MAPLIB CNM4MAP User Site System
MIBLIB CNM4MIB User Site System
PANELLIB CNM4BPNL User Site System
PARMLIB CNM4BPRM User Site System
PLOTLIB CNM4BPLT User Site System
PROFILE CNM4BPRF n/a n/a System
REXXLIB CNM4BREX n/a Site System
SAMPLIB CNM4BSAM n/a n/a System
SECURITY CNM4BSEC n/a n/a System
TEMPLATE CNM4BTMP User Site System
The following table shows data set eligibility by library type before Release 13.9:
Note: A SITE data set did not exist and a USER data set was available for a limited
number of library types. Only a limited number of parmlib members were eligible for
the USER library.
Library Type DSN Suffix User Data Set Site Data Set System Data Set
CAPLIB CNM4BCAP n/a n/a System
CLISTLIB CNM4BCLS User n/a System
DATALIB CNM4BDAT n/a n/a System
HELPLIB CNM4BHLP n/a n/a System

JES Definitions
MAPLIB CNM4MAP User n/a System

MIBLIB CNM4MIB User n/a System
PANELLIB CNM4BPNL n/a n/a System
PARMLIB CNM4BPRM User n/a System
PLOTLIB CNM4BPLT User n/a System
PROFILE CNM4BPRF n/a n/a System
REXXLIB CNM4BREX n/a n/a System
SAMPLIB CNM4BSAM n/a n/a System
SECURITY CNM4BSEC n/a n/a System
TEMPLATE CNM4BTMP n/a n/a System
For more information, see the following help topic: Library concatenation - USER, SITE,
and SYSTEM.
JES Definitions
In releases before CA SYSVIEW Release 13.9, the data statements that were entered in
the JES parmlib member were column-dependent or specific.
The data is no longer column specific. The data is positional and can be entered in any
column as long as the data is contained in columns 1 through 72.
Configuration Options Member - OPTIONS

All CA SYSVIEW tasks and sessions read the OPTIONS parmlib member.
Starting in CA SYSVIEW Version 14.0, the OPTIONS parmlib member is cached to reduce
the data set allocation.
The main task within each of the service address spaces will:
Read the member from the parmlib data sets
Replace any cached data

External Security
External Security
To control command access using external security, code a SAF Class Name in the
External Security section of the User Groups in the security file.
A new XSDATA resource has been added in CA SYSVIEW Version 14.0. To handle the new
XSDATA resource, you create a rule or profile.
Permit all users read access to:
SV.SUSP.*.RESN.XSDATA
*
The wildcard third node assumes that you have the default value of YES for System
SMFID in Entity Name. By creating the suspend rule, you cause all XSDATA SAF calls
to be bypassed. This suspend rule allows all cross-system eligible commands to
function as they did in prior releases.
To start controlling access to the command data from remote systems:

You would not grant access to the suspend rule.
You would create new rules for the cross-system capable commands.
See the online help XSCMDS command for the complete list.
Example, allow all commands except CTASKS to retrieve cross-system data:

Permit the user read access to: SV.RESN.CA31.XSDATA.*
Forbid the user read access to: SV.RESN.CA31.XSDATA.CTASKS
Event Scheduler
The WebSphere MQ event function MQSDATA-SYSTEM has been functionally combined
with the event function MQSDATA-QMGRS. MQSDATA-SYSTEM is now obsolete.
If you use the CA SYSVIEW persistent data store to save scheduled events, then the
definitions are converted automatically.
If the SYSVIEW event scheduler task (SCHEDULE) is being COLD started, then update the
parmlib member SCHDMQS to remove:
The event MQS-SYSTEM
Any defined event with the function MQSDATA-SYSTEM
If any events with function MQSDATA-SYSTEM remain, you receive a warning message
indicating the function is now obsolete.

Configuration Options - Parmlib Member CICSOPTS
Configuration Options - Parmlib Member CICSOPTS

Default values were changed for the following configuration options:
New Prior
Configuration Options Default Default
-------------------------------- -------- --------
PERFORMANCE-GLOBAL-EXIT-TS Yes No
The following configuration options have been removed and made obsolete:
TRANSACTION-GROUP-MEMBER
TRANSACTION-GROUPS-STARTTYPE
Logical Group Definitions Removed - Parmlib Member

CICSGRPS
The parmlib member CICSGRPS is no longer used and has been removed.
Logical group definitions are no longer maintained for a specific CICS region. The
definitions have been merged into the common set of logical groups that CA SYSVIEW
maintains.
Define your definitions in the parmlib member GROUPS or using the online command
GROUPS.
Logical Groups Overview

CA SYSVIEW Logical Groups define a list of similar items as a single logical group name.
Use the group name for referencing the entire list.
The following list provides example logical group ideas:

Production CICS regions
CICS MRO regions
CICS transactions that are part of an application
A logical group of DASD volumes for exception processing
A logical group of related job names

Logical Group Definitions Removed - Parmlib Member CICSGRPS
How to Use Logical Groups

CA SYSVIEW Logical Groups can be used in several ways.
Create a threshold definition that monitors CPU usage for a list of job names.
1. Create a logical group with a type of JOBNAME that contains the list of job
names.
Parmlib: GROUPS
Command: GROUPS
DEFINE PROD TYPE JOBNAME

DESC 'Production jobs'
MEMBER CICSPROD
MEMBER PAYROLL
MEMBER DB2PROD
2. Create a threshold definition using the logical group name PROD.

Parmlib: MVSTHRSH
Command: THRESH
DEFINE JOBCPUT% RSCE >PROD LIMIT 90
The RSCE value for the metric JOBCPUT% is a jobname. The value >PROD begins
with the logical group name indicator character >. Therefore, the supplied
jobname processes as a logical group instead of a single job name.
Use a jobname logical group within a source member )IF statement.
Using multiple )IF statements:
Parmlib: CICSOPTS
)IF JOBNAME EQ CICSPROD
LOGGER-NAME CICSLOGR
)ENDIF
)IF JOBNAME EQ CICSTEST
)ENDIF
Using logical groups:

Parmlib: GROUPS
Command: GROUPS
DEFINE CICSLST TYPE JOBNAME

DESC 'CICS jobs'
MEMBER CICSPROD
MEMBER CICSTEST
Parmlib: CICSOPTS
)IF JOBNAME IN CICSLST/JOBNAME

)ENDIF

Use a jobname logical group for displaying a list of job names on the command
ACTIVITY.
1. Create a logical group with a type of JOBNAME that contains the list of job
names.
Parmlib: GROUPS
Command: GROUPS
DEFINE PROD TYPE JOBNAME

DESC 'Production jobs'
MEMBER CICSPROD
MEMBER PAYROLL
MEMBER DB2PROD
2. Issue the command ACTIVITY.

3. Issue the command SELECT to filter the displayed information.
SELECT fieldname IN group.instance/type
SELECT fieldname IN group/type
SELECT JOBNAME IN PROD/JOBNAME
The JOBNAME field on the ACTIVITY display is defined to have an associated

logical group type of JOBNAME. Therefore, the logical group type is not
required on the SELECT command.
SELECT JOBNAME IN PROD

Migrating Logical Group Definitions

Starting with CA SYSVIEW 14.0:
You have one single set of logical group definitions.
All definitions are loaded each time the SYSVIEW Main Services Address Space is
started.
All logical group definitions are loaded from the parmlib member GROUPS or from
the SYSVIEW persistent data store. This choice depends on the start type of WARM
or COLD.
Logical Groups can be displayed, updated, or altered using the online command
GROUPS.
The CICS logical group definitions must be combined with the definitions
maintained by the SYSVIEW Main Services Address Space.
When the CA SYSVIEW Main Services Address Space terminates, the list of logical
group definitions are written to the CA SYSVIEW persistent data store
The syntax for the logical groups definitions are the same.
The migration of logical group definitions from one release of CA SYSVIEW to another
depends on the method being used to start CA SYSVIEW.
Starting SYSVIEW using WARM Start (see page 169)
The migration is automatic if the logical groups definitions are stored in the
persistent data store.
Starting SYSVIEW using COLD Start (see page 170)
Logical group definitions load from the parmlib member GROUPS when COLD
starting the SYSVIEW Main Services Address Space. In this case, the user is
responsible for maintaining the definitions from release to release. The SYSVIEW
SITE libraries ease the need for manual changes or tracking.
Logical Groups Prior to CA SYSVIEW 14.0
Before CA SYSVIEW 14.0, there were two separately maintained sets of logical groups.
1. Logical Groups that SYSVIEW Main Services Address Space maintained.
Parameter Library Member: GROUPS
Online Command: GROUPS
2. Logical Groups that CA SYSVIEW for CICS Data Collector maintained in each
monitored CICS region. These groups have been removed.
Parameter Library Member: CICSGRPS
Online Command: CGROUPS

Load logical group definitions into each CICS region separately to let the same
logical group name be defined in multiple CICS regions, but contain a different list
of logical group members.
CICS logical group definitions were loaded from the parmlib member CICSGRPS or
the CA SYSVIEW persistent data store.
The CICS logical group processor supported the following logical group types:
CICSTRAN - CICS transaction IDs
TRAPDEST - SNMP trap destinations specified as IP addresses or DNS names
Use the Warm Start Method
When WARM starting CA SYSVIEW:

The logical group definitions are not being maintained in parmlib members GROUPS
and CICSGRPS.
SYSVIEW Main Services Address Space and all CICS data collectors are being WARM
started.
The persistent data store is being utilized to maintain definitions.
The CICS logical group definitions need added. Create a parmlib member containing
the list of logical group definitions that are required.
Follow these steps:

1. Create a parmlib member using the conversion utility GSVYLGCV.
2. Add the CICS logical group definitions that were maintained in the SYSVIEW
persistent data store.
3. From the GROUPS command on a SYSVIEW 14.0 system, issue the following
commands to load the definitions from this new parmlib member.
a. Issue the command:
GROUPS
b. Issue the command:

RELOAD member

Use the Cold Start Method
When COLD starting CA SYSVIEW:

All logical group definitions are being maintained in parmlib members GROUPS and
CICSGRPS.
The SYSVIEW Main Services Address Space and all CICS data collectors are being
COLD started.
The persistent data store is not being utilized to maintain definitions.
Follow these steps:

1. Copy the definitions in the parmlib member CICSGRPS to the parmlib member
GROUPS.
2. Carry any CICS definition )IF logic forward as an instance when that logic caused a
specific CICS region to use the definition.
Note: The instance value can be defined using generic mask characters.
Example: The prior CICSGRPS definition with no )IF logic:
DEFINE CICS TYPE CICSTRAN
DESC 'CICS transaction group'
MEMBER CEMT
MEMBER CEDA
MEMBER CECI
MEMBER CEBR
Example: The new definition in the member GROUPS

INSTANCE =
MEMBER CEMT
MEMBER CEDA
MEMBER CECI
MEMBER CEBR
Example: The prior CICSGRPS definition with )IF logic

)IF JOBNAME EQ CICSPROD
MEMBER CEMT
MEMBER CEDA
MEMBER CECI
MEMBER CEBR
)ENDIF
Example: The new definition in the member GROUPS

INSTANCE CICSPROD


MEMBER CEMT
MEMBER CEDA
MEMBER CECI
MEMBER CEBR

Conversion Utility - GSVYLGCV

The conversion utility processes the CICS logical groups that have been saved in the CA
SYSVIEW persistent data store.
You can find a sample job to convert CA SYSVIEW for CICS logical group definitions in
SYSVIEW.DEV.BASE.SAMPLIB(GSVYLGCV).
In previous releases, CICS logical group definitions were saved in the persistent data
store. Definitions were saved for each CICS jobname. View a list of all saved definitions
using the DLLIST online command.
The definitions are saved and contain the following information:

DataId: CICSGRPS_jobname
System: System name
SSid: Subsystem identifier of the SYSVIEW
Bld: The build associated with the SYSVIEW release.
The utility processes the saved definitions. The goal of the utility is to combine logical
group definitions that are identical across all CICS regions for a specific group name and
type. The identical definitions convert to a single definition with an INSTANCE value of
"=".
Example: Identical logical group definitions

INSTANCE =
MEMBER CEMT
MEMBER CEDA
MEMBER CECI
MEMBER CEBR
If the members of a logical group are not identical for a specific group name and type,
then a jobname specific logical group definition must be created for that jobname. The
CICS jobname is used as the INSTANCE value.
Example: Different logical group members

INSTANCE jobname
MEMBER CEMT
MEMBER CEDA
MEMBER CECI
MEMBER CEBR

Logical Group Types:
Max Max
Length Length
Group Member
Type Name Name Description
--------- ------ ------ -----------------------------------
CHANNEL 7 2 MVS channel
Format: FF (hex)
CICSJOB 8 8 CICS job names
CICSPLEX 8 8 CICS job names

Used by the GROUP parameter
on CICS commands.
CICSTRAN 7 8 CICS transaction IDs
CPU 7 4 CPU processor number

Format: 0000 (hex)
ALL, CP, IIP, IFA. SP
DBAREA 7 17 Database areas

Format: database.areaname
DB2SSID 8 4 DB2 subsystem IDs
DEVICE 7 8 Device names

Formats: DASD volume = volume
DASD device = DASDnnnn
TAPE device = TAPEnnnn
EMAIL 8 64 Email IDs
IDMS 8 8 IDMS job names
IMSBALG 7 8 IMS balance groups
IMSBUFP 7 4 IMS buffer pool names
IMSESUB 7 17 IMS external subsystems

Format: jobname.subsys
IMSID 7 4 IMS subsystem IDs
IMSLTERM 7 17 IMS Logical Terminals

Format: termtype.terminal
IMSOTMA 7 17 IMS OTMA
Format: Tmember.Tpipe
IMSPOOL 7 4 IMS pool names

IMSREGN 7 13 IMS dependent regions

Format: type.jobname
type - IMS dependent region type
IMSSPOC 8 8 IMS subsystems ID to used by the

command: IMSSPOC
IMSTRAN 7 8 IMS transaction names
JES2NODE 7 8 JES2 node names
JOBCLASS 8 8 JES job classes

JOBNAME 7 8 Job names
MQBPOOL 7 4 WebSphere MQ buffer pools
MQCHAN 7 20 WebSphere MQ channels
MQPSET 7 4 WebSphere MQ page sets
MQQMGR 7 4 WebSphere MQ queue managers
MQQUEUE 7 48 WebSphere MQ queue names
OUTCLASS 8 8 JES output classes
PORTLIST 8 5 TCP/IP port numbers
SYSNAME 8 8 System names
TCPID 7 8 TCP/IP job names
TRAPDEST 8 64 SNMP trap destinations specified

as IP addresses or DNS names
TYPEJOBN 8 12 Job type and job names

Format: Type.Jobname
USER 8 128 User defined. The members in this

logical group type have no
predefined meaning or association.
This logical group type can be

very useful when creating a group
to be used with the SELECT command.
VTAMAPPL 7 8 VTAM applids

WMREPORT 8 8 WLM Report Class

XSCONN 8 8 Cross-system connection
XSDS 8 8 Cross-system data server
XSHDWR 8 8 Cross-system hardware
XSLOGNNR 8 8 Cross-system logon not required
XSLOGNRQ 8 8 Cross-system logon required
XSNODE 8 8 Cross-system nodes
XSPLEX 8 8 Cross-system sysplex
XSSS 8 8 Cross-system session server
XSSYSTEM 8 8 Cross-system sysnames
The following logical group types support an instance qualifier:
Max Instance
Type Instance Length Description
--------- -------- ------ -----------------------------------
CICSTRAN jobname 8 CICS jobname
TRAPDEST jobname 8 CICS jobname
USER anything 8 User defined.

When used on a SELECT command,
if a specific instance value is not
specified, the userid associated
with the session will be used
to locate the best match logical
group definition.

IMS Dependent Regions - Data Collection
IMS Dependent Regions - Data Collection

New data collection has been added to collect information about IMS-dependent
regions.
The following process explains how you perform this type of collection.
1. Add a data collection event to the CA SYSVIEW Event Scheduler.
The event IMS-REGIONS is automatically added.
The event IMS-REGIONS is also defined in the parmlib member SCHDIMS.
2. Add a monitor entry that defines those IMS regions to be monitored.
The parmlib member IMSMON contains the following sample definitions for monitoring
all regions and types by default:
MONITOR IMSREGN IMSID = RSCE = INCLUDE

MONITOR IMSREGN IMSID = RSCE =.= INCLUDE
If you are starting the IMS data collector with a WARM start, IMS monitor definition is
loaded from the SYSVIEW persistent data store. In that case, you add manually the
monitor definitions using the online IMSMON command or start the IMS data collector
with a COLD start.

Appendix A: CCS for z/OS Component
Requirements
FMIDs (see page 177)
FMIDs
This section describes the CA Common Services for z/OS components and their
corresponding FMIDs that are required by CA SYSVIEW to perform various functions. For
more complete and up-to-date information, see Installation Dependencies in the
chapter System Requirements in the CCS for z/OS Getting Started Guide.
Two sets of FMIDs are provided:

The first set of FMIDs are based on CCS for z/OS 14.0.
The second set is based on CCS for z/OS r14.1.
CA LMP (License Management Program)

The following CCS for z/OS components are required to validate base product licensing
for CA SYSVIEW.
The FMID based on CCS for z/OS v14:
FMID Component
CAS9E00 CAIRIM
The FMIDs based on CCS for z/OS r14.1:
FMID Component
CAS9E10 CAIRIM

FMIDs
CA MASTER
The following CCS for z/OS components are required for the CA SYSVIEW interface to
the CAMASTER services.
The FMID based on CCS for z/OS v14:
FMID Component
CEI0E00 CA MASTER
The FMIDs based on CCS for z/OS r14.1:
FMID Component
CEI0E10 CA MASTER
Interface to IBM Health Checker

The following CCS for z/OS component is required for the CA SYSVIEW interface to the
IBM Health Checker.
The FMID based on CCS for z/OS r14.1:
FMID Component
CEF5E10 CA Health Checker Common Service
Note: For information on additional setup and configuration steps that must be
completed, see the CCS for z/OS Administration Guide.
CA zIIP Enablement Services

The following CCS for z/OS component is required for the CA SYSVIEW interface to the
CA zIIP Enablement Services.
The FMID based on CCS for z/OS r14:
FMID Component
CAS9E00 CAIRIM

FMIDs
The FMID based on CCS for z/OS r14.1:
FMID Component
CAS9E10 CAIRIM

Appendix B: Interface Options
TSO and CA Roscoe/ETSO Interface Support (see page 181)
ISPF Interface Support (see page 182)
VTAM Interface Support (see page 183)
CICS Interface Support (see page 184)
Console Interface Support (see page 186)
Local 3270 Device Interface Support (see page 188)
Batch Interface Support (see page 188)
TSO and CA Roscoe/ETSO Interface Support

The timesharing option (TSO) and the CA Roscoe/Extended timesharing option (CA
Roscoe/ETSO) interface let you access CA SYSVIEW from TSO or CA Roscoe/ETSO.
You can use the CA SYSVIEW TSO interface or the CA Roscoe/ETSO interface without
performing additional installation steps.
Note: Add a STEPLIB or JOBLIB DD statement when the sysview.CNM4BLOD data set is
not in the linklist. This addition lets you use the TSO interface for accessing CA SYSVIEW.
The TSO command module for CA SYSVIEW is named SYSV.
Access CA SYSVIEW from CA Roscoe/ETSO

After you install the CA Roscoe/ETSO interface, you can access CA SYSVIEW from CA
Roscoe/ETSO.
Follow these steps:

1. Add an entry for the SYSV program name to the Eligible Program List (EPL).
MODESET authorization flag
Sets the MODESET authorization flag when the flag is set to Y (yes).
Command processor flag
Sets the command processor flag when the flag is set to CP (command
processor).
2. Add the sysview.CNM4BLOD data set to the ETSOLIB DD statement in the ROSCOE
JCL.

ISPF Interface Support
3. Enter the following command on the CA Roscoe/ETSO command line:

CALL SYSV
CA SYSVIEW initiates under CA Roscoe/ETSO.
Note: For detailed information about defining applications to CA Roscoe/ETSO, see the
CA Roscoe documentation.
ISPF Interface Support

The ISPF interface lets CA SYSVIEW run under ISPF to take advantage of the ISPF
split-screen capabilities.
Installing ISPF support consists of copying members from the data set
sysview.CNM4BISP to the appropriate ISPF DD statement in your TSO logon PROC.
Note: If you are reinstalling ISPF interface support, then also install the new ISPF panels
and the GSVXCMDS member.
Install ISPF Support Permanently

You can install ISPF support permanently to use the ISPF split-screen capabilities.
Follow these steps:

1. Copy the GSVXCMDS member in the data set sysview.CNM4BISP to a data set
pointed to by the ISPTLIB DD statement in your TSO logon PROC.
Note: Specify a user-defined data set, if possible.
2. Copy the following members from the data set sysview.CNM4BISP to a data set
pointed to by the ISPPLIB DD statement in your TSO logon PROC:
GSVX000M
GSVX000J
GSVX000D
GSVX00KM
GSVX000P
GSVX00KP
Note: Specify a user-defined data set, if possible.

VTAM Interface Support
3. Update the ISPF Primary Option Menu member ISR@PRIM with the statements that
contain SYSV or GSVX in the sysview.CNM4BISP(SAM@PRIM) member. The
ISR@PRIM member is in a data set pointed to by the ISPPLIB DD statement in your
TSO logon PROC.
CA SYSVIEW appears on the ISPF Main Menu as a selection option.
Note: Add a STEPLIB or JOBLIB DD statement when the sysview.CNM4BLOD data set is
not in the linklist. This addition lets you use the ISPF interface for accessing CA SYSVIEW.
Install ISPF Support Dynamically

You can also install ISPF support dynamically to use the ISPF split-screen capabilities.
Follow these steps:

1. Use the SYSVCLST member or the SYSVREXX member from the data set
sysview.CNM4BSAM to access the ISPF LIBDEF facilities.
These members use the ISPF LIBDEF facilities.
2. Temporarily allocate the panels, tables, and modules that are required to invoke CA
SYSVIEW.
The dynamic installation of the ISPF support is complete.
VTAM Interface Support

The VTAM interface lets CA SYSVIEW run under VTAM. Using the IBM ACF/VTAM
Programmed Operator Interface, you can enter VTAM commands and see the results
from within CA SYSVIEW.
Install VTAM Support

After you install the VTAM interface support, you can use CA SYSVIEW from VTAM.
Follow these steps:

1. Copy the SYSVAPPL member from the data set sysview.CNM4BSAM to the
SYS1.VTAMLST data set.
The following support is now available from the data set SYS1.VTAMLST:
The APPLIDs used when using CA SYSVIEW with VTAM.
The APPL statements the CA SYSVIEW VTAM command uses.

CICS Interface Support
2. Set the ACBNAME parameter on the first APPL statement in the SYSVAPPL member.
Select the name to use when logging in to CA SYSVIEW through the VTAM interface.
Use that name when you start the VTAM interface.
The CA SYSVIEW VTAM command uses the remaining APPL statements (named
SYSVPO00 through SYSVPO03) to submit commands to ACF/VTAM. The four APPL
statements provide support for users who are using the VTAM command
concurrently. To increase this number, add additional APPL statements
incrementing the numeric suffix of the SYSVPOnn APPL name by one for each APPL
added.
3. Add the SYSVAPPL name to the ATCCON member in the SYS1.VTAMLST data set.
The SYSVAPPL member activates when VTAM starts.
4. Add the CA SYSVIEW USSTAB entry that is in the USSTAB member in the data set
sysview.CNM4BSAM to your installation USSTAB member.
This entry simplifies the CA SYSVIEW logon procedure.
If you do not use the USSTAB entry, use the complete LOGON command to log in to
CA SYSVIEW from VTAM.
5. Set the CMD and DEFAULT parameters in the USSTAB member to the value you
used for the ACBNAME parameter in Step 2 of this procedure.
6. Assemble the USSTAB table and place it in the appropriate data set in your
VTAMLIB concatenation.
Note: Skip this step if your site already has a suitable USSTAB available.
7. Reload the USSTAB in VTAM using the MODIFY TABLE command.
The changes for CA SYSVIEW are incorporated into your system. VTAM interface
support is installed.
Note: For information about how to start the VTAM interface, see the
Administration Guide.

CICS interface support lets you access CA SYSVIEW from a CICS session and monitor and
customize the interface.
The CICS interface does not require the CICS data collection option to be active.
Note: After you have installed CICS interface support and before you can log in, start the
CICS interface in the CA SYSVIEW user address space. For information about starting and
using the CICS interface, see the Administration Guide.

CICS User ID Exit Routine

The following information describes the CICS user ID exit routines:
The user ID exit routine obtains the user ID of a CICS user. This routine provides the
appropriate CA SYSVIEW profile data set member for the online interface. The user
ID is also used for CA SYSVIEW security.
The default user ID exit distributed in the CA SYSVIEW load library does not pass a
user ID back to CA SYSVIEW. Therefore, CA SYSVIEW prompts the user for a user ID.
The source for the default exit is in the GSVXCXT1 member of the
sysview.CNM4BSAM data set. You do not need to assemble it.
Modify the Exit to Use Your Security System

Some CICS systems have their own exit security system. You can alter the exit to obtain
user IDs from the control blocks of your security system.
Follow these steps:

1. Obtain the GSVXCXT1 member from the sysview.CNM4BSAM data set.
2. Alter the GSVXCXT1 member to meet your security needs.
3. Assemble the GSVXCXT1 member and link it into the data set sysview.CNM4BLOD
with the name GSVXCXT1.
Your security system is defined to CA SYSVIEW.
CICS Transaction Termination Exit Routine

A description of the CICS transaction termination exit routine follows:
The routine can pass control to another transaction at CA SYSVIEW online interface
transaction termination time.
The source for the default exit is in the GSVXCXT2 member in the
sysview.CNM4BSAM data set. You do not need to assemble it.

Console Interface Support
Modify the Transaction Termination Exit

You can alter the transaction termination exit to specify the transaction to which control
is passed.
Follow these steps:

1. Obtain the GSVXCXT2 member from the data set sysview.CNM4BSAM.
2. Alter the GSVXCXT2 member to meet your needs.
3. Assemble the GSVXCXT2 member and link it into the data set sysview.CNM4BLOD
with the name GSVXCXT2.
Control is passed to the transaction you specified.

The CA SYSVIEW console interface, which lets you communicate with and execute CA
SYSVIEW commands from a console, is implemented through the product CA GSS. CA
GSS is installed with CA Common Services for z/OS, which is also required for the
licensing of CA SYSVIEW.
How CA GSS Communicates with CA SYSVIEW

CA GSS communicates with CA SYSVIEW through the supplied application program
interface GSVXAPIE.
During initialization, CA GSS communicates as follows:

Starts a server that attaches a long-running session with CA SYSVIEW. The default
server name is SYSVCONS. All console commands that are directed to CA SYSVIEW
are routed through this server.
Executes the IMOD $SYSVIEWE_INIT. This IMOD starts CA SYSVIEW services.
During termination, CA GSS executes the IMOD $SYSVIEWE_TERM. This IMOD

terminates CA SYSVIEW services.

Enabling the Console Interface

Before the console interface can be enabled, the following conditions must be met:
CA SYSVIEW must be installed.
CA GSS must be installed and active.
The following statements must be in the CA GSS run-time parameter member
RUNPARM:
COMMAND VERB SYSV IMOD SYSVIEW_CONSOLE
PRODUCT SYSVIEWE
ADDRESS SYSVIEWE GSVXAPIE 15 DETACH TYPE 0
ISET SYSVIEWE DSN sysview.CNM4BIMD SSID ISRV LOAD
Note: The RUNPARM member may already contain some or all of the preceding
statements. The SAMPLIB member GSS contains these statements.
Customize the Console Interface

You can customize the console interface to meet the needs of your site.
Follow these steps:

1. Select any or all of the following options in the IMOD SYSVIEW_CONSOLE:
Attach a prefix to all output messages.
Specify a WTO route code.
Specify WTO descriptor codes.
Specify maximum message length.
Display the end of data line.
Specify the maximum number of data lines.
2. Customize and save each option.
When you finish, your console interface is customized.

Local 3270 Device Interface Support
Local 3270 Device Interface Support

The CA SYSVIEW local 3270 device interface lets you run the product in a dedicated
mode from any locally attached 3270 device. Copy the SYSVLCL PROC from the
sysview.SAMPJCL data set to one of your system procedure libraries to install the
interface.
Use this interface:

To start a session with CA SYSVIEW, even when TSO and VTAM are not active.
When JES is not active.
If the SYSVLCL PROC is placed in SYS1.PROCLIB and you specify SUB=MSTR when
you start the procedure.
Note: For information about how to start the SYSVLCL local 3270 device interface
procedure, see the Administration Guide.
Batch Interface Support

The batch interface lets you perform batch processing in CA SYSVIEW. No installation
procedures are required to use the batch interface.
Note: For more information, see the Administration Guide.

Index
3 F
3270 device support 188
FMIDs 177
JES control block maps 116
options, learning about 25 G
A GSVIINST installation parameters 53, 81
allocate libraries 65 H
assemble
JES control block maps 116 history data collection 118
z/OS control block maps 110 HOLDDATA 71
authorization
APF 51
I
CA LMP 32 install job, running and modifying 51
interface support, installing
B CA Roscoe/ETSO 181
batch interface 188 CICS 184
ISPF 182
C VTAM 183
internal HOLDDATA 71
CA Health Checker 26, 30
CA LMP 31 J
catalog captured events 117
CICS JES
format internal trace table entries 149 configuration names table 111
interface support 184 naming conventions 113
JCL 150
transaction termination exit 185
K
components key certificate 33
CCS for z/OS requirements 177
learning about 26 L
specifying 53, 81 local 3270 device support 188
console interface 186 log
contacting technical support 4 defining 118
control block maps module 110 naming conventions 121
converting security requirements 23
convert the profile data set 141
convert the security data set 139 N
customer support, contacting 4
naming conventions
D JES configuration modules 113
device support for the 3270 188 O

E options, learning about 25
external HOLDDATA 71
Index 189
S
security requirements 23
support, contacting 4
T
technical support, contacting 4
U
upgrade information 157

Sysview Install ENU

Uploaded by

Copyright:

Available Formats

Sysview Install ENU

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sysview Install ENU

Uploaded by

Copyright:

Available Formats

CA SYSVIEW Performance

CA Easytrieve Report Generator (CA Easytrieve RG)

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you

To provide feedback about CA Technologies product documentation, complete our

Chapter 2: Preparing for Installation 19

Chapter 3: Installing Your Products Using CA CSM 35

Chapter 4: Installing Your Product Using Pax ESD or DVD 37

Chapter 5: Starting Your Product 75

Chapter 6: Migration Information 157

Appendix A: CCS for z/OS Component Requirements 177

This section contains the following topics:

CA SYSVIEW Server Overview

Consult with the following personnel, as required:

How the Installation Process Works

CA Chorus Software Manager (CA CSM) - formerly known as CA Mainframe Software

To install your product, do the following tasks:

Integration with Other CA Products

This section contains the following topics:

Chapter 2: Preparing for Installation 19

IBM REXX Library:

Option/Component Product Supported Releases Dropped

Option/Component Product Supported Releases Dropped

Requires the following 15.0, 16.0, 17.0 14.0, 14.5

Chapter 2: Preparing for Installation 21

CA Common Services Requirements

CA Insight for DB2

GMI Software Requirements

IBM REXX Library Requirements

http://www-01.ibm.com/support/Alternate REXX Library

Note: For detailed security requirements, see the Security Guide.

Chapter 2: Preparing for Installation 23

Options OPTIONS Value LMP Code Installation and Customization Requirements

CA Cross Enterprise APM CEAPM 11 Complete the installation process. Additional

How Components and Options Are Enabled (see page 34)

Chapter 2: Preparing for Installation 25

Note: To customize components, follow the procedures in the Administration Guide.

Component COMPONENT LMP Code Installation and Customization Requirements

How Components and Options Are Enabled (see page 34)

Access and Invoke the IMS APIs

Follow these steps:

Chapter 2: Preparing for Installation 27

Access the MVS/QuickRef Interface

Follow these steps:

CA Common Services for z/OS Components

Chapter 2: Preparing for Installation 29

CA Health Checker Common Service

License the Product

Follow these steps:

KEYS MemberAdd Execution Key

PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss)

The parameter definitions are as follows:

Chapter 2: Preparing for Installation 31

Values for pp are as follows:

Example: Add CA LMP Execution Key

PROD(FU) DATE(27JUN12) CPU(2097-E26 /370623)

CA LMP Key Certificate

Chapter 2: Preparing for Installation 33

How Components and Options Are Enabled

Available Components (see page 26)