If you have any questions about the content of this page, please contact CICS Requests for clarification

This section describes how to request CICS application resources be defined and later modified.

• Defining New CICS Application Resources
  • Requirements
• Modifying CICS Application Resources
  • NWRDC CICS Load Module Newcopy Facility
  • Enclaves
  • Moving Help Data To Production

Defining New CICS Application Resources

CICS resources come in a variety of types:

• Transactions
• Programs
• Mapsets
• VSAM Files
• ASSIST/TS Help Windows

NWR must define each transaction, VSAM file and ASSIST/TS help window to CICS before they can be used.. We define those things to the test and production separately. A request to define something to a test region does not automatically flow to production, as many entities never make it all the way to production. Production requests can be combined with test requests when appropriate.

Program and Mapset Auto-install

We have implemented CICS's program auto-install process. You are no longer required to contact NWRDC to predefine any:

• Program that is the object of a LINK or XCTL command.
• Mapset

Just code them and go. If CICS can find the load module, it will run the program or process the mapset.

Note: Since the definition of a CICS transactions must identify the program that is to receive initial control, we still need to know the name of that program ahead of time.

Requirements
Entries will be added to the test system when the following information is presented by a duly authorized individual.

Each New Transaction

1. Four character transaction ID
2. Initial program to receive control or tell us it's a "mirror" transaction.
3. If appropriate, DB2 plan name, plan package name or indication of the use of plan exit.
4. ACF2 Resource set name in which the transaction should reside.
5. If ASSIST/GT help windows will be supported under this transaction, we need to know the help PFkey.

Each New VSAM file (BASE CLUSTER):

1. Data Set Name
2. Eight character FILE-ID (DDNAME).
3. Is the file an ESDS (entry sequence)
4. Fixed or variable records.
5. File status: read only, browse, updateable.

Each New VSAM AIX Path

1. DATA SET NAME of the "path", not the aix proper.
2. Eight character FILE-ID (DDNAME).
3. Eight character FILE-ID of base cluster.
4. Fixed or variable records (same as base).
5. File status: read only, browse, updateable.

Alterations to existing resource definitions are handled in much the same way. Just let us know what needs to be changed.

Newcopying Production Programs and Mapsets

This section covers only "newcopies" not initial definition of transactions or programs. Individual programmers are responsible for providing the CICS test regions with "object" code.  Batch compiles, map assemblies and BMS/GT utility jobs produce that object code.

NWRDC CICS Load Module Newcopy Facility

The NWRDC CICS load module NEWCOPY facility was written to perform the controlled movement of CICS load modules from the test to the production environment. All moves are documented for subsequent review. Duly authorized users initiate all moves, no contact with the NWRDC is required.

Not all customers of NWRDC use the CICS load module NEWCOPY facility. Its use is strictly voluntary.

• An authorized individual logs on to their CICS production region.
• They invoke the NWPM transaction.
• They are prompted for the names of the load modules to be moved.
• They can select either immediate or overnight processing.
• A batch job is submitted to either perform the move immediately, or to stage the move for overnight processing.
• The batch job does its work and updates a DB2 table.
• The online application reads that DB2 table and reports back the success or failure of the request.
• The log of “who” moved “what” can be viewed for auditing questions.

Rules Of The Road

• Only properly defined CICS programs and mapsets can be processed by this system.
• All users are associated with an enclave based on their logon ID. See the enclave discussion below.
• Once a load module has been staged, users are free to recompile the program without disturbing the staged load module.
• A given load module can only be in the staging system once per enclave. Any attempt to stage a given load module again will result in a prompt. The user will be forced to choose between the new version and the old version.
• Any time the status of a newcopy changes, a job mail is sent to the logon ID of the requester. This includes the immediate newcopy, the staging process. an overnight newcopy and any cancellation requests.
• Any staged newcopy request can be canceled (killed). The original  requester will be notified.
• Any newcopy request can be “replayed.” All a replay does is retrieve the list of modules to be processed and the type (immediate or overnight) of newcopy. That list of modules can then be “edited down” or “added to” as needed.
• All modules in a single request must reside in the same load library.
•  32 modules can be moved at once.

Enclaves

All CICS programming resources are organized into “enclaves.” These enclaves represent the structure of the programming staffs that contribute load modules to the CICS environment.  Unique libraries for Load modules (test and production), PROCS, and copy books are all provided for each enclave.

Just because users are segregated into enclaves, does not mean that you can ignore the other enclaves in existence. Most CICS regions have more than one enclave running in them. Users of the UWF payroll system, FACTS and SAS as well as county schools and Chipola Jr. College, fall into this category. We should try to keep our program names unique across enclaves, but that is no longer a hard and fast rule. There are times it may be very convenient for a university to have a private version (for example) of a particular DCU program.

The individual enclave load libraries are made available to the appropriate CICS regions via load library concatenation. Each region has a different order to the concatenation of enclave load libraries. Some CICS regions have multiple Enclave load libraries in their program library concatenation.

The library names associated with each enclave (where 'eee' is an enclave code from the table above) are:

    CICS.USER.eee.LOADLIB

    CICS.PROCLIB.eee

    CICS.COPYLIB.eee

Moving Help Data To Production

ASSIST/GT help data is moved from the CICS test region to the appropriate production region. These moves may be done immediately, if necessary, but we would prefer to schedule them overnight. We need to be told the following:

• Is the move a first time affair (i.e., does the transaction involved already have some help data or not)?
• The CICS transactions involved.

We will do the following:

• For first time moves, we duplicate the HELP and STICKY CURSOR key definitions from the test region.
• We will copy all help windows whose names start with the transactions involved.
• We will copy all FIELD CONTROL RECORDS for mapsets whose names contain the transaction ID involved (in columns 3-6).

We are glad to provide interested parties with the JCL that allows them to move GT/ASSIST help data without any NWR assistance.