The CMAS, which is a CICS® Transaction Server for z/OS® Version 3 Release 1 system, provides most of the functions of CICSPlex® SM.
To set up a CMAS, you need to:
- Add CICS resource definitions for the CMAS
- Because the CMAS is a CICS system, it requires resource definitions
to be created. These definitions are provided with CICSPlex SM and can be applied
using the resource definition utility, DFHCSDUP. The resources include:
- CICSPlex SM resource groups
- A file definition for the data repository
- CMAS program definitions
- CMAS transaction definitions
- CMAS group list
No tailoring of these resources is required or expected. However,
you are required to make some changes to the tables DFHPLT and DFHSRT. These
changes are detailed in CICSPlex SM Managing Workloads.
- Define common data spaces
- In each MVS/ESA environment in which a CMAS is to be installed,
a minimum of five common data spaces (and a maximum of 45) is required. You
are recommended to begin by defining 10 common data spaces, and to add more
if necessary.
- Provide CMAS VTAM® definitions
- If you are defining multiple CMASs, CMAS-to-CMAS links require each
CMAS to have a VTAM application definition.
Full details of necessary
changes to the MVS/ESA and VTAM environments are provided in CICS Transaction Server for z/OS Installation Guide.
- Create the CMAS data repository
- Each CMAS requires a data
repository, which can be created using the sample JCL created during the installation
process. The data repository must be initialized before it can be used.
- Decide how to start the CMAS
- Like the CAS, the CMAS can be started at MVS™ IPL time, as a started task, or as a batch
job. You are recommended to start the CMAS at MVS IPL time, so that it is part of the MVS/ESA start-up procedure and treated as a permanent part of the environment.
This is much more efficient than starting and stopping the CMAS throughout
the day. It also ensures that the CMAS is active before any MAS attempts to
connect to it. A sample start-up procedure for the CMAS is generated during
the installation process.
CICSPlex SM supplies a batched repository-update facility that you can use to make bulk changes
to a CMAS’s data repository. You
can invoke this facility from the Web User Interface, the EUI, the CICSPlex SM API
or from a batch utility. When using the batched repository-update facility,
you supply an input file of commands that are applied to the data repository.
Valid commands are:
- CONTEXT
- which identifies whether subsequent commands relate to the CMAS whose
repository is being updated, or to a CICSplex that it maintains.
- CREATE
- which adds a new record to the data repository.
- UPDATE
- which alters an existing record in the data repository.
- REMOVE
- which deletes an existing record from the data repository.
- LIST
- which creates a list of all records in the data repository.
- DUMP
- which creates a list of all records in the data repository and prefaces
each entry in the list with a Create command. The output from the Dump command
can therefore be used as input to a different CMAS data repository.
- MAPLEFT
- which displays a map of definitions in the data repository to the left
of the starting point.
- MAPRIGHT
- which displays a map of definitions in the data repository to the right
of the starting point.
For example, a typical command file for input to the batched repository-update facility would contain
a Context command, followed by multiple Create commands. An example command
file is supplied with the CICSPlex SM Starter Set. Detailed information about the batched repository-update facility is
supplied in CICSPlex SM Administration.
[[ Contents Previous Page | Next Page Index ]]