IBM Support

Updates to IMS Fast Path Solution Pack V1.3 IMS High Performance Fast Path Utilities User’s Guide

Product Documentation


Abstract

Updates that apply to IMS Fast Path Solution Pack V1.3 IMS High Performance Fast Path Utilities User’s Guide (SC19-4010-04).

Content

The most recent updates appear at the top of the list.


Update 5

Date of change: March 2019

Change description: Documentation changes by APAR PH08805. This APAR modifies the Online Area Extender (OAE) utility of FPO.  After this PTF is applied, IOVF expansion will not refer to ACBLIB when IOVF_ROOT=(number2,overflow2) or IOVF_UOW keyword is specified. 

Topics: Changes apply to multiple topics.

============

Topic: IMS Fast Path Online Tools > Extending a DEDB online with FPO > DD statements for OAE

ACBLIB DD has been updated as follows:

Table. OAE DD statements

(Table 134 in PDF)

DDNAME Use Format Required or optional
... ... ... ...
ACBLIB Input PDS and member
image-20180716101203-34Required if either of the following conditions is met:
  • Shadow expansion: Extend the IOVF portion without the ROOT=(aaaaa,bbbbb) keyword
  • Original expansion: IOVF_ROOT=ACBLIB is specifiedimage-20180716101203-35
... ... ... ...

ACBLIB DD

Identifies the ACBLIB and DEDB member to be used. This DD must also contain the name of the DBD member.

image-20180716101203-34This DD statement is required for extending the IOVF portion when either of the following conditions is met:
  • Shadow expansion: Extend the IOVF portion without the ROOT=(aaaaa,bbbbb) keyword
  • Original expansion: IOVF_ROOT=ACBLIB is specified

This DD statement is ignored when either of the following conditions is met:
  • SDEP expansion
  • IOVF expansion with one of the following keywords:
    • Shadow expansion: The ROOT=(aaaaa,bbbbb) keyword is specified
    • Original expansion: The IOVF_ROOT=(number2,overflow2) keyword or the IOVF_UOW keyword is specifiedimage-20180716101203-35
This DD statement must specify the ACBLIB library that contains the member of the present DEDB.

============

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > FPX messages

The following message has been removed:

image-20180716101203-34
FPX0294I   OAE replaced the ROOT= parameter value in DMAC (IMS storage) from (value1, value2) to (value3, value4).

Explanation: OAE replaced the ROOT= parameter value in DMAC with the indicated ROOT= parameter value.
System action: Processing continues.
User response: None. This message is informational.
image-20180716101203-35

Update 4
Date of change: February 2019

Change description: Documentation changes by APAR PH01862. This APAR enhances  FPB DEDB Pointer Checker, DEDB Unload, and DEDB Reload to support IMS managed ACB environment.

Topics: Changes apply to multiple topics.

============

Topic: Overview of IMS HP Fast Path Utilities > What is IMS HP Fast Path Utilities? > Support for IMS managed ACB environment

The following section has been added after "IMS Fast Path Advanced Tool":

image-20180716101203-34IMS Fast Path Basic Tools

The following functions of FPB support IMS managed ACB environment:

  • DEDB Pointer Checker
  • DEDB Unload and Reload

To use IMS managed ACBs instead of ACBs in ACB libraries, you must apply APAR PH01862.

For more information, see the following topics:

  • "IMS Tools Catalog Interface"
  • "IMSCATHLQ keyword"
  • "IMSCATACB_INPUT keyword"
  • "IMSCATACB_OUTPUT keyword"image-20180716101203-35
 
============
Topic: IMS Fast Path Basic Tools > Analyzing a DEDB offline with FPB >
Data and system flow of DEDB Pointer Checker


This topic has been updated as follows:

image-20180716101203-34The following figure shows the general data flow for the DEDB Pointer Checker utility. Input consists of the DEDB area, the SYSIN data set, and the location of ACB definitions.

ACB definitions are retrieved from the ACB library (ACBLIB DD) or from the libraries specified by IMSACBA and IMSACBB DD statements when MODSTAT and MODSTAT2 DD statements are specified. However, if the IMS catalog and the IMS management of ACBs are enabled, ACB definitions can be retrieved from the IMS directory. image-20180716101203-35

Output consists of the validation error messages, the analysis report, and other analysis reports.

Figure. Flow of DEDB Pointer Checker
(Figure 290 in PDF)

image-20180716101203-34

 
 
image-20180716101203-35
============
Topic: IMS Fast Path Basic Tools > Analyzing a DEDB offline with FPB > DD statements for DEDB Pointer Checker > FABADA1 JCL

This topic has been updated as follows:

Table. FABADA1 DD statements
(Table 82 in PDF)
DDNAME Use Format Required or optional
... ... ... ...
ACBLIB Input PDS image-20180716101203-34Required when IMSCATHLQ=*NOimage-20180716101203-35
... ... ... ...

JOBLIB/STEPLIB DD
When the DBRC=Y parameter of the EXEC statement is specified, the IMS load module library (IMSVS.SDFSRESL) must be concatenated with the DEDB Pointer Checker library on the JOBLIB or STEPLIB DD.
To dynamically allocate an area data set, the IMS library that contains DFSMDA members must be concatenated with the DEDB Pointer Checker library on JOBLIB or STEPLIB DD.
image-20180716101203-34If you specify the IMSCATHLQ= bsdshlq keyword, the IMS Tools Base library (SGLXLOAD) must be concatenated to JOBLIB or STEPLIB DD. image-20180716101203-35

ACBLIB DD
This statement defines the library that contains the DBD member that describes the database to be analyzed. For example:
//ACBLIB DD DSN=IMSVS.ACBLIB,DISP=SHR

image-20180716101203-34The location of ACB definitions must be specified with one of the following methods:
  • Specify the ACB library with the ACBLIB DD statement.
  • Specify the high level qualifier of the bootstrap data set of the IMS directory with the IMSCATHLQ=bsdshlq keyword. In this case, ACB definitions are obtained from the IMS directory instead of from the ACB library.
  • Specify the ACB library with IMSACBA and IMSACBB DD statements. MODSTAT and MODSTAT2 DD statements must also be specified.
If the IMSCATHLQ= bsdshlq keyword is specified, ACBLIB DD, IMSACBA, IMSACBB, MODSTAT, and MODSTAT2 DD statements are ignored. image-20180716101203-35

IMSACBA DD
Defines the library that contains the DMB for the database.
image-20180716101203-34If you do not specify the IMSCATHLQ= bsdshlq keyword or the ACBLIB DD statement, you must specify this DD statement together with the IMSACBB, MODSTAT, and MODSTAT2 DD statements. image-20180716101203-35

IMSACBB DD
Defines the library that contains the DMB for the database.
image-20180716101203-34If you do not specify the IMSCATHLQ= bsdshlq keyword or the ACBLIB DD statement, you must specify this DD statement together with the IMSACBA, MODSTAT, and MODSTAT2 DD statements. image-20180716101203-35

MODSTAT DD
Defines the MODSTAT data set.
image-20180716101203-34If you do not specify the IMSCATHLQ= bsdshlq keyword or the ACBLIB DD statement, you must specify this DD statement together with the IMSACBA, IMSACBB, and MODSTAT2 DD statements. image-20180716101203-35

MODSTAT2 DD
Defines the MODSTAT2 data set.
image-20180716101203-34If you do not specify the IMSCATHLQ= bsdshlq keyword or the ACBLIB DD statement, you must specify this DD statement together with the IMSACBA, IMSACBB, and MODSTAT DD statements. image-20180716101203-35

============
Topic: IMS Fast Path Basic Tools > Analyzing a DEDB offline with FPB > DD statements for DEDB Pointer Checker > FABADA4 JCL

This topic has been updated as follows:

Table. FABADA4 DD statements
(Table 89 in PDF)
DDNAME Use Format Required or optional
ACBLIB Input PDS image-20180716101203-34Required when IMSCATHLQ=*NOimage-20180716101203-35
... ... ... ...

ACBLIB DD
This statement defines the library that contains the DBD member that describes the database analyzed by FABADA1. For example:
//ACBLIB DD DSN=IMSVS.ACBLIB,DISP=SHR

image-20180716101203-34If the IMSCATHLQ= bsdshlq keyword is specified as a site default keyword (specifies to retrieve ACB definitions from the IMS directory instead of the ACB library), ACBLIB DD statement is ignored. image-20180716101203-35

============
Topic: IMS Fast Path Basic Tools > Analyzing a DEDB offline with FPB > Input for DEDB Pointer Checker > FABADA1 SYSIN DD data set

This topic has been updated as follows:

...

Format
This control-statement data set usually resides in the input stream. However, it can also be defined as a sequential data set or as a member of a partitioned data set. It must contain 80-byte fixed-length records. Block size, if coded, must be a multiple of 80.

image-20180716101203-34 This data set must contain one or two control records. They can be coded as shown in the following figure.
Control records can be coded as shown in the following figure. image-20180716101203-35

Record format
There is only one statement type in the SYSIN file. It contains the following keywords:
 
DBDNAME= dbdname
[AREA= areaname]
[TYPRUN={ RPT|PTRSCAN|PTRALL|FS|MODEL|DATA|DATACMP}]
[VSAM]
[SDEP]
[OVRD]

[STATS]
[STATS=YES| NO]
[TBLENTRY={ 10000| nnnnnnnn}]
[SPTFALL]

VSAM={YES| NO}
SDEP={YES| NO}
OVRD={YES| NO}
SPTFALL={YES| NO}

image-20180716101203-34IMSCATHLQ= { *NO| bsdshlq} image-20180716101203-35
image-20180716101203-34IMSCATACB_INPUT= { CURRENT|PENDING} image-20180716101203-35


image-20180716101203-34 IMSCATHLQ=
This optional keyword specifies to retrieve ACBs from the IMS directory (an extension of the IMS catalog) instead of from the ACB library.
  • 'bsdshlq' specifies to read ACBs from the IMS directory by using the IMS Tools Catalog Interface. bsdshlq specifies the high level qualifier of the bootstrap data set of the IMS directory. IMSCATHLQ=bsdshlq is effective when the IMS catalog and the IMS management of ACBs are enabled.
    If a TYPE=CATDSHLQ statement was used to create a DFSMDA member in your MDA library, you must specify the SYSDSHLQ parameter used in that DFSMDA member for the IMSCATHLQ keyword parameter.
  • '*NO' specifies to read ACBs from the ACB library. *NO is the default value.image-20180716101203-35
 

image-20180716101203-34 IMSCATACB_INPUT=
This optional keyword specifies whether to retrieve currently active ACB definitions or pending ACB definitions from the IMS directory. IMSCATACB_INPUT keyword is effective only when the IMSCATHLQ= bsdshlq option is specified.
  • 'CURRENT' specifies that currently active ACB members are retrieved from the IMS directory data sets. CURRENT is the default value.
  • 'PENDING' specifies that pending ACB members are retrieved from the staging data set.image-20180716101203-35
============
Topic: IMS Fast Path Basic Tools > Unloading a DEDB offline with FPB > Data and system flow of DEDB Unload

This topic has been updated as follows:

The unload processor (FABCUR1) is a z/OS batch program that controls and manages the unloading of one or more DEDB areas to QSAM data sets. It achieves significant performance improvements (that is, reduced elapsed time) by implementing a parallel processing environment and by reducing the number of EXCPs issued.
image-20180716101203-34If you enable the IMS catalog and the IMS management of ACBs, ACB definitions are retrieved from the IMS directory instead of from OLDACB and NEWACB libraries. image-20180716101203-35

The following figure shows the flow of the unlaod procedure.

Figure. Flow of Unload
(Figure 332 in PDF)


image-20180716101203-34

image-20180716101203-35
============
Topic: IMS Fast Path Basic Tools > Unloading a DEDB offline with FPB > DD statements for DEDB Unload

Table. FABCUR1 DD statements
(Table 106 in PDF)
DDNAME Use Format Required or optional
... ... ... ...
OLDACB Input PDS image-20180716101203-34Required when IMSCATHLQ=*NOimage-20180716101203-35
... ... ... ...

JOBLIB DD or STEPLIB DD
When DBRC=Y is specified on the EXEC statement, the IMS load module library (IMSVS.SDFSRESL) must be concatenated with the FPB DEDB Unload/Reload library on the JOBLIB or STEPLIB DD.
To allocate a DBRC RECON data set and/or a DBRC nonregistered area data set dynamically, the DFSMDA library data set must be concatenated.
To allocate an area data set dynamically when DBRC=N is specified, the DFSMDA library data set must be concatenated.
image-20180716101203-34If you specify the IMSCATHLQ= bsdshlq keyword, the IMS Tools Base library (SGLXLOAD) must be concatenated. image-20180716101203-35

OLDACB DD
This statement defines the library that contains the old DMB for the database.
image-20180716101203-34You must specify the library that contains ACB definitions either with an OLDACB DD statement or with the IMSCATHLQ= bsdshlq keyword. If IMSCATHLQ= bsdshlq is specified, ACB definitions are read from the IMS directory instead of the ACB library. image-20180716101203-35

NEWACB DD
This statement defines the library that contains the new DMB for the database. This DD statement is ignored if an area is being reorganized (that is, the keyword REORG is specified). If this DD statement is present, REORG is not assumed even if there are no DBD specification changes (that is, the randomizer is called for each root segment).
image-20180716101203-34If IMSCATHLQ= bsdshlq keyword is specified, NEWACB DD statement is ignored. If an ACB definition change is requested, the new DMB is retrieved from the IMS directory. image-20180716101203-35

============
Topic: IMS Fast Path Basic Tools > Unloading a DEDB offline with FPB > Input for DEDB Unload > Control statements

The following new control statements have been added after "SEGMCTL control statement":
  • IMSCATHLQ control statement
  • IMSCATACB_INPUT control statement
  • IMSCATACB_OUTPUT control statement

image-20180716101203-34 IMSCATHLQ control statement
The optional IMSCATHLQ statement specifies to retrieve ACBs from the IMS directory (an extension of the IMS catalog) instead of from the ACB library.

IMSCATHLQ= bsdshlq|*NO
 
The IMSCATHLQ control statement is composed of:

bsdshlq
Reads ACBs from the IMS directory by using the IMS Tools Catalog Interface. bsdshlq specifies the high level qualifier of the bootstrap data set of the IMS directory. IMSCATHLQ= bsdshlq is effective when the IMS catalog and the IMS management of ACBs are enabled.
If a TYPE=CATDSHLQ statement was used to create a DFSMDA member in your MDA library, you must specify the SYSDSHLQ parameter used in that DFSMDA member for the IMSCATHLQ keyword parameter.

*NO
Reads ACBs from the ACB library.  This is the default value. image-20180716101203-35

image-20180716101203-34 IMSCATACB_INPUT control statement
The optional IMSCATACB_INPUT statement specifies whether to retrieve currently active ACB definitions or pending ACB definitions from the IMS directory. IMSCATACB_INPUT keyword is effective only when the IMSCATHLQ= bsdshlq option is specified.

IMSCATACB_INPUT=CURRENT|PENDING

The IMSCATACB_INPUT control statement is composed of:

CURRENT
Currently active ACB members are retrieved from the IMS directory data sets. This is the default value.

PENDING
Pending ACB members are retrieved from the staging data set. image-20180716101203-35

image-20180716101203-34 IMSCATACB_OUTPUT control statement
The optional IMSCATACB_OUTPUT statement specifies whether to retrieve currently active ACB definitions or pending ACB definitions from the IMS directory. This keyword specifies the new ACB definition, which is used when an ACB definition change is requested. IMSCATACB_OUTPUT keyword is effective only when the IMSCATHLQ= bsdshlq is specified.

IMSCATACB_OUTPUT=CURRENT|PENDING

The IMSCATACB_OUTPUT control statement is composed of:

CURRENT
Currently active ACB members are retrieved from the IMS directory data sets.

PENDING
Pending ACB members are retrieved from the staging data set. image-20180716101203-35

============
Topic: IMS Fast Path Basic Tools > Unloading a DEDB offline with FPB > Examples for DEDB Unload > Example 5: Expanding a three-area database to five areas (generating three outputs)

The title of this topic has been changed as follows:
image-20180716101203-34Example 5: Expanding a three-area database to five areas (generating three outputs) when IMS management of ACBs is enabled image-20180716101203-35

The topic has been updated as follows:
...
The database is under the control of a "general" randomizer. Three output files are produced. (This unload example is the same as Example 4, except for the number of output files.)
image-20180716101203-34This unload example is similar to Example 4. The only differences are:
  • The number of output files
  • ACB definitions are retrieved from the IMS directoryimage-20180716101203-35
...
...
  1. ...
  2. The control statements stream is coded as follows: 
DBDNAME=TSSDBD5 RMODTYPE=G STATS
     AREACTL=ALL
     TASKCTL=(,7)
     FILECTL=1,(1,4)
     FILECTL=2,(2,5)
     FILECTL=3,3
     image-20180716101203-34IMSCATHLQ=IMSVS.CATALOG image-20180716101203-35
     image-20180716101203-34IMSCATACB_INPUT=CURRENT image-20180716101203-35
     image-20180716101203-34IMSCATACB_OUTPUT=PENDING image-20180716101203-35

============
Topic: IMS Fast Path Basic Tools > Reloading a DEDB offline with FPB > Data and system flow of DEDB Reload

This topic has been updated as follows:

The reload processor (FABCUR3) is a z/OS batch program that reloads one or more DEDB areas from the formatted QSAM data sets created by the unload processor. It achieves significant performance improvements (that is, elapsed time reduction) by reducing the number of EXCPs issued and eliminating the need to run the DEDB Initialization utility (DBFUMIN0). The only limitation on the number of concurrent reload jobs is the number of available initiators.
image-20180716101203-34ACB definitions are retrieved from the ACB library specified by the DURDBDFN DD statement or the ACBLIB DD statement. However, if the IMS catalog and the IMS management of ACBs are enabled, ACB definitions can be retrieved from the IMS directory. image-20180716101203-35

Figure. Flow of Reload
(Figure 342 in PDF)
 

image-20180716101203-34

fgfpb011
image-20180716101203-35
============
Topic: IMS Fast Path Basic Tools > Reloading a DEDB offline with FPB > DD statements for DEDB Reload > FABCUR3 JCL


This topic has been updated as follows:

DDNAME Use Format Required or optional
... ... ... ...
DURDBDFN Input PDS image-20180716101203-34Required when the DBDNAME= keyword is not specifiedimage-20180716101203-35
... ... ... ...

JOBLIB DD or STEPLIB DD
When DBRC=Y is specified on the EXEC statement or when IMGCPY=YES|DUAL and ICHASH=(YES) parameters are specified, the IMS load module library (IMSVS.SDFSRESL) must be concatenated with the FPB DEDB Unload/Reload library on the JOBLIB or STEPLIB DD.
To allocate a DBRC RECON data set and/or a DBRC non-registered area data set dynamically, the DFSMDA library data set must be concatenated.
To allocate an area data set dynamically when DBRC=N is specified, the DFSMDA library data set must be concatenated.
image-20180716101203-34If you specify the IMSCATHLQ= bsdshlq keyword, the IMS Tools Base library (SGLXLOAD) must be concatenated. image-20180716101203-35

ACBLIB DD
This statement defines the library that contains the DMB for the database.
image-20180716101203-34The location of the DMB must be supplied by the ACBLIB DD statement, the DURDBDFN DD statement, or the IMSCATHLQ=bsdshlq keyword.
FABCUR3 retrieves the DMB according to the following rules:
  1. The DBDNAME= keyword is specified.
    a. If the IMSCATHLQ=bsdshlq keyword is specified, DMB is retrieved from the IMS directory.
    b. If the IMSCATHLQ=bsdshlq keyword is not specified, DMB is retrieved from the ACBLIB library (ACBLIB DD).
  2. The DBDNAME= keyword is not specified. DMB is retrieved from the DURDBDFN data set (DURDBDFN DD).image-20180716101203-35

DURDBDFN DD
This statement defines the data set that contains a formatted copy of the DMB. It is the DURDBDFN data set from FABCUR1.
image-20180716101203-34The location of the DMB must be supplied by the ACBLIB DD statement, the DURDBDFN DD statement, or the IMSCATHLQ=bsdshlq keyword.
FABCUR3 retrieves the DMB according to the following rules:
  1. The DBDNAME= keyword is specified.
    a. If the IMSCATHLQ=bsdshlq keyword is specified, DMB is retrieved from the IMS directory.
    b. If the IMSCATHLQ=bsdshlq keyword is not specified, DMB is retrieved from the ACBLIB library (ACBLIB DD).
  2. The DBDNAME= keyword is not specified. DMB is retrieved from the DURDBDFN data set (DURDBDFN DD).image-20180716101203-35

============
Topic: IMS Fast Path Basic Tools > Reloading a DEDB offline with FPB > Input for DEDB Reload > SYSIN DD data set

The following new control statements have been added before "RAPERROR control statement":
  • IMSCATHLQ keyword
  • IMSCATACB_INPUT keyword

Control statement keywords
The FABCUR3 control statement contains the following keywords

Control statement keywords
The FABCUR3 control statement contains the following keywords
[DBDNAME= dbdname]
[IOVFBUF= nn]
[STARTAREA= zzz]
[TBLENTRY= mmmm]
[EXITRTN=( exit-routine, function)]
[IMGCPY= NO|YES|DUAL]
[ICHASH=( NO|YES,SSP)]
[ICCOMPRESS=( NO|YES, routine)]
[KEYSEQERROR={ NOCHECK|ABEND|BYPASS}]
[KEYCHGCHECK={ YES|NO}]
[SDEPRELOCATE={YES| NO}]
image-20180716101203-34[IMSCATHLQ={ *NO| bsdshlq}] image-20180716101203-35
image-20180716101203-34[IMSCATACB_INPUT={ CURRENT|PENDING}] image-20180716101203-35
[RAPERROR= NOCHECK|ABEND]

DBDNAME=
image-20180716101203-34This optional keyword specifies the DBD name of the DEDB for the unloaded segment records file. This keyword is required if ACBLIB DD or IMSCATHLQ= bsdshlq is specified instead of DURDBDFN DD to obtain the DEDB definition.
If DURDBDFN DD is specified, this keyword is not necessary.
When DBDNAME= is specified:
  • If both DURDBDFN DD and ACBLIB DD statements are specified, or both DURDBDFN DD statement and the IMSCATHLQ=bsdshlq keyword are specified, ACBLIB DD or the IMSCATHLQ=bsdshlq keyword takes precedence over DURDBDFN DD.
  • If the ACB library or the IMS directory is used, the ACB library or the IMS directory is validated to make sure that the correct ACB library or IMS directory is provided.image-20180716101203-35

image-20180716101203-34 IMSCATHLQ=
This optional keyword specifies to retrieve ACBs from the IMS directory (an extension of the IMS catalog) instead of from the ACB library.
bsdshlq
Specifies to read ACBs from the IMS directory by using the IMS Tools Catalog Interface. bsdshlq specifies the high level qualifier of the bootstrap data set of the IMS directory. IMSCATHLQ= bsdshlq is effective when the IMS catalog and the IMS management of ACBs are enabled.
If a TYPE=CATDSHLQ statement was used to create a DFSMDA member in your MDA library, you must specify the SYSDSHLQ parameter used in that DFSMDA member for the IMSCATHLQ keyword parameter.
*NO
Specifies to read ACBs from the ACB library. This is the default. image-20180716101203-35


image-20180716101203-34 IMSCATACB_INPUT=
This optional keyword specifies whether to retrieve currently active ACB definitions or pending ACB definitions from the IMS directory. IMSCATACB_INPUT keyword is effective only when the IMSCATHLQ=bsdshlq option is specified.
CURRENT
Specifies that currently active ACB members are retrieved from the IMS directory data sets. This is the default.
PENDING
Specifies that pending ACB members are retrieved from the staging data set. image-20180716101203-35

RAPERROR=
This optional keyword specifies whether FABCUR3 checks the validity of RAP data in the prefix part of the unloaded segment record by using the result of the randomizer call.
NOCHECK
Specifies that FABCUR3 does not check the validity of the RAP data in the prefix part of the unloaded segment record by using a randomizer. This is the default.
ABEND
Specifies that FABCUR3 checks the validity of the RAP data in the prefix part of the unloaded segment record by using a randomizer. FABCUR3 ends abnormally with an error message if it finds an error.
image-20180716101203-34 The DBDNAME= keyword and the ACBLIB DD are required for the ABEND option.
The DBDNAME keyword must be specified for RAPERROR=ABEND. Also, either the ACBLIB DD statement or the IMSCATHLQ=bsdshlq keyword must be specified. image-20180716101203-35

============
Topic: IMS Fast Path Basic Tools > Reloading a DEDB offline with FPB > Examples for DEDB Reload > Example 1: Reloading from an input data set with three areas

The title of this topic has been changed as follows:
image-20180716101203-34Example 1: Reloading from an input data set with three areas when IMS management of ACBs is enabled image-20180716101203-35

This topic has been updated as follows:

The execution JCL for the reload Job must contain DD statements for each of the three areas (that is, the ddnames specified in the new DMB).

image-20180716101203-34To retrieve ACB definitions from the staging IMS directory data set instead of the ACBLIB library, specify the following control statement keywords:
IMSCATHLQ=IMSVS.CATALOG
IMSCATACB_INPUT=PENDING image-20180716101203-35
For optimum performance, the following control statement keyword should be specified:
...

============
Topic: IMS Fast Path Basic Tools > Site default support for FPB

This topic has been updated as follows:

FPB allows you to specify site default parameters for its utilities: DEDB Pointer Checker (FABADA1 and FABADA4), DEDB Unload (FABCUR1), DEDB Reload (FABCUR3), DEDB Reload Segment Data Set Create utility (FABCUR6), and DEDB/HD Unload Conversion utility (FABCUR9). Macros and sample JCL streams are provided to generate the site default table.
...

Table. Macros and JCL members for site default table
(Table 115 in PDF)
Program Macro Sample JCL
FABADA1 FABAOP1M FABAOP1J
image-20180716101203-34FABADA4 FABAOP1M FABAOP1Jimage-20180716101203-35
... ... ...

FABAOP1M

The following paragraph has been added to all the keyword descriptions under FABAOP1M except for the two new keywords:

image-20180716101203-34This keyword is applicable to FABADA1 only. image-20180716101203-35


The following two new keywords have been added to the end of the FABAOP1M section:

image-20180716101203-34 IMSCATHLQ=
Specifies to retrieve ACBs from the IMS directory (an extension of the IMS catalog) instead of from the ACB library.
bsdshlq
Specifies to read ACBs from the IMS directory by using the IMS Tools Catalog Interface. bsdshlq specifies the high level qualifier of the bootstrap data set of the IMS directory. IMSCATHLQ=bsdshlq is effective when the IMS catalog and the IMS management of ACBs are enabled.
*NO
Specifies to read ACBs from the ACB library. This is the system default value.

This keyword is applicable to both FABADA1 and FABADA4. image-20180716101203-35


image-20180716101203-34 IMSCATACB_INPUT=
Specifies whether to retrieve currently active ACB definitions or pending ACB definitions from the IMS directory. IMSCATACB_INPUT keyword is effective only when the IMSCATHLQ= bsdshlq option is specified.
CURRENT
Currently active ACB members are retrieved from the IMS directory data sets. This is the system default value.
PENDING
Pending ACB members are retrieved from the staging data set.

This keyword is applicable to both FABADA1 and FABADA4. image-20180716101203-35

FABCOP1M

The following keywords have been added to the end of the FABCOP1M section:

image-20180716101203-34 IMSCATHLQ=
Specifies to retrieve ACBs from the IMS directory (an extension of the IMS catalog) instead of from the ACB library.
bsdshlq
Specifies to read ACBs from the IMS directory by using the IMS Tools Catalog Interface. bsdshlq specifies the high level qualifier of the bootstrap data set of the IMS directory. IMSCATHLQ=bsdshlq is effective when the IMS catalog and the IMS management of ACBs are enabled.
*NO
Specifies to read ACBs from the ACB library. This is the system default value. image-20180716101203-35

image-20180716101203-34 IMSCATACB_INPUT=
Specifies whether to retrieve currently active ACB definitions or pending ACB definitions from the IMS directory. IMSCATACB_INPUT keyword is effective only when the IMSCATHLQ= bsdshlq option is specified.
CURRENT
Currently active ACB members are retrieved from the IMS directory data sets.  This is the system default value.
PENDING
Pending ACB members are retrieved from the staging data set. image-20180716101203-35

FABCOP3M

The following keywords have been added to the end of the FABCOP3M section:

image-20180716101203-34 IMSCATHLQ=
Specifies to retrieve ACBs from the IMS directory (an extension of the IMS catalog) instead of from the ACB library.
bsdshlq
Specifies to read ACBs from the IMS directory by using the IMS Tools Catalog Interface. bsdshlq specifies the high level qualifier of the bootstrap data set of the IMS directory. IMSCATHLQ=bsdshlq is effective when the IMS catalog and the IMS management of ACBs are enabled.
*NO
Specifies to read ACBs from the ACB library. This is the system default value. image-20180716101203-35

image-20180716101203-34 IMSCATACB_INPUT=
Specifies whether to retrieve currently active ACB definitions or pending ACB definitions from the IMS directory. IMSCATACB_INPUT keyword is effective only when the IMSCATHLQ= bsdshlq option is specified.
CURRENT
Currently active ACB members are retrieved from the IMS directory data sets.  This is the system default value.
PENDING
Pending ACB members are retrieved from the staging data set. image-20180716101203-35
 

============

Topic: IMS Fast Path Online Tools > Extending a DEDB online with FPO > Region size requirements for OAE

This topic has been updated as follows:

  • image-20180716101203-34OAE requires the buffer set and IOVF work buffer calculated by the following formulas:
    Buffer set: (UOW1 + 5) * CISZ
    IOVF work buffer: CISZ * 125
    For the original expansion, an additional work buffer is required for the DEDB Area Data Set Create utility's use:
    Work buffer: (UOW1 + 7) * CISZimage-20180716101203-35
...

============

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > FABA messages

The following messages have been added:

image-20180716101203-34
FABA0113I INFORMATION OF THE DB DEFINITION WAS OBTAINED FROM resource

Explanation: This message indicates the resource (ACB library or IMS directory) where FABADA1 obtained DMB definitions from.
System action: FABADA1 continues processing.
User response: None. This message is informational.

image-20180716101203-35

---

image-20180716101203-34

FABA3537E IMS TOOLS CATALOG INTERFACE CANNOT BE USED
          - UNSUPPORTED IMS RELEASE

Explanation: The IMSCATHLQ= bsdshlq keyword is specified, but FABADA1 or FABADA4 could not use the IMS Tools Catalog Interface to read ACBs from the IMS directory because the version of IMS is lower than 14.
System action: FABADA1 or FABADA4 ends with an abend code of 3537.
User response: Rerun the job using a supported version of IMS.

image-20180716101203-35

---

image-20180716101203-34

FABA3538E IMS TOOLS CATALOG INTERFACE function FUNCTION (DEFINITION=CURRENT|PENDING) FAILED
          - RETURN CODE: rc, REASON CODE: rsn

Explanation: The IMS Tools Catalog Interface ended with an error. function shows the function code of the IMS Tools Catalog Interface. The return code and reason code from the IMS Tools Catalog Interface are shown in rc and rsn, respectively.
System action: FABADA1 or FABADA4 ends with an abend code of U3538.
User response: If the function is OPEN, check if the correct high level qualifier of the bootstrap data set is specified in the IMSCATHLQ keyword. Otherwise,
contact IBM Software Support.
image-20180716101203-35
---
The following messages have been updated as follows:

FABA0111W   image-20180716101203-34 xxxxxxxxxxxxx  DATE/TIME STAMP LATER THAN DATE/TIME STAMP FROM IMAGE-COPY DATA SET image-20180716101203-35

Explanation: image-20180716101203-34Program FABADA1 determined that the DMB read from the ACB library or the IMS directory was created after the Image Copy of the DEDB was created. image-20180716101203-35

---
FABA0111E   image-20180716101203-34 xxxxxxxxxxxxx  DATE/TIME STAMP LATER THAN DATE/TIME STAMP FROM IMAGE-COPY DATA SET image-20180716101203-35

Explanation: image-20180716101203-34Program FABADA1 determined that the DMB read from the ACB library or the IMS directory was created after the Image Copy of the DEDB was created. image-20180716101203-35

---
FABA3504E   image-20180716101203-34 PROCESSING FAILED FOR xxxxxx MEMBER
- xxxxxx MEMBER IS NOT A DEDB DMB
- MEMBER NAME NOT EQUAL DEFINED DATABASE NAME
- ddname DD STATEMENT NOT FOUND
- MEMBER NOT FOUND IN ACBLIB
- INSUFFICIENT STORAGE
- INVALID PARAMETER LIST IN CALL TO nnnnnnnn
- IMS LEVEL OF ACB MEMBER acbname NOT SUPPORTED
- ACB MEMBER acbname HAS NO DATA
image-20180716101203-35

Explanation: image-20180716101203-34Program FABADA1 called either the FABAGDD program to get DMB information from the ACBLIB library, or the  FABAGDD2 program to get DMB information from the IMS directory, related to the database being processed. The return code specified that the attempt so was unsuccessful. image-20180716101203-35
System action: FABADA1 ends with an abend code of 3504.
User response: image-20180716101203-34Make sure that the files associated with the DD statements DFSUDUMP (or DARVSAM) and ACBLIB or the IMS directory are correctly specified. Also, make sure that the ACBGEN and DBDGEN or IMS catalog population were correctly performed for the database being analyzed. Correct any errors, and rerun the job. If "- INVALID PARAMETER LIST IN CALL TO FABAGDD" is shown, contact IBM Software Support. image-20180716101203-35

---

FABA3526E   DEDB DEFINITION MISMATCH:
FIELD: fieldname
image-20180716101203-34 VALUE FROM xxxxxx DMB: value-1
VALUE FROM I/C "DMAC" RCD: value-2
image-20180716101203-35

Explanation: image-20180716101203-34Program FABADA1 determined that the specifications found in the file associated with the ACBLIB DD statement or the IMS directory did not match those found in the "DMAC" record of the Image Copy data set. image-20180716101203-35
System action: FABADA1 ends with an abend code of 3526.
User response: image-20180716101203-34Make sure that the file associated with the ACBLIB DD statement or the IMS directory contains the correct DMB for the database in the files associated with the DFSUDUMP DD statement. Rerun the job. image-20180716101203-35

============

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > FABC messages

The following messages have been added:
image-20180716101203-34
FABC0186E keyword1=value1 IS NOT ALLOWED
          - keyword1=value1 AND keyword2=value2 ARE EXCLUSIVE

Explanation: Keywords keyword1 and keyword2 cannot be specified together.
System action: FABCUR1 ends with an abend code of 3728.
User response: Correct or remove the indicated control statement.
image-20180716101203-35

---

image-20180716101203-34
FABC0187I INFORMATION OF THE DB DEFINITION WAS OBTAINED FROM resource
 
Explanation:  This message indicates the resource (ACB library or IMS directory) where FABCUR1 obtained DMB definitions from.
System action: FABCUR1 continues processing.
User response: None. This message is informational.
image-20180716101203-35
---
image-20180716101203-34
FABC0188E keyword= CONTROL CARD PREVIOUSLY PROCESSED

Explanation: The indicated keyword cannot be specified more than once in a control statement.
System action: FABCUR1 ends with an abend code of 3728.
User response: Remove the duplicate specification and rerun the job.
image-20180716101203-35
---
image-20180716101203-34
FABC0189E INVALID keyword= CONTROL CARD

Explanation: Program FABCUR1 encountered an invalid specification while parsing the user-supplied control statement.
System action: FABCUR1 ends with an abend code of 3728.
User response: Correct the error and rerun the job.
image-20180716101203-35
---
image-20180716101203-34
FABC0368E "keyword=" PREVIOUSLY SPECIFIED

Explanation: The indicated keyword cannot be specified more than once in a control statement.
System action: FABCUR3 ends with an abend code of 3728.
User response: Remove the duplicate specification and rerun the job.
image-20180716101203-35
---
image-20180716101203-34
FABC0369E "keyword=" VALUE INCORRECT

Explanation: Program FABCUR3 encountered an invalid specification while parsing the user-supplied control statement.
System action: FABCUR3 ends with an abend code of 3761.
User response: Correct the error and rerun the job.
image-20180716101203-35
---
image-20180716101203-34
FABC3835E IMS TOOLS CATALOG INTERFACE CANNOT BE USED
          - UNSUPPORTED IMS RELEASE

Explanation: The IMSCATHLQ= bsdshlq parameter is specified on SYSIN, but FABCUR1 or FABCUR3 could not use the IMS Tools Catalog Interface to read the ACB from the IMS directory because the version of IMS is lower than 14.
System action: FABCUR1 or FABCUR3 ends with an abend code of 3835.
User response: Rerun the job using a supported version of IMS.
image-20180716101203-35
---

image-20180716101203-34

FABC3836E IMS TOOLS CATALOG INTERFACE function FUNCTION (DEFINITION=CURRENT|PENDING) FAILED
          - RETURN CODE: rc, REASON CODE: rsn

Explanation: The IMS Tools Catalog Interface ended with an error. function shows the function code of the IMS Tools Catalog Interface. The return code and reason code from the IMS Tools Catalog Interface are shown in rc and rsn, respectively.
System action: FABCUR1 or FABCUR3 ends with an abend code of U3836.
User response: If the function is OPEN, check if the correct high level qualifier of the bootstrap data set is specified in the IMSCATHLQ keyword. Otherwise,
contact IBM Software Support.
image-20180716101203-35

---

The following messages have been updated as follows:

FABC0155W   image-20180716101203-34 xxxxxxxxx; NEWDBDNM= KEYWORD IGNORED image-20180716101203-35 

Explanation: image-20180716101203-34Program FABCUR1 found a DB name change requirement, but the NEWACB DD statement was not present or the IMSCATACB_OUTPUT keyword is not specified. The additional message FABC0164I appears. image-20180716101203-35

---
FABC0160W   image-20180716101203-34 xxxxxxxx; HIERCHNG=YES/YESFORCE IGNORED image-20180716101203-35

Explanation: Self-explanatory.
System action: Program FABCUR1 sets an end-of-job return code of 4, and continues processing.
User response: Correct the control statement stream in subsequent executions of FABCUR1. The HIERCHNG keyword of the DBDNAME control statement should be specified with a value of YES/YESFORCE only when:
  1. A change to the segment hierarchy is desired, and
  2. image-20180716101203-34A DMB reflecting that change is provided in the file associated with the NEWACB DD statement or the pending ACB definition in the IMS directoryimage-20180716101203-35

---
FABC0163W  image-20180716101203-34 xxxxxxxx; IGNORED DUE TO "REORG" KEYWORD

Explanation: image-20180716101203-34Program FABCUR1 detected the presence of a NEWACB DD statement or the IMSCATACB_OUTPUT keyword. When REORG is specified for the DBDNAME control statement, NEWACB DD statement and the IMSCATACB_OUTPUT keyword are ignored.

---
FABC0164I image-20180716101203-34 xxxxxxxx; "REORG" MODE ASSUMED image-20180716101203-35

Explanation: image-20180716101203-34Program FABCUR1 issued an SVC 24 (DEVTYPE) specifying the ddname NEWACB. The return code specified that such a DD statement was not present in the JCL stream, hence REORG mode processing was assumed.  If IMS managed ACBs are used and the IMSCATACB_OUTPUT keyword is not specified, the program runs the job in REORG mode. image-20180716101203-35

---
FABC0174E   - INCORRECT SEGMCTL= CONTROL CARD
image-20180716101203-34 SEGMENT: segname IS NOT DEFINED IN DMB xxxxxxxx FROM nnnnnnnn image-20180716101203-35

---
FABC0328I   image-20180716101203-34 SDEP SEGMENTS ARE RELOCATED DUE TO SDEP=PHYSICAL SPECIFIED WITH xxxxxxxx image-20180716101203-35

Explanation: image-20180716101203-34Locations of each SDEP segments are changed from the original RBA because the segments were unloaded with SDEP=PHYSICAL accompanied by a DEDB change with NEWACB or the IMSCATACB_OUTPUT keyword. image-20180716101203-35

---
FABC0361I  image-20180716101203-34 INFORMATION OF THE DB DEFINITION WAS OBTAINED FROM resource image-20180716101203-35

Explanation: image-20180716101203-34This message is to inform which source (DURDBDFN DD, ACBLIB DD, or the IMS directory) is used to obtain the DEDB definition information. image-20180716101203-35

---
FABC3729E  image-20180716101203-34 DMB MEMBER member-name FOR xxxxxxxxxxxxx HAS NO DATA image-20180716101203-35

---
FABC3731E image-20180716101203-34 MEMBER member-name FROM xxxxxxxxxx  DEFINES DATABASE dbdname image-20180716101203-35

Explanation: image-20180716101203-34Program FABCUR1/FABCUR3/FABCUR5/FABCUR6/FABCUR8 called an internal routine to read and analyze a DMB in the specified ACBLIB data set or the IMS directory. The return code from the routine specified that the member name did not match the name of the database for which the member was a DEDB DMB. image-20180716101203-35
System action: FABCUR1/FABCUR3/FABCUR5/FABCUR6/FABCUR8 ends with an abend code of 3731.
User response: image-20180716101203-34Make sure that the DD statement specified properly specifies the correct data set, and that the DBDGEN and ACBGEN, or IMS catalog population, have completed successfully for the database being processed. Correct the errors, and rerun the job. image-20180716101203-35

---
FABC3732E   image-20180716101203-34 MEMBER member-name FROM xxxxxxxxxx  IS NOT A DEDB DMB image-20180716101203-35

Explanation; Self-explanatory.
System action; Program FABCUR1/FABCUR3/FABCUR5/FABCUR6/FABCUR8 ends with an abend code of 3732.
User response: image-20180716101203-34Make sure that the DD statement specified specifies the correct data set, and that the DBDGEN and ACBGEN, or IMS catalog population, have completed successfully for the database being processed. Correct the errors, and rerun the job. image-20180716101203-35

---
FABC3733E   image-20180716101203-34 AREA xxxxx SPECIFIED ON AREACTL= CARD NOT DEFINED IN DMB xxxxxxxx FROM xxxxxxxx image-20180716101203-35

User response: image-20180716101203-34Verify the correctness of the user-supplied AREACTL control statements. Make sure that the OLDACB DD statement or the IMS directory is specified correctly. Correct the errors, and rerun the job. image-20180716101203-35

---
FABC3738E   image-20180716101203-34 IMS LEVEL OF MEMBER member-name FROM xxxxxxxxxx IS NOT SUPPORTED image-20180716101203-35

Explanation: Self-explanatory.
System action: Program FABCUR1/FABCUR3/FABCUR5/FABCUR6/FABCUR8 ends with an abend code of 3738.
User response: image-20180716101203-34Make sure that the correct data set is referenced, and that the DBDGEN and ACBGEN, or IMS catalog population have completed successfully for the database being processed. The ACB member may have been assembled with an unsupported release of IMS. Correct the errors, and rerun the job. image-20180716101203-35

---
FABC3788E   image-20180716101203-34 SDEP=PHYSICAL SPECIFIED BUT
CI SIZE UNMATCH BETWEEN xxxxxxxx AND yyyyyyyy
AREA NAME SPECIFIED IN  xxxxxxxx NOT FOUND IN yyyyyyyy
image-20180716101203-35

Explanation: Program FABCUR1 found that the SDEP=PHYSICAL keyword parameter is specified, but there is one of the following errors:
  • image-20180716101203-34The CI size of an area does not match between OLDACB and NEWACB, or between the current active ACB and the pending ACB in the IMS catalog.image-20180716101203-35
  • The REORG keyword is not specified or NEWACB DD is provided with or without the HIERCHNG= keyword parameter.
  • image-20180716101203-34The area name defined in the OLDACB was not found in the NEWACB. If IMS managed ACBs are used, the area name defined in the current active ACB was not found in the pending ACB.image-20180716101203-35

---
FABC3789E   image-20180716101203-34 SDEP= CONTROL CARD SPECIFIED
SDEP SEGMENT NOT DEFINED IN DMB xxxxxxxx FROM yyyyyyyy
image-20180716101203-35

Explanation: Program FABCUR1 found that the SDEP=LOGICAL|PHYSICAL keyword parameter is specified, but the database specified by the DMB name does not define a SDEP segment.
System action: FABCUR1 terminates with an abend code of 3789.
User response: image-20180716101203-34Make sure that the correct DBDNAME or ACB library, or the IMS catalog is specified. Correct the error, and rerun the job. image-20180716101203-35

---
FABC3813E   image-20180716101203-34 DBDNAME AND xxxxxxxx ARE REQUIRED WHEN RAPERROR=ABEND IS SPECIFIED image-20180716101203-35

---
FABC3905E   image-20180716101203-34 AREA IN xxxxxxxx AREA nnnnn (AREANAME: areaname) NOT DEFINED IN yyyyyyyy image-20180716101203-35

Explanation: image-20180716101203-34The area specified is defined in OLDACB but not in NEWACB, or in the current active ACB but not in the pending ACB. image-20180716101203-35
System action: Program FABCUR1 ends with an abend code of 3905.
User response: image-20180716101203-34Make sure that the correct NEWACB data set or the pending ACB is specified. Correct the error, and rerun the job. image-20180716101203-35


Update 3

Date of change: December 2018

Change description: Documentation changes by APAR PH05366. This APAR resolves ABENDU3824 that is caused by errors related to CSI calls.

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > FABC messages

The following two new messages have been added:

image-20180716101203-34
FABC0370I INSUFF. STORAGE FOR: aaaa - INCREASE REGION SIZE


Explanation: Program FABCUR3 issued a GETMAIN macro to allocate storage for the purpose of aaaa. The attempt was unsuccessful.

System action: FABCUR3 calculates HIGH ALLOCATE RBA of the multi-volume ADS without using the Catalog Search Interface (CSI) and continues processing.

User response: None. This message is informational.

image-20180716101203-35
---

image-20180716101203-34

FABC0371I - FAILURE READING DATA SET INFORMATION FROM CATALOG

- DSN: data_set

- REASON CODE: xxx RETURN CODE: yyy

- NOT FOUND DATA PORTION

- INCONSISTENT ENTRY NUMBER. VOLSER: nn xxxxxxxx: nn

- THE NUMBER OF VOLUME IS BEYOND THE LIMIT


Explanation: An inconsistency is found in the catalog information.

System action: FABCUR3 calculates HIGH ALLOCATE RBA of the multi-volume ADS without using the Catalog Search Interface (CSI) and continues processing.

User response: None. This message is informational.

image-20180716101203-35
============

Message FABC3760E has been changed as follows:


image-20180716101203-34FABC3760E INSUFF. STORAGE FOR: aaaa - INCREASE REGION SIZEimage-20180716101203-35


============

Message FABC3824E has been deleted:

image-20180716101203-34
FABC3824E   - FAILURE READING DATA SET INFORMATION FROM CATALOG.

- DSN: data_set

- REASON CODE: xxx RETURN CODE: yyy

- NOT FOUND DATA PORTION

- INCONSISTENT ENTRY NUMBER. VOLSER: nn xxxxxxxx: nn

- THE NUMBER OF VOLUME IS BEYOND THE LIMIT.

image-20180716101203-35


Update 2

Date of change: July 2018

Change description: Documentation changes by APAR PI94622. This APAR enhances the tools and utilities of IMS HP Fast Path Utilities to support encrypted DEDB area data sets.

Topics: Changes apply to multiple topics.

Topic: Overview of IMS HP Fast Path Utilities > What is IMS HP Fast Path Utilities?

The following new topic has been added:

image-20180716101203-34

Support for DEDB encryption


All the tools and utilities of IMS HP Fast Path Utilities support encrypted DEDB area data sets (ADSs).


To enable the tools and utilities to process DEDB ADSs that are encrypted with z/OS data set encryption, the following conditions must be met:

    APAR PI83756 is applied to IMS Version 15.
    APAR PI94622 is applied to IMS Fast Path Solution Pack.

You do not need to change the JCL streams to process encrypted DEDB ADSs.


For IMS Fast Path Advanced Tool, if you use the ALLOCATE subcommand to dynamically define a VSAM cluster that is used for the processing of a FPA command, you can also encrypt the VSAM cluster by specifying the encryption key label with the KEYLABEL keyword.

For more information, see "KEYLABEL keyword".

image-20180716101203-35

Topic: IMS Fast Path Advanced Tool > Reloading a DEDB offline with FPA > Examples for the Reload function > Example 3: Reloading multiple areas of a DEDB from one input unloaded segment record data set

This topic has been updated as follows:

The following figure shows example JCL for reloading multiple areas of a DEDB from one input unloaded segment record data set.

This example shows a case of Reload by using the unloaded segment records data sets that are produced by Example 3: Unloading multiple areas of a DEDB into one output unloaded segment record data set.

In this example:

  • The DBRC=NO option specifies not to check the area status in DBRC, so RECON data sets are not needed.
  • The input unloaded segment records data set for area DB22AR0 and DB22AR1 is HPFP.USRFILE1 that is specified by the IAREA001 DD statement.
  • The input unloaded segment records data set for area DB22AR2 and DB22AR3 is HPFP.USRFILE2 that is specified by the IAREA002 DD statement.
  • Because the two input unloaded segment records data sets are already sorted during the unloading process, it is not necessary to specify the SORT=YES parameter. If these data sets were not sorted during the Unload process, SORT=YES must be specified.
  • The output ADSs to be reloaded for specified areas are dynamically allocated by using the ODSNMASK parameter and the ALLOCATE subcommand.
  • image-20180716101203-36The output ADSs to be reloaded for specified areas are encrypted with a key label associated with the area data sets. The key label is specified on the KEYLABEL keyword of the ALLOCATE subcommand. image-20180716101203-37
  • The following ADSs are allocated:

Area

Allocated ADS

DB22AR0

HPFP.DB22AR0.ADS1

DB22AR1

HPFP.DB22AR1.ADS1

DB22AR2

HPFP.DB22AR2.ADS1

DB22AR3

HPFP.DB22AR3.ADS1

Figure. Reloading multiple areas of a DEDB from one input unloaded segment record data set

(Figure 45 in PDF)

image-20180716101203-38

image-20180716101203-39

image-20180716101203-40

Topic: IMS Fast Path Advanced Tool >  Initializing a DEDB offline with FPA > Examples for the Initialize function > Example 2: Initializing multiple areas in an SMS environment

This topic has been updated as follows:

The following figure shows example JCL for initializing multiple areas in an SMS environment.

In this example:

  • The DBRC=IGNORE option specifies not to check the area status in DBRC, so RECON data sets are not needed. Even if DBRC=FORCE is set for IMS, DBRC is not activated when the DBRC=IGNORE option is specified.
  • The output ADSs to be initialized for specified areas are dynamically allocated by using the ODSNMASK parameter and the ALLOCATE subcommand.
  • image-20180716101203-41The output ADSs to be reloaded for specified areas are encrypted with a key label associated with the area data sets. The key label is specified on the KEYLABEL keyword of the ALLOCATE subcommand. image-20180716101203-42
  • The following ADSs are allocated:

Area

Allocated ADS

DB22AR0

HPFP.DB22AR0.ADS1

DB22AR1

HPFP.DB22AR1.ADS1

DB22AR2

HPFP.DB22AR2.ADS1

Figure. Initializing multiple areas in an SMS environment

(Figure 192 in PDF)

image-20180716101203-43

image-20180716101203-44

image-20180716101203-45

Topic: IMS Fast Path Advanced Tool > Command reference for FPA > FPA subcommands > ALLOCATE subcommand

This topic has been updated as follows:

Use the ALLOCATE subcommand to dynamically define a VSAM cluster that is used for the processing of the FPA command.

ALLOCATE is an optional subcommand for the following commands:

  • CHANGE
  • INITIALIZE
  • RELOAD

Related keywords:

  • AMSOPT keyword
  • ATTRIBUTE keyword
  • AVGREC keyword
  • DATACLAS keyword
  • image-20180716101203-46KEYLABEL keyword image-20180716101203-47
  • MGMTCLAS keyword
  • OAREA keyword
  • SPACE keyword
  • STORCLAS keyword
  • VOLSER keyword

Format:

ALLOCATE [keyword=parameter[,...]]

Syntax:

image-20180716101203-48

image-20180716101203-49

image-20180716101203-50

Topic: IMS Fast Path Advanced Tool > Command reference for FPA > FPA subcommands > FPA keywords  

The following new topic has been added:

image-20180716101203-51

KEYLABEL keyword


Use the KEYLABEL keyword to specify the key label for encrypting a new VSAM cluster. When encryption is requested for the base cluster, any alternate indexes associated with the base cluster will also be encrypted and use the same key label as specified for the cluster.


For more information about KEYLABEL parameter, see z/OS DFSMS Access Method Services Commands.


KEYLABEL is an optional keyword for the ALLOCATE subcommand.


Format:

image-20180716101203-52

keylabel

Specify a 1- to 64-character data key label.

Default: None.


Site default support: Not supported.


Alias: KLBL  


Keyword abbreviation: Not supported.

image-20180716101203-53

Topic: IMS Fast Path Online Tools > RACF considerations for FPO

This topic has been updated as follows:

...

The following call is issued by the security module to validate that the user has sufficient authority to access the utility of FPO:

image-20180716101203-54

image-20180716101203-55Note: The high level qualifier of the ADS does not need to be the same as the ENTITYX parameter ’imsid.dbname.areaname’.image-20180716101203-56

...

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > FABC messages

The following new message has been added:

image-20180716101203-57

FABC3825E THE SIZE OF THE RELOADED AREA DATA SET IS MORE THAN 4G BYTES

- AREA NO: nn, AREA NAME: areaname

- DDNAME: ddname, DSNAME: dsname

Explanation: The size of the reloaded area data set exceeds 4GB.

System action: FABCUR3 ends with an abend code of 3825.

User response: Delete and redefine the area data set. Make sure that the size of the ADS does not exceed 4GB.

image-20180716101203-58

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > FPX messages

The user response section has been updated as follows:

FPX0005E Authorization failure ENTITY = <imsid.dbname.areaname> SAF RC=aa RACF RC=bb RACF RSN=dd

Explanation: A security check to validate access failed.

System action: Processing ends with a return code of 8, and the ODE run-level control using SYSIN and FPXCTL DD ends with a return code of 12.

User response: Make sure that you have appropriate authorization to the specified entity. For details, see “RACF considerations for FPO”.

image-20180716101203-59The high level qualifier of the ADS does not need to be the same as the ENTITYX parameter ’imsid.dbname.areaname’.

image-20180716101203-60

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > HFPF messages

The following new message has been added:

image-20180716101203-61

HFPF3374E   "PGSER" MACRO FAILED. (RC: xx)


Explanation: Program HFPMAIN0 issued a PGSER macro to do page fix or page free. The return code shows that the attempt was unsuccessful.

System action: The job ends with an abend code of U3003.

User response: Correct any errors, and rerun the job. If this situation persists, contact IBM Software Support.

image-20180716101203-62

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages >  HFPV messages

The following new messages have been added:

image-20180716101203-63

HFPV0008I DEFINED AREA DATA SET DOES NOT HAVE THE ENCRYPTION ATTRIBUTE.

-  AREA NO: nn, AREA NAME: areaname 

- DDNAME: ddname, DSNAME: dsname

Explanation: An encryption key label is specified on the KEYLABEL keyword of the ALLOCATE subcommand. However, this key label was not applied to the indicated area data set because the area data set is not in extended format.

System action: Processing continues. The area data set is successfully created as a non-encrypted format data set.

User response: No further action is required. However, if you want the area data set to be an encrypted data set, allocate the data set by specifying the DATACLAS parameter with the extended format attribute.

image-20180716101203-64

---

image-20180716101203-65

HFPV3068E THE SIZE OF THE AREA DATA SET IS MORE THAN 4G BYTES.

- AREA NO: nn, AREA NAME: areaname 

- DDNAME: ddname, DSNAME: dsname

Explanation: The size of the area data set exceeds 4GB.

System action: The job ends with an abend code of U3003.

User response: If the indicated ADS contains segment data, run the ODE utility to extract all segments from the ADS, then reload the segments to a new ADS whose size is smaller than 4GB.

If the indicated ADS is empty, delete and redefine the ADS. Make sure that the size of the ADS does not exceed 4GB.

image-20180716101203-66



Update 1
Date of change: April 2018
Change description: Documentation changes by APAR PI94659.
Topics: Changes apply to multiple topics.

Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > HFPV messages

The following messages have been updated as follows:

HFPV0005E ALL ADS I/O FAILED FOR AREA NO: nnnnn, AREANAME: areaname

Explanation: An I/O error occurred. If multiple area data sets (MADS) are defined, this message indicates that the I/O error occurred for all area data sets of the MADS.
System action: The return code is set to 8 and processing continues.
User response: See the other messages that are related to I/O error, correct the error, and rerun the job.

---
HFPV3056E ALL ADS I/O FAILED FOR AREA NO: nnnnn, AREANAME: areaname

Explanation: An I/O error occurred. If multiple area data sets (MADS) are defined, this message indicates that the I/O error occurred for all area data sets of the MADS.
System action: The job ends with an abend code of U3003, or ends with a return code of 12.
User response: See the other messages that are related to I/O error, correct the error, and rerun the job.
Topic: Troubleshooting > Messages and codes of IMS HP Fast Path Utilities > Messages > HFPS messages

Message HFPS0001E has been updated as follows:

HFPS0001E DATASET AT DDNAME ddname IS NOT FOR AREA areaname
    • - MISMATCH VALIDATING FIELD: xxxxxxxx
      - VALUE IN DMB xxxxxxxx: xxxxxxxx
      - VALUE IN DMAC : xxxxxxxx

Explanation: Program HFPMAIN0 or HFPSENSR issued an OPEN macro for the VSAM that is associated with the ddname that is specified. A comparison of certain key values that were extracted from the DMB from data sets OLDACB, IMSACB, IMSACBA, or IMSACBB with the contents of the second CI in the VSAM showed that the VSAM was not the database that was described by the DMB.
System action: The program ends with an abend code of 3003. If this error occurs for multiple area data sets (MADS) but not for all the area data sets of the MADS, the program ends with a return code of 8.
User response: Verify that the DD statement that was specified is correct and that the OLDACB DD statement specifies the correct data set. Correct the errors, and rerun the job.

Document information

More support for: IMS Tools

Component: IMS Fast Path Solution Pack

Software version: 1.3.0

Operating system(s): z/OS

Reference #: 7050984

Modified date: 28 March 2019