Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Using COPE Logical System Support


COPE is a BMC AMI product that allows an installation to operate separate and distinct versions of their IMS DB/DC applications under one IMS control region. These separate and distinct versions of their IMS DB/DC applications are called Logical Systems. These Logical Systems can be treated as if they were separate IMS regions.

Xchange features improved flexibility to allow users to set Xchange requests based on COPE Logical System. A running time clock for all programs run under that COPE Logical System will be started the moment the request is first used and will run parallel to real time. The request, including its displacement from the real time and date, is retained until you delete it with the D (Delete) line command or reset it with the R (Reset) line command.

If an individual Xchange request is entered on the primary Simulated Date Time Settings screen for a job that happens to run in a COPE Logical System for which there is an active COPE Logical System request, the date/time fields from the individual request will be used instead of the COPE Logical System screen's date/time fields. This is because specific individual requests always take precedence over COPE Logical System requests.

For a COPE Logical System to be eligible for COPE Logical System processing, it must have been defined with the Xchange parameter COPELSYS. For more information, see Task-3-2-2-Specify-Xchange-parameters.

When the COPE primary command is entered on the Command line of the primary Xchange Date Time Settings screen, the screen is displayed in COPE Logical System format as shown in the following figure. All the COPE Logical Systems that were designated with the COPELSYS parameter are displayed.

Simulated Date Time Settings Screen for COPE Logical System Support

Simulated Date Time Settings Screen for COPE Logical System Support.png

Tip

COPE Logical System support is also provided in date/time offset format. Enter the COPEOFF primary command on the primary Simulated Date Time Settings screen to redisplay the screen in COPE Logical System format with date/time offset capability. For more information, see COPEOFF and Using-COPE-Logical-System-Support-with-Date-Time-Offset.

Primary Commands-Using COPE Logical System Support

Enter primary commands in the COMMAND field at the top of the Simulated Date Time Settings screen. Except for the PRIMARY command shown as follows, only the standard ISPF primary commands are supported when in COPE Logical System format. The END command returns to the standard Simulated Date Time Settings screen. The RETURN command returns you to ISPF.

PRIMARY

worddav12a505665caa64f2f7cd96373c121f22.png

Display the list of valid primary commands.

Line Commands-Using COPE Logical System Support

The line commands described as follows can be entered if the user has the necessary authority. For more information on authority for COPE Logical System line commands, see Milestone-8-Configuring-Xchange-external-security.

Line commands are available for each of the COPE Logical Systems displayed on the Simulated Date Time Settings screen in COPE Logical System format. If your site is using Xchange external security (SECUSE=YES, SECDFLT=DENY), the TSO userID of the person entering the line command must have update access to the COPELSYS pseudo-data set name as described in Milestone-8-Configuring-Xchange-external-security. If that update access is not established, a NAUT (not authorized) error will be displayed under the Imsg column. If Xchange external security is not used (SECUSE=NO), any user can enter line commands on the Simulated Date Time Settings screen in COPE Logical System format.

H

Sets and holds a pattern COPE Logical System request. This command activates COPE Logical System processing for the COPE Logical System indicated on the line on which it is entered.

D

Deletes an existing pattern COPE Logical System request and its related jobs (if applicable).

R

Resets an existing pattern COPE Logical System request. This command deletes the existing pattern COPE Logical System request and its related jobs, then adds the COPE Logical System pattern back to the request table. The R command allows you to modify the values in the Requested Time YYYY/MM/DD and HH:MM:SS fields of the COPE Logical System request.

Status Codes-Using COPE Logical System Support

Status codes are displayed in the S portion of the C/S field next to each Xchange COPE Logical System request. Any of the following status codes can be displayed:

A

The COPE Logical System request has an active job.

E

The COPE Logical System request is executing.

P

The COPE Logical System request is pending. Because pending is a momentary status, this code is normally not seen.

Q

The COPE Logical System request is queued.

*

The COPE Logical System request contains an error.


Fields-Using COPE Logical System Support

Line commands can be entered next to each COPE Logical System request in the C portion of the C/S field, and the desired date and/or time can be entered in the Requested Time fields. The S portion of the C/S field, Imsg, and LSYS fields are display-only. The Filter row contains a series of mask fields, each corresponding to the column directly following it.

Filter Requested Time YYYY/MM/DD, HH:MM:SS

The mask for the Requested Time YYYY/MM/DD and HH:MM:SS fields. The initial values are all asterisks, which directs Xchange to display all COPE Logical System requests for which the rest of the request entry fields match their corresponding masks. These masks are saved upon exit and restored upon entry.

An asterisk represents a single wildcard character in the position of the date or time where it is placed. For example, masks 20** and **25 would each result in the display of all COPE Logical System requests for year 2025—assuming the rest of the request entry fields match their masks. A mask of all blanks is valid. A combination of blanks and asterisks, or numeric data and asterisks, is also valid. If you enter all numeric data, validation rules are equivalent to that of the request entry date and time fields.

C/S

The command and status fields for each COPE Logical System request. You can enter line commands in the C portion of the field. Status codes are displayed in the S portion of the field.

Imsg

The informational message area for each entry. When an asterisk (*) is displayed in the S portion of the C/S field, an informational error message will be displayed in the Imsg field.

LSYS

The COPE Logical System of each entry is displayed in this field. All COPE Logical Systems displayed have been defined with the Xchange parameter COPELSYS.

Requested Time YYYY/MM/DD

The year, month, and day that you want Xchange to simulate for jobs running in a COPE Logical System. If the PREVDATE parameter is set to NO (in the Xchange CMSC PARMLIB member), dates prior to the current date are not allowed. The following entries are valid:

YYYY

1900 to 2041 (2099 if POSTEPOC parameter is set to YES)

MM

01 to 12

DD

01 to 28 (Feb.)
01 to 29 (Feb. during a leap year)
01 to 30 (Apr., June, Sept., and Nov.)
01 to 31 (Jan., Mar., May, July, Aug., Oct., and Dec.)

If you enter a value for the day (DD), the month and year are required. If you enter a value for the month (MM), the year is required. You can just enter the year. This field defaults to the current year, month, and day. If you leave the DD field blank, an error will occur if the current day of the month is invalid for the month you specified—for example, if you entered February on July 31.

Requested Time HH:MM:SS

The hour, minute, and second that you want Xchange to simulate for jobs running in a COPE Logical System. The following entries are valid:

HH

00 to 23

MM

00 to 59

SS

00 to 59

If you enter a value for seconds (SS), the hour and minutes are required. If you enter a value for minutes (MM), the hour is required. You can just enter the hour. This field defaults to the current hour, minute, and second for any values not specified.

PF Keys-Using COPE Logical System Support

Xchange supports the standard default ISPF keys.

Additional Considerations-Using COPE Logical System Support

The following limitations and special concerns apply to Xchange COPE Logical System support:

  • Specific, non-COPE Logical System requests which cover jobs running in the same COPE Logical System as an active COPE Logical System request override that COPE Logical System request. The date/time of the non-COPE Logical System request is used for the exchange.
  • A COPE job will not be exchanged if the COPE Logical System under which it runs is not defined to Xchange with the parameter COPELSYS. Such jobs are displayed on the Simulated Date Time Settings screen with a LAUT error message.


 

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