Software Reference Manual - NetEx

More documents

Recommendations

Info

4. The record module may return an informational message, an abnormal end message, or an end of information message. If the message indicates an end of transfer, the record module will have already closed the file. Forward the message to the control module and free any storage if an end message was passed up. 5. The control module may call with an abnormal end indication based on a loss of communications or an abort issued by the receiving BFX module. In that case, call the record module with an abnormal end indication. On return, the file should have been closed. Free any allocated storage areas and return to the control module for the last time. Receiving Record Module (RRM) The receiving record module is actually responsible for the QSAM I/O that will put the logical records in the file designated by the user. It opens the file, determines record format and logical record formatting requirements, and issues PUT macros to write the data when it is delivered by the block module. If I/O errors occur, it is responsible for analyzing the errors, determining if the error is fatal or not, and returning a comprehensible error message to the block module in the event of an I/O error. The BFX default receiving record module operates as follows: 1. When the receiving record module receives control for the first time, it opens the file whose DDNAME is passed to it from the block module. Using the LRECL parameter produced as a result of the OPEN, it returns the maximum logical record length to the block module. If the specified BLOCK= parameter is not large enough to accommodate the largest logical record, then the RCV module will adjust the value of BLOCK upwards. If the open for the file does not succeed, then the record module will return an open failure message to the block module for logging. 2. Subsequent calls to the record module will provide the address and length of the logical record. The record module will PUT (WRITE for VBS format) this record to the file, adding V-format header information if needed. If record type conversion is called for, then it will truncate or pad the record before it is written. 3. If the record module is called with an error or EOF indication, then the record module will close the file and return to the block module. Sending Record Module (SRM) The sending record module is responsible for reading logical records from the file to be sent over the network. On the first call, it will open the file for input. Subsequently, it will provide a logical record every time it is called. When end of file is reached or a permanent error is detected in reading the file, then it will close the file, generate a termination message, and return. SRM flow of control proceeds as follows: 1. When the sending record module receives control for the first time, it opens the file whose DDNAME is passed to it from the block module. Using the LRECL parameter produced as a result of the OPEN, it returns the maximum logical record length to the block module. If the specified BLOCK= parameter is not large enough to accommodate the largest logical record, then the SND module will adjust the value of BLOCK upwards. If the open for the file does not succeed, then the record module will return an open failure message to the block module for logging. 2. Subsequent calls to the record module will provide the address and length in which the logical record is to be placed. The record module will GET the record into this block module provided area. 3. If the record module is called with an error or EOF indication, then the record module will close the file and return to the block module. Page 88 Appendix B: BFX Internal Summary MAN-REF-H211-05
BFX Standard Job Transmission Module (SUB) This module is the standard Job Transmission Module (JMODULE). Its logic is as follows: 1. Using the information in the TROL data structure passed to it from the TRC or TIC control module, it constructs another TROL that will be used to do a character file transfer from the RMTJOB DDNAME to the BFXJS ID that is to receive the job on the remote host. 2. Using this constructed TROL, it calls the send control module to send the RMTJOB DDNAME as a remote file. On return from the send control module, the job will have been submitted to the remote host. MAN-REF-H211-05 Appendix B: BFX Internal Summary Page 89
Page 1 and 2:
H211 Bulk File Transfer (BFX) Utili
Page 3 and 4:
Preface This manual describes the u
Page 5 and 6:
Reference Material The following ma
Page 7 and 8:
Notice to the Reader The material c
Page 9 and 10:
Glossary asynchronous: A class of d
Page 11 and 12:
Contents Revision Record ..........
Page 13 and 14:
Appendix E. BFX Condition Codes....
Page 15 and 16:
Tables Table 1. Block module exit p
Page 17 and 18:
Introduction The Bulk File Transfer
Page 19 and 20:
Using BFX To use BFX, the programme
Page 21 and 22:
Notice that a SEND in one job must
Page 23 and 24:
The BFXTR and BFXTI programs contin
Page 25 and 26:
BFXRVM opens the VSAM file and dete
Page 27 and 28:
JCL and Control Parameters for BFX
Page 29 and 30:
EXEC PGM=BFXTR This statement invok
Page 31 and 32:
RECEIVE SUBMIT For any given file t
Page 33 and 34:
HOSTCHK INDD This optional paramete
Page 35 and 36:
formation that is binary in nature,
Page 37 and 38:
connect to the BFXJSTAT function on
Page 39 and 40:
Job Status Function Request Compone
Page 41 and 42:
Applications The following examples
Page 43 and 44:
IBM z/OS to Linux The example in Fi
Page 45 and 46:
Installing BFX This section describ
Page 47 and 48:
Installation Process This section d
Page 49 and 50:
Tailor the installation job in BFXI
Page 51 and 52:
HLQ Default value: BFX.DIST Allowed
Page 53 and 54: LOADLIB Default value: hlq.BFXLOAD
Page 55 and 56: BFXDEF#CLOSE Example: Default value
Page 57 and 58: This parameter (abbreviated JBP) sp
Page 59 and 60: This is a list of up to eight alter
Page 61 and 62: Example: BFXDEF#BUFFERS(‘’)
Page 63 and 64: BFXJSD#JRPARM Default value: Allowe
Page 65 and 66: BFXJSD#UPPER Default value: Allowed
Page 67 and 68: SAMPACCT Default value: ‘’(none
Page 69 and 70: The following statements appear in
Page 71 and 72: BFXJSTAT PROC SYSCL=A //* //* NOTE:
Page 73 and 74: ASM,FORT initep These parameters ar
Page 75 and 76: Appendix A: User Modules BFX provid
Page 77 and 78: MSG MSGLEN MSGLEV call to the recor
Page 79 and 80: -----------------------------------
Page 81 and 82: BUFLEN BUFLEV MSGLEN MSGLEV Signifi
Page 83 and 84: C BUMP RECORD COUNTER C 300 NREC =
Page 85 and 86: MVC RMSGLEN,=F’22’ Message is 2
Page 87 and 88: RDDNAME DS CL8 DDNAME of file RRPAR
Page 89 and 90: LCM MODE DDNAME BBPARM RMOD BRPARM
Page 91 and 92: ===================================
Page 93 and 94: Appendix B. BFX Internal Summary Th
Page 95 and 96: Block Diagram Many modules are used
Page 97 and 98: BFXJSC BFXJS Control BFXPRM Analyze
Page 99 and 100: CONTROL BLOCK RECORD MODULE MODULE
Page 101 and 102: CONTROL BLOCK RECORD MODULE MODULE
Page 103: Receiving Block Module (RBM) This m
Page 107 and 108: Appendix C. BFX Error Messages BFX
Page 109 and 110: BFX010I TO = or FROM = host name om
Page 111 and 112: BFX026F Remote host NETEX not prese
Page 113 and 114: BFX051F BFX Abend Unnn in Module $$
Page 115 and 116: BFX105S Cannot find block module mm
Page 117 and 118: BFX118S Sending block module abort
Page 119 and 120: User Response: If the truncation wa
Page 121 and 122: BFX300I Offering ssssssss; Block ou
Page 123 and 124: gotiated, which contains a value ot
Page 125 and 126: Appendix D. H211 User Abend Codes T
Page 127 and 128: Appendix E. BFX Condition Codes Aft
Page 129 and 130: Index A ASCII......................
show all

Software Reference Manual - NetEx

Create successful ePaper yourself

Delete template?

Save as template?