SQL/MP Programming Manual for COBOL85

Program Execution
HP NonStop SQL/MP Programming Manual for COBOL85—429326-004
7-4
Running a Program in the OSS Environment
For more information about the CREATEPROCESS routine, see the COBOL85 for
NonStop Systems Manual.
Running a Program in the OSS Environment
After successfully compiling your COBOL program with the cobol utility in the OSS
environment, you have an executable object file. Its name is either a.out (by default)
or the name you gave it with the -o flag. If the current directory is in your search path,
you can run your program by typing the name of the executable object file and
pressing the Return key. For example, if the name of the executable object file is
a.out, enter:
a.out
If the current directory is not in your search path, add it with this command:
export PATH=$PATH:.
In an OSS environment, you execute a program file by entering its name at the OSS
shell prompt and pressing the Return key. The current directory must be in your search
path. If the current directory is not in your search path, add it with this command:
export PATH=$PATH:.
You can also use the OSS run command to run a program file by using HP attributes
(for example, a CPU or priority for the process). For example, to run the program with
the Inspect symbolic debugger, enter:
run -debug a.out
For information about the run command, see the Open System Services Shell and
Utilities Reference Manual.
The COBOL85 for NonStop Systems Manual also has detailed information on running
COBOL programs from the OSS environment.
Running a Program at a Low PIN on a
D-Series Node
The operating system identifies a process (a running program) by a unique process
identification number (PIN). In displays and printouts, a PIN usually appears after the
number of the processor (CPU) where the process is running. For example, the
operating system identifies a process in processor 4 with PIN 195 as 4,195.
The D-series operating system supports an architectural limit of 65,535 concurrent
processes per processor. The actual number of concurrent processes depends on the
available system resources (such as virtual memory) and the values specified during
system generation.