A fix is available
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.Issue in wazideploy-generate with * * several files in --packageInputFile * * argument * * 2.Issue with deployment fails with * * extraVars in yaml file * * 3.Issue in wazideploy-generate when * * accessing Artifactory in anonymous * * mode * * 4.Issue in deployment with * * --processPlanTagsBeforeBeginAt * * argument and 'always' tag * * 5.Issue in deployment in a step subject * * to artifacts and artifacts list empty * * 6.Issue in deployment with --restart * * argument when the same step fails * * again * * 7.Ansible path: Issue in member_xxx and * * sequential_xxx when 2 similar name * * type in environment file * * 8.Python path: WaziDeploy is not * * compatible with ZOAU 1.4 and Python * * 3.14 * **************************************************************** 1.When several package input files in generate input, the priority of the package file was not respected and the warning was wrong in case of deletion 2.When environment file contains a variable which calls a "{{test}}" variable contained in an extra_vars file, the deployment fails with an "Undefined attribute: test" 3.The anonymous mode is not working anymore in waideloy_generate command with Artifactory 4.If a "beginat" is requested with a starting point (activity/action/step) and if there is an "always" tag on a step (located after the starting point) and if the "-pptbba" option has been set (without an "always" tag), the step with the "always" tag is not executed (skipped). 5.During deployment, if a step is subject to artifacts and artifacts list is empty, due to for example excluded or included artifacts, the deployment with --restart option fails with exception. 6.When a step fails during a deployment, we create a restart plan to execute it with just the failed artifacts in it. If it fails again in the same step, we lose the failed_artifacts in this new "restart" plan 7.Issue with member_xxx with use_native_copy and sequential_copy when using Python module through Ansible. If a deployment plan contains 2 steps, the first step being member_copy for the "sql" type and the second step being sequential_copy for the "sql2" type, the copies are done but for the sql2 type, Wazi Deploy tries to catch sql and gives the message: "No 'ds''prefix' nor 'dataset_prefix' attribute declared for pattern: 'sql'" 8.For the Python deployment path this fix adds support for ZOAU 1.4.1.x and Python 3.14. This is not applicable to the Ansible path as for now the z/OS Ansible collections does not support ZOAU 1.4
Problem conclusion
1.Fixed in this version 2.Fixed in this version 3.Fixed in this version 4.Fixed in this version 5.Fixed in this version 6.Fixed in this version 7.Fixed in this version 8.Fixed in this version
Temporary fix
Comments
APAR Information
APAR number
PH70691
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
2026-03-26
Closed date
2026-03-27
Last modified date
2026-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO07331
Modules/Macros
GDPSHTAR GDPTAR01
Fix information
Fixed component name
WAZI DEPLOY
Fixed component ID
5724T0783
Applicable component levels
R300 PSY UO07331
UP26/03/28 P F603
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:
02 April 2026