Software Reference Manual - NetEx

More documents

Recommendations

Info

| SEND | | RECEIVE | | SUBMIT | | TO=destination host name, | | FROM=originating host name, | ID=bfx identifier name [BLOCK=size of data block to send over network] [BMODULE=module to send/receive blocks] [BPARM=string for block module] [BUFFERS=number of block buffers] [BUSYMAX=number of seconds to wait for offerer to be not busy or number of sessions to drop below the limit] [CONTRY=number of seconds between connect and/or offer attempts] [DISCMAX=number of seconds to wait for the remote program to be offered] [HOSTCHK] [INDD=ddname of input file] [JBLOCK=job submission buffer size] [JBMODULE=block module for job submission] [JBPARM=string for sending block mod on j.s.] [JCLDD=ddname of remote job input] [JID=offered name of bfxjs job] [JMODULE=module to submit remote job] [JPARM=string for job module] [JRMODULE=record module for job submission] [JRPARM=string for sending record mod on j.s.] [MAXRATE=maximum transmission rate for sending data] [MODE=| CHAR |] | BIT | [MSGLVL=severity of messages to be logged] [NOSUB] [NTXID=NETEX subsystem name] [,NTXID=(ntxidl,ntxid2 ... ntxid8)] [OUTDD=ddname of output file] [RMODULE=module to read/write file records] [RMTJOB=jobname of job on remote host] [RPARM=| string for record module |] | TRANSL | [TIMEOUT=time in seconds for bfxtr to start] [-] the line continuation character [ | CLOSE | ] | NOCLOSE | [ | TIME | ] | NOTIME | [ | UPPER | ] | UPLOW | Figure 7. BFX Control Statements Control Statements SEND This statement (abbreviated S) indicates that the file transfer will be from the local host to the remote host. A SEND statement implies that the FILEIN or INDD specified DDNAME will be used for input file I/O. Page 14 JCL and Control Parameters for BFX MAN-REF-H211-05
RECEIVE SUBMIT For any given file transfer, a SEND statement on one end must match a RECEIVE statement on the other end. This statement (abbreviated R) indicates that the file transfer will be from the remote host to the local host. A RECEIVE statement implies that the FILEOUT or OUTDD specified DDNAME will be used for output file I/O. For any given file transfer, a RECEIVE statement on one end must match a SEND statement on the other end. If both sides specify either SEND or RECEIVE, an error occurs. This statement (abbreviated U) indicates that a remote job is to be submitted for execution on the responding host. The remote job is included in the BFXTI execution statements where the BFXTR job is otherwise included. When the SUBMIT statement is specified, the BFXTI program does not wait for the other host to connect back, but simply submits the job to BFXJS and terminates. Control Statement Parameters The SEND, RECEIVE, and SUBMIT statements use the following parameters (shown in Figure 7 on page 14). Defaults for many of these parameters are defined in the BFXDEF#xxxxx definitions in "Installing BFX" on page 29.. ID This required parameter (not required with the SUBMIT statement) specifies a unique identifier for the program being OFFERed by the initiating procedure. The ID BFX application name specified by the ID parameter may be any uppercase alphanumeric string 1 to 8 characters in length. Only one BFX program with this ID should be present in the initiating CPU. Users are strongly encouraged to use the jobname of the “remote” job as the ID in both the BFXTI and BFXTR programs. The ID parameters for the BFXTI and BFXTR parameters must agree for file transfer to take place. This parameter is required on the first SEND/RECEIVE card in both the procedures using the BFXTI and BFXTR programs. BLOCK This optional parameter (abbreviated B) specifies the size of the buffers of data to be sent through NETEX to the other host. The size in BLOCK must be at least large enough to accommodate the largest logical record to be sent from the file. If specified, it should be included on both the BFXTI and BFXTR execution parameters; if the values are not equal (or one is allowed to default) then the smaller of the two sizes implicitly or explicitly specified will be used. This parameter can be specified as nnK (for example, B=60K). The largest BLOCK allowed is 65,535 bytes. BMODULE If this parameter is not supplied, an installation-defined default is used. This optional parameter (abbreviated BM) specifies the name of the user module (the block module) that provides or accepts buffers of information sent through the IP network via <strong>NetEx</strong>/IP. In order to be accessed, the block module must have been previously link edited into the BFX program. Certain user-written block modules may not use record modules to read file information. In that case, the RMODULE and RPARM parameters will be ignored. MAN-REF-H211-05 JCL and Control Parameters for BFX Page 15
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: EXEC PGM=BFXTR This statement invok
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 and 104:
Receiving Block Module (RBM) This m
Page 105 and 106:
BFX Standard Job Transmission Modul
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

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

Delete template?

Save as template?