SUBMIT

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

At least one valid job card must be contained within an Infile specified with SUBMIT. This job card may be contained within the Infile or any included ##FD file. The job card must adhere to the following format:

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:

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.

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

PUNCH output differences: For PUNCH output, the parameters are the same as described in Table 3-3 “Default FOPEN Parameters”, 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 “Default FOPEN Parameters”, 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.

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 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:

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

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 “Job Output” for a discussion of how job output is received. Also see 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 disk file; for example, SUBMIT myjob;PR=myfile;FO=myfile This causes data to be overwritten in the file myfile.