NetBatch:NBEXEC/Starting NBexec: Difference between revisions

<div style="width: 80ch">

{{terminal|title=TACL|text=

>RUN NBEXEC/NAME [<pname>], IN <control file> &

[,OUT <list file>]/[<command>,...]

}}

</div>

:or

<div style="width: 80ch">

{{terminal|title=TACL|text=

>BATCHCOM;SUBMIT <job-name>, IN <control file> [,OUT <list file>] &

, EXECUTOR-PROGRAM NBEXEC &

[, STARTUP "<command>,..." ]

}}

</div>

:where:

<control file> Is the control file that NBEXEC will execute. This file must be a TANDEM EDIT format file.

<list file> Is a non disk device, process or disk file to which the output listing is directed.

<command> Is a string containing one or more NBEXEC startup instructions. <command> is limited by NetBatch to a maximum of forty bytes.

If <list file> is a disk file, the following rules apply:

* If the file does not exist, an entry-sequenced file is created, with a logical record length of 132 characters and with primary and secondary extents set to 10.

* If the file already exists, it must be either entry-sequenced, relative, or unstructured.

* If it is entry-sequenced or relative, then the logical record length at creation will be used. This length need not be greater than 132.

* If unstructured, a logical record length of 132 characters will be presumed.

* The <list file> extent sizes must be chosen to suit the expected amount of output listing.

:If <list file> is left blank, the output is suppressed.

:If the whole OUT option is omitted, the normal defaults apply. For TACL this is usually the home terminal. For NetBatch, this is configured for your scheduler.

==NBEXEC Startup Commands==

NBEXEC startup commands are in the form:

:{{code|[ name [ value ] ] #, ...}}

:where name is an identifier consisting of one or more alphabetic characters, and value is some text associated with the identifier. Alphabetic values must be separated from the name by at least a single space. Consecutive identifiers may be separated by commas {{button|,}}, or semicolons {{button|;}}.

{| class="wikitable"

|+ Commands may be abbreviated.

|-

! Command !! Value !! 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.

|-

| '''{{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.

|-

| '''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.

|-

| '''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.

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|-

| Example || Example || Example

|}