Software Reference Manual - NetEx

BFXJSTAT PROC SYSCL=A
//*
//* NOTE: BFXJSTAT must reside in an Authorized Library
//*
//* The STEPLIB library will be modified to match
//* what was specified during installation.
//*
//* Or, modify the JCL statements below to meet
//* your installation requirements.
//*
//BFXJSTAT EXEC PGM=BFXJSTAT,
// TIME=1440,
// PARM='0,$$$$'
//*
//STEPLIB DD DSN=BFX.AUTH.BFXLOAD,DISP=SHR
//*
//SYSUDUMP DD SYSOUT=&SYSCL
Figure 13. Sample BFXJSTAT JCL
Note: Two parameters are allowed to be passed in the form PARM =’timeout,ssn’. Not specifying the subsystem
name or specifying “$$$$” will allow the default to be selected by NETEX. The default
TIMEOUT value is zero.
The remote job status function may then be started by specifying START BFXSTAT from the operator’s console.
In order to use the remote job status function, the remote job status function must be started on the remote
host (where BFXTR will execute) and the RMTJOB parameter must be specified as part of the
SEND/RECEIVE command issued in the BFXTI job. See "Job Status Function Request Component
(BFXJSTAT)” on page 23 for an explanation of the BFXJSTAT function. BFXJSTAT can be stopped only
by an operator cancel or a NETEX “HALT SREF” command.
Step 9: (Optional) Establish BFX Catalogued Procedures
BFX is not distributed with any catalogued procedures to use BFX services. Generally, installations will either
want to invoke BFX directly, or they will want to write easy to use procedures to perform very specific
end user functions (such as transferring a specific type of file to a specific other host in the network).
Step 10: (Optional) Customize BFX
BFX can be immediately put to use by continuing with the installation. In addition, there is a generation facility
that allows user-written block and record modules to be added by relinking the BFX programs.
The following paragraphs describe the BFXMOD macro used with this step. If no customization is required,
the installation is complete.
MAN-REF-H211-05 Installing BFX Page 55