Guardian Programmer's Guide

Table Of Contents
Creating and Managing Processes
Guardian Programmer’s Guide 421922-014
16 - 35
Specifying Process Attributes and Resources
ERROR_DETAIL,
OUTPUT_LIST:$LEN(OUTPUT_LIST),
OUTPUT_LIST_LEN);
IF ERROR <> 0 THEN ...
Specifying a Device Subtype
You can assign a device subtype attribute to a process at compile or link time. (There
is no input parameter to PROCESS_LAUNCH_ for specifying a subtype attribute.)
One use for giving a process a device subtype is when creating a terminal simulation
process as described in Section 24, Writing a Terminal Simulator.
The HP linkers (the nld and Binder utilities) and the TNS compilers provide directives
that allow you to assign a device subtype to a program file. For details, see the
appropriate compiler manual; also see the nld and noft Manual or the Binder Manual.
For H-series software, see the nld Manual and the noft Manual as well as the Binder
Manual
Each subtype is an integer value. There are 64 possible values:
Subtype zero is the default value.
Subtypes 1 through 47 are reserved for HP use.
Subtypes 48 through 63 are available for general use; you can create a named
process with a device subtype in this range.
Specifying a CPU
Normally, a new process runs on the same CPU as its creator process. However, you
can use the CPU field of the input parameter structure of the PROCESS_LAUNCH_
procedure to specify a CPU. The following example runs a new process on CPU
number 6:
.
.
PARAM_LIST.CPU ':=' 6;
ERROR := PROCESS_LAUNCH_( PARAM_LIST,
ERROR_DETAIL,
OUTPUT_LIST:$LEN(OUTPUT_LIST),
OUTPUT_LIST_LEN);
Specifying a New Job
For applications that do batch processing, you can use the JOBID field of the input
parameter structure of the PROCESS_LAUNCH_ procedure to specify a new job.
For batch processing, you can group related processes into jobs by assigning the
same job number to each process. The job number is interpreted by the NetBatch
utility to establish the members of a given job.