Skip to Content
Information
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.

COPE Logical System and END Block Parameters

The parameters that identify COPE Logical Systems for jobs that are eligible for exchange are listed as follows. These related parameters must be grouped into blocks identified with a block start parameter and a corresponding end parameter.

COPE_LOGICAL_SYSTEMS

Block start parameter to identify those COPE Logical Systems whose jobs under which they run are eligible for date/time simulation.

This parameter must precede the related COPELSYS parameter.

COPELSYS

A one- to eight-character COPE Logical System name that identifies those COPE Logical Systems whose jobs under which they run are eligible for date/time simulation. It must begin with an alpha character. The remaining characters can be alpha, numeric, or national ($, @, #) characters. Multiple COPELSYS parameters are valid. For more information, see Using-COPE-Logical-System-Support.

If specified, this parameter must immediately follow the COPE_LOGICAL_SYSTEMS parameter.

END

Block end statement that identifies the end of COPE Logical System definitions.

This parameter must immediately follow any COPELSYS parameters.

If an Xchange request is set for a job that runs under a COPE Logical System not defined with the COPELSYS parameter, the date and time will not be exchanged, and an ERR=LAUT (COPE Logical System not authorized) error message will be displayed in the Owner field of the request. This protection is active even if external security has been disabled by setting SECUSE=NO.

 

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

BMC AMI DevX Xchange 17.02