This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
tutorials:exec [2022/03/14 01:38] papa |
tutorials:exec [2022/03/15 09:41] (current) papa [Automatic commands] |
||
---|---|---|---|
Line 3: | Line 3: | ||
====== Using EXEC ====== | ====== Using EXEC ====== | ||
- | [Put general information | + | Similarly to a Unix shell, EXEC presents the user with a simple text-based command line interface. EXEC prints a prompt string (the default prompt is '' |
+ | |||
+ | Commands are entered in the form: | ||
+ | |||
+ | * command name | ||
+ | * one or more optional arguments or switches (separated from the command name and each other by one or more spaces) | ||
+ | * **Enter** key to indicated command input has been completed. | ||
+ | |||
+ | (Some commands also allow the input of [[# | ||
+ | |||
+ | Long commands can be continued to a second line by typing a hyphen ('' | ||
+ | |||
+ | EXEC then processes the command, possibly displaying output on the user's terminal. When command processing has been completed, EXEC displays a new prompt to indicate that it is ready for another command. | ||
+ | |||
+ | EXEC has several features that assist the user in entering commands. | ||
+ | |||
+ | ===== Command and argument list ===== | ||
+ | |||
+ | Pressing ''?'' | ||
+ | |||
+ | * At the EXEC prompt, pressing ''?'' | ||
+ | * In the middle of command name input, pressing ''?'' | ||
+ | * Elsewhere, pressing ''?'' | ||
+ | |||
+ | ===== Completion | ||
+ | |||
+ | During command entry, pressing **Esc** will complete partial commands and arguments and display // | ||
+ | |||
+ | // | ||
+ | |||
+ | @diRECTORY (OF FILES) | ||
+ | |||
+ | ... and wait for the user to specify what files he wants listed, or press **Enter** to list all files in the current directory. | ||
+ | |||
+ | ===== Abbreviations ===== | ||
+ | |||
+ | Commands, arguments, and switches can be entered in abbreviated form --- only typing enough characters to be distinguishable from alternatives. For some commands, etc., only one or two characters is sufficient. | ||
+ | |||
+ | Acceptable non-unique abbreviations have been defined for some commands: | ||
+ | |||
+ | ^ Command ^ Accepted | ||
+ | | CONTINUE | CON | | ||
+ | | CONNECT | CONN | | ||
+ | | EXECUTE | EX | | ||
+ | | EXPUNGE | EXP | | ||
+ | | LOGIN | LOG | | ||
+ | | LOGOUT | LOGO | | ||
+ | |||
+ | ===== Command | ||
+ | |||
+ | Use the following control keys to edit command text before pressing **Enter** (except for **Ctrl-H**). | ||
+ | |||
+ | | **Backspace** | Delete last-typed character to the left. | | ||
+ | | **Ctrl-R** | Retype current command line. | | ||
+ | | **Ctrl-U** | Erase current command line. | | ||
+ | | **Ctrl-W** | Erase previous word. | | ||
+ | | **Ctrl-H** | Reprint erroneous command up to error.< | ||
+ | |||
+ | < | ||
+ | |||
+ | ===== Subcommands ===== | ||
+ | |||
+ | To enter subcommands, | ||
====== Command Files ====== | ====== Command Files ====== | ||
Line 15: | Line 78: | ||
End of MYCMDS.CMD.1 | End of MYCMDS.CMD.1 | ||
- | You can suppress the display of the end-of-processing message by putting the command '' | + | You can suppress the display of the end-of-processing message by putting the command '' |
> EXEC requires all command file lines to end with carriage return+line feed control sequence ('' | > EXEC requires all command file lines to end with carriage return+line feed control sequence ('' | ||
Line 29: | Line 92: | ||
| SUBMIT | 1. SYSTEM: | | SUBMIT | 1. SYSTEM: | ||
| PUSH | 1. SYSTEM: | | PUSH | 1. SYSTEM: | ||
+ | | ATTACH | 1. ATTACH.CMD | | ||
| LOGOUT | 1. LOGOUT.CMD \\ 2. SYSTEM: | | LOGOUT | 1. LOGOUT.CMD \\ 2. SYSTEM: | ||
When EXEC executes multiple command files, commands in earlier command files may be overridden by commands in later files. For example, during log-in a '' | When EXEC executes multiple command files, commands in earlier command files may be overridden by commands in later files. For example, during log-in a '' | ||
+ | |||
+ | In principle, your LOGIN.CMD file should contain programs you want to run automatically when you log-in and job-wide customizations (DEFINE, SET LOCATION), while your COMAND.CMD should contain local EXEC customizations that you want applied every time EXEC starts for both LOGIN and PUSH (SET DEFAULT, SET PROGRAM, SET PROMPT | ||
+ | or PCL declarations). | ||