IBM Support

PH63950: IBM WAZI DEPLOY - INTERNAL DEFECTS AND ENHANCEMENTS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IBM Wazi Deploy 3.0.3.1
    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                            *
    *                 9. System Programmer                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Enhancement to handle Conditioning   *
    *                         in a deployment                      *
    *                      2. Enhancement to handle filter to      *
    *                         include or exclude artifacts         *
    *                      3. Enhancements on existing Building    *
    *                         Blocks                               *
    *                      4. Enhancement on the structure of the  *
    *                         evidences                            *
    *                      5. Definition of Wazi Deploy APIs       *
    *                      6. Improvement of "include_vars"        *
    *                         Building Block                       *
    *                      7. Enhancement on wazideploy-package    *
    *                      8. Better handling of command line      *
    *                         arguments                            *
    *                      9. Enhancement to simplify the          *
    *                         installation process                 *
    ****************************************************************
    1. This version introduces the conditional deployment. You can
       set the following conditions on an activity, an action, or a
       step of the deployment method:
       - "loop" to iteratively run the activity, action, or step.
       - "when" to run the activity, action, or step only if the
         condition is True.
       - "failed_when" to force the status of an activity, an
         action, or a step and exit.
       - "jumps_when" to run a specified activity, action, or step
         before or after the current activity, action, or step, when
         a condition is met.
    2. You can indicate filters to include or exclude artifacts in
       the deployment phase. You indicate these filters on the
       deployment command or in the environment variables file.
    3. The following enhancements are available on the building
       blocks:
       - When you create a building block, you can reference the
         content of the evidences. This content corresponds to the
         state of the evidences at the beginning of the building
         block execution. To reference the content of the evidences
         in the building block, use the following elements:
         - The wd_evidences variable in Ansible. For more
           information, see Creating an Ansible building block.
         - The evidences argument in the Python process method. For
           more information, see Creating a Python building block.
       - The include_vars building block is now available for
         Python.
       - A new timeout variable can be used in the
         cics_cmci_prog_create, cics_cmci_prog_delete, and
         cics_cmci_prog_update building blocks.
       - A new use_native_copy variable can be used in the
         member_archive, member_copy, and member_restore building
         blocks. If this variable is set to True, the copy step is
         faster because it uses the native UNIX System Services
         shell cp command instead of IBM Z Open Automation Utilities
         (ZOAU). However, it has fewer capabilities.
    4. The structure of the evidence file contains the following
       enhancements:
       - The status of an activity, an action, or a step is set to
         skipped if this activity, action, or step was excluded from
         the deployment or was not run because of a specified
         condition.
       - A loop_index field is generated if a loop condition is
         specified in the deployment method.
       - An args field lists the arguments of each step. It is
         always present in the Python evidence file. In the Ansible
         evidence file, it is present only if the step calls an
         Ansible module.
    5. The Wazi Deploy API is available as Python functions or
       Ansible modules. This API constitutes an alternative to the
       Wazi Deploy command-line interface. You can use it to run the
       various phases of the Wazi Deploy deployment.
    6. Some structures of the environment variables file has changed
       for the include_vars building block. Deprecation messages are
       displayed but the upward compatibility is ensured.
    7. You can now create a package locally with the Wazi Deploy
       packager command (wazideploy-package). For an example of how
       to create a local package, see the example provided in the
       packager command.
    8. Some options of The Python deployment command command have
       changed. You must now indicate the absolute path to the
       package file and the environment file.
    9. Enhancement to include all prerequisite components in the
       package. This avoids the need for additional actions in an
       air-gapped system setup.
    

Problem conclusion

  • Problem Conclusion :
    1. Enhancement provided
    2. Enhancement provided
    3. Enhancement provided
    4. Enhancement provided
    5. Enhancement provided
    6. Enhancement provided
    7. Enhancement provided
    8. Command line argument coherence
    9. Installation improvement
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH63950

  • Reported component name

    WAZI DEPLOY

  • Reported component ID

    5724T0783

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-10-30

  • Closed date

    2024-10-30

  • Last modified date

    2024-11-03

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

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

    UI98916

Modules/Macros

  • GDPTAR01
    

Fix information

  • Fixed component name

    WAZI DEPLOY

  • Fixed component ID

    5724T0783

Applicable component levels

  • R300 PSY UI98916

       UP24/11/01 P F410

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.

[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300"}]

Document Information

Modified date:
03 November 2024