A fix is available
APAR status
Closed as program error.
Error description
When purging a subconfiguration entry, the z/VM Directory Maintenance Facility satellite server can receive the following error when handling a DIRECTXA request associated with the deletion of the entry's minidisk(s): DVHREQ2290I Request is: REQUEST 166.1 MSG_USER MIGMAINT MSG_NODE VMLNX2D DVHREQ2290I MSG_LANG 1SAPI DSATCTL DIRECT MIGMAINT VMLNX2D 1SAPI DVHREQ2288I Your DSATCTL request for DIRMAINT at * has been accepted. z/VM USER DIRECTORY CREATION PROGRAM - VERSION 6 RELEASE 2.0 HCPDIR750I RESTRICTED PASSWORD FILE NOT FOUND HCPDIR666E SUBCONFIG DHCPD-1 IS NOT SPECIFIED ON ANY BUILD STATEMENTS EOJ DIRECTORY NOT UPDATED DVHXMT1191I Your DSATCTL request has been sent for processing to DVHXMT1191I DIRMAINT at VMLNX2D. DVHREQ2289E REQUEST=166 RTN=DVHREQ MSG=2289 FMT=03 SUBS= 2 DSATC, DVHREQ2289E CONT=TL DIRMAINT * DIRMSAT4 VMLNX20D DIRMSAT4 VMLNX20D - 2013/10/07; T=0.04/0.05 08:19:23 DVHWAI2140I Waiting for work on 13/10/07 at 08:19:23. The problem occurs because the DIRMAINT server continues to process the entry's deletion by removing its associated BUILD statement from the source directory without obtaining the source directory lock. Based on the timing of the deletion of the BUILD statement, error HCPDIR666E may occur when the satellite server processes a previous DIRECTXA request associated with the entry. The HCPDIR666E error in the satellite server processing causes any automated process using the DVHSAPI interface to fail the associated PURGE request. When this problem occurs in the z/VM installation upgrade procedure, the failing command must be reissued each time the error occurs. The following information is present in the INSTUPGR $CONSLOG file when this error occurs: **************************************************** * INSTUPGR $CONSLOG E * Created on: 7 Oct 2013 at 08:14:49 * By user: MIGMAINT on VMLNX2D * Command entered: INSTUPGR STAGE2 (COMMIT **************************************************** 08:14:51 Now processing line 10 of 814 08:16:12 Now processing line 20 of 814 08:17:58 Now processing line 30 of 814 DVHREQ2289E REQUEST=166 RTN=DVHREQ MSG=2289 FMT=03 SUBS= 2 DSATC, DVHREQ2289E CONT=TL DIRMAINT * DIRMSAT2 VMLNX3D DVHREQ2289E REQUEST=166 RTN=DVHREQ MSG=2289 FMT=03 SUBS= 2 DSATC, DVHREQ2289E CONT=TL DIRMAINT * DIRMSAT4 VMLNX20D 08:19:23 IUG2EX8518E The following error was returned from a call to 08:19:23 IUG2EX8518E directory exit UPGDVHXT : 08:19:23 IUG2EX8520E General error 08:19:23 IUGUPG8376E INSTUPGR ended in error
Local fix
Reissue the failing z/VM installation upgrade procedure command.
Problem summary
**************************************************************** * USERS AFFECTED: All z/VM DirMaint users in a z/VM Single * * System Image cluster environment. * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** When purging a subconfiguration entry, the z/VM Directory Maintenance Facility satellite server can receive the following error when handling a DIRECTXA request associated with the deletion of the entry's minidisk(s): DVHREQ2290I Request is: REQUEST 166.1 MSG_USER MIGMAINT MSG_NODE DVHTEST DVHREQ2290I MSG_LANG 1SAPI DSATCTL DIRECT MIGMAINT DVHTEST 1SAPI DVHREQ2288I Your DSATCTL request for DIRMAINT at * has been accepted. z/VM USER DIRECTORY CREATION PROGRAM - VERSION 6 RELEASE 2.0 HCPDIR750I RESTRICTED PASSWORD FILE NOT FOUND HCPDIR666E SUBCONFIG DHCPD-1 IS NOT SPECIFIED ON ANY BUILD STATEMENTS EOJ DIRECTORY NOT UPDATED DVHXMT1191I Your DSATCTL request has been sent for processing to DVHXMT1191I DIRMAINT at DVHTEST. DVHREQ2289E REQUEST=166 RTN=DVHREQ MSG=2289 FMT=03 SUBS= 2 DSATC, DVHREQ2289E CONT=TL DIRMAINT * DIRMSAT4 DVHTEST4 DIRMSAT4 DVHTEST4 - 2013/10/07; T=0.04/0.05 08:19:23 DVHWAI2140I Waiting for work on 13/10/07 at 08:19:23. The problem occurs because the DIRMAINT server continues to process the entry's deletion by removing its associated BUILD statement from the source directory without obtaining the source directory lock. Based on the timing of the deletion of the BUILD statement, error HCPDIR666E may occur when the satellite server processes a previous DIRECTXA request associated with the entry. The HCPDIR666E error in the satellite server processing causes any automated process using the DVHSAPI interface to fail the associated PURGE request. When this problem occurs in the z/VM installation upgrade procedure, the failing command must be reissued each time the error occurs. The following information is present in the INSTUPGR $CONSLOG file when this error occurs: **************************************************** * INSTUPGR $CONSLOG E * Created on: 7 Oct 2013 at 08:14:49 * By user: MIGMAINT on DVHTEST * Command entered: INSTUPGR STAGE2 (COMMIT) **************************************************** 08:14:51 Now processing line 10 of 814 08:16:12 Now processing line 20 of 814 08:17:58 Now processing line 30 of 814 DVHREQ2289E REQUEST=166 RTN=DVHREQ MSG=2289 FMT=03 SUBS= 2 DSATC, DVHREQ2289E CONT=TL DIRMAINT * DIRMSAT2 DVHTEST2 DVHREQ2289E REQUEST=166 RTN=DVHREQ MSG=2289 FMT=03 SUBS= 2 DSATC, DVHREQ2289E CONT=TL DIRMAINT * DIRMSAT4 DVHTEST4 08:19:23 IUG2EX8518E The following error was returned from a call to 08:19:23 IUG2EX8518E directory exit UPGDVHXT : 08:19:23 IUG2EX8520E General error 08:19:23 IUGUPG8376E INSTUPGR ended in error
Problem conclusion
DVHPURGE EXEC has been updated to obtain the source directory lock by linking the DIRMAINT 15D disk in W mode before removing the BUILD statement from the identity entry associated with the purged subconfiguration entry. In addition, UPGDVHXT EXEC has been updated to write the DVHSAPI return code to its log file when DVHSAPI returns a non-zero return code.
Temporary fix
Comments
APAR Information
APAR number
VM65444
Reported component name
VM CP
Reported component ID
568411202
Reported release
630
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-10-10
Closed date
2013-10-28
Last modified date
2017-01-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UV61208 UV61209
Modules/Macros
DVHPURGE UPGDVHXT
Fix information
Fixed component name
IBM DIRMAINT-VM
Fixed component ID
5749DVH00
Applicable component levels
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
17 January 2017