IBM Support

Updates to IMS High Performance Load V2.1 User's Guide

Release Notes


Abstract

Updates that apply to IMS High Performance Load V2.1 User's Guide (SC18-9222-08)

Content

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

Update 3

Date of change: February 2021

Change description: Documentation changes to support APAR PH32332.

Topics: Changes apply to multiple topics.

==========

Topic: Bitmap Resetter > Resetting bitmaps with the Bitmap Resetter utility > Bitmap Resetter control statements > ZIIPMODE control statement

Description of the COND parameter has been updated as follows:

Specifies whether Bitmap Resetter offloads eligible I/O workloads to zIIP processors.

This control statement is optional. If you do not specify this control statement, ZIIPMODE=NEVER is used.

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

COND

image 7001Offloads VSAM ESDS I/O or OSAM LDS I/O workloads to zIIP processors. COND is effective only when available zIIP processors are found. Otherwise, the job is run on the main CPs.image 7002

To apply ZIIPMODE=COND, the SGLXLOAD library of IMS™ Tools Base must be specified to the STEPLIB.

NEVER

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

==========

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

The Explanation sections of the following messages have been updated:


FABS3680W   RAA SIZE IS LARGER THAN OR EQUAL TO 4 GIGABYTES
Explanation: image 7001PSSR attempted to process a PSSR control statement that contained inconsistent values in the blk or rbn field. The product of these two values was larger than or equal to 4 GB for OSAM database.image 7002
System action: Processing continues.
User response: If your subsequent reload step allows to process an OSAM database of size larger than or equal to 4 GB, no response is needed. If not, reduce the size of the root addressable area.

---
FABS3699E "BLKSZIN" OR "NBLKSIN" (ON CONTROL STATEMENT) IS TOO LARGE
Explanation: image 7001PSSR attempted to process a FABSRT15 control statement that contained inconsistent values in the blk or rbn fields but it failed.
For the following database data sets, the product of these two values must be less than 4 GB.
  • VSAM (ESDS) database data set
  • OSAM database data set with an odd block size
  • OSAM LDS database data set without the extended addressability attribute
For the following database data sets, the product of these two values must be less than 8 GB.
  • OSAM database data set with an even block size
  • OSAM LDS database data set with the extended addressability attributeimage 7002
System action: PSSR issues a user 3699 abend.
User response: Check the FABSRT15 control statement (in the CTL DD statement) for errors in the blk or rbn (column 34 or 20) fields. Correct the error and rerun the job.

==========

Topic: Troubleshooting > Messages and codes > MessagesBitmap Resetter messages

The Explanation section of message HPSB0317E has been updated as follows:

HPSB0317E - CLOSE FAILED FOR DDNAME: ddname
Explanation: image 7001An error occurred while the database data set that is allocated to the DD ddname was being closed.image 7002
System action: Processing stops with a return code of 8.
User response: Correct the error and rerun the job.

Update 2

Date of change: September 2020

Change description: Documentation change to support APAR PH28860.

Topic: Reloading IMS databases with IMS High Performance Load > 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 as with IMS HD Reorganization Reload.

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

NO

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


Update 1

Date of change: June 2020

Change description: Documentation changes to support APAR PH22458. This APAR enhances IMS High Performance Load to support IMS OSAM database enhancement.

Topics: Changes apply to multiple topics.

==========

Topic: Reloading IMS database with IMS High Performance Load > Restrictions

This topic has been updated as follows:

IMS HP Load performs the same functions as the IMS HD Reorganization Reload utility, with certain restrictions.

The following restrictions apply to the IMS HP Load utility:

  • ...
  • ...
  • image 7001IMS catalog databases that are not registered to RECON cannot be encrypted during reload.image 7002

==========

Topic: Reloading IMS database with IMS High Performance Load > Control statements > DBIOBUF control statement

This topic has been updated as follows:

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

IMS HP Load 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. If you do not specify this control statement, DBIOBUF=30 is used for VSAMA and OSAM LDS, and DBIOBUF=15 is used for OSAM. In the case of HIDAM, DBIOBUF=15 is used.image 7002

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

==========

Topic: Troubleshooting > Messages and codes > Messages > IMS HP Load messages

The following new messages have been added:

image 7001
HPSR3680E OSAM IS DEFINED IN THE DBD BUT AN ESDS IS ALLOCATED AS A DATABASE DATA SET

Explanation: The access method is defined as OSAM in the DBD. However, IMS HP Load found an ESDS allocated for a database data set. To use ESDS, the access method must be VSAM.

System action: IMS HP Load issues a user 3672 abend and a dump.

User response: Update the access method defined in the DBD or change the allocation method for database data sets, and rerun the job.

image 7002

---

image 7001

HPSR3681E RDJFCB MACRO FAILED FOR DDNAME ddname (RC=xx)

Explanation: The RDJFCB macro failed with a return code xx for the data set that is specified for the DDNAME ddname.

System action: Process ends abnormally.

User response: Check the job log messages and other printed output for an indication that some system service has failed. If none can be found, it is likely that IMS High Performance Load has had an internal logic error. Contact IBM Software Support.

image 7002
---

User response sections of the following messages have been updated:

HPSR3614E  I/O FAILURE OCCURRED DURING A VSAM SEQUENTIAL WRITE

Explanation: An error occurred attempting a VSAM sequential write.

System action: Module HPSRVSAM issues a user 3614 abend and a dump.

User response: Register 3 contains the RPL feedback code, and register 5 contains the RPL address. The second byte of register 3 contains the return code, and the fourth byte contains the reason code. The explanation of these codes is in the DFSMS/MVS Macro Instructions for Data Sets.

image 7001If you are reloading an HIDAM or a PHIDAM database, this message likely indicates that the size of the database data set exceeds 4 GB.image 7002

Correct the error and rerun the job.

---
HPSR3784E   VSAM EXTEND FAILURE OCCURRED IN HPIO

Explanation: An error occurred while extending the VSAM data set (EXTEND VSAM) with HPIO. This error could be the result from one of the following causes:

  • The new allocation amount exceeds the maximum RBA.
  • All space is used on the current volume and no more volumes are specified.

For more information, see the IEC message that is printed before this message.

System action: Module HPSRIOIN issues a user 0004 abend.

User response: If the new allocation amount exceeds the maximum RBA, decrease the total size of the database by one of the following methods:

  • Archive old data.
  • Use segment compression.
  • Divide the database data set into two or more data set groups.
  • Convert to OSAM or HALDB.

If you are reloading an HDAM or a PHDAM database, you can also decrease the total size of the database by one of the following methods:

  • Adjust the SEARCH control statement value to decrease the number of segments that will be directed to the overflow portion of the database.
  • Decrease the number of RAA blocks if there are many unused RAPs and the RAA has a high percentage of free space.

image 7001If you are reloading an HIDAM or a PHIDAM database, this message likely indicates that the size of the database data set exceeds 4 GB.image 7002

If necessary, contact IBM Software Support.

Publication Number

SC18-9222-08

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSAVE5","label":"IMS High Performance Load for z\/OS"},"ARM Category":[{"code":"a8m0z000000cvYlAAI","label":"IMS High Performance Load"}],"Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.1.0"},{"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":"a8m0z000000cvYlAAI","label":"IMS High Performance Load"}],"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":"a8m0z000000cvYlAAI","label":"IMS High Performance Load"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
07 February 2021

UID

ibm16239250