+ENFORCERI
YES or NO | Specifies whether BMC AMI Load should expect LOADPLUS (YES) or BMC AMI Load (NO) syntax. |
---|---|
IGNORE, WARN, or ERROR | If referential integrity is requested, specifies how BMC AMI Load will handle the request for referential integrity checking:
|
BMC AMI Load currently accept the LOADPLUS ENFORCE option keywords even though BMC AMI Utilities do not currently support referential integrity. For more information, see ENFORCE.
Using the +ENFORCERI parameter
Depending on the scenario, use the +ENFORCERI parameter as follows:
- If you have been using the BMC AMI Load syntax, set the +ENFORCERI sub-parameters to NO and IGNORE (the default) so that the existing BMC AMI Utilities customers will see no impact from this change.
- Users transitioning from BMC LOADPLUS to BMC AMI Load can also use this setting if they want to use the existing JCL with BMC AMI Load while ignoring referential integrity (BMC AMI Load issue an informational message only).
- If you are transitioning from LOADPLUS to BMC AMI Load and want to identify jobs that request referential integrity, you can set the +ENFORCERI sub-parameters to YES and WARN. YES tells BMC AMI Load to expect LOADPLUS syntax for the ENFORCE keyword. WARN causes BMC AMI Load to not only issue a warning message, but also set the STEP CC = 0004 (the LOAD process proceeds as normal, otherwise).
- If needed, the BMC LOADPLUS customers can also configure the +ENFORCERI sub-parameters to YES and ERROR to stop BMC AMI Load jobs that request referential integrity. As above, YES tells BMC AMI Load to expect the LOADPLUS syntax for the ENFORCE keyword. ERROR causes BMC AMI Load to set the STEP CC = 0008 and fail the LOAD processing.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*