Updates to IMS Fast Path Solution Pack: IMS High Performance Fast Path Utilities V1.2 User's Guide

Product documentation


Abstract

Updates that apply to IMS Fast Path Solution Pack: IMS High Performance Fast Path Utilities V1.2 User's Guide (SC19-3287-00).

Content

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



Update 32
Date of change: April 2014
Change description: User's guide update.
Topic:
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.1 FABA messages

Explanation and User response sections in the following message have been updated as follows:

FABA3519E "OPEN" FAILED FOR VSAM DATA SET
- VSAM ERROR DATA: RETURN CODE: aaa ( bb ) ACB ERROR: ccc ( dd )

Explanation: Start of changeBecause VSAM=YES was found in either the FABADA1 SYSIN data set or the site default table, program FABADA1 issued an OPEN macro for the VSAM data set specified by the DARVSAM DD statement. The return code indicates that the attempt was unsuccessful. End of change The return code and ACB error code values are shown in both decimal ( aaa, ccc) and hexadecimal ( bb, dd) format.
System action: FABADA1 ends with an abend code of 3519.
User response: Make sure that a DARVSAM DD statement is present and that it properly identifies the correct data set. Start of changeIf you want to process image copy data sets, remove the VSAM=YES entry in the FABADA1 SYSIN data set and in the site default table. Then, rerun the job. If this situation persists, report it to systems operations personnel. End of change




Update 31
Date of change: March 2014
Change description: Documentation changes by APAR PI08199. Three new messages have been added.
Topics: Changes are made to the following multiple topics.

> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.6 FPX messages

The following two new messages have been added:
Start of change
FPX0339E Incorrect RBA value in CI at RBA xxxxxxxx.
      (cont) RBA value: yyyyyyyy Offset: zzzz

Explanation: The indicated RBA value ( yyyyyyyy), which is at offset zzzz of a CI at RBA xxxxxxxx, is incorrect.
System action: Processing ends with an abend code of U3500.
User response: Run the FPA Analyze function to check the integrity of the CI. Correct the reported problem, and rerun the job.
End of change
-----------------
Start of change
FPX0340E [OPEN | GET] failed for VSAM data set.
      (cont) - DSNAME: dsname
      (cont) - Return code is rc ( hex_rc), [ACB error flag code | RPL feedback area] is rsn ( hex_rsn)

Explanation: The utility received a nonzero return code from VSAM when attempting to access the VSAM data set with the OPEN or GET macro. The return code and the reason code are shown in both decimal ( rc, rsn) and hexadecimal ( hex_rc, hex_rsn) format.
System action: Processing ends with an abend code of U3500.
User response: See DFSMS Macro Instructions for Data Sets, which describes VSAM administration macros. If this situation persists, contact IBM Software Support.
End of change
-----------------
>>>> 7.1.3.29 Resolve Pointers report messages

The following new message has been added:
Start of change
0120
    INCORRECT RBA VALUE IN CI AT RBA: xxxxxxxx (RBA VALUE: yyyyyyyy OFFSET: zzzz)

Explanation: The Analyze process detected that the indicated RBA value ( yyyyyyyy), which is at offset zzzz of a CI at RBA xxxxxxxx, is incorrect.
User response: Run the FPA Unload function and the FPA Reload function for the area to fix the incorrect FPA value in the CI.
End of change



Update 30
Date of change: January 2014
Change description: User's guide updates and corrections.
Topic: Changes are made to the following multiple topics.

> 2.0 IMS Fast Path Advanced Tool
>> 2.11 Command reference for FPA
>>> 2.11.4 FPA keywords
>>>> 2.11.4.30 ICACHE

This topic has been updated as follows:

Use the ICACHE keyword to specify the type of control intervals that are to be preloaded into a data space storage for processing.

ICACHE is an optional keyword for the following commands:
  • ANALYZE
  • CHANGE
  • EXTRACT
  • INDEXBLD
  • REORG
  • TUNE
  • UNLOAD
Start of changeIf an image copy is used as the input data set for the Analyze function, the Change function, the Extract function, or the Unload function, ICACHE=YES must be specified because sufficient storage is needed to read image copies.

If CISNAP=YES is specified for the Analyze function or the Tune function and pointer errors are detected, these functions generate a CI Map/CI Dump report. The following table shows how the function generates a CI Map/CI Dump report from the areas that have pointer errors.

Input area data set ICACHE parameter How a dump is generated when pointer errors are detected
Image copy NO Re-reads the image copy data set until the RBA that has pointer errors is reached, and then generates a snap dump for the pointer errors.
Image copy YES Image copy data set is not read. Generates a snap dump by using the CI image that is preloaded into the data space.
VSAM ESDS Forced to NO Re-reads the VSAM data set that corresponds to the RBA that has pointer errors, and then generates a snap dump for the pointer errors.
End of change

When you use the INDEXBLD command and when the input data sets are area data sets, consider specifying ICACHE=NO. If ICACHE=NO is not specified, considerable amount of data space is consumed by many input thread tasks because generally IAREA=ALL is used for the INDEXBLD command.

To determine the number of data spaces that are created by FPA, complete the following steps:
    1. Calculate the size of the BASE, IOVF, and SDEP parts for each input thread subtask.
    2. Add the sizes of all BASE, IOVF, and SDEP parts.

If the total size of the BASE, IOVF, and SDEP parts is less than 2 GB, FPA requires only one data space. Otherwise, FPA requires two data spaces.

Note: The BASE part is required only when the input is in IC format.

Related keywords:
    • ICINCOMP
    • OCACHE

Format:

 ICACHE=parameter

    parameter
      Specify one of the following parameters:
    YES
      Start of changePreload IOVF and SDEP parts into the data space when an ADS is used as the input data set with any FPA command except the ANALYZE command and the TUNE command.

      If a VSAM ESDS is used as the input data set for the Analyze function or the Tune function, ICACHE parameter is forced to NO, even if ICACHE=YES is specified. End of change

      If an image copy is used as the input data set for the Analyze function, the Change function, the Extract function, the Tune function, or the Unload function, FPA preloads the root addressable part, the IOVF part, and the SDEP part into the data space.

    NO
      Start of changeDo not preload BASE, IOVF and SDEP parts into the data space. End of change

Default:
    ICACHE=YES

Site default support:
    Supported.

=====================
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.27 HFPV messages

Descriptions of the following messages have been updated as follows:

HFPV0004I xxxx PART COULD NOT BE PRELOADED INTO A DATA SPACE FOR PROCESSING IN keyword=YES.
        - AREA NO: nn, AREANAME: areaname
        - RC: return-code, RSN: reason-code
Explanation: Start of changeProgram HFPMAIN0 uses a VSAM area data set or an image copy data set for xxxx (BASE, IOVF or SDEP) as the work area even if keyword (ICACHE or OCACHE)=YES is specified because the work area cannot be acquired in the data space. End of change
System action: Start of changeIf a VSAM area data set is used, processing continues by using the VSAM area data set instead of the data space for an IOVF and/or a SDEP part. If an image copy data set is used, processing ends and the program issues a HFPV error message. End of change
User response: Start of changeIf an image copy data set is used, check the subsequent HFPV message. Otherwise, no action is required. End of change

-----------------
HFPV3053E RESOURCE SHORTAGE FOR ACCESS OF IMAGE COPY DATA SET DDNAME: ddname
        - RC: return-code, RSN: reason-code
        - UNABLE TO GET IC BUFFER.
        RESOURCE LIMITED BY THE IEFUSI EXIT. RC: return-code, RSN: reason-code

Explanation: IC buffer exceeded the data space or the storage for the RAA BASE, IOVF, SDEP part, or the required data space could not be created. Either of the subtexts is issued.
System action: The job ends with an abend code of U3003.
User response: Rerun the job with the ICINCOMP=YES keyword. If the problem is caused by the IEFUSI exit, contact your system programmer for local restrictions on creating and using data spaces. Start of changeFor the Analyze function or the Tune function, if this problem persists, rerun the job with the ICACHE=NO keyword. End of change
For information about the keywords, see the following topics:
  • ICACHE
  • ICINCOMP

-----------------
HFPV3060E NOT EMPTY DATA SET FOR AREANAME: areaname, DDNAME: ddname

Explanation: The VSAM data set that was specified in ddname for the area areaname was not empty.
System action: The job ends with an abend code of U3003.
User response: Start of changeDelete and redefine the VSAM cluster for the specified area. Do not run the FPA Initialize function or the DEDB Initialization utility (DBFUMIN0). Rerun the reload job. End of change

-----------------
HFPV3067E BASE PART COULD NOT BE PRELOADED.
        - IC BUFFER IS OVER THE LIMIT
        - AREA NO: nnnnn, AREANAME: areaname

Explanation: IC buffer exceeded the data space storage for the RAA BASE, IOVF, SDEP part in the image copy.
System action: The job ends with an abend code of U3003.
User response: Start of changeIf the job is run with ICINCOMP=NO keyword, rerun the job with the ICINCOMP=YES keyword. If ICINCOMP=YES keyword is specified, the image copy cannot be processed as the input data set except for the Analyze function and the Tune function. For the Analyze function or the Tune function, if this problem persists, rerun the job with the ICACHE=NO keyword. End of change
-----------------
In the following message, the quotation mark at the end has been removed:

HFPV3055E "PGSER" MACRO FAILED. (RC: xx) Start of change ' End of change



Update 29
Date of change: December 2013
Change description: Documentation changes by APAR PI07604. This APAR updates the explanation of message FPX0061E.
Topic:
> Part 7. Troubleshooting
>> 7.1. Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.6 FPX messages

The explanation section of the FPX0061E message has been updated as follows:

FPX0061E (One of the texts listed in Explanation)

Explanation: An error was encountered during pointer checking. This message contains one of the following texts describing the error encountered:
  • ...
  • Start of change SDEP CI not marked FULL: End of change
  • ...
  • SDEP segment flagged as IN-DOUBT though it is a logically deleted SDEP segment.
  • Start of changePossible loop in segment twin chain.
  • CIDF/RDF in CI suffix is invalid.
  • CI Type was not RAA/DOVF as expected.
  • CI Type was not IOVF as expected.
  • IOVF CI ownership error.
  • Bad scrap bytes detected in CI.
  • Length goes beyond CI end.
  • Space bytes not zero.
  • Invalid 02/SDEP segment found.
  • Invalid segment length found.
  • Invalid FSEs in CI, checksum error.
  • Unmatched CI process length.
  • IOVF Space Map CI Block ID error.
  • CUSN bit not set in IOVF Space Map CI.
  • Invalid Free Chain pointer in IOVF Space Map CI.
  • Invalid element on free chain in IOVF Space Map CI.
  • Possible loop in free chain in IOVF Space Map CI.
  • CI Allocation information was discrepant between IOVF CI and IOVF Space Map.
  • Free CI marked Allocated in IOVF Space Map CI.
  • Invalid element in IOVF Space Map CI.
  • Orphan free element in IOVF Space Map CI.End of change



Update 28
Date of change: December 2013
Change description: Documentation changes by APAR PI06811. This APAR addresses some issues related to the Analyze function of IMS Fast Path Advanced Tool.
Topics: Changes are made to the following multiple topics.

> 2.0 IMS Fast Path Advanced Tool
>> 2.7 Analyzing a DEDB offline with FPA
>>> 2.7.3 Running the Analyze function
>>>> 2.7.3.1 Preprocess for the Analyze process: Initializing permanent data set

The JCL example has been updated as follows:

Figure. Sample JCL to initialize permanent data set (History data sets)
(Figure 74 in PDF and BookManager formats)

//**************************************************************
//** ALLOCATE AND INITIALIZE HISTORY DATA SET
//**************************************************************
//IDCAMS EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
   DELETE ( HPFP.STAT.HIST  ) NONVSAM
   DELETE ( HPFP.STAT.HIST2 ) NONVSAM
   SET MAXCC = 0
/
//**************************************************************
//** ALLOCATE STATISTICS HISTORY DATA SET
//** ALLOCATE STATISTICS HISTORY2 DATA SET
//**************************************************************
//IEFBR14 EXEC PGM=IEFBR14
//DASDHIO DD   DSN=HPFP.STAT.HIST,DISP=(NEW,CATLG,CATLG),
//             DCB=(DSORG=PS,RECFM=FB,LRECL=100,BLKSIZE=800),
//             UNIT=SYSDA,SPACE=(CYL,(2,2),RLSE)
//DASDHIO2 DD  DSN=HPFP.STAT.HIST2,DISP=(NEW,CATLG,CATLG),
//             DCB=(DSORG=PS,RECFM=FB,LRECL=200,BLKSIZE=1600),
//             UNIT=SYSDA,SPACE=(CYL,(4,4),RLSE)

-----------------
>>> 2.7.5 DD statements for the Analyze process

The contents of following table, HFPAPARM keywords, have been updated as follows:

Table. HFPAPARM keywords
(Table 32 in PDF and BookManager formats)
Keyword Description
... ...
RBASEFS Start of changeThis keyword is an optional keyword. If a RAP CI contains free space that is greater than or equal to the percentage specified, and the RAP CI also uses overflow CIs, a reorganization control statement is generated for the UOW, and the UOW is included in the UOW Exception report.
The default is 100%. The maximum value is 99, and the minimum value is 0.End of change
RDOVFFS Start of changeThis keyword is an optional keyword. If the DOVF part of a UOW contains free space that is greater than or equal to the percentage specified, and the UOW also uses IOVF CIs, a reorganization control statement is generated for the UOW and the UOW is included in the UOW Exception report.
The default is 100%. The maximum value is 99, and the minimum value is 0.End of change
... ...
UDOVFFS Start of changeThis keyword is an optional keyword. If the DOVF UOW contains free space that is less than or equal to the percentage specified, the UOW is included in the UOW Exception report.
The default is 0%. The maximum value is 99, and the minimum value is 0.End of change

-----------------
>> 2.12 Sample reports of FPA
>> 2.12.17 UOW Exception report

Description has been updated as follows:

Start of changeThe UOW Exception report contains the analysis information of the UOW that satisfies the criteria specified by the HFPAPARM keywords. End of change

Start of changeEntries are written to this report when one or more of the reporting criteria are met. These reporting criteria are controlled by the keywords that you specify on the HFPAPARM DD statement. End of change
  • > nn% free space in a RAP CI and overflow CIs are used. Use the RBASEFS keyword to specify this parameter.
  • > nn% free space in DOVF and the UOW uses IOVF CIs. Use the RDOVFFS keyword to specify this parameter.
  • < nn% free space in the DOVF part of a UOW. Use the UDOVFFS keyword to specify this parameter.

The UOW Exception report can be used to:
  • List detailed information about each UOW
  • Identify which UOWs require reorganization
  • Manage space utilization when the randomizer has been modified to group related data into contiguous UOWs
  • List only those UOWs that violate the user-specified space utilization criteria

Start of changeThis report is generated by the following commands and by the HFPAPARM reporting criteria: End of change
  • ANALYZE with the REPORT subcommand and the PTRCHKLVL=FULL or the PTRCHKLVL=QUICK keyword
  • CHANGE with the REPORT subcommand and the PTRCHKLVL=FULL or the PTRCHKLVL=QUICK keyword
  • RELOAD with the REPORT subcommand and the PTRCHKLVL=FULL or the PTRCHKLVL=QUICK keyword
  • REORG with the REPORT subcommand and the PTRCHKLVL=FULL or the PTRCHKLVL=QUICK keyword

For information about the HFPAPARM DD statement, see the description about the DD statement in the following topics:
  • "DD statements for the Analyze process" in topic 2.7.5
  • "DD statements for the Change process" in topic 2.5.5
  • "DD statements for the Reload process" in topic 2.4.5
  • "DD statements for the Reorg process" in topic 2.6.6

Start of changeThe following figure is an example of the UOW Exception report when PTRCHKLVL=FULL and the reporting criteria are specified on the HFPAPARM DD statement. End of change

-----------------
>>> 2.12.29 Sensor Data Statistics report

The header of the SYNONYM CHAIN LENGTH STATISTICS sections in the Sensor Data Statistics reports has been changed as follows:

Before change:

    ==============================================
       SYNONYM CHAIN LENGTH STATISTICS
    ==============================================

After change:

    ==============================================
       RANDOMIZING STATISTICS
    ==============================================

(In PDF and BookManager formats, figures 180 to 189.)



Update 27
Date of change: December 2013
Change description: User's guide update.
Topic:
> 3.0 IMS Fast Path Basic Tools
>> 3.4 Unloading a DEDB offline with FPB
>>> 3.4.8 Input for DEDB Unload
>>>> 3.4.8.2 Control statements

Description of DBDNAME SDEP=LOGICAL has been updated as follows:

DBDNAME control statement
    SDEP=
    This optional keyword specifies whether or not to unload SDEP segments.
      NO
        Specifies that SDEP segments are not unloaded. This is the default value.
      LOGICAL
        Specifies that SDEP segments are being unloaded in logical order. The valid SDEP segments are extracted during the unload process. They will be inserted into the new database during the reload process and will retain their logical order (entry sequence) within each database record.
        Start of changeYou must run the DFSORT job before you reload the segments with the DEDB Reload job. End of change




Update 26
Date of change: November 2013
Change description: Documentation changes by APAR PM94821. This APAR adds a new parameter for the OLRECL keyword of IMS Fast Path Online Tools (FPO). When this parameter is specified, FPO determines the LRECL value of FPXOFILE based on the following factors:
  • The maximum segment length defined in the DBD.
  • The SEG keyword on the OUTPUT statement, the FIELDS keyword on the OUTPUT statement, or both.
Topics: Changes are made to the following multiple topics.

> 4.0 IMS Fast Path Online Tools
>> 4.7 Keyword reference for FPO
>>> 4.7.3 FPO keywords
>>>> 4.7.3.52 OLRECL

New parameter, SEGMENT, has been added to the OLRECL keyword as follows:

Start of changeSEGMENT
    The LRECL of FPXOFILE is determined based on the following factors:
    • The maximum segment length defined in the DBD.
    • The SEG keyword on the OUTPUT statement, the FIELDS keyword on the OUTPUT statement, or both.End of change

The following item has been added to the list of restrictions:
  • Start of changeOLRECL=SEGMENT is internally changed to OLRECL=BLOCK when OUTPUT=TFMT, OUTPUT=UR, or OUTPUT=USER is specified.End of change

=================
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.6 FPX messages

The following message has been added:

Start of change
FPX0337I OLRECL=SEGMENT is ignored because OUTPUT= parameter was specified.

Explanation: ODE supports OLRECL=SEGMENT only when STD or DBT format is specified.
System action: Processing continues.
User response: None. This message is informational.
End of change



Update 25
Date of change: November 2013
Change description: Documentation changes by APAR PM96394. By applying this APAR, you can specify the new parameter, IMSID=, on the EXEC statement of certain FPA jobs (Unload, Reload, Change, Analyze, and Build Index) to provide IMS ID to the randomizer.
Topics: Changes are made to the following multiple topics.

> 2.0 IMS Fast Path Advanced Tool
>> 2.1 Overview of IMS Fast Path Advanced Tool
>>> 2.1.4 Restriction of FPA

The following description has been added:

...
When a randomizer is invoked by IMS, register 10 contains the addresses of the EPST, and register 11 contains the addresses of the ESCD. Some user-written or user-customized randomizers are designed to use these addresses to gain access to IMS control blocks other than those passed as part of the published interface. To show that the call is not being issued in an IMS online environment, when one of the IMS Fast Path Advanced Tool functions issues a call to a randomizing module, register 10 is set to -1 and register 11 is set to 0.

Start of changeHowever, if the IMSID parameter is specified on the EXEC statement, FPA generates the buffers for temporary ESCD and SCD. Register 11 contains the address of the temporary ESCD when FPA issues a call to a randomizing module. FPA sets only the ESCDSCD field, which contains the address of SCD, in the temporary ESCD. Also, FPA sets only the SSCDIMID field, which contains the IMS subsystem ID, in the temporary SCD. Other fields of temporary ESCD and temporary SCD cannot be referred to. End of change

-----------------
>>> 2.3.3 Running the Unload function
>>> 2.4.3 Running the Reload function
>>> 2.5.3 Running the Change function
>>> 2.7.3 Running the Analyze function
>>> 2.10.3 Running the Build Index function

New EXEC parameter, IMSID, has been added as follows:

Procedure

1. Estimate the region size required to run the function.
2. Specify the EXEC statement in the following format:


// cmd_name  EXEC PGM=HFPMAIN0,REGION= rrrr M,
//         PARM='DBRCGRP= dbrcgrp ,GSGNAME= gsgname ,IMSPLEX= imsplex ,
//               IMSID= imsid '  


Parameter Description
... ...
Start of changeIMSID= IMSID is an optional 1- to 8-character parameter that specifies the IMS subsystem identification name.

If specified, FPA generates the buffers for temporary ESCD and SCD. Register 11 contains the address of the temporary ESCD when FPA issues a call to a randomizing module. FPA sets only the ESCDSCD field, which contains the address of SCD, in the temporary ESCD. Also, FPA sets only the SSCDIMID field, which contains the IMS subsystem ID, in the temporary SCD. Other fields of temporary ESCD and temporary SCD cannot be referred to.End of change



Update 24
Date of change: October 2013
Change description: Documentation changes by APAR PM96636. This APAR supports a new keyword, the RCEXLOAD keyword for FPO, which specifies whether to call the return code exit routine FPXRCEX0.
Topics: Changes are made to the following multiple topics.

> 4.0 IMS Fast Path Online Tools
>>> 4.2.8 Utility control statements for OPC
>>> 4.3.9 Utility control statements for ODE
>>> 4.5.7 Utility control statements for OER

RCEXLOAD keyword has been added to the following tables:
  • Table. ANALYZE statement keywords (Table 101 in PDF and BookManager formats)
  • Table. EXTRACT statement keywords (Table 106 in PDF and BookManager formats)
  • Table. REORG statement keywords (Table 121 in PDF and BookManager formats)
    Keyword Description
    ... ...
    Start of changeRCEXLOAD Specifies whether to call the return code exit routine FPXRCEX0 from the STEPLIB or JOBLIB data set concatenation.End of change

-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.2 FPO control statements
>>>> 4.7.2.1 ANALYZE
>>>> 4.7.2.10 REORG

RCEXLOAD keyword has been added to the list of Related keywords and to the syntax diagram.

-----------------
>>>> 4.7.2.4 EXTRACT
  • RCEXLOAD and PROC_AFT_ERROR keyword have been added to the list of Related keywords and to the syntax diagram.
  • The following sentence has been deleted:
      The keyword associated with the EXTRACT command is not available for site default options.

-----------------
>>> 4.7.3 FPO keywords

The following new topic has been added:
Start of change
RCEXLOAD

The RCEXLOAD keyword specifies whether to call the return code exit routine FPXRCEX0 from the STEPLIB or JOBLIB data set concatenation.

The RCEXLOAD keyword is an optional keyword for the following statements:
  • ANALYZE statement of OPC
  • EXTRACT statement of ODE
  • REORG statement of OER

Format:

 >>--- RCEXLOAD= --+-- YES --+------><      
                   |         |    
                   +-- NO  --+  

    The variable fields are defined as follows:

    YES
      FPXRCEX0 is called if it is found in the STEPLIB or JOBLIB data set concatenation.
      You can specify Y rather than YES.

    NO
      FPXRCEX0 is not called.
      You can specify N rather than NO.

Default: YES, if the RCEXLOAD keyword is not specified.

Site default support: Supported.

Restriction: The RCEXLOAD keyword can be specified only in FPXIN.
End of change
-----------------
>> 4.10 Return code user exit routine (FPXRCEX0)

The following change has been made:

Overview of the return code use exit routine
The following list provides the overview of the return code user exit routine:
  • This user exit routine must be named FPXRCEX0, and should be included in STEPLIB or JOBLIB.
  • If FPXRCEX0 is found by OPC, ODE, or OER, Start of changeand RCEXLOAD=NO is not specified,End of change it will be called no matter what the return code is.
  • ...



Update 23
Date of change: October 2013
Change description: User's guide update.
Topic:
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.12 HFPF messages

The following message has been modified:

HFPF3361E ESDS DATA SET FOR AREANAME: areaname HAS NO ENOUGH SPACE.
HI-ALLOCATED RBA: xxxxxxxx, SDEP FIRST CI RBA: xxxxxxxx

Explanation: Start of changeThe ESDS data set for the indicated area does not have enough space. The HFPMAIN0 program detected one of the following errors:
  1. High-allocated RBA of the ESDS data set is smaller than the ending RBA of the last CI in REORG UOW (the first CI RBA of SDEP) 
  2. Although the database definition was changed in the Unload process, the Reload process is using the original ACBLIB.End of change
System action: The job ends with an abend code of U3003.
User response: Start of changeBased on the size of the area in the database definition, define enough space for the ESDS data set and rerun the job.
If you changed the database definition in the Unload process, you must provide the updated ACBLIB for the Reload process. Ensure that the IMSACB DD statement of the Reload job specifies the updated ACBLIB and rerun the job. End of change




Update 22
Date of change: August 2013
Change description: Documentation change by APAR PM94550. A new message, HFPK3215E, has been added.
Topic:
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.17 HFPK messages

The following message has been added:

Start of change
HFPK3215E USR RAP RBA ISN'T RAP CI RBA IN AREA NO: nnnn, AREANAME: xxxxxxxx RBA: nnnnnnnn

Explanation: Program HFPMAIN0 found that the RAP RBA in the prefix of the unloaded segment record is not an RBA of a RAP CI.
System action: The job ends with an abend code of 3215.
User response: Check whether the combination of the DEDB definition that is obtained from the IMSACB DD and the unloaded segment record file is correct. Correct the error and rerun the job.
End of change


Update 21
Date of change: June 2013
Change description: Documentation change by APAR PM89915. The Explanation section of the FPX0110I message has been updated.
Topic:
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.6 FPX messages

The Explanation section of the FPX0110I message has been updated as follows:

FPX0110I CI formatted by Create Utility was encountered, CI was skipped. RBA of CI: nnnnnnnn

Explanation: A control interval that contains dummy data formatted by the DEDB Area Data Set Create Utility was encountered, but it was not processed. The dummy data CI that is specified by the subsystem ID "CREATFMT" is in the subsystem name filed in the SDEP CI prefix, and the CI was formatted during the copy phase of the DEDB Area Data Set Create Utility.
This CI implies that it was preallocated and will be overlaid by either of the following SDEP CI images:
  • SDEP CI image that contains real SDEP segments
  • Start of changeSDEP preallocated dummy CI image that contains the CIs that were expanded by Online Area Extender(OAE) SDEP expansion. End of change
System action: Processing continues, but the "CREATFMT" dummy CI will be skipped on this run.
User response: This message is informational.



Update 20
Date of change: May 2013
Change description: Documentation changes by APAR PM73630. This APAR introduces a new keyword, SEGLDIST, for FPA and FPO for generating the Segment Length Distribution report.
Topics: Changes are made to the following multiple topics.

> 2.0 IMS Fast Path Advanced Tool
>> 2.11 Command reference for FPA
>>> 2.11.4 FPA keywords

The following new topic has been added:

Start of change
SEGLDIST

Use the SEGLDIST keyword to specify whether to generate the Segment Length Distribution report.

SEGLDIST is an optional keyword for the REPORT subcommand.

Related keywords: None.

Format:
    SEGLDIST= parameter

    parameter
      parameter can be one of the following values:
      YES
        Prints the Segment Length Distribution report.
        SEGLDIST=YES is effective only when PTRCHKLVL=FULL is specified.

      NO
        Do not print the Segment Length Distribution report.

Default: SEGLDIST=NO

Site default support: Supported.
End of change
-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.14 DEDB Area Analysis reports
>>>> 2.12.14.2 DB Record Profile Analysis report

The "DB Record Profile Analysis report" figure has been replaced with the following figure. Also the title has been changed to "DB Record Profile Analysis report with SEGLSTAT=DETAILED and SEGLDIST=YES".

(This figure replaces the figure provided in the Update 9 section of this techdoc.)

Start of changeFigure. DB Record Profile Analysis report with SEGLSTAT=DETAILED and SEGLDIST=YES
(Figure 154 in PDF and BookManager formats)

End of change

The following description has been added:

SEGNAME
    Shows the name of the segment as defined in the DBD.

    Start of changeAn exclamation point (!) is displayed before the segment name if SEGLDIST=YES is specified and either or both of the following conditions are met:
    • Segment is defined as variable length and its occurrence is not zero.
    • Segment is compressed and its occurrence is not zero.End of change

-----------------
>> 2.12 Sample reports of FPA

The following new topic has been added as the last topic in 2.12.

Start of change
Segment Length Distribution report

The Segment Length Distribution report provides detailed information about each segment. You can use this report to analyze the segments.

The Segment Length Distribution report can be used to:
  • List detailed information about each segment
  • Identify which segment requires tuning

This report is generated by the following commands:
  • FPA ANALYZE with the REPORT subcommand and the PTRCHKLVL=FULL
  • FPA CHANGE with the REPORT subcommand and the PTRCHKLVL=FULL
  • FPA RELOAD with the REPORT subcommand and the PTRCHKLVL=FULL
  • FPA REORG with the REPORT subcommand and the PTRCHKLVL=FULL

The following figure shows an example of the Segment Length Distribution report.


Figure x. Segment Length Distribution report

CI SIZE
    The CI size of the area.

SEGMENT LENGTH
    The average length of the segments (AVG), the length of the longest segment (MAX), and length of the shortest segment (MIN).
SC
    Segment code.

SEGMENT NAME
    Segment name, as coded on the SEGM macro in the DBD.

SIZE RANGE
    The size (in bytes) range of the part of the variable-length segment to be reported. For compressed segment, the length after compression is used for the size. The shortest and the longest sizes are actual values detected in the database, not extracted from the DBD. This report divides the size range into 20. If the segment length is distributed within a certain narrow range, the size range might become less than 20 or the size range might not be fixed.

OCCURRENCES
    The number of occurrences that are included in this range.

PCT OF NUMBER OF SEGMENTS
    The percentage of occurrences of this range, and what percentage it makes of the total.

CUM. PCT FROM SHORTEST
    The cumulative value of PERCENTAGE.

SIZE RANGES THAT AVG, MAX, MIN, MED, AND 1ST/3RD QUARTILES EXISTED
    Data flag of segments is as follows:
      AVG:
        Size range in which the average segment length lies.
      MAX:
        Size range in which the maximum segment length lies.
      MIX:
        Size range in which the minimum segment length lies.
      MED:
        Size range in which the median of segment length lies.
      1ST QUARTILE:
        Size range in which the top quartile of segment lies.
      3RD QUARTILE:
        Size range in which the lower quartile of segment lies.

TOTALS
    The minimum length, maximum length, and occurrences of the segment.

MORE THAN 90 PERCENT OF SEGMENT OCCURRENCES ARE INCLUDED IN THE RANGE xxx - xxx.
    This field shows the range that contains more than 90% of segment occurrences. This field is based on a more specific range that includes the average segment length.
End of change
=================
> 4.0 IMS Fast Path Online Tools
>> 4.7 Keyword reference for FPO
>>> 4.7.3 FPO keywords

The following new topic has been added:

Start of change
SEGLDIST

Use the SEGLDIST keyword to specify whether to generate the Segment Length Distribution report.

SEGLDIST is an optional keyword for the REPORT statement:

Related keyword: None.

Format:
    SEGLDIST= parameter

    parameter
      parameter can be one of the following values:
      YES
        Prints the Segment Length Distribution report. You can specify just Y rather than YES.
        SEGLDIST=YES is effective only when TYPRUN=RPT and FULLSTEP=YES are specified. For OER, PTRCHK=YES and CHKUOW=ALL are also required.

      NO
        Do not print the Segment Length Distribution report. You can specify just N rather than NO.

Default: SEGLDIST=NO

Site default support: Supported.
End of change



Update 19
Date of change: May 2013
Change description: Documentation changes by APAR PM83156. By applying this APAR, you can extend the image copies of the DEDB area during DEDB area expansion with the Online Area Extender (OAE) utility of Fast Path Online Tools (FPO). The extended image copies can be used to recover the extended DEDB area.
Topics:
Changes are made to the following multiple topics.

> 4.0 IMS Fast Path Online Tools
>> 4.4 Extending a DEDB online with FPO
>>> 4.4.1 Functions of OAE

The following paragraph has been added to the end of the topic:


Start of changeWhen you extend only the SDEP portion of the DEDB area, you can optionally extend the image copy data sets in the same job step. This option is called the image copy expansion option. To use this option, the image copy data set must be created before the OAE job and it must be registered in the RECON data sets. By having OAE extend the image copy data sets, the area that is extended by OAE can be recovered by using the extended image copy data sets. Shadow expansion and original expansion both support this option. This option can be requested by the ICEXTEND keyword in SYSIN DD for shadow expansion, and ICEXTEND=YES in FPXIN DD for original expansion. End of change

-----------------
>>> 4.4.3 Input and output for OAE

The following two figures have been updated as follows:


Figure. Input and output for OAE--Original expansion
(Figure 303 in PDF and BookManager formats)


Figure 304. Input and output for OAE--Shadow expansion
(Figure 304 in PDF and BookManager formats)


-----------------
>> 4.4 Extending a DEDB online with FPO
>>> 4.4.4 Considerations for running OAE

The following new topic has been added after 4.4.4.2 "Considerations on running OAE":


Start of change
Considerations on image copy expansion

OAE can extend both the DEDB area and the image copies of the area in a single job step. OAE extends the size of the image copy data sets that are created before the area expansion by inserting dummy SDEP CIs in the extended portion. By extending the image copies, you can later use the extended image copies to recover the DEDB area.

To extend the image copy data set, the following conditions must be met:
  • The image copy must be registered in the RECON data sets
  • The DD statements that specify the target extended image copy data sets must be coded in the JCL stream
  • Only the SDEP portion of the area is extended

OAE can extend the primary image copy, the secondary image copy, or both.

Review the following considerations before you extend image copies with OAE:
  • OAE extends the latest image copy data set that is registered in the RECON data sets. If the image copy data set is written on a tape volume, OAE requests you to mount the tape volume.
  • OAE can extend the image copy that is compressed with compression routine FABJCMPx, which is provided by IMS HP Image Copy.
  • OAE cannot extend an IC2 image copy that is created by the IMS Database Image Copy 2 Utility (DFSUDMT0). Also, OAE cannot extend an image copy that is created by the flash copy process.
  • For shadow expansion, if the size of the target area data set is the same as the size of the original area data set, image copy data sets of the area can be used for recovery without having them extended. Therefore, when the size is the same, OAE does not extend the image copy data set.
  • If both the primary image copy and the secondary image copy are registered in the RECON data sets and if OAE extends only one of them due to an error, OAE invalidates the image copy that is not extended in the RECON data sets to ensure the consistency.
End of change
-----------------
>>>> 4.4.4.3 Considerations on recovery and restart

Descriptions have been updated as follows:


Recovery


Start of change Once the utility is successfully run, the DEDB area is expanded, and it cannot be undone. In other words, once the area is expanded, you cannot go back to a smaller area.

Warning:
In view of the irrevocability of the utility, proceed with caution. Consider using the TEST keyword, which verifies the correctness of your parameters and shows you the structure of the new area--without actually performing the expansion. End of change

As part of updating the IMS control blocks (DMAC) with the new AREA structure information, all datasharing IMS subsystems are notified by OAE of the AREA structure change. If this notify process fails, the AREA is marked recovery needed, and all ADS(s) are stopped. The AREA can then be recovered, but only into a data set at least as large as the input ADS. After recovery, the AREA will be partially expanded, and the utility must be restarted to complete the process from the point of failure.

Start of changeIf OAE extended the image copy that is taken prior to OAE along with the DEDB area, you can use that extended image copy to recover the extended DEDB area.

One of the recovery methods is to recover the DEDB area by using the extended image copy data set with the point-in-time recovery (PITR) of IMS Database Recovery Facility. When you do so, be careful about the time you specify for recovery. If you specify a recovery time that is after the OAE run, the extended DEDB area recovers completely. However, if you specify a recovery time that is earlier than the OAE run, the recovered DEDB area will have the size of the extended DEDB area (because the extended image copy is used for recovery), but the DMAC information will be that of before the OAE run because the log updates during the OAE job are not applied. In this case, if you want to resize the recovered DEDB area to the size before the OAE run, use the DEDB Area Data Set Create utility (DBFUMRI0) to copy the recovered DEDB area data set to a smaller data set. End of change

Restart

If the utility ends prematurely, simply restart the utility by using the same input and the following parameters:
  • Start of changeFor shadow expansion, specify the RESTART parameter on the EXIT statement on the SYSIN DD.
  • For original expansion, specify the RUNTYPE=RESTART keyword on the EXTEND statement on the FPXIN DD.End of change
The area is accessible to the online environment until OAE is restarted.

Start of changeImportant: OAE cannot extend the image copies in the restart process. When restart processing ends, create an image copy of the extended area as soon as possible. End of change

-----------------
>>> 4.4.5 Running OAE
>>>> 4.4.5.2 Step 2: Coding and running JCL

The region size requirement has been updated as follows:


2. Use the REGION= parameter on either the JOB or the EXEC statement to specify the region size.
    Region size varies with:
    • UOW size (CI number x CI size)
    • CI size
    • (CI number x CI size) for the rest of the buffer after IOVF in case of SDEP

      If there is no SDEP portion in the DBD source definition of an area, OAE acquires (GETMAIN) buffers after IOVF, up to the high allocated RBA. Specify the region size big enough to contain the buffer acquired.

    Start of changeThe required region size increases when you extend image copy data sets along with the DEDB area:
    • For shadow expansion, additional 11 M is required
    • For original expansion, additional 7 M is requiredEnd of change

-----------------
>>>> 4.4.5.4 Recovering and restarting OAE
>>>>> 4.4.5.4.1 When the shadow or the original expansion fails

The Procedure section has been updated as follows:

Start of change
Procedure

If one of following messages is issued in the OAE restart processing, follow the description:
  • FPX0091E OAE restart not processed. Follow the RESTART procedure in the OAE User's Guide.

      1. Check the status of the original ADS in DBRC.
          • If the original ADS is in AVAIL status in DBRC,
              a. Check the status of the temporary ADS in DBRC.
                • If the temporary ADS is in AVAIL status, then complete the following steps:
                    i. Separate the temporary ADS from the IMS online system by using the /STOP ADS command.
                    ii. Unregister the temporary ADS with DBRC.
                • If the temporary ADS is in UNAVAIL status in DBRC, then unregister the temporary ADS with DBRC.
                • If the temporary ADS is not registered with DBRC, do nothing with DBRC.
              b. If DELETE is not specified on the DSNAME keyword, delete the temporary ADS cluster if exists.
          • If the original ADS is in UNAVAIL status in DBRC, then complete the following steps:
              a. Run the DEDB Area Data Set Create utility (DBFUMRI0) by specifying the DD name of the original ADS.
              b. Separate the temporary ADS from the IMS online system by using the /STOP ADS command.
              c. Unregister the temporary ADS with DBRC.
              d. If DELETE is not specified on the DSNAME keyword, delete the temporary ADS cluster if exists.

        2. If ICEXTEND=YES is specified, delete and redefine the target extended image copy data sets that are specified as DISP=NEW on FPXBIC01 DD, FPXBIC02 DD, or both.

        3. Rerun OAE without the RUNTYPE=RESTART option.

  • FPX0292E OAE restart is not required. Remove the RESTART parameter from the EXTEND statement.

      1. If ICEXTEND is specified, delete and redefine the target extended image copy data sets that are specified as DISP=NEW on FPXBIC01 DD, FPXBIC02 DD, or both.

      2. Rerun OAE without the RESTART option.

  • FPX0136W The OAE RESTART process extended the temporary ADS. It did not copy the temporary ADS back to the original ADS.

      1. If the extended temporary ADS is used instead of the original ADS, do nothing.

      2. Identify the original ADSs from the subtexts of message FPX0136W.

      3. Redefine the original ADS clusters if they do not exist.

      4. Run the DEDB Area Data Set Create utility (DBFUMRI0) by specifying the DD names of the original ADSs.

      5. Separate the temporary ADS from the IMS online system by using the /STOP ADS command.

      6. Unregister the temporary ADS with DBRC.

      7. Delete the temporary ADS cluster.

  • DFS3736A VALIDATION CALL FAILED FOR AREA=areaname DD=ddname CODE=xx

      1. Check the status of the original ADS in DBRC.

      2. If the original ADS is in AVAIL status in DBRC, separate the target ADS from the IMS online system by using the /STOP ADS command.

      3. If the original ADS is in UNAVAIL status in DBRC, then complete the following steps:
          a. Run the DEDB Area Data Set Create utility (DBFUMRI0) by specifying the DD name of the original ADS.
          b. Separate the target ADS from the IMS online system by using the /STOP ADS command.

      4. If ICEXTEND=YES is specified, delete and redefine the target extended image copy data sets that are specified as DISP=NEW on FPXBIC01 DD, FPXBIC02 DD, or both.

      5. Rerun OAE without the RESTART option.
End of change
-----------------
>>> 4.4.6 Region size considerations for OAE

This topic has been updated as follows:


Start of change
The region size for OAE depends on the size of a UOW.

Because OAE operates in a virtual storage region as an IMS IFP utility, the actual region size required to run OAE is higher than the following values.

OAE requires the buffer set and IOVF work buffer calculated by the following formulas:


     Buffer Set:       UOW1 x CISZ x 2
     IOVF Work Buffer: CISZ x 125


The region size required by OAE also depends on whether the image copy expansion option is used (ICEXTEND keyword). The required region size increases when you extend image copy data sets along with the DEDB area:
  • For shadow expansion, additional 11 M is required
  • For original expansion, additional 7 M is required
End of change
-----------------
>>> 4.4.7 DD statements for OAE

RECONn, FPXBIC01, FPXBIC02 DD statements have been added as follows:


Table. OAE DD statements
(Table 111 in PDF and BookManager formats)
DDNAME Use Format Required or optional
... ... ... ...
ACBLIB ... ... ...
Start of changeRECONn Input/Output OptionalEnd of change
... ... ... ...
FPXBINTP ... ... ...
Start of changeFPXBIC01 Output PS OptionalEnd of change
Start of changeFPXBIC02 Output PS OptionalEnd of change


The following descriptions have been updated:


STEPLIB DD
    Describes the library that contains the OAE utility. The data set that contains the DBRC SCI registration exit routine (DSPSCIX0) must be concatenated when using the RECON data set, in which an IMSplex name is set.

    Start of changeIf the image copy expansion option is specified, and the image copy data set to be extended is compressed with the compression routine FABJCMPx, which is provided by IMS HP image copy, the load library of IMS HP Image Copy must be concatenated. End of change

SYSPRINT DD
    Describes the data set that contains output messages.

    Start of changeWarning: You cannot allocate the OAE SYSPRINT DD output stream to a data set because SYSPRINT DD is also used by IMS. If you specify SYSPRINT DD as a data set, some output might be overridden or unpredictable open/close errors might occur. You must specify SYSPRINT DD as SYSOUT. End of change

Description of the RECONn, FPXBIC01, FPXBIC02 DD statements have been added as follows:


Start of change
RECON n DD
    Defines the DBRC RECON data sets. They are required when the original expansion or image copy expansion is requested. The RECONn data sets must be the same data sets as those used by the IMS control region because OAE refers to and updates the records in the RECON data sets.

    If these statements are not specified in the JCL statement when the data sets are necessary, the data sets are allocated dynamically by using a DFSMDA member.
End of change

Start of change
FPXBIC01 DD/FPXBIC02 DD
    Defines the target extended image copy data sets when the image copy expansion option is specified. The extended image copy data sets can be used to recover the extended DEDB area.

    FPXBIC01 DD is used to extend the latest primary image copy data set that is registered in the RECON data sets, and FPXBIC02 DD is used to extend the latest secondary image copy data set that is registered in the RECON data sets. After extending the image copies, OAE modifies the last image record in the RECON data sets to replace the information of the original image copy with the information of the extended image copy.

    If you want OAE to perform both area expansion and image copy expansion, you must specify the FPXBIC01 DD, the FPXBIC02 DD, or both statements, in the JCL stream. Do not code the DCB information in the JCL statement. You must not specify DISP=MOD for these DD statements.
    Considerations:
    • If both FPXBIC01 DD and FPXBIC02 DD are not specified in the JCL stream, OAE does not extend the image copies even if the primary image copy and the secondary image copy are registered in the RECON data sets. When only one of the target extended image copy data sets is specified correctly, OAE extends the DEDB area, extends the image copy that is specified by the correct FPXBIC0x DD, and invalidates the other image copy (that is, either the primary image copy or the secondary image copy) in the RECON data sets.
    • If both FPXBIC01 DD and FPXBIC02 DD are specified as DUMMY or NULLFILE, OAE does not extend the image copies. If only one of the FPXBIC0x DDs is specified correctly and the other specifies DUMMY or NULLFILE, OAE extends the DEDB area, extends the image copy that is specified by the valid FPXBIC0x DD, and invalidates the other image copy in the RECON data sets.
    • The target extended image copy data sets must not be stacked data sets.
    • FPXBIC01 DD and FPXBIC02 DD must specify different data sets.
    • The data set names of the original image copy data and the target extended image copy must be different.
    • The data set names can contain a reference to a generation data group (GDG), with or without a relative generation number such as "(+1)".
End of change

-----------------
>>> 4.4.9 Utility control statements for OAE
>>>> 4.4.9.1 SYSIN DD data set (Shadow expansion)

ICEXTEND and ICERR_CONT keywords have been added to the following table:


Table. Control commands for the SYSIN data set
(Table 113 in PDF and BookManager formats)
Command name Description
... ...
EXIT ...

Start of changeICEXTEND
    Specifies whether to extend the latest image copy data set that is registered in the RECON data sets, along with the DEDB area.

    Restriction: IOVF and ICEXTEND are mutually exclusive.

ICERR_CONT
    Specifies whether to continue extending the DEDB area when image copy expansion fails.

    This keyword is valid only when ICEXTEND is specified.
End of change
...
... ...


-----------------
>>>> 4.4.9.2 FPXIN DD data set (Original expansion)

ICEXTEND and ICERR_CONT keywords have been added to the following table:


Table. EXTEND statement keywords
(Table 115 in PDF and BookManager formats)
Keyword Description
... ...
Start of changeICEXTEND An optional keyword that is used to specify whether to extend the latest image copy data set that is registered in the RECON data sets, along with the DEDB area.End of change
Start of changeICERR_CONT An optional keyword that is used to specify whether to continue extending the DEDB area when image copy expansion fails.End of change
... ...


-----------------
>>> 4.4.10 Output for OAE
>>>> 4.4.10.1 SYSPRINT DD data set

The following examples are added to the end of the topic:


Start of changeIf image copies are extended along with DEDB area expansion, the following additional information is printed in the SYSPRINT data set.
  • The following figure shows the original last image record, which is the last image record in the RECON data sets before OAE extends the latest image copy data set.
  • The following figure shows the extended last image record, which is the last image record in the RECON data sets after OAE extended the latest image copy data set.

  • The following figure shows the CHANGE.IC command list. These commands were issued to update the last image record in the RECON data sets after OAE extended the latest image copy data set.

End of change

-----------------
>> 4.4.10 Output for OAE

The following new topic has been added after 4.4.10.1 "SYSPRINT DD data set":


Start of change
FPXBIC01 and FPXBIC02 DD data sets

The FPXBIC01 and FPXBIC02 DD data sets contain the image copy data that is extended by OAE. This data can be used to recover the DEDB area extended by OAE.

These data sets are produced only when the image copy expansion option is specified.
End of change
-----------------
>>> 4.4.12 Examples for OAE
>>>> 4.4.12.1 Examples for the original expansion

The following example has been added:


Start of change
Example 7: Extending the SDEP portion of the area and the latest image copy data sets

The following figure shows example JCL to extend the SDEP portion of the area. At the same time, OAE extends the latest image copy data sets that are registered in the RECON data sets.



//EXTEND EXEC FPUTIL,DBD=DEDBJN21,IMSID=imsid
//*                
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//         DD DISP=SHR,DSN=HPS.SHPSLMD0 <--- Edit/comp rtn
//SYSOUT   DD SYSOUT=*,FREE=END  
//SYSPRINT DD SYSOUT=*,FREE=END  
//ACBLIB   DD DISP=SHR,DSN=IMSVS.ACBLIB(DEDBJN21)
//FPXBIC01 DD DISP=SHR,DSN=HPFP.DB21AR1.IC1(+1)
//FPXBIC02 DD DISP=SHR,DSN=HPFP.DB21AR1.IC2(+1)
//FPXIN DD *
*
*   EXTEND parameter
*
  EXTEND
  AREA=DB21AR1
  SDEP_CI=600
  ICEXTEND=YES
  DDNAME=DBOAETMP
  DSNAME=IMSVS.USER.DB21AR1
  DATACLAS=SMSTMP
/*
//RECON1 DD DISP=SHR,DSN=IMSVS.RECON1
//RECON2 DD DISP=SHR,DSN=IMSVS.RECON2
//RECON3 DD DISP=SHR,DSN=IMSVS.RECON3

Figure xxx. Extending the SDEP portion of the area and the latest image copy data sets (original expansion)
End of change
-----------------
>>> 4.4.12 Examples for OAE
>>>> 4.4.12.2 Examples for the shadow expansion

The following example has been added:


Start of change
Example 2: Extending the SDEP portion of the area and the latest image copy data sets

The following figure shows example JCL to extend the SDEP portion of the area. At the same time, OAE extends the latest image copy data sets that are registered in the RECON data sets.

//EXTEND EXEC FPUTIL,DBD=DEDBJN21,IMSID=imsid
//*                
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//         DD DISP=SHR,DSN=HPS.SHPSLMD0 <--- Edit/comp rtn
//SYSOUT   DD SYSOUT=*,FREE=END        
//SYSPRINT DD SYSOUT=*,FREE=END              
//ACBLIB   DD DISP=SHR,DSN=IMSVS.ACBLIB(DEDBJN21)
//FPXBIC01 DD DISP=SHR,DSN=HPFP.DB21AR1.IC1(+1)
//FPXBIC02 DD DISP=SHR,DSN=HPFP.DB21AR1.IC2(+1)
//*                 <-- START SYSIN STREAM
//*                 (OAE UTILITY CONTROL STATEMENTS)
//SYSIN    DD *
*                    
TYPE TOOL
*                    
AREA DB21AR1
*                
DDNAME DB21AR13
DDNAME DB21AR14
*                    
EXIT EXTEND SDEP ICEXTEND
*                
GO
/*        
//RECON1 DD DISP=SHR,DSN=IMSVS.RECON1
//RECON2 DD DISP=SHR,DSN=IMSVS.RECON2
//RECON3 DD DISP=SHR,DSN=IMSVS.RECON3

Figure xxx. Extending the SDEP portion of the area and the latest image copy data sets (shadow expansion)
End of change

-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.2 FPO control statements
>>>> 4.7.2.3 EXTEND

ICEXTEND and ICERR_CONT keywords have been added tot he list of related keywords as follows:


Related keywords:
  • ...
  • Start of changeICEXTEND End of change
  • Start of changeICERR_CONT End of change
  • ...

-----------------
>>> 4.7.3 FPO keywords

The following new topics have been added:


Start of change
ICEXTEND

The ICEXTEND keyword activates the image copy expansion option. When this option is activated, OAE extends the image copies during DEDB area expansion. The extended image copy can be used to recover the DEDB area when necessary.

ICEXTEND is an optional keyword for the EXTEND statement of OAE original expansion.

Format:

 >>__ICEXTEND=_____NO____________________________><
                |__YES__|

Variable fields are defined as follows:

NO
    Does not extend the image copy data sets.
    You can specify just N rather than NO.

    Important: The image copy data set that was created before this OAE run cannot be used to recover the extended DEDB area. Create an image copy of the extended DEDB area as soon as the OAE job ends.

YES
    Extends the latest image copy data set that is registered in the RECON data sets. The extended image copy data set can be used to recover the extended DEDB area.
    You can specify just Y rather than YES.

Default:
    NO, if the ICEXTEND keyword is not specified.

Site default:
    Not supported.

Restrictions:
  • ICEXTEND=YES can be specified when OAE extends only the SDEP portion of the DEDB area.
  • When the ICEXTEND=YES keyword is specified in FPXIN DD, you must include either or both of the FPXBIC0x DD statements in the JCL stream.
End of change


Start of change
ICERR_CONT

The ICERR_CONT keyword specifies whether to continue extending the DEDB area when image copy expansion fails.

ICERR_CONT is an optional keyword for the EXTEND statement of OAE original expansion. This keyword is valid only when ICEXTEND is specified.


Format:

>>__ICERR_CONT=_____NO_____________________________><
                 |__YES__|

Variable fields are defined as follows:

NO
    Stops extending the DEDB area when image copy expansion failed.
    You can specify just N rather than NO.

YES
    Continues to extend the DEDB area even when image copy expansion fails.
    You can specify just Y rather than YES.

Default:
    NO, if the ICERR_CONT keyword is not specified.

Site default:
    Not supported.
End of change

=====================
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.6 FPX messages

The following messages have been changed:


FPX0136
E has been changed to FPX0136 W . The message text and explanation have also changed as follows:

Start of change FPX0136E FPX0136W The OAE restart process extended the temporary ADS. It did not copy the temporary ADS back to the original ADS. End of change

Explanation: The OAE restart process extended the temporary ADS, but it did not copy the temporary ADS back to the original ADS. All area data sets except the temporary area data set are unavailable with DBRC. Start of change OAE RESTART cannot identify the original area data set when more than one ADS are in UNAVAIL status, or cannot get necessary information to define the extended original area data set when only one ADS is in UNAVAIL status. End of change
System action: Processing ends with a return code of 4.
User Response: Start of change Delete and define the original area data set(s) by extending the space, and run the DEDB Area Data Set Create Utility to copy the extended original area data set from the temporary one. End of changeSee "Recovering and restarting OAE" for detailed procedure to complete the OAE.

-----------------
FPX0137
W has been changed to FPX0137 I . Explanation has also changed as follows:

Start of change FPX0137W FPX0137I End of change OAE RESTART process determines the original area data set with the DBRC available ADS.

Explanation: Start of changeOAE restart process determines the original area data set from the DBRC. End of change The temporary area data set is reported as one of the available ADSs. FPX0125I and FPX0126I messages will follow this message to tell that the temporary area data set is deleted with DBRC, and the temporary area data set cluster is deleted as a result of the Start of changeOAE restart process. End of change
System action: Processing continues.
User Response: Start of changeNone. End of change

-----------------
The following new messages have been added:


Start of change
FPX0279I DUMMY or NULLFILE or SYSOUT is specified for the ddname DD statement.

Explanation: You cannot specify DUMMY, NULLFILE, or SYSOUT for the indicated DD statement.
System action: Processing continues. OAE does not extend the image copy whose target extended image copy data set is specified as DUMMY, NULLFILE, or SYSOUT, and invalidates the image copy in the RECON data sets.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, check the image copy data set that is registered in the RECON data sets, correct the incompatible error, and rerun the job.
End of change
-----------------
Start of change
FPX0280W Due to errors, no image copy data set was extended.

Explanation: OAE did not extend the image copy due to errors.
System action: If the ICERR_CONT option is in effect, OAE continues to extend the DEDB area. The return code is set to 4 and processing continues. If the ICERR_CONT option is not in effect, OAE stops extending the DEDB area and ends the process with a return code of 8.
User response: Check the preceding messages. Follow the User Response for those messages, and, if necessary, rerun the job.
End of change
-----------------
Start of change
FPX0281W The output data set for the extended image copy is not specified. Specify the ddname DD statement.

Explanation: Even though the image copy is registered in the RECON data sets, the corresponding output data set for the extended image copy is not specified in the JCL stream.
System action: The return code is set to 4 and processing continues. OAE does not extend the image copy whose target extended image copy data set is not specified, and invalidates the image copy in the RECON data sets.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, specify the indicated DD statement in JCL, and rerun the job.
End of change
-----------------
Start of change
FPX0282W The image copy record is not found in RECON.

Explanation: No valid image copy is registered in the RECON data sets.
System action: The return code is set to 4 and processing continues. No image copy data set is extended.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, ensure that valid image copies are registered in the RECON data sets and rerun the job.
End of change
-----------------
Start of change
FPX0283W The image copy data set is incorrect. [IC1 | IC2] DSN= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    - The format is incorrect.
    - The DBD name is incorrect. DBD name: dbd_name
    - The area name is incorrect. AREA name: area_name
    - The CI size is incorrect. CI size: xxxxx
    - An unsupported compression routine is used. Routine: routine_name
    - The timestamps that are recorded in RECON and image copy header record do not match.
    (cont) Primary image copy data set:
    (cont) RECON yyyy/ddd HH:MM:DD thmiju +x
    (cont) IC Header yyyy/ddd HH:MM:DD thmiju +x
    (cont) Secondary image copy data set:
    (cont) RECON yyyy/ddd HH:MM:DD thmiju +x
    (cont) IC Header yyyy/ddd HH:MM:DD thmiju +x

Explanation: The image copy data set that is registered in the RECON data sets cannot be extended. The reason is described in the subtext of this message.
System action: The return code is set to 4 and processing continues. OAE does not extend this image copy data set, and invalidates the image copy in the RECON data sets.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, ensure that valid image copies are registered in the RECON data sets and rerun the job.
End of change
-----------------
Start of change
FPX0283W The image copy data set is incorrect.
    - The numbers of records are different.
    (cont) IC1 DSN= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ( x,xxx,xxx,xxx)
    (cont) IC2 DSN= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ( x,xxx,xxx,xxx)

Explanation: The number of the primary image copy records is different from that of the secondary image copy records.
System action: The return code is set to 4 and processing continues. OAE does not extend the image copy data sets.
User response: If an FPX0287W message is issued, create an image copy of the extended area as soon as possible. If an FPX0328E message is issued, ensure that valid image copies are registered in the RECON data sets and rerun the job.
End of change
-----------------
Start of change
FPX0284I Image copy [IC1|IC2] is not registered in RECON. The following specification is ignored:
    (cont) DDN=FPXBIC0 x DSN= xxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: The indicated FPXBIC0 x DD statement is ignored because the corresponding image copy is not registered in the RECON data sets.
System action: Processing continues.
User response: None.
End of change
-----------------
Start of change
FPX0285W The following error occurred while extending the image copy data set:
    (cont) - The image copy data set that is registered in RECON does not exist. [IC1|IC2] DSN= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    (cont) - Function = typ DD name = ddname MVS RET and RSN codes are: rc + rsn
    (cont) - I/O error. [IC1|IC2|FPXBIC01|FPXBIC02] DSN= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: An error occurred while extending the image copy data set that is registered in the RECON data sets. The reason is described in the subtext of this message.
System action: The return code is set to 4 and processing continues. OAE does not extend this image copy data set, and invalidates the image copy in the RECON data sets.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, correct the invalid specification and rerun the job.
End of change
-----------------
Start of change
FPX0286I OAE invalidated the entry for the following image copy data set in RECON:
    (cont) [IC1|IC2] DSN= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: To keep the consistency, OAE invalided the specified image copy data set in the RECON data sets.
System action: Processing continues.
User response: None.
End of change
-----------------
Start of change
FPX0287W Create an image copy of the extended DEDB area immediately.

Explanation: Although the image copy expansion option is specified, no image copy data set was extended because an error was detected or the RESTART keyword is specified.
Important: Because the image copy that was created before this OAE run cannot be used to recover the extended DEDB area, create an image copy of the extended area as soon as possible.
System action: The return code is set to 4 and processing continues.
User response: Create an image copy of the extended area as soon as possible.
End of change
-----------------
Start of change
FPX0288I OAE extended the image copy data set.

Explanation: The OAE process ended normally. Both the area and the image copy data sets are extended by OAE. The extended area can be recovered by using the extended image copy data set.
System action: Processing continues.
User response: None. This message is informational.
End of change
-----------------
Start of change
FPX0289I Create an image copy of the extended DEDB area immediately.

Explanation: The OAE process ended normally.
Important: Because the image copy that was created before this OAE run cannot be used to recover the extended DEDB area, create an image copy of the extended area as soon as possible.
System action: Processing continues.
User response: Create an image copy of the extended area as soon as possible.
End of change
-----------------
Start of change
FPX0291W The data set names on the FPXBIC01 DD, the FPXBIC02 DD, the IC1 and the IC2 fields in RECON must be different.
    (cont) DSN= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Explanation: OAE detected same data set names. The data set name must be different.
System action: The return code is set to 4 and processing continues. OAE does not extend the corresponding image copy data set, and invalidates the image copy in the RECON data sets.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, correct the invalid specification and rerun the job.
End of change
-----------------
Start of change
FPX0292E OAE restart is not required. Remove the RESTART parameter from the EXTEND statement.

Explanation: Although a prior occurrence of the OAE utility had ended prematurely, OAE can be rerun without the RESTART parameter.
System action: The return code is set to 8.
User response: Remove the RESTART parameter from the EXTEND statement and rerun the job.
End of change
-----------------
Start of change
FPX0293I The xxxxxxxxxxxxxxxxx process ended.

Explanation: The following OAE process ended normally.
  • Initialization
  • Environment setup
  • ADS copy
  • SDEP expansion
  • CSC checking
  • IOVF expansion
  • ADS copy back
  • Termination
System action: Processing continues.
User response: None. This message is informational.
End of change
-----------------
Start of change
FPX0294I OAE replaced the ROOT= parameter value in DMAC (IMS storage) from ( aaaaa, bbbbb) to ( ccccc, fffff).

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.
End of change
-----------------
Start of change
FPX0295W The function function of compression exit routine exit-routine-name failed with RC= nn.

Explanation: The compression exit routine exit-routine-name returned an error return code. function shows the function that failed, which is one of the following functions:
    INITIALIZATION: Initialization processing
    BLOCK WRITE: Block writing processing
    TERMINATION: Termination processing
System action: The return code is set to 4 and processing continues. OAE does not extend the corresponding image copy data set, and invalidates the image copy in the RECON data sets.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, locate the error message from IMS HP Image Copy in the job log, correct the error, and rerun the job.
End of change
-----------------
Start of change
FPX0296W The image copy that is registered in RECON cannot be supported.

Explanation: OAE cannot extend an IC2 image copy that was created by the IMS Database Image Copy 2 Utility (DFSUDMT0). Also, OAE cannot extend an image copy that is created by the flash copy process.
System action: The return code is set to 4 and processing continues. No image copy is extended.
User response: If an FPX0287W message is issued, create an image copy of the extended DEDB area as soon as possible. If an FPX0328E message is issued, ensure that valid image copies are registered in the RECON data sets and rerun the job.
End of change
-----------------
Start of change
FPX0297W The image copy data set was extended, but the DBRC RECON data sets were not updated.

Explanation: OAE extended the image copy data set, but failed to update the RECON data sets.
System action: Processing continues. OAE did not update the last image record in the RECON data set with the information of the extended image copy data set.
User response: See message FPX0267W and messages issued by DBRC. Correct the error, and issue the CHANGE.IC command.
End of change
-----------------
Start of change
FPX0298W ICEXTEND keyword is ignored because RESTART keyword is specified.

Explanation: OAE cannot extend image copies during restart processing. The ICEXTEND keyword is ignored.
System action: The ICEXTEND keyword is ignored. Processing ends with a return code of 4.
User response: Create an image copy of the extended DEDB area as soon as possible.
End of change
-----------------
Start of change
FPX0299E The xxxxxxxxxxxxxxxxx process ended with errors.

Explanation: The following OAE process ended with errors.
  • Initialization
  • Environment setup
  • ADS copy
  • SDEP expansion
  • CSC checking
  • IOVF expansion
  • ADS copy back
  • Termination
System action: Processing ends with a return code of 8.
User response: See the preceding error messages, correct any errors, and rerun the job with the RESTART keyword.
End of change
-----------------
Start of change
FPX0328E OAE process stopped due to ICERR_CONT=NO option.

Explanation: OAE stopped expanding the DEDB area because the ICERR_CON=NO option is specified and the attempt to extend the image copy failed.
System action: Processing ends with a return code of 8.
User response: See the preceding error messages, correct any errors, and rerun the job.
If you want OAE to extend the DEDB area only, specify the ICERR_CONT keyword in SYSIN DD for shadow expansion or the ICERR_CONT=YES keyword in FPXIN DD for original expansion. After OAE ends normally, create an image copy of the extended DEDB area as soon as possible.
End of change
-----------------
Start of change
FPX0329W The xxxxxxxxxxxxxxxxx process ended with warnings.

Explanation: The following OAE process ended with warnings.
  • Initialization
  • Environment setup
  • ADS copy
  • SDEP expansion
  • CSC checking
  • IOVF expansion
  • ADS copy back
  • Termination
System action: Processing ends with a return code of 4.
User response: See the preceding error messages.
End of change
-----------------
Start of change
FPX0330I LISTCAT information of the temporary area data set after extending:
    (cont) - AREA: areaname
    (cont) - ADSDD: ddname ADSDS: dsname

Explanation: This message shows the LISTCAT report of the temporary area data set after extension.
System action: Processing continues.
User response: None. This message is informational. This message provides you information when you run OAE with the RESTART option or when you recover the area after OAE.
End of change
-----------------
Start of change
FPX0331I LISTCAT information of the area data set after extending:
    (cont) - AREA: areaname
    (cont) - ADSDD: ddname ADSDS: dsname

Explanation: This message shows the LISTCAT report of the original area data set after extension.
System action: Processing continues.
User response: None. This message is informational. This message provides you information when you recover the area after OAE.
End of change



Update 18
Date of change: April 2013
Change description: Documentation changes by APAR PM79336. By applying this APAR, the FPA utility can collect sensor data even when image copy data sets are used as input.
Topics: Changes are made to the following multiple topics:

> 2.0 IMS Fast Path Advanced Tool

New keyword, SENSOR_PTRERR, has been added to the following topics:

>>> 2.4.6 Utility control statements for the Reload process
    --> Table. RELOAD command keywords (Table 10 in PDF and BookManager formats)
>>> 2.5.6 Utility control statements for the Change process
    --> Table. CHANGE command keywords (Table 18 in PDF and BookManager formats)
>>> 2.6.7 Utility control statements for the Reorg process
    --> Table. REORG command keywords (Table 27 in PDF and BookManager formats)
>>> 2.7.6 Utility control statements for the Analyze process
    --> Table. ANALYZE command keywords (Table 34 in PDF and BookManager formats)

Keyword Description
... ...
SENSOR_DBREC ...
Start of changeSENSOR_PTRERR An optional keyword that specifies to store the sensor data in the Sensor Data repository of IMS Tools KB even when pointer errors are detected in the area.End of change
... ...


-----------------

SENSOR_PTRERR keyword has been added to the Related keywords list and the syntax diagram in the following topics:

>>>> 2.11.2.1 ANALYZE
>>>> 2.11.2.2 CHANGE
>>>> 2.11.2.8 RELOAD
>>>> 2.11.2.9 REORG

-----------------
>> 2.11 Command reference for FPA
>>> 2.11.4 FPA keywords
>>>> 2.11.4.91 SENSOR

SENSOR_PTRERR keyword has been added to the Related keywords list.

The following description has been changed:
<Before>
Sensor data from the following areas is not stored:
    • Areas that have pointer errors
    • ...
<After>
Sensor data from the following areas is not stored:
    • Start of changeWhen SENSOR_PTRERR=YES is not specified, areas that have pointer errorsEnd of change
    • ...

-----------------
The following new keyword has been added:

Start of changeSENSOR_PTRERR

Use the SENSOR_PTRERR keyword to store the sensor data in the Sensor Data repository of IMS Tools KB even when pointer errors are detected in the area.

SENSOR_PTRERR is an optional keyword for the following commands:
  • ANALYZE
  • CHANGE
  • RELOAD
  • REORG

Related keyword: SENSOR

Format: SENSOR_PTRERR= parameter

parameter
    parameter can be one of the following values:
    NO
      Does not store the sensor data in the Sensor Data repository of IMS Tools KB when pointer errors are detected in the area.

    YES
      Stores the sensor data in the Sensor Data repository of IMS Tools KB even when pointer errors are detected in the area.

Default: NO

Site default support: Supported. End of change

-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.3 Processing report

SENSOR_PTRERR: NO has been added after SENSOR_DBREC: NO in the PROCESSING OPTION section of the following reports:
  • Processing report for the Reload function (Figure 125 in PDF and BookManager formats)
  • Processing report for the Change function (Figure 126 in PDF and BookManager formats)
  • Processing report for the Reorg function (Figure 128 in PDF and BookManager formats)
  • Processing report for the Analyze function (Figure 129 in PDF and BookManager formats)

-----------------
>>> 2.12.15 Largest Database Records report

DSNAME, DDNAME, DSTYPE, and IC TIMESTAMP fields have been added to the header part of the Largest database Records report (Figure 159 in PDF and BookManager formats).

-----------------
>>> 2.12.27 Site and System Default report

SENSOR_PTRERR: YES NO has been added after the SENSOR_DBREC row in the Site and System Default report examples (Figure 177 and 178 in PDF and BookManager formats).

-----------------
>> 2.13 Site default options support for FPA
>>> 2.13.1 Available keywords for the site default option

Keywords have been added to the Keywords for site default option table (Table 53 in PDF and BookManager formats):

Command/Subcommand Keywords
ANALYZE ...Start of changeSENSOR_PTRERREnd of change...
CHANGE ...Start of changeSENSOR, SENSOR_DBREC, SENSOR_PTRERR, SENSOR_UOW, SENSOR_UOW_REPORTEnd of change...
... ...
RELOAD ...Start of changeSENSOR, SENSOR_DBREC, SENSOR_PTRERR, SENSOR_UOW, SENSOR_UOW_REPORTEnd of change...
REORG ...Start of changeSENSOR, SENSOR_DBREC, SENSOR_PTRERR, SENSOR_UOW, SENSOR_UOW_REPORTEnd of change...
... ...


=====================
> 4.0 IMS Fast Path Online Tools
>> 4.2 Analyzing a DEDB online with FPO
>>> 4.2.8 Utility control statements for OPC

New keyword, SENSOR_PTRERR, has been added to the following table:

Table. ANALYZE statement keywords
(Table 101 in PDF and BookManager formats)
Keyword Used in FPXIN DD Used in DASYSIN DD Description
... ... ... ...
SENSOR_DBREC ... ... ...
Start of changeSENSOR_PTRERR Yes No An optional keyword that specifies to store the sensor data in the Sensor Data repository of IMS Tools KB even when pointer errors are detected in the area.End of change
... ... ... ...

-----------------
>> 4.5 Reorganizing a DEDB online with FPO
>>> 4.5.7 Utility control statements for OER

New keyword, SENSOR_PTRERR, has been added to the following table:

Table. PTRCHK statement keywords
(Table 122 in PDF and BookManager formats)
Keyword Description
... ...
SENSOR_DBREC ...
Start of changeSENSOR_PTRERR An optional keyword that specifies to store the sensor data in the Sensor Data repository of IMS Tools KB even when pointer errors are detected in the area.End of change
... ...

-----------------

SENSOR_PTRERR keyword has been added to the Related keywords list and the syntax diagram in the following topics:

>>>> 4.7.2.1 ANALYZE
>>>> 4.7.2.9 PTRCHK

-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.3 FPO keywords
>>>> 4.7.3.81 SENSOR

The following description has been changed:
<Before>
Sensor data from the following areas is not stored:
    • Areas that have pointer errors
    • ...
<After>
Sensor data from the following areas is not stored:
    • Start of changeWhen SENSOR_PTRERR=YES is not specified, areas that have pointer errorsEnd of change
    • ...
-----------------
The following new keyword has been added:

Start of changeSENSOR_PTRERR

The SENSOR_PTRERR specifies to store the sensor data in the Sensor Data repository of IMS Tools KB even when pointer errors are detected in the area.

SENSOR_PTRERR is an optional keyword for the following statements:
  • ANALYZE statement of OPC
  • PTRCHK statement of OER

Format:

 >>---SENSOR_PTRERR=--------NO------><    
                         |_YES_|        

The variable fields are defined as follows:
    NO
      Does not store the sensor data in the Sensor Data repository of IMS Tools KB when pointer errors are detected in the area.

    YES
      Stores the sensor data in the Sensor Data repository of IMS Tools KB even when pointer errors are detected in the area.

Default: NO, if the SENSOR_PTRERR keyword is not specified.

Site default support: Supported.

Restriction: The SENSOR_PTRERR keyword can be specified only in FPXIN. End of change



Update 17
Date of change: March 2013
Change description: User's Guide update.

For certain DD statements, you must not specify DISP=MOD. This restriction will be added to the description of the following DD statements:

IMS Fast Path Advanced Tool (FPA)
Function DD statements Topic
Unload
  • OAREAnnn or OARnnnnn
  • ctttWKnn
  • itttWKnn
DD statements for the Unload process
Reload
  • HFPARERG
  • ctttWKnn
  • itttWKnn
DD statements for the Reload process
Change
  • HFPARERG
  • ctttWKnn
  • itttWKnn
DD statements for the Change process
Reorg
  • itttWKnn
DD statements for the Reorg process
Analyze
  • HFPARERG
  • itttWKnn
DD statements for the Analyze process
Extract
  • OAREAnnn or OARnnnnn
  • ctttWKnn
DD statements for the Extract process
Build Index
  • UtttWKnn
  • S0nnnnn0
DD statements for the Build Index process


IMS Fast Path Basic Tools (FPB)
Function DD statements Topic
DEDB Pointer Checker For FABADA1 JCL:
  • DAR12O or DAR12
  • DAR13SO or DA13S
  • SORT12
  • SORT3CS
  • DAR3CSO or DAR3CS

For DFSORT JCL (STEP SORT3CS):
  • SORTOUT

For FABADA3 JCL:
  • DAR13O or DAR13
  • SORTR13 or SORT13R
  • DAR4ERRS
  • SORT4CTL

For DFSORT JCL (STEP SORT4):
  • SORTOUT

For DFSORT JCL (STEP SORT12):
  • SORTOUT

For DFSORT JCL (STEP SORTR13):
  • SORTOUT

For FABADA5 JCL:
  • REORGCTL
DD statements for DEDB Pointer Checker
DEDB Tuning Aid For FABBME1 JCL:
  • MESORTCD
  • MEDARO

For DFSORT JCL (Step SORT13):
  • SORTOUT

For FABBME3 JCL:
  • MEDAR12O
  • MEDAR3O
  • SORT12
  • SORT3

For DFSORT JCL (Step SORT12):
  • SORTOUT

For DFSORT JCL (Step SORT3):
  • SORTOUT

For FABADA5 JCL:
  • REORGCTL
DD statements for DEDB Tuning Aid
DEDB Unload/Reload For FABCUR1 JCL:
  • DURDBDFN
  • DURDzzzO or XDzzzzzO
  • DURDzzzE or XDzzzzzE
  • DURSzzzO or XSzzzzzO
  • EXzzzzzO or EXzzzzzE

For DFSORT JCL:
  • SORTOUT
DD statements for DEDB Unload

DD statements for DEDB Reload


IMS Fast Path Online Tools (FPO)
Function DD statements Topic
OPC
  • DFSUDUMP (ic1outdd or ic2outdd)
  • FPXARERG
  • DAR12O
  • DAR13SO
  • SORT12
  • SORT3CS
  • DAR3CSO
  • i001WKnn
DD statements for OPC
ODE
  • FPXOFILE
  • ODESORT
DD statements for ODE
OAE
  • FPXBINTP
DD statements for OAE
OER
  • DAR12O
  • DAR13SO
  • DFSUDUMP (ic1outdd or ic2outdd)
  • SORT12
  • SORT3CS
  • DAR3CSO
  • FPXARERG
  • i001WKnn
DD statements for OER

Supplementary utilities
Utility DD statements Topic
SDEP Space Utilization utility For FABADA8 JCL:
  • DADARO

For DFSORT JCL (STEP SORTSDEP):
  • SORTOUT
DD statements for the SDEP Space Utilization utility
Database Definition Record Create utility For FABCUR5 JCL:
  • DURDBDFN
DD statements for the Database Definition Record Create utility
Reload Segment Data Set Create utility For FABCUR6 JCL:
  • UR6DBDFN
  • DURDzzzO or XDzzzzzO
  • DURDzzzE or XDzzzzzE
  • DURSzzzO or XSzzzzzO
DD statements for the DEDB Reload Segment Data Set Create utility
HD To DEDB Unload Data Set Conversion utility For FABCUR8 JCL:
  • UR6DBDFN
  • DURDzzzO or XDzzzzzO
  • DURDzzzE or XDzzzzzE
  • DURSzzzO or XSzzzzzO
DD statements for the HD To DEDB Unload Data Set Conversion utility




Update 16
Date of change: February 2013
Change description: User's Guide update.
Topics:
> 4.0 IMS Fast Path Online Tools
>> 4.9 Site default options support for FPO
>>> 4.9.3 Setting site default values for FPO
>>>> 4.9.3.2 Setting members for site default options

This topic has been updated as follows:

...
About this task
    The statements specified in each of the following members must follow the control statement syntactical rules for each utility:
    • A PROCLIB member for the global site default options
    • A DB member in the parameter library
    • An AREA member in the parameter library

    If none of these members exist for the utility, no site default options are applied to the subject utility.

    Start of changeWhen FPXIN DD is specified in the JCL stream, the control statements of site default must start with a line that contains one of the following commands:
    • GLOBAL
    • ANALYZE
    • DMACPRT
    • EXTRACT
    • REORG
    For FPXIN syntax rules, see "4.7.1.1 Syntax rules for FPXIN".

    When SYSIN DD is specified in the JCL stream, the control statements of site default must not start with a line that contains these commands. For syntax rules, see the following topics:
    • For OPC, see "4.7.1.2 Syntax rules for DASYSIN".
    • For ODE, see "4.7.1.4 Syntax rules for FPXCTL and areaname".End of change

...




Update 15
Date of change: January 2013
Change description: Documentation change by APAR PM75252. This APAR adds support for IMS Version 13.
Topic:
> 1.0 Overview of IMS HP Fast Path Utilities
>> 1.1 What is IMS HP Fast Path Utilities
>>> 1.1.5 IMS HP Fast Path Utilities terminology

IMS Version 13 has been added to the following list:

...

To make this information easier to read, the version and release levels of IMS are abbreviated, as follows:
  • IMS Version 10 refers to IMS Version 10 Release 1.
  • IMS Version 11 refers to IMS Version 11 Release 1.
  • IMS Version 12 refers to IMS Version 12 Release 1.
  • Start of changeIMS Version 13 refers to IMS Version 13 Release 1.End of change



Update 14
Date of change: December 2012
Change description: Documentation changes by APAR PM76414. By applying this APAR, you can:
  • Use wildcard characters to specify areas on the IAREA and OAREA keywords of FPA, and the AREA keyword of FPO.
  • Specify areas by range on the IAREA and OAREA keywords of FPA, and the AREA keyword of FPO.
  • Include timestamps in FPA and FP stand-alone DB Sensor messages.
Topics: Changes are made to the following multiple topics:

> 2.0 IMS Fast Path Advanced Tool

New keyword, MSTIMESTAMP, has been added to the GLOBAL command keywords tables in the following topics:

>>> 2.3.6 Utility control statements for the Unload process
>>> 2.4.6 Utility control statements for the Reload process
>>> 2.5.6 Utility control statements for the Change process
>>> 2.6.7 Utility control statements for the Reorg process
>>> 2.7.6 Utility control statements for the Analyze process
>>> 2.8.6 Utility control statements for the Extract process
>>> 2.9.6 Utility control statements for the DMAC print process
>>> 2.10.6 Utility control statements for the Build Index process
>>> 2.11.6 Utility control statements for the Initialize process (This topic was added by APAR PM73363. For more information, see the Update 13 section of this techdoc.)

Table. GLOBAL command keywords
(Table 3, 9, 17, 26, 33, 40, 47, and 50 in PDF and BookManager formats)
Keyword Description
... ...
Start of changeMSTIMESTAMP An optional keyword that specifies whether to include a timestamp in the messages.End of change
... ...

-----------------
>> 2.11 Command reference for FPA
>>> 2.11.4 FPA keywords
>>>> 2.11.4.29 IAREA

The format of the IAREA keyword has been changed as follows:

Format:
    IAREA=ALL
    Start of changeIAREA= areaname| n1-n2| areaname1-areaname2
    IAREA=( areanam1, areaname2...,| n1-n2,..,| areaname1-areaname2,...) End of change

    areaname
      Specify a 1- to 8-character area name.
      Start of changeYou can also use certain wildcard characters to specify areas. These wildcard characters are the asterisk (*), which represents from 0 to 8 characters, and the percent sign (%), which represents any single character. For example, IAREA=area* matches area, area1, area1234, and so on; IAREA=area% matches area1, area2, and so on.

    n1-n2
      Specify the range of areas by area numbers. n1 and n2 are area numbers, which are decimal numbers assigned sequentially to the areas within a database. The value for n1 and n2 can be in the range of 1 - 2048. n2 must be equal to or greater than n1. At least one area must exist in the specified range.

    areaname1-areaname2
      Specify the range of areas by area names. areaname1 and areaname2 must be specified in alphabetical order. At least one area must exist in the specified range. End of change

-----------------
>>>> 2.11.4.57 OAREA

The format of the OAREA keyword has been changed as follows:

Format:
    OAREA=ALL
    Start of changeOAREA=areaname| n1-n2| areaname1-areaname2
    OAREA=(areaname1,...,| n1-n2,..,| areaname1-areaname2,...) End of change
    areaname
      Specify a 1- to 8-character area name.
      Start of changeYou can also use certain wildcard characters to specify areas. These wildcard characters are the asterisk (*), which represents from 0 to 8 characters, and the percent sign (%), which represents any single character. For example, OAREA=area* matches area, area1, area1234, and so on; OAREA=area% matches area1, area2, and so on.

    n1-n2
      Specify the range of areas by area numbers. n1 and n2 are area numbers, which are decimal numbers assigned sequentially to the areas within a database. The value for n1 and n2 can be in the range of 1 - 2048. n2 must be equal to or greater than n1. At least one area must exist in the specified range.

    areaname1-areaname2
      Specify the range of areas by area names. areaname1 and areaname2 must be specified in alphabetical order. At least one area must exist in the specified range. End of change


-----------------
>>> 2.11.4 FPA keywords

The following new topic has been added:

Start of change MSTIMESTAMP

Use the MSTIMESTAMP keyword to specify whether to include a timestamp in the messages.

MSTIMESTAMP is an optional keyword for the GLOBAL command.

Related keywords: None.

Format: MSTIMESTAMP= parameter
    parameter
    parameter can be one of the following values:
    LOCAL
      Include a local timestamp in the messages.
    NO
      Do not include a timestamp in the messages.

Default: MSTIMESTAMP=NO

Site default: Supported. End of change

-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.24 Secondary Index Processing report

TOTAL SEGMENTS column has been added to the report as follows:

Figure. Secondary Index Processing report
(Figure 174 in PDF and BookManager formats)


SUPPRESSED SEGMENTS
    ...

Start of changeTOTAL SEGMENTS
    The total number of segments. The value is a sum of loaded segments and suppressed segments. End of change

=================
> 4.0 IMS Fast Path Online Tools
>> 4.7 Keyword reference for FPO
>>> 4.7.3 FPO keywords
>>>> 4.7.3.5 AREA

The format of the AREA keyword has been changed as follows:
...

Format:

    AREA=___areaname,|n1-n2|areanam1-areaname2_________________><
           |__(area1,area2...,|n1-n2,..,|area1-area2,...)_|    
           |___ALL________________________________________|  


    areaname
      The specified area is processed. Specify a 1- to 8-character area name.
      Start of changeYou can also use certain wildcard characters to specify areas. These wildcard characters are the asterisk (*), which represents from 0 to 8 characters, and the percent sign (%), which represents any single character. For example, AREA=area* matches area, area1, area1234, and so on; AREA=area% matches area1, area2, and so on.

    ( area1,area2... ,| n1-n2,..,| area1-area2,...)
      The specified areas are processed.
      Specify the range of areas by area numbers. n1 and n2 are area numbers, which are decimal numbers assigned sequentially to the areas within a database. The value for n1 and n2 can be in the range of 1 - 2048. n2 must be equal to or greater than n1. At least one area must exist in the specified range.

      You can also specify the range of areas by area names. area1 and area2 must be specified in alphabetical order. At least one area must exist in the specified range.
      This parameter can only be used with following statements:
      • ANALYZE statement
      • EXTRACT statement
      • REORG statement
      • DMACPRT statement

    ALL
      All areas are processed. This parameter can only be used with following statements:
      • ANALYZE statement
      • EXTRACT statement
      • REORG statement
      • DMACPRT statement

Multiple areas can be specified only with the following statements:
  • ANALYZE statement
  • EXTRACT statement
  • REORG statement
  • DMACPRT statementEnd of change
=================
>>>> 7.1.3.10 HFPC messages

The following message has been added:

Start of change
HFPC0152E AN ERROR OCCURRED WHILE ANALYZING THE [IAREA | OAREA] KEYWORD PARAMETER.

Explanation: Program HFPMAIN0, HFPSENSR, or HFPSTGEN found that an incorrect parameter is specified on the IAREA or OAREA keyword.
System action: For HFPMAIN0, if SCAN=YES is specified, the return code is set to 8. If SCAN=NO is specified, an abend occurs with a code of U3003. For HFPSENSR or HFPSTGEN, the job ends with a return code of 8.
User response: Correct the command set in HFPSYSIN, and rerun the job.
End of change

-----------------
>>>> 7.1.3.13 HFPG messages

The following messages have been added:

Start of change
HFPG0009E AREA areaname IS SPECIFIED MORE THAN ONCE BY THE FOLLOWING KEYWORD PARAMETERS:
    - " areaname1|range1|wildcard1 " AND " areaname2|range2|wildcard2 "

Explanation: The indicated area is specified more than once.
System action: For FPA, if SCAN=YES is specified, the return code is set to 8. If SCAN=NO is specified, an abend occurs with a code of U3003. For FPO and FP stand-alone DB Sensor, the job ends with a return code of 8.
User response: Correct the command set in HFPSYSIN for FPA and FP stand-alone DB Sensor, or in FPXIN for FPO, and rerun the job.
End of change

-----------------
Start of change
HFPG0010E DBD dbdname CONTAINS NO AREA THAT MATCHES THE WILDCARD CONDITION (xxxxxxxx).

Explanation: No area matches the wildcard specification.
System action: For FPA, if SCAN=YES is specified, the return code is set to 8. If SCAN=NO is specified, an abend occurs with a code of U3003. For FPO and FP stand-alone DB Sensor, the job ends with a return code of 8.
User response: Correct the command set in HFPSYSIN for FPA and FP stand-alone DB Sensor, or in FPXIN for FPO, and rerun the job.
End of change

-----------------
Start of change
HFPG0011E (IAREA|OAREA|AREA)=(n1-n2 | area1-areaN) SPECIFICATION IS INVALID.
    - THE FIRST OPERAND VALUE MUST BE SMALLER THAN OR EQUAL TO THE SECOND OPERAND VALUE.
    - THE SPECIFIED AREA NUMBER (n1-n2) IS NOT DEFINED IN DBD dbdname.
    - THE MAXIMUM AREA NUMBER IS nnnn.
    - THE AREA RANGE IS SPECIFIED IN REVERSE ALPHABETICAL ORDER.
    - THE SPECIFIED AREA [area1 | areaN] IS NOT DEFINED IN DBD dbdname.
    - AN AREA RANGE MUST BE SPECIFIED BY A PAIR OF AREA NUMBERS OR BY A PAIR OF AREA NAMES.
    - WILDCARD PARAMETERS CANNOT BE USED TO SPECIFY THE AREA RANGE.
    - FORMAT ERROR
    - LENGTH ERROR

Explanation: The values specified on the indicated keyword is incorrect.
System action: For FPA, if SCAN=YES is specified, the return code is set to 8. If SCAN=NO is specified, an abend occurs with a code of U3003. For FPO and FP stand-alone DB Sensor, the job ends with a return code of 8.
User response: Correct the command set in HFPSYSIN for FPA and FP stand-alone DB Sensor, or in FPXIN for FPO, and rerun the job.
End of change

-----------------
>>>> 7.1.3.19 HFPM messages

The following message has been added:

Start of change
HFPM0005I SUBSEQUENT MESSAGES ARE SHOWN WITH THE timetype TIMESTAMP.

Explanation: This message notifies that messages that are issued after this message include a timestamp.
System action: Processing continues.
User response: None. This message is informational.
End of change



Update 13
Date of change: December 2012
Change description: Documentation changes by APAR PM73363. This APAR introduces a new command, INITIALIZE, for FPA. This APAR also adds a new parameter, DBRC=IGNORE, for the FPA DBRC keyword.
Topics: Changes are made to the following multiple topics:

> 2.0 IMS Fast Path Advanced Tool
>> 2.1 Overview of IMS Fast Path Advanced Tool
>>> 2.1.1 Functions of FPA

A description of the new Initialize function has been added as follows:

Start of change Initialize
    The Initialize function of FPA efficiently initializes a single DEDB area. It can also concurrently initialize multiple DEDB areas. End of change

-----------------
>>> 2.1.3 Program overview of FPA

Descriptions are updated to include the Initialize function as follows:

IMS Fast Path Advanced Tool makes it easy to develop standardized JCL (that is, a single driver) for unloading, reloading, restructuring, reorganizing, analyzing, extracting, Start of changeand initializing DEDBs. End of change
...

FPA offers the following features:
  • ...
  • The following input and output data sets can be allocated dynamically to minimize JCL DD statements.
    • DEDB area data sets for:
      • ...
      • The output of the Reload process
      • Start of changeThe output of the Initialize processEnd of change
      • ...

Multiple areas of a DEDB can be analyzed, extracted, Start of changeinitialized, End of change unloaded, reloaded, restructured (changed), or reorganized concurrently in multiple subtasks as long as system resources are available. The number of concurrent processes can be controlled by an optional parameter of a control statement.

-----------------
>> 2.3 Unloading a DEDB offline with FPA
>>> 2.3.8 Examples for the Unload function

The following new example has been added:

Start of change
Example 14: Unloading an area without activating the DBRC process

The following figure shows example JCL for unloading an area without activating the DBRC process.

In this example:
  • The DBRC=IGNORE option specifies not to check the area status in DBRC, so the 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.
  • Area authorization is not obtained from DBRC, so the integrity of the area is not protected.
  • The input ADS to be unloaded for the specified area is HPFP.DB22AR0.ADS1.
  • The output unloaded segment records data set is specified on the OAREA001 DD statement.

//HFP      EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//DB22AR0  DD DISP=SHR,DSN=HPFP.DB22AR0.ADS1
//OAREA001 DD DISP=OLD,DSN=HPFP.USRFILE.DB22AR0
//HFPRPTS  DD SYSOUT=*
//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
 GLOBAL
   DBRC=IGNORE
 UNLOAD
   DBD=DEDBJN22,
   IAREA=(DB22AR0),
   OAREA=(DB22AR0)
/*
Figure xx. Unloading an area without activating the DBRC process
End of change
-----------------
>> 2.4 Reloading a DEDB offline with FPA
>>> 2.4.7 Examples for the Reload function

The following new example has been added:

Start of change
Example 14: Reloading an area without activating the DBRC process

The following figure shows example JCL for reloading an area without activating the DBRC process.

This example shows the case of a Reload by using the unloaded segment records data set that is produced by "Example 14: Unloading an area without activating the DBRC process".

In this example:
  • The DBRC=IGNORE option specifies not to check the area status in DBRC, so the 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.
  • Area authorization is not obtained from DBRC, so the integrity of the area is not protected.
  • The input unloaded segment records data set for the area is specified on the IAREA001 DD statement.
  • The output ADS to be reloaded for the specified area is HPFP.DB22AR0.ADS1.

//HFP      EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//DB22AR0  DD DISP=SHR,DSN=HPFP.DB22AR0.ADS1
//IAREA001 DD DISP=OLD,DSN=HPFP.USRFILE.DB22AR0
//HFPRPTS  DD SYSOUT=*
//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
 GLOBAL
   DBRC=IGNORE
 RELOAD
   DBD=DEDBJN22,
   IAREA=(DB22AR0),
   OAREA=(DB22AR0)
/*
Figure xx. Reloading an area without activating the DBRC process
End of change

-----------------
A new chapter, Initializing a DEDB offline with FPA, has been added. Use the attached PDF to view the contents provided in this chapter.

IMSFastPathSolutionPack_Techdoc_December2012.pdfIMSFastPathSolutionPack_Techdoc_December2012.pdf

Note: Page, figure, table, and cross-reference numbers in this PDF extract might not match your current user guide version. Use this documentation extract for content update purposes only. Change bar markings on the left side of the page indicate the new or changed information. This information will be included in any future refreshes of the entire user guide.

-----------------
>> 2.11 Command reference for FPA
>>> 2.11.2 FPA commands

The following new topic has been added:

Start of change
INITIALIZE

Use the INITIALIZE command to initialize one or more area data sets of a DEDB.

INITIALIZE is an optional command for the HFPSYSIN DD statement.

Related keywords:
  • DBD (required keyword)
  • OAREA
  • ODSNMASK
  • OTASKCTL

Format:
    INITIALIZE [ keyword= parameter[,...]] [ subcommand [ keyword= parameter[,...]]]

Syntax:




Default:
    N/A
End of change
-----------------
>>> 2.11.3 FPA subcommands
>>>> 2.11.3.1 ALLOCATE

The INITIALIZE command has been added to the following list:

ALLOCATE is an optional subcommand for the following commands:
  • CHANGE
  • Start of changeINITIALIZEEnd of change
  • RELOAD

-----------------
>>> 2.11.4 FPA keywords
>>>> 2.11.4.12 DBD

The INITIALIZE command has been added to the following list:

DBD is a required keyword for the following commands:
  • ANALYZE
  • CHANGE
  • DMACPRT
  • EXTRACT
  • INDEXBLD
  • Start of changeINITIALIZEEnd of change
  • RELOAD
  • REORG
  • UNLOAD

-----------------
>>>> 2.11.4.13 DBRC

Description has been changed as follows:
...

If you specify DBRC=YES for the CHANGE, Start of changethe INITIALIZE, End of change or the RELOAD command, the RECOV NEEDED status of the area is changed to OFF for that command.

...
parameter
    parameter can be one of the following values:

    YES
      Request the DBRC process of the database.

    NO
      Bypass the DBRC process of the database. If DBRC=FORCE is set for IMS, specifying DBRC=NO does not bypass DBRC.

    Start of changeIGNORE
      Bypass the DBRC process of the database even if DBRC=FORCE is set for IMS. End of change

-----------------
>>>> 2.11.4.57 OAREA

The INITIALIZE command has been added to the following list:

OAREA is an optional keyword for the following commands and subcommands:
  • ALLOCATE
  • CHANGE
  • FILECTL
  • Start of changeINITIALIZEEnd of change
  • RELOAD
  • UNLOAD

-----------------
>>>> 2.11.4.60 ODSNMASK

Description has been changed as follows:

When used with Start of changethe INITIALIZE or End of change the RELOAD command, ODSNMASK is used to allocate the output area being created.

ODSNMASK is an optional keyword for the following commands:
  • CHANGE
  • EXTRACT
  • Start of changeINITIALIZEEnd of change
  • RELOAD
  • UNLOAD

-----------------
>>>> 2.11.4.62 OTASKCTL

Description has been changed as follows:

For the CHANGE Start of changeor the INITIALIZE End of change command, use the OTASKCTL keyword to specify the maximum number of output areas to be processed concurrently. For the INDEXBLD command, use the OTASKCTL keyword to specify the maximum number of secondary index DBDs to be processed concurrently.

OTASKCTL is an optional keyword for the following commands:
  • CHANGE
  • INDEXBLD
  • Start of changeINITIALIZEEnd of change

...

You can use the following parameters when this keyword is specified for the CHANGE Start of changeor the INITIALIZE End of change command:

AREA
    ...

nnnn
    ...

Default:
  • For the CHANGE Start of changeor the INITIALIZEEnd of change command, OTASKCTL=AREA
  • For the INDEXBLD command, OTASKCTL=4


-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.1 Reports generated by each process of FPA

Reports generated by the Initialize process have been added to the following table:

FPA process Generated reports Whether the report can be stored in the IMS Tools KB Output repository
... ... ...
Build Index ... ...
... ...
Start of changeInitialize Audit report Y
Processing report Y
DBD Definition report Y
Initialization Processing Summary report YEnd of change

-----------------
>> 2.12 Sample reports of FPA

The INITIALIZE command has been added to the list in the following three topics:

>>> 2.12.2 Audit report
>>> 2.12.3 Processing report
>>> 2.12.4 DBD Definition report

This report is generated by the following commands:
  • ...
  • Start of changeINITIALIZEEnd of change
  • ...

-----------------
>> 2.12 Sample reports of FPA

The following new topic has been added:

Start of change
Initialization Processing Summary report

The Initialization Processing Summary report provides information about the initialized areas.

This report is generated by the INITIALIZE command.
This report is not printed if you specified the GLOBAL SCAN=YES keyword.

The following figure is an example of the Initialization Processing Summary report.

Figure x. Initialization Processing Summary report

AREA NO
    The area number.

AREANAME
    The area name.

DDNAME
    The DDNAME with the following information:
    (DYNAMIC ALLOCATION):
      DDNAME is allocated dynamically.
    (JCL DD ALLOCATION):
      DDNAME is specified in the JCL statement.

DSNAME
    The DSNAME of the area name DDNAME.

RAA PORTION
    TOTAL BASE CI'S/UOW
      The total number of BASE CIs in each RAA part.
    TOTAL DOVF CI'S/UOW
      The total number of DOVF CIs in each RAA part.
    TOTAL DOVF CI'S/UOW
      The total number of CIs in each RAA part.
    TOTAL UOW's
      The total number of UOWs.

IOVF PORTION
    TOTAL CI'S
      The total number of CIs in IOVF part.
    TOTAL MAP CI'S
      The total number of MAP CIs in IOVF part.

SDEP PORTION
    TOTAL CI'S
      The total number of CIs in SDEP part.
    RANGE
      The SDEP logical begin and logical end RBAs.
    LOGICAL BEGIN
      The cycle count and RBA of SDEP logical begin.
    LOGICAL END
      The cycle count and RBA of SDEP logical end.
    LOGICAL BEGIN TS
      The timestamp of the SDEP logical begin.
End of change
-----------------
>> 2.13 Site default options support for FPA
>>> 2.13.1 Available keywords for the site default option

The INITIALIZE command has been added:

Table x. Keywords for site default option
(Table 53 in PDF and BookManager formats)
Command/Subcommand Keywords
... ...
INDEXBLD ...
Start of changeINITIALIZE OTASKCTLEnd of change
RELOAD ...
... ...

=================
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.12 HFPF messages

The following message text and explanation have been modified:

HFPF3363E AT LEAST ONE ADS IS AVAILABLE IN DBRC FOR Start of change[RELOAD|INITIALIZE] End of change AREANAME: areaname

Explanation: Program HFPMAIN0 or HFPSENSR processed the Reload function Start of changeor the INITIALIZE function End of change with DBRC=YES. However, the program found at least one available ADS for area areaname in DBRC. All ADSs of the area must be in the UNAVAILABLE status in DBRC.
System action: ...
User response: ...

-----------------
>>>> 7.1.3.17 HFPK messages

The following new messages have been added:

Start of change
HFPK0001I INITIALIZE PROCESSING STARTED FOR AREA NO: nnnnn, AREANAME: areaname

Explanation: This message is generated when the Initialize process starts for each area.
System Action: Processing continues.
User Response: None.
End of change

-----------------
Start of change
HFPK0002I INITIALIZE PROCESSING COMPLETED FOR AREA NO: nnnnn, AREANAME: areaname

Explanation: This message is generated when the Initialize process is successfully completed for an area.
System Action: Processing continues.
User Response: None.
End of change



Update 12
Date of change: October 2012
Change description: Documentation change by APAR PM61220. This APAR introduces a new keyword, IDXMAXERROR keyword, which sets the maximum allowable number of pointer segment errors before FPA ends abnormally.
Topic: The following new topic has been added.

> 2.0 IMS Fast Path Advanced Tool
>> 2.11 Command reference for FPA
>>> 2.11.4 FPA keywords

The following new keyword has been added:

Start of change
IDXMAXERROR

Use the IDXMAXERROR keyword to specify the maximum allowable number of pointer segment errors for an index database. When the maximum number is reached, the ANALYZE process ends abnormally.

IDXMAXERROR is an optional keyword for the ANALYZE command.

Related keywords: None.

Format: IDXMAXERROR= parameter

parameter
    Specify a value in the range of 0 - 999. If 0 is specified, the maximum allowable number is not set.

Default: IDXMAXERROR=100

Site default support: Supported.
End of change

=================
> 7.1 Messages and codes of IMS HP Fast Path Utilities
>> 7.1.3 Messages
>>> 7.1.3.9 HFPB messages

In the following messages, message texts and explanations have been changed as follows:

HFPB0002I INDEXBLD SCAN PROCESSING COMPLETED FOR AREA NO: nnnn, AREANAME: areaname Start of change(ELAPSED TIME: hh:mm:ss.tt) End of change

Explanation: The scan phase of the Build Index process for the secondary index database has completed. Start of changeELAPSED TIME shows the time spent for the processing. End of change

-----------------
HFPB0004I INDEXBLD [LOAD|RESYNC] PROCESSING COMPLETED FOR SECONDARY INDEX DBD: index_dbdbase Start of change(ELAPSED TIME: hh:mm:ss.tt) End of change
    - THE SECONDARY INDEX DATABASE DID NOT NEED TO BE UPDATED. ALREADY IN SYNC WITH THE DEDB.

Explanation: The load phase or the resync phase of the Build Index process for the indicated secondary index database has completed. Start of changeELAPSED TIME shows the time spent for the processing. End of change When the secondary index database is already in sync with the DEDB, the sub text is issued.



Update 11
Date of change: October 2012
Change description: Documentation changes by APAR PM69660. This APAR enhances FPA and FPO to generate Consolidated Largest Database Records reports.
Topics: Changes are made to the following multiple topics:

>>> 2.4.5 DD statements for the Reload process
>>> 2.5.5 DD statements for the Change process
>>> 2.6.6 DD statements for the Reorg process
>>> 2.7.5 DD statements for the Analyze process

The Consolidated Largest Database Records report has been added to the list as follows:

HFPRPTS DD
...
When the REPORT subcommand and PTRCHKLVL=FULL are specified, the following reports are generated:
  • DEDB Area Analysis reports
  • ...
  • Largest Database Records report (When LARGEREC_REPORT=YES is specified.)
  • Start of changeConsolidated Largest Database Records report (When LARGEREC_REPORT=YES is specified and the second parameter of the LARGEREC_COUNT keyword specifies a value that is equal to or larger than 1.) End of change

-----------------
>>> 2.4.6 Utility control statements for the Reload process
>>> 2.5.6 Utility control statements for the Change process
>>> 2.6.7 Utility control statements for the Reorg process
>>> 2.7.6 Utility control statements for the Analyze process

The description of the LARGEREC_COUNT keyword has been changed as follows:

Table. REPORT subcommand keywords
(Tables 13, 22, 29, and 35 in PDF and BookManager formats)
Keyword Description
... ...
LARGEREC_COUNT An optional keyword that specifies the number of reporting entries in the Largest Database Records report Start of changeand the Consolidated Largest Database Records report.End of change This keyword is effective only when PTRCHKLVL=FULL is specified.

-----------------
> 2.0 IMS Fast Path Advanced Tool
>> 2.11 Command reference for FPA
>>> 2.11.3 FPA subcommands
>>>> 2.11.3.6 REPORT

The Consolidated Largest Database Records report has been added to the list as follows:
...
The REPORT subcommand can be used to request the following reports:
  • Process Summary of Analysis report
  • DEDB Area Analysis reports
  • UOW report
  • UOW Exception report
  • Largest Database Records report
  • Start of changeConsolidated Largest Database Records reportEnd of change

-----------------
>>>> 2.11.4.48 LARGEREC_COUNT

The content has been changed as follows:

Use the LARGEREC_COUNT keyword to specify the number of reporting entries in the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change
...

Format:
    Start of changeLARGEREC_COUNT= parm1
    LARGEREC_COUNT=( parm1,parm2)

parm1
    Specify the number of reporting entries in the Largest Database Records report. The value is in the range of 0 - 9999. If 0 is specified, the Largest Database Records report is not generated.
parm2
    Specify the number of reporting entries in the Consolidated Largest Database Records report. The value is in the range of 0 - 9999. If 0 is specified, the Consolidated Largest Database Records report is not generated.

LARGEREC_COUNT=(0,0) is mutually exclusive with LARGEREC_REPORT=YES.

Default: LARGEREC_COUNT=(10,0) End of change
...

-----------------
>>>> 2.11.4.49 LARGEREC_REPORT

The description has been changed as follows:

Use the LARGEREC_REPORT keyword to specify whether to generate the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change
...
parameter
    parameter can be one of the following values:

    YES
      Generate the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change
    NO
      Do not generate the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change

-----------------
>>>> 2.11.4.76 REPORTDD

The Consolidated Largest Database Records report has been added to the list as follows:

You can specify the destination ddname for the following reports:
  • DEDB Area Analysis reports
  • UOW report
  • UOW Exception report
  • Largest Database Records report
  • Start of changeConsolidated Largest Database Records reportEnd of change

-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.1 Reports generated by each process of FPA

The Consolidated Largest Database Records report has been added to the following table as follows:

Table. Reports generated by each process of FPA
(Table 52 in PDF and BookManager formats)
FPA process Generated reports Whether the report can be stored in the IMS Tools KB Output repository
... ... ...
Analyze ... ...
Largest Database Records report Y
Start of changeConsolidated Largest Database Records report YEnd of change
... ...

-----------------
The following new topic has been added after 2.12.15 "Largest Database Records report".

Start of change
Consolidated Largest Database Records report

You can use this optional report to analyze the largest database records. The report provides information about each of the large database records, starting with the largest database record.

The difference between this report and the Largest Database Records report is that the Largest Database Records report provides information about the large database records for each area whereas the Consolidated Largest Database Records report consolidates information about the large database records found in multiple areas into a single report.

This report is generated by the following commands when the second parameter of the LARGEREC_COUNT keyword, which specifies the number of reporting entries in the Consolidated Largest Database Record report, specifies a value that is equal to or larger than 1.
  • ANALYZE with the LARGEREC_REPORT=YES keyword of REPORT subcommand and the PTRCHKLVL=FULL keyword
  • CHANGE with the LARGEREC_REPORT=YES keyword of REPORT subcommand and the PTRCHKLVL=FULL keyword
  • RELOAD with the LARGEREC_REPORT=YES keyword of REPORT subcommand and the PTRCHKLVL=FULL keyword
  • REORG with the LARGEREC_REPORT=YES keyword of REPORT subcommand and the PTRCHKLVL=FULL keyword

The following figure shows an example of the Consolidated Largest Database Records report.


Figure. Consolidated Largest Database Records report

DBDNAME
    Shows the DBD name of the database.
KEY LENGTH
    Shows the length of the key in the root segment.
RECORD COUNT
    Shows the number of reporting entries of the largest database records.
TOTAL AREA#
    Shows the number of areas that were analyzed.
AREA
    Shows the names of areas that were analyzed.
RECORD SIZE
    Shows the total length of the database record that includes prefix length of all segments in the record.
# OF SEG'S
    Shows the total number of segments in the record.
AREANAME
    Shows the name of the area.
AREA#
    Shows the area number.
ROOT RBA
    Shows the value of root segment RBA.
RAP RBA
    Shows the value of RAP RBA.
ROOT SEGMENT SEQUENCE FIELD (HEX) and (CHARACTER)
    Shows the value of the key in the root segment.
End of change

=================
> 4.0 IMS Fast Path Online Tools
>> 4.2 Analyzing a DEDB online with FPO
>>> 4.2.3 Considerations for running FPO
>>>> 4.2.3.1 Selecting the operating modes

The Consolidated Largest Database Records report has been added to the following table:

Table. TYPRUN= values and associated functions
(Table 95 in PDF and BookManager formats)
TYPRUN= Integrity verification Analysis and report
... ... ...
RPT
  • ...
  • Complete analysis reports
  • Optional Largest Database Records report
  • Start of changeOptional Consolidated Largest Database Records reportEnd of change
  • ...

-----------------
>>> 4.2.8 Utility control statements for OPC
>>> 4.5.7 Utility control statements for OER

The description of the LARGEREC_COUNT keyword has been changed as follows:

Table. REPORT statement keywords
(Tables 102 and 123 in PDF and BookManager formats)
Keyword Description
... ...
LARGEREC_COUNT An optional keyword that specifies the number of reporting entries in the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change

-----------------
>>> 4.2.9 Output for OPC
>>>> 4.2.9.1 FPXRPTS DD data set

The Consolidated Largest Database Records report has been added to the list as follows:

When the TYPRUN=RPT keyword and the FULLSTEP=YES keyword are specified, the following reports are produced in the data set or in the output stream depending on the REPORTDD keyword of the REPORT control statement:
  • Processing Summary of Analysis report
  • ...
  • Largest Database Records report
  • Start of changeConsolidated Largest Database Records reportEnd of change
  • ...

The following subsection has been added after the Largest Database Records report subsection:

Start of change
Consolidated Largest Database Records report

You can use this optional report to analyze the largest database records. The report provides information about each of the large database records, starting with the largest database record.

The difference between this report and the Largest Database Records report is that the Largest Database Records report provides information about the large database records for each area whereas the Consolidated Largest Database Records report consolidates information about the large database records found in multiple areas into a single report.

The Consolidated Largest Database Records report is produced by the Analyze function of FPA, which is internally called by OPC when the following conditions are met:
  • The TYPRUN=RPT keyword is specified.
  • The FULLSTEP=YES keyword is specified.
  • The LARGEREC_REPORT=YES keyword is specified.
  • The second parameter of LARGEREC_COUNT keyword, which specifies the number of reporting entries in the Consolidated Largest Database Record report, specifies a value that is equal to or larger than 1.
End of change
-----------------
>> 4.5 Reorganizing a DEDB online with FPO
>>> 4.5.8 Output for OER
>>>> 4.5.8.1 FPXRPTS DD data set

The Consolidated Largest Database Records report has been added to the list as follows:

Detailed area statistics reports

If PTRCHK=YES keyword is specified for the REORG control statement, and the TYPRUN=RPT keyword and the FULLSTEP=YES keyword are specified for the PTRCHK control statement, the following reports are produced in the data set or in the output stream depending on the REPORTDD keyword of the REPORT control statement:
  • Processing Summary of Analysis report
    • ...
  • Largest Database Records report
  • Start of changeConsolidated Largest Database Records reportEnd of change
  • ...

-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.3 FPO keywords
>>>> 4.7.3.42 LARGEREC_COUNT

The content has been changed as follows:

The LARGEREC_COUNT keyword specifies the number of reporting entries in the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change
...

Format:

  >>---LARGEREC_COUNT=---+-----parm1--------------+-----><
                         +____(parm1,parm2)_______+

The variable field is defined as follows:
Start of change
parm1
    Specify the number of reporting entries in the Largest Database Records report. The value is in the range of 0 - 9999. If 0 is specified, the Largest Database Records report is not generated.
parm2
    Specify the number of reporting entries in the Consolidated Largest Database Records report. The value is in the range of 0 - 9999. If 0 is specified, the Consolidated Largest Database Records report is not generated.
End of change

Default: Start of change(10,0) End of change, if the LARGEREC_COUNT keyword is not specified.
...

Restrictions:
  • The LARGEREC_COUNT keyword can be specified only in FPXIN.
  • Start of changeLARGEREC_COUNT=(0,0) is mutually exclusive with LARGEREC_REPORT=YES.End of change

-----------------
>>>> 4.7.3.43 LARGEREC_REPORT

The description has been changed as follows:

The LARGEREC_REPORT keyword specifies whether to generate the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change

The variable field is defined as follows:
YES
    Generate the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change
NO
    Do not generate the Largest Database Records report Start of changeand the Consolidated Largest Database Records report. End of change

-----------------
>> 4.8 FPO reports stored in IMS Tools KB

The Consolidated Largest Database Records report has been added to the following table:

Table. Messages and reports stored in IMS Tools KB
(Table 130 in PDF and BookManager formats)
Utility Generated messages and reports Whether the report can be stored in the IMS Tools KB Output repository
OPC ... ...
Largest Database Records report Y
Start of changeConsolidated Largest Database Records reportEnd of change Y
... ...
... ... ...
OER ... ...
Largest Database Records report Y
Start of changeConsolidated Largest Database Records reportEnd of change Y
... ...

===============
> 6.0 References
>> 6.1 DEDB monitoring and tuning guide
>>> 6.1.4 Determining the actions to resolve the detected exceptions
>>>> 6.1.4.1 Generating the analysis reports

The Consolidated Largest Database Records report has been added to the following table:

Table. Analysis reports printed by each utility
(Table 149 in PDF and BookManager formats)
Report number Report FPA FPO FPB IMS HP Image Copy
... ... ... ... ... ...
Start of change12 Consolidated Largest Database Records report Printable Printable - -End of change


Step 4 has been added as follows:

Generating the reports by using a function of FPA
To generate the reports by using the FPA Analyze function, the FPA Change function, the FPA Reload function, or the FPA Reorg function, complete these steps:
  1. Specify the REPORT subcommand.
    This specification generates reports 1 and 7.
  2. Specify the PTRCHKLVL=FULL option.
    This specification generates reports 2, 3, 4, 5, 6, and 8.
  3. Specify the LARGEREC_REPORT=YES option.
    This specification generates report 10, and is also required to generate report 12.
  4. Start of changeSpecify a value that is equal to or larger than 1 for the second parameter of the LARGEREC_COUNT keyword.
    This specification generates report 12.End of change
  5. Run the job.

Step 5 has been added as follows:

Generating the reports by using a utility of FPO
To generate the reports by using the Online Pointer Checker utility or the Online Expert Reorganization utility, complete these steps:
  1. Specify the TYPRUN=RPT option.
  2. If you use the Online Expert Reorganization utility, also specify the PTRCHK=YES option.
  3. Specify the FULLSTEP=YES option.
    This specification generates reports 1, 2, 3, 4, 5, 6, 7, and 8.
  4. Specify the LARGEREC_REPORT=YES option.
    This specification generates report 10, and is also required to generate report 12.
  5. Start of changeSpecify a value that is equal to or larger than 1 for the second parameter of the LARGEREC_COUNT keyword.
    This specification generates report 12.End of change
  6. Run the job.

-----------------
>>>> 6.1.5.1 FPA Analyze JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.2 FPA Reload JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.3 FPA Change JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.4 FPA Reorg JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.6 Online Pointer Checker JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.7 Online Expert Reorganization JCL examples for monitoring and tuning DEDBs

The LARGEREC_COUNT keyword has been added to example 7 as follows:

Example 7: Generating reports to obtain large database records information

The following figure shows example JCL for generating the reports that contain information about the large database records.
In this example:
  • PTRCHKLVL=FULL for the ANALYZE command specifies that the integrity verification process runs in FULL mode.
  • The REPORT subcommand, LARGEREC_REPORT=YES, Start of changeand LARGEREC_COUNT=(10,20) specify that the Largest Database Records report and the Consolidated Largest Database Records report are generated.End of change


Figure. Generating reports to obtain large database records information
(Figures 457, 467, 477, 487, 504, 513 in PDF and BookManager formats)

...
   REPORT
    LARGEREC_REPORT=YES,
    LARGEREC_COUNT=(10,20)
/*



===============
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.6 FPX messages

The explanation section of the FPX0017E message has been changed as follows:

FPX0017E Failure to acquire storage.

Explanation: Storage was being obtained by the GETMAIN or the STORAGE macro. The action completed unsuccessfully with a nonzero return code.
This message might be accompanied by one of the following additional texts:

Requested for typ tbl  MVS RET and RSN codes are: rc  + rsn  


This accompanying text identifies the following associated with the storage failure:
  • Start of change typ tbl
    The failing internal table operation type End of change
  • rc
    The MVS return code associated with the storage failure
  • rsn
    The MVS reason code associated with the storage failure
System action: Processing ends with a return code of 8. The OAE Rename program (FPXBTOA0) ends with abend code U3530.
User response: Provide the appropriate action for the specified return code and reason code, as described in MVS/ESA System Programming Library.



Update 10
Date of change: July 2012
Change description: User's Guide update.
Topics: Changes are made to the following multiple topics:

> 2.0 IMS Fast Path Advanced Tool
>> 2.3 Unloading a DEDB offline with FPA
>>> 2.3.8 Examples for the Unload function
>>>> 2.3.8.10 Example 10: Unloading all areas of a DEDB that are registered with DBRC and creating their image copies

The ICERPRT DD statement has been added to the following figure:

Figure. Unloading all areas of a DEDB that are registered with DBRC and creating their image copies
(Figure 24 in PDF and BookManager formats)

//HFP      EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=HPS.SHPSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//RECON1   DD DISP=SHR,DSN=IMSVS.RECON1
//RECON2   DD DISP=SHR,DSN=IMSVS.RECON2
//RECON3   DD DISP=SHR,DSN=IMSVS.RECON3
//HFPRPTS  DD SYSOUT=*
//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
 GLOBAL
   DBRC=YES
 UNLOAD
   DBD=DEDBJN22,
   IAREA=ALL,
   OAREA=ALL,
   ODSNMASK='HPFP.USRFILE.&AREA',
   ICOUT=YES
/*
//ICEIN    DD *
  GLOBAL   ICHLQ=ICOUT.HFP,
           UNIT=SYSDA,
           SPACE=(CYL,100,100)
/*
//ICERPRT  DD SYSOUT=*

-----------------
>>>> 2.3.8.12 Example 12: Unloading all areas of a DEDB that are registered with DBRC and creating their image copies with the checkpoint restart option

The ICERPRT DD statement has been added to the following figure:

Figure. Unloading all areas of a DEDB that are registered with DBRC and creating their image copies with the checkpoint restart option
(Figure 27 in PDF and BookManager formats)

//HFPEXE EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=HPS.SHPSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
//HFPPRINT DD SYSOUT=*
//HFPRPTS  DD SYSOUT=*
//ICEPRINT DD SYSOUT=*
//ICERPRT  DD SYSOUT=*
//HFPCHKPT DD DISP=SHR,DSN=HPFP.HFPCHKPT
//STACK1   DD UNIT=TAPE,DSN=HFP001.ICDS,
//            DISP=OLD,VOL=SER=HFP001
//STACK2   DD UNIT=TAPE,DSN=HFP002.ICDS,
//            DISP=OLD,VOL=SER=HFP002
//STACK3   DD UNIT=TAPE,DSN=HFP003.ICDS,
//            DISP=OLD,VOL=SER=HFP003
//STACK4   DD UNIT=TAPE,DSN=HFP004.ICDS,
//            DISP=OLD,VOL=SER=HFP004
//HFPSYSIN DD *
  GLOBAL DBRC=YES,
      RESTART=YES
  UNLOAD
      DBD=DEDBJN22,
      IAREA=ALL,
      OAREA=ALL,
      ODSNMASK='HPFP.USRFILE.&AREA',
      KEYSEQCHK=ABEND,
      ICOUT=YES
/*
//ICEIN DD *
  GLOBAL ICHLQ=HFPICDS,UNIT=TAPE
  IC DBD=DEDBJN22,AREA=DB22AR1,STACK=STACK1
  IC DBD=DEDBJN22,AREA=DB22AR2,STACK=STACK1
  IC DBD=DEDBJN22,AREA=DB22AR3,STACK=STACK2
  IC DBD=DEDBJN22,AREA=DB22AR4,STACK=STACK3
  IC DBD=DEDBJN22,AREA=DB22AR5,STACK=STACK4
  IC DBD=DEDBJN22,AREA=DB22AR6,STACK=STACK4
  IC DBD=DEDBJN22,AREA=DB22AR7,STACK=STACK2
  IC DBD=DEDBJN22,AREA=DB22AR8,STACK=STACK1
  IC DBD=DEDBJN22,AREA=DB22AR9,STACK=STACK1
/*

-----------------
>>> 2.3.8 Examples for the Unload function

The following new example has been added:

Start of change
Example 13: Unloading multiple areas of a DEDB into one output unloaded segment record data set under SMS environment

The following figure shows example JCL for unloading multiple areas of a DEDB into one output unloaded segment record data set under an SMS environment.

In this example:
  • The DBRC=NO option does not check the area status in DBRC, so RECON data sets are not needed.
  • The input ADSs to be unloaded for specified areas are dynamically allocated by using the IDSNMASK parameter.
    The following ADSs are allocated:
    • HPFP.DB22AR0.ADS1 for area DB22AR0
    • HPFP.DB22AR1.ADS1 for area DB22AR1
    • HPFP.DB22AR2.ADS1 for area DB22AR2
    • HPFP.DB22AR3.ADS1 for area DB22AR3
  • The output unloaded segment records data set for all areas is HPFP.USRFILE, which is specified by DSNAME='HPFP.USRFILE' in the FILECTL subcommand. This data set is allocated dynamically.
  • Because the STORCLAS keyword is specified, the output data set is an SMS-managed data set.
    Tip: When the output data set is an SMS-managed data set, the UNIT keyword and the VOLSER keyword, which are required for non-SMS managed data sets, are not required.

//HFP      EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
//HFPRPTS  DD SYSOUT=*
//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
GLOBAL
  DBRC=NO
UNLOAD
  DBD=DEDBJN22,
  IAREA=ALL,
  IDSNMASK='HPFP.&AREA.ADS1',
  SORT=YES
FILECTL
  OAREA=ALL,
  DSNAME='HPFP.USRFILE',
  DISP=(NEW,CATLG),
  SPACE=(CYL,5,1),
  STORCLAS=HFPSTOR
/*

Figure xx. Unloading multiple areas of a DEDB into one output unloaded segment record data set under SMS environment
End of change
-----------------
>> 2.4 Reloading a DEDB offline with FPA
>>> 2.4.7 Examples for the Reload function
>>>> 2.4.7.3 Example 3: Reloading multiple areas of a DEDB from one input unloaded segment record data set

The following change has been made:

This example shows a case of Reload by using Start of change reloaded unloaded End of change segment records data sets

-----------------
>>>> 2.4.7.10 Example 10: Reloading an area that is registered with DBRC and creating its image copy

The ICERPRT DD statement has been added to the following figure:

Figure. Reloading an area that is registered with DBRC and creating its image copy
(Figure 44 in PDF and BookManager formats)

//HFP EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=HPS.SHFSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
//HFPRPTS  DD SYSOUT=*
//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
 GLOBAL
   DBRC=YES
 RELOAD
   DBD=DEDBJN22,
   IAREA=(DB22AR0),
   IDSNMASK='HPFP.USRFILE.&AREA',
   OAREA=(DB22AR0),
   ICOUT=YES,
   ICNOTIFY=YES
/*
//ICEIN DD *
  GLOBAL ICHLQ=ICOUT.HFP,
         UNIT=SYSDA,
         SPACE=(CYL,100,100)
/*
//ICERPRT  DD SYSOUT=*

-----------------
>>> 2.4.7 Examples for the Reload function

The following new example has been added:

Start of change
Example 13: Reloading multiple areas of a DEDB from one input unloaded segment record data set under SMS environment

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

This example shows a case of Reload by using unloaded segment records data sets that are produced by "Example 13: Unloading multiple areas of a DEDB into one output unloaded segment record data set under SMS environment" in topic 2.3.8.13.

In this example:
  • The DBRC=NO option does not check the area status in DBRC, so RECON data sets are not needed.
  • The input unloaded segment records data set for all areas is HPFP.USRFILE that is specified by the IAREA001 DD statement.
  • Because the input unloaded segment records data set is already sorted during the unloading process, it is not necessary to specify the SORT=YES parameter. If this data set was not sorted during the Unload process, SORT=YES must be specified.
  • The output ADSs to be reloaded for all areas are dynamically allocated by using the ODSNMASK parameter and the ALLOCATE subcommand.
    The following ADSs are allocated:
    • HPFP.DB22AR0.ADS1 for area DB22AR0
    • HPFP.DB22AR1.ADS1 for area DB22AR1
    • HPFP.DB22AR2.ADS1 for area DB22AR2
    • HPFP.DB22AR3.ADS1 for area DB22AR3

//HFP      EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//IAREA001 DD DISP=SHR,DSN=HPFP.USRFILE
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
//HFPRPTS  DD SYSOUT=*

//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
 GLOBAL
   DBRC=NO
 RELOAD
   DBD=DEDBJN22,
   IAREA=(DB22AR0),
   ODSNMASK='HPFP.&AREA.ADS1'
 ALLOCATE
   OAREA=ALL,
   SPACE=(CYL,5),
  STORCLAS=HFPSTOR

/*
    Figure xx. Reloading multiple areas of a DEDB from one input unloaded segment record data set under SMS environment
End of change
-----------------
>> 2.5 Changing a DEDB offline with FPA
>>> 2.5.7 Example for the Change function
>>>> 2.5.7.4 Example 4: Reorganizing an area that is registered with DBRC and creating its image copy

The ICERPRT DD statement has been added to the following figure:

Figure. Reorganizing an area that is registered with DBRC and creating its image copy
(Figure 58 in PDF and BookManager formats)

//HFP EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=HPS.SHFSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
//IAREA001 DD DISP=SHR,DSN=HPFP.OLD.DB22AR0.ADS1
//HFPRPTS  DD SYSOUT=*
//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
GLOBAL
  DBRC=YES
CHANGE
  DBD=DEDBJN22,
  IAREA=(DB22AR0),
  OAREA=(DB22AR0),
  ICOUT=YES,
  ICNOTIFY=YES
/*
//ICEIN    DD *
  GLOBAL   ICHLQ=ICOUT.HFP,
           UNIT=SYSDA,
           SPACE=(CYL,100,100)
/*
//ICERPRT  DD SYSOUT=*

-----------------
>> 2.6 Reorganizing a DEDB offline with FPA
>>> 2.6.8 Examples for the Reorg function
>>>> 2.6.8.2 Example 2: Reorganizing UOWs that use IOVF CIs and generating an image copy

The ICERPRT DD statement has been added to the following figure:

Figure. Reorganizing UOWs that use IOVF CIs and generating an image copy
(Figure 70 in PDF and BookManager formats)

//HFP EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=HPS.SHPSLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
//HFPRPTS  DD SYSOUT=*
//HFPPRINT DD SYSOUT=*
//HFPSYSIN DD *
 GLOBAL
   DBRC=YES
 REORG
   DBD=DEDBJN22,
   IAREA=(DB22AR0),
   RDOVFFS=0,
   ICOUT=YES,
   ICNOTIFY=YES
/*
//ICEIN    DD *
 GLOBAL    ICHLQ=ICOUT.HFP,
           UNIT=SYSDA,
           SPACE=(CYL,100,100)
/*
//ICERPRT  DD SYSOUT=*

-----------------
>> 2.11 Command reference for FPA
>>> 2.11.3 FPA subcommands
>>>> 2.11.3.6 GLOBAL

The RESTART keyword and the RESTART_COUNT keyword have been added to the "Related keywords" section and to the "Syntax" section.

-----------------
>>> 2.11.3 FPA subcommands
>>>> 2.11.3.8 THRESHOLD

The following change has been made:

If you do not specify the Start of change PTRCHKLVL=FULL keyword REPORT subcommand, End of change this subcommand is ignored.

-----------------
>>> 2.4.6 Utility control statements for the Reload process
>>> 2.5.6 Utility control statements for the Change process
>>> 2.6.7 Utility control statements for the Reorg process
>>> 2.7.6 Utility control statements for the Analyze process

The following change has been made to these topics:

The THRESHOLD subcommand is used to specify the threshold parameter values, which cause warning messages to be generated when the actual values do not meet the specified criteria. If you do not specify the REPORT subcommand Start of change and the PTRCHKLVL=FULL keyword , End of change this subcommand is ignored.

-----------------
>>> 2.11.4 FPA keywords
>>>> 2.11.4.45 ITKBSRVR

The parameter descriptions have been changed as follows:

parameter
    parameter can be one of the following values:
    servername
      Start of changeFPA stores reports, sensor data, or both in the repositories of the specified IMS Tools KB server. End of change

    *NO
      Start of changeFPA does not store reports or sensor data in the repositories of IMS Tools KB. End of change

-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.2 Audit report

DBRCGRP has been added to the following figure:

Figure. Audit report
(Figure 123 in PDF and BookManager formats)

PROCESSING INFORMATION

EXEC
    - DBRCGRP :
    - IMSPLEX :

=================
> 4.0 IMS Fast Path Online Tools
>> 4.2 Analyzing a DEDB online with FPO
>>> 4.2.10 Examples for OPC
>>>> 4.2.10.6 Example 6: Processing multiple areas and taking image copies

The ICERPRT DD statement has been added to the following figure:

Figure. Processing multiple areas and taking image copies
(Figure 294 in PDF and BookManager formats)

//ANALYZE EXEC FPUTIL,DBD=DEDBJN23,IMSID=IMS1
//STEPLIB DD DISP=SHR,DSN=HPFP.SHFPLMD0
//        DD DISP=SHR,DSN=HPIC.SHPSLMD0
//        DD DISP=SHR,DSN=IMS.SDFSRESL
//FPXIN   DD *
 ANALYZE AREA=(DB23AR1,DB23AR2),
         FULLSTEP=YES,
         TYPRUN=RPT,
         IC=(YES,ICEIN),
         ICNOTIFY=YES
 REPORT  REPORTDD=FPXRPTS
/*
//ICEIN   DD *
  GLOBAL   COMP=Y,COMPRTN=FABJCMP4
  CIC      DBD=DEDBJN23,
           AREA=DB23AR1,
           ICOUT=ICOUT001
  CIC      DBD=DEDBJN23,
           AREA=DB23AR2,
           ICOUT=ICOUT002
/*
//FPXRPTS  DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//ICERPRT  DD SYSOUT=*
//ICOUT001 DD DISP=SHR,DSN=HPFP.DB23AR1.IC
//ICOUT002 DD DISP=SHR,DSN=HPFP.DB23AR2,IC

-----------------
>> 4.5 Reorganizing a DEDB online with FPO
>>> 4.5.9 Examples for OER
>>>> 4.5.9.3 Example 3: Running OER with OPC for multiple areas and taking image copies

The ICERPRT DD statement has been added to the following figure:

Figure. Running OER with OPC for multiple areas and taking image copies
(Figure 336 in PDF and BookManager formats)

//ANALYZE EXEC FPUTIL,DBD=DEDBJN23,IMSID=IMS1
//STEPLIB DD DISP=SHR,DSN=HPFP.SHFPLMD0
//        DD DISP=SHR,DSN=HPIC.SHPSLMD0
//        DD DISP=SHR,DSN=IMS.SDFSRESL
//FPXIN   DD *
 ANALYZE AREA=(DB23AR1,DB23AR2),
         FULLSTEP=YES,
         TYPRUN=RPT,
         IC=(YES,ICEIN),
         ICNOTIFY=YES
 REPORT  REPORTDD=FPXRPTS
/*
//ICEIN   DD *
  GLOBAL   COMP=Y,COMPRTN=FABJCMP4
  CIC      DBD=DEDBJN23,
           AREA=DB23AR1,
           ICOUT=ICOUT001
  CIC      DBD=DEDBJN23,
           AREA=DB23AR2,
           ICOUT=ICOUT002
/*
//FPXRPTS  DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//ICERPRT  DD SYSOUT=*
//ICOUT001 DD DISP=SHR,DSN=HPFP.DB23AR1.IC
//ICOUT002 DD DISP=SHR,DSN=HPFP.DB23AR2,IC


=================
> 6.0 References
>> 6.3 Record layouts
>>> 6.3.4 Total segments records layout

The description column for TOTRECRL has been changed as follows:

Table. Record layout of the total segments records file
(Table 158 in PDF and BookManager formats)
Field name Assembler definition Description
: : :
TOTRECRL CL1 HFP Release Start of changeC'2'End of change
: : :



Update 9
Date of change: July 2012
Change description: Documentation changes by APAR PM65854. This APAR enhances the format of the DEDB Area Analysis reports to provide additional information.
Topics: Changes are made to the following multiple topics.

> 2.0 IMS Fast Path Advanced Tool
>> 2.11 Command reference for FPA
>>> 2.11.3 FPA subcommands
>>>> 2.11.3.6 REPORT

The SEGLSTAT keyword has been added to the Related keywords section and the Syntax section.

-----------------
>>>> 2.11.4 FPA keywords

The following new topic has been added:

Start of change
SEGLSTAT

Use the SEGLSTAT keyword to specify the format of the DB Record Profile Analysis report, which is one of the DEDB Area Analysis reports.

SEGLSTAT is an optional keyword for the REPORT subcommand.

Related keywords: None.

Format: SEGLSTAT= parameter

parameter
    Specify one of the following parameters:

    COMPACT
      The DB Record Profile Analysis report provides analysis information of the database records. It does not include details such as prefix length and data flags.
    DETAILED
      The DB Record Profile Analysis report provides prefix length and data flags in addition to the default contents. This additional information is helpful in database tuning.

Default: SEGLSTAT=COMPACT

Site default support: Supported.
End of change

-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.14 DEDB Area Analysis reports
>>>> 2.12.14.1 Freespace Analysis report

The "Overview and RAA BASE sections of the Freespace Analysis report " figure has been replaced with the following figure:

Figure. Overview and RAA BASE sections of the Freespace Analysis report
(Figure 152 in PDF and BookManager formats)


Description of %FREESPACE SDEP has been changed as follows:

%FREESPACE SDEP
Shows the total amount of usable, unused space, Start of changeLB, and LE information End of change in the SDEP part at the time of run. Data for this calculation is obtained from the DMAC.


The "DOVF and IOVF sections of the Freespace Analysis report " figure has been replaced with the following figure:

Figure. DOVF and IOVF sections of the Freespace Analysis report
(Figure 153 in PDF and BookManager formats)


-----------------
>>>> 2.12.14.2 DB Record Profile Analysis report

The following description has been added:

Start of changeWhen SEGLSTAT=DETAILED is specified, the report contains prefix length and data flags. This additional information is helpful in database tuning.
Note: The ACTUAL LENGTH field does not include the length of prefix. End of change

The "DB Record Profile Analysis report" figure has been replaced with the following figure. Also the title has been changed to DB Record Profile Analysis report with SEGLSTAT=COMPACT.

Figure. DB Record Profile Analysis report Start of changewith SEGLSTAT=COMPACT End of change
(Figure 154 in PDF and BookManager formats)


The following description and figure have been added:

Start of changeThe following figure shows another example of the report when SEGLSTAT=DETAILED is specified. End of change

Start of changeFigure. DB Record Profile Analysis report with SEGLSTAT=DETAILED End of change


The following description has been added below the report examples:

Start of change
DEFINED LENGTH
    Shows the prefix length, maximum and minimum segment lengths, and data flag that are defined in the DBD. Data flag of the segment is as follows:
    F
      Fixed-length segment
    V
      Variable-length segment
    C
      Compressed segment
    Note: ACBGEN ignores the minimum length that is specified in the DBD and substitutes key length plus key offset with a minimum value of 4.
End of change

-----------------
>>>> 2.12.14.4 Segment Placement Analysis report

The following note item has been added:

Start of changeNote: SDEP information is displayed only if SDEP is defined. N/A is displayed when SDEPCHKLVL=NONE (FPA) or SDEP=NO (FPO) is specified. End of change

The "Segment Placement Analysis report" figure has been replaced with the following figure:

Figure. Segment Placement Analysis report
(Figure 156 in PDF and BookManager formats)


-----------------
>>>> 2.12.16 UOW report

The "UOW report" figure has been replaced with the following figure:

Figure. UOW report
(Figure 160 in PDF and BookManager formats)


=================
> 4.0 IMS Fast Path Online Tools
>> 4.2 Analyzing a DEDB online with FPO
>>> 4.2.10 Examples for OPC

The following new example has been added:

Start of change
Example 8: Generating reports that contain SDEP record information, prefix length, and data flags

The following figure shows example JCL for generating the reports that contain SDEP record information, prefix length, and data flags to facilitate the diagnosis of the database.

In this example:
  • SDEP=YES for the ANALYZE command specifies that Segment Placement Analysis report with SDEP information is generated.
  • SEGLSTAT=DETAILED keyword specifies that the DB Record Profile Analysis report with prefix length and data flags is generated.

//ANALYZE      EXEC FPUTIL,DBD=DEDBJN23,IMSID=IMS1
//*
//FPU.STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//             DD DISP=SHR,DSN=IMSVS.SDFSRESL
//FPXMFILE DD SYSOUT=*
//FPXRPTS  DD SYSOUT=*
//FPXSPRT  DD SYSOUT=*
//FPXIN    DD *
  GLOBAL
    ITKBSRVR=FPQSVR01
  ANALYZE
        AREA=ALL
        TYPRUN=RPT,
        SDEP=YES,
        FULLSTEP=YES
   REPORT
      SEGLSTAT=DETAILED
/*
Figure. Generating reports that contain SDEP record information, prefix length, and data flags
End of change

-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.2 FPO control statements
>>>> 4.7.2.11 REPORT

The SEGLSTAT keyword has been added to the Related keywords section and the Syntax section.

-----------------
>>> 4.7.3 FPO keywords

The following new topic has been added:

Start of change
SEGLSTAT

The SEGLSTAT keyword specifies the format of the DB Record Profile Analysis report, which is one of the DEDB Area Analysis reports.

SEGLSTAT is an optional keyword for the REPORT control statement.

Format:

             
>>---SEGLSTAT=--+--COMPACT---+-----------><
                +--DETAILED--+


The variable field is defined as follows:
    COMPACT
      The DB Record Profile Analysis report provides analysis information of the database records. It does not include details such as prefix length and data flags.
    DETAILED
      The DB Record Profile Analysis report provides prefix length and data flags in addition to the default contents. This additional information is helpful in database tuning.


Default: COMPACT, if the SEGLSTAT keyword is not specified.

Site default support: Supported.
End of change

=================
> 6.0 References
>> 6.1 DEDB monitoring and tuning guide
>>> 6.1.5 JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.1 FPA Analyze JCL examples for monitoring and tuning DEDBs

Another example has been added to the "Example 6: Generating reports to obtain database records and randomizing information" section:

Start of change
The following figure shows example JCL for generating the reports that contain SDEP record information, prefix length, and data flags to facilitate the diagnosis of the database.

In this example:
  • SDEPCHKLVL=FULL for the ANALYZE command specifies that the Segment Placement Analysis report with SDEP information is generated.
  • SEGLSTAT=DETAILED keyword specifies that the DB Record Profile Analysis report with prefix length and data flags is generated.

//HFP      EXEC PGM=HFPMAIN0
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB   DD DISP=SHR,DSN=IMSVS.ACBLIB
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
GLOBAL
  DBRC=YES
ANALYZE
  DBD=DEDBJN23,
  IAREA=ALL,
  SDEPCHKLVL=FULL,
  PTRCHKLVL=FULL
REPORT
  SEGLSTAT=DETAILED
Figure. FPA Analyze example 7: Generating reports to obtain SDEP record information, prefix length, and data flags
End of change



Update 8
Date of change: July 2012
Change description: Documentation changes by APAR PM67683. This APAR fixes a DEDB Reload Utility (FABCUR3) abend problem and adds two new messages.
Topic:
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.3 FABC messages

The following messages have been added:

Start of change
FABC3822E - NOT ENOUGH SDEP SPACE AVAIL IN AREA zzzzz (AREANAME: areaname) DUE TO DBD CHANGE
    - THE FIRST CI RBA IN THE NEW SDEP PART: X'xxxxxxxx'
    - REQUIRED SDEP SPACE: X'xxxxxxxx'

Explanation: Program FABCUR1 unload subtask identified that the ESDS data set for the indicated area will not have enough space for the SDEP part (range between LB and LE) even if the ESDS data set is defined with the maximum size.
System action: The unload subtask ends with an abend code of 3822.
User response: Change the database definition so that enough space is available for the SDEP part, or delete SDEP segments so that the required amount of SDEP space is reduced. Then rerun the unload job.
End of change
-----------------
Start of change
FABC3823E - THE FORMAT OF THE USR FILE IS OLD. REGENERATE THE USR FILE

Explanation: Program FABCUR3 found that the SDEP flag field (USRSDEP) in the area information record of the input USR file is "PN". Such USR files are no longer supported.
System action: FABCUR3 ends with an abend code of 3823.
User response: Rerun the unload job with SDEP=PHYSICAL accompanied by a DBD change to regenerate the input USR file. Then rerun the reload job.
End of change



Update 7
Date of change: July 2012
Change description: Documentation changes by APAR PM60111. This APAR enhances the Online Pointer Checker and the Online Expert Reorganization utilities to store sensor data and generate free space analysis reports.
Topics: Changes are made to the following multiple topics.

> 4.0 IMS Fast Path Online Tools
>> 4.2 Analyzing a DEDB online with FPO
>>> 4.2.3 Considerations for running OPC
>>>> 4.2.3.1 Selecting the operating modes

In the following table, "Analysis and report" column for TYPRUN=FS has been changed as follows:

Table. TYPRUN= values and associated functions
(Table 95 in PDF and BookManager formats)
TYPRUN= Integrity verification Analysis and report
... ... ...
FS ... Start of change
When FULLSTEP=YES:
  • Freespace Analysis reports only
  • Optional Reorg control statement generation
  • Optional threshold analysis (freespace variables only)

When FULLSTEP=NO:
  • Freespace Analysis reports only
  • Optional Reorg control statement generation
  • Optional History file update
  • Optional History2 file update
  • Optional threshold analysis (freespace variables only)
End of change
... ... ...


-----------------
>>>> 4.2.3.2 Data sets required for each operating mode

"Input and output data sets for each specification of TYPRUN= and FULLSTEP=" table has been changed as follows:

Table. Input and output data sets for each specification of TYPRUN= and FULLSTEP=
(Table 96 in PDF and BookManager formats)
TYPRUN= FULLSTEP= Required input data sets Required output data sets Optional output data sets
PTRSCAN N/A SYSIN and DASYSIN SYSPRINT FPXMFILE, FPXRPTS, SNAPPIT
NO FPXIN SYSPRINT FPXMFILE, FPXRPTS, Start of changeFPXSPRT,End of change SNAPPIT
FS N/A SYSIN and DASYSIN SYSPRINT, DAR12O, SORT12 FPXMFILE, FPXRPTS, SNAPPIT
NO FPXIN SYSPRINT,DAR12O, SORT12 FPXMFILE, FPXRPTS, Start of changeFPXSPRT,End of change SNAPPIT
Start of changeYESEnd of change Start of changeFPXINEnd of change Start of changeSYSPRINTEnd of change Start of changeFPXMFILE, FPXRPTS, FPXSPRT, SNAPPIT, FPXARERGEnd of change
MODEL NO FPXIN SYSPRINT, DAR12O, SORT12, DAR13SO, DAR3CSO, SORT3CS FPXMFILE, FPXRPTS, SNAPPIT
PTRALL N/A SYSIN and DASYSIN SYSPRINT, DAR13SO, DAR3CSO, SORT13CS FPXMFILE, FPXRPTS, SNAPPIT
NO FPXIN SYSPRINT, DAR13SO, DAR3CSO, SORT13CS FPXMFILE, FPXRPTS, Start of changeFPXSPRT,End of change SNAPPIT
YES FPXIN SYSPRINTStart of change , SYSOUT End of change FPXMFILE, FPXRPTS, Start of changeFPXSPRT,End of change SNAPPIT
RPT N/A SYSIN and DASYSIN SYSPRINT, DAR12O, SORT12, DAR13SO, DAR3CSO, SORT23CS FPXMFILE, FPXRPTS, SNAPPIT
NO FPXIN SYSPRINT, DAR12O, SORT12, DAR13SO, DAR3CSO, SORT3CS FPXMFILE, FPXRPTS, Start of changeFPXSPRT,End of change SNAPPIT
YES FPXIN SYSPRINTStart of change , SYSOUT End of change FPXMFILE, FPXRPTS, FPXSPRT, SNAPPIT, Start of change FPXAUOWC ,End of change FPXAHST, FPXAHST2, FPXARERG

Start of changeFor TYPRUN=FS and FULLSTEP=YES, DAR12O DD and SORT12 DD will be dynamically allocated by OPC. If any of them are specified, it will be used as an output data set by OPC. End of change

For TYPRUN=PTRALL and FULLSTEP=YES, DAR13SO DD, DAR3CSO DD, and SORT13CS DD will be dynamically allocated by OPC. If any of them are specified, it will be used as an output data set by OPC.

-----------------
>>> 4.2.6 DD statements for OPC

"DD statements for OPC" table has been changed as follows:

Table. DD statements for OPC
(Table 98 in PDF and BookManager formats)
DDNAME Use Format Required or optional
... ... ... ...
FPXSPRT Output LRECL=133 Start of changeOptionalEnd of change
... ... ... ...

DD descriptions have been changed as follows:

reportdd DD
...
The output can go to a data set or to a printer, routed through the output stream. FPXRPTS is the default DD name, however, the DD name can be overridden by the REPORTDD keyword specification of the REPORT control statement. This statement is used only when you specify the Start of changeTYPRUN=RPT and the FULLSTEP=YES keywords, or the TYPRUN=FS and the FULLSTEP=YES keywords. End of change
...

FPXARERG DD
Defines an output data set that contains the reorganization control statements for the High-Speed DEDB Direct Reorganization utility (DBFUHDR0). This statement is used only when you specify the Start of changeTYPRUN=RPT and the FULLSTEP=YES keywords, or the TYPRUN=FS and the FULLSTEP=YES keywords. End of change
...

i001WK nn DD
An optional DD statement. These are intermediate storage data sets that are used by DFSORT. For more information about coding the SORTWKnn DD statements, see the DFSORT Application Programming Guide. The adequate size of storage data sets is 1.5 to 2.5 times the input file size. This statement is used only when you specify the FULLSTEP=YES keyword.
Start of changeAllocating twice the space used by the SORTIN data set is usually adequate for each work data set. End of change
In the analyze step, the size of each input file is as follows:
    i :
      A: Always used
        30 x the number of pointers in the area
      D: If SDEP=YES is specified
        30 x the number of SDEP segments in the area
      G: If SNAPPIT DD is specified
        112 x the number of pointers in which pointer errors are detected
      J: If TYPRUN=RPT is specified
        X x ( the number of non-SDEP segments in the areas + the number of free space elements in the areas + the number of references to other CIs)
          Where X is: Start of change
          • 34 + ( the maximum segment level x 4)
            Allocating twice the space used by the SORTIN data set is usually adequate for each work data set.
          • When LARGEREC_REPORT=NO is specified, X is calculated as follows:
              34 + ( the maximum segment level x 4)
              However, if X is smaller than 48, 48 is used for X.
          • When LARGEREC_REPORT=YES is specified, X is calculated as follows:
              34 + ( the maximum segment level x 4) + root key length
              However, if X is smaller than 48, 48 is used for X.
        If TYPRUN=FS is specified
        23 x ( the number of free space elements in the area + the number of references to other CIs) End of change
      Q: Always used
        34 x the number of segments in the area

-----------------
>>> 4.2.8 Utility control statements for OPC

Description for the REPORT statement keywords has been changed as follows:

REPORT statement keywords

The REPORT control statement specifies the parameter values Start of changerelated to the analysis reports. This control statement is effective only when the FULLSTEP=YES keyword is specified together with the TYPRUN=RPT or the TYPRUN=FS keyword. Otherwise, this control statement is ignored. End of change

-----------------
>>> 4.2.9 Output for OPC
>>>> 4.2.9.1 FPXRPTS DD data set

The following description has been added:

Start of changeWhen the TYPRUN=FS keyword and the FULLSTEP=YES keyword are specified, the following reports are produced in the data set or in the output stream depending on the REPORTDD keyword of the REPORT control statement:
  • Processing Summary of Analysis report
  • DEDB Area Analysis report:
    • Freespace Analysis report
      • Summary section
      • Overview and RAA BASE section
      • DOVF and IOVF sections
  • UOW report (without DB record information)
  • UOW Exception report (without DB record information) End of change

When the TYPRUN=RPT keyword and the FULLSTEP=YES keyword are specified, ...

Description of each report has been changed as follows:

Processing Summary of Analysis report
This report contains the processing information of the analysis report.
The report is produced by the Analyze function of FPA, which is called by OPC internally when TYPRUN=RPT and FULLSTEP=YES are specified, Start of changeor when TYPRUN=FS and FULLSTEP=YES are specified. End of change

DEDB Area Analysis reports
...
The DEDB Area Analysis reports are produced by the Analyze function of FPA, which is called by OPC internally when TYPRUN=RPT and FULLSTEP=YES are specified. Start of changeWhen TYPRUN=FS and FULLSTEP=YES are specified, only the Freespace Analysis report is produced. End of change

UOW report
...
The UOW report is produced by the Analyze function of FPA, which is called by OPC internally when TYPRUN=RPT and FULLSTEP=YES are specified, Start of changeor when TYPRUN=FS and FULLSTEP=YES are specified. End of change

UOW Exception report
...
The UOW exception report is produced by the Analyze function of FPA, which is called by OPC internally when TYPRUN=RPT and FULLSTEP=YES are specified, Start of changeor when TYPRUN=FS and FULLSTEP=YES are specified. End of change

-----------------
>> 4.5 Reorganizing a DEDB online with FPO
>>> 4.5.5 DD statements for OER

"DD statements for OER" table has been changed as follows:

Table. DD statements for OER
(Table 118 in PDF and BookManager formats)
DDNAME Use Format Required or optional
...
FPXSPRT Output LRECL=133 Start of changeOptionalEnd of change
...
DD descriptions have been changed as follows:

reportdd DD
...
The output can go to a data set or to a printer, routed through the output stream. FPXRPTS is the default DD name, however, the DD name can be overridden by the REPORTDD keyword specification of the REPORT control statement. This statement is used only when you specify the Start of changeTYPRUN=RPT and the FULLSTEP=YES keywords, or the TYPRUN=FS and the FULLSTEP=YES keywords. End of change
...

FPXARERG DD
Defines an output data set that contains the reorganization control statements for the High-Speed DEDB Direct Reorganization utility (DBFUHDR0). This statement is used only when you specify the Start of changeTYPRUN=RPT and the FULLSTEP=YES keywords, or the TYPRUN=FS and the FULLSTEP=YES keywords. End of change
...

i001WK nn DD
An optional DD statement. These are intermediate storage data sets that are used by DFSORT. For more information about coding the SORTWKnn DD statements, see the DFSORT Application Programming Guide. The adequate size of storage data sets is 1.5 to 2.5 times the input file size. This statement is used only when you specify the FULLSTEP=YES keyword.
Start of changeAllocating twice the space used by the SORTIN data set is usually adequate for each work data set. End of change
In the analyze step, the size of each input file is as follows:
    i :
      A: Always used
        30 x the number of pointers in the area
      D: If SDEP=YES is specified
        30 x the number of SDEP segments in the area
      G: If SNAPPIT DD is specified
        112 x the number of pointers in which pointer errors are detected
      J: If TYPRUN=RPT is specified
        X x ( the number of non-SDEP segments in the areas + the number of free space elements in the areas + the number of references to other CIs)
        Where X is: Start of change
        • 34 + ( the maximum segment level x 4)
          Allocating twice the space used by the SORTIN data set is usually adequate for each work data set.
        • When LARGEREC_REPORT=NO is specified, X is calculated as follows:
            34 + ( the maximum segment level x 4)
            However, if X is smaller than 48, 48 is used for X.
        • When LARGEREC_REPORT=YES is specified, X is calculated as follows:
            34 + ( the maximum segment level x 4) + root key length
            However, if X is smaller than 48, 48 is used for X.
        If TYPRUN=FS is specified
          23 x ( the number of free space elements in the area + the number of references to other CIs) End of change
      Q: Always used
        34 x the number of segments in the area

-----------------
>>> 4.5.7 Utility control statements for OER

Description for the REPORT statement keywords has been changed as follows:

...
REPORT statement keywords

Start of changeThe REPORT control statement specifies the parameter values related to the analysis reports. This control statement is effective only when the PTRCHK=YES keyword is specified on the REORG control statement and either of the following keyword combinations exists on the PTRCHK control statement:
  • FULLSTEP=YES and TYPRUN=RPT
  • FULLSTEP=YES and TYPRUN=FS
End of change
-----------------
>>> 4.5.8 Output for OER
>>>> 4.5.8.1 FPXRPTS DD data set

Description in the Detailed area statistics report section has been changed as follows:

Detailed area statistics reports

Start of change
If PTRCHK=YES keyword is specified for the REORG control statement, and the TYPRUN=FS keyword and the FULLSTEP=YES keyword are specified for the PTRCHK control statement, the following reports are produced in the data set or in the output stream depending on the REPORTDD keyword of the REPORT control statement:
  • Processing Summary of Analysis report
  • DEDB Area Analysis report:
    • Freespace Analysis report
      • Summary section
      • Overview and RAA BASE section
      • DOVF and IOVF sections
  • UOW report (without DB record information)
  • UOW Exception report (without DB record information)
End of change

If PTRCHK=YES keyword is specified for the REORG control statement, and the TYPRUN=RPT keyword and the FULLSTEP=YES keyword are specified for the PTRCHK control statement, the following reports are produced in the data set or in the output stream depending on the REPORTDD keyword of the REPORT control statement:
...

-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.2 FPO control statements
>>>> 4.7.2.11 REPORT

Description has been changed as follows:

Start of changeThe REPORT control statement specifies the parameter values related to the analysis reports.
This control statement is effective only when the FULLSTEP=YES keyword is specified together with the TYPRUN=RPT or the TYPRUN=FS keyword. Otherwise, this control statement is ignored.
The keywords that can be specified on the REPORT statement are similar to those of the Analyze function of FPA. End of change

-----------------
>>> 4.7.3 FPO keywords
>>>> 4.7.3.8 CHKUOW

Description has been changed as follows:
...
CHKUOW=REORGED can be specified only Start of changewhen TYPRUN=PTRSCAN, SENSOR=NO, End of change and SDEP=NO are specified. If CHKUOW=REORGED is specified, IC=YES cannot be specified.
...

-----------------
>>>> 4.7.3.29 FULLSTEP

Description has been changed as follows:
...
YES
    If TYPRUN=PTRALL is specified, OPC checks cross-reference of pointers. If TYPRUN=RPT, OPC performs all functions of the FULLSTEP=YES and the TYPRUN=PTRALL mode, and also produces complete analysis reports. Start of changeIf TYPRUN=FS is specified, OPC produces free space analysis reports. End of change

Restrictions:
...
  • A specification of YES is mutually exclusive with TYPRUN=PTRSCAN or TYPRUN=MODEL.

-----------------
>>>> 4.7.3.81 SENSOR

Description has been changed as follows:
...
Restrictions:
  • Start of change SENSOR=YES is effective only when FULLSTEP=YES and TYPRUN=RPT are specified.
  • SENSOR=YES is mutually exclusive with TYPRUN=MODEL.End of change

-----------------
>>>> 4.7.3.81 SENSOR_DBREC

Description has been changed as follows:
...
Restrictions:
  • Start of change SENSOR_DBREC=YES is mutually exclusive with SENSOR=NO.
  • When you specify SENSOR_DBREC=YES, you must also specify SENSOR=YES, TYPRUN=RPT, and FULLSTEP=YES. End of change

-----------------
>>>> 4.7.3.82 SENSOR_UOW

Description has been changed as follows:
...
Restrictions:
  • When you specify SENSOR_UOW=YES, you must also specify SENSOR=YES, SENSOR_DBREC=YES, Start of changeTYPRUN=RPT, and FULLSTEP=YES. End of change

-----------------
>>>> 4.7.3.99 TYPRUN

Description has been changed as follows:
...
When this keyword is used with the PTRCHK statement, you must specify CHKUOW=ALL to specify TYPRUN=RPT, TYPRUN=PTRALL, Start of changeTYPRUN=FS, or TYPRUN=MODEL. End of change
...

RPT
    Start of changeWhen this mode is specified, the behavior and the output from the job depends on the FULLSTEP keyword specification as follows:
    • When FULLSTEP=YES is specified, OPC scans the database in the FULL mode and generates complete analysis reports.
    • When FULLSTEP=NO is specified, OPC scans the database in the QUICK mode and generates output records that are required by DEDB Pointer Checker. DEDB Pointer Checker uses these records to run the integrity verification in the FULL mode and to generate complete analysis reports.End of change
    ...

PTRSCAN
    When this mode is specified, OPC scans the database Start of changein the QUICK mode End of change without creating any output records for further analysis and reporting. Messages are generated if any pointer integrity errors are detected. The exact RBA of some errors cannot be reported in this mode.
    ...

PTRALL
    Start of changeWhen this mode is specified, the behavior and the output from the job depends on the FULLSTEP keyword specification as follows:
    • When FULLSTEP=YES is specified, OPC scans the database in the FULL mode.
    • When FULLSTEP=NO is specified, OPC scans the database in the QUICK mode and generates output records that are required by DEDB Pointer Checker. DEDB Pointer Checker uses these records to run the integrity verification in the FULL mode. End of change
    The exact RBA of the error is reported in this mode. Any output records associated with further analysis of the database are not generated in this mode.
    ...

FS
    Start of changeWhen this mode is specified, the behavior and the output from the job depends on the FULLSTEP keyword specification as follows:
    • When FULLSTEP=YES is specified, OPC scans the database in the QUICK mode and generates free space analysis reports.
    • When FULLSTEP=NO is specified, OPC scans the database in the QUICK mode and generates the output records that are required by DEDB Pointer Checker. DEDB Pointer Checker uses these records to analyze and report free space information.End of change
    ...

MODEL
    When this mode is specified, Start of changeOPC scans the database in the QUICK mode and generates output records that are required by DEDB Pointer Checker. DEDB Pointer Checker uses these records to run the integrity verification in the FULL mode and to generate complete analysis reports. End of change OPC also generates segment information records including the root key, which can be used as input for FPB DEDB Tuning Aid.
    ...

Restrictions:
  • A specification of PTFSCAN, Start of change FS, End of change or MODEL is mutually exclusive with FULLSTEP=YES.
  • TYPRUN=MODEL can be specified only in FPXIN.
  • TYPRUN=MODEL cannot be specified on the PTRCHK statement.
  • Only the following operating modes are supported when processing multiple areas:
    • PTRSCAN
    • Start of changeFS when FULLSTEP=YES is specifiedEnd of change
    • PTRALL when FULLSTEP=YES is specified
    • RPT when FULLSTEP=YES is specified


=================
> 6.0 References
>> 6.1 DEDB monitoring and tuning guide
>>> 6.1.2 Collecting and storing statistical data for DEDB areas
>>>> 6.1.2.3 Storing data in the Sensor Data repository of IMS Tools KB

Description for OPC and OER has been changed as follows:
...
With OPC and the internal OPC process in OER, Start of change values of all data items are always collected and stored if the Sensor Data repository is used. you can choose to collect all the statistics data items or only a subset of the data items. To collect all the data items, you must specify TYPRUN=RPT and FULLSTEP=YES. End of change

...


Storing data by using a function of FPA

Changes have been made to Step 3:

To store the sensor data in the Sensor Data repository by using the FPA Analyze function, the FPA Change function, the FPA Reload function, or the FPA Reorg function, specify the following options for the HFPSYSIN control statements:
  1. Specify the ITKBSRVR keyword for the GLOBAL command, and specify the IMS Tools KB XCF group name for its parameter.
  2. Specify the SENSOR=YES option for the function command.
  3. If you want to collect all the data items, specify the PTRCHKLVL=FULL option, the SENSOR_DBREC=YES option, Start of changeand the SENSOR_UOW=YES optionEnd of change for the function command.
    Notes:
    • If you want to collect only the subset of the data items, you can skip this step.
    • If you do not want to store the sensor data for the data elements that belong to the synonym chain length, root I/O, and record I/O categories in the Sensor Data repository, specify SENSOR_DBREC=NO. For a list of data elements that are collected by the SENSOR_DBREC keyword, see "SENSOR_DBREC" in topic 2.11.4.92.
    • Start of changeIf you do not want to store the sensor data for the data elements that are related to UOW in the Sensor Data repository, specify SENSOR_UOW=NO.End of change


Storing data by using OPC

The steps for storing data by using OPC have been changed as follows:

To store the sensor data in the Sensor Data repository by using OPC, specify the following options for the FPXIN control statements:
  1. Specify the ITKBSRVR keyword for the GLOBAL statement, and specify the IMS Tools KB XCF group name for its parameter.
  2. Specify the SENSOR=YES option for the ANALYZE statement.
  3. Start of changeIf you want to collect all the data items, specify the following options for the ANALYZE statement:
    • TYPRUN=RPT
    • FULLSTEP=YES
    • SENSOR_DBREC=YES
    • SENSOR_UOW=YES
    If you want to collect only the subset of the data items, specify one of the following options:
    • TYPRUN=PTRSCAN
    • TYPRUN=FS
    • TYPRUN=PTRALL
    • TYPRUN=RPT and FULLSTEP=NO
    Notes:
    • If you do not want to store the sensor data for the data elements that belong to the synonym chain length, root I/O, and record I/O categories in the Sensor Data repository, specify SENSOR_DBREC=NO. For a list of data elements that are collected by the SENSOR_DBREC keyword, see "SENSOR_DBREC" in topic 4.7.3.82.
    • If you do not want to store the sensor data for the data elements that are related to UOW in the Sensor Data repository, specify SENSOR_UOW=NO.End of change

You can find a coding example in "Online Pointer Checker JCL examples for monitoring and tuning DEDBs" in topic 6.1.5.6.

Storing data by using OER

The steps for storing data by using OER have been changed as follows:

To store the sensor data in the Sensor Data repository by using OER, specify the following options for the FPXIN control statements:
1. Specify the ITKBSRVR keyword for the GLOBAL statement, and specify the IMS Tools KB XCF group name for its parameter.
2. Specify the PTRCHK=YES option for the REORG statement to call the OPC process.
3. Specify the SENSOR=YES option for the PTRCHK statement.
4. Start of changeIf you want to collect all the data items, specify the following options for the PTRCHK statement:
    • TYPRUN=RPT
    • FULLSTEP=YES
    • SENSOR_DBREC=YES
    • SENSOR_UOW=YES
    If you want to collect only the subset of the data items, specify one of the following options:
    • TYPRUN=PTRSCAN
    • TYPRUN=FS
    • TYPRUN=PTRALL
    • TYPRUN=RPT and FULLSTEP=NO
    Notes:
    • If you do not want to store the sensor data for the data elements that belong to the synonym chain length, root I/O, and record I/O categories in the Sensor Data repository, specify SENSOR_DBREC=NO. For a list of data elements that are collected by the SENSOR_DBREC keyword, see "SENSOR_DBREC" in topic 4.7.3.82.
    • If you do not want to store the sensor data for the data elements that are related to UOW in the Sensor Data repository, specify SENSOR_UOW=NO.End of change
5. Specify the CHKUOW=ALL option for the PTRCHK statement.
    Note: The options specified for the PTRCHK statement are applied to the OPC process.

You can find a coding example in "Online Expert Reorganization JCL examples for monitoring and tuning DEDBs" in topic 6.1.5.7.

Storing data by using Stand-alone DB Sensor

A note item has been added as follows:

To store the sensor data in the Sensor Data repository by using Stand-alone DB Sensor, run the DB Sensor job.

Notes:
  • If you do not want to store the sensor data for the data elements that belong to the synonym chain length, root I/O, and record I/O categories in the Sensor Data repository, specify SENSOR_DBREC=NO.
  • Start of changeIf you do not want to store the sensor data for the data elements that are related to UOW in the Sensor Data repository, specify SENSOR_UOW=NO. End of change

For information about using Stand-alone DB Sensor and coding examples, see the IMS Solution Packs: Database Sensor User's Guide.

-----------------
>>> 6.1.5 JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.6 Online Pointer Checker JCL examples for monitoring and tuning DEDBs

The following new subsection has been added:

Start of change
Example 9: Generating free space analysis reports

The following figure shows example JCL for generating the reports that are required for free space analysis.
In this example, TYPRUN=FS for the ANALYZE statement specifies that the Freespace Analysis report is generated.


//OPC      EXEC FPUTIL,DBD=DEDBJN22,IMSID=IMS1
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=ITBVS.SHKTLOAD
//FPXIN    DD *

  ANALYZE AREA=(DB22AR0,DB22AR1),
    FULLSTEP=YES,
    TYPRUN=FS
/*

Figure. Online Pointer Checker example 9: Generating reports for free space analysis
End of change

-----------------
>>>> 6.1.5.7 Online Expert Reorganization JCL examples for monitoring and tuning DEDBs

The following new subsection has been added:

Start of change
Example 9: Generating free space analysis reports

The following figure shows example JCL for generating the reports that are required for free space analysis.
In this example, TYPRUN=FS for the PTRCHK statement specifies that the Freespace Analysis report is generated.


//OPC      EXEC FPUTIL,DBD=DEDBJN22,IMSID=IMS1
//STEPLIB  DD DISP=SHR,DSN=HPFP.SHFPLMD0
//         DD DISP=SHR,DSN=IMSVS.SDFSRESL
//         DD DISP=SHR,DSN=ITBVS.SHKTLOAD
//FPXIN    DD *

  REORG AREA=(DB22AR0,DB22AR1),
         PTRCHK=YES
       PTRCHK
         TYPRUN=FS,
         CHKUOW=ALL,
         FULLSTEP=YES
/*

Figure. Online Expert Reorganization example 9: Generating reports for free space analysis
End of change

-----------------
>> 6.3 Record layouts
>>> 6.3.1 Historical records layout

Description has been changed as follows:

These topics present the layouts for the historical records that are created by the FPA Analyze function, the FPB DEDB Pointer Checker utility, Start of changeand the OPC utility. End of change

-----------------
>>>> 6.3.1.1 History file records layout

Description has been changed as follows:

History file records are created by the FPA Analyze function, the FPB DEDB Pointer Checker utility, Start of changeand the OPC utility. End of change
...
You can use Start of changethe HFPAMHST macro (FPA and FPO) End of change or the FABAMHST macro (FPB) to map these records.

-----------------
>>>> 6.3.1.2 History file records layout

Description has been changed as follows:

History2 file records are created by Start of changethe FPA Analyze function, the FPB DEDB Pointer Checker utility and the OPC utility. End of change
...
You can use Start of changethe HFPAMHS2 macro (FPA and FPO) or the FABAMHS2 macro (FPB) End of change to map the History2 record in the assembler language.

=================
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.6 FPX messages

The following new messages have been added:

Start of change
FPX0277I The REPORT control statement is ignored.

Explanation: Found a REPORT control statement. However, the REPORT control statement is ignored because analysis reports can be generated only in the following operating modes:
  • TYPRUN=RPT and FULLSTEP=YES
  • TYPRUN=FS and FULLSTEP=YES
System action: Processing continues.
User response: None. This message is informational.
End of change

Start of change
FPX0278I FULLSTEP=YES must be specified in order to generate the analysis reports.

Explanation: Found a REPORT control statement. However, FULLSTEP=YES is not specified and, therefore, analysis reports are not generated.
System action: Processing continues. No analysis reports are generated.
User response: None. This message is informational.
End of change

-----------------
The Explanation section of the FPX0258E message has been changed as follows:

FPX0258E The operating mode specified is not supported in multiple area processing.

Explanation: The operating modes that are supported in multiple area processing are the following modes:
  • TYPRUN=PTRSCAN
  • Start of changeTYPRUN=FS and FULLSTEP=YESEnd of change
  • TYPRUN=PTRALL and FULLSTEP=YES
  • TYPRUN=RTP and FULLSTEP=YES
...



Update 6
Date of change: May 2012
Change description: Documentation changes by APAR PM54862. The Build Index function of FPA can synchronize secondary index databases with their primary DEDB database.
Topics: Changes are made to the following multiple topics.

>1.0 Overview of IMS Fast Path Utilities
>> 1.1 What is IMS HP Fast Path Utilities?
>>> 1.1.3 Support for Tools Base

The description in the "IMS Tools Online System Interface" section has been changed as follows:

Start of changeIn IMS HP Fast Path Utilities, IMS Tools Online System Interface is used by the following functions:
  • The FPA Build Index function (INDEXBLD command) when the RESYNC option is used. For more information about the RESYNC option, see "Functions of Build Index" in topic 2.10.1.
  • The OAE Rename program of the FPO Online Area Extender utility. For more information about the OAE Rename program, see "OAE Rename program" in topic 4.4.11. End of change

=====================
> 2.0 IMS Fast Path Advanced Tool
>> 2.10 Building secondary index databases for a DEDB offline with FPA
>>> 2.10.1 Functions of Build Index

The following description has been added:

The Build Index function has the following characteristics:
  • ...
  • ...
  • Start of changeIt synchronizes a DEDB and its secondary index databases when they are out of synchronization.
    • For example, if a DEDB is updated with the index suppression option in a BMP region, its secondary index databases are not updated. As a result, the DEDB and its secondary index databases are out of synchronization.
    • Build Index jobs run against online areas. However, secondary index databases will experience a short outage while they are resynchronized.End of change

-----------------
>>> 2.10.2 Input and output for the Build Index process

This topic has been replaced with the following contents:

The Build Index function is invoked by the INDEXBLD command in the HFPSYSIN DD control statement. Start of changeWhen IDXPROC=BUILD is specified, it scans multiple DEDB areas and builds multiple secondary index databases. When IDXPROC=RESYNC is specified, it scans multiple DEDB areas and secondary index databases, then resynchronizes multiple secondary index databases. End of change

The following figure shows the input and the output for the Build Index process Start of changewhen IDXPROC=BUILD is specified. End of change


Figure xxx. Input and output for the Build Index process Start of changewith IDXPROC=BUILD End of change

The Build Index function with Start of changeIDXPROC=BUILD End of change can also read and scan the following image copies of a DEDB:
  • Standard image copies that are created by the IMS Image Copy utility (DFSUDMP0) or IMS HP Image Copy
  • Compressed image copies that are created by IMS HP Image Copy

Start of changeThe following figure shows the input and the output for the Build Index process when IDXPROC=RESYNC is specified. End of change


Start of changeFigure xxx. Input and output for the Build Index process with IDXPROC=RESYNC End of change

Start of changeThe Build Index function with IDXPROC=RESYNC cannot read or scan image copies of a DEDB. End of change

Restriction: Unlike other functions of FPA, the Build Index function cannot internally invoke IMS HP Image Copy to create image copies.


-----------------
>>> 2.10.5 DD statements for the Build Index process

Input DD statements

The following description has been added to the JOBLIB/STEPLIB DD description:
  • Start of changeThe Tools Base library (SFOILOAD, SGLXLOAD) if you specify the IDXPROC=RESYNC option.End of change
The description of HFPRPTS DD has has been changed as follows:
...
The following reports are generated in this data set:
  • Audit report
  • Processing report
  • DBD Definition report
  • Secondary Index Definition report
  • Start of changeSecondary Index Processing report (when IDXPROC=BUILD is specified)
  • Secondary Index Resync report (when IDXPROC=RESYNC is specified)End of change

The description of IMS DD has been changed as follows:
    This DD statement is required Start of changewhen DBRC=YES for the GLOBAL command and IDXPROC=BUILD for the INDEXBLD command are both specified. End of change This statement is used when the NOTIFY.REORG command is issued to DBRC. This statement defines the library that contains the DBD that describes the secondary index databases.

Output DD statements

The description of index DD has been changed as follows:
    Start of changeThis DD statement is a required output DD statement when the IDXPROC=BUILD option is used. This DD statement defines the VSAM KSDS data set to be loaded. End of change

The following description has been added to the indexovrflw DD:
    Start of changeThis DD statement is a required output DD statement when the IDXPROC=BUILD option is used. This DD statement defines the VSAM ESDS data set to be loaded. End of change

Input/Output DD statements

The following DD statement descriptions have been added:
Start of change
index DD
    This DD statement is a required DD statement when the IDXPROC=RESYNC option is used. This DD statement defines the VSAM KSDS data set to be synchronized. The DD name must be the DD name for the secondary index database that is defined in the input ACB library (IMSACB DD). Multiple index DD statements can be specified for each secondary index database that is built by the Build Index function.
    The data set that is used by FPA is determined by the following factors:
    • The name of the secondary index database member in the IMS DFSMDA library
    • The index DD JCL statement
End of change
Start of change
indexovrflw DD
    This DD statement is a required DD statement when the IDXPROC=RESYNC option is used. This DD statement defines the VSAM ESDS data set to be synchronized. The DD name must be the DD name for the secondary index database that is defined in the input ACB library (IMSACB DD). Multiple indexovrflw DD statements can be specified for each secondary index database that is built by the Build Index function.

    The data set that is used by FPA is determined by the following factors:
    • The name of the secondary index database member in the IMS DFSMDA library
    • The indexovrflw DD JCL statement
End of change
-----------------
>>> 2.10.6 Utility control statements for the Build Index process

The following new keywords have been added:

Table x. GLOBAL command keywords
(Table 50 in PDF and BookManager formats)
Keyword Description
Start of changeTOINUM An optional keyword that specifies the number of retries for issuing the command to obtain a response from IMS Tools Online System Interface. End of change
Start of changeTOITIME An optional keyword that specifies the time limit for obtaining a response from IMS Tools Online System Interface. End of change
Start of changeTOIXCFGRP An optional keyword that specifies the XCF group that IMS Tools Online System Interface uses to interface with FPA. End of change

Table x. INDEXBLD command keywords
(Table 51 in PDF and BookManager formats)
Keyword Description
Start of changeIDXPROC An optional keyword that specifies whether to build secondary index databases or to synchronize the secondary index databases with their primary DEDB database.End of change
Start of changeTOICTL An optional keyword that specifies whether IMS Tools Online System Interface issues a /DBRECOVERY command or a /DBDUMP command to stop the secondary index databases.End of change

-----------------
>>> 2.10.7 Examples for the Build Index function

The following new example has been added:

Start of change
Example 4: Resynchronizing the DEDB areas and all secondary index databases

The following figure shows example JCL statement for resynchronizing the DEDB areas and all secondary index databases.

In this example:
  • RECON data sets are allocated dynamically by using the DFSMDA members in the IMSDALIB DD data set.
  • The input ADS to be validated is dynamically allocated. The allocation information (DD name and DS name of the ADS) is obtained from DBRC.
  • The resynchronized secondary index database data sets to be validated are dynamically allocated. The allocation information (DD name and DS name of the secondary index database data sets) is obtained from DFSMDA members in the IMSDALIB DD data set.
  • /DBRECOVEY command is issued to stop the secondary index databases. After the resynchronization, /START command is issued to stop the databases.


//HFP EXEC PGM=HFPMAIN0
//STEPLIB DD DISP=SHR,DSN=HPFP.SHFPLMD0
//        DD DISP=SHR,DSN=TOSI.SFOILOAD
//        DD DISP=SHR,DSN=TOSI.SGLXLOAD
//        DD DISP=SHR,DSN=IMSVS.SDFSRESL
//        DD DISP=SHR,DSN=IMSVS.PGMLIB
//IMSACB  DD DISP=SHR,DSN=IMSVS.ACBLIB
//IMSDALIB DD DISP=SHR,DSN=IMSVS.MDALIB
//HFPSYSIN DD *
  GLOBAL DBRC=YES
  INDEXBLD DBD=DEDBJN22,
           IAREA=ALL,
           INDEXDBD=ALL,
           IDXPROC=RESYNC,
           TOICTL=DBR
/*

Figure xx. Resynchronizing the DEDB areas and all secondary index databases.
End of change
-----------------
>> 2.11 Command reference for FPA
>>> 2.11.2 FPA commands
>>>> 2.11.2.6 GLOBAL

TOINUM, TOITIME, and TOIXCFGRP have been added.

-----------------
>>>> 2.11.2.7 INDEXBLD

IDXPROC and TOICTL have been added.

-----------------
>>> 2.11.4 FPA keywords

The following keywords have been added:

Start of change
IDXPROC

Use the IDXPROC keyword to specify whether to build secondary index databases or to synchronize the secondary index databases with their primary DEDB database.

IDXPROC is an optional keyword for the INDEXBLD command.

Related keywords: None.

Format: IDXPROC= parameter

parameter
    Specify one of the following parameters:

    BUILD
      Builds secondary index databases.

    RESYNC
      Synchronizes a primary DEDB database and its secondary index databases.
Default: IDXPROC=BUILD

Site default support: Supported.
End of change
-----------------
Start of change
TOICTL

Use the TOICTL keyword to specify whether IMS Tools Online System Interface issues a /DBRECOVERY command or a /DBDUMP command to stop the secondary index databases.

If you do not specify IDXPROC=RESYNC, this keyword is ignored.

TOICTL is an optional keyword for the INDEXBLD command.

Related keywords: None.

Format: TOICTL= parameter

parameter
    Specify one of the following parameters:

    DBR
      Indicates that a /DBRECOVERY command is issued to stop the secondary index databases.
    DBD
      Indicates that a /DBDUMP command is issued to stop the secondary index databases.

Default: TOICTL=DBR

Site default support: Supported.
End of change
-----------------
Start of change
TOINUM

Use the TOINUM keyword to specify the number of retries for issuing the command to obtain a response from IMS Tools Online System Interface.

If you do not specify IDXPROC=RESYNC, this keyword is ignored.

TOINUM is an optional keyword for the GLOBAL command.

Related keywords: TOITIME

Format: TOINUM= parameter

parameter
    Specify the number of retries for issuing the command. Specify an integer value in the range of 1 - 100.

Default: TOINUM=10

Site default support: Supported.
End of change
-----------------
Start of change
TOITIME

Use the TOITIME keyword to specify the time limit for obtaining a response from IMS Tools Online System Interface.

If you do not specify IDXPROC=RESYNC, this keyword is ignored.
TOITIME is an optional keyword for the GLOBAL command.

Related keywords: TOINUM

Format: TOITIME= parameter

parameter
    Specify, in seconds, the maximum allowable wait time for FPA to obtain a response from IMS Tools Online System Interface that the database has stopped. Specify an integer value in the range of 1 -100.

    If FPA does not receive a response from IMS Tools Online System Interface within the specified time frame, FPA continues to reissue the command until the value specified on the TOINUM keyword is reached. If the maximum retry count is reached and FPA does not receive a response, the HFPX0103E message is issued.

Default: TOITIME=30

Site default support: Supported.
End of change
-----------------
Start of change
TOIXCFGRP

Use the TOIXCFGRP keyword to identify the XCF group that IMS Tools Online System Interface uses to interface with FPA.

If you do not specify IDXPROC=RESYNC, this keyword is ignored.

TOIXCFGRP is an optional keyword for the GLOBAL command.

Related keywords: None.

Format: TOIXCFGRP= parameter

parameter
    Specify the XCF group name. The group name is a 1-5 alphanumeric character string that IMS Tools Online System Interface prefixes with the characters "TOI", to produce the XCF group name.

Default: TOIXCFGRP=*NO

Site default support: Supported.
End of change
-----------------
>> 2.12 Sample reports of FPA
>>> 2.12.1 Reports generated by each process of FPA

Secondary Index Resync report entry has been added to the following table:

Table x. Reports generated by each process of FPA
(Table 52 in PDF and BookManager formats)
FPA process Generated reports Whether the report can be stored in the IMS Tools KB Output repository
Build Index Audit report Y
Processing report Y
DBD Definition report Y
Secondary Index Definition report Y
Secondary Index Processing report Y
Start of changeSecondary Index Resync report YEnd of change

-----------------
>>> 2.12.24 Secondary Index Processing report

The following description has been changed:

This report is generated by the INDEXBLD command Start of changewith IDXPROC=BUILD. End of change

-----------------
>> 2.12 Sample reports of FPA

The following new topic has been added:

Start of change
Secondary Index Resync report

The Secondary Index Resync report provides information about the segments that were inserted to or deleted from the secondary index databases.

This report is generated by the INDEXBLD command with IDXPROC=RESYNC.

This report is not printed if you specified the GLOBAL SCAN=YES keyword.

The following figure is an example of the Secondary Index Resync report.

Figure xxx. Secondary Index Resync report

PRIMARY DEDB NAME
    The name of the primary DEDB.

NUMBER OF SEC. INDEXES
    The number of secondary indexes that were specified. When one or more partitioned indexes were processed, (PARTITION INCLUDED) is printed after the number.

PARTITION GROUP
    The first DBD name in the partition group.

DBDNAME
    The name of the DBD.

DDNAME
    The ddname of the secondary index database data set.

DSNAME
    The name of the data set.

BEFORE RESYNC
    The number of segments before resynchronization.

AFTER RESYNC
    The number of segments after resynchronization.

INSERTED
    The number of segments that were inserted during resynchronization.

DELETED
    The number of segments that were deleted during resynchronization.

Note: The numbers of segments that are reported in this report are the numbers of the segments that point to the input areas.
End of change
-----------------
>> 2.13 Site default options support for FPA
>>> 2.13.1 Available keywords for the site default option

The following keywords have been added:

Table x. Keywords for site default option
(Table 53 in PDF and BookManager formats)
Command/Subcommand Keywords
GLOBAL ...Start of changeTOINUM, TOITIME, TOIXCFGRPEnd of change...
INDEXBLD ...Start of changeIDXPROC, TOICTLEnd of change...

=====================
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.9 HFPB messages

The following message texts, sub text, and descriptions have been changed:

HFPB0003I INDEXBLD Start of change[LOAD|RESYNC] End of change PROCESSING STARTED FOR SECONDARY INDEX DBD: index_dbdbase

Explanation: The load phase Start of changeor the resync phase of the Build Index process End of change for the indicated secondary index database has started.


HFPB0004I INDEXBLD Start of change[LOAD|RESYNC] End of change PROCESSING COMPLETED FOR SECONDARY INDEX DBD: index_dbdbase
      Start of change- THE SECONDARY INDEX DATABASE DID NOT NEED TO BE UPDATED. ALREADY IN SYNC WITH THE DEDB. End of change

Explanation: The load phase Start of changeor the resync phase of the Build Index process for the indicated secondary index database has completed. When the secondary index database is already in sync with the DEDB, the sub text is issued. End of change

-----------------
>>>> 7.1.3.28 HFPX messages

The following messages have been added:

Start of change
HFPX0101I CONNECTED TO IMS THROUGH TOOLS ONLINE SYSTEM INTERFACE. XCF GROUP NAME: TOIxxxxx
      - IMS ID: xxxx

Explanation: The TOSI CONNECT function has completed.
System Action: Processing continues.
User Response: None.
End of change

Start of change
HFPX0102I THE [/DBRECOVERY|/DBDUMP|/START] COMMAND FOR SECONDARY INDEX DATABASE index_name WAS ISSUED SUCCESSFULLY.

Explanation: The indicated command was issued successfully.
System Action: Processing continues.
User Response: None.
End of change

Start of change
HFPX0103E THE [/DBRECOVERY|/DBDUMP] COMMAND FOR SECONDARY INDEX DATABASE index_name FAILED.
      - TOOLS ONLINE SYSTEM INTERFACE API FAILED. FUNCTION: xxxxxxx, RC: xx, RSN: yyyyyyyy
      - RESPONSE FAILED. IMS ID: xxxx, RC: xxxxxxxx, RSN: yyyyyyyy
      - WAIT TIME LIMIT EXCEEDED.

Explanation: An attempt to run the /DBRECOVERY or /DBDUMP command for the secondary index database has failed.
System Action: The return code is set to 8.
User Response: Contact IBM Software Support and provide the function name, the return code, and the reason code that are shown in the message. If WAIT TIME LIMIT EXCEEDED is displayed, increase the number that is specified in the TOINUM keyword or in the TOITIME keyword.
End of change

Start of change
HFPX0104W THE /START COMMAND FOR SECONDARY INDEX DATABASE index_name FAILED.
      - TOOLS ONLINE SYSTEM INTERFACE API FAILED. FUNCTION: xxxxxxx, RC: xx, RSN: yyyyyyyy
      - RESPONSE FAILED. IMS ID: xxxx, RC: xxxxxxxx, RSN: yyyyyyyy

Explanation: An attempt to run the /START command for the secondary index database has failed.
System Action: The secondary index database remains offline, and the return code is set to 4.
User Response: Manually issue the /START command for the secondary index database. If the problem persists, contact IBM Software Support and provide the function name, the return code, and the reason code that are shown in the message.
End of change

Start of change
HFPX0105E TOOLS ONLINE SYSTEM INTERFACE API FAILED. FUNCTION: xxxxxxx, RC: xx, RSN: yyyyyyyy

Explanation: An attempt to use IMS Tools Online System Interface service has failed.
System Action: The return code is set to 8.
User Response: Contact IBM Software Support and provide the function name, the return code, and the reason code that are shown in the message.
End of change

Start of change
HFPX0107E TOOLS ONLINE SYSTEM INTERFACE CANNOT BE USED.
      - TOOLS ONLINE SYSTEM INTERFACE MODULE modulename IS NOT FOUND.

Explanation: The load module library of IMS Tools Online System Interface is not concatenated to the STEPLIB or JOBLIB.
System Action: The return code is set to 8.
User Response: Ensure that the load module library of IMS Tools Online System Interface is concatenated to the STEPLIB or JOBLIB.
End of change



Update 5
Date of change: May 2012
Change description: User's Guide update.
Topics: Changes are made to the following multiple topics.

> 3.0 IMS Fast Path Basic Tools
>> 3.4 Unloading a DEDB offline with FPB
>>> 3.4.8 Input for DEDB Unload
>>>> 3.4.8.2 Control statements

The second item in "Control statements" section has been changed as follows:

Syntax of the control statement

The FABCUR1 keywords and their associated parameter values may be coded in a free format (columns 1 - 71). Start of changeThe syntactical rules are as follows: End of change
    1. Control statements are coded on 80-byte records.
    2. All control statement specifications must start in column 1. Start of changeA control statement record can include only one control statement.End of change
    3. ...

=====================
> 5.0 Supplementary utilities
>> 5.3 Database Definition Record Create utility
>>> 5.3.5 Input for the Database Definition Record Create utility
>>>> 5.3.5.1 SYSIN DD data set

The second item in "Control statements" section has been changed as follows:

Control statements

The FABCUR5 keywords and their associated parameter values can be coded in a free format (columns 1 - 71). Start of changeThe syntactical rules are as follows: End of change
    1. Control statements are coded on 80-byte records.
    2. Specifications for all control statements must start in column 1. Start of changeA control statement record can include only one control statement.End of change
    3. ...

-----------------
>>> 5.4.1 Functions of the DEDB Reload Segment Data Set Create utility

The first paragraph has been changed as follows:

The DEDB Reload Segment Data Set Create utility (FABCUR6) is called from a user application program. FABCUR6 is used to format and write the segment data records in the format required by Start of changethe FPA Reload function and the FPB DEDB Reload Utility End of change (FABCUR3).

-----------------
>>> 5.4.5 Input for the DEDB Reload Segment Data Set Create utility
>>>> 5.4.5.1 UR6CTL DD data set

Description for AREA_INFROMATION_RECORD=NO has been changed as follows:

AREA_INFORMATION_RECORD=
...
    NO
      Specifies that no area information records will be generated for areas. The EMPTY=YES keyword parameter of the USERCTL control statement will be ignored except when AREA_INFORMATION_RECORD=NO, FORMAT=TFMT, and LRECL=SEGTFMT control statements are specified.

      Start of changeThe segment records that are created by FABCUR6 when AREA_INFORMATION_RECORD=NO is specified can be reloaded by the FPB DEDB Reload utility, but cannot be reloaded by the FPA Reload function. End of change

-----------------
>> 5.5 DEDB Unloaded Segment Data Set Retrieve utility
>>> 5.5.3 Calling the DEDB Unloaded Segment Data Set Retrieve utility (from your program)
>>>> 5.5.3.3 Application interface

A note item has been added to the description of interface parameter list for the "Initialization functions: INIT/INID" and the "End of file: EOF" sections:

Initialization functions: INIT/INID
...
Interface parameter list
    Function code
      This is a mandatory parameter. It is a 4-byte field containing an address of a 4-byte function code field containing INIT or INID. Use function code INIT to initialize the utility in single mode. Use function code INID to initialize the utility in dual mode.

    Start of changeNote: The high-order bit of the last address parameter must be set to 1. The bit can be checked to determine the end of the list. End of change


End of file: EOF
...
Interface parameter list
    Function code
      This is a mandatory parameter. It is a 4-byte field containing an address of the 4-byte function code field containing EOF, left-adjusted in the field.

    Start of changeNote: The high-order bit of the last address parameter must be set to 1. The bit can be checked to determine the end of the list. End of change

-----------------
>> 5.7 DEDB/HD Unload Conversion utility
>>> 5.7.8 Input for the DEDB/HD Unload Conversion utility
>>>> 5.7.8.1 CNTLCRDS DD data set

The second item for control statement syntax has been changed as follows:
...
The following rules apply to control statements:
    • Control statement records have a fixed length of 80 bytes.
    • One or more control statements can be specified. Start of changeA control statement record can include only one control statement.End of change
...



Update 4
Date of change: March 2012
Change description: User's Guide update.
Topics:
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.20 HFPO messages

The User response section in the following messages have been changed as follows (For message HFPO1008W, the Explanation section has also been changed):

HFPO1002W DB SENSOR DID NOT STORE SENSOR DATA FOR DATABASE: dbdname, AREA NO: areanum, AREANAME: areaname

User Response: See the previous IMS Tools KB messages Start of changeto determine the errors and correct any errors. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1004W DB SENSOR COULD NOT SEND NOTIFICATION TO AD FOR DATABASE: dbdname, AREA NO: areanum, AREANAME: areaname

User Response: See the previous Autonomics Director messages Start of changeto determine the errors and correct any errors. If you want a sensor data notification to be sent to Autonomics Director to start a policy evaluation, rerun the job or run a job that stores statistics data in the Sensor Data repository and that sends a sensor data notification to Autonomics Director. End of change

-----------------
HFPO1007W UNABLE TO OBTAIN RECON ID. FUNC= function, RC= return_code, RSN= reason_code.

User Response: Ensure that an appropriate RECON ID is registered in the IMS Tools KB repository. Start of changeIf you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1008W SENSOR DATA SERVICE FAILED. FUNC= function, RC= return_code, RSN= reason_code [, ELEM= data_element xxxx/yyyy]

Explanation: The sensor data service function call ended with errors. If the errors are detected in specific data elements, data_element shows the name of the data element, and hexadecimal values xxxx and yyyy show the return and reason codes of the error, respectively.

Start of changeIf this message contains FUNC=INIT, RC=4, and RSN=X'52', the message indicates that the Sensor Data repository is not initialized. End of change

System Action: Processing continues, but IMS HP Fast Path Utilities does not store any sensor data in the Sensor Data repository of IMS Tools KB.

User Response: See the Tools Base Policy Services User's Guide to determine the meaning of the return code and reason code Start of changeand correct any errors. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository.

When FUNC=INIT, RC=4, and RSN=X'52', follow the instructions in the topic "Initializing the repositories" in the Tools Base: IMS Tools Knowledge Base User's Guide and initialize the Sensor Data repository. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1009W DATA DICTIONARY SERVICE FAILED. FUNC= function, RC= return_code, RSN= reason_code

User Response: Determine if the correct load module library for Policy Services is specified in your JCL. See the Tools Base Policy Services User's Guide to determine the meaning of the return code and reason code Start of changeand correct any errors. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change If the problem persists, contact IBM Software Support.

-----------------
HFPO1010W PHYSICAL ERROR DETECTED IN A CI. DATABASE: dbdname, AREA NO: areanum, AREANAME: areaname

User Response: Run OPC or FPA Analyze to identify the errors in the DEDB area Start of changeand correct any errors. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1011W GETMAIN FAILURE OCCURRED (RC= return_code) FOR SENSOR DATA BUFFER. [DATABASE: dbdname, AREA NO: areanum, AREA: areaname]

User Response: If the region size that is specified is too small, increase the region size on the JOB statement in the JCL. Start of changeIf you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1012W FAILED TO SEND SENSOR DATA NOTIFICATION TO AD. FUNC= function, RC= return_code, RSN= reason_code[, DB: dbdname, AREA: areaname]

User Response: See the Tools Base Autonomics Director User's Guide to determine the meaning of the return code and reason code Start of changeand correct any errors. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1013W LOAD FAILED. SC= system_completion_code, RSN= reason_code, MEMBER: membername

User Response: Determine if the correct load module library for Tools Base is specified in your JCL. Specify the correct load module library Start of changein STEPLIB. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1014W DYNAMIC ALLOCATION FAILED FOR DDNAME: ddname, RC= code, RSN= eeeeiiii

User Response: Look up the dynamic allocation (SVC99) code in the MVS Programming: Assembler Services Reference Start of changeand correct any errors. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1015W OPEN FAILURE OCCURRED FOR DDNAME: ddname

User Response: Ensure that a DD statement is present for the indicated DD and that it is specified correctly Start of changeand correct any errors. If you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1017W FAILED TO SEND SENSOR DATA NOTIFICATION TO AD. MASTER AD ADDRESS SPACE IS NOT ACTIVE. DB: dbdname, AREA: areaname

User Response: See the Tools Base Autonomics Director User's Guide to determine the meaning of the return code and reason code and correct any errors. Start of changeIf you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change

-----------------
HFPO1018W FAILED TO SEND SENSOR DATA NOTIFICATION TO AD. DBRC=YES AND RECON1 DD MUST BE SPECIFIED.

User Response: Specify DBRC=YES and RECON1 DD. Start of changeIf you want to store the sensor data in the IMS Tools KB Sensor Data repository, rerun the job or run a job that stores statistics data in the Sensor Data repository. End of change



Update 3
Date of change: March 2012
Change description: User's Guide update. The following topics (region size considerations for running IMS Fast Path Online Tools utilities) are replaced by this update:
  • Region size considerations for OPC
  • Region size considerations for ODE
  • Region size considerations for OAE
  • Region size considerations for OER
  • Region size considerations for ODM

-----------------
> 4.0 IMS Fast Path Online Tools
>> 4.2 Analyzing a DEDB online with FPO
>>> 4.2.5 Region size considerations for OPC

This topic has been replaced with the following information:

Start of change
The region size for OPC depends on the size of a UOW and keyword specifications.

Because OPC operates in a virtual storage region as an IMS IFP utility, the actual region size required to run OPC is higher than the following values.

For the buffer sets portion for UOW processing, OPC requires the storage calculated by the following formula:

     Buffer Sets:  UOW1 x CISZ x 5
Note: If the value of UOW1 is smaller than 120, 120 is used instead of UOW1.

For the IOVFPOOL-dependent portion, OPC requires the storage calculated by the following formulas:

    Work Buffer:         (UOW1+IOVFPOOL) x CISZ x
10
    IOVF Private Buffer: IOVFPOOL x CISZ x 5


If the return code user exit routine is specified, the required region size of OPC is also affected by the MAXERROR keyword as follows:

     Message and return code table: MAXERROR x 8
End of change
-----------------
>> 4.3 Extracting a DEDB online with FPO
>>> 4.3.6 Region size considerations for ODE

This topic has been replaced with the following information:

Start of change
The region size for ODE depends on the size of a UOW and keyword specifications.

Because ODE operates in a virtual storage region as an IMS IFP utility, the actual region size required to run ODE is higher than the following values.

For the buffer sets portion for UOW processing, ODE requires the storage calculated by the following formula:

     Buffer Sets:         UOW1 x CISZ x 5

For the IOVFPOOL-dependent portion, ODE requires the storage calculated by the following formulas:

    Work Buffer:         (UOW1+IOVFPOOL) x CISZ x
10
    IOVF Private Buffer: IOVFPOOL x CISZ x 5
End of change
-----------------
>> 4.4 Extending a DEDB online with FPO
>>> 4.4.6 Region size considerations for OAE

This topic has been replaced with the following information:

Start of change
The region size for OAE depends on the size of a UOW, and it does not depend on keyword specifications.

Because OAE operates in a virtual storage region as an IMS IFP utility, the actual region size required to run OAE is higher than the following values.

OAE requires the buffer set and IOVF work buffer calculated by the following formulas:

     Buffer Set:       UOW1 x CISZ x 2
     IOVF Work Buffer: CISZ x 125
End of change
-----------------
>> 4.5 Reorganizing a DEDB online with FPO
>>> 4.5.4 Region size considerations for OER

This topic has been replaced with the following information:

Start of change
The region size for OER depends on the size of a UOW and keyword specifications.

Because OER operates in a virtual storage region as an IMS IFP utility, the actual region size required to run OER is higher than the following values.

If the PTRCHK=YES keyword is specified, OER requires the storage calculated by the following formulas:

     Buffer Sets:         UOW1 x CISZ x 5
     Work Buffer:         (UOW1+IOVFPOOL) x CISZ x 10
     IOVF Private Buffer: IOVFPOOL x CISZ x 5
Note: In calculating the buffer sets, if the value of UOW1 is smaller than 120, 120 is used instead of UOW1. For the work buffer, the UOW1 value is used even if the value is smaller than 120.

If the RFSSCAN=(YES,*) keyword or the RFSSCAN=(*,YES) keyword is specified, OER requires the storage calculated by the following formula:

     Buffer Set:  UOW1 x CISZ
Note: If the value of UOW1 is smaller than 120, 120 is used instead of UOW1.

If the return code user exit routine is specified, the required region size of OER is also affected by the MAXERROR keyword as follows:

     Message and return code table: MAXERROR x 8

The MAXBUFFS keyword specifies the number of buffer sets that are used in the reorganization. The meaning of MAXBUFFS is the same as that of the BUFNO command for the High-Speed DEDB Direct Reorganization utility (DBFUHDR0).
End of change
-----------------
>> 4.6 Printing DMAC blocks in a DEDB online with FPO
>>> 4.6.4 Region size considerations for ODM

This topic has been replaced with the following information:

Start of change
The region size for ODM depends on the size of a UOW, and it does not depend on keyword specifications.

Because ODM operates in a virtual storage region as an IMS IFP utility, the actual region size required to run ODM is higher than the following value.

ODM requires the work buffer calculated by the following formula:

     Work buffer: CISZ
End of change



Update 2
Date of change: January 2012
Change description: User's guide updates.
Topics: Changes are made to the following topics.

> 2.0 IMS Fast Path Advanced Tool
>> 2.12 Sample reports of FPA
>>> 2.12.3 Processing report

RELOCATE_SDEP specification has been added to the Processing report for the Unload function as follows:

Figure: Processing report for the Unload function
(Figure 124 in PDF and BookManager formats)



RELOCATE_SDEP specification has been added to the Processing report for the Change function as follows:

Figure: Processing report for the Change function (Part 1 of 2)
(Figure 126 in PDF and BookManager formats)



-----------------
>>>> 2.12.27 Site and System Default report

RELOCATE_SDEP specification has been added to the CHANGE section in the Site and System Default report as follows:

Figure: Site and System Default report
(Figure 177 in PDF and BookManager formats)



In the second example of Site and System Default report, IDXDUMP specification has been added as follows:

Figure: Site and System Default report
(Figure 178 in PDF and BookManager formats)



-----------------
>> 2.13 Site default options support for FPA
>>> 2.13.1 Available keywords for the site default option

RELOCATE_SDEP keyword has been added to the following table:

Table: Keywords for site default option
(Table 53 in PDF and BookManager formats)

Command/ Subcommand Keywords
... ...
CHANGE ... Start of changeRELOCATE_SDEP,End of change ...
... ...
UNLOAD ... Start of changeRELOCATE_SDEP,End of change ...
... ...

=====================
> 7.0 Troubleshooting
>> 7.1 Messages and codes of IMS HP Fast Path Utilities
>>> 7.1.3 Messages
>>>> 7.1.3.3 FABC messages

The User response section of FABC3750E has been changed as follows:

FABC3750E "OPEN" FAILED FOR DDNAME ddname - FAILED BY OS

Explanation: OPEN processing failed for the file associated with the DD statement specified.
System action: Program FABCUR3/FABCUR7 ends with an abend code of 3750.
User response: Start of change See the reason shown in the message. Correct any errors, and rerun the job. See the reason shown in the message and refer to the DD statement description for FABCUR3 or FABCUR7. Correct any errors, and rerun the job. End of change





Update 1
Date of change: January 2012
Change description: Documentation changes by APAR PM50736. This APAR adds the following new functionality:
  • FPA Analyze and FPO OPC can store historical records with UOW information in the Statistics History2 data set.
  • FPA Analyze and FPO OPC can store sensor data with UOW or UOW group information in the IMS Tools KB Sensor Data repository.
  • FPO OPC and OER can store sensor data in the IMS Tools KB Sensor Data repository.
  • FP DB Sensor Printing utility can generate a Sensor Data Statistics report that includes UOW data or UOW group data.
  • FPO OPC and OER can generate Largest Database Records reports.

Topics: Changes are made to the following topics.

> 2.0 IMS Fast Path Advanced Tool

A description for writing the HFPAUOWC DD has been added to the following topics:
The following description has been added to the HFPAUOWC DD description:

HFPAUOWC DD
    ... Start of changeYou can specify the UOW ranges for each area in any order. However, you must specify the area numbers in ascending order. End of change

-----------------
>> 2.11 Command reference for FPA
>>> 2.11.4 FPA keywords
>>>> 2.11.4.29 IAREA

The areaname description has been changed as follows:

Format:
...
    areaname
      Specify a 1- to 8-character area name. Start of changeWhen you specify the HFPAUOWC DD and if you want to process multiple areas, specify the area names in ascending order of their area number. End of change

-----------------
>>>> 2.11.4.92 SENSOR_DBREC

The SENSOR_DBREC=YES description has been changed as follows:

Format:
...
    YES
      Stores the sensor data for the data elements that are related to database records and root segment distribution in the Sensor Data repository of IMS Tools KB.
      Start of change SENSOR_DBREC=YES is mutually exclusive with SENSOR=NO or PTRCHKLVL=QUICK.
      Requirement: When you specify SENSOR_DBREC=YES, you must also specify SENSOR=YES and PTRCHKLVL=FULL. End of change

-----------------
>>>> 2.11.4.93 SENSOR_UOW

The SENSOR_UOW=YES description has been changed as follows:

Format:
...
    YES
      Stores the sensor data for the data elements that are related to UOW in the Sensor Data repository of IMS Tools KB.
      Start of change SENSOR_UOW=YES is mutually exclusive with SENSOR=NO.
      Requirement: When you specify SENSOR_UOW=YES, you must also specify SENSOR=YES and SENSOR_DBREC=YES. End of change

-----------------
>>>> 2.11.4.94 SENSOR_UOW_REPORT

The SENSOR_UOW_REPORT=YES description has been changed as follows:

Format:
...
    YES
      Prints the data elements that are related to UOW in the Sensor Data Statistics report.
      Start of change SENSOR_UOW_REPORT=YES is mutually exclusive with SENSOR_UOW=NO.
      Requirement: When you specify SENSOR_UOW_REPORT=YES, you must also specify SENSOR_UOW=YES. End of change

=====================
> 4.0 IMS Fast Path Online Tools
>> 4.2 Analyzing a DEDB online with FPO
>>> 4.2.10 Examples for OPC
>>>> 4.2.10.7 Example 7: Running cross-reference validation of pointers, generating analysis reports, and storing sensor data in the IMS Tools KB repository

DBRC=YES, RECON DD, and STEPLIB DD have been added in the following JCL example:

Figure: Running cross-reference validation of pointers, generating analysis reports, and storing sensor data in the IMS Tools KB repository
(Figure 295 in PDF and BookManager formats)


//ANALYZE     EXEC FPUTIL,DBD=DEDBJN23,IMSID=IMS1
//*
//FPU.STEPLIB DD DISP=SHR,DSN=HPFP.SHFPLMD0
//            DD DISP=SHR,DSN=IMSVS.SDFSRESL
//            DD DISP=SHR,DSN=ITB.SHKTLOAD
//FPXMFILE    DD SYSOUT=*
//FPXRPTS     DD SYSOUT=*
//FPXSPRT     DD SYSOUT=*
//RECON1      DD DISP=SHR,DSN=IMSVS.RECON1
//RECON2      DD DISP=SHR,DSN=IMSVS.RECON2
//RECON3      DD DISP=SHR,DSN=IMSVS.RECON3
//FPXIN       DD *
  GLOBAL
    DBRC=YES,
    ITKBSRVR=FPQSVR01,
    ADXCFGRP=ADSVR01
  ANALYZE
    AREA=ALL,
    TYPRUN=RPT,
    FULLSTEP=YES,
    SENSOR=YES,
    SENSOR_DBREC=YES
/*


-----------------
>> 4.5 Reorganizing a DEDB online with FPO
>>> 4.5.9 Examples for OER
>>>> 4.5.9.4 Running OER with OPC and storing sensor data in the IMS Tools KB repository

DBRC=YES, RECON DD, and STEPLIB DD have been added in the following JCL example:
Figure: Running OER with OPC and storing sensor data in the IMS Tools KB repository
(Figure 337 in PDF and BookManager formats)


//REORG       EXEC FPUTIL,DBD=DEDBJN23,IMSID=IMS1
//*
//FPU.STEPLIB DD DISP=SHR,DSN=HPFP.SHFPLMD0
//            DD DISP=SHR,DSN=IMSVS.SDFSRESL
//            DD DISP=SHR,DSN=ITB.SHKTLOAD
//FPXMFILE    DD SYSOUT=*
//FPXRPTS     DD SYSOUT=*
//FPXSPRT     DD SYSOUT=*
//RECON1      DD DISP=SHR,DSN=IMSVS.RECON1
//RECON2      DD DISP=SHR,DSN=IMSVS.RECON2
//RECON3      DD DISP=SHR,DSN=IMSVS.RECON3
//FPXIN       DD *
  GLOBAL
    DBRC=YES,
    ITKBSRVR=FPQSVR01,
    ADXCFGRP=ADSVR01
  REORG
    AREA=ALL,
    PTRCHK=YES
  PTRCHK
    TYPRUN=RPT,
    CHKUOW=ALL,
    FULLSTEP=YES,
    SENSOR=YES,
    SENSOR_DBREC=YES
/*


-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.3 FPO keywords
>>>> 4.7.3.43 LARGEREC_REPORT

Abbreviations for keyword parameters have been added as follows:

Format:
...
    YES
      Generate the Largest Database Records report. Start of changeYou can specify Y rather than YES.
    NO
      Do not generate the Largest Database Records report. Start of changeYou can specify N rather than NO. End of change

-----------------
>>>> 4.7.3.82 SENSOR_DBREC

The restriction section has been changed as follows:

Restrictions Start of changeand requirements: End of change
  • The SENSOR_DBREC keyword can be specified only in FPXIN.
  • Start of change SENSOR_DBREC=YES is mutually exclusive with SENSOR=NO.
  • When you specify SENSOR_DBREC=YES, you must also specify SENSOR=YES.End of change

-----------------
>>>> 4.7.3.83 SENSOR_UOW

The restriction section has been changed as follows:

Restrictions Start of changeand requirements: End of change
  • The SENSOR_UOW keyword can be specified only in FPXIN.
  • Start of change SENSOR_UOW=YES is mutually exclusive with SENSOR=NO.
  • SENSOR_UOW=NO is mutually exclusive with SENSOR_UOW_REPORT=YES.
  • When you specify SENSOR_UOW=YES, you must also specify SENSOR=YES and SENSOR_DBREC=YES.End of change

-----------------
>>>> 4.7.3.84 SENSOR_UOW_REPORT

The restriction section has been changed as follows:

Restrictions Start of changeand requirements: End of change
  • The SENSOR_UOW_REPORT keyword can be specified only in FPXIN.
  • Start of change SENSOR_UOW_REPORT=YES is mutually exclusive with SENSOR_UOW=NO.
  • When you specify SENSOR_UOW_REPORT=YES, you must also specify SENSOR_UOW=YES.End of change

=====================
> 6.0 References
>> 6.1 DEDB monitoring and tuning guide
>>> 6.1.5 JCL examples for monitoring and tuning DEDBs
>>>> 6.1.5.7 Online Expert Reorganization JCL examples for monitoring and tuning DEDBs

Example 7: Generating reports to obtain large database records information

FULLSTEP=YES keyword for the PTRCHK subcommand has been added in the JCL example as follows:

Figure: Online Expert Reorganization example 7: Generating reports to obtain large database records information
(Figure 513 in PDF and BookManager formats)


//FPXIN DD *
  REORG AREA=(DB22AR0,DB22AR1),
     PTRCHK=YES
  PTRCHK
     TYPRUN=RPT,
     FULLSTEP=YES,
     CHKUOW=ALL
   REPORT LARGEREC_REPORT=YES
/*

Publication number

SC19-3287-00

Copyright date

1985, 2011

Original publication date

2012/1/10

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IMS Tools
IMS Fast Path Solution Pack: IMS High Performance Fast Path Utilities

Software version:

1.2.0

Operating system(s):

z/OS

Reference #:

7023880

Modified date:

2014-04-24

Translate my page

Machine Translation

Content navigation