HP 3000 Manuals HP 3000 Manuals
Job Output Handling
SNA NRJE's control hierarchy for resolving any potentially conflicting
output routing specifications is as follows:
1. Use the SUBMIT command specifications PR, PU, or FO, if supplied.
2. If no SUBMIT command routing specifications are supplied, use the
Lookup Table.
3. If no specifications are in the SUBMIT command and the Lookup
Table is not in use, route the data sets to the default
destination specified in the NMMGR Writer Data Screen.
4. When configuring your NRJE workstation, you have the option of
configuring a 'formid' in the Output Destination field of the
NMMGR Writer Data screen. (This screen is described in the SNA
NRJE Node Manager's Guide and the SNA Link Reference Manual.)
This 'formid' must be a valid entry in the Lookup Table for the
workstation.
You can configure your system to use this 'formid' to route output
received from the host. On the NMMGR Writer Data screen, set the
field identified as "FORCED" as follows:
* To route all output to 'formid', set FORCED=Y
* To route only standard form output to 'formid', set FORCED=N.
NOTE Note that FORCED=Y option is valid only when a 'formid' is
configured in the Output Destination field.
The following table illustrates how NRJE resolves output routing
specifications for each data set. This resolution depends on whether the
user selects a special form (under the Selected Form in JCL heading) and
how the writer is configured (under the Writer Data Screen Specifications
heading).
In table 4-1, FORM "X" represents any JCL-selected form. CLASS "A"
represents any valid device class, and LDEV "N" represents any valid
ldev. For example, if you routed output to a JCL-specified form (FORM
"X"), configured a 'formid' in the Output Destination field, and
specified FORCED=Y, output for both the standard form ('STD') and the
JCL-specified form (FORM "X") would be routed to the 'formid'.
Table 4-1. JES2 Example for Default Output Destination
![[]](../../pic3k/M010428/TA04013c50.gif)
General Considerations
Regardless of the method you use to control the output returning from the
host, a number of general considerations must be taken into account:
* Matching data set output class to device output class.
* Handling carriage control characters.
* Controlling output directed to an HP 268xx laser printer.
* The structure of the Peripheral Device Information Record (PDIR).
* Routing standard forms output.
* Routing special forms output.
* Specifying multiple copies.
* Routing output to disc files.
* Routing output to tape files.
This subsection describes those features.
Host Output Classes and Logical Writers
Output data sets are routed to logical writers configured for your NRJE
workstation. The routing is based on a match between the class of the
output and the classes assigned to the logical output devices. This
match can be determined by combining the following:
* The workstation configuration at the host; specifically, the classes
that are defined for each of the logical output devices configured
for your remote,
and
* The JCL in your job, which defines the class of the output data sets,
and
* The use of host job entry subsystem console commands, if you are an
NRJE manager.
Host Configuration. The configuration of logical writers and output
classes is described in the SNA Link Services Reference Manual or the SNA
NRJE Node Manager's Guide. Also, see the preface of this manual for a
list of IBM publications.
JCL Class Specification. You associate data sets with output classes by
using JCL in your jobs. The specific statements you use depend on the
operating system (either MVS or VSE) and the job entry subsystem of the
host to which you are connected.
MVS JCL Class Specification
If you are connected to an MVS host system (using either JES2 or JES3),
associate the output data sets with a specific output class in the
following ways:
* The class subparameter of the SYSOUT parameter as part of a DD
statement; for example,
// DD...SYSOUT=x
where x is a class letter
and/or
* The MSGCLASS parameter of the JOB statement; for example,
// JOB...MSGCLASS=x
where x is a class letter
MVS JCL Class Example
Use JCL statements as shown in Figure 4-1.
// DD...SYSOUT=(A,,P2) The first subparameter of SYSOUT is the
class letter A. The third subparameter
indicates special form names, in this case
P2.
Output would be received on a logical device
that is configured on the host to be
associated with output class=A, or on a
logical device that has been modified
by console command to be associated
with class=A. The required console
commands are described in "Host Job Entry
Subsystem Console Commands" later in this
chapter.
// JOB...MSGCLASS=D This statement causes JCL message data sets
to be sent to a logical output device
that is configured or modified by
console command to be associated with
class=D.
Figure 4-1. MVS JCL Example
VSE/POWER JECL Class Specification
If you are connected to a VSE host system (using VSE/POWER), associate
the output data sets with a specific output class in the following way:
* The CLASS=class parameter of either the * LST statement or the *
PUN statement; for example,
* LST,CLASS=x
where x is a class letter.
Host Job Entry Subsystem Console Commands. Each supported host job entry
subsystem has interactive methods by which you can use console commands
to match the class of the output to the class of a logical output device.
JES2 Commands
If you are in the Host Console Facility, you can use the JES2 $T (Set)
command to relate a class to a logical writer. See the IBM publication
Operator's Library: JES2 Commands (SC23-0048).
Examples
$T R11.PR1,Q=A Job output for class A (Q=A) goes to printer 1
(R11.PR1).
$T R11.PR3,Q=A If you have done the previous $T command, job
output for class A goes to PR1 or PR3 (R11.PR1,
R11.PR3.)
$T R11.PR2,Q=DE Job output for classes D and E (Q=DE) goes to PR2
(R11.PR2).
JES3 Commands
If you are connected to a JES3 host system, the console operator command
that you use to modify the class of a logical output device is the
*START(*S) command: *S,dev,WC=cls,cls,.... See the IBM publication
Operator's Library: OS/VS2 MVS JES3 Commands (GC23-0008).
Example
*S,PR1,WC=A,P This command modifies the device PR1 so that it is
associated with output classes A and P.
VSE/POWER Commands
If your NRJE workstation is connected to a VSE/POWER host system, you can
modify the class of the output to match the class of a logical output
device configured on your host as your remote. The command that you use
is the ALTER (A) command:
[]A,queue,jobname,CLASS=class where [] is the host command prefix
that you have configured in the NMMGR
Workstation Data screen for your
workstation; queue is either LST for
list queue output, or PUN for punch
queue output; jobname is the name you
used on your VSE/POWER JECL or VSE JCL
JOB statement; and class is an
alphabetic (A-Z) character.
See the IBM publication VSE/POWER
Remote Job Entry User's Guide
(SH12-5328).
Example
*A,PUN,MYJOB,CLASS=A This command alters the punch output for MYJOB
to class A. In this example, the host console
command prefix character has been configured to
be an asterisk (*).
Summary. You can associate each output data set in a job with a logical
writer by using appropriate job control statements in your job stream or,
for VSE/POWER, by issuing an []ALTER console command. Your host system
must relate an output class to a logical writer. This occurs when your
host is configured, or for JES2 and JES3, when appropriate console
commands are issued.
Carriage Control Translation
The host system inserts SNA character strings into printer, console, and
punch data. SNA character strings contain carriage control and record
separation information.
Carriage control characters are written only to printer devices. For
punch devices, carriage control characters are not written. For console
output, the carriage control character %201 (print then single space) is
written with each record to the $STDLIST device of the console user. For
console output, multiple carriage control characters sent in sequence are
treated as a single carriage control character by NRJE. The carriage
control characters (except No operation) delimit records.
Table 4-2, below, describes the relationship between the control codes
and the operation performed on printer devices by each code.
NOTE HP line printers interpret channel skipping control codes
(%300-%313) differently from one another. You can redefine channel
skipping control codes using environment files containing VFCs.
See the SNA Link Services Reference Manual, the SNA NRJE Node
Manager's Guide, and the HP 2608S Line Printer Reference
(02608-90910).
Table 4-2. SNA and HP 3000 Printer Carriage Control Codes
-------------------------------------------------------------------------------------------
| |
| SNA Character String HP 3000 Control Code and Function |
| |
-------------------------------------------------------------------------------------------
| |
| Set Vertical Format (SVF) No operation. |
| ! 2B... Multiple 2B characters may be |
| sent in the string. |
| |
| Vertical Channel Skip (VCS) %3nn |
| ! 04... |
| nn=the number of 04 |
| characters received contiguously |
| (0<=nn<=13). Causes nn |
| vertical channel skips. |
| |
| New Line (NL) %201 |
| ! 15 Space one line. |
| |
| Required New Line (RNL) %201 |
| ! 06 Space one line. |
| |
| Carriage Return (CR) %53 |
| ! 0D No space; return to 1. |
| |
| Carriage Return/New Line %201 |
| (CR NL) Space one line. |
| ! 0D15 |
| |
-------------------------------------------------------------------------------------------
Table 4-2. SNA and HP 3000 Printer Carriage Control Codes (cont.)
-------------------------------------------------------------------------------------------
| |
| SNA Character String HP 3000 Control Code and Function |
| |
-------------------------------------------------------------------------------------------
| |
| Carriage Return/Form Feed %61 |
| (CR FF) Form feed. |
| ! 0D0C |
| |
| Carriage Return/Vertical %3nn |
| Channel Skip (CR VCS) |
| ! 0D04 nn=the number of 04 |
| characters received contiguously |
| (0<=nn<=13). Causes nn |
| vertical channel skips. |
| |
| Form Feed (FF) %61 |
| ! 0C Form feed. |
| |
| Backspace (BS) No operation. |
| ! 16 |
| |
| Inter-record separator (IRS) %201 |
| ! 1E Space one line. |
| |
| Transparent Data (TR) No code; indicates |
| ! 35 transparent data follows. |
| |
| All SNA character strings are All HP 3000 control codes |
| |
| hexadecimal numbers depicted are octal numbers depicted |
| by %abc%. |
| by !abcd. |
| |
-------------------------------------------------------------------------------------------
HP 268xx Laser Printer Output
Output from jobs you submit using NRJE can be printed on an HP 268xx
laser printer. You must configure your workstation to include the
logical device number (ldev) or logical device class (for example, PP) of
the HP 268xx in the NMMGR Writer Data screen. Output can be directed to
the laser printer by one of these methods:
* Creating file equations in your Lookup Table that specify the use of
the laser printer. In this case, you can specify an environment file
or you can omit that specification and use the default environment
file.
* JCL specifications that assign the output class of your data sets to
the same output class being handled by the remote writer that is your
laser printer. The link between the logical device (for example,
R11.PR3) that is configured to handle the given output data sets, and
the physical device (for example, the laser printer) is established
in the NMMGR Writer Data screen. Note that the relationship defined
by JCL specifications can be overridden by the SUBMIT command and
Lookup Table specifications as described above.
For example,
* The writername of your laser printer is R11.PR3, as configured
under NRJE and at the host.
* By the host configuration, R11.PR3 is assigned to handle output
class=C.
* In your JCL you assign class C to the output data sets. These data
sets are then directed by default to the laser printer.
Data sets can be printed using environment files you specify. You can
specify an environment file by any of these methods:
* In your JCL, by routing the output data sets to a special form that
corresponds to a Lookup Table entry specifying an environment file.
* In the NMMGR Writer Data screen configuration for a logical writer.
* In a file equation that you backreference directly as a SUBMIT
command output destination.
* In a Lookup Table file equation that you reference in a SUBMIT
command by its form name.
If you do not specify an environment file by one of these methods, the
default environment file configured for the HP 268xx is used. The
recommended procedure is to use the Lookup Table and map form names to
environment files that can be used when output is routed to the laser
printer. This process is described under "Output Management with the
Lookup Table" later in this chapter. In this case, FCB records returned
from the host are ignored.
It is possible to name an environment file in an FCB, although this
procedure is more difficult than the procedures listed above. If you do
not use the Lookup Table, the FCB information is used as an environment
file name that is appended with the accounting information HPENV.SYS. An
example of an MVS JCL DD card with an environment file is:
// DD....FCB=KIM
Environment file KIM.HPENV.SYS is used for this data set, unless the
FORCED option is Y for your workstation logical writer configuration.
When your output is received from the host system, NRJE uses the
environment file named in the FCB and residing in HPENV.SYS to produce
your output on an HP 268xx. The environment file is always copied to
your spool file.
Peripheral Device Information Record
Whether you are controlling the output received by NRJE by specifications
made in the SUBMIT command, through the use of the Lookup Table, or by
allowing the MPE Spooler to handle the output, much of the information
used by NRJE to perform job and output management is transferred in a
header data structure called the Peripheral Device Information Record
(PDIR). SNA NRJE can be configured to log PDIR information. The contents
of a PDIR are described in Table 4-3.
NOTE NRJE requires that the IBM host job entry subsystem (JES2, JES3, or
VSE/POWER) send a PDIR after selecting the output destination with
an FMH1 BDS (Begin Destination Selection) before sending job
output. NRJE will reject output not preceded by a PDIR.
Table 4-3. Peripheral Device Information Record Structure
------------------------------------------------------------------------------------------
| |
| Byte Contents and Meaning |
| |
| 0 The length of this record, including this byte. |
| |
| 1 Function Management Header (FMH) concatenation. An FMH is SNA-specific |
| information which may be present to perform the following functions: |
| |
| |
| * Select a destination and control the way data is handled there. |
| |
| * Change the characteristics of data or its destination. |
| |
| * Transmit status information about a destination, such as for a program or |
| a device. |
| |
| Bit 0 indicates the following: |
| |
| * 0 = No FMH follows. |
| |
| * 1 = Another FMH follows. |
| |
| Bits 1-7 are set to binary 0000010 to indicate an FMH-2 identifier. |
| |
| 2 Indicates that this record is a PDIR. Its value is !01. |
| |
| 3 A PDIR request identifier. |
| |
| Values are as follows: |
| |
| * 0 = Standard PDIR. |
| |
| * 1 = Job separator PDIR. |
| |
| * 2 = System message PDIR. |
| |
| All other values are undefined. |
| |
------------------------------------------------------------------------------------------
NOTE Bytes 4-99 are transmitted by the host in EBCDIC. NRJE translates
each of the fields in this range to ASCII. If NRJE is configured to
log the PDIRs, those fields are logged in ASCII.
Table 4-3. PDIR Structure (cont.)
------------------------------------------------------------------------------------------
| |
| 4-11 Data set creation date, in ASCII characters. The format is |
| |
| MM/DD/YY |
| |
| The default value is 00/00/00. |
| |
| 12-19 Data set creation time, in ASCII characters. The format is |
| |
| HH.MM.SS |
| |
| The default value is 00.00.00. |
| |
| 20-27 Form name as specified in the job JCL, in ASCII, left-justified, with |
| trailing blanks. JES2 typically uses STD , JES3 typically uses 1PRT |
| , and VSE/POWER uses (eight blank characters) to indicate standard form. |
| Special form names are transferred in this field. |
| |
| 28-35 Forms Control Buffer (FCB), in ASCII, left-justified, with trailing blanks. |
| This field is ignored by NRJE if your workstation is configured to route |
| output using the Lookup Table. If the Lookup Table is not in use, the FCB |
| is used to identify an HP 2680A environment file name. |
| |
| The default FCB value is all blank characters. |
| |
| 36-43 Printer train name to be mounted, in ASCII, left-justified, with trailing |
| blank characters. JES2 uses 0 as a default train. |
| |
| 44-51 Number of additional copies of the data set to be reproduced, in ASCII |
| characters, right-justified, with leading blank characters. The default |
| value is 0. |
| |
| 52-59 The volume of output, in ASCII characters, right-justified, with leading |
| blank characters. This specifies the approximate number of printer lines, |
| or the approximate number of cards in the data set. The default value is |
| all blank characters. |
| |
| The volume of output can be used for scheduling and estimating processing |
| time. |
| |
------------------------------------------------------------------------------------------
Table 4-3. PDIR Structure (cont.)
------------------------------------------------------------------------------------------
| |
| 60-67 Jobname field, in ASCII, left-justified, with trailing blank characters. A |
| jobname can be entered in a JCL JOB card image in columns 3-10, to identify |
| a batch job input stream submitted to a host system. The default value is |
| all blank characters. |
| |
| |
| Note If you are connected to a VSE host system, bytes 60-99 are |
| used as a Jobname field, left-justified, with trailing |
| blank characters. The following fields are defined for an |
| MVS host system. |
| |
| 68-75 Step name field, in ASCII, left-justified, with trailing blank characters. |
| A step name can be entered in a JCL EXEC card image in columns 3-10, to |
| identify an action in a batch job input stream submitted to a host system. |
| The default value is all blank characters. |
| |
| 76-83 Procedure step name field, in ASCII, left-justified, with trailing blank |
| characters. A procedure step is a unit of work associated with one |
| processing program and its related data, within a cataloged or in-stream |
| procedure, as in columns 3-10 in a JCL PROC statement. The default value is |
| all blank characters. |
| |
| 84-91 Data definition (DD) name field, in ASCII, left justified, with trailing |
| blank characters. A DD name field can be entered in a JCL DD card image in |
| columns 3-10, to identify the name of a data set within a job stream. The |
| default value is all blank characters. |
| |
| 92-99 Spin number, in ASCII, left-justified, with trailing blank characters. The |
| spin number is a unique identifier to distinguish among data sets with the |
| same jobname (bytes 60-67). The default value is all blank characters. |
| |
| |
| Note The spin number is used by JES3 to transfer the host job |
| number to the workstation. |
| |
------------------------------------------------------------------------------------------
Routing to the Standard Form
Standard form output refers to any output data sets for which you choose
the host default form and do not specify an alternate form, using job
control statements. SNA NRJE must be configured for the name of the
standard form in the NMMGR Workstation Data Page 2 screen. This
configured value must agree with the value configured on the host. The
standard form identifier is usually STD for JES2, 1PRT for JES3, and a
blank string for VSE/POWER.
Unless you have specified PR='formid' or PU='formid' options in your
SUBMIT command (not available if NRJE is connected to a VSE/POWER host
system), output routed to the standard form is not controlled by the
Lookup Table even if it is in use. For all host job entry subsystems,
when using the Lookup Table, if a data set is to be routed to the
standard or host default form, the output file characteristics defined in
the NMMGR Writer Data screen are used to open the destination file.
These characteristics include logical device number or name of a spooled
device and output priority. So, you do not have to put an entry for the
standard form in the table. Any entry in the Lookup Table under the
standard form name is ignored for standard form output.
PR= and PU= options to the SUBMIT command are used to control standard
forms output in printer and punch streams, respectively. If you have
used PR='formid' or PU='formid' options in a SUBMIT command, the standard
forms output is routed according to the file equation attributes for the
entry formid in the Lookup Table.
Data sets routed to forms other than the standard form are referred to as
special forms output.
Special Forms Processing
For SNA NRJE, a special form is any form name other than the default or
standard form name configured for your host system. Special forms are
supported for both print and punch output. NRJE processes special forms
through one of the following:
* The SUBMIT command FO= parameter specifications, or
* The Lookup Table, which maps the form name to an output destination.
If you are not using job management or output management, NRJE processes
special forms requests as follows:
1. Whenever special forms output destined for printers is received
from the host system and becomes active in the MPE Spooler, the HP
3000 console operator is prompted to mount the required special
form on the printer.
2. After the form has been mounted, MPE writes the output file to the
printer.
Remember, if you submit several jobs to a host with one SUBMIT command,
any alternate output destinations specified in the PRINT or PUNCH
parameters (for standard forms output) or FORMS parameters (for special
forms output) override JCL specifications. The SUBMIT command is
explained in chapter 3, "User Commands."
Specifying Multiple Copies
You can direct NRJE to print multiple copies of a data set when output is
routed to an NRJE print device. You select multiple copies by using the
COPIES parameter in your JCL. For example, for MVS JCL,
//ddname DD SYSOUT=C,COPIES=27
To select multiple copies of a single data set, you should specify a
unique class for each data set. To generate multiple data sets with
multiple copies, you should select a separate class for each data set or
generate the data sets in separate jobs. Also, each workstation writer
should be configured to receive a unique class of output.
NOTE The COPIES parameter is not supported on punch output.
Routing Output to Disc Files
When writing to a fixed-width disc file, MPE pads with ASCII blanks if
the destination file is ASCII and with binary zeros if the destination
file is binary. No padding is done for variable- or undefined-width
files.
For print output, the Carriage Control character is the first byte of
each record. No carriage control information is in punch output.
Routing Output to Tape Files
When writing to a tape device, variable record widths should be specified
in the file equation. Note that the default record width used by NRJE is
256 bytes. This value can be overridden in a file equation if desired.
For print output, include the cctl designation in the file equation.
Examples
file tape;dev=tape;rec=-132,,v,ascii;cctl (for print output)
or
file tape;dev=tape;rec=128,,v,binary;nocctl (for punch output)
then, issue this command:
infile ;FO=*tape
Use of the SUBMIT command is described in chapter 3, "User Commands," and
under "Job Management with the SUBMIT Command" later in this chapter.
Alternately, similar file equation records could be referenced in the
output management Lookup Table. Use of the Lookup Table is described in
"Output Management with the Lookup Table" later in this chapter.