PH36904: INZI800E ACTION: GET RC: 0X8 REASON: 0X78 ... - IBM

IBM Support

No results were found for your search query.

Tips

To return expected results, you can:

• Reduce the number of search terms. Each term you use focuses the search further.
• Check your spelling. A single misspelled or incorrectly typed term can change your result.
• Try substituting synonyms for your original terms. For example, instead of searching for "java classes", try "java training"
• Did you search for an IBM acquired or sold product ? If so, follow the appropriate link below to find the content you need.

Our apologies

Search results are not available at this time. Please try again later or use one of the other support options on this page.

PH36904: INZI800E ACTION: GET RC: 0X8 REASON: 0X78 AND SUBSEQUENT HANGINGSITUATION OR ABENDS47B OR INZU362E WITH RC 0XBA004 OR ABENDU1205

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

Notify me when an APAR for this component changes.

APAR status

• Closed as program error.

Error description

• (HPU 5.1 only) An unload run in native mode and exploiting ZIIP processors issues the following message : INZI800E ERROR ACCESSING TO A DATASET. ACTION : GET RC: 0x8 REASON: 0x78 and subsequently either : - hangs - or terminates with ABENDS47B - or terminates with completion code of 8 after having issued the following messages INZU362E UNLOAD 00001 FROM TABLESPACE dbname.tsname FAILED POS(1, 3). RC = 0xba004 INZU447E AN ERROR OCCURRED DURING UNLOAD PROCESSING - REFER TO PREVIOUS EXPLANATION MESSAGES. INZU366I UTILITY RETURN CODE 8 (REASON CODE 0xba004) This occurs only when Db2 HPU retrieves the data from an online tablespace or from a Flash Image Copy dataset. It more likely occurs if the value of VUM023/VSBUFND is set to a value lower than the default and recommended value, i.e; 360. The following subparameter VUU030/ULOPTNS will allow the customer to enable/test the fix. ------ FIX(APAR_PH36904[,VERBOSE]) APAR_PH36904 : Enables the fix of APAR PH36904. VERBOSE : specify the additional VERBOSE option to request the WTO INZX001 message be issued whenever the fix for PH36904 is used. As this issue cannot be recreated at will, this feature helps validating the fix once in place. To do so, enable the verbose mode of the fix by specifying FIX(APAR_PH36904,VERBOSE) and by controlling the output of any unload that has issued the INZX001 message. Once the fix has been validated, just ignore the INZX001 message or remove the VERBOSE option to prevent INZX001 to be issued. The fix is disabled by default. ----- As this will be an official fix, its reliability will allow the customer to install it in production and to check its impact.

Local fix

• if applicable, consider increasing the value of VUM023/VSBUFND to a value closer to 360 and, if the issue still occurs, disable the use of zIIP processors with ZIIP OFF or run the unload in SQL mode by specifying the DB2 FORCE option,

Problem summary

• **************************************************************** * USERS AFFECTED: Users of Db2 High Performance Unload * * for z/OS * **************************************************************** * PROBLEM DESCRIPTION: An unload run in native mode issues and * * exploiting zIIP processors the * * following message: * * INZI800E ERROR ACCESSING TO A DATASET. * * ACTION: GET RC: 0x8 REASON: 0x78 * * and subsequently either : * * - hangs * * - or terminates with ABENDS47B * * - or terminates with completion code of * * 8 after having issued the following * * messages * * INZU362E UNLOAD 00001 FROM * * TABLESPACE dbname.tsname FAILED * * POS(1, 3). RC = 0xba004 * * INZU447E AN ERROR OCCURRED DURING * * UNLOAD PROCESSING - REFER TO * * PREVIOUS EXPLANATION MESSAGES. * * INZU366I UTILITY RETURN CODE 8 * * (REASON CODE 0xba004) * * * * This occurs only when Db2 HPU retrieves the data from an * * online tablespace or from a Flash Image Copy dataset. * * * * It more likely occurs if the value of VUM023/VSBUFND is * * set to a value lower than the default and recommended * * value i.e; 360. * **************************************************************** * RECOMMENDATION: Apply the PTF * **************************************************************** Message INZI800E ACTION: GET RC: 0x8 REASON: 0x78 and subsequent hanging situation or ABENDS47B or INZU362E with reason code 0xba004.

Problem conclusion

• Code has been changed to fix this problem

Temporary fix

Comments

APAR Information

• APAR number

  PH36904

• Reported component name

  DB2 HI PERF UNL

• Reported component ID

  5697F4400

• Reported release

  510

• Status

  CLOSED PER

• PE

  NoPE

• HIPER

  NoHIPER

• Special Attention

  NoSpecatt / Xsystem

• Submitted date

  2021-05-04

• Closed date

  2021-07-08

• Last modified date

  2024-06-12

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• INZUTILK

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI76253

  UP21/07/14 P F107

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date: 12 June 2024

Page Feedback

Share your feedback

Need support?

• Submit feedback to IBM Support

• 1-800-IBM-7378 (USA)

• Directory of worldwide contacts