HP-UX SNAplus2 RJE User's Guide

SNAplus2 RJE Components and Operation
Processing Output Data
Chapter 3 53
punch files), or EXCnnnn (for exchange device files).
For more information see “Usr Card Parameters” later
in this chapter.
The rjeusrpad program has an extra feature. It pads
punch records with blanks. (See “Punch Padding”.)
The above mentioned minor options (pdir_passthrough and
keep_failed_files) can be defined by editing the RJE style file.
Punch Padding
The punch_padding option offers several variations on how punchoutput
is padded.
punch_padding Option The preferred method for punch padding is to
specify the punch_padding option in the define_minor_options record
in the RJE style file. Specifying this option allows you to pad all punch
output without configuring an output program to do the padding.
Note that when punch_padding causes RJE to add blanks, these blanks
are either ASCII or EBCDIC, depending on whether translation is done.
This method of padding punch records does not depend on the addition of
new-line characters. If you do not desire new-line character insertion,
you must use the snaprjecust program to configure NL between
records off, or set add_punch_nl to NO in the style file.
NOTE If output is sent to rjeusrpad, new-line characters will be removed. Use
rjeusr with the punch_padding option to route output with insertion of
new lines.
rjeusrpad Program Another method for punch padding is to use the
rjeusrpad program. The rjeusrpad program pads punch output that is
logged as being received in TEXT mode (ASCII or EBCDIC). Check the
audit log to determine if your data was received as text or transparent.
While actual output data may be both text and transparent, if any record
is a transparent record (sent with a transparency character), it is logged
as TRANSP. In the case of data that is logged as TRANSP, punch records
will not be padded. (For other types of punch padding, see the next
section.)