IBM Support

Updates to IMS Database Reorganization Expert for z/OS V4.1 User's Guide

Product Documentation


Abstract

Updates that apply to IMS Database Reorganization Expert V4.1 User's Guide (SC19-1137-06).

Content

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

Update 14

Date of change: May 2021

Change description: User's guide update.

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > SPACEALLOC control statement

Description has been added as follows:

Using the HPSGAMSA data set containing the IDCAMS commands
If you specify the HPSGAMSA DD statement, which specifies the data set that contains the IDCAMS commands for the shadow allocation, Smart Reorg utility passes the commands to the IDCAMS program.
Notes:
  • If the IDCAMS returns the non-zero condition code, Smart Reorg utility terminates the reorganization processing. Specify 'SET MAXCC=0' after the DELETE command in case the used shadow data set does not exist.
  • image 7001If the HPSGAMSA data set contains many IDCAMS ALLOCATE commands, IDCAMS processing might end without allocating some  shadow database data sets. When this happens, IDCAMS message IKJ56220I is printed in the Result of Shadow Space Allocation report to alert data set allocation failures. If the HPSGAMSA data set contains many ALLOCATE commands, specify the DYNAMNBR parameter on the EXEC statement to prevent data set allocation failures.
    Example:
    //REORG EXEC PGM=HPSGMAIN,PARM='DBD=dbdname,DBRC=Y',DYNAMNBR=999
image 7002
...
==========

Topic:  Troubleshooting > Messages and codes > Messages > HPSG messages

The User response section of message HPSG0102E has been updated as follows:

HPSG0102E   DYNAMIC ALLOCATION FAILED FOR DDNAME= ddname RC=rc, RSN=rsn
Explanation: An attempt of dynamic allocation for the data set that is identified by the DD name ddname failed. The values rc and rsn are the decimal return code and the hexadecimal reason code of the DYNALLOC macro.
  • When RC=04 and RSN=1708, this message indicates that the data set does not exist.
  • When RC=04 and RSN=0238, this message indicates that the TIOT space is full.
System action: The Smart Reorg utility task or the subtask that issued the dynamic allocation request abends with a completion code of U0102, and the Smart Reorg utility job step ends with a return code of 16.
User response: image 7001Correct the error and rerun the job. If RC is 04 and RSN is 043C, specify the DYNAMNBR parameter on the EXEC statement for the Smart Reorg utility and rerun the job. If the error cannot be resolved, keep the dump produced at the time of error and contact IBM Software Support.image 7002
Problem determination: For the return code and the reason code from the DYNALLOC macro, see the z/OS MVS Authorized Assembler Services Guide.

Update 13

Date of change: May 2021

Change description: Documentation changes to support APAR PH35323.

Topic:  Troubleshooting > Messages and codes > Messages > HPSG messages

User response sections of the following HPSG messages have been updated:

HPSG0306E   DEVTYPE MACRO FAILED ON DDNAME: ddname (RC=rc)

Explanation: An error occurred when the DEVTYPE macro is used to get information about the device that is associated with the DD name ddname. The value rc shows the return code from DEVTYPE macro.

System action: Reorganization Manager issues a U0306 abend, and the Smart Reorg utility ends with a return code of 16.

User response: Check if the DD statement for the indicated DD name points to the correct data set. Correct the error and rerun the job.

image 7001If the indicated DD name (ddname) is IMSD0000 or IMSDSTAG, this is likely an internal system error. Contact IBM Software Support.image 7002

---

HPSG0307E   DDNAME xxxxxxxx IS NOT FOUND

Explanation: No DD statement is coded in the JCL stream for the DD name xxxxxxxx although the dynamic allocation is not designated for the DD statement.

System action: The Smart Reorg utility ends with a return code of 8.

User response: Specify the DD statement for the DD name or specify the dynamic allocation of the DD statement. On how to specify the dynamic allocation, see DYNALLOC control statement.

image 7001If the indicated DD name (xxxxxxxx) is IMSD0000 or IMSDSTAG, this is likely an internal system error. Contact IBM Software Support.image 7002


Update 12

Date of change: April 2021

Change description: Documentation changes by APAR PH35209. 

Topic: Troubleshooting > Messages and codes > BBE messages

Message BBE1444E has been updated as follows:
BBE1444E image 7001TOSI IS NOT AT THE REQUIRED MAINTENANCE LEVEL: reason_codeimage 7002
Explanation: image 7001The version and release of IMS Tools Online System Interface (TOSI) that was used in the DB Sensor job, in the IMS control regions, or both are lower than the required maintenance level. reason_code has the following meaning:
Reason code Meaning
0001 The version of IMS Tools Online System Interface is not at the required maintenance level to support the VSAMSTAT command. One of the currently supported versions of IMS Tools Base is required.
0002 The version of IMS Tools Online System Interface is not at the required maintenance level to run the VSAMSTAT command against VSAM linear data sets. IMS Tools Base 1.6 with APAR PH23664 or later is required.
image 7002
System action: DB Sensor processing ends with return code 8.
User response: image 7001Use IMS Tools Online System Interface that is at the required maintenance level.image 7002

Update 11

Date of change: February 2021

Change description: Documentation changes by APAR PH29916. 

Topic: Troubleshooting > Messages and codes > Messages > HPSG messages > HPSG2313W

HPSG2313W   CONDITIONAL REORG SERVICE IS DEACTIVATED DUE TO reason
Explanation:The Conditional Reorganization Support Service (CRSS) cannot continue the job because of one of the following reasons.
reason

Meaning

OLR-CURSOR ACTIVE

OLR cursor is active in a partition.

HALDB DEFINITION ACCESS FAILURE

The HALDB partition definition could not be obtained.

GETMAIN FAILURE

A storage area could not be obtained.

DYNAMIC ALLOCATION FAILURE

The allocation of a database data set failed.

LOAD FAILURE

The Conditional Reorganization API module could not be loaded.

ITS FAILURE

The CRSS failed. The cause of the error is shown in BBExxxxx messages.

UNSUPPORTED IMS LEVEL

This level of IMS is not supported.

FREEMAIN FAILURE

The storage area could not be freed.

image 7001UNSUPPORTED DATA SET TYPE

The data set type that is defined for the original database data set is not supported.image 7002

System action:Smart Reorg utility processing continues without the CRSS. If the job is run in Conditional Reorganization mode and if the error in the CRSS occurred before reorganization need is determined or if the job is run in Reorganization Diagnosis mode, the runtime mode is switched to unconditional reorganization mode. In this case, message HPSG0001I follows this message.
User response:Take one of the following steps that corresponds to the reason, and rerun the job:
OLR-CURSOR ACTIVE

Run the reorganization job after the HALDB OLR ends.

HALDB DEFINITION ACCESS FAILURE

Register the HALDB definition in RECON.

GETMAIN FAILURE

Increase the region size for the job.

DYNAMIC ALLOCATION FAILURE

Message HPSG0122E and HPSG0123I are issued before this message. Follow the directions in the user response sections of these messages.

LOAD FAILURE

Specify the correct load library for IMS Database Reorganization Expert.

ITS FAILURE

BBExxxxx error messages are issued before this message. Follow the user response sections of these messages.

UNSUPPORTED IMS LEVEL

Use the supported version of IMS.

FREEMAIN FAILURE

This is likely an internal system error. Contact IBM Software Support.

image 7001UNSUPPORTED DATA SET TYPE

Ensure that the original database data set is valid. If the problem persists, contact IBM Software Support.image 7002


Update 10

Date of change: September 2020

Change description: Documentation changes to support APAR PH26055. IMS OSAM database enhancement support.

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > DYNALLOC control statement

This topic has been updated as follows:

Notes:

  • For a non-HALDB, the DFSMDA members are used to allocate the original database and the original indexes. You can use the IMSDALIB DD statement to specify a library that contains the DFSMDA members. For more information about the IMSDALIB DD statement, see DD names common to all processing options.
  • If DBRC is active, as it always is for a HALDB, the data sets for the original database and the original indexes, including secondary indexes if INDEXBLD=YES or PSINDEXBLD=YES, must be registered to DBRC. For a non-HALDB, if a data set name that is defined in the DFSMDA member differs from the data set name registered to DBRC, the job ends abnormally.
  • For a HALDB, the indirect list data sets (ILDSs) are included in the set of original or shadow database data sets. If ILDSBLD=NO is specified or there is no segment for which the indirect list entry (ILE) is to be created, the shadow ILDSs are not used and there is no need to preallocate the shadow ILDSs.
  • For a HALDB, if the M-through-V and Y data sets are active, the shadow database data sets are named with the names of the corresponding A-through-J and X data sets with a suffix character c added.
  • If all of the following conditions are met, XTIOT (extended task input/output table) is used to allocate each HALDB data set dynamically:
    • All of the STEPLIB libraries are APF-authorized.
    • z/OS is V1.12 or later.
    • (If one or more OSAM data sets are included) The NON_VSAM_XTIOT option is coded in the DEVSUPxx member of PARMLIB.
    • The DBALLABOVE statement is specified in the DFSVSAMP data set.
      image 7001If the DFSVSAMP data set is dynamically allocated and if other conditions are met, the DBALLABOVE statement is automatically coded in the DFSVSAMP data set. However, if all database data sets are OSAM LDS data sets, the DBALLABOVE statement is not coded automatically. This is true even when the NON_VSAM_XTIOT option is not coded.image 7002
==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > SPACEALLOC control statement

This topic has been updated as follows:

Restrictions:

Smart Reorg utility does not generate the commands automatically for the following data sets:

  • Shadow data set if its original is an OSAM multi-volume data set and the volumes are not SMS-managed. If the volumes are SMS-managed, Smart Reorg utility attempts to allocate the shadow data set. The SMS storage class must have the guaranteed space attribute.
  • Output secondary index data set if INDEXBLD=YES,CURRENT or PSINDEXBLD=YES,CURRENT.
  • Output secondary index data set if INDEXBLD=YES,NEW or PSINDEXBLD=YES,NEW and its original data set is not found.
image 7001Migrating from an OSAM data set to an OSAM LDS data set using the automatic shadow space allocation feature is not supported. You must allocate the shadow OSAM LDS data set by specifying SPACEALLOC=NO, or by using the HPSGAMSA DD statement or the DDEFPDS2 DD statement.image 7002
==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Reload task

This topic has been updated as follows:

Table. Control statements for the Reload task

(Table 27 in PDF)

Keyword Acceptable values Default Description
... ... ... ...
DBIOBUF 1 - 999 30 (for VSAM), 15 (for OSAM) Sets the number of VSAM/OSAM buffers. See DBIOBUF control statement.
DBRLBUF 1 - 999 image 700145image 7002 Specifies the amount (the number of tracks) of database buffers that are used for one database data set group when reading or writing the database. See DBRLBUF control statement.
EXTENT 1 - 60 52 Specifies the maximum number of extensions of the OSAM DS that can be created.
... ... ... ...
==========

Topic: Reorganizing a database in one job step > Smart Reorg reports > HPSOUT2 data set > Result of Shadow Space Allocation report

Report examples have been replaced with the following figures:

Figure. Result of Shadow Space Allocation report (Part 1 of 2)

(Figure 76 in PDF)

image 7001

IMS DB REORG EXPERT                         "RESULT OF SHADOW SPACE ALLOCATION"                                        PAGE:       1
5655-S35                                                                                                        09/25/2020  16.46.03

 IF MAXCC EQ 0 THEN -
   DO

     DELETE (TESTDS.OIFC3338.DDHD0011.Z                  ) 
IDC3012I ENTRY TESTDS.OIFC3338.DDHD0011.Z NOT FOUND
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLA3-42
IDC0551I ** ENTRY TESTDS.OIFC3338.DDHD0011.Z NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

     DELETE (TESTDS.OIFC3338.DDHD0011.T                  ) 
IDC0550I ENTRY (D) TESTDS.OIFC3338.DDHD0011.DATA.T DELETED         
IDC0550I ENTRY (C) TESTDS.OIFC3338.DDHD0011.T  DELETED              
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0     

     SET MAXCC=0

     DEFINE CLUSTER ( -
            NAME(TESTDS.OIFC3338.DDHD0011.Z                  ) -
            MODEL(TESTDS.OIFC3338.DDHD0011                    ) -
            ) -
            DATA(NAME(TESTDS.OIFC3338.DDHD0011.DATA.Z             ) -
            )
IDC0508I DATA ALLOCATION STATUS FOR VOLUME TST001 IS 0
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0

   END

 IF MAXCC EQ 0 THEN -
   DO

     DELETE (TESTDS.OIFC3338.DDHD0012.Z                  ) 
IDC3012I ENTRY TESTDS.OIFC3338.DDHD0012.Z NOT FOUND
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLA3-42
IDC0551I ** ENTRY TESTDS.OIFC3338.DDHD0012.Z NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

     DELETE (TESTDS.OIFC3338.DDHD0012.T                  ) 
IDC0550I ENTRY (D) TESTDS.OIFC3338.DDHD0012.DATA.T DELETED         
IDC0550I ENTRY (C) TESTDS.OIFC3338.DDHD0012.T  DELETED              
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0     

     SET MAXCC=0

     DEFINE CLUSTER ( -
            NAME(TESTDS.OIFC3338.DDHD0012.Z                  ) -
            MODEL(TESTDS.OIFC3338.DDHD0012                    ) -
            ) -
            DATA(NAME(TESTDS.OIFC3338.DDHD0012.DATA.Z             ) -
            )
IDC0508I DATA ALLOCATION STATUS FOR VOLUME TST039 IS 0
image 7002

Figure. Result of Shadow Space Allocation report (Part 2 of 2)

(Figure 77 in PDF)

image 7001

IMS DB REORG EXPERT                         "RESULT OF SHADOW SPACE ALLOCATION"                                        PAGE:       2

5655-S35                                                                                                        09/25/2020  16.46.03


IDC0508I DATA ALLOCATION STATUS FOR VOLUME TST001 IS 0
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0


   END

 IF MAXCC EQ 0 THEN -
   DO

     DELETE (TESTDS.OIFC3338.DDHD0013.Z                  ) 
IDC3012I ENTRY TESTDS.OIFC3338.DDHD0013.Z NOT FOUND
IDC3009I ** VSAM CATALOG RETURN CODE IS 8 - REASON CODE IS IGG0CLA3-42
IDC0551I ** ENTRY TESTDS.OIFC3338.DDHD0013.Z NOT DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 8

     DELETE (TESTDS.OIFC3338.DDHD0013.T                  )
IDC0550I ENTRY (D) TESTDS.OIFC3338.DDHD0013.DATA.T DELETED         
IDC0550I ENTRY (C) TESTDS.OIFC3338.DDHD0013.T  DELETED              
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0     

     SET MAXCC=0

     DEFINE CLUSTER ( -
            NAME(TESTDS.OIFC3338.DDHD0013.Z                  ) -
            MODEL(TESTDS.OIFC3338.DDHD0013                    ) -
            ) -
            DATA(NAME(TESTDS.OIFC3338.DDHD0013.DATA.Z             ) -
            )
IDC0508I DATA ALLOCATION STATUS FOR VOLUME TST001 IS 0
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0

   END

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0
image 7002
==========

Topic: Reorganizing a database in one job step > Smart Reorg reports > HPSOUT2 data set > Result of Old Data Sets Deletion report

Report example has been replaced with the following figure:

Figure. Result of Old Data Sets Deletion report

(Figure 89 in PDF)

image 7001

IMS DB REORG EXPERT                          "RESULT OF OLD DATA SETS DELETION"                                        PAGE:       1
5655-S35                                                                                                        09/25/2020  13.04.55

 DELETE (TEMPDS.IPRV3.OIFC0101.DDHD0041.T            ) 
IDC0550I ENTRY (A) TEMPDS.IPRV3.OIFC0101.DDHD0041.T DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0

 DELETE (TEMPDS.IPRV3.OIFC0101.DDHD0042.T            ) 
IDC0550I ENTRY (A) TEMPDS.IPRV3.OIFC0101.DDHD0042.T DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0

 DELETE (TEMPDS.IPRV3.OIFC0101.DDHD0043.T            ) 
IDC0550I ENTRY (A) TEMPDS.IPRV3.OIFC0101.DDHD0043.T DELETED
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0  
  
image 7002
==========

Topic: Reorganizing databases that have external logical relationships > Pre-reorganization utility and Post-reorganization utility reports > Post-reorganization utility reports > HPSOUT2 data set (Post-reorganization utility) > Result of Old Data Sets Deletion report (Post-reorganization utility)

Report example has been replaced with the following figure:

Figure. Result of Old Data Sets Deletion report (Post-reorganization utility)

(Figure 124 in PDF)

image 7001

IMS DB REORG EXPERT                          "RESULT OF OLD DATA SETS DELETION"                                        PAGE:       1
5655-S35                                                                                                        09/25/2020  23.49.14
                                                                                                                                    
                                                                                                                                   
 DELETE (TESTDB.IMS11A.ITHIDM02.DBDS1.T              )                                                              
IDC0550I ENTRY (D) TESTDB.IMS11A.ITHIDM02.DBDS1.DATA.T DELETED                                                                     
IDC0550I ENTRY (C) TESTDB.IMS11A.ITHIDM02.DBDS1.T DELETED                                                                           
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0                                                                          
                                                                                                                                    
 DELETE (TESTDB.IMS11A.ITHIDM01.DBDS1.T              )                                                            
IDC0550I ENTRY (D) TESTDB.IMS11A.ITHIDM01.DBDS1.DATA.T DELETED                                                                      
IDC0550I ENTRY (I) TESTDB.IMS11A.ITHIDM01.DBDS1.INDEX.T DELETED                                                                    
IDC0550I ENTRY (C) TESTDB.IMS11A.ITHIDM01.DBDS1.T DELETED                                                                           
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0                                                                          
                                                                                                                                    
 DELETE (TESTDB.IMS11A.ITHIDM04.DBDS1.T              )                                                              
IDC0550I ENTRY (D) TESTDB.IMS11A.ITHIDM04.DBDS1.DATA.T DELETED                                                                     
IDC0550I ENTRY (C) TESTDB.IMS11A.ITHIDM04.DBDS1.T DELETED                                                                          
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0                                                                          
                                                                                                                                   
 DELETE (TESTDB.IMS11A.ITHIDM03.DBDS1.T              )                                                             
IDC0550I ENTRY (D) TESTDB.IMS11A.ITHIDM03.DBDS1.DATA.T DELETED                                                                     
IDC0550I ENTRY (I) TESTDB.IMS11A.ITHIDM03.DBDS1.INDEX.T DELETED                                                                    
IDC0550I ENTRY (C) TESTDB.IMS11A.ITHIDM03.DBDS1.T DELETED                                                                          
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0                                                                          
                                                                                                                                 
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0  
image 7002
==========

Topic: Unloading a database > IPR Unload control statements > Control statements for HSSR Engine > BUFFERS control statement

This topic has been updated as follows:

...

The size of a database buffer is almost the same as the CI or block size of the database data set group. The total number of database buffers is the sum of the buffers in the buffer pools each of which is allocated for a data set group and is used exclusively by the data set group.

image 7001The BUFFERS control statement applies only to ESDS, OSAM LDS, and OSAM data sets. KSDS buffering is done by VSAM, not by HSSR Engine. For a HALDB, a buffer pool is allocated for each data set group and each buffer pool is shared by all partitions.image 7002

There is no need to code a BUFFERS statement in most cases because buffering parameters that can be specified by the BUFFERS statement are automatically tuned and optimized for the input database. For severely fragmented databases, however, allocating more buffers than the default could improve the performance of your job. In those cases, code the BUFFERS control statement.

The abbreviation BUFS= can be used for BUFFERS=.

target

Indicates that the BUFFERS statement is effective for the data set or the set of data sets that is identified by ddname.

This parameter can be specified in one of the following ways:

  • A keyword: *ALL, *HD, or *PHD
  • A DD name: ddname
  • A pattern of DD names: 'pattern'

*ALL

image 7001Specifies that the statement applies to all ESDS, OSAM LDS, or OSAM data sets. *ALL is the default.image 7002

*HD

image 7001Specifies that the statement applies to all ESDS, OSAM LDS, or  OSAM data sets of all HIDAM and HDAM databases.image 7002

*PHD

image 7001Specifies that the statement applies to all ESDS, OSAM LDS, or OSAM data sets of all PHIDAM and PHDAM databases.image 7002

*HS

Specifies that the statement applies to all ESDS data sets of all HISAM databases.

ddname

Specifies that the statement applies to the data set identified by the specified DD name ddname.

...

seq_buf_amount

image 7001Specifies the number of buffer slots allocated for a sequential buffer—that is, the number of OSAM blocks, OSAM LDSCIs, or ESDS CIs that are read together in a single sequential read.

The acceptable value is in the range of 2 - 255.

The default value is determined internally depending on the size of the OSAM block, OSAM LDS CI, or ESDS CI.image 7002

seq_buf_num

Specifies the number of sequential buffers.

The acceptable value is in the range of 3 - 9999.

The default value is 8.

dir_buf_num

image 7001Specifies the number of direct buffers. An OSAM block, OSAM LDS CI, or ESDS CI is read into a direct buffer by a direct read.image 7002

The acceptable value is in the range of 3 - 255.

The default value is determined internally from the seq_buf_amount value.

==========

Topic: Unloading a database > IPR Unload control statements > Control statements for HSSR Engine > CABBASE control statement

This topic has been updated as follows:

access_method

Specifies the access method of the data set to which this statement is applied.

ALL

image 7001Indicates that this statement applies to all ESDS, OSAM LDS, or  OSAM data sets.image 7002

VSAM

image 7001Indicates that this statement applies to all ESDS or OSAM LDS data sets.image 7002

OSAM

Indicates that this statement applies to all OSAM data sets.

buf_type

Specifies the buffering type to which this statement is applied.

ALL

Indicates that this statement applies to both sequential buffering and direct buffering.

SEQ

Indicates that this statement applies to sequential buffering.

DIR

Indicates that this statement applies to direct buffering.

==========

Topic: Unloading a database > IPR Unload control statements > Control statements for HSSR Engine > ZIIPMODE control statement

This topic has been updated as follows:

image 7001Specifies whether HSSR engine offloads eligible VSAM ESDS I/O or OSAM LDS I/O workloads to zIIP processors.image 7002

This control statement is optional. The default is ZIIPMODE=NEVER.

             .-NEVER-.       
>>-ZIIPMODE=-+-COND--+-----------------------------------------><   

COND

image 7001Offloads VSAM ESDS I/O or OSAM LDS I/O workloads to zIIP processors when all of the following conditions are met:image 7002

  • zIIP processor are available.
  • The SGLXLOAD library of IMS Tools Base is specified to the STEPLIB or JOBLIB.
  • VSAM ESDS is to be read using Media Manager. Media Manager is available only when the STEPLIB libraries are all APF-authorized. For more information, see DD statements.

If any of these conditions is not satisfied, the job runs using the main CPs.

NEVER

Does not offload any workload to zIIP processors. NEVER is the default to avoid unexpected performance degradation.

==========

Topic: Reloading a database > IPR Reload JCL requirements

This topic has been updated as follows:

The IPR Reload utility uses a performance default of the access method buffer number for each input and output data set. The summary of the default values is shown in the following table.

Table. IPR Reload utility defaults for the data set access method buffer

(Table 73 in PDF)

DDNAME Use Access Default parameter Storage used
DFSUINPT IN QSAM DCB=(BUFNO=60) private high
HPSRSIDX OUT QSAM DCB=(BUFNO=40) private low
DFSURWF1 OUT QSAM DCB=(BUFNO=40) private low
HPSRPnnn OUT QSAM DCB=(BUFNO=105) private high
database OUT
  • ESDS
  • image 7001OSAM LDSimage 7002
  • KSDS
  • BSAM
  • DBIOBUF=30 (See Note 1)
  • image 7001DBIOBUF=30 (See Note 1)image 7002
  • DBIOBUF=30 (See Note 2)
  • DBIOBUF=15 (See Note 3)
  • private high
  • image 7001private highimage 7002
  • private high
  • private high

Notes:

  1. image 7001The IPR Reload utility calculates the number of VSAM buffers that fit into 30 tracks (that is, the default value of the DBIOBUF parameter) depending on the CI size, and specifies AMP=('BUFND=nn') in the ESDS or OSAM LDS database data set internally.image 7002
  2. The IPR Reload utility calculates the number of VSAM buffers that fit into 30 tracks (that is, the default value of the DBIOBUF parameter) depending on the CI size, and specifies AMP=('BUFND=nn,BUFNI=100') in the KSDS database data set internally. BUFNI=100 is used commonly for any CI size.
  3. The IPR Reload utility calculates the number of BSAM buffers that fit into 15 tracks (that is, the default value of the DBIOBUF parameter) depending on the block size, and specifies DCB=(NCP=nn) in the OSAM database data set internally.
==========

Topic: Reloading a database > IPR Reload control statements > DBIOBUF control statement

This topic has been updated as follows:

Specifies the number of tracks for the access method (VSAM or BSAM) buffers that are used for one database data set group when the database is read or written to.

The IPR Reload utility translates the specified number into the AMP= or DCB= (NCP=) parameter value internally. If the translated value exceeds the maximum allowable value for each access method, the translated value is overwritten. If you specify the AMP= or the DCB= (NCP=) parameter for the database DD statement, it precedes the DBIOBUF= specification.

image 7001This control statement is optional. The default is DBIOBUF=30 for ESDS and OSAM LDS, and DBIOBUF=15 for OSAM. In the case of HISAM, DBIOBUF=15 is used.

For OSAM LDS, DBIOBUF=15 is printed in the HPSIN Control Statements report even if DBIOBUF=30 is applied.image 7002

==========

Topic: Reloading a database > IPR Reload control statements > ILDSBLD control statement

This topic has been updated as follows:

YES,INITONLY

The ILDS is initialized but no ILEs are built. Use ILDSBLD=YES,INITONLY only when the HALDB has no logical relationships and you want to rebuild PSINDEXes in a separate job by using IMS Index Builder.

C

ILDS is rebuilt in the same manner of IMS HD Reorganization Reload.

image 7001If the database an OSAM database, ILDSBLD=C is changed to ILDSBLD=YES,DSPR.image 7002

NO

ILDS is not built. In this case, you must rebuild ILDS after the reorganization of the database. To do this, scan the reorganized database by using IMS HALDB Index/ILDS Rebuild utility (DFSPREC0).

==========

Topic: Reference > Performance tips and considerations > Performance tips for the Smart Reorg utility

This topic has been updated as follows:

zIIP processor

image 7001A portion of VSAM ESDS I/O or OSAM LDS I/O workloads can be offloaded to IBM System z Integrated Information Processor (zIIP) and reduce the use of the main CPU.image 7002

To enable zIIP processing, specify the ZIIPMODE=COND control statement in the (REORG) block of the HPSIN DD statement. Certain conditions must be satisfied to enable zIIP processing. For more information, see ZIIPMODE control statement.

You can set this value in the Installation Default Option Table (HPSCOPTI) so that the value is always applied. Use the following example to specify this value in HPSCOPTI:

  HPSCOPT DRIVER,ZIIPMODE=COND  
==========

Topic: Reference > Performance tips and considerations > Performance tips for the IPR Unload utility

This topic has been updated as follows:

Media Manager

image 7001Media Manager improves the performance and reduces CPU time required to read VSAM ESDS or OSAM LDS database data sets.image 7002

To use Media Manager, APF-authorize all the libraries that are concatenated in the JOBLIB or the STEPLIB. You do not need to specify specific keywords to enable Media Manager.

Restriction: Media Manager cannot be used in IPR Unload utility jobs that are invoked by JCL written for IMS HD Reorganization Unload (DFSURGU0).


zIIP processor

image 7001A portion of VSAM ESDS I/O or OSAM LDS I/O workloads can be offloaded to IBM System z Integrated Information Processor (zIIP) and reduce the use of the main CPU.image 7002

To enable zIIP processing, specify the ZIIPMODE=COND control statement in the HPSIN DD statement. Certain conditions must be satisfied to enable zIIP processing. For more information, see ZIIPMODE control statement.

You can set this value in the Installation Default Option Table (HPSCOPTI) so that the value is always applied. Use the following example to specify this value in HPSCOPTI:

  HPSCOPT UNLOAD,ZIIPMODE=COND

==========

Topic: Reference > Performance tips and considerations > Performance tips for the IPR Reload utility

This topic has been updated as follows:

zIIP processor

image 7001A portion of VSAM ESDS I/O or OSAM LDS I/O workloads can be offloaded to IBM System z Integrated Information Processor (zIIP) and reduce the use of the main CPU.image 7002

To enable zIIP processing, specify the ZIIPMODE=COND control statement in the HPSIN DD statement. Certain conditions must be satisfied to enable zIIP processing. For more information, see "ZIIPMODE control statement".
You can set this value in the Installation Default Option Table (HPSCOPTI) so that the value is always applied. Use the following example to specify this value in HPSCOPTI:

  HPSCOPT RELOAD,ZIIPMODE=COND

==========

Topic:  Troubleshooting > Messages and codes > Messages > HPSG messages

Message HPSG0111E has been updated as follows:

HPSG0111E PRE-PRODUCT ERROR (reason); PROD=prodname

Explanation: The prerequisite product prodname is not found in libraries that are concatenated to STEPLIB, or the release level or the maintenance level of product prodname is not high enough for the product to run under the Smart Reorg utility. The level is the internal level of the IMS Database Reorganization Expert-support function of the product. For the software requirements, see "Software prerequisites". Reason code reason shows the reason of the error.

Reason code

Meaning

image 700101000001

IMS HP Unload V1 with APAR PQ93668 is required.image 7002

01000002

IMS HP Unload V1 with APAR PK28097 is required.

01000003

IMS HP Unload V1 with APAR PK90234 is required.

01000004

IMS HP Unload V1 with APAR PM94788 is required.

01000005

IMS HP Unload V1 with APAR PM75257 is required.

01000006

IMS HP Unload V1 with APAR PI64269 is required.  

01000007

IMS HP Unload V1 with APAR PH06589 is required. 

01000008 

IMS HP Unload V1 with APAR PH12333 is required.

image 700101000009

IMS HP Unload V1.2 with APAR PH22529 is required.image 7002

image 700102000001

IMS HP Load V2 is required.image 7002

image 700102000002

IMS HP Load V2 with APAR PQ96282 is required.image 7002

02000003

IMS HP Load V2 with APAR PK28098 is required.

02000004

IMS HP Load V2 with APAR PK88818 is required.

02000005

IMS HP Load V2 with APAR PM94789 is required.

02000006

IMS HP Load V2 with APAR PM75254 is required.  

02000008   

IMS HP Load V2 with APAR PI69221 is required.   

02000009   

IMS HP Load V2 with APAR PH04683 is required. 

image 700102000010   

IMS HP Load V2.1 with APAR PH28860 is required.image 7002

03000001

IMS Index Builder V2.3 with APAR PQ94145 is required.

03000002

IMS Index Builder V3.1 with APAR PM94790 is required.  

03000003   

IMS Index Builder V3.1 with APAR PI72375 is required.   

03000004   

IMS Index Builder V3.1 with APAR PH04685 is required. 

03000005

IMS Index Builder V3.1 with APAR PH14570 is required.

image 700104000002

IMS HP Image Copy V4.1 with APAR PK28108 is required.image 7002

04000005

IMS HP Image Copy V4.1 with APAR PM01166 is required.  

04000007   

IMS HP Image Copy V4.1 with APAR PH06497 is required. 

image 700104000008

IMS HP Image Copy V4.2 with APAR PH25480 is required.image 7002

05000001

IMS HP Prefix Resolution V3 is required.

05000002

IMS HP Prefix Resolution V3 with APAR PK28100 is required.  

05000003   

IMS HP Prefix Resolution V3 with APAR PH06187 is required. 

image 700105000004   

IMS HP Prefix Resolution V3.1 with APAR PH26983 is required.image 7002

image 700106000001

IMS HP Pointer Checker V2.2 with APAR PK45122 is required.image 7002

image 700106000002

IMS HP Pointer Checker V3.1 with APAR PH05165 is required.image 7002

image 700106000003   

IMS HP Pointer Checker V3.1 with APAR PH24727 is required.image 7002

System action: The Smart Reorg utility ends with a return code of 8.

User response: Check the control statement that you specified for the IMS Database Reorganization Expert job, and check that the product or products that are required for the function that is activated by the control statement are installed and in the required maintenance level. If a required product was not installed, install it. If a required maintenance was not applied, apply the maintenance.


Update 9

Date of change: July 2020

Change description: Documentation changes to support APAR PH26788.

Topic:  Troubleshooting > Messages and codes > Messages > HPSG messages

The following two error messages have been changed to warning messages:

image 7001HPSG0451EW DELETION OF OLD DATA SET FAILEDimage 7002
Explanation: An error occurred while deleting the old data sets.
System action: image 7001The Smart Reorg utility continues processing and ends with a return code of 4.image 7002
User response: See the messages that were issued from the IDCAMS program, and identify the cause of the error. The messages are printed in the Result of Old Data Sets Deletion report.
---

image 7001HPSG0459EW RENAMING OF OLD DATA SET FAILEDimage 7002
Explanation: Because DISPOLDDS=NEWSHADOW is specified, the Smart Reorg utility attempted to rename the data set name from the temporary data set name to the shadow data set name. However, it failed.
System action: image 7001The Smart Reorg utility continues processing and ends with a return code of 4.image 7002
User response: See the messages that were issued from the IDCAMS program, and identify the cause of the error. The messages are printed in the Result of Renaming Old Data Sets.

Update 8

Date of change: June 2020

Change description: Documentation changes  to support APAR PH25042.

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Smart Reorg reports > HPSOUT2 data set > Result of Old Data Sets Deletion report

This topic has been updated as follows:

The Result of Old Data Sets Deletion report contains the result of deleting the old original data sets with the IDCAMS command.

image 7001
The following figure shows the report produced when DELOLDDS=YES is specified in the (REORG) block.
This report is produced before the reorganization process if SPACEALLOC=NO and either DISPOLDDS=DELETE, DIPOLDDS=NEWSHADOW, or DELOLDDS=YES is specified in the (REORG) block, or after the name swapping process if DELOLDDS=YES or DISPOLDDS=DELETE is specified in the (REORG) block.
image 7002
Note: The original data sets are renamed with a temporary name with suffix .T by the preceding name swapping process.

==========

Topic: Reorganizing a database in one job step > Smart Reorg reports > HPSOUT2 data set

The following new topic has been added after "Result of Old Data Sets Deletion report:

image 7001

Result of Renaming Old Data Sets report
The Result of Renaming Old Data Sets report contains the result of renaming the old original data sets with the IDCAMS command.
The following figure shows the report produced when DISPOLDDS=NEWSHADOW is specified in the (REORG) block.

Figure. Result of Renaming Old Data Sets report
IMS DB REORG EXPERT                          "RESULT OF RENAMING OLD DATA SETS"                                        PAGE:       1
5655-S35                                                                                                        05/29/2020  01.36.22
                                                                                                                                    
                                                                                                                                    
 IF MAXCC EQ 0 THEN -                                                                                                               
   DO                                                                                                                               
                                                                                                                                    
     ALTER   RSTEST.IPRV3.OIFC0101.DDHD0041.T             -                                                                         
     NEWNAME(RSTEST.IPRV3.OIFC0101.DDHD0041.Z            )                                                                          
IDC0531I ENTRY RSTEST.IPRV3.OIFC0101.DDHD0041.T ALTERED                                                                             
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0                                                                           
                                                                                                                                    
   END                                                                                                                              
                                                                                                                                    
 IF MAXCC EQ 0 THEN -                                                                                                               
   DO                                                                                                                               
                                                                                                                                    
     ALTER   RSTEST.IPRV3.OIFC0101.DDHD0042.T             -                                                                         
     NEWNAME(RSTEST.IPRV3.OIFC0101.DDHD0042.Z            )                                                                          
IDC0531I ENTRY RSTEST.IPRV3.OIFC0101.DDHD0042.T ALTERED                                                                             
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0                                                                           
                                                                                                                                    
   END                                                                                                                              
                                                                                                                                    
 IF MAXCC EQ 0 THEN -                                                                                                               
   DO                                                                                                                               
                                                                                                                                    
     ALTER   RSTEST.IPRV3.OIFC0101.DDHD0043.T             -                                                                         
     NEWNAME(RSTEST.IPRV3.OIFC0101.DDHD0043.Z            )                                                                          
IDC0531I ENTRY RSTEST.IPRV3.OIFC0101.DDHD0043.T ALTERED                                                                             
IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0                                                                           
                                                                                                                                    
   END                                                                                                                              
                                                                                                                                    
IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0      
image 7002

==========

Topic:  Troubleshooting > Messages and codes > Messages > HPSG messages

The following new message has been added:
image 7001
HPSG0459E RENAMING OF OLD DATA SET FAILED
Explanation: Because DISPOLDDS=NEWSHADOW is specified, the Smart Reorg utility attempted to rename the data set name from the temporary data set name to the shadow data set name. However, it failed.
System action: The Smart Reorg utility ends with a return code of 4.
User response: See the messages that were issued from the IDCAMS program, and identify the cause of the error. The messages are printed in the Result of Renaming Old Data Sets.
image 7002

Update 7

Date of change: September 2019

Change description: Documentation changes  to support APAR PH15942. DDEFPDS2 DD statement, which was introduced by APAR PH13318, has been enhanced by APAR PH15942.

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > SPACEALLOC control statement

This topic has been updated as follows:

Specifies whether to delete and allocate DASD space for each shadow data set within the IMS Database Reorganization Expert job step.

...

If you specify SPACEALLOC=YES, each shadow data set can be deleted and allocated within the Smart Reorg utility job step. You can specify the IDCAMS commands in the DDEFPDS2 data set or the HPSGAMSA data set, otherwise Smart Reorg utility generates the commands automatically.

Using the DDEFPDS2 data set containing the IDCAMS commands

If you specify the DDEFPDS2 DD statement, which specifies a partitioned data set that contains the IDCAMS commands for the shadow data sets allocation, the Smart Reorg utility passes the commands to the IDCAMS program. The names of each PDS member must be the same as the DD name of the original data set.  The names of shadow data sets do not need to be "original data set name plus a suffix", they can have any desired names.

For HALDBs, the names of each PDS member must be the same as the DD name of the A-side data sets even when M-side is active.

The following example shows IDCAMS control statements specified in a PDS member:

  DELETE (shadow.database.data-set.name)  
  SET MAXCC=0  
  DEFINE CLUSTER(NAME(shadow.database.data-set.name)...) or ALLOCATE DSNAME('shadow.database.data-set.name')  ...
image 7001In this example, the command to delete the old temporary data set (with suffix .T) is not included because the command will be added automatically.
If not all the members of the database data sets are present in the DDEFPDS2 data set, the Smart Reorg utility generates the IDCAMS commands for the missing database data sets.image 7002
==========

Topic: Troubleshooting > Messages and codes > Messages


Explanation of the following message has been updated:

HPSG0111E PRE-PRODUCT ERROR (reason); PROD=prodname dhs


Explanation:The prerequisite product prodname is not found in libraries that are concatenated to STEPLIB, or the release level or the maintenance level of product prodname is not high enough for the product to run under the Smart Reorg utility. The level is the internal level of the IMS  Database Reorganization Expert-support function of the product. For the software requirements, see Software prerequisites.
Reason code reason shows the reason of the error.
Reason code Meaning

...

image 700103000005 IMS Index Builder V3.1 with APAR PH14570 is required.image 7002

...

---

The suffix character for message HPSG0458 has been changed from E to I. Also, the message has been updated as follows:

image 7001HPSG0458I MEMBER FOR DD=xxxxxxxx NOT FOUND IN DDEFPDS2 DATA SET

Explanation: The data set specified for the DDEFPDS2 DD statement does not contain a member with the indicated name.
image 7001System action: The Smart Reorg utility generates IDCAMS commands to define or allocate the shadow data set of the indicated database data set.image 7002
image 7001User response: None. This message is informational.image 7002

Update 6

Date of change: July 2019

Change description: Documentation change to support APAR PH13318. The Smart Reorg utility supports a new DD statement, DDEFPDS2. This DD statement points to a data set that contains IDCAMS commands for deleting and allocating shadow data sets.

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Smart Reorg JCL requirements > DD statements

DDEFPDS2 DD statement has been added as follows:

Table. DD statements and record format for the Smart Reorg utility

(Table 5 in PDF)

DDNAME Use Format Need
... ... ... ...
image 7001DDEFPDS2 Input PDS or PDSE, LRECL=80, RECFM=FB Optionalimage 7002
HPSGAMSA ... ... ...
... ... ... ...

==========

Topic: Reorganizing a database in one job step > Smart Reorg JCL requirements > DD statements > DD names common to all processing options

DDEFPDS2 DD statement has been added. Also, description for the HPSGAMSA DD statement has been updated.

image 7001DDEFPDS2 DD

Specifies a partitioned data set that contains the IDCAMS commands for deleting and allocating each shadow space. This data set is optional and is used if SPACEALLOC=YES is specified.  For details, see SPACEALLOC control statement.image 7002

HPSGAMSA DD

Defines an optional data set that contains IDCAMS commands for deleting and allocating the DASD spaces of the output data sets. For details, see SPACEALLOC control statement.
image 7001This DD statement is mutually exclusive with the DDEFPDS2 DD statement.image 7002

==========

Topic: Reorganizing a database in one job step > Smart Reorg JCL requirements > Considerations for database data sets

The "Dynamic allocation of original and shadow data sets" section has been updated as follows:

Dynamic allocation of original and shadow data sets

The way in which original and shadow data sets for database and indexes are allocated is determined by the DYNALLOC control statement. The DASD space of the shadow data sets is allocated by the SPACEALLOC control statement.

By default, the original database data sets of HISAM, SHISAM, HDAM, or HIDAM are allocated by using DFSMDA members. If DBRC is active, all databases including the primary index and the secondary indexes must be registered in RECON unless you disable the DYNALLOC option. If DBRC is active and DYNALLOC=(YES,xxx,xxx) is specified, the integrity of the data set names defined in DFSMDA members and those registered in DBRC is checked before the reorganization starts.

For a HALDB, the data sets of a PHDAM or PHIDAM partition are always allocated dynamically by using RECON registration, not before the reorganization starts, but when the partition is first accessed.

By default, the shadow data sets are allocated dynamically. For a non-partitioned database, the names for the shadow data sets are determined automatically. The shadow name consists of the name of the corresponding original input data set followed by a suffix (the default is .Z). For example, suppose your original data set is named IMS.TESTDB01. By default, the shadow data set is named IMS.TESTDB01.Z. If you specify 'DYNALLOC=,A', the shadow data set is named IMS.TESTDB01.A. You can specify any alphabetic character except T as the suffix. The same rule also applies to the shadow primary index for a HIDAM database, a shadow secondary index, and a shadow indirect list data set of PHDAM or PHIDAM.

If the A-through-J and X data sets of a PHDAM or PHIDAM partition is active, the same naming rule as the one applied to non-partitioned database is applied. If the M-through-V and Y data sets of a PHDAM or PHIDAM partition is active, the shadow data set name for the partition is determined by the names of A-through-J and X data sets. For example, if your original data set name of DSG A is IMS.TESTDB01.M0001, the default shadow data set name is IMS.TESTDB01.A0001.Z (the corresponding A-side data set name IMS.TESTDB01.A0001 suffixed with .Z). And, by the name swapping process, the shadow data set is renamed to the A-side data set name IMS.TESTDB01.A0001. The original data set IMS.TESTDB01.M0001 is not renamed but remain as it is.

image 7001If both SPACALLOC=YES and the DDEFPDS2 DD statement are specified, this naming convention for shadow data sets does not apply. The names of the shadow data sets are determined from the information defined in the DDEFPDS2 data set. For details, see SPACEALLOC control statement.image 7002

For details of dynamic allocation of the original and shadow data sets, see DYNALLOC control statement and SPACEALLOC control statement. For details of data set name swapping, see NAMESWAP control statement.

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > DISPOLDDS control statement

A note item has been added as follows:

Specifies the disposition of the original data sets after successful reorganization.

This control statement is optional. The default is DISPOLDDS=TEMPNAME.

image 1358

  ...

If NAMESWAP=YES is specified, first, the old original data sets are renamed to the temporary data set names. Then, the data sets are processed according to the parameter specified for DISPOLDDS:

  • When DISPOLDDS=TEMPNAME, the old data sets remain with the temporary names with suffix '.T'.
  • When DISPOLDDS=DELETE, the old data sets are deleted.
  • When DISPOLDDS=NEWSHADOW, the temporary data sets are renamed to the shadow names with suffix '.Z'. If you want to change the suffix, use DYNALLOC control statement.

image 7001Note:  If both SPACALLOC=YES and the DDEFPDS2 DD statement are specified, old data set name plus suffix '.T' is used for the names of the temporary data sets. The names defined in the DDEFPDS2 data set are used for the shadow data sets.  For details, see SPACEALLOC control statement.image 7002

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > DYNALLOC control statement

A note item has been added as follows:

Specifies whether the data sets for the input and shadow databases and the indexes are dynamically allocated.

image 1361

  ...

The second parameter c specifies a suffix character, other than 'T'. The shadow data set names are created by adding the suffix to the corresponding original data set names. The default suffix is 'Z'. For example, if your original data set is named IMS.TESTDB01, the shadow data set is named IMS.TESTDB01.Z.

If the shadow data set names are not appropriate, you should specify DYNALLOC=(xxx,NO,xxx) or DYNALLOC=(xxx,xxx,NO) and specify your shadow data set names in the JCL stream. For the DD names for the primary database and the primary index, see DDNMAP control statement in the case of a non-HALDB, and see Database, primary index, and ILDS in the case of a HALDB. For secondary indexes of a non-HALDB, for either INDEXBLD=YES,CURRENT or INDEXBLD=YES,NEW, use the DD names that are defined in the DBD in the job step.

image 7001Note: If you specify both SPACEALLOC=YES and the DDEFPDS2 data set, the second parameter is ignored.  The names of each shadow data set is determined from the information defined in the DDEFPDS2 data set. For details, see SPACEALLOC control statement.image 7002

...

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > SPACEALLOC control statement

This topic has been updated as follows:

Specifies whether to delete and allocate DASD space for each shadow data set within the IMS Database Reorganization Expert job step.

...

image 7001If you specify SPACEALLOC=YES, each shadow data set can be deleted and allocated within the Smart Reorg utility job step. You can specify the IDCAMS commands in the DDEFPDS2 data set or the HPSGAMSA data set, otherwise Smart Reorg utility generates the commands automatically.image 7002

image 7001Using the DDEFPDS2 data set containing the IDCAMS commands

If you specify the DDEFPDS2 DD statement, which specifies a partitioned data set that contains the IDCAMS commands for the shadow data sets allocation, the Smart Reorg utility passes the commands to the IDCAMS program. The names of each PDS member must be the same as the DD name of the original data set. 

The names of shadow data sets do not need to be "original data set name plus a suffix", they can have any desired names. 

For HALDBs, the names of each PDS member must be the same as the DD name of the A-side data sets even when M-side is active.

The following example shows IDCAMS control statements specified in a PDS member:

  DELETE (shadow.database.data-set.name

  SET MAXCC=0

  DEFINE CLUSTER(NAME(shadow.database.data-set.name)...) or ALLOCATE DSNAME('shadow.database.data-set.name') ...image 7002

Using the HPSGAMSA data set containing the IDCAMS commands

image 7001If you specify the HPSGAMSA DD statement, which specifies the data set that contains the IDCAMS commands for the shadow data sets allocation, the Smart Reorg utility passes the commands to the IDCAMS program. The names of shadow data sets must be "original data set name + suffix character that the DYNALLOC control statement specifies."image 7002

Automatic shadow space allocation

image 7001If you do not specify the DDEFPDS2 data set or the HPSGAMSA DD statement, Smart Reorg utility automatically attempts to delete and allocate the DASD space for each shadow data set based on the attributes of its original data set. For the volume list and the SMS classes, see the notes. If DYNALLOC=(,,YES) is specified with INDEXBLD=YES,NEW or PSINDEXBLD=YES,NEW, the commands for the shadow secondary index data sets are included. For HALDB, the commands for the shadow ILDS are included unless ILDSBLD=NO is specified. If NAMESWAP=YES, the commands to delete the old temporary data set with suffix '.T' are added.image 7002

==========

Topic: Troubleshooting > Messages and codes > Messages

The following new messages have been added:

image 7001HPSG0457I DDEFPDS2 DATA SET IS USED FOR ALLOCATING SHADOW SPACE

Explanation:  The IDCAMS commands that are specified in the DDEFPDS2 data set are used by the IDCAMS program to delete and define the shadow data sets.
System action:  The Smart Reorg utility continues processing.
User response:  None. This message is informational.image 7002

---

image 7001HPSG0458E MEMBER FOR DD=xxxxxxxx NOT FOUND IN DDEFPDS2 DATA SET

Explanation: The data set specified for the DDEFPDS2 DD statement does not contain a member with the indicated name.
System action: The Smart Reorg utility ends with a return code of 8.
User response: Ensure that a member with the indicated name exists in the data sets that the DDEFPDS2 DD statement specifies, and rerun the job.   image 7002


Update 5

Date of change: June 2019

Change description: Documentation changes to support APAR PH11352. The default value for the EXTENT control statement of the IPR Reload utility has been changed. Also, the default value for the EXTENT control statement can be specified in the Installation Default Option Table (HPSCOPTI).

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Reload task

Values for the EXTENT keyword have been updated as follows:

Table. Control statements for the Reload task

(Table 27 in PDF)

Keyword Acceptable values Default Description
... ... ... ...
DBRLBUF 1 - 999 150 (for VSAM), 45 (for OSAM) ...
image 7001EXTENT 1 - 120 120image 7002 ...
FRSPC YES or NO YES ...
... ... ... ...

==========

Topic: Reloading a database > IPR Reload control statements > Overview of the IPR Reload control statements

The default value for the EXTENT keyword has been updated as follows:

Table. IPR Reload utility control statements for process control

(Table 74 in PDF)

Keyword Accepted values Default Description
... ... ... ...
image 7001EXTENT 1 - 120 120image 7002 ...
... ... ... ...

==========

Topic: Reloading a database > IPR Reload control statements > EXTENT control statement

This topic has been updated as follows:

Specifies the maximum number of extensions of the OSAM data set that can be created.

image 7001When IPR Reload detects an extension number that is greater than the EXTENT control statement value, IPR Reload issues message HPSR3739E and ends abnormally:

  • If HPIO=YES, IPR Reload checks the extension number during the reorganization. It checks the number every time an extent is allocated. The job could end abnormally during the reorganization.
  • If HPIO=NO, IPR Reload checks the extension number after the reorganization. The job ends abnormally only after the reorganization.

This control statement is optional. The default is EXTENT=120. If the job is run under IMS V13 or earlier, EXTENT=60 is applied.

image 1280

image 7002

nnn

Specifies a left-aligned decimal number in the range of 1 - 120.

If you are using IMS V13 or earlier, the maximum value is limited to 60.

If the OSAM data set is created on EAV, this control statement is ignored.

image 7001Tip: You can change the default value of this control statement by creating an Installation Default Option Table (HPSCOPTI). For more information, see "Setting installation default options".image 7002

==========

Topic: Reloading a database > IPR Reload reports > HPSOUT data set > Default Option Tables report

Report example has been replaced with the following figure:

Figure. Default Option Tables report

(Figure 185 in PDF)

image 1279

==========

Topic: Reference > Setting installation default options > How to code HPSCOPT macro statements

EXTENT control statement has been added as follows:

image 7001

image 1281

image 7002

The identifier of each utility and the option keywords that are supported by the utility are as follows:

 ...

DRIVRL

This parameter identifies the Reload task under the Smart Reorg Driver. This parameter supports the following values:

 
  • COMPAUTH
  • image 7001EXTENTimage 7002
  • ILEDATAC
  •   ...

...

RELOAD

This parameter identifies the IPR Reload utility. This parameter supports the following values:

  •   ...
  • DECODEDBD
  • image 7001EXTENTimage 7002
  • GDGBASE
  •   ...

Update 4

Date of change: June 2019

Change description: Documentation changes to support APAR PH12332. This APAR enhances the Smart Reorg utility to support conditional unload. When conditional unload is enabled, the Smart Reorg utility only unloads the database without reorganizing the database. It can also pass a specific return code to the succeeding job step so that the database is reorganized in the succeeding job step.

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Conditional Reorganization Support Service > What is the Conditional Reorganization Support Service?

This topic has been updated as follows:

...

  1. First evaluation phase
    ...
  2. Reorganization phase
    ...
  3. Second evaluation phase
    ...
  4. Reporting phase
    ...
 

image 7001When a Smart Reorg job is run in Conditional Reorganization mode, optionally the Smart Reorg job can create an unload data set without reorganizing the database. When this happens, a specific return code is passed to the succeeding job step to run the database reorganization in the succeeding job step.image 7002

When a Smart Reorg job is run in Diagnosis-only mode, the job goes through only the first evaluation phase and the reporting phase.

...

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > CONDREORG control statement

A note item has been added as follows:

Notes:

  • ...
  • If PSINDEXBLD=YES...
  • image 7001To create an unload data set without reorganizing the database, specify UNLOADONLY=YES with CONDREORG=YES or CONDREORG=YES,REORGDIAG.
    For more information, see "UNLOADONLY control statement" and "Example 16: Conditionally reorganizing a database in separate job steps".image 7002
==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > RC_CHANGE control statement

New value, POLICY.ACTION.REORG, has been added as follows:

Specifies the return code of the Smart Reorg utility that is returned when a specific event is detected during Smart Reorg utility processing.

This control statement is optional. The default is RC_CHANGE=NONE. 

                 .-NONE------------.     >>-RC_CHANGE=--+-(event_name,rc)-+----------------------------><

event_name

Specifies the name of the event to be detected in Smart Reorg utility processing. The following event name can be specified:

  • POLICY.EXCEPTIONS.CRITICAL

This event specifies a condition where one or more critical-level exceptions exist in the database. This parameter must be specified with CONDREORG=YES, CONDREORG=YES,REORGDIAG, or CONDREORG=YES,DIAGONLY.

image 7001If the Smart Reorg utility performs a database reorganization, it returns the specified return code when it detects one or more critical-level exceptions in the reorganized database.

  • POLICY.ACTION.REORG

This event specifies a condition where a database reorganization is needed for the database or for one or more HALDB partitions, and reorganization is not performed yet. This parameter can be specified with CONDREORG=YES,DIAGONLY. However, if UNLOADONLY=YES is specified, this parameter can be specified with CONDREORG=YES or CONDREORG=YES,REORGDIAG. For an example, see "Example 16: Conditionally reorganizing a database in separate job steps".image 7002

rc
Specifies the return code for the Smart Reorg utility that will be issued when the event is detected. The maximum value is 99, and the minimum value is 1.

NONE
Does not change the return codes. The default return codes of the Smart Reorg utility are used.

image 7001You can specify multiple RC_CHANGE control statements, one for each event.  If two or more events are detected, the largest return code is returned.image 7002

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > STARTDB control statement

This topic has been updated as follows:

In the following cases, the /STA DATABASE command is not issued even if STARTDB=YES is specified:

  • ...
  • image 7001In Conditional Reorganization mode, CONDREORG=YES is specified with UNLOADONLY=YES and the CRSS determines that the database reorganization is necessary. In this case, the Smart Reorg utility expects a database reorganization to occur in the succeeding job step.image 7002
==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver

The following new topic has been added:

image 7001UNLOADONLY control statement

Specifies to run only the Unload task to create an unload data set without reorganizing the database.

This control statement is optional. The default is UNLOADONLY=NO.

  image 1272

NO 

Both the Unload task and the Reload task are called to reorganize the database.

YES

Only the Unload task is called to create an unload data set. The Reload task and any other reorganization-related tasks are not called. Shadow data sets are not used.

  • The DFSURGU1 DD statement is required for the unload data set.
  • You can specify the format for the unload data and a user exit routine by providing the OUTPUT control statement in the (UNLOAD) block of the HPSIN control statements. For example:
      (UNLOAD)    OUTPUT=DFSURGU1,*HD,(MYEXIT,B)
    If the OUTPUT control statement is omitted, OUTPUT=DFSURGU1,*HD is used. For more information, see "OUTPUT control statement".
  • The database must be in the read-only state during unload. To set the database to the read-only state, specify DBRCAUTHCMD=YES, IMSCMD=YES,TOSI, and STARTDB=YES.  For more information, see "DBAUTHCMD control statement", "IMSCMD control statement", and "STARTDB control statement".

You can specify UNLOADONLY=YES in Unconditional Reorganization mode and Conditional Reorganization mode. 

  • When CONDREORG=YES is specified, an unload data set is created only when the CRSS determines that the database reorganization is necessary. For HALDB, an unload data set is created for the partitions that require reorganization.
  • When CONDREORG=YES,REORGDIAG is specified, an unload data set is always created regardless of the results from CRSS policy evaluation. For HALDB, an unload data set is created for all partitions.
  • When CONREORG=YES,DIAGONLY is specified, the Unload task is not called and, therefore, unload data set is not created.

For an example, see "Example 16: Conditionally reorganizing a database in separate job steps".image 7002

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Unload task

Description of OUTPUT has been updated as follows:

Table. Control statements used for controlling Unload function

(Table 24 in PDF)

Keyword Acceptable values Default Description
... ... ... ...
OUTPUT (See OUTPUT control statement) SYSUT2,*HD Specifies the characteristics of the output data sets to be created and the optional user exit routine for the output.

The default DD name SYSUT2 has a special meaning; the data written into SYSUT2 is passed to the Reload task. For the DD name SYSUT2, only the *HD unload record format is allowed.
image 7001If UNLOADONLY=YES is specified in the (REORG) block, the default DD name is DFSURGU1. SYSUTn (n=2,3,4) is not supported.image 7002

See OUTPUT control statement.

... ... ... ...
==========

Topic: Reorganizing a database in one job step > Smart Reorg examples

The following new example has been added:

image 7001Example 16: Conditionally reorganizing a database in separate job steps

This example shows JCL streams to evaluate a HIDAM database and, if the database requires a reorganization, create an unload data set and run the reorganization in the succeeding job step.

In this example:

  • The database is evaluated by Conditional Reorganization Support Service (CRSS). If the database needs to be reorganized, the Smart Reorg utility calls the Unload task to create an unload data set and returns a specific return code, which will be passed to the succeeding job step.
  • If a specific code is returned in the first job step, the data sets of the database and its secondary indexes are deleted and newly defined. The database is reorganized in one job step by the Smart Reorg utility, which calls the Reload task, the Index Build task, and the Image Copy task.

Figure. Sample JCL stream to diagnose a database and conditionally unload the database

image 1270

  • CONDREORG=YES and UNLOADONLY=YES specify to diagnose the database and unload the database if the database needs to be reorganized.
    If CONDREORG=YES,REORGDIAG is specified instead of CONDREORG=YES, the database is always unloaded regardless of the evaluation result.
  • The DFSURGU1 DD statement specifies the output unload data set. 
  • RC_CHANGE=(POLICY.ACTION.REORG,22) specifies that return code 22 is returned if the database requires reorganization.
  • The database must be in the read-only state while it is being unloaded. DBRCAUTHCMD=YES specifies to issue the DBRC commands and IMSCMD=YES,TOSI specifies to issue IMS commands automatically.
  • CHECKREC=YES in the (UNLOAD) block is required to pass certain information to the Reload task called in the succeeding job step.

Figure. Sample JCL stream to reorganize the database depending on the return code from the previous step

image 1271

  • The two job steps are processed when the return code from the CONDUNLD job step indicates that the database requires a reorganization.   
  • Before starting the Smart Reorg step, the original database data sets are deleted and defined. The shadow data sets are not used.
  • REORGINPUT=ULDS specifies to reload the database using the unload data set that the DFSUINPT DD statement specifies.
  • INDEXBUILD=YES and IC=YES specify to call the Index Builder task and the Image Copy task. 
  • IMSCMD=YES,TOSI specifies to issue IMS /DBR commands and STARTDB=YES specifies to issue IMS /STA commands automatically.image 7002
==========

Topic: Troubleshooting > Messages and codes > Messages > HPSG messages

The following new message have been added:

image 7001HPSG0253E INCORRECT EVENT OR RC IN RC_CHANGE STATEMENT

Explanation:  An invalid event name or return code is specified for the RC_CHANGE control statement. The event name must be either POLICY.ACTION.REORG or POLICY.EXCEPTIONS.CRITICAL. The return code must be in the range of 1 to 100.  If RC_CHANGE=NONE is specified, a return code value cannot be specified.

System action: The Smart Reorg utility ends with a return code of 8.

User response: Correct the RC_CHANGE control statement error, and rerun the job.image 7002

---

 

image 7001HPSG0456W UNABLE TO ISSUE /STA BECAUSE REORGANIZATION IS NEEDED

Explanation:  The Conditional Reorganization Support Service (CRSS) determined that the database needs to be reorganized, but the database is not reorganized yet because UNLOADONLY=YES is specified. The /STA DATABASE command is not issued even though STARTDB=YES is specified.

System action: The Smart Reorg utility ends with a return code of 4.

User response: Run a database reorganization after this job step. image 7002

---

The explanation sections of the following messages have been updated:

HPSG2319I   EVENT "event_name" IS DETECTED AND RC_CHANGE WILL BE APPLIED

Explanation: The event that was specified by the RC_CHANGE control statement is detected. The return code of the Smart Reorg utility is changed as specified on the RC_CHANGE control statement.

The event that is indicated by event_name is:

     
POLICY.EXCEPTIONS.CRITICAL Critical-level exceptions remain in the database.
image 7001POLICY.ACTION.REORG The database requires a reorganization.image 7002

System action: ...

User response: ...

---

HPSG0010W process_option ENDED FOR DATABASE dbdname (RC=04, RSN=xxxxxxxx)

Explanation: ...

Reason code  Meaning

...
 

image 700140100018  The automated /STA command is not issued. See message HPSG0456W.image 7002

...

System action: ...

User response: ...

---

HPSG0111E PRE-PRODUCT ERROR (reason); PROD=prodname


Explanation: ...

Reason code  Meaning

...
image 700101000008       IMS HP Unload V1 with APAR PH12333 is required.image 7002

...

System action: ...

User response: ...


Update 3

Date of change: June 2019

Change description: Documentation change to support APAR PH11511. This APAR enhances the FF Database Sensor to support encrypted VSAM ESDS database data sets.

Topic: Reorganizing a database in one job step >  Smart Reorg control statements > Control statements for the Smart Reorg Driver > SPACEALLOC control statement

A new item has been added to the Notes section as follows:

Notes:

  • If a new or reusable data set with the shadow name is not found, the Smart Reorg utility generates the commands for allocation.
  • If the original data set is not SMS-managed, and the old data set with the shadow name remains1, the volume list is derived from the old shadow data set. If the old shadow data set is not found, the volume list is derived from the original data set. You should take care whether there is enough available space on the volumes.
  • If the original data set is SMS-managed, the number of volumes and the SMS classes are derived from the original data set and the volumes are assigned by SMS.
  • image 7001To encrypt data sets with z/OS data set encryption, the original data sets must be associated to a SMS data class that has an encryption key label. image 7002
  • The primary space quantity for an OSAM shadow data set is determined by adding up the space allocated in the first three extents of the original data set. Therefore, the space allocated for the shadow data set might not match the space that was specified for the original data set.
  • If you specify CONDREORG=YES and if the Smart Reorg utility did not reorganize the database, shadow data sets are not deleted or allocated even if you specify SPACEALLOC=YES or SPACEALLOC=YES,FORCE.

Update 2

Date of change: May 2019

Change description: Documentation changes to support APAR PH09434. By this APAR, new parameters, which specify the access intent of the database, are added to the STARTDB control statement.

Topics: Changes apply to multiple topics.

==========

Topic: Reorganizing a database in one job step > Smart Reorg control statements > Control statements for the Smart Reorg Driver > STARTDB control statement

New parameters have been added as follows:

image 7001Specifies whether a /START DB command is issued automatically after the completion of the post-reorganization processing.image 7002

This control statement is optional. The default is STARTDB=NO.
image 7001
image-20190527094405-1
image 7002

STARTDB=YES must be specified together with NAMESWAP=YES, IMSCMD=YES,TOSI, and TOSIXCFGRP=.

If STARTDB=YES is specified, Smart Reorg utility sends the following command to the IMS online subsystems, to which the /DBR command has been issued by Smart Reorg utility:

  START DB dbname LOCAL DBALLOC
image 7001The second parameter of the STARTDB control statement, which is the access option and is applied as the value of the ACCESS parameter of the /START DB command, is optional and it specifies the access intent RO, RD, UP, or EX.image 7002
image 7001If the job is run for a HALDB, the /START DB command is issued for the HALDB master and HALDB partitions. If the second parameter is omitted, the ACCESS parameter is omitted and the /START DB command is issued only for HALDB partitions.image 7002
Restrictions:
  • image 7001The access option of the STARTDB control statement and the GLOBAL option of the IMSCMDOPT control statement are mutually exclusive.image 7002
  • image 7001In the following cases, the /START DB command is not issued even if STARTDB=YES is specified.image 7002
    • The reorganization processing fails.
    • The name swapping process or DBRC notification processing fails.
    • The NEWDBD control statement is specified.
    • The prefix resolution and update processing for non-HALDB is not done for logical relationships.
    • The secondary indexes building for non-HALDB is not done.
    • For HALDBs, either the ILDS is not built or the PSINDEX is not built.
    • The Image Copy Needed (ICNEEDED) flag is on.

Tip: You can change the option parameters for the /STA commands by using the IMSCMDOPT control statements. For more information, see IMSCMDOPT control statement.
==========

Topic: Troubleshooting > Messages and codes > Messages > HPSG messages

The following new message has been added:

image 7001
HPSG0252E ACCESS OPTION IN STARTDB STATEMENT IS NOT ALLOWED WHEN /STA DB GLOBAL

Explanation: The access option of the STARTDB control statement cannot be specified when the GLOBAL option of the IMSCMDOPT control statement is enabled for the /STA command.
System action: The Smart Reorg utility ends with a return code of 8.
User response: Remove the access option of the STARTDB control statement, or specify the LOCAL option for the IMSCMDOPT control statement for the /STA command.
image 7002
==========

Topic: All applicable topics.

All mentions of "/STA DATABASE" have been changed to "/START DB".


Update 1
Date of change: February 2019
Change description: Documentation changes to support APAR PH07025. This APAR enhances the IPR Unload utility to print statistics about twin chained segments in the Segment Statistics report.
Topic: Unloading a database > IPR Unload reports > Segment Statistics report
This topic has been updated as follows:
This report contains information about the segments in databases by segment type.
This report does not show the segment types of a virtual logical child.
For HDAM, PHDAM, or HISAM databases, information about the segments in the overflow area or the overflow data set is shown by segment type under SEGMENT IN OVERFLOW STATISTICS. image 7001 For HALDBs, this report is shown for each partition.
In addition to the basic information about segments, this report contains the following sections. image 7002
Variable Length Segment Statistics section
When there is any variable-length segment in a database, this section is produced as part of the Segment Statistics report. When there is no variable-length segment, this section is not printed. For HISAM databases, this section is not printed because no segment split occurs for variable-length segments.
This section shows—for each segment type—information about segments of variable-length segments (including compressed fixed-length segments).
This section does not show the segment types of virtual logical child or fixed-length segments.
Variable Length Segment Split Statistics section
When there is any variable-length segment in a database, this section is produced as part of the Segment Statistics report. When there is no variable-length segment, this section is not printed. This section shows—for each segment type—information about segments of split variable-length segments (including compressed fixed-length segments).
This section does not show the segment types of virtual logical child or fixed-length segments.
image 7001Twin Segment Statistics section
This section is always produced as a part of the Segment Statistics report. This section is not printed for HISAM and SHISAM databases.
This section shows statistics about twin chained segments.
image 7002
The following figures show examples of Segment Statistics reports.
The following figure shows an example Segment Statistic report of a case in which the following conditions are met in a HIDAM database:
  • There is no split segment
  • There are variable-length segments
  • There is no segment type for which a Segment Edit/Compression routine is specified
Figure. Segment Statistics report for a HIDAM database (The IPR Unload utility)
(Figure 153 in PDF)
image 7001
image-20190201095408-1
image 7002

The following figure shows an example Segment Statistic report of a case in which the following conditions are met in a PHDAM database:

  • There are split segments
  • There are variable-length segments
  • There is a segment type for which a Segment Edit/Compression routine is specified
  • DECOMPRESS=NO is specified

Figure. Segment Statistics report for a PHDAM database (The IPR Unload utility)

(Figure 154 in PDF)

image 7001

image-20190201095650-2

image 7002

The following figure shows an example Segment Statistic report of a case in which the following conditions are met in a HISAM database:
  • There are variable-length segments
  • There is a segment type for which a Segment Edit/Compression routine is specified
  • DECOMPRESS=YES is specified

...

The meaning of the fields in the Segment Statistics report is as follows:
...

<<< VARIABLE LENGTH SEGMENT SPLIT STATISTICS >>>
SEGMENT
...
image 7001
TWIN SEGMENT STATISTICS
The twin chain statistics section provides statistics about twin chained segments:
SEGMENT
The name of the segment.
NUMBER OF CHAINS
The total number of twin chain occurrences for the segment type. N/A is shown if a twin pointer is not defined for the segment.
MAX CHAIN LENGTH
The maximum length of the twin chains.
AVG CHAIN LENGTH
The average length of the twin chains.
image 7002

Publication Number

SC19-1137-06

Document Location

Worldwide

[{"Line of Business":{"code":"","label":""},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC3T2G","label":"IMS Database Reorganization Expert"},"ARM Category":[{"code":"","label":""}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"},{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSS8QJ","label":"IMS Database Solution Pack for z\/OS"},"ARM Category":[{"code":"a8m0z000000cvYuAAI","label":"IMS Database Reorganization Expert for z\/OS"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"},{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCLV2","label":"IMS Database Utility Solution for z\/OS"},"ARM Category":[{"code":"a8m0z000000cvYuAAI","label":"IMS Database Reorganization Expert for z\/OS"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
24 May 2021

UID

ibm10869956