Software Reference Manual - NetEx

BFX090S Connecting host (hhhhhhhh) not equal to HOST parm.
Severity: 15 (Terminal error)
Module: BFXCON in BFXTI
Explanation: With HOSTCHK specified as YES, after a CONNECT arrived from BFXTR, the hostname
it is trying to connect to does not match the HOST specified on the ‘SEND TO hostname’ or
‘RECEIVE FROM hostname’ BFXTI statements. The connection is rejected.
User Response: Determine the cause of the error. If dissimilar NCTs are used on both sides of the
connection, or group host names are used, or a local loopback hostname (NCTLCLxx) is used,
HOSTCHK will not work in any of these configurations. If that is the case, specify
‘HOSTCHK=NO’ and rerun the job. If none of these conditions are true, then look for a configuration
or procedural error when running these jobs.
BFX101I File ffffffff done; nnnn records sent.
Severity: 6 (Informational)
Module: BFXSRM in BFXTI, BFXTR.
Explanation: The BFX default standard sending record module has detected normal end of file on
the input file specified by DDNAME “ffffffff”. The total number of QSAM logical records sent for
this particular file is “nnnn”. At the time the message was issued, the last record of the file will already
have been sent to the receiving BFX.
User Response: None.
BFX102S File ffffffff Permanent I/O error -- < SYNAD info>.
Severity: 12 (Severe error)
Module: BFXSRM in BFXTI, BFXTR. BFXRRM in BFXTI, BFXTR, BFXJS.
Explanation: The QSAM access method reported a permanent I/O error reading or writing a file during
transfer of the job or transfer of the file. The DDNAME of the file is indicated by “ffffffff”. The
SYNAD information associated with the error follows the text of the message. Transfer of this file is
aborted. If batched transfer of files is being performed, BFX will attempt to transfer the rest of the
specified files.
User Response: Determine the cause of the I/O error. If the error can be corrected, rerun the BFX
jobs.
BFX103S Cannot find record module mmmmmmmm.
Severity: 12 (Severe error)
Module: BFXSBM in BFXTI, BFXTR. BFXRBM in BFXTI, BFXTR, BFXJS.
Explanation: The record module specified by the RMODULE= parameter was not installed in this
copy of the BFX program. Transfer of this file is aborted; if batched transfer of files is being performed,
BFX will attempt to transfer the rest of the specified files.
User Response: This can be caused because the module does not exist, or if the module does exist
but was generated as being the wrong type.
BFX104S Record module “mmmmmmmm” language unsupported.
Severity: 12 (Severe error)
Module: BFXSBM in BFXTI, BFXTR. BFXRBM in BFXTI, BFXTR, BFXJS.
Explanation: The module specified by the RMODULE= operand was found in the module table, but
it is written in a source language that is not currently supported by BFX.
User Response: This is principally a diagnostic message for incorrect module table generation during
BFX installation. If the error is genuine, then the module needs to be rewritten.
Page 98 Appendix C: BFX Error Messages MAN-REF-H211-05