Software Reference Manual - NetEx

formation that is binary in nature, such as binary integers, floating point numbers, packed decimal
numbers, or others.
If the file being transferred is going to another IBM processor, then MODE=CHAR or MODE=BIT
will usually result in exactly the same file being written on the receiving host. If the destination processor
is not an IBM host, however, the processing is considerably different. If MODE=CHAR was
specified, the data text will be converted to the character set of the receiving system when received.
Also the logical records of character information will be converted to the corresponding logical record
structure of the non-IBM host. If MODE=BIT is specified, then the exact pattern of bits in the
logical record will be sent to the other host and stored as a binary logical record. This record would
presumably be converted to a useful form at some later time.
Both sides must specify MODE=BIT or MODE=CHAR. If the two specifications are inconsistent, an
error will occur.
If this parameter is not supplied, an installation-defined default is used (see “Installation” on page 37).
MSGLVL
This optional parameter (abbreviated MS) specifies the type of messages that the user wants to see in
the SYSPRINT log file. The parameter must be specified as a decimal number in the range of 0-15.
The meaning of the various message levels is shown below:
0-3 This will generate messages that are meant for diagnostic purposes. These messages will
trace the flow of events in BFX in detail, and are intended only for use in diagnosing problems
with BFX, NETEX, or newly written user modules.
4-7 This will generate messages indicating the status of job submission, starting of the remote
BFXTR job if applicable, and statistics on the file transferred.
8-11 If transfer of the file is normal, this will generate only the transfer complete message. If an
error is encountered that causes the transfer to fail, then the error messages will be logged.
12-15 Only errors that cause the file transfer process to be aborted will be printed.
If this parameter is not supplied, an installation-defined default is used.
NOSUB
This optional parameter (abbreviated NS) specifies that the BFXTI job does not contain a BFXTR job
for submission on the remote host. (NOSUB selects manual job submission as described in the introduction.)
If NOSUB is specified, the user on the local host and the user on the remote host must
manually submit the BFXTI and BFXTR jobs on the two hosts. The users must coordinate the submitting
of the jobs so that the BFXTI job is started just before the BFXTR job.
NTXID
OUTDD
This optional parameter specifies a list of alternate NETEX subsystem names to use. The list can be
from one to eight names in parentheses. Specifying “$$$$” for the subsystem name, or not specifying
this parameter, results in the default NETEX subsystem name to be used (normally NETX).
This optional parameter (abbreviated O) specifies an alternate DDNAME for the FILEOUT DD statement.
If this parameter is not supplied, an installation-defined default is used.
MAN-REF-H211-05 JCL and Control Parameters for BFX Page 19