08.11.2014 Views

Software Reference Manual - NetEx

Software Reference Manual - NetEx

Software Reference Manual - NetEx

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

BFX Send File Control (SND)<br />

This module receives control from the TIC, TRC, or JSC main modules when a file is to be transferred. The<br />

parameters to be used for the transfer are specified in the TROL that was built by the PRM module or internally<br />

generated as is the case when called by the default JMODULE (SUB). Its flow of control is as follows:<br />

1. The sending block module is called for the first time. On a first time call, the block module will call the<br />

record module to open the file for input and determine the maximum record size. This initialization logic<br />

is illustrated in Figure 25 on page 85.<br />

2. On return from the block module, RCV adjusts the BLOCK= value upwards if necessary. Based on the<br />

calling main program (which is specified in the TROL) it calls CON (BFX session offer or BFX session<br />

connect) with the TROL as the passed parameter. These modules will allow the connection to complete<br />

and complete the buffer size, least common multiple, minimum byte count, and file mode negotiations as<br />

detailed in the BFX General Design Specification.<br />

3. Upon completion of connection negotiation, SND allocates the requested number of buffers and begins<br />

the transfer process. It uses a multiple buffering technique to overlap NETEX processing of the incoming<br />

record with the file writes performed by the block module. Figure 26 on page 86 below shows the normal<br />

flow of data transfer.<br />

4. Whenever the block module is called to provide a block to be sent to NETEX, the block module may return<br />

with a message. The message will be sent to the RCV control module in the other application, and<br />

its contents will be placed on the SYSPRINT log files of both applications. If the message indicates a<br />

normal or abnormal end of transfer, SND will send the message and wait for a disconnect indication from<br />

the other BFX to indicate acknowledgement of the ending indication.<br />

5. If an abnormal end indication is received from the receiving remote BFX, SND will call the block and<br />

record modules with an error indication. In that case, the block and record modules are to close the file<br />

and return without any additional data. Upon return from the block module, SND will free the buffers allocated<br />

in step 2 and will return to the module that called SND.<br />

6. If the called block module returns an informational message, it will be forwarded to the opposite RCV<br />

module for logging. In addition, the message will be recorded locally on the SYSPRINT file. If an error<br />

or end of transfer message is returned from the record module, SND will forward the message and wait<br />

for a disconnect indication from the other side to acknowledge end of transfer.<br />

Page 84 Appendix B: BFX Internal Summary MAN-REF-H211-05

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!