aggregated package
An aggregated package is a file that comprises several single maintenance packages (nested packages).
automatic ID
The automatic ID is the value of the MSMID variable. This is part of the snapshot and is unique for every deployment.
CA CSM application server
The CA CSM application server is the CA CSM Tomcat region that supports the CA CSM application code.
CA Datacom/MSM server
The CA Datacom/MSM server is a server that lets workstation-based applications use the CA Datacom/MSM database.
CA Recommended Service (CA RS)
CA Recommended Service (CA RS) is a set of maintenance packages that have been tested in a mainframe integrated system test environment. We recommend that you install CA RS maintenance to keep your products up-to-date. To keep yourself informed about new CA RS maintenance available, download (manually or automatically) all CA RS files that list published maintenance for that CA RS level.
CAICCI system ID
The CAICCI system ID is a unique name for a system that is part of a CAICCI network. If you do not specify one, CA CSM obtains it using a validate action.
configuration category
A configuration category is a group of variables for a configuration. The top root level is a category that encompasses all categories and variables.
configurations
A configuration is a CA CSM object that you create to tailor your deployed software and make it usable in your environment. A configuration contains the profiles, variables, and resources specific to your environment.
confirm
Confirms that the deployment is complete. This is the final action by the user. A deployment is not completed until it is confirmed. After it is confirmed the deployment moves to the Confirmed deployment list.
contact system
The contact system defines which system the deployment is unpackaged on. That is, which system CAICCI is spawned to run the unpackaging.
custom data set
A custom data set is a data set that contains either a z/OS data set or USS path.
data destination
A data destination must be defined for every system. The data destination is how you tell CA CSM which technique to use to transport the deployment data to the remote system. Data destinations are assigned to non-sysplex systems, sysplexes, and shared DASD clusters. Data destinations are named objects, and thus can be assigned to multiple entities in the system registry and have their own independent maintenance dialogs.
data set name mask
A data set name mask is a unique name that identifies each data set. It consists of one or more qualifiers separated by periods, and has a maximum input length of 64 characters, including the periods. When the data set name mask is translated, it has a maximum length of 44 characters including the periods.
deploy
The deploy functionality combines the snapshot, transmit, and deploy actions into one action, letting you copy your CA CSM product onto systems across your enterprise. For example, you can send one or many products to one or many systems by copying it to a shared DASD or through FTP.
deployment
A deployment is a CA CSM object that you create to deploy libraries and data sets using a process that copies target libraries defined to SMP/E and user data sets across both shared DASD and networked environments.
directory path
The root directory path is the base directory to which the FTP server is allowed access. The FTP server will be allowed to create files to or read files from this directory and any of its subdirectories. The directory path is a USS path name, it consists of one or more directory leaves separated by forward slashes, and has a maximum input length of 255 characters including slashes. When the directory path is translated, it has a maximum length of 255 characters.
File Transfer Protocol (FTP)
File Transfer Protocol (FTP) is a protocol for transfer of files from one computer to another over the network.
FIXCAT
FIXCAT (fix category) associates a maintenance package to one or more categories of PTFs (for example, installation, function, z/OS version, or communication).
FTP port
An FTP port is the point of connection through which files are transferred. The default is 21.
gen level
A gen level is the innermost level in the product list in the left pane under the release level of a product. Selecting a gen level in the left pane displays the available base installation packages and other product components in the right pane. Gen levels are preceded with the following icon: 
GIMUNZIP volume
The GIMUNZIP volume is a data destination setting in CA CSM that specifies the GIMUNZIP volume to direct GIMUNZIP to use GIMUNZIP control files to unpack the data sets onto the specified volume. Use this setting when your environmental setup requires that the libraries that are deployed and copied by CA CSM are directed to a particular volume on your target system.
GIMZIP
GIMZIP is an IBM utility that creates portable packages of software with a suffix of z.
landing directory
The landing directory is where the data is temporarily placed during a deployment.
managed product USS file system
A managed product USS file system is a collection of USS file systems that are used by SMP/E environment under the control of CA CSM. CA CSM creates managed product USS file systems during a base installation and optionally during migration of an SMP/E environment.
methodology
A methodology is the process by which data sets are named on the target system. It provides the how of a deployment. It is a named object with a description that is assigned to an individual deployment.
monoplex
A monoplex is a sysplex that has only one member system and minimally a single coupling facility. Currently, a monoplex is tracked in the same manner as a sysplex, except the sysplex name shown in the web-based interface is actually the monoplex system name.
MSM Common Services
The MSM Common Services (CETN500) is a contributed component of CA Common Services for z/OS that consists of the Software Deployment Service (SDS) and the Software Configuration Service (SCS).
MSMCAUX
MSMCAUX is the JCL procedure that is used to start the auxiliary address space. CA Common Services for z/OS that CA CSM uses includes a sample procedure in the member MSMCAUX of the CCS CAIPROC (CCShlq.CAIPROC) library. You must copy this procedure to a system PROCLIB that z/OS START commands use and modify it to suit your installation environment. The MSMCAUX sample member describes the changes that are required. Do not start the MSMCAUX procedure manually. The MSMCAUX procedure is started by the SCS address space (MSMCPROC).
MSMCPROC
MSMCPROC is the JCL procedure that is used to start the SCS address space. CA Common Services for z/OS that CA CSM uses includes a sample procedure in the member MSMCPROC of the CCS CAIPROC (CCShlq.CAIPROC) library. You must copy this procedure to a system PROCLIB that the z/OS START commands use and modify it to suit your installation environment. The MSMCPROC sample member describes the changes that are required.
MSMTC/MSMTCSRV
MSMTC/MSMTCSRV is the job stream or started task associated with the CA CSM application server.
non-sysplex
A non-sysplex is a stand-alone z/OS system that is not part of a sysplex or a monoplex system.
optional variable
An optional variable does not require a value. Some optional variables must be confirmed.
policy
A policy in CA CSM represents a combination of (1) metadata input that identifies the component parts of a product, and (2) user-supplied input that identifies the deployment criteria, such as where it will go and what will it be called.
preview
Preview identifies the deployment by name and briefly states the products, systems, means of transport, target libraries including source, target and resolution, as well as SMP/E environment and snapshot information.
product
A product is a level in the product list in the left pane under the vendor. Selecting a product in the left pane displays product releases in the right pane. Products are preceded with the following icon: 
Product Acquisition Service (PAS)
The Product Acquisition Service (PAS) facilitates the acquisition of mainframe products and the service for those products, such as program temporary fixes (PTFs). PAS retrieves information about products to which your site is entitled. Then it records these entitlements in a software inventory that is maintained on your driving system.
profile/profile occurrence
A profile is a grouping of variables that belong to a subsystem or a component. A profile occurrence is a version of that profile that has been tailored for a specific system. You can have multiple profile occurrences for the same profile on one system.
release
A release is the level in the product list in the left pane under the product. Selecting a release in the left pane displays maintenance packages in the right pane. Releases are preceded with the following icon: 
resolved variable
A resolved variable contains a value and has been confirmed (if required). You can modify a variable that has been resolved.
resource
A resource is a physical or virtual component of a system. Resources include data sets, parameter settings, libraries, files, and operator commands. Dummy resources are temporary resources used during the configuration build or implementation process, or that serve as place holders for tracking purposes.
SCS address space
The SCS address space is a specially defined location where the system registry and commands for interrogating output and console traffic reside within the operating system. The SCS address space provides the services and processing necessary to implement configurations across your targeted z/OS systems. Each target system that is expected to support SCS processing must execute an SCS address space.
SCS address space port
An SCS address space port is the point of connection through which the client communicates with the address space. The default is 49152.
shared DASD clusters
A shared DASD clusters system is a set of systems that shared DASD and it can be composed of sysplex and/or non-sysplex systems. Staging system cannot be part of a shared DASD cluster.
snapshot
A snapshot is a copy of the set of target libraries that CA CSM makes using the IBM utility GIMZIP. CA CSM uses GIMZIP to create a compressed archive of these libraries, including a list of applied maintenance. The SMP/E environment is locked during this archive creation process to verify the integrity of the archived data.
Software Configuration Service (SCS)
The Software Configuration Service (SCS) facilitates the mainframe product configuration from the software inventory of the driving system to targeted z/OS operating systems.
Software Deployment Service (SDS)
The Software Deployment Service (SDS) facilitates the mainframe product deployment from the software inventory of the driving system to the target system. This facilitation includes deploying installed products that are policy-driven with a set of appropriate transport mechanisms across a known topology.
Software Installation Service (SIS)
The Software Installation Service (SIS) facilitates the installation and maintenance of mainframe products in the software inventory of the driving system. This facilitation includes browsing downloaded software packages, managing SMP/E consolidated software inventories on the driving system, and automating installation tasks.
staging system
A staging system is a virtual system that deploys the deployment to the computer where the CA CSM driving system is located. To use a staging system, the CA CSM driving system must be registered in the CA CSM system registry. A staging system can be useful in testing your deployments, and learning deployment in general. It can also be used if your target systems are outside a firewall. For example, deploy to a staging system and then manually copy the deployment to tape.
storage classes
storage classes apply only to SMS-managed data sets and objects. They allow you to define different levels of performance and availability services for your data sets. Using them, you can separate the level of service needed by a data set or object from its physical characteristics. Storage classes can supply such information as attributes for dynamic cache management, sequential data set striping, and concurrent copy.
It is the association of a storage class with a data set or object which causes the data set or object to be SMS-managed. Because of this, such functions as dynamic cache management and sequential data set striping apply only to SMS managed data sets. Data sets may be SMS-managed or non-SMS managed. Objects must be SMS-managed.
symbolic substitution
symbolic substitution, or translation, is a process performed by CA CSM to resolve the mask values specified in the data set name mask and Directory Path, into real names based upon the contents of the symbolic variables at translation time. A CA CSM symbol is defined in the list of symbols. Each symbol begins with an ampersand (&) and ends with a period (.). For example the symbol &LYYMMDD., would be completely replaced with its value at translation time, including the ampersand and trailing period. The trailing period is important and is considered part of the symbolic name.
sysplex
A sysplex (SYStem comPLEX) is the IBM mainframe system complex which is a single logic system running on one or more physical systems. Each of the physical systems that make up a sysplex, is often referred to as a “member” system.
system registry
The system registry is a repository of variable data that all CA CSM managed products share. The system registry repository contains information about the systems that have been defined to CA CSM and selected as a target for deployments and configurations. You can create non-sysplex, sysplex, shared DASD cluster, and staging systems. You can maintain, validate, view, and delete a registered system and you can investigate a failed validation.
task output browser
The task output browser displays the details of finished tasks.
topology
The enterprise system topology can include shared DASD environments, networked environments, and z/OS systems.
transmit
The transmit functionality lets you copy a product onto systems across the enterprise through FTP, in preparation for a subsequent deployment.
Uniform Resource Identifier (URI)
A Uniform Resource Identifier (URI) is a string of characters used to identify a name or a resource on the Internet. Such identification enables interaction with representations of the resource over a network (typically the World Wide Web) using specific protocols. Schemes specifying a concrete syntax and associated protocols define each URI.
For a shared DASD cluster or sysplex, the URI must be the URI of the Contact System.
UNIX System Services (USS) files
For UNIX System Services (USS) files for z/OS systems, there are three types of files system: HFS (Hierarchical File Systems), zFS (zSeries File Systems), and NFS (Network File Systems). USS files are any one, or combination, of these file systems, and start with the root directory, which is denoted by a single forward slash (/).
validation
The validation process is started by the user when they select the Validate button in the Actions drop down for a sysplex system, non-sysplex system, and shared DASD cluster on that system’s System Registry Page (staging systems are not validated). This starts a background security procedure using the CAICCI validation services to validate this system.
VOLSER
A VOLSER is the Volume Serial Number that places the data on an explicit volume.
working set
A working set is a selected group of SMP/E environments with which you want to work. Future displayed information will be based on the working set. For example, maintenance information is shown for the working set. The information is not shown for environments outside the set.
zFS candidate volumes
You can use a zFS candidate volume when your environmental setup dictates that zFS container data sets are directed to the specified volume.
|
Copyright © 2014 CA.
All rights reserved.
|
|