PH66050: IN WAZI DEPLOY V 3.0.4, MEMBER_ARCHIVE STEP FAILS DURING FIRST TIME DEPLOYMENT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When attempting a first time deployment, the following error
  message is received :
  "stdout": "cp: FSUM6258 cannot open file
  \\................................\\": EDC5067I An attempt was
  made to open a nonexistent file for read.",
  

Local fix

• Error can be bypassed during member_archive with an extra_vars :
  
  
  -e wd_file_not_exist_ignore_error_message='EDC5067I'
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1.System engineer                            *
  *                 2.Build engineer                             *
  *                 3.Build engineer                             *
  *                 4.Build engineer                             *
  *                 5.Build engineer                             *
  *                 6.Build engineer                             *
  *                 7.Build engineer                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1.member_archive fails if source does   *
  *                        not exist                             *
  *                      2.Capability to define the name of the  *
  *                        evidences file                        *
  *                      3.New archiveName argument in the       *
  *                        wazideploy-package command            *
  *                      4.Capability to parse Yaml file with    *
  *                        our schemas                           *
  *                      5.New Building Blocks for GDG support   *
  *                      6.New IMS_DDL Building Block            *
  *                      7.Improve existing building Blocks      *
  ****************************************************************
  1.The member_archive fails with error code EDC5067I because
    source does not exist. It should not fail because it's normal
    that source does not exist during first deployment.
  2.A new wd_evidence_file argument is available on the Ansible
    deployment command to specify the evidence file name or path
  3.A new --archiveName argument is available on the packager
    command to specify the name of the archive file
  4.You now access the Wazi Deploy YAML schemas to validate the
    structure of the configuration files, deployment method files,
    and manifest files
  5.New building blocks related to the management of Generation
    Data Group (GDG) files are now available (gdg_archive,
    gdg_copy, gdg_delete, gdg_restore)
  6.A new ims_ddl building block is available. It submits Data
    Definition Language (DDL) SQL statements
  7.The existing Wazi Deploy building blocks have been enhanced
    (shell_command, tso_command, template, http_request)
  

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
  

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:

  UO03544

Modules/Macros

• GDPSHTAR GDPTAR01
  

Fix information

• Fixed component name

  WAZI DEPLOY

• Fixed component ID

  5724T0783

Applicable component levels

• R300 PSY UO03544

     UP25/06/13 P F506

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.