A fix is available
APAR status
Closed as program error.
Error description
When customer uses wazideploy-generate with a list of urls to the tarballs in nexus as arguments and generate a single new tarball for the wazideploy-deploy process, then the deleted records are not recognized by wazideploy-deploy
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1.Build engineer * **************************************************************** * PROBLEM DESCRIPTION: 1.Issue when deploying artefacts with * * Wazi Deploy * **************************************************************** 1.We handle correctly the deletion for artifacts when we provide multiples tar file as input of the generate command
Problem conclusion
1.Fixed in this version
Temporary fix
Comments
APAR Information
APAR number
PH70025
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-02-06
Closed date
2026-02-17
Last modified date
2026-03-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO06853
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.
[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300"}]
Document Information
Modified date:
02 March 2026