A fix is available
APAR status
Closed as program error.
Error description
When using WAZI DEPLOY to obtain the result in a variable, Ansible must be set accordingly to allow the actualization step when the module is not loaded.
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.sysprog * **************************************************************** * PROBLEM DESCRIPTION: 1.The ims_command building block fails * * when a module is not loaded * * 2.Implements rename in building blocks * * 3.Consolidate IMS building block * * 4.Support latests Ansible and Python * * Collection * * 5.Support for aliases for Load Modules * * 6.The use of Jinja2 templates has been * * enhanced * * 7.Ability to include Deployment Method * * Fragment in a Deployment Method * * 8.New building block tso_command * * 9.Applying service does not remove * * previous service * **************************************************************** 1.If a module is not loaded the deployment failed during the execution of ims_command. 2.You can rename artifacts for the deployment. Then, the building blocks process these artifacts under names that are different from the names in the application package. 3.The design and implementation of the ims_mfsutl building block has been improved. A new ims_olcutl building block is available to copy a source library with your new definitions to a target library. 4.Support Ansible z/OS Core 1.8.0 collection Support ZOAU 1.2.4.5 Support Ansible IMS z/OS 3.0.0 collection Support Ansible CICS z/OS 1.0.5 5.Aliases are supported for the load module artifacts. Any aliases that are found in the PDS/E library or member can be preserved during the copy operation of the member_archive, member_copy, and member_restore building blocks. 6.The job_submit building block accepts a Jinja2 template as the source file. This template is rendered before the generated JCL is submitted. You can provide your own Jinja2 JCL template for the db2_bind_package, db2_bind_plan, ims_mfsutl, and ims_olcutl building blocks. The execution JCL that is submitted for the building block is generated from this template. 7.You can create a deployment method fragment and reuse it in various deployment methods. 8.A new tso_command building block is available to run TSO commands on the target z/OS® system. 9.During apply of service, Wazi Deploy is supposed to remove the z/OS UNIX files of the previous service level before laying down the new z/OS UNIX files. This removal fails without failing the apply step, resulting in older files still being present in z/OS UNIX.
Problem conclusion
1.Problem fixed 2.Enhancement provided 3.Enhancement provided 4.Enhancement provided 5.Enhancement provided 6.Enhancement provided 7.Enhancement provided 8.Enhancement provided 9.Corrected SMPE unpax script
Temporary fix
Comments
APAR Information
APAR number
PH59753
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-02-12
Closed date
2024-03-12
Last modified date
2024-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
GDPSHTAR GDPTAR01
Fix information
Fixed component name
WAZI DEPLOY
Fixed component ID
5724T0783
Applicable component levels
R300 PSY UI96050
UP24/03/15 P F403
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:
04 April 2024