FABHFSU JCL requirements

FABHFSU runs as an HSSR application program and, therefore, must meet the requirements for the basic JCL (FABHX034 JCL). In addition, FABHFSU JCL requires other DD statements.

Prerequisite: See Basic JCL requirements for the basic (FABHX034) JCL requirements.

The following table summarizes additional JCL requirements for FABHFSU.

Table 1. FABHFSU DD statements
DDNAME	Use	Format	Need
CARDIN	Input	LRECL=80	Optional
PRNTOUT	Output	LRECL=133	Required
`ddname1`	Output	RECFM=VB	Required

EXEC

This required statement invokes either the FABHULU or FABHDLI procedure (see Preparing the basic JCL). Before using either procedure, modify the JCL to include the correct names of the PSBLIB, DBDLIB. Use one of the following formats:

 //  EXEC FABHULU,MBR=FABHFSU,DBD=dbdname
 //  EXEC FABHDLI,MBR=FABHFSU,PSB=psbname

Restriction: FABHFSU cannot be run in the DBB region.

CARDIN DD

This required DD statement defines the input data set that contains the control statements for FABHFSU. For details, see FABHFSU CARDIN input data set.

PRNTOUT DD

This required statement defines the output data set to which FABHFSU writes error messages and segment statistics. For details, see FABHFSU output: PRNTOUT output data set. The data set can be defined as:

 //PRNTOUT DD SYSOUT=A

ddname1 DD

This DD statement specifies the primary output data set that contains the unloaded database. One DD statement is required for each PSB control statement (in the CARDIN data set) that specifies an output format other than NO. (ddname1 must be the name specified in the ddname1 field of the PSB control statement. See PSB control statement.) You can have up to three of those data sets.

The large format data set can be specified for those data sets if z/OS® Version 1 Release 7 or later and IMS Version 10 or later is used.

The data set can reside either on tape or on a direct-access device, or it can be specified as DUMMY.

For an HSAM output data set, specify the BLKSIZE on the DD statement. For the BLKSIZE of other output formats, see Unload output format supported by FABHFSU and the description of the PSB control statement.

You can specify the number of buffers in the FSUBUFNO= option in the default option table (FABHOPT). For details, see Site default options. The buffers are obtained above the 16-MB line.

If neither the BUFNO subparameter of the DCB parameter on the DD statement nor the FSUBUFNO= option is given, the number of buffers is determined automatically. The buffers are approximately 1 MB in total size and are above the 16-MB line.

Note: The LRECL values for ddname1 are determined as follows.

For VB and VN formats, the LRECL value prepared in the JCL DD statement is used when the value is specified either:

Explicitly by the LRECL subparameter of the DCB parameter
Implicitly, for example, by using a model data set or the DFSMS/MVS DATACLAS parameter

If the LRECL value is not specified either explicitly or implicitly, the default record size (block size minus 4) is used.

For UL format, the LRECL value prepared in the JCL DD statement is always ignored, and the default record size (block size minus 4) is used.

In addition to these DDs, the standard HSSRTRAC DD statement is required whenever HSSROPT options that produce trace and diagnostic data are specified. It is also required when the pointer bypass option is specified on a DBD control statement in the CARDIN data set (see DBD control statement). This specification causes the DIAGG option to be invoked automatically (see DIAGG control statement).