ibm:vm370-lib:cmshelp:control.helpexc
CONTROL
EXEC Interpreter
- control.helpexc.txt
&CONTROL STATEMENT EXEC statement Use the &CONTROL control statement to specify the amount of data to be displayed in the execution summary of an EXEC. The format of the &CONTROL control statement is: +-----------+-----------------------------------------------------------------+ | &CONTROL | [CMS|ALL|ERROR|OFF] [NOTIME|TIME] [MSG|NOMSG] [PACK|NOPACK] | +-----------+-----------------------------------------------------------------+ where: CMS displays each CMS command as it is executed and all nonzero return codes. This is the default. ALL displays CMS commands and EXEC executable statements as they execute as well as any nonzero return codes from CMS commands. ERROR displays only those CMS commands that result in an error and also displays the error message and the return code. OFF suppresses the display of CMS commands and EXEC control statements as they execute and of any return codes that may result from CMS commands. TIME includes the time-of-day value with each CMS command printed in the execution summary; for example: 14:36:30 TYPE A B This operand is effective only if CMS or ALL is also specified. NOTIME does not include the time-of-day value with CMS commands printed in the execution summary. This is the default. MSG does not suppress the "FILE NOT FOUND" message if it is issued by the following commands when they are invoked from an EXEC procedure: ERASE, LISTFILE, RENAME, or STATE. This is the default. NOMSG suppresses the "FILE NOT FOUND" message from the above-named commands. PACK packs the lines of the execution summary so that surplus blanks are removed from the displayed lines. This is the default. NOPACK does not pack the lines of the execution summary. Usage Notes: 1. The execution summary may consist of CP and CMS commands, responses, error messages, and return codes, as well as EXEC control statements and assignment statements. When EXEC statements are displayed, they are displayed in their scanned format, with all variable symbols substituted. 2. Each operand remains set until explicitly reset by another &CONTROL statement that specifies a conflicting operand. When &CONTROL is used with no operands, all operands are reset to their default values. 3. There is no global setting for &CONTROL. When an EXEC is nested within another EXEC, the execution summary is controlled by the nested EXEC's &CONTROL setting. When control returns to the outer EXEC, the original &CONTROL setting is restored.
ibm/vm370-lib/cmshelp/control.helpexc.txt ยท Last modified: 2023/08/06 13:36 by Site Administrator