Software Reference Manual - NetEx
Software Reference Manual - NetEx
Software Reference Manual - NetEx
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
files in a batched run following this error. Generally VM or Z/OS will issue a message indicating the<br />
reason for the open failure.<br />
User Response: Correct the reason for the open failure. Transfer the failing files once again.<br />
BFX211S Cannot open output file ffffffff.<br />
Severity: 12 (Severe error)<br />
Module: BFXRRM in BFXTI, BFXTR.<br />
Explanation: The receiving BFX program was unable to open the output file whose DDNAIME is<br />
specified by “ffffffff”. Transfer of this particular file is aborted. BFX will attempt to transfer subsequent<br />
files in a batched run following this error. Generally VM or Z/OS will issue a message indicating<br />
the reason for the open failure.<br />
User Response: Correct the reason for the open failure. Transfer the failing files once again.<br />
BFX213S RECFM must be specified for file ffffffff.<br />
Severity: 12 (Severe error)<br />
Module: BFXRRM in BFXTI, BFXTR.<br />
Explanation: The output file already exists and is a VS or VBS file. However, the DD card does not<br />
specify the record format of the file. Therefore, BFX will not know that it is a spanned file and will<br />
not correctly open it for BSAM processing.<br />
User Response: Add DCB = (RECFM = VBS) to the DD statement for the file ffffffff<br />
BFX214S LRECL = X must be specified for file ffffffff.<br />
Severity: 12 (Severe error)<br />
Module: BFXSRM in BFXTI, BFXTR<br />
Explanation: The input file for the sending record module is “LRECL=X” format. However, the DD<br />
card does not specify the LRECL = X in the JCL. Module BFXSRM did not get the proper information<br />
before opening the file and hence fails this transfer.<br />
User Response: Add DCB=(LRECL=X) to the JCL before initiating the SEND function for the file.<br />
BFX215F Fatal I/O Error Sccc-rr; ffffffff Transfer Aborted; Records Received nnnnnnnn.<br />
Severity: 15 (Fatal error)<br />
Module: BFXRRM in BFXTI, BFXTR, BFXJS.<br />
Explanation: During the process of writing a file, a fatal I/O error occurred. The message displays<br />
the System code (ccc) and reason code (rr) from the operating system. The transfer of this file<br />
(“ffffffff”) is aborted. The number of records received (nnnnnnnn) is displayed. Subsequent files in a<br />
batched BFX execution will not be transferred.<br />
User Response: Analyze the System code in the message, fix the JCL or the file, and rerun the job.<br />
BFX220I Sending file ffffffff.<br />
Severity: 4 (Informational)<br />
Module: BFXSRM in BFXTI, BFXTR.<br />
Explanation: The sending BFX has successfully opened the input file and is ready to begin transfer<br />
of data. Transmission will begin as soon as this message is issued. The DDNAME or FILEDEF of<br />
the file is “ffffffff”.<br />
User Response: None<br />
BFX221I Receiving file ffffffff.<br />
Severity: 4 (Informational)<br />
Module: BFXRRM in BFXTI, BFXTR, BFXJS.<br />
Explanation: The receiving BFX has successfully opened the output file and is ready to receive file<br />
data. The DDNAME or FILEDEF of the file is “ffffffff”.<br />
User Response: None<br />
Page 104 Appendix C: BFX Error Messages MAN-REF-H211-05
Change language