Although the data set names that you use are not significant for this tour, consider naming the three copies:
Ensure that the CICS® region user ID (for the CICS region running the CICS Configuration Manager server) can access the three new CSD files.
We are going to define a CICS configuration for each of these three CSD files. We will name these CICS configurations TOURDEVT, TOURTEST, and TOURPROD.
If you prefer, you can create three CICSPlex® SM contexts instead. You could even use a mix of CSD files and contexts. For example, use a context for TOURDEVT, and CSD files for TOURTEST and TOURPROD. It will make no difference to the rest of the tour.
File Menu Settings Help ────────────────────────────────────────────────────────────────────────────── CICS Configuration Manager - Primary Menu Option ===> 0 Settings Set user parameters and options 1 Administer Administer CICS Configuration Manager definitions 2 CICS Resources Maintain CICS resource definitions 3 Packages Process change packages to migrate CICS resources 4 Reports Reporting views of CICS resource definitions X Exit Exit CICS Configuration Manager Server connection details IP address . . . . . FTS1 Port number . . . . . 11311 SSL enabled . . . . . NO (NO, YES) SSL keyring name . . SSL key database . .
The list of existing CICS configurations appears.
A pop-up window appears, prompting for the name of the new CICS configuration and, optionally, the name of an existing CICS configuration to use as a model.
File Menu Settings Help ────────────────────────────────────────────────────────────────────────────── Edit CICS Configuration Row 1 to 1 of 1 Command ===> Scroll ===> CSR Name . . . . : TOURDEVT Description . . Guided Tour Development Environment Specify the type of file or repository 2 1. CICSPlex SM Context . . 2. CSD File . . . . . . . CCVCICS.TOUR.DEVT.DFHCSD 3. Export-import file . . Choose a view for related options 2 1. Transform variables 2. CSD file options 3. Export-Import file options Define CSD file options and connections for CICS remote systems RLS access . . . . . DYNAMIC + DYNAMIC, NOTRLS or RLS / Connection + ******************************* Bottom of data ********************************