CICS regions and New Copy

Verification state: not yet run against a CICS region. Tested against a modelled CMCI server only; the request shapes come from the open-source Zowe CICS client, cited per request. The verification kit lists regions and resources, and runs New Copy and Phase In only when you name a program in a test region.

This is the deploy step for CICS programs: after Compile on z/OS, the new load module reaches the running region.

Connect to a region

The CICS management client interface (CMCI REST) is reached through the z/OS connection's transport, with an LtpaToken2 session kept for the window. Connections come from a Zowe cics profile or Set CICS Connection. Add CICS Region... and Remove CICS Region change the regions listed.

Browse the region

A CICS Regions node per connection in the z/OS Data Sets view lists, per region:

• programs, with use count and load library;
• transactions;
• local and remote files;
• libraries with their data sets;
• TS queues.

Filter CICS Resources narrows the list.

Act on resources

Each is confirmed, naming the resource, the region and CICSplex, the connection, its host and the CMCI server. CICS's refusal is shown with its reason. CEMT in the 3270 session remains available for anything else.

New Copy after a compile

Set host.cics in mainframe.json:

{
  "host": {
    "cics": {
      "region": "CICSA",
      "afterCompile": "offer"
    }
  }
}

After a successful Compile on z/OS of a CICS program, New Copy or Phase In is offered (or asked at once, still confirmed), and CMCI's answer is recorded in the compile job.