A fix is available
APAR status
Closed as unreproducible.
Error description
When PIPELINEs were installed during Region Initialization, the following Messages were received: . DFHPI0705 E 09/07/2008 08:02:24 REGNAME USERID PIPELINE PIPENAME encountered an error writing the configuration to the derived shelf /u/cics/sysx/shelf/xplex/REGNAME/PIPELINE/PIPENAME/. The response code from the HFS write was X'00000081' and the reason code was 'X'0594003D'. . DFHPI0709 E 09/07/2008 08:02:24 REGNAME USERID PIPELINE PIPENAME resolution failed because the XML configuration file cannot be copied to the derived shelf. . Here's what the Return Codes mean: . +------+-------+------------+---------------------------------- 129 0081 ENOENT No such file, directory, or IPC member exists. +------+-------+------------+---------------------------------- . +--------+----------------------------------------------------- 003D JRDirNotFound A directory in the pathname was not found. Action: One of the directories specified was not found. Verify that the name specified is spelled correctly. +--------+----------------------------------------------------- . The first time a CICS APPLID tries to write to (for example) the shelf named /u/cics/sysx/shelf/xplex we need to create a directory structure of the form /<APPLID>/PIPELINE which is appended to the shelf directory. The install of the first PIPELINE will create this directory then create another subdirectory using the name of its PIPELINE (PIPENAME in this case). Later PIPELINE installs will simply add their own PIPELINE name as a subdirectory of /u/cics/sysx/shelf/xplex/ REGNAME/PIPELINE/. . The creation of these subdirectories are done on L8 TCBs as the USS calls are blocking. If 2 PIPELINEs are being installed at the same time, they can both end up trying to create the /APPLID/PIPELINE subdirectory in parallel - running on their own L8 TCBs. A BPX1MKD call is needed to create each part of the subdirectory. If the first CPIR for installing PIPELINE1 creates subdirectory /APPLID just beating the second CPIR for PIPELINE2 then the second CPIR will get an EEXIST response to its BPX1MKD call (issued from DFHDHFS ?Make_HFS_directory). This will eventually cause the PIPELINE2 install to fail. This failure will get mis-reported in the log as a X'00000081' HFS write failure. The good news is that once the /APPLID/PIPELINE subdirectory has been created underneath the shelf directory this problem cannot reoccur for the named shelf. . Additional Symptom(s) Search Keyword(s): KIXREVGJT
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: During the installation of a CICS * * pipeline, msgDFHPI0705 is issued with * * response code X'00000081' and reason * * code 'X'0594003D'. * **************************************************************** * RECOMMENDATION: * **************************************************************** When CICS is installing multiple pipeline definitions that use the same shelf and the APPLID/PIPELINE subdirectories that occur below the shelf directory do not exist, it is possible for more than one task to attempt to create the directory structure at the same time as another task. This results in message DFHPI0705 with a response code of X'00000081' and a reason code of 'X'0594003D'. This is followed by message DFHPI0709. One or more of the pipelines will be installed in a disabled state. The problem happens because two tasks are running in parallel on L8 TCBs without any synchronization to avoid the simultaneous updates to the HFS. Once the directory structure is established, this error will not occur again. Additional keyword: msgDFHPI0709
Problem conclusion
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
Code has been added to module DFHDHFS to serialize writing to the HFS by using a CICS ENQUEUE/DEQUEUE.
APAR Information
APAR number
PK73826
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
400
Status
CLOSED UR3
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-10-15
Closed date
2009-02-06
Last modified date
2009-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK43834
Modules/Macros
DESDHFS DFHDHFS
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R400 PSY UK43834
UP09/02/11 P F902
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":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 March 2009