PH71833: WAZI DEPLOY V3.0.7.1 DOESN'T CATCH THE JOB STATUS NOW SEC (NONE) AND FAIL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When submitting a jcl, the following error message Job JOB37041
  submitted with ZOAU Python API is displayed :
  *** Job status now SEC (None) security error but still pipeline
  is successfully.
  Instead, Wazi Deploy should can catch such errors and fail the
  pipeline/deployment.
  

Local fix

• Possibility to manually add a shell command after the job submit
  to make the deployment failing.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Build Engineer                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: Job that fails due to security error is *
  *                      marked as successful in evidence files  *
  ****************************************************************
  A submitted job that failed due to a security error ('SEC'
  status) is wrongly reported as succeeded in step_result in
  evidences files
  

Problem conclusion

• Fix in version 3.0.8.1
  

Temporary fix

Comments

• ×**** PE26/08/25 FIX IN ERROR. SEE APAR PH72875  FOR DESCRIPTION
  

APAR Information

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

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

  UO09034

Modules/Macros

• GDPSHTAR GDPTAR01
  

Fix information

• Fixed component name

  WAZI DEPLOY

• Fixed component ID

  5724T0783

Applicable component levels

• R300 PSY UO09034

     UP26/09/02 P F608

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.