Note on usage
User group: FT administrator
Functional description
You use the TSO procedure FJGEN to set up a new openFT instance or to modify the parameter settings of existing instances. The FJGEN command can only be issued in TSO command mode:
EXEC <FT-basic-procedure-library>(FJGEN)
where <FT-basic-procedure-library> must be replaced by the CLIST present in the FJGEN command (generally OPENFT.CLIST under the openFT installation ID).
FJGEN starts a dialog that requests the installation parameters for the openFT instance. Filenames must be entered with the user ID but without single quotes.
FJGEN uses the installation parameters to create installation-specific CLISTs and the JCL for an installation-specific batch job (see below). These procedures are required for the administration of openFT. FJGEN stores them in the FT procedure library (CLIST library):
<openft qualifier>.<inst>.CLIST
The first two name parts here are replaced by OPENFT QUALIFIER and INSTANCE NAME.
FJGEN can also be used without an operand to modify the installation parameters; the procedures mentioned are then regenerated. The changes take effect the next time the installation-specific batch job is started with FJINIT.
The batch job and the FJINIT command are located in the CLIST generated by FJGEN: <openft qualifier>.<inst>.CLIST.
Even if openFT is running as a started task, the installation parameters are modified with FJGEN. The FT administrator must make the necessary changes in the start procedure himself/herself; see section “openFT as a job or started task”. In the case of parameters that are queried by FJGEN but are not required for the started task, the best solution is to enter an "x" in FJGEN.
Note
You can also store some of the installation parameters in the PARM member of the FT parameter library and pass them to openFT; specifications of this kind overwrite the specifications made for FJGEN. Further information is given in the section “Setting up the FT parameter library”.
Example: Set installation parameters (FJGEN without an operand)
fjgen ***** FJGEN/V121A00 INSTALLATION PROCEDURE openFT V12.1C00 ***** ENTER INSTANCE NAME : (DEFAULT: STD) ENTER FT-LOADLIB : USERA.openft.load ENTER FT-NCLOADLIB : USERA.openft.NCLOAD ENTER VOLUME/UNIT : vsn123/sysda ENTER openFT USER ID : openft ENTER openFT USER ACCOUNT : (a123,b123) ENTER openFT USER PASSWORD: openft ENTER OPENFT QUALIFIER : openftqu ENTER FT-ID : ftid1 ENTER FT-PASSWORD : affe ENTER RUNMODE : S(TANDARD)/A(UTOMATIC) ENTER FT-PARMLIB : openftqu.std.parm ENTER CMDPORT : 1100 ENTER HOST NAME : ENTER HSM-MCDS NAME : FJGENPAR CREATED FJINIT CREATED FJBATCH CREATED FJVERS CREATED (FUNCTION: GET VERSION OF LOADMODULS) ****** FJGEN END ****** READY
The various items of information requested or displayed have the following meaning:
INSTANCE NAME
The instance name is used to administer the openFT instance. It may be up to 5 characters in length. If this entry is omitted then the instance name STD is set.
The names of instances that are to be switched within a computer cluster must be unique within the cluster.
The instance name identifies the components that belong to an openFT instance (data sets) and is used to address these internally (see also section “Setting up openFT instances”). However, it should not be confused with the instance identifier (this is defined for the purposes of address information with the FTMODOPT command).
FT-PROCLIB
Name of the FT procedure library (CLIST library). This is only displayed with FJGEN ’INFO’ or FJGENPAR (see FJGENPAR - Output installation parameters).
If it does not already exist, this PO file is created automatically when FJGEN is called. FJGEN stores the command procedures for the openFT instance in this library. It has the fixed name <openft qualifier>.<inst>.CLIST
The first two name parts here are replaced by OPENFT QUALIFIER and the instance name.
FT-LOADLIB
Name of the FT load module library. This PO or PDSE data set must contain the following load modules: OPENFT, OPENFTSL and OPFTSUBL. The name of the library must be entered including its user ID but without single quotes.
FT-NCLOADLIB
Name of the FT load module library for openFT commands such as FTSHWPTN, NCOPY, etc. Among other things, this PO or PDSE file must contain the load modules FTATTP and FTDETP. The name of this library must be entered with the user ID but without quotes.
VOLUME/UNIT
VSN (volume serial number) and group name (unit) of the disk containing the request file, the partner list, the log file, the FTAC file, the trace files and the dump files, if any (see section “Internal openFT data sets”).
If the corresponding files are SMS managed, the specifications for VOLUME and UNIT may have no effect under certain circumstances. If the files are not SMS managed, an "SMS managed volume" must not be specified here.
You can specify both values; if you only want to specify one of the two values, it may be necessary to use a slash to distinguish which value you want to specify. If you want to specify neither VOLUME nor UNIT (i.e. only a slash), openFT assumes the UNIT name DASD. This UNIT name must therefore be defined in the system. (You can also define the volume for the request file, the partner list and the volume for the trace files and dump files via the corresponding parameters in the PARM member. Specifications in PARM overwrite the specifications made for FJGEN. Further information is provided in the section “Setting up the FT parameter library”. The assumption is made here that no volume specifications are made in PARM.)
Examples
VOLUME/UNIT | VOLUME | UNIT |
VSN123/SYSDA | VSN123 | SYSDA |
VSN123 | VSN123 | --- |
/SYSDA | --- | SYSDA |
/ | --- | DASD |
openFT USER ID
User ID under which the openFT job is to execute. Once an instance has been set up, this user ID is also authorized by default to administer FT and possibly also FTAC.
openFT USER ACCOUNT
Accounting information for the job under which openFT is to execute. If the accounting information contains more than one parameter it must be specified in parentheses (see IBM manual "MVS/ESA JES2 Commands").
Null input is permissible if no accounting information is required.
Maximum length of accounting information: 40 characters.
openFT USER PASSWORD
Password for the user ID under which openFT is to execute.
OPENFT QUALIFIER
Qualifier for the instance-specific files. The OPENFT QUALIFIER may be up to 17 characters in length and may contain maximal a period. Hence, It may consist solely of a "first level qualifier" or a "first level qualifier" and a "second level qualifier".
Please note the following:
The "second level qualifier" in the OPENFT QUALIFIER may consist of at most one character if ADM traps are to be output.
Trace file names can be shortened if the OPENFT QUALIFIER contains a "second level qualifier".
The "switch log files" function in the FTMODOPT command works only to a limited degree if the qualifier is longer than 11 characters. If a "second level qualifier" is defined (LOGFILE_2ND_Q parameter in the parameter library, PARM member), there are restrictions if the two qualifiers together are more than 23 characters in length.
FT-ID
FT identifier. This character string can consist of up to 5 alphanumeric characters and must be unique among all FT systems interconnected via an SNA network. If an SNA network is not used either for internal communication or for interconnections with other FT systems, then you can specify any value for FT-ID (preferably an 'x').
FT-PASSWORD
FT password. This password serves to protect the VTAM applications, the request file, the partner list and the trace files.
This parameter must be specified even if these resources are not password-protected.
RUNMODE
specifies the openFT start mode:
S or SS | the FJINIT command merely loads openFT. |
A or AA | the FJINIT command loads and immediately activates openFT (the |
**D | snap dumps can be generated for diagnostic purposes. |
"**" stands for "SS" or "AA" with the same meaning as above.
openFT can only be loaded in non-privileged mode for test purposes.
In non-privileged mode, openFT does not check the transfer admission or data access authorization. This means that:
Transfer requests are accepted and executed even if invalid specifications are made in the TRANSFER-ADMISSION or PROCESSING-ADMISSION.
The execution of other functions, e.g. follow-up processing or the printing of result lists, however, can be rejected by the system if invalid specifications are detected which openFT has not rejected.
openFT is loaded with the following specifications in non-privileged mode:
N or NS | openFT is loaded in non-privileged mode. |
NA | openFT is loaded in non-privileged mode and activated immediately. |
NSD | openFT is loaded in non-privileged mode. Diagnostic capabilities are |
NAD | As above. |
FT-PARMLIB
Name of the openFT parameter library. If no name is entered for this library in FJGEN then openFT uses the default value:<openft qualifier>.<inst>.PARM
The first two name parts are replaced by OPENFT QUALIFIER and the name of the instance.
If the parameter library does not exist at the time FJGEN is called, openFT creates it with the following content:
PARM member with the entries:
CMD_TRANS=TCP DSTYPEDEF=PS LIBTYPEDEF=PO OPENFT_SVC=211
The entry OPENFT_SVC is important if openFT is to perform command encryption using the started openFT subsystem, see section “Providing the OPFT subsystem”. If the openFT subsystem is not available or not started, the openFT batch job or the started task can only be started if this entry is deleted or invalidated.
FTADM with the entries
"OPENFT USER ID" from FJGENConsoleFTACADM with the entries
"OPENFT USER ID" from FJGENConsole
Details on the parameter library and its members can be found in the section “Setting up the FT parameter library” on section “Setting up the FT parameter library”).
CMDPORT
Port number of the command client, i.e. the port number of the current openFT instance for connecting the interactive tasks to openFT. CMDPORT is only relevant if the CMD TRANS parameter is not set to VTAM in the PARM member of the openFT parameter library. If no port number is specified here, openFT uses the openFT-specific default port number 1100.
HOST NAME
Host name for the current openFT instance. This information is required for addressing in TCP. The host should be specified directly as an IP address or as a hostname. If multiple openFT instances are to be able to run in parallel with TCP/IP then they must be assigned different IP addresses. Please note that you may only use IP addresses that are defined in your z/OS system’s address space. If you do not specify this value, openFT uses the first IP address that is defined in the z/OS system.
HSM-MCDS NAME
Help file for archiving and restoring (migrating) files. If nothing is specified, openFT sets the default value DFHSM.MCDS.
FJGEN uses the specified installation parameters, for example, to create the following JCL statements for a batch job for loading and starting the openFT load module (these statements are stored in the FJBATCH member of the FT procedure library):
//OPENFTF JOB (A123,B123), (1)
// CLASS=A,MSGCLASS=A,
// USER=OPENFT,PASSWORD=OPENFT, (2)
// TIME=1440,REGION=0M
//DLTMDMP EXEC PGM=IEFBR14 (7a)
//DELFILE DD DSN=OPENFTQU.STD.SYSUDUMP.PREV,
// DISP=(MOD,DELETE,DELETE),
// SPACE=(CYL,(20,5)),
// DCB=(DSORG=PS)
//RENAME EXEC PGM=IDCAMS (9)
//SYSPRINT DD SYSOUT=*
//SYSTSIN DD *
//SYSIN DD *
//ALTER 'OPENFTQU.STD.SYSUDUMP' +
//NEWNAME('OPENFTQU.STD.SYSUDUMP.PREV')
//IF LASTCC = 8 THEN SET MAXCC = 0
//OPENFT EXEC PGM=OPENFT,TIME=1440,
// PARMDD=FTPARMS
//* openFT V12.1C00 / FJBATCH V121C00 (3)
//FTPARMS DD DSNAME=OPENFTQU.STD.PARM(FTPARM),
// DISP=(SHR,KEEP)
//STEPLIB DD DSNAME=OPENFTQU.OPENFT.LOAD, (4)
// DISP=(SHR,KEEP)
//OPENFTS DD DSNAME=OPENFTQU.OPENFT.NCLOAD, (4a)
// DISP=(SHR,KEEP)
//OPENFT DD DSNAME=OPENFTQU.STD.CONN, (8)
// DISP=(SHR,KEEP)
//OPFTATT DD DSNAME=OPENFTQU.STD.OPFTATT,
// DISP=(SHR,KEEP)
//*DDUADS DD DSNAME=SYS1.UADS, (5)
//* DISP=(SHR,KEEP)
//OPFTHSM DD DSNAME=OPENFTQU.STD.COLLECT.DATA,
// DISP=(SHR,KEEP)
//MCDS DD DSNAME=DFHSM.MCDS,DISP=SHR
//SYSIN DD DUMMY
//SYSOUT DD DUMMY
//IEBCOUT DD DUMMY (6)
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD DSN=OPENFTQU.STD.SYSUDUMP, (7)
// SPACE=(CYL,(20,5)),DISP=(,CATLG),
// DCB=(DSORG=PS)
//*******************************************************************/
//* */
//* FJBATCH V12.1C00 - 15.10.2020 */
//* (C) 2020 FUJITSU TECHNOLOGY SOLUTIONS GMBH */
//* ALL RIGHTS RESERVED */
//* */
//*******************************************************************/
//
Explanation:
(1) | Jobname = openFT USER ID with appended F "accounting information" as specified |
(2) | openFT USER ID and openFT USER PASSWORD |
(3) | This DD statement refers to the start parameters, the values of which are specified in The start parameters are ignored if you specify the corresponding parameters in |
(4) | FT-LOADLIB |
(4a) | FT-NCLOADLIB |
(5) | This DD statement is created as comment if the SYS1.UADS file exists on your
If user IDs are to be checked using SYS1.UADS, this DD statement must be activated
|
(6) | openFT requires this DD statement in order to call the IBM utility IEBCOPY for |
(7) | DD statement for the generation of a machine-readable dump in the case of system |
(7a) | Statements for deleting the dump before the next openFT run. |
(8) | The instance-specific connection file |
(9) | With this statement you save the SYSUDUMP file when the batch job is restarted by |
You can adapt the JCL statements created by FJGEN to the requirements of your own system. Modifications which affect the function of openFT are described in the section“openFT as a job or started task”.