Introduction to COPE

COPE is a software package that allows replication of environments for IMS TM (Information Management System), IMS DCCTL and IMS DBCTL 
The IMS system can be (approximately) represented in the following diagram:


The system is managed by compiling a set of related source statements into various load libraries so that application programs can execute in the IMS environment. 
In most installations, multiple IMS environments are required for development and testing. Replicating the environment requires replicating everything as follows:

COPE is a software system that allows multiple environments to execute in a single IMS system.

It uses duplicate source definition datasets but only has a single set of load libraries that are input to IMS. It adds two additional datasets named PGMLIB and STUBXLIB and two dictionary databases. One of the dictionaries is maintained with ISPF tables and the other is accessed from IMS and may be a DLI database or a DB2 table.

Siblings and what they are used for

COPE allows the definition of 'Logical Systems'. Each Logical System has a set of source libraries that contain separate IMS component definitions, such as PSBs or DBDs or Stage 1.
It would be possible to copy separate definitions from existing systems into separated libraries related to a specific Logical System. However, in most installations, test and development systems are similar, and much time would be spent in copying duplicate and identical definitions into various Logical Systems.
To alleviate this problem, a Sibling relationship can be defined between Logical Systems:

The diagram shows a production environment named PROD and three development environments named DEV1, DEV2, DEV3 logically attached to it.

The PROD System is designated as the 'Senior' Sibling and all the other environments are designated as Junior Siblings.

When a component is copied into a Senior Sibling the data is also copied into all Junior Siblings attached to it. UNLESS, there is an identically named component in the Junior Sibling library.

During the initial installation, multiple copies of the production environment may be defined with a single set of Imports, and then testing environments may be changed by importing differences into any of the Junior Siblings.

Since environments are typically 90% identical, this enhances the installation process.

How COPE manages the IMS environment

Information is transferred from the COPE ISPF dictionary to the executing IMS environment via several generated load modules and a database.

The database is used to manage the Start/Stop (SS) Application that is accessed from the COPE IMS transaction. The data describes the databases and transactions that are defined in each Logical System. IMS Transactions are shared between many Logical Systems and if a transaction is stopped in IMS, no system could use it. The SS Application is used to 'Logically Stop or Start Databases and Transactions and allows the IMS status to always be available..

The generated load modules are;

• STUBX
• COPEXRF1
• COPEXRF2
• COPEXRF3
• COPEXRF4
• COPEXRF5
• COPEMFSX
• COPEPSYS

These modules are generated automatically during various COPE processes.

A brief description of the data of each load module follows although the users of COPE have no need to understand the contents.

STUBX

Whenever a PSB is generated, a STUBX module is generated that contains information about the user database names and PCB names as well as the application program name for each Logical System. The modules are put into STUBXLIB and PGMLIB depending on whether IMS is executing or not.

COPEXRF1

This load module contains the user names and the COPE assigned C-number name for all objects in the system. COPE assigns unique names that begin with a C and are followed by 7 digits. The combination is called a C-number. Many items are renamed to allow them to execute in a common system.

COPEXRF2

This load module contains information about transactions and the PSBs that are scheduled by them.

COPEXRF3

This load module contains information about alternate LTERM names.

COPEXRF4

This load module contains information about the datasets that contain the application programs for each Logical System. Each Logical System can have separate program load libraries defined for it.

COPEXRF5

This load module contains system information extracted from the COPE Dictionary.

COPEMFSX

This load module contains information used to manage different versions of MFS definitions

COPEPSYS

The module contains information used in executing Batch or BMP applications. Each Logical System has a 'token' assigned to it that may be defined in the JOB card, on a COPEBSYS DD statement or in place of the IMS ID in the DFSRRC00 PARM field. The token is used by COPE to identify a Logical System the Job is to execute in.

How COPE supports Batch and BMP applications

COPE allows the same set of JCL to be used in all Logical System environments. The user identifies the Logical System in one of three ways:

• Put a token in the second positional parameter in the JOB statement
• Replace the IMS ID token in the DFSRRC00 PARM field
• Add a COPEBSYS DD statement with a token making a temporary dataset name (two && on the front)

Overview of the User ISPF Interface

Up to 255 environments may be defined to COPE in a way which will allow them to execute simultaneously under IMS. Each environment has separate definitions and may execute different versions of application programs.

An installation will copy or 'Import' definitions from existing environments into COPE, and COPE will regenerate them into the same set of Load datasets that IMS requires.

The online environments are managed by the data in the COPE Dictionary and by the contents of various load modules generated in the recompilation process.

The Enhanced User Interface has arranged the applications that make up the ISPF portion of COPE into five categories.

• Setup Activities
• Import Activities
• Change/Generate Activities
• Data Transformation Activities
• Other

Pictorially, these assignments may be represented as shown

 

The COPE Prime User Menu

Accessing the ISPF COPE application will result in the following menu being displayed.

• Option 1 is used to Setup or define environments and System variables
• Option 2 is used to Import and Generate definitions into Logical Systems
• Option 3 is used to Update, Copy, Move and Generate definitions imported into COPE
• Option 4 is used to perform Data Transformations, such as ACB generations, Stage 1 generations, PSB generations or SS application data load.

Option 5,6,7,8 and 9 belong to the 'Other' category

• Option 5 allows generation and submission of various (infrequently used) Utility programs
• Option 6 is used to view trace records generated by executing IMS applications. DB2 and DL1 records are traced together with debugging messages issued from the application programs
• Option 7 or T accesses an application that converts a C-number to the associated entity and Logical System it belongs to. It is intended for use in translating messages and trace information.
• Option B accesses the previous COPE User interface. It provides some facilities that are not present in the 'Enhanced User Interface'
• Option 9 accesses the IBM IMS SPOC application from which Type 2 commands can be issued to an executing IMS system.

Hidden Panel Commands

The following commands may be entered on any panel even though they are not specified on the panel

• BROW Invokes the ISPF (Option 10) Browse Application
• EDIT Invokes the ISPF (Option 2) Edit application
• UTIL Invokes the ISPF (Option 3) Utility's
• J Displays the user JOB statements. They may be altered if required
• JOB Displays an application that allows review of all background jobs generated by the user and their completion codes. The jobs may be edited and resubmitted if required. An example of the JOB application display follows :

The EVARS prime panel command

Entering EVARS on the prime menu allows editing of the COPE system variables that are used to tailor the COPE environment. These variables are described in the COPE Installation manual.

The Setup Option (Option 1)

Options 1-9 are generally performed once during the initial COPE installation. Options 10 to 12 may be performed any time.

Define Logical Systems (1.1)

Each Logical system is identified by a two part name. The PREV SYSTEM field defines the 'Senior Sibling'. Inactive systems may also be defined.

During the definition process, application load libraries are required. Entering 'L' next to a row allows this.

When the definition is complete, application dataset will be allocated for each Logical System. This Option may be entered any number of times without affecting previous allocations or data.

Generate Batch JCL Procedure (1.2)

Many COPE processes submit jobs that invoke TSO in the Background. A JCL Procedure must be generated that contains installation specific dataset names and options.

THIS OPTION MUST BE EXECUTED BEFORE ANY OTHER WORK CAN BE PERFORMED.

Selecting this option will cause a JCL procedure to be generated and placed in the JCLLIB dataset specified on the JOBCARD statements on the Setup Panel. If the JOBCARD statements do not contain a JCLLIB statement an error message will be issued and no procedure will be generated.

Define Batch JOB Card (1.3)

Use of this Option will allow editing of the DEFLTJOB member in the COPE CTLCD dataset.

This member should have 4 JOB statements defined and is used when COPE background applications generate additional jobs for defining environments. If separate JOB statements are required for different users, additional USER ID named members may be provided in the CTLCD dataset.

Edit External Interface (Batch Input) Sample JCL (1.4)

The External Interface is a JCL procedure that allows Import to COPE and generation from COPE of any IMS definition. If a Change Management System in integrated with COPE, it can generate JOBS that will promote definitions to various Logical Systems.
This option allows editing of a sample JCL procedure that contains comments about the usage of it and directions as to the values of the fields that are input to the procedure.

Specify Message Region Datasets (1.5)

Multiple message region TASKLIB (STEPLIB) datasets may be specified for each Logical System.

In addition to message region datasets, datasets associated with hard coded message region DD statements that are accessed by application programs may be defined. Each Logical System can have different 'hard coded' datasets.

On exit from this panel, an opportunity will be provided to define datasets by message region class or by Fast Path PSB. This facility is used to provide different TASKLIB specifications for Logical Systems. This can be useful when, for example, applications in an Lsys use different versions of COBOL because they were developed at different times and have not been converted.

Define Lsys Identifying Tokens (Re-Linkedit IMS Modules) (1.6)

COPE allows the same JCL to be used for execution in all environments. The Lsys environment is identified by a Token placed in the JOB card (2^nd positional position) or in place of the IMS ID in the DFSRRC00 PARM field or on a COPEBSYS DD statement as a temporary dataset name (defined with && in the front of the token).

In addition to defining tokens, the application generates Linkedit JCL that re-linkedits DFSRRC00 and certain IMS utilities. The re-linkedit is required for intercepting the run time execution so that the environment can be transformed to match the Logical System requirements. No modifications of IMS code is performed.

When the 'G' option is selected on the following panel, the following is displayed for definition.

Different tokens may be defined for use on the JOB card or IMSID and COPEBSYS field. 1-8 characters may be used even though the IMS ID is limited to 4 by IMS.

It is strongly suggested that the same token be used for both definitions.

When the definition panel is exited, the user is placed in an edit session for reviewing and submitting a job that re-linkedits IMS modules and creates the COPEPSYS load module.

Define Excluded (Not Modified by COPE) Databases and Transactions (1.7)

COPE requires, and there may be other, system wide transactions and databases that do not need to be replicated in every Logical System. This option allows DATABASE TRANSACT and APPLCTN Stage 1 statements to be defined. These statements are copied without change into Stage 1 source definitions generated by COPE. The PSB and DBD names are not modified and execute in message regions outside the COPE environment.

Define Common Stage 1 Specifications (1.8)

This allows Logical Systems to have identical Stage 1 definitions. If the Stage 1 definition of any Logical System is altered, the changes are applied to all the other definitions.

Not all defined Logical Systems may share a common Stage 1 definition. This can happen when COPE executes systems developed by different organizations before the organizations were merged. Sometimes, development environments do not require access to all the applications and data that is available in the production system.

If the COPE system parameter &XCMNSTG1 = YES, all defined Logical Systems share a single Stage 1 definition automatically.

Bind COPE DB2 Plans (1.9)

A job is generated that binds DB2 plans for SQL extract for viewing traces (DB2 Trace Feature) and, if the DCCTL system is installed, plans for accessing the COPE control tables

Generate Environment Member after Changes to ZDEFAULT (1.10)

If COPE System variables are modified (by using the EVARS command on the prime menu), the changes need to be defined to the IMS system by regenerating the COPEXRF5 load module,

This option causes the generation of a background job which should be submitted to regenerate the load module.

Limit Lsys Access to Specific Users (1.11)

Logical Systems require time to set them up. During this setup period, access to the Logical System will result in various failures because of missing components.

The COPE Administrator can prevent all users from connecting to a Logical System by specifying the User ID of those people who are allowed access. All others will be prevented.

In the example, if USER are defined as '*' all users may access the system.

If there is a User ID or User ID's specified against a Lsys name, only those users can access the system. If a Y is specified under the S/P Lsys column, that specific user will not have permission to access the Lsys.

Specify a Virtual Date and Time for HourGlass (1.12)

This option will only appear if the COPE system parameter is &XHRGLASS=YES. It allows relative or actual dates and times to be defined for every Logical system. These specifications are enforced for MPP, Batch and BMP executions.

After generation, a JOB will be generated to transfer the information via the COPEXRF1 load module to the executing IMS system.

Import and Generate (Option 2)

The process of transferring existing definitions into COPE is named 'Importing' Stage 1, DFSMDA (Dynalloc) DBD(COPY) PSB(COPY), MFS(COPY) and Recon definitions may be imported

Import operations involve specifying a dataset. If member names are not specified, selection lists will be displayed.

Depending on the component, data may be imported from source, load or (in Release 14 of IMS and later) Dictionary.

In general MFS is not imported since COPE uses the existing FORMAT libraries. Only changes to MFS need to be imported.

The Stage 1 definition must be imported before PSBs are imported. COPE assigns the MPP or BATCH attributes to a PSB via the Stage 1 definition.

Importing PSBs will result in a panel that asks if a PSB and ACB gen are required. In order to save processing time, it is recommended that NO be specified for both options and the Data Transfer Options 4 and 5 are used at the completion of the Import process.

Importing RECON definitions requires importing DFSMDA (Dynalloc) and DBD definitions before it. The dataset and DD names are extracted from the DFSMDA and the IMS RECON compiler requires the DBDs to be in the DBD dataset.

Update/Copy/Move/Generate Specifications Imported into COPE (Option 3)

Specifications that have been 'Imported' into COPE may be modified and regenerated.

Option 3 from the prime menu provides applications to do this.

Update the Full Stage 1 Definition and Save in COPE (3.1)

Specification of this option together with the 'Target Logical System' name results in an edit session for the Stage 1 definitions for that system. If changes are made, a JOB is generated to parse the specifications and transfer the results to the COPE Dictionary. The generated JOB should be checked for errors.

Add Stage 1 Statements to COPE and IMS via SPOC (3.2)

This option allows a dataset and member containing Stage 1 definitions that is to be compared with the existing COPE definitions.

If complete Stage 1 source is provided (containing an IMSCTL statement) a comparison is made and DELETE, ADD, and UPDATE type 2 commands are generated which are used to update the executing system.

If a partial Stage 1 statement member (containing no IMSCTL statement) is provided, ADD and UPDATE commands are generated but no DELETE commands.

If the SPOC feature is not present, the appropriate Additions, Deletions and Updates are added to the COPE dictionary but no Stage 1 generation is performed. A Stage 1 generation may be performed by using Option 4.1

Update All DFSMDA (Dynalloc) Definitions and Select for Generation (3.3)

Selection of this options invokes an edit session on the DFSMDA definitions for the target Logical System. When the edit session is terminated (by pressing PFKey 3) a selection menu of databases and their datasets is presented for selection. A database will not appear in the selection if it has not been imported into the Target COPE Logical System.

After selecting databases, a job is generated to compile the definitions.

• Update and Generate DBD Source or Update DBDCOPY Members (3.4/3.4C)
• Update and Generate PSB Source or Update PSBCOPY Members.(3.5/3.5C)
• Update and Generate MFS Source or Update MFSCOPY Members (3.6/3.6C).

The same application manages all these components that exist inside COPE.

THE TARGET LOGICAL SYSTEM SPECIFIED ON THE PANEL IS THE SYSTEM THAT COMPONENTS ARE MOVED OR COPIED INTO.

When you enter a “C” or “M” next to a member shown on the following display, that member is copied or moved to the target Lsys. A “move” us a Copy followed by a Delete. Specifications may be regenerated into the IMS load libraries. Specifications can be deleted from the Target as well as other Logical Systems.

To understand how the application works, consideration of the ‘Sibling’ arrangement must be made.

Previously in this manual, a description of Sibling relationships was presented. If a member exists in a ‘Senior Sibling’ its contents are applied to ‘Junior Siblings’ unless an equivalent member exists in those Siblings.

If a Senior Sibling is modified, the change may affect some or all of the ‘Junior Siblings’ that are connected to it. In many instances, this is probably not desirable.

The application can ‘Protect’ the contents of Junior Siblings. Before a Senior Sibling is replaced, the Junior Siblings get a copy of the contents of the Senior Sibling so that the Senior Sibling replacement has no effect on their definitions

The above display shows the specifications for the “Target Logical System” specified on the previous panel. The name of the “Target Logical System” is displayed on the top line.

The ‘Protect Sibling’ field is set to Y and ‘Sibling Display Lines’ field is set to 0.

If another Logical System is specified in the ‘Additional System’ field and the ‘Sibling Display Lines’ field is set to 1, the following results:

Beneath each Logical System Specification Member row there is a row of Sibling names that this member applies to

[B]rowse, [E]dit,[C]opy,[M]ove,[Delete,[R]eset and [G]enerate row commands can be specified.

In addition to the row commands, several panel commands can be specified that will allow many members to be selected from a specific Logical System based on masking characters. PFKey 1 should be used to display a help screen that describes these capabilities.

[F]ind and [S]ort commands are also available.

After the specification process, PFKey 3 is used, and a background JOB is generated that will implement all the changes and regenerations. The JOB will generate further JOBs. The JOB command should be used to check the completion codes of all JOBs

Specify partitions for HALDBs (3.4H)

HAL Databases require a DBD and a RECON partition definition to be present. The HAL DBD may be imported and generated in COPE in the same way as any other DBD.

When the DBD has been imported into one or more Logical Systems, the Partition definitions may be performed with this option.

On selection, the following panel is displayed.

COPE assigns C-numbers to all DBDs and Partitions for a database associated with a Logical System.

If 'DEF' is entered in the command field together with a Logical System name and DBD name, the application searches the RECON for existing records and copies them after changing the C- number names to the original names. The IBM Partition Definition Utility (^DFSHALDB) dialogue is then invoked to allow modification or addition of Partition information. The definitions may be performed using User defined names, not C-number names. When the definitions are complete, the COPE application assigns C-number names (if required) and copies the partition definition records back into the same RECON dataset.

Before definition can begin a COPE IMS Configuration must be defined with the RECON and DBDLIB names shown on the panel. Option 7 on the following %DFSHALDB panel must be performed first

Once the configuration is defined, definition of partitions is accomplished in the same way as in a non-COPE system.

Update COPE Start/Stop Definitions and Submit Load JOB (3.7)

Under online IMS, users start and stop Lsys's, databases and transactions using COPE's Start/Stop Application. This application shows scrolling lists of the databases and transactions, together with Descriptions of each.

When using this option. if you receive a screen saying that databases have changed and groups need to be regenerated, hit <Enter> to submit the group regeneration job. When the job has completed, return to the n option.

If you choose not to run the group regeneration job by hitting <PF3> instead of <Enter>, the edit process can be entered immediately. Any changes made will be carried forward to when the group regeneration job is eventually submitted. Go through options 1 and 2 of the selection screen, to describe the physical IMS system (Psys), and the logical IMS systems (Lsys's), as shown below.

Enter option 3 (databases), to view the list to check that all database names are known to COPE. If they are not, you should correct the Stage 1, and/or import missing DBD source. No update action is required in option 3. This option is not shown for a DCCTL system.

Enter option 4 (groups of databases), and issue the SPECIFYD command. Add your database descriptions. Insert lines for your database groups. Press <PF3> to save. This option is not shown for a DCCTL system.

Enter options 5 and 6 for transactions, if desired. Option 6 has a SPECIFYT command that can be used to specify and describe transaction groups.

When the application is exited (by pressing PFKey 3), a background JOB is generated that will load the information into the USTDLMGR IMS database or table.

A complete description of the details of using the definition application can be found in the 'COPE for IMS Admin Guide' in the section 'Describe Database and Transactions (Option 4.2.DG, DBSTOP)'

COPE Utilities - Change DBD/Area Names in DEDB DMAC Record (3.8)

If a DEDB database id REPRO'd so that it can be accessed by a different DBD definition, the DMAC control block contained in the Database must be changed to reflect the DBD name and Area name of the DBD that is accessing it.

Since every COPE DBD has a unique C-number and every Area also has a unique C-number, the DMAC of a REPRO'd database must be modified to reflect the correct values.

The application accesses all DYNALLOC and DBD information within the COPE physical system and accesses all DEDB files to extract the DMAC information.

The results are displayed as follows

The 'Old DBD and Area Names' are the values that exist in the DMAC currently. The 'COPE DBD and Area Names' are the values that must be present for the COPE System to access the Database.

If the values are different, a S may be entered in the line command field and the DMAC values will be modified to the COPE values.

If the operation is performed when IMS is executing, there may be problems caused by the SHAREOPTIONS values.

A value of 'NO-GOOD' will be placed in the Selection field. Performing the operation when IMS is down will circumvent the issue.

If the database cannot be allocated a value of 'Missing' will be placed in the selection field.

Data Transform (IMS and COPE) (Option 4)

This set of applications allows the conversion of data from one form to another. It supports:

• 
  
  • Stage 1 specifications to Modblks
  • DFSMDA (Dynalloc) source specifications to load modules
  • PSB specifications from source to load modules
  • ACB generation from DBDLIB and PSBLIB data
  • COPE Dictionary Information to Load Modules
  • COPE MFS information to load modules
  • Specify DB2 Packages for the DCCTL COPE Logical System
  • Internal COPE PSB dictionary information
  • Internal COPE Dictionary Start Stop (SS) information

Perform a Stage1 Generation and Update Executing System (4.1)

This submits a job that generates Stage 1 source that describes the COPE IMS system. The source contains the user specifications and additional specifications related to the support of Xpediter and Overflow transactions. Overflow transactions occur when the limit of 1000 PCBs in a PSB is exceeded. The generated Stage 1 source also includes the 'Excluded' specifications that were defined in the COPE setup process.

If the SPOC feature is installed, a comparison is made between the generated source and the executing system and any differences are added to or deleted from the system via Type 2 Commands. Updates to attributes are not supported.

The generated Stage 1 is compiled and a Stage 2 source member is produced. An additional step is added to re-generate the COPE COPEXRFn modules.

Occasionally, during a mature COPE installation, there should be a full MODBLKS generation performed, and the RDDS datasets reset to allow it to be used by the IMS system.

This is because the update process available in Option 3.2 does not add COPE generated transactions and additional ones may be required if many changes are made to the system.

Edit (and submit) a Stage 1 Member (4.1E)

COPE generates a Stage 1 member (with Option 1) and puts it into an IMSGEN dataset.
 This option allows the generated source to be edited and generates a job to compile it and produce a Stage 2 member. Use of this option is only necessary if there are syntax errors or if changes are made to the source that COPE generates

Edit (and submit) a Stage 2 member (4.2)

An edit session is entered for the member generated by the previous Option 1 process. Typically the JOB name is changed. When edit is exited (by pressing PFKey 3) a background JOB is generated to compile the Stage 2 specifications.

Perform a Dynalloc Generation for all Databases (4.3)

This Option generates source from all defined Dynalloc Specifications and submits everything for compilation. The difference between this Option and that in Option 3.3 is that there is no selection process and it applies to all defined Logical Systems not specific ones.

Perform a PSBGEN (4.4)

This Option displays the following menu:

If GB is entered in the command field and Lsys is specified as an '*" and the PSB Name is left blank, all PSBs for all Logical Systems are displayed and may be selected for generation.

The COPE attributes assigned to the PSB, such as Online, Batch, Excluded, Message Switched Etc. are also displayed.

Perform an ACBGEN (4.5)

This application is described in Step 11. ACBGEN (Option 4.8) of the 'COPE for IMS Administration Guide'. It allows ACB generations for any PSBs or DBDs defined to COPE.

COPE supports concatenated ACB Libraries to overcome the limitation of a single volume. It also supports a 'Parallel ACB Gen Process' which can generate up to 7 jobs that can execute simultaneously and overcome the limitation of excessive time for a single ACB GENERATION job.

Create/Generate DBRC definitions (4.DBRC)

This application uses the previously imported Dynalloc (DFSMDA) data and generates INIT.DB, INIT.DBDS and INIT.ADS RECON statements with the correct COPE C-number names in them. All dataset information is obtained from the DFSMDA data.

Selection of this option will result in the following display.

The G option will generate INIT. Data for all logical systems. It will also generate INIT

.RECON statements and RECON allocate JCL. These may be removed if they are not required.

The generated data is accessed cia the E option.

If there are new DFSMDA data specifications, an cross reference job will be generated if the G option is specified. When this job completes, the G option must again be selected to generate the INIT. Statements.

The U option generates a job that compares the DFSMDA data with the RECON specifications and generates missing INIT. Statements.

Refresh COPE Name Translation Members (COPEXRF1/2/3) (4.6)

This generates a background JOB that regenerates the IMS information accessible information for translating user names to COPE C-numbers and vice versa. T is only required if some previous JOB has terminated unsuccessfully and the appropriate updates of load libraries have not been performed.

Generate MFS Name Translation Table (COPEMFSX) (4.7)

A background JOB is generated that compiles the COPEMFSX table. This is only required if some previous process has terminated unsuccessfully.

Specify Packages for all Logical Systems (4.PACK)

This Option only appears when the DCCTL system is in use. It allows RTT tables and Stage 1 source to be parsed and DB2 plans and Packages extracted for every Logical System. COPE causes different PACKLIST definitions to be available for different Logical Systems. In this way, different DB2 tables can be accessed.

Recreate Dictionary of PSB Definitions (4.8)

The table displayed in Option 4 described previously may not be current due to system problems and unsuccessful completion of previous JOBS. This Option generated a background JOB that recreates the PSB definition table from several associated tables in the COPE dictionary.

Recreate COPE Transaction and Database Start/Stop Definitions (4.9)

The Start/Stop (SS) table may be corrupted by unsuccessful job terminations. This Option recreates it from associated Dictionary tables.

Internal COPE Dictionary Tables (4.10)

This Option is used for problem resolution and is not required during normal COPE operation. It displays internal tables that contain the C-number conversion information.

Review Generated XREF and SS Definitions (4.11)

Most of the COPE Data Transform processes place members in the IMSGEN dataset. This option places the user in Edit on the dataset so that they may be reviewed or resubmitted

Utilities (Option 5)

The Utilities Option allows infrequently used applications to be executed in Batch or BMP mode (except for DBCTL systems which only allow Batch operation)

The selection menu follows:

The COPE Database Cleanup Job (5.1)

Generates a JOB that deletes the scrolling records that are associated with users. This job only needs to be run when users of the IMS COPE system get inconsistent displays due to corruption of the data records that are used to display the results of commands that have been issued.

Edit Job that Allows Commands to be entered from Batch (5.2)

Type 1 and Type 2 commands may be entered from a BMP program. The DBD and PSB names are translated depending on the Logical System identified in the JCL. This Option generates an example job that may be modified by users.

COPE Start/Stop Record Print (5.3)

The JOB dumps the Start/Stop (SS) records in the COPE database.

COPE 'Restore User Logon' Job (5.4)

This job scans the COPE USTDLMGR database and generates records that can re-login users to their Logic Systems after the Database has been deleted and reformatted. Selection of this option will display a panel that allows execution of the Logon generation JOB or the execution of the previously generated JOB.

COPE User to Lsys Disconnect Job (5.5)

Option 1.10 provides a 'Limit Lsys Access to Specific Users' option. This utility scans the COPE database and logs off all users from specific systems. They will then be unable to re- connect to the systems defined in Option 1.10.

COPE User Statistics Job (5.6)

This utility scans the COPE database or table and prints out the User ID's and the Logical Systems they are connected to. The utility is useful for statistical usage information collection.

COPE Database Initialization Job (5.7)

This generated job is required to format the USTDLMGR COPE database (for IMS TM) or the USTDLMGR tables (for DCCTL) in a new installation. The job can only be executed after a Stage 1 generation with Option 4.1 has been performed because it generates the Start/Stop (SS) data that is loaded into the databases.

Gen-Sub COPE Database Update Job (5.8)

If the COPE SS data is required to be reloaded into the COPE USTDLMGR database or (if DCCTL) the DB2 tables, this option will generate a job that will perform the operation.

Running this job will not Logoff the users of the system

Batch Logon of Users Job (5.L)

This option generates an example Job that allows Users to be connected to a Logical System. The example JCL also contains IMS commands submitted from a BMP job.

Print COPE Internal tables (5.9)

The Option is only used for debugging purposes and should only be used when directed to by Compuware personal.

Scan Source or Load Datasets for string (5.10)

This is a useful utility that scans for a string in a PDS or Library. It can scan Load or Source Datasets.

PDS Management Utility (Compress/Expand) (5.11)

This is a useful utility that displays the State of a PDS and can expand it by allocating a new dataset and copying the contents before renaming and deleting the existing dataset. In addition a background compress JOB can be generated that allows compression of allocated datasets.

Other Facilities

Functions that are not related to Importing, Changing or Transforming Data are:

Trace Function (Option 6)

The Trace Facility is documented in the COPE for IMS Programmers Guide under 'TRACE'.

It allows records to be retrieved from the Online OLDS datasets which contain trace records from application programs executing in the MPP or IFP regions.

Begin, end time and date are entered and the trace records are retrieved and presented in an Edit session.

The trace is initiated by a user under IMS by entering

COPE TRACE ON

From a cleared IMS terminal screen.

This command makes COPE trace all DLI calls and also intercept messages from the application program.

If the command COPE TRACE ON NOTRUNC is entered, DB2 SQL calls are also intercepted together with the data that pertains to them. The DB2 SQL call trace records can be expanded by entering a Q next to them and entering DB2 in the command field of the edit session.

The facility has an archive feature that allows an installation specified period (for example 20 days) of trace records to be kept and be available for retrieval. Without this facility, the records would be overwritten when the OLDS datasets were reused.

Translate Function (Option 7)

This is used to translate COPE C-numbers to the entities they represent and visa-versa.

In addition, DFSMDA (Dynalloc) load members can be retrieved and PSB and DBD source statements can be generated from the members in PSBLIB and DBDLIB. This can be useful for checking the consistency of IMS specifications. The contents of a STUBX are also displayed when a PSB is reviewed.

Another feature is the retrieval of compile and ACBGEN dates and the status of modules in ACBLIB.

Base Selection Menu (Option 8)

This option displays the ISPF application documented in the COPE for IMS Programmers Guide. Some rarely used functions are available from this set of applications.

SPOC Function (Option 9)

The IMS online system can be connected to by SPOC and Type 2 Commands issued to manage it. The COPE SPOC interface translates DBD and PSB names before sending them to IMS so that the C-number equivalents do not have to be entered. The returning information from commands is also translated before being displayed.