z/OS CallAPI terminates with Return Code 4
Article ID: 87786
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
UCCALL - STEP WAS EXECUTED - COND CODE 0004
The z/OS CallAPI in V11.2 doesn’t work at all. The program UCXBM25C abends with Condition Code 4 (RC4):
The same Job works, when v10 Load Library is used (without any other change).
The reason is that REGION=2M, as mention in the documentation, is not sufficient anymore.
It’s recommended using REGION=0M in the JOB card of the CallAPI Job. The API will work as expected afterwards.
The documentation will be updated.
UCCALL - STEP WAS EXECUTED - COND CODE 0004
The z/OS CallAPI in V11.2 doesn’t work at all. The program UCXBM25C abends with Condition Code 4 (RC4):
UCCALL - STEP WAS EXECUTED - COND CODE 0004
The same Job works, when v10 Load Library is used (without any other change).
The reason is that REGION=2M, as mention in the documentation, is not sufficient anymore.
It’s recommended using REGION=0M in the JOB card of the CallAPI Job. The API will work as expected afterwards.
The documentation will be updated.
Environment
OS: MVS
Cause
Cause type:
Configuration
Configuration
Resolution
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.
Additional Information
Workaround :
n/a
n/a
Feedback
Yes
No
Powered by
