PH70041: "EDC5119I FILE TOO LARGE" ERROR WITH WAZI DEPLOY V3.0.6.2

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In Wazi Deploy 3.0.6.2 , copying a member from the uss to z/os
  PDS Dataset provokes a 'File too large' Error.
  However this worked well with 3.0.5.2.
  Building Block and member_copy are impacted (with default
  fastcopy option). It works when using use_native_copy: False
  The error is the following :
  wd_cpf_log: EDC5119I File too large. (errno2=0x05FC0119)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1.Build engineer                             *
  *                 2.Build engineer                             *
  *                 3.Build engineer                             *
  *                 4.Build engineer                             *
  *                 5.Build engineer                             *
  *                 6.Build engineer                             *
  *                 7.Build engineer                             *
  *                 8.Build engineer                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1.'File too large' error with           *
  *                        Wazi Deploy 3.0.6.2                   *
  *                      2.New restart capability for a          *
  *                        deployment                            *
  *                      3.New retry capability in the           *
  *                        deployment method                     *
  *                      4.New variables available for a Jinja2  *
  *                        template                              *
  *                      5.New shortcuts in the conditional      *
  *                        deployment to access directly an      *
  *                        activity, action or step              *
  *                      6.Handle correctly migrated data sets   *
  *                      7.Homogenize environment parameters     *
  *                        between Python and Ansible            *
  *                      8.Factorize runtime execution between   *
  *                        Ansible and Python                    *
  ****************************************************************
  1.The presence of LOW Value or HIGH Value in a file is taken
    into account now
  2.During a deployment, for some Building Blocks with artifacts,
    you can restart the same deployment only with the failed
    artifacts of the previous one
  3.You can add a retry attribute in a deployment method on
    Activity, Action or Step to execute it again after a delay
  4.Some new variables are available in a Jinja2 Template
  5.Some new shortcuts were added for a better experience in the
    queries used for Conditional Deployment
  6.Migrated data sets are well taken into account during a
    deployment
  7.We improve the environment definition and made modifications
    to have the same declarations between Python and Ansible
  8.During the execution of a deployment, if you use the Ansible
    path, you will use the same runtime execution as in Python
  

Problem conclusion

• 1.Fixed in this version
  2.Enhancement provided
  3.Enhancement provided
  4.Enhancement provided
  5.Enhancement provided
  6.Enhancement provided
  7.Enhancement provided
  8.Enhancement provided
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• GDPSHTAR GDPTAR01
  

Fix information

• Fixed component name

  WAZI DEPLOY

• Fixed component ID

  5724T0783

Applicable component levels

• R300 PSY UO06853

     UP26/03/02 P F602

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.