During product initialization, CA OPS/MVS defines its command prefixes to the z/OS Command Prefix Facility (CPF). The command prefixes are defined by the following product parameters:
There is no mechanism that will prevent you from defining the same prefix value for each of these parameters, although doing so will cause problems.
If the prefixes you define conflict with those of another CA OPS/MVS subsystem or if a prefix was defined to the CPF by some other product, the new prefix will not be registered in the CPF registry table. This, in itself, does not indicate a problem (message OPS0100W will be issued with return code 8 and reason code 8). However, you should avoid command prefix conflicts whenever possible.
If you define the OSFCHAR, ECFCHAR, or ATMCMDCHAR parameter as a NULL character (that is, without a prefix), then it will not be defined to the CPF. The CPF definition is performed only at product initialization. Therefore, if you change the OSFCHAR or ECFCHAR parameter after product initialization, then your change will not be reflected in the CPF. We strongly recommend that you set these parameters only at product initialization.
The CPF prefixes are deleted during product termination, and the sysplex-wide CPF definitions are deleted when CA OPS/MVS abends or the entire system fails.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|