Data Sets Eligible for Library Concatenation

Migration Information › Post-Installation Considerations › Data Sets Eligible for Library Concatenation

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

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

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

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
               LOGGER-NAME CICSLOGR
            )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
   LOGGER-NAME CICSLOGR
)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
The migration is automatic if the logical groups definitions are stored in the persistent data store.
Starting SYSVIEW using COLD Start
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.

Logical Groups that SYSVIEW Main Services Address Space maintained.
- Parameter Library Member: GROUPS
- Online Command: GROUPS
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:

Create a parmlib member using the conversion utility GSVYLGCV.
Add the CICS logical group definitions that were maintained in the SYSVIEW persistent data store.
From the GROUPS command on a SYSVIEW 14.0 system, issue the following commands to load the definitions from this new parmlib member.
1. Issue the command:
```
GROUPS
```
2. 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:

Copy the definitions in the parmlib member CICSGRPS to the parmlib member GROUPS.

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

DEFINE CICS   TYPE     CICSTRAN
               INSTANCE =
               DESC     'CICS transaction group'
               MEMBER   CEMT
               MEMBER   CEDA
               MEMBER   CECI
               MEMBER   CEBR

Example: The prior CICSGRPS definition with )IF logic

)IF JOBNAME EQ CICSPROD
DEFINE CICS   TYPE   CICSTRAN
              DESC   'CICS transaction group'
              MEMBER CEMT
              MEMBER CEDA
              MEMBER CECI
              MEMBER CEBR
)ENDIF

Example: The new definition in the member GROUPS

DEFINE CICS   TYPE     CICSTRAN
              INSTANCE CICSPROD
              DESC     'CICS transaction group'
              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

DEFINE CICS   TYPE     CICSTRAN
              INSTANCE =
              DESC     'CICS transaction group'
              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

DEFINE CICS   TYPE     CICSTRAN
              INSTANCE jobname
              DESC     'CICS transaction group'
              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

New data collection has been added to collect information about IMS-dependent regions.

The following process explains how you perform this type of collection.

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