PH68489: WAZI DEPLOY INTERNAL DEFECTS AND ENHANCEMENTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Wazi Deploy internal defects and enhancements
  

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.No ability to restore artifacts to a  *
  *                        z/OS sequential data set and a z/OS   *
  *                        UNIX System Services directory.       *
  *                      2.Missing variables to specify who owns *
  *                        the objects of the z/OS UNIX System   *
  *                        Service directory.                    *
  *                      3.The use_native_copy copy option is    *
  *                        not performant enough.                *
  *                      4.The force_lock variable cannot be     *
  *                        used in conjunction with the          *
  *                        is_asa_text variable.                 *
  *                      5.No solution if a step, an action, or  *
  *                        an activity ended with a Failed       *
  *                        status and if the error that caused   *
  *                        the failure has not been processed by *
  *                        other conditional deployment          *
  *                        instructions at the activity level.   *
  *                      6.Impossible to begin the deployment at *
  *                        a specific activity, action, or step. *
  *                      7.Need for an enhancement to be able to *
  *                        use my own Jinja2 filters for a       *
  *                        Python deployment.                    *
  *                      8.No guidance on how to use Wazi Deploy *
  *                        to deploy z/OS Connect APIs on z/OS.  *
  ****************************************************************
  1.Two new restore building blocks are available:
    sequential_restore and uss_restore.
  2.The Group and owner variables are now available in uss_archive
    and uss_copy.
  3.The performances of the use_native_copy copy option have been
    greatly enhanced in the member_archive, member_copy, and
    member_restore building blocks for the deployment with Python
    or Ansible.
  4.For a Python deployment, the force_lock variable can be used
    in conjunction with the is_asa_text variable in the
    member_archive, member_copy, and member_restore building
    blocks.
  5.The rescue deployment instruction can be inserted at the root
    level of the deployment method.
  6.A new beginAt argument can be specified on the deployment
    command to begin the deployment at a specific activity,
    action, or step.
  7.You can add your own Jinja2 filters and use them in Jinja2
    templates or in the z/OS environment. By default, filters are
    searched for in the filters folder of the current working
    folder. However, you can change this default by setting the
    DEPLOY_FILTERS_PATH environment variable just before the
    invocation of the wazideploy-deploy command.
  8.A tutorial is now available in the Wazi Deploy documentation.
  

Problem conclusion

• 1.Enhancement provided
  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:

  UO05488

Modules/Macros

• GDPSHTAR GDPTAR01
  

Fix information

• Fixed component name

  WAZI DEPLOY

• Fixed component ID

  5724T0783

Applicable component levels

• R300 PSY UO05488

     UP25/10/24 P F510

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.