HP Integrity NonStop J-Series - Manual (Page 287)

Sample Project-Tracking System
Sample Obey Files
SAMPLE OBEY FILES
Figure 12-29 shows a sample obey file that establishes the
PATHWAY system.
-----------------------------------------------------------------
| |
| PURGE projlog <----------- purges the current PATHCOM |
| |
| CREATE projlog <---------- creates a new PATHCOM log file |
| |
| PATHMON/NAME $one, NOWAIT, |
| CPU 0, OUT projlog/ <--- creates a PATHMON process |
| |
| PATHCOM/IN prfile1/$one <- cold starts PATHWAY from |
| information in the named |
| PATHCOM command file |
| |
| PATHCOM $one; START TCP ENABLE-TCP <- starts the TCP |
| |
| PATHCOM $one; START TERM TERM01 <- starts execution of a |
| SCREEN COBOL program |
| for one terminal in |
| the PATHWAY system |
| |
| Note that if you want to execute your applications by |
| entering a PATHCOM RUN PROGRAM command, omit the START |
| TERM command from your obey file and create a separate |
| obey file that contains the following: |
| |
| PATHCOM $one;RUN MENU |
| |
-----------------------------------------------------------------
Figure 12-29. Sample Obey File That Establishes the PATHWAY
System
Figure 12-30 shows the contents of a sample obey file that
suspends the PATHWAY system.
-----------------------------------------------------------------
| |
| PATHCOM $one; SHUTDOWN, WAIT |
| |
-----------------------------------------------------------------
Figure 12-30. Sample Obey File to Suspend the PATHWAY System
12-59