Common COPE Facilities
Overview
There are a series of facilities that are available from all
COPE
ISPF panels. These facilities are intended to provide convenience of operation for the user of
COPE
.The common facilities are:
- Invoke ISPF Edit by entering 'EDIT' in the command or option field
- Invoke ISPF View by entering 'VIEW’ or 'BROW' in the command or option field
- Invoke ISPF Utility selection menu (ISPF option 3) by entering 'UTIL' in the command or option field
- Access previously generated JCL together with job execution results by entering 'JOB' in the command or option field
Find the explanation and user action for all COPE generated messages beginning with the letters 'COP'. These messages will be seen in the IMS portion of COPE. The same message description may be accessed from IMS or ISPF by entering 'COPnnn' in the command field of any COPE controlled menu (nnn represents a numeric suffix).
Another feature of COPE is the common method for selecting options from a menu. Some applications require multiple items to be selected. A summary of the selection technique is given at the end of this section.
ISPF Edit, View, and Utility Access
Instead of accessing the ISPF facilities of 1 (for View), 2 (for Edit), or 3 (for Utilities), the commands VIEW/BROW, EDIT, or UTIL can be entered from any COPE controlled ISPF menu.
Re-submitting COPE Generated Jobs
When you perform many of the functions in COPE, such as importing PSB’s or DBD’s, or generating MFS, batch jobs are submitted.
Entering 'JOB' in the command or option field of any menu, accesses a dataset in which all submitted job JCL has been stored. The most recently submitted job is displayed first. This option is controlled by the XJOBSAVE installation parameter (refer to the COPE for IMS/DC Installation Guide appendix).
If the XJOBSAVE parameter has been set to NO, a message will be displayed indicating the option is not available.
When JOB is entered, the following screen (see the following figure) will be displayed.
JOB Status Display
The display shows the maximum return code from any step in a job. If E is entered next to a job record, the user is placed into edit on a copy of the job JCL.
If a job is to be resubmitted, SUB may be entered next to the job name. The job name will be replaced with the name of the resubmitted job.
The copy of the JCL and status record may be deleted by entering a D next to the job name.
Error Message Explanation
The COPE product has an error message manual. The text of error messages that begin with 'COP' and end with a three-digit numeric suffix, can be accessed online, from any screen, under ISPF or IMS, by entering the numeric suffix or the full COPnnn message number.
Member Selection Lists and Data Display
COPE ISPF applications allow both data entry and display of member lists. Both operations have standard commands and procedures.
Data entry is performed from a common application that allows the display of existing data in row/column format. An example of a data display format is shown in the following figure.
Data Selection Display Example
In the above example a data table is displayed for update. Data may be changed by overtyping. Sometimes there is more data present than can fit on a line. In this event the word "MORE" will appear on the third line with a right pointing arrow. The screen may be scrolled right and left by using the <PF11> and <PF10> keys, or by using the RIGHT and LEFT commands.
If data from an entire row is to be displayed, S may be entered on the row selection field and a screen will appear that shows all data from a row. Again, data may be updated by overtyping. The previous or next row data may be displayed by pressing <PF7> or <PF8>.
Row commands specific to the application are noted on the 5th line opposite "Rcd(s):" (in this case S) and commands that apply to the entire data are noted on the right of the 4th line (in this example ALL, INLIBS, L, NOTCOMP, NOTINACB).
There are several standard functions that apply to all data display applications. A description of the other functions may be obtained by typing 'POPUP' in the command field.
Standard functions include finding data in a column, sorting rows based on the contents of a column, and changing data in a column. In addition, the contents of a display can be formatted and written to a dataset by entering the 'REPORT' command.
Many of the COPE panels display member selection lists, of which there are two types:
- Selection for a single member
- Selection for multiple members
The single member list is used in the edit panel, and requires <Enter> to be pressed after entering an S next to the desired member.
The multiple member selection list requires <PF3> to be pressed after selecting one or more members.
The action to be taken is always noted in the top left-hand corner of the screen.
You may select multiple members by scrolling through the list and entering an S next to the desired members. If all members are required, ALL is entered in the command field, and an S will appear next to all members in the list. If some members are to be excluded from processing, the S can be blanked out.
If a set of selections is invalid, the RESET command will cause all selections to be removed.
When the selection process is completed, <PF3> is pressed to begin processing
Some of the displays contain hundreds of rows. If selection of a subset is required a ‘S +nn’ command may be entered. nn represents a number. The nn rows from the first row displayed are selected. The function is useful for generating recompile JOBs and limiting the number of members’.
Selection Mask
Anywhere that a member name may be specified, a partial name with special characters in it can be entered to cause the resulting display to only contain members that match the mask. e.g. Entering a name of *a+ results in a list of members that have the last but one character of 'A'.
In addition, the S capability on all displays has been enhanced to allow multiple masks to be specified e.g.
This selection statement selects all members that begin with an A or B and which do not have the character C anywhere in the name. (The ¬ character is Upper Case 6) Entering a S without a mask results in a prompt display that describes the masking characters.
Selection Mask Prompt
The description of the masking options is given in the above example (Selection Mask Prompt).
Problem Solving
In the unlikely event that a "BREAK" is invoked while executing under ISPF, it is important that <PF1> be pressed, and the long and short message information be carefully recorded before contacting BMC Software for assistance (refer to Getting Help ).
Use of the COPE External Interface
If the COPE External Interface is used, the compile procedures for PSBs, DBDs, and MFS must be modified by adding a step to import the source into COPE. Sample jobs for the external interface can be generated with Option 1.4. The following figure shows an example of such a step.
Example of External Interface Import
In this example, a COPE system named RELEASEE will have a PSB named DBDMEMB1 AND DBDMEMB2 transferred from the source dataset 'FTPROD.CTF4BASE.DBDSRCLB' to the LIBSET type PSBSOURC. The Userid that the recompilation of the PSB is to be performed for is IBMUSER. The Userid is used for JOB card control and security.
The above job step may be added to the installation's normal compile procedure. It may also be generated by CLISTS or ISPF PROCS, depending on the techniques used to compile modules.
1. COPE System Name (There may be several COPE Psys's in an Installation).
2. Logical IMS system name for COPE.
3. Source dataset and member name for PSB, DBD, or MFS modules.
4. Userid for JCL job cards
What happens in the External COPE Interface
The External Interface invokes TSO and ISPF, and executes a COPE application under ISPF. The application imports the module into the appropriate COPE library. Then, if it is either a program, PSB, DBD, or MFS module, regenerates it and submits a job to recompile it with the appropriate name changes required for execution in a shared environment.
The user will see two jobs executing every time the External Interface is used, if the module regenerates successfully. If, for some reason such as the absence of a COPY member, the module can- not be regenerated, only one job will be seen, and the messages that the job generates must be reviewed to diagnose and correct the problem.
Importing COPYLIB Members
If PSBs, DBDs, or MFS utilize copy members, the copy members must be imported before any compilations take place.
The COPE external interface can import any member into any COPE library. Recompilation will not take place for modules that are not programs, PSBs, DBDs, or MFS.
Controlling the User Jobcard
Some installations have unique requirements for the format of a job card. COPE supports either a single default job card, or a specific job card for each Userid. All Job cards are contained in a dataset named '&XCOPE1.CTLCD' (where the value of &XCOPE1 is that specified in the ZDEFAULT member (refer to the COPE for IMS/DC Installation Guide appendix).
The default job card is contained in a member named 'DEFLTJOB'. It can be edited and changed with COPE ISPF option 1.3. It consists of the following statements:
//NOTIFY=&XXXXXX,MSGCLASS=V,MSGLEVEL=(1,1)
/*JOBPARM P=TFTI
/*ROUTE PRINT U144
//** N O T E **************************************** N O T E *******
//* THIS JOBCARD IS THE DEFAULT JOBCARD PROVIDED IN THE CTLCD*
//* DATASET MEMBER NAME DEFLTJOB. IF THE JOBCARD IS INCORRECT*
//* THE DEFLTJOB MEMBER MUST BE CHANGED*
//*******************************************************************
The Userid is identified with a 7-character string beginning with an ampersand (&). The Userid supplied in the external JCL interface will be substituted for the ampersand and the six characters following it, before submitting.
If a user needs a different job card from this overall default, an individual member with the same name as the Userid may be set up in the CTLCD dataset.