IBM Support

PH64443: SSL ERROR WHEN USING WAZI DEPLOY PYTHON V3.0.3.1 TO DEPLOY CHANGES TO CICS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using Wazi Deploy Python building blocks to deploy changes
    into CICS,
    the CICS region requires SSL access to the port.
    
    However when attempting SSL this error is displayed :
    File "/service/IDZEE17/usr/lpp/IBM/cyp/v3r12/pyz/lib/python3.12
    /ssl.py",line 1326, in do_handshake
                   self._sslobj.do_handshake()
               ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong
    version number (_ssl.c:1001)
    

Local fix

  • A possible workaround is to unset CURL_CA_BUNDLE and
    
    unset REQUESTS_CA_BUNDLE
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 1.System engineer                            *
    *                 2.Build engineer                             *
    *                 3.Build engineer                             *
    *                 4.Build engineer                             *
    *                 5.System engineer                            *
    *                 6.Build engineer                             *
    *                 7.System engineer                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1.Use of SSL, CERT/KEY authentification *
    *                        and precise scope on CICSPlex when    *
    *                        deploying a CICS application is       *
    *                        available                             *
    *                      2.Support Latests Ansible and Python    *
    *                        Collection                            *
    *                      3.Enhancement to the Conditional        *
    *                        Deployment                            *
    *                      4.Develop new Building Block python to  *
    *                        trigger REST API                      *
    *                      5.The evidences requester does not use  *
    *                        Whoosh, a deprecated library          *
    *                      6.We add more informations in the       *
    *                        evidences file to be more complete    *
    *                        and precise                           *
    *                      7.Check that a deployment can begin     *
    ****************************************************************
    1.Absence of parameters for python cics building block (scope,
      insecure, cmci_cert, cmci_key) prevents from deploying a CICS
      application using SSL, or precising CICSPlex subsystem, or
      certificate authentification.
    2.Here are the supported versions
      - Ansible z/OS core v1.12.x and ZOAU 1.3.4.x
      - Ansible z/OS core v1.9.x and ZOAU 1.2.5.x
      - Support IBM Python for z/OS SDK 3.13 also
    3.You can add a "rescue" capability on an activity/action/step
      to handle "untrapped" exceptions during a deployment.
    4.A new Building Block allow the user to trigger REST API
    5.We use our own development library to index and query
      evidences.
    6.Informations provided in the evidences file:
      - Versions of the Ansible collections and ZOAU libraries used
        for the deployment.
      - List of important variables needed during a deployment
      - Information in the Activity/Action or Step in the evidence
        file indicating from where a jump occured and where it goes.
      - The filtered artifacts list, that matches with the excluded
        patterns defined in the environment, is present in the
        step['filtered_artifacts'] part.
    7.Before beginnig the deployment, we check that all the
      conditions are OK:
      - correct dependencies versions
      - control of variables definition
      - for Ansible, control the callback presence
    

Problem conclusion

  • 1.Fixed in this version
    2.Enhancement provided
    3.Enhancement provided
    4.Enhancement provided
    5.Enhancement provided
    6.Enhancement provided
    7.Enhancement provided
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH64443

  • Reported component name

    WAZI DEPLOY

  • Reported component ID

    5724T0783

  • Reported release

    303

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-12-06

  • Closed date

    2025-02-18

  • Last modified date

    2025-03-04

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

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

    UO02123

Modules/Macros

  • GDPSHTAR GDPTAR01
    

Fix information

  • Fixed component name

    WAZI DEPLOY

  • Fixed component ID

    5724T0783

Applicable component levels

  • R300 PSY UO02123

       UP25/02/21 P F502

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":"303"}]

Document Information

Modified date:
04 March 2025