Configuration Members

Configuration members.
cvsrmv-14-0
2
 
 
Data Set Groups - Logical Collections of Data Sets
A data set group is a collection of data sets regardless of their physical location, that is, a logical collection of data sets based on their attributes. The data set groups contain following categories:
  • Data sets on primary disk storage (formerly named Logical Groups)
  • Data sets on secondary storage (formerly named External Groups)
  • Data sets on tape storage
Examples:
  • All data sets that belong to an application, or a department that are based on naming conventions
  • All data sets of the same SMS management class
  • All data sets matching a particular index (node) name
User-defined Storage Groups - USR Pools
USR Storage Groups (Pools) are defined in PARMLIB member POOLDEFS. System parameter POOLDEF (S) actually sets the last character of the member name. The default of S indicates member POOLDEFS. If you specify system parameter POOLDEF (1), USR pool definitions must be in member POOLDEF1.
For more information, see Configure User-defined Storage Groups
ARJES2XT - (Optional) Local PARMLIB Member
Use this member to define the pseudo volumes, dsnames, job names, and program names that tailor the candidates for invoking auto- restores from the JES2 Exit. If the member is not present or empty, copy the sample from the CCTUSAMP library.
CASCMDS - (Optional) Local PARMLIB Member
This member contains CAS (Catalog Address Space) modify commands to be used from the presentation clients. If the member is missing or empty, copy the sample member from the CCTUSAMP library. Remove, edit, or add the appropriate commands to customize the list.
CATEXCL - (Optional) Local PARMLIB Member
This member is obsolete. See the member 
INCLEXCL
 that provides the same functionality.
CATINCL - (Optional) Local PARMLIB Member
This member is obsolete. See the member 
INCLEXCL
 that provides the same functionality.
CIMLIST - (Optional) Local PARMLIB Member
CIM information is obtained through servers and systems running CIM Object Manager Providers (CIMOM Providers). Define each Provider in PARMLIB member CIMLIST (or an alternate member specified that is by the system parameter CIMLIST).
The CIM Provider architecture includes an automatic discovery process that is based on the Service Locator Protocol (SLP), but this protocol is based on an underlying TCP/IP 
multicast
 facility which is not supported by the z/OS mainframe TCP/IP now.
As the mainframe cannot discover the CIMOM Providers automatically through the TCP/IP SLP protocol, manually define any and all CIMOM Providers. Providers are defined in XML, as illustrated in the following example:
<CIMPROVIDERS> <CLASS NAME="ESS2105"> <PROVIDER DESC="your description for provider 01"> <SERVER>ip address1 or DNS name1</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON ENCODE="YES">encoded-userid-pswrd-for-provider-01</LOGON> </PROVIDER> </CLASS> </CIMPROVIDERS>
Use XML syntax. XML follows a basic structure of paired tags (a start-tag and a terminating-tag). The third form of XML tag is named a self-terminating tag, but that form of XML is not used in the CIMLIST member structure. Starting XML tags denote the beginning of a section of information. Each section ends when its matching termination tag is reached.
The following list shows the XML tags used in the CIMLIST member (the matching termination tags are not shown):
  • <CIMPROVIDERS>
  • <CLASS>
  • <PROVIDER>
  • <SERVER>
  • CA Portal
  • <NAMESPACE>
  • <DOCUMENT>
  • <LOGON>
  • <COMMENTS>
Any XML tag other than those previously mentioned on paired terminator tags is ignored, however, they are not treated as an error.
Five XML tags are used to identify uniquely a specific CIMOM Provider. They are: <SERVER>, CA Portal, <NAMESPACE>, <DOCUMENT>, and <LOGON>. The <SERVER> tag is followed by either an IPv4 dot-address (for example, 255.255.1.1), an IPv6 address (for example, C0D1:4011::FE12:0001), or the DNS name of the target server running the CIMOM Provider software. The IPv6 addresses can include embedded IPv4 addresses, such as ::FFFF:255.255.1.1, ::255.255.1.1 and 255.255.1.1, all of which actually refer to the same IP address. The </SERVER> XML termination tag must immediately follow the IP address. Do not use any leading, embedded, or trailing blanks in this value or any of the CIMLIST XML values.
Example:
<SERVER>255.255.1.1</SERVER> <SERVER>esscim01.mydomain.com</SERVER> <SERVER>::FFFF:255.255.1.1</SERVER> <SERVER>::255.255.1.1</SERVER> <SERVER>C0D1:4011::FE12:0001</SERVER>
When configuring a CIM provider, one of the configuration options is the TCP/IP port number on which the provider listens for connection requests. The CA Portal XML tag is used to define the TCP/IP port number for a given CIM provider. Currently, all vendor CIM providers default to 5988 for basic TCP/IP sockets and 5989 for secure TCP/IP sockets. Because CA Vantage SRM does not currently support secure sockets, specify a port number of 5988 when defining a CIM provider entry. When defining a native Hitachi HiCommand Device Manager Server entry, however, the port number default is 2001.
Examples:
<PORT>5988</PORT> <PORT>2001</PORT>
Two more CIM provider data elements might vary from one provider to the next. These elements are the CIM namespace name and the name of the document to be requested on the HTTP request header, much like the name of the document or web page you would access in a browser URL. Current versions of the various vendor CIM providers default to the vendor name as the namespace. This would be ibm for IBM, hitachi for Hitachi, and emc for EMC. Earlier versions of the IBM CIM provider defaulted to a namespace of cimv2. To define the parameter, refer to the CIM provider documentation and configuration to determine the proper value for the namespace name.
Examples:
<NAMESPACE>ibm</NAMESPACE> <NAMESPACE>hitachi</NAMESPACE>
Observe the following:
  • When you define an entry for a native HiCommand Device Manager server, omit the namespace parameter.
  • CA Vantage SRM currently does not support Secure Sockets.
  • Two more CIMOM data elements might vary from one CIMOM Provider to the next. These elements are the CIMOM 
    namespace name
     and the name of the document to be requested on the HTTP request header, much like the name of the document or web page you would access in a browser URL. The namespace name for the ESS2105 is always “cimv2” under the current releases of the IBM ESS 2105 CIMOM Provider software as shown in the following example:
    <NAMESPACE>cimv2</NAMESPACE>
The namespace name for the current Hitachi CIM provider is “hitachi” and “emc” for the current EMC provider. When coding this parameter, refer to the CIM provider documentation to determine the proper value for the namespace name.
The document name for the current releases of the IBM, Hitachi, and EMC CIMOM Providers are always “/cimom”. In actuality, what you are defining through the <SERVER>, CA Portal, and <DOCUMENT> tags is you would code for a Web browser URL, only in a different form. The URL address http://255.255.1.1:5988/cimom would be coded here as shown in the following example:
<SERVER>255.255.1.1</SERVER> <PORT>5988</PORT> <DOCUMENT>/cimom</DOCUMENT>
When defining an entry for a native HiCommand Device Manager server, omit the document name parameter.
These three entities identify the target server, the port to which CA Vantage SRM connects, and the name of the document CA Vantage SRM requests in the HTTP packet that it sends to this server. The namespace name is not an HTTP entity, but is used by the CIM architecture to define a schema and scope of the CIM requests.
The last of the XML tags associated with specific CIMOM Providers is the <LOGON> tag. A CIMOM provider can be configured to require a security login. If security has been turned on, any attempt to connect to the Provider without a logon ID and Password is rejected with a standard HTTP 401 error response.
If this happens, CA Vantage SRM login using the information that you specify in the <LOGON> XML tag. This might mean that you should have login IDs and Passwords in your CIMLIST member, which is certainly a security concern.
To address this security concern, CA Vantage SRM gives you an option to encode the logon ID and Password string using the CA Vantage SRM CIM Logon Encoder utility (GENCIMEN), which is delivered in the CA Vantage SRM load library with the CIM support. This is a TSO command-line style utility that accepts a logon ID and Password string and outputs an encoded string. You can execute this utility as a TSO command or can execute the program with a call. The utility prompts you for the Userid:Password string, and you should respond using the proper upper/lower case characters.
For example, as a TSO command as illustrated in the following example:
READY GENCIMEN Please enter authorization string (Uid:Pwd): userid:password The encoded string is: the-encoded-string READY
To call this program under TSO or ISPF, use the following code:
CALL 'loadlib(GENCIMEN)' Please enter authorization string (Uid:Pwd): userid:password The encoded string is: the-encoded-string
By executing this command, a string of encoded, printable characters are output to your terminal. Copy this string, exactly as it is displayed, placing it after the <LOGON ENCODE=”YES”> tag. Do not use any leading or trailing blanks in this string.
Example:
<LOGON ENCODE=”YES”>gRda8vv3JJqzop=</LOGON>
You can also code the Userid:Password string in the CIMLIST member without first encoding this string:
<LOGON>myid:mypwd</LOGON>
Notice that the ENCODE=”YES” parameter has been omitted from the <LOGON> XML tag when using this form of Userid:Password string. This omision tells CA Vantage SRM that the string is not encoded and is therefore in its raw format of myid:mypwd.
An example of a complete CIMOM Provider entry for a specific Provider might look something like the following code:
<SERVER>ip address or DNS name</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON ENCODE=”YES”>encoded-userid-password</LOGON>
As these same XML tags must be used repeatedly to describe each instance of a CIMOM Provider in your network, these XML tags must be grouped to associate a set of these tags with a specific Provider. This grouping is done by wrapping all of these tags with a <PROVIDER>…</PROVIDER> XML tag pair. In the CIMLIST member, each occurrence of a <PROVIDER>…</PROVIDER> pair uniquely identifies a single instance of a CIMOM Provider in the network as shown in the following example:
<PROVIDER DESC=”your description of this provider”> <SERVER>ip address or DNS name</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON ENCODE=”YES”>encoded-userid-password</LOGON> </PROVIDER>
The <PROVIDER> XML tag has an optional parameter: DESC. The DESC parameter allows you to code a short description of each CIMOM provider instance. This description should be no more than 32 characters long, anything beyond 32 characters are ignored.
CA Vantage SRM currently supports the IBM ESS 2105, IBM TotalStorage DS6000 and DS8000, Hitachi HDS9XXX, and EMC Symmetrix or CLARiiON CIM providers and native HiCommand Device Manager servers. Support for other providers will be released as they become available. Therefore, each instance of a CIMOM Provider is identified by its type, or classification. To identify the type or classification of individual Providers within the CIMLIST member, all instances of a like classification must be grouped together and wrapped by a <CLASS NAME=”type”>…</CLASS> XML tag. The NAME parameter on the <CLASS> XML tag identifies the classification of all the Providers that follow up to the matched </CLASS> terminator. Currently, the only valid values for the NAME parameter are ESS2105, IBMDSxK, HDS9XXX, HICOMMND, and EMCNSS.
For example, if we had two ESS 2105 CIMOM Providers it would look something like the following example:
<CLASS NAME=”ESS2105”> <PROVIDER DESC=”your description”> <SERVER>ip address or DNS name</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON ENCODE=”YES”>encoded-userid-password</LOGON> </PROVIDER> <PROVIDER> <SERVER>ip address2 or DNS name2</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON>userid:password</LOGON> </PROVIDER> </CLASS>
To wrap everything in the CIMLIST member into a package, all of the CIMOM Provider XML must be wrapped by a <CIMPROVIDERS>… </CIMPROVIDERS> pair of XML tags as shown in the following example:
<CIMPROVIDERS> <CLASS NAME=”ESS2105”> <PROVIDER DESC=”your description”> <SERVER>ip address or DNS name</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON ENCODE=”YES”>encoded-userid-password</LOGON> </PROVIDER> <PROVIDER> <SERVER>ip address2 or DNS name2</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON>userid:password</LOGON> </PROVIDER> </CLASS> </CIMPROVIDERS>
You can add comments to your CIMLIST member to document the entries or track changes to the member. As stated previously, any paired XML tags not in the list of reserved tags are ignored, effectively treating them and their contents as comments, but adding different tags is not recommended.
Following are the two recommended ways to document the CIMLIST member with your own comments:
  • Use the <COMMENTS>…</COMMENTS> tag pairs. 
  • Use the standard XML comment statement syntax. An XML comment begins with <!- - and ends with - -> . (The “- -“ that follows the “<!” and precedes the ending “>” consists of two hyphens). All data between the <!- - and - -> is ignored. For example, <!- -what you are reading up to here- -> is in the format of a standard XML comment. 
Other examples follow:
<!--This would be a valid XML comment line --> <!--This is invalid. Ending two hyphens and bracket are missing.
The following example shows how a full CIMLIST member might look like:
<!--This is a standalone comment line --> <COMMENTS> Here I can add my own freeform comments. These can span multiple lines and contain any text you like. </COMMENTS> <CIMPROVIDERS> <CLASS NAME=”ESS2105”> <COMMENTS> This provider is located in the third-floor lab (maintained by Sam @ ext. 1234). </COMMENTS> <PROVIDER DESC=”Third floor ESS2105”> <SERVER>ip address or DNS name</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON ENCODE=”YES”>encoded-userid-password</LOGON> </PROVIDER> <PROVIDER> <SERVER>ip address of DNS name</SERVER> <PORT>5988</PORT> <NAMESPACE>cimv2</NAMESPACE> <DOCUMENT>/cimom</DOCUMENT> <LOGON>userid:password</LOGON> </PROVIDER> </CLASS> <CLASS NAME="HICOMMND"> <PROVIDER DESC="your description for provider 04"> <SERVER>127.0.0.1</SERVER> <PORT>2001</PORT> <LOGON ENCODE="YES">encoded-userid-pswrd-for-provider-04</LOGON> <COMMENTS> This is a HiCommand Device Manager server definition example </COMMENTS> </PROVIDER> </CLASS> </CIMPROVIDERS>
The CIMLIST XML is case-sensitive. Everything in the CIMLIST member should be uppercase with the following exceptions:
  • The description on the DESC parameter of the <PROVIDER> tag can be upper, lower, or mixed case
  • The CIM namespace names must be lowercase:
    • cimv2 for IBM ESS 2105
    • hitachi for Hitachi HDS9XXX
    • emc for EMC Symmetrix and CLARiiON
  • The CIM document name must be lowercase:
    • /cimon for IBM ESS 2105
    • /cimon for Hitachi HDS9XXX
    • /cimon for EMC Symmetrix and CLARiiON
    • Code user id and password exactly as defined to the CIMOM provider, or exactly as presented by the GENCIMEN encoder
    • XML comments can be upper, lower, or mixed case as you see fit
CONFIG - Local PARMLIB Member
The started task requires this member. CONFIG is the supplied default member name. The exact member name is identified in the PARM field of the EXEC statement in the started task JCL (the SAMS procedure). You can modify part of this member to suit your needs.
 
If the member is not present or empty, copy the VNPCONF member from the CCTUSAMP library and rename the VNPCONF member to CONFIG.
For a description of the CONFIG= parameter and the CONFIG member, see Setting System Parameters.
DMSTRIGS - (Optional) Local PARMLIB Member
Use this member for your early filters for CA Disk message automation. The first 72 bytes of each record are tested. Blank positions are skipped and non-blank positions are tested to match the corresponding character in the CA Disk message. Bytes 73-80 should be blank. If the member is not present or empty, copy the sample from the CCTUSAMP library.
DSNEXCL - (Optional) Local PARMLIB Member
This member is obsolete. See the 
INCLEXCL
 member, which now provides the same functionality.
DTOCDEXC - (Optional) Local PARMLIB Member
This member is obsolete. See the 
INCLEXCL
 member, which now provides the same functionality.
DTOCPEXC - (Optional) Local PARMLIB Member
This member is obsolete. See the 
INCLEXCL
 member, which now provides the same functionality.
DTOCVEXC - (Optional) Local PARMLIB Member
This member is obsolete. See the 
INCLEXCL
 member, which now provides the same functionality.
EXCLUDE - (Optional) Local PARMLIB Member
This member is obsolete. See the 
INCLEXCL
 member, which now provides the same functionality.
FILTMPM1 - (Optional) Local PARMLIB Member
The Tape Resource Option can present error information that is collected about tape media for any user-defined VOLSER range of cartridges. You can define as many volumes ranges as necessary by editing the filter statements in FILTMPM1 member in your PARMLIB. You can specify separate volume ranges for temporary and permanent errors.
If the member is missing or empty, copy the sample from the CCTUSAMP library. Verify that it specifies filter statements appropriate to your installation.
The member contains two sets of filters, one for temporary and one for permanent errors.
These filter members define summaries using statements:
SET_SUM_LABEL= SET_SUM_FILTER=
A maximum of 1000 such statements is allowed.
FILTRMnn - (Optional) Local PARMLIB Members
These members are used by the DFSMSrmm interface to create summaries that are based on tape volume grouping. Use the FILTRM
nn
 members in the CCTUSAMP library as a starter set.
For more information, see Configure for DFSMSrmm.
These filter members define summaries using statements:
SET_SUM_LABEL= SET_SUM_FILTER=
A maximum of 1000 such statements is allowed.
FILTTLxx - (Optional) Local PARMLIB Members
These members are used by the CA TLMS interface to create summaries that are based on tape volume grouping. Use the FILTTL
nn
 members in the CCTUSAMP library as a starter set.
For more information, see Configure for CA TLMS.
These filter members define summaries using statements:
SET_SUM_LABEL= SET_SUM_FILTER=
A maximum of 1000 such statements is allowed.
FILTVInn - (Optional) Local PARMLIB Members
These members are used by the Tape Resource Option to create summaries that are based on TMC tape volume grouping. Use the FILTVI
nn
 members in the CCTUSAMP library as the starter set.
For more information, see Configure for CA 1.
These filter members define summaries using statements:
SET_SUM_LABEL= SET_SUM_FILTER=
A maximum of 1000 such statements is allowed.
FILTZAnn - (Optional) Local PARMLIB Members
These members are used by the Tape Resource Option to create summaries that are based on ZARA tape volume grouping. Use the FILTZA
nn
 members in the CCTUSAMP library as the starter set.
For more information, see Configure for ASG-Zara.
These filter members define summaries using the following statements:
SET_SUM_LABEL= SET_SUM_FILTER=
A maximum of 1000 such statements is allowed.
FIXCDS - Sample Member
This member contains the DFSMShsm FIXCDS JCL to be used for ACTIONS in the Audit of the HSM MCDS, BCDS, and OCDS control data sets. Copy the member FIXCDS from the CCTUSAMP library to your JCLLIB data set and customize the member by including a JOB statement.
HSMCMDS - (Optional) Local PARMLIB Member
Use this member to contain DFSMShsm commands you use from the Windows Client or Web Client. If the member is missing or empty, copy the sample from the CCTUSAMP library. The list in the CCTUSAMP library might change in upgrades or new versions of the system. Customize this list to your needs by removing, editing, or adding appropriate commands.
HSMPATCH - (Optional) Local PARMLIB Member
This
 
member contains the DFSMShsm PATCH commands to be used by the user interfaces. If the member is missing, copy it from the CCTUSAMP library. If changes are needed, customize this list with commands to meet your needs by removing, editing, or adding appropriate commands.
HSMTRIGS - (Optional) Local PARMLIB Member
Use this member for your early filters for DFSMShsm message automation. The first 72 bytes of each record are tested. Blank positions are skipped and non-blank positions are tested to match the corresponding character in the HSM message. Bytes 73-80 should be blank. If the member is missing or empty, copy the sample from the CCTUSAMP library.
INCLEXCL - Local PARMLIB Member
The INCLEXCL member in your local PARMLIB is used to contain optional include-exclude lists for various objects and functions. Use the Host Configuration Client to update these lists as needed. You can also use TSO/ISPF or other editors, but because they do not know the syntax rules, you might unknowingly introduce errors.
If you run multiple CA Vantage SRM systems and each requires a different configuration (for example, different system parameters in VKGPARMS, different INCLEXCL lists, and so on) you can configure all of them in one local parmlib and you can distribute the parmlib data set to your other systems.
For more information, see Configure PARMLIB Member CONFIG.
This member contains all includes/excludes previously contained in these members: CATEXCL, CATINCL, DSNEXCL, DTOCDEXC, DTOCPEXC, DTOCVEXC, EXCLUDE, MCDAUDIT, VOLEXCL, and VOLINCL.
The “POOLDEF
n
” PARMLIB member continues handling Storage Group exclusions. For more information, see 
POOLDEFS - (Optional) Local PARMLIB Member
.
Include/exclude support is also provided for the following functions:
  • Audit of BCDS (created by script AUDITBCD)
  • VSAMVVDS Extract (created by script VSAMVVDS)
  • Duplicate Data sets (created by script DUPEDSNS)
If member INCLEXCL does not exist, it is automatically created whenever a function using one of the include/exclude lists is started. That is, the content of each old member name is read, and automatically converted to a section within this new member. This conversion usually occurs only once. (If you delete the INCLEXCL member for some reason, it will be re-created the next time any include/exclude list is needed.)
If you do not want your existing include/exclude members to be converted automatically, copy the INCLEXCL member from the CCTUSAMP library to your local PARMLIB. The sample defines null lists for all the various functions. You must then manually update the lists to meet your needs.
The INCLEXCL member is divided into section names, where each section has its own includes and excludes in the format:
INCL= EXCL=
These can start in either column 1 or 2. If an asterisk (*) appears in column 1 of such a statement, it is treated as a comment.
If this member is customized through the Host Configuration Client, any INCL= or EXCL= statement that is 
commented out
 (that is, it starts with *INCL, *EXCL, *NCL or *XCL) is preserved, such that it can easily be 
uncommented
 again. However, any other comment statement within the list of includes and excludes are skipped and never written back as part of the INCLEXCL member.
Include-Exclude Processing Logic
The processing logic for Include-Exclude lists is as follows. If there are any exceptions to the standard processing logic, they are noted under the applicable section names.
  1. You might specify complete names, pattern names, or both, for the entries you want to include or exclude.
    For more information, see Wildcard Characters and Pattern Strings.
  2. INCL= entries determine the scope of what is processed.
    If you do not provide any INCL= entries, standard processing functions as if you specified INCL=/ which means all entries are to be included. (The forward slash is a wildcard character that causes comparison to the input string to terminate at the previous character. When used in the first position, all entries match the pattern.) This default relieves you from the need to configure every Include-Exclude list for processing to start. If you specify one or more INCL= entries, those entries determine the scope of what is processed. That scope is further limited by the EXCL= entries, if any are specified. 
  3. EXCL= entries override the scope of the INCL= entries.
    Excludes override includes. Includes never override excludes. If you do not provide any EXCL= entries, all the included entries are processed; that is, there is no default entry to be excluded.
  4. The order of INCL= and EXCL= statements is not functionally important.
    All includes are treated as one list, which determines the processing scope. All excludes are treated as a second list, which overrides the scope of the include-list.
In the following Include-Exclude example, the two INCL= statements determine the scope, which is that all volumes starting with VOL0 and all volumes starting with VOL10 is processed. The two EXCL= statements narrow the scope by excluding volumes VOL001 and VOL002.
INCL=VOL0/ EXCL=VOL001 EXCL=VOL002 INCL=VOL10/
The following sections define each INCLEXCL section name and its function.
START-ARCHIVED-CAT - Archived Data Sets Not Archived to CA Disk
Use this section to specify catalog names that you want the system to include or exclude from the audit. Use the pattern-matching (wildcard) characters in the catalog names to include or exclude.
START-AUDITBCD-DSN - Audit of BCDS
Use this section to define data set names that you want the system to include or exclude from the Audit of BCDS. Use the pattern-matching (wildcard) characters in the data set names to include or exclude.
START-AUDITMCD-DSN - Audit of MCDS
Use this section to define data set names that you want the system to include or exclude from the Audit of MCDS. Use the pattern-matching (wildcard) characters in the data set names to include or exclude.
START-AUDITMCD-TYPE - Audit of MCDS
Use this section to define what type of Audit of MCDS you want to perform. You can select the following types:
  • FULL
    Complete audit
  • RECALL
    Audit of recalled data sets
  • ML1
    Audit of ML1 data sets
  • ML2
    Audit of ML2 data sets
START-AUDITOCD-TAPE - Audit of OCDS
Use this section to define tape volumes that you want the system to include or exclude from the Audit of OCDS. Use the pattern-matching (wildcard) characters in the tape volumes to include or exclude.
START-BACKEDUP-DSN - Data Sets Not Backed Up by DFSMShsm(Dsnames checked)
Use this section to define data set names that you want the system to include or exclude from the audit. Use the pattern-matching (wildcard) characters in the data set names to include or exclude.
START-BACKEDUP-VOL - Data Sets Not Backed Up By DFSMShsm
Use this section to define volumes that you want the system to include or exclude from the audit. Use the pattern-matching (wildcard) characters in the volumes to include or exclude.
START-DSNCTLG-CAT - Audit of Cataloged Data Sets
Use this section to define the catalogs to include or exclude from the Audit of Cataloged Data Sets. Use the pattern-matching (wildcard) characters in the catalog names to include or exclude.
START-DSNDISK-DSN - Disk Data Sets without Backup(Dsnames checked)
Use this section to define data sets that you want the system to include or exclude from the audit. Use the pattern-matching (wildcard) characters in the data set names to include or exclude.
START-DSNDISK-VOL - Disk Data Sets without Backup
Use this section to define volumes that you want the system to include or exclude from the audit. Use the pattern-matching (wildcard) characters in the volume names to include or exclude.
START-DSNUCTL-DSN - Audit of Uncataloged Data Sets
Use this section to define data set names that you want the system to include or exclude from the Audit of Uncataloged Data Sets. Use the pattern-matching (wildcard) characters in the data set names to include or exclude.
START-DSNUCTL-VOL - Audit of Uncataloged Data Sets
Use this section to define volumes that you want the system to include or exclude from the Audit of Uncataloged Data Sets. Use the pattern-matching (wildcard) characters in the volumes to include or exclude.
START-DTOCDEXC-DSN - DTOC Data Sets
Use this section to define data sets that you want the system to include or exclude from all the DTOCs. Use the pattern-matching (wildcard) characters in the data set names to include or exclude.
START-DTOCPEXC-POOL - DTOC Pools
Use this section to define storage group (pool) names that you want the system to include or exclude from the DTOCs for pools. Use the pattern-matching (wildcard) characters in the storage group (pool) names to include or exclude.
START-DTOCVEXC-VOL - DTOC Volumes
Use this section to define volumes that you want the system to include or exclude from all the DTOCs. Use the pattern-matching (wildcard) characters in the volume names to include or exclude. This section narrows the scope of volumes as defined by the START-EXCLUDE-VOL section. It does not expand it.
START-DUPEDSNS-VOL - Duplicate Data Sets
Use this section to define volumes that you want the system to include or exclude from the Duplicate Data sets. Use the pattern-matching (wildcard) characters in the volumes to include or exclude.
The volumes in this list act as a "filter" on the duplicate data set name entries in the DTOC. For example, if a data set name was found on multiple volumes and one of those volumes is excluded, the remaining duplicate data set name entries - possibly only one - is still listed in the DUPEDSNS object.
An alternative would be to add volumes to the START-DTOCVEXC-VOL DTOC Volumes list that have the most potential for duplicate data sets (that is, multiple SYSRES volumes) so they can be excluded from the DTOC scan.
START-DFSMS-STOR-GR - SMS Storage Groups
Usually CA Vantage SRM should see all online volumes that are the default. But if you want to exclude any, there are three ways to do so. You can place volumes to exclude in the Include-Exclude List for Online/Offline Volumes, device numbers to exclude in the Include-Exclude List for Online/Offline Devices (CUAs), or DFSMS storage groups to exclude in the Include-Exclude List for DFSMS Storage Groups. Either list by itself is sufficient to indicate which volumes are to be processed, so it is easiest to use one list or the other. However, all three lists can be used simultaneously, but a clear understanding of the processing is needed.
If you use INCL=/ in the START-DFSMS-STOR-GR section, only SMS volumes are included. If you leave the START-DFSMS-STOR-GR section empty, both SMS and non-SMS volumes are included. The include criteria in the START-DFSMS-STOR-GR section also apply to the DASDUCBS, LSPACEPO object. The scope of disk ranges is changed. For more information, see Exclude Volumes.
START-EXCLUDE-DAYS - Dates to Exclude Processing
(Typically these dates are holidays and weekends.) Use this section to define days or dates that you want the system to use to exclude scripts from giving control to the Event Procedure or for use by applications outside CA Vantage SRM address space. You may use pattern-matching (wildcard) characters in the dates or days.
START-EXCLUDE-CUA - Online/Offline Devices
Use this section to define device addresses that you want the system to include or exclude when scanning volumes (devices) for various functions. The purpose for this section is the same as the 
START-EXCLUDE-VOL
 section, except that it excludes volumes that are based on the device address (CUA or CCUU) instead of volume names. You may use pattern-matching (wildcard) characters in the device addresses to include or exclude. Any device address that is excluded by these tests is treated as logically offline to the system functions that scan for online volumes. (The VSAMVVDS script does not use this list. It uses its own specific list, which is the 
START-VSAMVVDS-VOL
 section).
START-EXCLUDE-VOL - Online/Offline Volumes
Use this section to define volumes that you want the system to include or exclude when scanning volumes for various functions. Use the pattern-matching (wildcard) characters in the volume names to include or exclude. Any volume that is excluded by these tests is treated as logically offline to the system functions that scan for online volumes. (The VSAMVVDS script does not use this list. It uses its own specific list, which is the START-VSAMVVDS-VOL section).
START-RAID-INTERVAL RAID - Interval Collection Objects
Use this section to define which RAID interval collection objects you want to include or exclude from RAID interval collection. If this section is not defined or has no includes or excludes, then RAID interval collection functions as before and all RAID interval objects are built at expiration of their various intervals. If you identify one or more objects to be included, then only those objects that are included are built at RAID interval collection. Likewise, if you identify one or more objects to be excluded, only those specific objects are excluded from RAID interval collection, all others are included. Optionally use pattern-matching (wildcard) characters in the object names to be included or excluded. Specify the object name to include or exclude the following objects:
 
Object Names
 
 
Titles
 
OBJ02122
IBM ESS Volumes
OBJ02129
IBM ESS Raid Ranks
OBJ02120
IBM ESS SSID
OBJ02121
IBM ESS Logical Paths
OBJ02119
IBM ESS Subsystems
OBJ02150
IBM ESS PPRC Information
OBJ02226
Parallel Access Volumes
HTCVOLS
Hitachi Volumes
HTCSSID
Hitachi Logical Subsystems
OBJ02232
Hitachi Subsystems
OBJ02151
Hitachi PPRC Information
STKVOLS
STK SVA Volumes
STKSUBFM
STK SVA Subsystem Family
STKFDV
STK Volume Performance Statistics
OBJ02153
STK SVA PPRC Information
RVAVOLS
RVA Volumes
RVASUBFM
RVA Subsystem Family
RVAFDV
RVA Volume Performance Statistics
SYMVOLS
EMC Symmetrix Volumes
SYMSSID
EMC Symmetrix SSIDs
SYMLPATH
EMC Symmetrix Logical Paths
OBJ02105*
Symmetrix Logical Volume
OBJ02104*
Symmetrix logical to Physical
OBJ02099
EMC Symmetrix Systems
OBJ02100
EMC Symmetrix Channel Directors
OBJ02101
EMC Symmetrix Disk Directors
OBJ02102
EMC Symmetrix Physical Devices
OBJ02103
EMC Symmetrix Logical Volumes
OBJ02225
EMC Symmetrix All Devices
OBJ02227
EMC Symmetrix RDF Devices
OBJ02228
EMC Symmetrix RDF Links
OBJ02229
EMC Symmetrix RDF Groups
OBJ02230
EMC Symmetrix BCV Devices
OBJ02157
EMC VMAX z/OS Device List
OBJ02158
EMC VMAX Logical Devices
OBJ02155
EMC VMAX Logical Devices
OBJ02159
EMC VMAX Back End Devices
OBJ02177
EMC VMAX RDF Remote Logical Devices
OBJ02176
EMC VMAX RDF Remote Groups
OBJ02156
EMC VMAX RDF Groups
  • Objects OBJ02105, OBJ02104, and OBJ02155 are internal and you cannot view these objects.These objects are used to build the other Symmetrix API objects.
  • Includes / excludes apply after the first collection interval expires. That means the first collection is always done for all the objects. 
  • Review the following CA Vantage system parameters for RAID support:
    • RAIDSUPP 
    • HWOBJINC 
    • RAIDONL 
    • RAIDRBLD 
    • RAIDEXCL 
    • EMCINTVL 
    • TSINTVL 
START-VSAMVVDS-VOL - Vsam Data Sets
Use this section to define volumes that you want the system to include or exclude from the Vsam Data Sets. Use pattern-matching (wildcard) characters in the volumes to include or exclude.
START-WARMSTART-OBJ
Use this section to specify LI objects that you want to be check-pointed by the W
armstart 
or
 Checkpoint-restart
 ability. Use pattern-matching (wildcard) characters in the objects to include or exclude.
JCLMLIST - Local PARMLIB Member
The JCLMLIST member in your local PARMLIB is used to associate JCL members with objects, and give descriptions for each. It provides an easy way to organize various (model) JCL members by associating each member with the objects on which it can be used. You no longer need to remember the name and where you saved it, once you have added it to the JCL Model List. Only reference the object in the object tree and associated JCL members can also be listed and accessed.
 For more information, see The JCL Model List.
MCDAUDIT - (Optional) Local PARMLIB Member
This member is obsolete, member INCLEXCL now provides the same functionality. For more information, see 
INCLEXCL
.
MSGTRIGS - (Optional) Local PARMLIB Member
Use this member for your early filters for MVS console message automation. The first 72 bytes of each record are tested. Blank positions are skipped and non-blank positions are tested to match the corresponding character in the console message. Bytes 73-80 should be blank.
There is one special parameter if you have a sysplex where the console messages for all LPARs are being merged, you can choose to filter out only the messages from the local LPAR (beginning in column 1):
LOCAL_MESSAGES_ONLY=YES
If this parameter is not present, the default is to filter out messages from all LPARS:
LOCAL_MESSAGES_ONLY=NO
If the member is missing or empty, copy the sample from the CCTUSAMP library.
PLSCMDS - (Optional) Local PARMLIB Member
Use this member to contain CA Allocate commands that you use from the Windows Client or Web Client. If the member is missing or empty, copy the sample from the CCTUSAMP library. The list in the CCTUSAMP library might change in upgrades or new versions of the system. Customize this list to your needs by removing, editing, or adding appropriate commands.
POOLDEFS - (Optional) Local PARMLIB Member
Use this member to define user-defined storage groups by volume names, patterns, or any other volume attribute, and to assign descriptions to any storage group.
These user-defined storage groups are displayed as USR (user) defined, in contrast to: SMS, MVS, or VAM defined storage groups.
You can also use this member to instruct the system to exclude certain MVS, SMS, or VAM storage groups based on their unit names.
Use the Host Configuration Client to define user-defined storage groups, assign descriptions to any storage group, and to exclude storage groups from the processing.
See the Help text in the Host Configuration Client for further assistance when defining the user-defined storage groups or when descriptions are going to be added to already defined storage groups.
System parameter POOLDEF controls the exact name of this member. For more information, see system parameter POOLDEF in System Parameters. It specifies the last character of the member name. The default is (S), which means the default member name is POOLDEFS.
Example of POOLDEFS Member:
 
POOLDEF NAME=(IBMPOOL),EXTFLT=(FPS00001) DESA=(USR Genned SG IBMPOOL) POOLDEF NAME=(FRAG250),EXTFLT=(FPS00003) DESA=(USR Genned SG FRAG250) DESB=(desc b) DESC=(filter smd06/) POOLDEF NAME=(3380) DESA=(test description a) DESB=(test desc b) DESC=(test desc c) EXCLUDE EXTFLT=(FPSEXCL)
 
Syntax of POOLDEFS Member:
 
  • POOLDEF (Required)
    This command is used to define a user (USR) pool of volumes, or to give descriptions to pools defined within SMS, MVS, or VAM. The command name must start in position 1 and must be followed by 1 blank. The POOLDEF command has the following parameters:
    • NAME=(
      poolname
      ) (Required)
      This parameter specifies the name of the pool. The name must be within parentheses, must not contain any blanks, and be a maximum of 8 characters. It must immediately follow the POOLDEF command. If the POOLDEF command is being used merely to associate descriptions with an existing SMS, MVS, or VAM pool (rather than to define a USR pool), the NAME= parameter must specify the name of an existing SMS, MVS, or VAM pool.
    • EXTFLT=(
      filtername
      ) (Required for USR defined pools)
      When defining a user (USR) pool, this parameter specifies the name of a filter in the External Filter Library. When the named filter is applied to the Volumes object, it selects the volumes that are to be included in the pool. The filtername must follow the naming standards for members of a PDS, and must be specified within the parentheses. When adding descriptions to an SMS, MVS, or VAM pool, the EXTFLT= parameter must be omitted.
    • DESA=(
      description part A
      ) (Optional)
    • DESB=(
      description part B
      ) (Optional)
    • DESC=(
      description part C
      ) (Optional)
    Each of the three description fields is optional. Specify a text string of 1 to 25 characters within parentheses. Use as many of the description parameters to give an adequate descriptive text to the named pool.
  • EXCLUDE (Optional)
    This command is used to indicate which pools (storage groups) are to be excluded from the Storage Groups object. The command name must start in position 1 and must be followed by 1 blank. The EXCLUDE command has the following parameter:
    EXTFLT=(
    filtername
    )
    When excluding pools from the Storage Groups object, this parameter specifies the name of a filter in the External Filter Library. When the named filter is applied to the names of the Storage Groups, it excludes the unwanted pools. The 
    filtername
     must follow the naming standards for members of a PDS, and must be specified within the parentheses.
Examples of External Filter Members for the POOLDEFS Example Above:
 
Notice the special syntax of the TITLE statement in the following examples. The first 8 characters after TITLE= must specify the object name. It must be LSPACE (with 2 trailing blanks) for filter members that are referenced on POOLDEF commands (for defining USR pools). It must be POOLESOU for filter members that are referenced on the EXCLUDE command (for excluding pools).
 For additional information, see 
External Filters
.
  • Member=(FPS00001)
    <GENERAL> EVENT_TYPE=FILTER TITLE=LSPACE Pool Name IBMPOOL <EVENT_PROCEDURE> SET_FILTER=('VENDOR' EQ IBM)
  • Member=(FPS00003)
    <GENERAL> EVENT_TYPE=FILTER TITLE=LSPACE Pool Name FRAG250 <EVENT_PROCEDURE> SET_FILTER=('FRINDX' GT 250)
  • Member=(FPSEXCL)
    <GENERAL> EVENT_TYPE=FILTER TITLE=POOLESOUExclude defs for Pools <EVENT_PROCEDURE> SET_FILTER=ESOPOOL EXCL (VIO,SYSSQ,SYSALLDA)
RCYCDEV - (Optional) Local PARMLIB Member
Use this member to specify default storage capacities of your various types of tape devices. The recycle simulation function uses these capacities to calculate the number of new tapes that are necessary to recycle a range of tapes. If the member is missing or empty, copy the sample from the CCTUSAMP library. You can modify the values in this table to reflect the devices present at your installation.
The table contains the following columns of data:
  • Column 1 = Device name (1 to 8 characters)
  • Column 10 = Capacity of the device in Megabytes (8 numeric digits). For this table, 1 MB = 1024 * 1024
  • Column 19 = Comments (1 to 28 characters)
Lines beginning with an asterisk (*) are comments and are ignored.
SUMMARY - (Optional) Local PARMLIB Member
Use this member to customize your summary reports. If the member is missing or empty, copy the sample from the CCTUSAMP library.
VAMSPARE - (Optional) Local PARMLIB Member
Use this member to define candidate volumes to be added dynamically to a CA Allocate Storage Group in violation.
  • Column 1 = Volume name or volume pattern that can be added to a CA Allocate storage group
  • Column 10 = Free space percentage that CA Allocate is to maintain on the volume when added to its storage group
  • Column 13 = Description of the volume name or volume pattern
If the member is missing or empty, copy the sample from the CCTUSAMP library.
VANEDM00 - (Optional) Local PARMLIB Member
Use this member if you audit CA Disk ARCHVOLS or HSM OCDS volumes against the TMC.
For more information, see Configure Tape Resource Option and the description of the VANEDM00 system parameter.
If the member is missing or empty, copy the sample from the CCTUSAMP library.
VKGPARMS - (Optional) Local PARMLIB Member
Use this member to contain your local system parameter values, values that override system defaults to tailor the system to your needs. If the member is missing or empty, copy the sample from the CCTUSAMP library.
For a description of each parameter, see System Parameters.
VNEMCGKS - (Optional) Local PARMLIB Member
Use this member to specify devices that are labeled as 'gatekeepers' used by EMC API calls to communicate with EMC VMAX Disc Arrays.
VOLEXCL - (Optional) Local PARMLIB Member
This member is obsolete. Member INCLEXCL now provides the same functionality. For information, see member 
INCLEXCL
.
VOLINCL - (Optional) Local PARMLIB Member
This member is obsolete. Member INCLEXCL now provides the same functionality. For information, see member 
INCLEXCL
.
VPVVDSSZ - (Optional) Local PARMLIB Member
Use this member to specify the VVDS size in tracks, VTOC start cylinder, VTOC size in tracks, and VTOC index size in tracks, when a spare volume is reinitialized and added to an SMS storage group. If the member is missing or empty, a default of 10 tracks is used for the VVDS, 1 is used for VTOC start cylinder, and 15 is used for VTOC and VTOCIX tracks. If different sizes are needed, or various sizes depending on the attributes of the storage group or spare volume, copy the sample from the CCTUSAMP library, and edit it as described within the member itself.