Setting up the MVS environment for CICS
You must perform a number of tasks after you have loaded the elements to DASD and before you run CICS®.
The information about ACF/Communications Server, MVS™, RACF®, and other products given is for guidance only. Always consult the current publications of these products for the latest information.
The term "RACF" is used throughout this information to mean the MVS Resource Access Control Facility (RACF) or any other external security manager that provides equivalent function.
- Authorizing the CICS and CICSPlex SM libraries
The SDFHAUTH, SEYUAUTH, SDFHLINK, and SEYULINK libraries must be APF-authorized. - Authorizing CICS regions to access MVS resources
Protect your data sets, authorize your user IDs and regions and activate your RACF resource classes when you set up your security requirements to run CICS. - Defining the default CICS user ID to RACF
If you intend to use RACF to authorize terminal users to access CICS resources, define a default CICS user ID to RACF and specify it on the CICS system initialization parameter, DFLTUSER. - Installing CICS-required modules in the MVS linklist
There are two categories of modules that are loaded from the MVS linklist. These are CICS- and CICSPlex® SM-supplied modules, and modules of other MVS products, for example, DFSMS. - CICSPlex SM API linklist modules
In each MVS image that contains a CMAS in which you plan to run the CICSPlex SM API, ensure that these required modules are in the correct location. - Defining CICS as an MVS subsystem
You define CICS as an MVS subsystem before you can use any of facilities listed. - Installing the CICS SVCs
Install the current level of the CICS Type 3 SVC, DFHCSVC, and the high performance option (HPO) SVC before you attempt to start a region. - Selecting the high-performance option
The high-performance option (HPO) is for users whose top priority is to optimize terminal response times and maximize transaction throughput. HPO improves performance by reducing the transaction path length; that is, the number of instructions required to service each request. - Defining EYU9XENF as a TSO/E authorized command
Define the EYU9XENF command during set up to streamline problem diagnosis later, if required. - Defining CICS regions as applications to SNA
To use SNA LUs with CICS, ensure that your CICS regions are defined to SNA before you attempt to run them. - Installing CICS modules in the MVS link pack area
How to define the CICS LPA library to your MVS, and how to install and use the CICS modules. - Installing CICSPlex SM modules in the MVS link pack area
There are benefits and points to consider if you use the MVS link pack area (LPA). - Defining CICS IPCS exit control data to MVS
If you use the MVS interactive problem control system (IPCS) to format and analyze CICS system dumps, ensure that the release-specific CICS formatting routines are defined and available to MVS. - Preparing to use the CICSPlex SM IPCS tools
The interactive problem control system (IPCS) provides MVS users with interactive diagnostics of software failures. Before using IPCS, you must update BLSCECT, update library allocations and set SDUMP options. - MVS Program properties table entries
You can optionally define some CICS properties to MVS in the MVS program properties table (PPT). - Configuring MVS workload management for CICS systems
You can use z/OS workload management to manage sysplex resources across MVS subsystems, in parallel with the existing system resource management facilities. - Implementing MVS automatic restart management
You can exploit MVS automatic restart management to implement a sysplex-wide integrated automatic restart mechanism. - MVS cross-system MRO definitions
You can use CICS interregion communication (IRC) for multiregion operation (MRO) between CICS regions across MVS images in a sysplex. - MVS ASREXIT - SYMREC Authorization Exit
A CICS program might call the first failure symptoms component. The component uses the MVS SYMREC macro to write symptom records to the MVS SYS1.LOGREC data set, in addition to, or instead of, a job log. - Setting up VSAM RLS support
These topics provide an overview of each task you need to perform if you want to use VSAM RLS to enable CICS regions to share VSAM data sets. - Console messages
The message domain supports the use of MVS message routing codes in the range 1 to 16 for those messages that are sent to the console. - Defining the logger environment for CICS
CICS uses the MVS system logger for all its logging and journaling requirements. - Unicode data conversion by z/OS
z/OS Unicode services provides support for the conversion of Unicode data (either UTF-8 or UTF-16) to any of the EBCDIC CCSIDs currently supported by CICS. - Applying service to CICS Transaction Server for z/OS
Service material for CICS Transaction Server for z/OS is distributed as APAR fixes and PTFs. - Applying service to CICSPlex SM
Service material for CICSPlex SM is distributed as corrective or preventive service.
dfha1l0.html |
Last updated: Sunday, 4 June 2017