|
|
|
Management Services has the following data sets:
Is the SMP DLIB that contains the same distributed NCL procedures as the CC2DEXEC run-time library.
Type: Distribution
Is the SMP DLIB that contains the same members as the CAIJCL installation data set.
Type: Distribution
Is the SMP DLIB that contains the same information as the CC2DMAC library.
Type: Distribution
Is the SMP DLIB that contains the modules used by SMP to build the load modules in the run-time LOAD libraries.
Type: Distribution
Is the SMP DLIB that contains the same information as the CC2DSAMP library.
Type: Distribution
Is the SMP DLIB that contains the same information as the CC2DVSMI library.
Type: Distribution
Is the SMP DLIB contains the same information as the CC2DXML library.
Type: Distribution
Is part of the Alert Monitor and enables you to view alerts that have been created in the past. Alerts in the history file can contain notes showing manual and automated actions that were performed for the alert.
Type: Local VSAM
Run-time DDname: ALERTH
Is the PDS that contains distributed NCL procedures and is concatenated after the TESTEXEC data set in DD COMMANDS. Collectively these data sets make up the procedure library.
Members in CC2DEXEC must not be changed.
Important! If modifications are required, copy the distributed member to the TESTEXEC data set for the region for modification.
Type: Run-time PDS (external)
Run-time DDName: COMMANDS
Is the PDS that contains the installation and maintenance JCL members.
Type: Run-time PDS
Is a PDS run-time load library that contains various NetView exits. Include in the STEPLIB DD concatenation for NetView if you are using the NVC component.
If your auditors want CA Auditor Product Descriptor Module (PDM) to know of your product running on your system, include this library in the system LNKLST.
Type: Run-time PDS
Is the PDS into which the TSO interface load modules are linked during installation.
Type: Run-time PDS (external)
Run-time DDName: STEPLIB (TSO)
Is the load library. This load library must be APF-authorized. This means that the run-time load library, as referenced by the STEPLIB DD statement, must be defined in the operating system APF list. If no STEPLIB DD statement is used, the program load modules must reside in one of the existing authorized LNKLST libraries. Ensure that these requirements are met before attempting to start your region.
You can install your product into its own installation load library and copy the load modules across to the system load library.
The library also contains the CA Datacom load modules for ReportCenter.
Type: Run-time PDS
Run-time DDName: STEPLIB
Is a separate PDS run-time load library containing modules that must be executed from the LPA. The data set contains only CNMNETM plus its aliases.
Type: Run-time PDS
Is the PDS that contains macros and copybooks for the sample assembler programs, which are also distributed in source form in the AC2DMAC library.
Type: Run-time PDS (external)
Is the PDS that contains various sample exits, utilities, source code, and JCL members. The members contain documentation.
Type: Run-time PDS (external)
Is the interim staging data set to which MODS, OSCNTL, PANEL, NETINFO, ICOPANL, and RAMDB files are unloaded. They are later copied to the run-time MODSDIS, OSCNTL, PANLDIS, NETINFO, ICOPANL, and RAMDB files.
Type: Staging
Is the PDS that contains the XML data used by CA MSM.
Type: Run-time PDS (external)
Is the data set the region uses for a formatted dump.
Type: SYSOUT
Run-time DDName: FMTDUMP
Is the data set the region uses for the hardcopy log.
Type: SYSOUT
Run-time DDNames: LOG1 through LOG9
Is the VSAM data set that contains the MODS database. The region uses the MODS database for control information for processing. The database includes standard message information, online help text, menus, Print Services Manager (PSM) definitions, and Report Writer definitions.
Type: Shared run-time VSAM
Run-time DDName: MODSDIS
Note: For information about the allocation and usage of MODS databases, see the Managed Object Development Services Guide.
Is a data set that has the same functions as MODSDIS and is intended for your own records. You can have separate records for test and production environments.
Type: Local VSAM
Run-time DDName: MODSUSR
Is the VSAM data set that contains various error codes (for example, 3274 error codes and SNA sense codes).
Type: Shared run-time VSAM
Run-time DDName: NETINFO
Are the VSAM data sets to which the LOGPROC NCL procedure ($LOPROC) in the region writes all activity log messages for subsequent online browsing from a terminal.
Type: Local VSAM
Run-time DDNames: NMLOG01 through NMLOG03
Is the VSAM data set used by the region to store MDO definitions and compiled object class specifications.
Type: Shared run-time VSAM
Run-time DDName: OSCNTL
Is the VSAM data set that stores full-screen panels defined by using the online editor. NCL procedures and Panel Services use these panels.
Your product provides the facility for multiple panel data sets per region. The data sets can be concatenated, and different data sets can be made available to different users.
Type: Shared run-time VSAM
Run-time DDName: PANLDIS
Is a data set that has the same functions as PANLDIS and is intended for your own records. You can have separate records for test and production environments.
Type: Local VSAM
Run-time DDName: PANLUSR
Is the data set (dsnpref.OPB9.PARMLIB) that contains the setup parameters for the product components in a region.
Type: Shared PDS
Run-time DDNames: DSIPARM and SXCTL
Is the data set used to store printed output handled by the PSM facility.
Type: Local VSAM
Run-time DDName: PSPOOL
Is the data set used to store analysis output from the REXX Analyzer.
Type: Local PDS
Is the data set used to store the report generated by the REXX Analyzer.
Type: Local sequential
Is the data set (dsnpref.rname.TESTEXEC) that is concatenated as the first of the data sets forming the COMMANDS DD. The data set is used for the following procedures:
The setup process allocates TESTEXEC as a local data set.
Type: TESTEXEC
Run-time DDName: COMMANDS
Is the User ID Access Maintenance Subsystem (UAMS) data set containing the security definitions for users authorized to use the region.
In a shared DASD environment with multiple regions, perhaps connected by INMC, you can define one UAMS data set that all regions can share. The regions use reserve and release logic during accesses, and ensure the integrity of the data set in a shared DASD environment. If only one data set is used, operators using ROF to connect to another region have identical authority and privileges in both regions. This situation may not be satisfactory if one region is dedicated to testing and the other to production. In this case, use two UAMS data sets, allowing a user to be profiled differently in the two regions.
If the installation uses a security exit to replace the UAMS component entirely, the UAMS data set is not required.
When logging on or changing UAMS records, a RESERVE is issued for NMUAMS. The RESERVE has the following attributes:
If the sysplex is in a STAR configuration, you can convert this RESERVE to a GRS global ENQ. If the sysplex is a RING configuration, do not convert the RESERVE.
Type: Shared run-time VSAM
Run-time DDName: USERIDS
Is the data set used by the region for internal processing activities and as a general database for use by the various products. The VFS is a database used to store many record types and must not be shared across regions.
Type: Local VSAM
Run-time DDName: VFS
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |