As mentioned above, there are three ways to control syntax error processing: VMO records, command models, and logonid records. The options available for all three are basically the same. That is, they all accept an ALLOW, LOG, PREVENT, or PREVENT-LOG keyword or a null (blank):
When you set this option, CA ACF2 for z/ VM passes the command to CP for normal syntax checking. CP issues standard error messages to the user. CA ACF2 for z/ VM does not log the syntax error to SMF.
When you set this option, CA ACF2 for z/ VM passes the command to CP for normal syntax checking. CP issues standard error messages to the user. CA ACF2 for z/ VM also writes an SMF record that appears on the Command Limiting Journal (ACFRPTCL).
When CA ACF2 for z/ VM detects a syntax error, it sends the following message to the user and rejects the command:
ACFpgm274E CA-ACF2 syntax error, operand number <operand> - command <cmd> rejected
Also, CA ACF2 for z/ VM does not charge the user with a violation (CA ACF2 for z/ VM does not increment the SEC-VIO count because of the syntax error).
SYNERR=PREVENT is the default for CMDLIM VMO record and the CA ACF2 for z/ VM-supplied command models. CA ACF2 for z/ VM does not write a System Management Facility (SMF) record for syntax errors.
When you set this option, CA ACF2 for z/ VM prevents the execution of the command and logs the fact that the user entered the command incorrectly. This option does not cause a violation.
In the logonid record and command model, SYNERR( ) is the default setting. You can change this setting to SYNERR(LOG) or SYNERR(PREVENT-LOG) if you need SMF records for an individual user. These SMF records appear in the Command Limiting Journal (ACFRPTCL).
If you set the value of SYNERR= to null (blank), CA ACF2 for z/ VM passes error processing to the VMO record for checking.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|