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

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

---

Update 7
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 FPXBIC01 FPXBIC02	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 6
Date of change: March 2013
Change description: Documentation changes by APAR PM59411. 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:

When 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.

-----------------
>>> 4.4.3 Data and system flow of OAE

The following two figures have been updated as follows:

Figure 285. Data and system flow of OAE: Original expansion


Figure 286. Data and system flow of OAE: Shadow expansion



-----------------
>> 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":


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:

• IMS 10 or later
• 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.

-----------------
>>>> 4.4.4.3 Considerations on recovery and restart

Descriptions have been updated as follows:

Recovery

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.

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.

If 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.

Important: To prevent DEDB areas from being destroyed, do not specify the time when OAE was in process as the recovery time.

Restart

If the utility ends prematurely, simply restart the utility by using the same input and the following parameters:

• For 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.

The area is accessible to the online environment until OAE is restarted.

Important: 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.

-----------------
>>> 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.

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

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

Content in the Procedure section has been updated as follows:

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,
       1. Check the status of the temporary ADS in DBRC.
          • If the temporary ADS is in AVAIL status, then complete the following steps:
            1. Separate the temporary ADS from the IMS online system by using the /STOP ADS command.
            2. 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.
       2. 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:
       1. Run the DEDB Area Data Set Create utility (DBFUMRI0) by specifying the DD name of the original ADS.
       2. Separate the temporary ADS from the IMS online system by using the /STOP ADS command.
       3. Unregister the temporary ADS with DBRC.
       4. 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:
     1. Run the DEDB Area Data Set Create utility (DBFUMRI0) by specifying the DD name of the original ADS.
     2. 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.

-----------------
>>> 4.4.6 Region size considerations for OAE

This topic has been updated as follows:

OAE operates in a virtual storage region as an IMS IFP utility.

The region size for OAE does not depend on keyword specifications.

The region size required by OAE 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

-----------------
>>> 4.4.7 DD statements for OAE

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

Table 116. OAE DD statements

DDNAME	Use	Format	Required or optional
...	...	...	...
ACBLIB	...	...	...
RECONn	Input/Output		Optional
...	...	...	...
FPXBINTP	...	...	...
FPXBIC01	Output	PS	Optional
FPXBIC02	Output	PS	Optional

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.

If 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.

SYSPRINT DD

Describes the data set that contains output messages.

Warning: 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.

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

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.

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.

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)".

-----------------
>>> 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 118. Control commands for the SYSIN data set

Command name	Description
...	...
EXIT	... ICEXTEND 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. ...
...	...

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

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

Table 120. EXTEND statements keywords

	Description
...	...
ICEXTEND	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.
ICERR_CONT	An optional keyword that is used to specify whether to continue extending the DEDB area when image copy expansion fails.
...	...

-----------------
>>> 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:

If 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.

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

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

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.

-----------------
>>> 4.4.12 Examples for OAE
>>>> 4.4.12.1 Examples for the original expansion

The following example has been added:

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)

-----------------
>>> 4.4.12 Examples for OAE
>>>> 4.4.12.2 Examples for the shadow expansion

The following example has been added:

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)


-----------------
>> 4.7 Keyword reference for FPO
>>> 4.7.2 Control statements and keywords
>>>> 4.7.2.21 EXTEND

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

Related keywords:

• ...
• ICEXTEND
• ICERR_CONT
• ...

-----------------
>>> 4.7.2 Control statements and keywords

The following new topics have been added:

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.

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.

=====================
> 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:

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

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. 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.
System Action: Processing ends with a return code of 4.
User Response: 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. See "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:

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

Explanation: OAE restart process determines the original area data set from the DBRC. 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 OAE restart process.
System Action: Processing continues.
User Response: None.

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

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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
FPX0288I OAE extended the image copy data set along with the DEDB area.

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.

-----------------
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.

-----------------
FPX0290W This version of IMS is not supported for extending image copy data sets.

Explanation: To use the image copy expansion option to extend image copies, version of IMS must be V10 or higher.
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, correct the error, and rerun the job.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
FPX0297I 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.

-----------------
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.

-----------------
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.

-----------------
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.

-----------------
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.

---

Update 5
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.

When 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".

...

---

Update 4
Date of change: October 2012
Change description: Documentation changes by APAR PM72627. This APAR changes the behavior of FABCUR6 and FABCUR7 programs so that they do not check the number of interface parameters.
Topics: Changes are made to the following multiple topics.

> 5.0 Supplementary utilities
>> 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

The following description has been added before "Initialization functions: INIT/INID":

FABCUR7 accepts multiple INIT(INID)-GET(GET1/GET2)-EOF calls, which means that FABCUR7 continues to process even when an INIT (INID) call is issued after the EOF call.

The following description has been deleted:

Note: The INIT or INID function must be run prior to any other function call.

-----------------
>>> 5.5.7 Examples for the DEDB Unloaded Segment Data Set Retrieve utility

In the following figure, "CLEAR STATUS CODE FOR THE NEXT GET CALL" section has been added as follows:

Figure 360. COBOL statements for using FABCUR6 and FABCUR7 (Part 2 of 2)

   * -------------------------------------------------------- *
   * -----        INITIALIZATION PROCESSING     ------------- *
   * -------------------------------------------------------- *
    INIT_PROC.
        CALL    'FABCUR7'         USING FUNC_INIT.
        CALL    'FABCUR6'         USING FUNC_INIT,
                                        UR6_DBDNAME.
   * -- CLEAR STATUS CODE FOR THE NEXT GET CALL. --*
        MOVE     STATUS-OK        TO STATUS-CODE.
    INIT_PROC_END. EXIT.

---

Update 3
Date of change: July 2012
Change description: Documentation changes by APAR PM60899. This APAR fixes a DEDB Reload Utility (FABCUR3) abend problem and adds two new messages.

> 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:

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.

-----------------
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.

---

Update 2
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). The syntactical rules are as follows:

1. Control statements are coded on 80-byte records.
2. All control statement specifications must start in column 1. A control statement record can include only one control statement.
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). The syntactical rules are as follows:

1. Control statements are coded on 80-byte records.
2. Specifications for all control statements must start in column 1. A control statement record can include only one control statement.
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 the FPA Reload function and the FPB DEDB Reload Utility (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.

The 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.

-----------------
>> 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.

Note: 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 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.

Note: 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.

-----------------
>> 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. A control statement record can include only one control statement.

...

---

Update 1
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:

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

-----------------
>> 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:

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

-----------------
>> 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:

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

-----------------
>> 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:

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).

-----------------
>> 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:

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