A fix is available
APAR status
Closed as program error.
Error description
When running command wazideploy -deploy to deploy some updated load modules into a CICS region, it gets to the step where CICS is called via CMCI interface, and where it passes a userid and password on that API call. This failed with the following message : ICH408I USER({'xxxxxx) GROUP( ) NAME(??? ) LOGON/JOB INITIATION - USER AT TERMINAL NOT RACF-DEFINED where xxxxx is the user ID. However this user ID is preceded with a " {' " string that provokes the error.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: 1.Build engineer * * 2.System programmer * * 3.Build engineer * * 4.Build engineer * * 5.Build engineer * **************************************************************** * PROBLEM DESCRIPTION: 1.Python translator fails when * * providing a password for a CICS * * building block * * 2.The latest version of the Python * * jsonschema module requires Rust to be * * installed * * 3.Enhancement to deploy IMS application * * 4.Enhancement to support Nexus * * repository manager * * 5.Enhancement to provide evidence * * queries/reports support * **************************************************************** 1.When the build engineer wants to provide a password for a CICS building block the Wazi Deploy Translator failed 2.Installation of the Wazi Deploy Python module requires the Python jsonschema library. The latest version of this library requires that the Rust compiler is installed, and will fail the Wazi Deploy install. 3.Enhancement to provide IMS building blocks in Wazi Deploy - Update ACBLIB with dbd & psb artefacts : ims_acb_gen - Read and/or update IMS catalog with dbds and psbs : ims_catalog_populate - Analyze and/or purge dbds and psbs from catalog : ims_catalog_purge - Launch IMS commands : ims_command - Submit DBRC command to manage RECON data sets : ims_dbrc - Build and compile MFS: ims_mfsutl 4.Wazi Deploy packager command line now supports the Nexus repository manager 5.With the new version of Wazi Deploy an evidence requester is available to audit the evidences produced during the deployment process. It analyzes the contents of the evidence files that are created at the end of each deployment. The requester involves a query language and a command. You use the Wazi Deploy query language, which involves YAML or Jinja2 coding, to specify the extraction criteria and how you want to print the result. Then, you use the new wazideploy-evidence CLI command to start the analysis.
Problem conclusion
1.This is fixed in this release. 2.The workaround is to install an old version of the Python module jsonschema. We have adjusted requirements to not be dependent on the latest versions of the upstream jsonschema library. 3.Enhancement provided 4.Enhancement provided 5.Enhancement provided
Temporary fix
Comments
APAR Information
APAR number
PH55946
Reported component name
WAZI DEPLOY
Reported component ID
5900A8N40
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2023-07-24
Closed date
2023-10-18
Last modified date
2023-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI94065
Modules/Macros
GDPTAR01
Fix information
Fixed component name
WAZI DEPLOY
Fixed component ID
5724T0783
Applicable component levels
R300 PSY UI94065
UP23/10/20 P F310
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 November 2023