IC89262: ERROR GENERATED WHEN EXECUTING DEPLOYER.CMD : DEPLOYALL: A DUPLICATE FILE NAME EXISTS, OR THE FILE CANNOT BE FOUND

patch_SI_5020500

APAR status

• Closed as program error.

Error description

• Environment Info: SI 5005.
  
  Problem Statement: The following message is generated onscreen
  (at the command prompt) when executing deployer.cmd (this
  message was also reported within the InstallService.log):
  deployall: A duplicate file name exists, or the file cannot be
  found
  
  Deployer.cmd appears to complete successfully despite the
  message, and system stability and functionality appear to be
  unaffected. However, the existance of the message has lead to a
  delay in the customer's testing and deployment into production.
  
  
  The cause of the message was determined to be the existence of
  the following file:
  <install dir>\Bin\deployer.cmd.donotmunge
  
  This file is generated during execution of deployer.cmd using
  the logic in the deployer.cmd.in file. Essentially, the logic
  within the deployer.cmd.in file renames the deployer.cmd.in file
  to deployer.cmd.donotmunge, and then back to deployer.cmd.in
  just before completion.
  
  If, for some reason such as a permissions issue or failure, the
  deployer.cmd.donotmunge file is not renamed back to
  deplyer.cmd.in, subsequent executions of deployer.cmd, will
  generate the message.
  
  Deletion of the deployer.cmd.donotmunge file will resolve the
  issue leading to the message.
  
  This case is being escalated so that the deployer.cmd can can be
  updated to address a situation where deployer.cmd.donotmunge
  already exists within the <install dir>\Bin\ directory.
  
  Simulation Steps: Issue was recreated on a 5.0 system .
  The deployer.cmd.donotmunge file was opened and the logic
  within it reviewed. The first step is to rename deployer.cmd.in
  to deployer.cmd.donotmunge, and one of the final steps is to
  name the file back from deployer.cmd.donotmunge to
  deployer.cmd.in.
  
  Observations: As a test the deployer.cmd.donotmunge file was
  renamed to a unique value so that deployer.cmd could complete
  the rename step from deployer.cmd.in to deployer.cmd.donotmunge
  successfully. This resolved the issue.
  
  Expected Behavior: deployer.cmd.donotmunge to be renamed
  regardless whether deployer script succeds or fails.
  

Local fix

• STRRTC: 184494
  MA/MA
  
  Circumvention:
  
  the deployer.cmd.donotmunge file was renamed to
  a unique value so that deployer.cmd could complete the rename
  step from deployer.cmd.in to deployer.cmd.donotmunge
  successfully. This resolved the issue.
  

Problem summary

• Users Affected:
  Windows Users during Install or when running deployer
  Problem Description:
  The following message is generated onscreen (at the command
  prompt) when executing deployer.cmd (this message was also
  reported within the InstallService.log):deployall: A duplicate
  file name exists, or the file cannot be found
  Platforms Affected:
  Windows
  

Problem conclusion

• Resolution Summary:
  Added change to test if file exists and clean it up as a
  dangling reference before renaming
  Delivered In:
  5010, 5104, 5020500
  

Temporary fix

Comments

• Published 4/26/2013
  

APAR Information

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

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

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels

• R500 PSY

     UP