Jump to content

NetBatch:NBEXEC/Starting NBexec: Difference between revisions

Content deleted Content added
No edit summary
No edit summary
Line 40: Line 40:
|+ Commands may be abbreviated.
|+ Commands may be abbreviated.
|-
|-
! Command !! Value !! Example !! Description
! Command
! Argument(s)
! {{nowrap|Example}}
! Description
|-
|-
| '''{{color|red|A}}'''PPEND || {{Na}} || A || Specifies that output is to be appended to the current list file if it exists. NBEXEC defaults to overwrite the <list file> if one exists.
| '''A'''{{small|PPEND}} || {{Cross}} || {{nowrap|{{kbd|A}}}} || Specifies that output is to be appended to the current list file if it exists. NBEXEC defaults to overwrite the <list file> if one exists.
|-
|-
| '''{{color|red|B}}'''ACKUPCPU || <cpu> || {{kbd|B 15}} || NBEXEC is able to function as a NonStop process. If the primary CPU running NBEXEC fails, a backup copy can takeover, determine what recovery the job may require, and resume execution from the appropriate place in the input control file. The number <cpu> must be the number of an available CPU, and must not be the CPU allocated to the EXECUTOR under which NBEXEC is started. Use -1 to indicate that NBEXEC should start its backup process in the highest available CPU.
| '''B'''ACKUPCPU || <cpu> || {{nowrap|{{kbd|B 15}}}} || NBEXEC is able to function as a NonStop process. If the primary CPU running NBEXEC fails, a backup copy can takeover, determine what recovery the job may require, and resume execution from the appropriate place in the input control file. The number <cpu> must be the number of an available CPU, and must not be the CPU allocated to the EXECUTOR under which NBEXEC is started. Use -1 to indicate that NBEXEC should start its backup process in the highest available CPU.
|-
|-
| '''C'''{{small|LASS}} || <cname> || {{kbd|1=C payroll}} || Specifies <cname> of up to eight alphanumeric characters to appear on the <list file> header page and possibly the spooler REPORTNAME. See the SPOOLREP attribute for details.
| '''C'''{{small|LASS}} || <cname> || {{nowrap|{{kbd|C&nbsp;payroll}}}} || Specifies <cname> of up to eight alphanumeric characters to appear on the <list file> header page and possibly the spooler REPORTNAME. See the SPOOLREP attribute for details.
|-
|-
| '''D{{small|PBUG}} || {{Na}} || D || Is used to force NBEXEC to call DEBUG. This is only useful for debugging purposes when NBEXEC is run at a terminal rather than as a NetBatch job.
| '''D{{small|PBUG}} || {{Na}} || D || Is used to force NBEXEC to call DEBUG. This is only useful for debugging purposes when NBEXEC is run at a terminal rather than as a NetBatch job.
|-
|-
| '''ID''' || <id> || {{nowrap|{{kbd|ID&nbsp;A2345678}}}} || Assigns a name of one alphabetic plus up to seven alpha numeric characters to a job to distinguish it among other jobs on the same <class>. Lower case characters are upshifted. This name appears on the job list file.
| Example || Example || Example
|-
|-
| '''ID''' || T{{small|ERM}} || {{nowrap|{{kbd|ID&nbsp;T}}}} || An <id> of "TERM" or "T" will cause NBEXEC to emulate a physical terminal, rather than a process. Processes compiled using COBOL74 ACCEPT/DISPLAY verbs will run under control of NBEXEC if ID TERM is specified. Before using ID TERM, users should be aware that many programs behave differently when they read commands from a terminal. For example, it is common for a program to request a continuation response when a full screen of output has been displayed.
| Example || Example || Example
|-
|-
| '''L'''{{small|ABEL}} || <label> || {{nowrap|{{kbd|L WORK010}}}} || Causes NBEXEC processing to begin at the specified label in the control file.
| Example || Example || Example
|-
|-
| '''L'''{{small|IMIT}} || <hh:mm> || {{nowrap|{{kbd|L 02:00}}}} || Specifies a maximum time limit for the NBEXEC job. Must be between 00:00 and 99:59, with the default being 01:00 (one hour).
| Example || Example || Example
<br>
NBEXEC will abort the job once this limit is exceeded logging the fact to <list file>. Jobs will issue a warning message to both the job list file and the supervisor log 15 minutes before timing out.
|-
|-
| '''N'''{{small|AME}} || <mname> || {{nowrap|{{kbd|N JOB45679}}}} || Specifies a name of up to eight alphanumeric characters to appear on the <list file> header page. It will be used by NBEXEC when identifying itself in $MESSAGE commands (rather than the control file name) and it can be used when building a spooler REPORTNAME attribute for the <list file>. See the SPOOLREP attribute for details.
| Example || Example || Example
|-
|-
| '''P'''{{small|RGE}} || {{na}} || {{nowrap|{{kbd|P}}}} || Specifies that the list file will be purged if the job terminates successfully. Therefore, if
| Example || Example || Example
<br>
::$IF #ERROR returned TRUE,
or
::$IF NOT #ERROR returned FALSE, or processing errors occurred,

the list file would be created. If the list file is the spooler and the job terminates successfully, the spooler entry is not deleted.
|-
|-
| '''S'''{{small|POOLREP}} || <c> || {{nowrap|{{kbd|S U}}}} || Controls the format of the REPORTNAME spooler attribute when <list file> is a spooler collector.
| Example || Example || Example

::{| class="wikitable"
! <c> !! REPORTNAME
|-
|-
| '''C'''{{small|LASS<}} || <cname> grp usr
| Example || Example || Example
|-
|-
| '''U'''{{small|SER}} || GROUP USER
| Example || Example || Example
|-
|-
| '''J'''{{small|OBNAME}} || <mname> grp usr
| Example || Example || Example
|}

where <cname> defaults to <mname> which in turn defaults to the <control file> name. GROUP, grp,
and USER, usr correspond to the Guardian90 UserID name and number of the NBEXEC process owner.
|-
| '''SY'''{{small|NTAX}} || {{na}} || {{nowrap|{{kbd|SY}}}} || Is specified to perform syntax validation of control cfile only.

When NBEXEC begins processing a control file, it first scans the file to locate labels, and validate
that there are no obvious syntax errors. If errorsare detected, the job will terminate immediately.
If SYNTAX was specified, the job always terminates after the syntax check. SYNTAX would normally beused immediately after altering a control file to verify that no mistakes were made.
|-
| '''X'''{{small|PRI}} || <xpri> || {{nowrap|{{kbd|X #}}}} ||
|-
|-
| Example || Example || Example
| Example || Example || Example || Example
|}
|}

==Examples==
Commands may be abbreviated.

The following example shows how to prevent NBEXEC from running more than two hours:
<command> is one of:
<div style="width: 80ch">
{{terminal|title=TACL|text=1> NBEXEC/NAME, IN X, OUT $S/L2:0}}
A[PPEND]
</div>
or via $ZBAT, the default NetBatch scheduler:
B[ACKUPCPU] <cpu>

<div style="width: 80ch">
C[LASS] <cname>
{{terminal|title=TACL|text=1> BATCHCOM; SUBMIT REPORT,IN REPORT,OUT $S, STARTUP "L E-O-M,L2:0"}}
</div>
D[PBUG]

{{kbd|L}} is an abbreviation of the command "LIMIT". "LIMIT" is the command used to specify a time limit for a job, while "2:0" is the value accompanying "LIMIT".
ID <id>
{{kbd|L}} is also a valid abbreviation of the command "LABEL".

L[ABEL] <label>
The following example shows how to make NBEXEC emulate a physical terminal for use by the processes created during the job:

L[IMIT] <hh:mm>
<div style="width: 80ch">
{{terminal|title=TACL|text=2> NBEXEC/IN COMP/ID T}}
N[AME] <mname>
</div>
The following example shows how to make NBEXEC perform a syntax check on a single control file:
P[URGE]
<div style="width: 80ch">
{{terminal|title=TACL|text=3> NBEXEC/IN CTRL/SY}}
S[POOLREP] C[LASS]
</div>
U[SER]
J[OBNAME]
SY[NTAX]
X[PRI] <xpri>
AP[PEND] Specifies that output is to be appended to the
current list file if it exists. NBEXEC defaults to
overwrite the <list file> if one exists.
$BIG1.T9190IPM.NBEXDOC - V1.6 - 09Sep1994 - 16 Feb 2026
2-2
NetBatch T9190D30 - NBEXEC - User Manual
STARTING NBEXEC
B[ACKUPCPU] <n> NBEXEC is able to function as a NonStop process.
If the primary CPU running NBEXEC fails, a backup
copy can takeover, determine what recovery the job
may require, and resume execution from the
appropriate place in the input control file. The
number <n> must be the number of an available CPU,
and must not be the CPU allocated to the EXECUTOR
under which NBEXEC is started. Use -1 to indicate
that NBEXEC should start its backup process in the
highest available CPU.
C[LASS] <cname> Specifies <cname> of up to eight alphanumeric
characters to appear on the <list file> header page
and possibly the spooler REPORTNAME. See the
SPOOLREP attribute for details.
D[PBUG] Is used to force NBEXEC to call DEBUG. This is only
useful for debugging purposes when NBEXEC is run at
a terminal rather than as a NetBatch job.
ID <id> Assigns a name of one alphabetic plus up to seven
alpha numeric characters to a job to distinguish it
among other jobs on the same <class>. Lower case
characters are upshifted. This name appears on the
job list file.
ID T[ERM] An <id> of "TERM" or "T" will cause NBEXEC to
emulate a physical terminal, rather than a process.
Processes compiled using COBOL74 ACCEPT/DISPLAY
verbs will run under control of NBEXEC if ID TERM
is specified. Before using ID TERM, users
should be aware that many programs behave
differently when they read commands from a
terminal. For example, it is common for a program
to request a continuation response when a full
screen of output has been displayed.
L[ABEL] <label> Causes NBEXEC processing to begin at the specified
label in the control file.
<label> Is one to thirty alpha numeric characters that
may be hyphenated. <label> must be defined within
the control file.
L[IMIT] <hh:mm> Specifies a maximum time limit for the NBEXEC job.
Must be between 00:00 and 99:59, with the default
being 01:00 (one hour).
NBEXEC will abort the job once this limit is
exceeded logging the fact to <list file>. Jobs will
issue a warning message to both the job list file
and the supervisor log 15 minutes before timing out.
$BIG1.T9190IPM.NBEXDOC - V1.6 - 09Sep1994 - 16 Feb 2026
2-3
NetBatch T9190D30 - NBEXEC - User Manual
STARTING NBEXEC
N[AME] <mname> Specifies a name of up to eight alphanumeric
characters to appear on the <list file> header page.
It will be used by NBEXEC when identifying itself
in $MESSAGE commands (rather than the control file
name) and it can be used when building a spooler
REPORTNAME attribute for the <list file>. See the
SPOOLREP attribute for details.
PU[RGE] Specifies that the list file will be purged if the
job terminates successfully. Therefore, if
$IF #ERROR returned TRUE,
or $IF NOT #ERROR returned FALSE,
or processing errors occurred,
the list file would be created.
If the list file is the spooler and the job
terminates successfully, the spooler entry is not
deleted.
S[POOLREP] <c> Controls the format of the REPORTNAME spooler
attribute when <list file> is a spooler collector.
<c> REPORTNAME
___________ _______________
C[LASS] <cname> grp usr
U[SER] GROUP USER
J[OBNAME] <mname> grp usr
where <cname> defaults to <mname> which in turn
defaults to the <control file> name. GROUP, grp,
and USER, usr correspond to the Guardian90 UserID
name and number of the NBEXEC process owner.
SY[NTAX] Is specified to perform syntax validation of control
file only.
When NBEXEC begins processing a control file, it
first scans the file to locate labels, and validate
that there are no obvious syntax errors. If errors
are detected, the job will terminate immediately.
If SYNTAX was specified, the job always terminates
after the syntax check. SYNTAX would normally be
used immediately after altering a control file to
verify that no mistakes were made.
>NBEXEC/NAME, IN <ctrl>/SYNTAX
$BIG1.T9190IPM.NBEXDOC - V1.6 - 09Sep1994 - 16 Feb 2026
2-4
NetBatch T9190D30 - NBEXEC - User Manual
STARTING NBEXEC
Examples
The following example shows how to prevent NBEXEC from running more
than two hours:
1> NBEXEC/NAME, IN X, OUT $S/L2:0
or via $ZBAT, the default NetBatch scheduler:
1> BATCHCOM; SUBMIT REPORT,IN REPORT,OUT $S, STARTUP "L E-O-M,L2:0"
"L" is an abbreviation of the command "LIMIT". "LIMIT" is the
command used to specify a time limit for a job, while "2:0" is the
value accompanying "LIMIT".
"L" is also a valid abbreviation of the command "LABEL".
The following example shows how to make NBEXEC emulate a physical
terminal for use by the processes created during the job:
2> NBEXEC/IN COMP/ID T
The following example shows how to make NBEXEC perform a syntax check
on a single control file:
3> NBEXEC/IN CTRL/SY

Debug data: