HP 3000 Manuals

SUBMIT [ SNA NRJE User/Programmer Reference Manual ] MPE/iX 5.0 Documentation

SNA NRJE User/Programmer Reference Manual

SUBMIT

Prepares a batch input job stream for transmission to a host system.

Parameters

Infile Identifies a file to be submitted. An Infile can be a qualified or
unqualified file designator, or a formal file designator which has
been equated with an actual file designator. See the discussion
below for additional information on Infile designation.

System files $NULL, $STDLIST, and $NEWPASS are not allowed as
Infiles.

For both $STDIN and $STDINX, you must close with :EOD.

You must specify at least one Infile; you can specify up to five.

NOTRANSLATE Indicates that the contents of the Infile should not be translated
into the character code configured for the host system.

If you indicate (N) for some Infiles, the other Infiles will be
translated while being stored in the transmission queue. You cannot
use (N)OTRANSLATE and DIRECT together.

If you omit this parameter, the default value configured for the
workstation in the NMMGR Reader Data screen is used.

DIRECT When you use this parameter, translation and compression will be done
during transmission to the host.

You cannot use NOTRANSLATE and DIRECT together.

n Identifies a spool file transmission queue priority number. The
highest priority is 14, and the lowest is 1.

Job transmission to the host can be deferred by specifying a priority
value less than or equal to the reader fence value, RDRFENCE, for a
workstation. If RDRFENCE=0, then OUTFENCE, an MPE parameter, is used
to select job spool files for transmission to the host. The
configuration of RDRFENCE is described in the SNA NRJE Node Manager's
Guide.

If you omit this parameter, the MPE-configured default is used.

Name Identifies a job when it is in a transmission queue. You can use
this Name in subsequent NRJE commands.

A Name must begin with a letter and may contain up to eight
alphanumeric characters.

If you give several jobs the same Name, then other NRJE commands,
such as SHOW, can refer to all job files with that Name.

If you omit this parameter, the job you submit and output from the
job are assigned the name specified in the JCL JOB card.

Wsid Identifies an alternate NRJE workstation on your node to which this
command applies. The job will be submitted to the reader in the
specified alternate workstation.

You normally omit this parameter and submit jobs to the workstation
you identified in the NRJE command. This parameter does not alter
the default workstation for subsequent commands.
PrintFile Used to specify routing for output data sets that are sent to an NRJE
logical printer on the standard form.

PunchFile Used to specify routing for output data sets that are sent to an NRJE
logical punch on the standard form.

FormFile Refers to print or punch output routed to any form other than the
standard form.

PR=, PU=, and FO= specifications require the use of the Job Log. Use
of these parameters is not supported for workstations connected to a
VSE/POWER host.

One of each type of file (PRINT, PUNCH, and FORMS) can be specified
by any of the following:

* A formal file designator (*fileid) which backreferences an actual
file designator.

* The logical device number (ldev) of an MPE output device (numeric
entry).

* An MPE device class name, enclosed in double quotation marks
("DevClass").

* An actual file designator (alphanumeric). The file must be built
before the job is submitted. Both the user and MANAGER.SYS must
have READ/WRITE access to the destination file.

* An alternate form name (formid) used as a key into the Lookup
Table. This designation is made with single quotation marks
('formid'). This designation references a predefined file
equation in the NRJE output management Lookup Table. See below
under "Default FOPEN Parameters Used," and under "Job and Output
Management" in Chapter 4 for additional information.

Limitations:

* The total length of PrintFile, PunchFile, and FormFile entries
cannot exceed 197 bytes. Each item cannot exceed 86 bytes in
length.

* SNA NRJE does not support NOWAIT I/O, MULTIRECORD ACCESS, or any
combination of file equation attributes which require Privileged
Mode to open the file.

* The maximum record width for output files is 255 bytes and the
minimum is 40 bytes. Output directed to files which are not wide
enough to accommodate the received data records may be wrapped by
NRJE. If a received record exceeds the width of the destination
file, output is segmented and any extra characters are written to
the line immediately following the truncated record.
MaxRecSize Identifies the maximum record size (in bytes) that will be
encountered in the Infiles or ##FD files. The minimum usable value
is 80. The maximum usable values are as follows:

* 248 for JES2 or JES3 workstations that use a 256-byte RU.

* 252 for JES2 or JES3 workstations that use a 512-byte RU.

* 128 for VSE/POWER workstations.

The default MaxRecSize is 80.

No intrinsic (programmatic) support is provided for this parameter.

Description

The SUBMIT command enables you to prepare a set of Infiles for
transmission to a host system. You can specify up to five Infiles in a
SUBMIT command. Taken together, these files can contain one or more host
system batch jobs.

The host jobs contained in the submitted Infiles (and any included ##FD
files) are broken into separate spool files. A list of the SpoolfileIDs
of the jobs is returned to you. If the submitted files comprise more
than 30 host jobs, all jobs are submitted to the host, but only the first
30 SpoolfileIDs are returned.

Infile Designation

An Infile can be a file reference, or a formal file designator that has
been equated with an actual file designator by a backreference
indication.

A file reference is in the following form:

Infile[/LockWord][.GrpName[.AcctName]][:Envid]

GrpName and AcctName refer to the group name and account name,
respectively, where the file is located. If you do not specify an
:Envid, the default values for GrpName and AcctName are those for your
logon on your HP 3000.

SNA NRJE provides the capability of submitting files that are stored at
remote locations. The :Envid parameter is used to identify the remote
location from which the file is to be submitted. This capability is
possible if you have either DS/3000 services in a point-to-point
connection to the remote, or NS/3000 services if you are connected in a
Local Area Network (LAN) with the remote.

If you have DS/3000 services, :Envid is a character string representing a
specific logon session on the remote. If you have NS/3000 services on
your HP 3000, :Envid is the name assigned to the remote node as it is
configured into the LAN. Refer to the NS/3000 User/Programmer Reference
Manual for additional information on designating :Envid.

If you specify an :Envid, the default GrpName and AcctName are those of
your logon on the remote machine.

Formal file designators backreference actual file designators and must be
prefixed with an asterisk ( *). Actual file designators are specified in
FILE equations created prior to the backreference.

An example of a formal file designator is IN, where a backreference is
made to an MPE FILE statement that identifies card reader images of
80-byte records:

:FILE IN;DEV=TAPE;REC=-80,16,F,ASCII
:NRJE RMT9
...
RMT9>SUBMIT *IN
...

Translation

While preparing your Infiles for transmission, NRJE can perform all
necessary data translation. You can vary this process by entering
various combinations of parameters. You can utilize these parameters to
inhibit translation for a variety of reasons, for example, if a file
contains non-printable characters such as packed decimal numerical data .

Files submitted already translated must contain only one host record per
HP 3000 file record. SNA NRJE expects the following in each record:

* An SNA String Control Byte (SCB) in byte 0.

* A TRN SNA Character String (SCS) control word in bytes 1 and 2.

* An IRS SCS , which is used to delimit records, as the last byte.

If these restrictions are not met, NRJE features such as job management
and output management and support of ##FD files may not function
correctly for these jobs.

Default FOPEN Parameters

Table 3-3 lists the default FOPEN parameters that NRJE uses when opening
the output file for PRINT output. (Differences for PUNCH and FORMS
output are noted after Table 3-3.)

Table 3-3. Default FOPEN Parameters

1 If a job generates multiple datasets to the same form, and output
is directed to a disc file, then read/write access is used for the
first data set only. All subsequent data sets are written with
append access .

PUNCH output differences: For PUNCH output, the parameters are the same
as described in Table 3-3, except that NRJE specifies NOCCTL and BINARY.

FORMS output differences: If you are using the FORMS= option, NRJE uses
the options specified in Table 3-3, except for using NOCCTL and BINARY if
punch output is routed to a special form. Also, if FORMS output is
routed without a Lookup Table, or if FORMS output is routed to a device
class or ldev, the name of the form is passed in the forms field of the
FOPEN intrinsic.

This causes a hard copy forms mount request for the form specified to be
sent to the HP 3000 console when the spoolfile goes active. If the FCB
field is specified in your JCL, and FORMS output is routed without the
Lookup Table, and you do not specify any alternate PR=, PU=, or FO=
destinations, the FCB field is passed to FOPEN as an environment file
name in the group HPENV.SYS. Note that in all other cases, the FCB field
of the PDIR is ignored.

NOTE You can override the default FOPEN options by specifying a
backreferenced formal file designator; for example,

FILE out=myfile;acc=append

Then, in the SUBMIT command include the following:

;PU=*out

You may track the progress of your job using the host console facility.
NRJE users may access the console provided that one or more console
commands have been allowed to users by the NRJE manager. Refer to the
SNA NRJE Node Manager's Guide for additional information on console
commands.

Other Parameters

Unless you are routing with PR=discfilename, NRJE specifies a record size
of 256 bytes and uses the number of copies specified in the PDIR. This
value is set by the host in response to the number of copies specified in
your JCL. NRJE uses the priority configured in the NMMGR Writer Data
Screen for the logical writer on which the output was received.

Console Commands

Console commands can be embedded in a submitted file. If included, these
commands must precede the JCL JOB card. If multiple jobs are included in
an input file, the host commands must precede the first JCL JOB card.
Embedded console commands between jobs in a single input stream are not
supported.

Note that "single input stream" means either a single input file with
multiple JOB cards or multiple input files entered with a single SUBMIT
command. If you have NM capability, or the embedded command is one of
those allowed to all users (specified in the NMMGR Workstation Data
screen ), the console command is passed on as part of the job.
Otherwise, the command is stripped out and an error message is displayed.
The remainder of the job is submitted. SIGNOFF cards are stripped from
the input stream and an error message is displayed.

Embedded console commands must be preceded by a host console command
prefix so that they are recognized as commands. The host console command
prefix you use depends on the host system to which you are connected:

* JES2: commands must be preceded by /*[], where [] is the host
command prefix configured for your workstation in the NMMGR
Workstation Data screen.

* JES3: commands must be preceded by //*[], where [] is the host
command prefix configured for your workstation in the NMMGR
Workstation Data screen.

* VSE/POWER: commands must be preceded by *� . . �, where � is a
required space.

NOTE The asterisk (*) is required by NRJE to parse console commands and
is not required by the host.

Additional Notes

The communications line to a host must be opened before the subsystem can
transmit files in the corresponding transmission queue of the
workstation. The communications line is opened as part of the
workstation startup.

In executing a SUBMIT command, NRJE prepares a spool file, but it does
not send the file to a host. If the communications line is down, your
files remain in the transmission queue. Once the communications line is
open, NRJE can transmit the spool files that have a priority greater than
the ReaderFence value, or if that value is zero, the MPE OutFence. The
subsystem defers files that have a priority less than or equal to the
operative fence value.

NRJE transmits undeferred files that have the highest priority first.
You can influence the initial position of a file in a transmission queue
by using the PRIORITY parameter in the SUBMIT command.

You can specify a particular workstation transmission queue by entering
the WSID=Wsid parameter in this command. If you omit the Wsid parameter,
this command refers to the transmission queue of the default workstation.
You establish a default workstation by using the Wsid parameter when you
start an NRJE workstation with an NRJE command.

Output from job streams is received when the communications line with the
host system is active. See Chapter 4 for a discussion of how job output
is received. Also see Chapter 3 of the Installing and Troubleshooting
SNA NRJE manual or the SNA NRJE Node Manager's Guide for information on
what to do when your output appears to go to the wrong destination.

CAUTION Do not direct multiple output data sets of different types (that
is, PRINT, PUNCH, or FORMS) to the same disc file; for example,

SUBMIT myjob;PR=myfile;FO=myfile

This causes data to be overwritten in the file myfile.

This example causes a copy of the file myjob to be placed in the NJRE
reader queue with a transmission priority of 9. If the link to the host
system is up, myjob is transmitted when it is the first in the queue.
Successful submittal is indicated by a message also identifying the spool
file.

Output data sets directed by your JCL to the host standard form on a
logical printer device are routed according to the attributes in the file
equation FILE outlist ... (determined by the pr=*outlist parameter).

Output data sets directed by your JCL to any special form on a printer or
punch logical device are routed according to the attributes in the Lookup
Table under the entry long.
_____________________________________________________________________________
| |
| R20>SUBMIT FRONTJCL,BINDATA(NOTRANSLATE),BACKJCL |
| |
| JOB SUCCESSFULLY SUBMITTED. THE SPOOL FILE IS: |
| #O95 |
| R20>... |
_____________________________________________________________________________

This example demonstrates how to submit binary data to a host. Three
Infiles are concatenated to one job file. The file FRONTJCL begins the
job stream, followed by file BINDATA and then BACKJCL.

The NOTRANSLATE parameter after the BINDATA file name indicates that it
has already been translated into the character code configured for the
host system.

Multiple files can be included by submitting a single file that contains
##FD statements referencing the JCL and/or data files. See "Job Input"
in Chapter 2, "Getting Started," for suggestions and examples.

Text Reference

The intrinsic for this command is NRJE2Submit. It is described in
Chapter 5, "User Intrinsics."

MPE/iX 5.0 Documentation