User Tools

Site Tools


tutorials:exec

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tutorials:exec [2022/03/14 07:52]
lars Describe ATTACH behavior with respect to COMAND.CMD.
tutorials:exec [2022/03/15 09:41] (current)
papa [Automatic commands]
Line 91: Line 91:
 | LOGIN | 1. SYSTEM:LOGIN.CMD \\ 2. LOGIN.CMD \\ 3. SYSTEM:COMAND.CMD \\ 4. COMAND.CMD | | LOGIN | 1. SYSTEM:LOGIN.CMD \\ 2. LOGIN.CMD \\ 3. SYSTEM:COMAND.CMD \\ 4. COMAND.CMD |
 | SUBMIT | 1. SYSTEM:BATCH.CMD \\ 2. BATCH.CMD \\ 3. SYSTEM:COMAND.CMD \\ 4. COMAND.CMD | | SUBMIT | 1. SYSTEM:BATCH.CMD \\ 2. BATCH.CMD \\ 3. SYSTEM:COMAND.CMD \\ 4. COMAND.CMD |
-| ATTACH | 1. SYSTEM:COMAND.CMD \\ 2. COMAND.CMD | 
 | PUSH | 1. SYSTEM:COMAND.CMD \\ 2. COMAND.CMD | | PUSH | 1. SYSTEM:COMAND.CMD \\ 2. COMAND.CMD |
 +| ATTACH | 1. ATTACH.CMD |
 | LOGOUT | 1. LOGOUT.CMD \\ 2. SYSTEM:LOGOUT.CMD | | LOGOUT | 1. LOGOUT.CMD \\ 2. SYSTEM:LOGOUT.CMD |
  
 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 ''SET PROMPTS'' command in a user's LOGIN.CMD may be overridden in SYSTEM:COMAND.CMD since it is executed later in the sequence. This may be the case if EXEC seems to be ignoring commands in your LOGIN.CMD. Try moving such commands to your COMAND.CMD file, which is executed last in the log-in sequence and will override any conflicting commands in SYSTEM:COMAND.CMD. 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 ''SET PROMPTS'' command in a user's LOGIN.CMD may be overridden in SYSTEM:COMAND.CMD since it is executed later in the sequence. This may be the case if EXEC seems to be ignoring commands in your LOGIN.CMD. Try moving such commands to your COMAND.CMD file, which is executed last in the log-in sequence and will override any conflicting commands in SYSTEM:COMAND.CMD.
 +
 +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).
  
  
  
  
tutorials/exec.1647244352.txt.gz ยท Last modified: 2022/03/14 07:52 by lars