BMC COPE Programmer’s Guide

The COPE Programmer’s Guide explains how to edit and generate, under ISPF from within the COPE environment.

The reader should be familiar with IMS concepts, such as Program Specification Block (PSB) and Database Descriptor (DBD).

How COPE Works

COPE contains two parts: one that operates under ISPF, and one that executes in IMS.  

The ISPF part of COPE produces an environment that lets IMS operate several Lsys's within a single Psys, by parsing information from source modules into ISPF tables, and then regenerating DBDs, Dynamic Allocation Macro specifications, IMS Stage 1 source specifications and PSBs for the combined system.

The IMS part of COPE controls the operation of Lsys's within the single physical IMS system that COPE generates. A Control database(DB/TM) or Db2 table (DCCTL) is used to record the state (started or stopped) of databases (DB/TM)and transactions (DB/TM and DCCTL) under COPE control, and tracks the name of the Lsys that a user is connected to. COPE provides transactions to start and stop databases (DB/TM) and transactions (DB/TM and DCCTL) one at a time or in user-defined groups.

All naming is automatically controlled by the COPE system. The COPE interfaces must be used for all development work associated with a COPE environment.

Application Programmer Responsibilities

  • Understand that when a PSB, DBD, or MFS source module is recompiled, a job will be generated to import it into
  • Another job will be generated to recompile a modified version of the module for use by
  • Be familiar with the Logon, Start/Stop, Call Trace and Abend Summary features of the COPE in TM/DB and DCCTL environments
  • Interface with the person administering the COPE environment to generate PSBs, DBDs, ACBs and MFS.

The COPE Parsers

COPE controls its environment with information supplied in DBDs, PSBs, MFS, Stage 1 and Dynamic Allocation source members. Since COPE  does not modify IMS code at execution time, a technique is required to obtain the same type of information for the manipulation of the objects that COPE controls.

A convenient method of extracting the information is by parsing the same source that drives IMS.

This allows COPE to adapt to existing environments and requires no re-entry of information by system or application programmers.

COPE parses DBDs, PSBs, and MFS control blocks to allow the renaming of objects required to run multiple logical environments in one IMS system. The parsed tokens are maintained in ISPF tables in a form that allows the information to be manipulated without errors. The COPE compile processes for DBDs, PSBs, and MFS control blocks, generate a new module from the ISPF tables and compile the generated module rather than the original source. If developers look at the compiler output, they will notice statements in a different order, and the suppression of all comments.

The original source is maintained in PDS members. It may be accessed thru COPE ISPF panels. When a change is made , the source is automatically re-parsed and a job submitted to do the generation

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*