JR49673: DATASTAGE COMMAND DSADMIN WITH -ENVADD OPTION INTERMITTENTLY CORRUPTS DSPARAMS FILE IF MULTIPLE UPDATES OCCUR AT SAME TIME.

APAR status

• Closed as program error.

Error description

• The DataStage command:  dsadmin -envadd
  intermittently corrupts the DSParams file if multiple requests
  to add environment variables occur at the same time.
                                                                 .
  When multiple requests to update DSParams file occur at same
  time using dsadmin command, then intermittently a timing issue
  may occur that results in the environment variable value added
  to DSParams file, but the environment variable definition line
  is missing.  A valid update should create both lines.
                                                                 .
  For example the following command should add 2 lines to DSParams
  file:
    dsadmin -domain  pbmdeaddst03:9080 -user jabuiles -password
    xxx -server pbmdeaddst04 -envadd TEST -type STRING -prompt
    "DESCRIPCION" -value "VALUE" ADMINISTRACION
  but in the case of failure we only see the value line added:
    "TEST"\1\"VALUE"
  while the associated (and required) definition line such as the
  following line is missing:
    TEST\User Defined\-1\String\\0\Project\DESCRIPCION\
  
  A similar problem can occur with the -envset option.  When run
  multiple concurrent scrips which issue dsadmin -envset command
  to make multiple updates to DSParams file at same time, some
  changes may be lost due to a timing issue.
                                                                .
  The final version of patch resolves the issue for -envadd
  -envset and -envdelete options.
  

Local fix

• Remove the partial entry (value line without corresponding
  definition line) then repeat the command.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  The problem only manifests itself when adding environment
  variables to a project in a concurrent manner. Either
  using the API or the dsadmin command line.
  ****************************************************************
  PROBLEM DESCRIPTION:
  The problem is an issue with the way in which the entries
  were being added to the DSParams file. The EnvVar Value
  and Defn sections were read and updated but the lock was
  only being taken during the update. This led to some
  updates being omitted.
  ****************************************************************
  RECOMMENDATION:
  The only resolution to the problem is to apply patch JR49673
  ****************************************************************
  

Problem conclusion

• The issue was resolved by using a new interface which updated
  the specific entry under the control of locking rather than
  reconstructing the whole section and writing it back. This
  change existed in later releases and was back ported and the
  code changed to ustilise it.
  

Temporary fix

• If the problem has been encountered then the DSParams file will
  have to be cleaned up by manual editing.
  

Comments

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R810 PSY

     UP

• R910 PSY

     UP

• R912 PSY

     UP