z/OS CallAPI Interface fails after Automation Engine Upgrade

Document ID : KB000085032
Last Modified Date : 19/04/2018
Show Technical Document Details
Issue:
After an upgrade of the Automation Engine from an older version to version 11.1, 11.2, 12.0 or 12.1, the z/OS CallAPI fails. This may happen even though the CallAPI was updated as well.

Investigation

The z/OS CallAPI doesn’t encrypt messages with the encryption algorithm which is expected by the CP. So they are rejected by the CP:
U00003354 Unencrypted message of '&01' is not permitted.
 
The CallAPI output doesn’t show the cause, it just gets condition code 12:
IEF142I CALLA112 UCCALL - STEP WAS EXECUTED - COND CODE 0012
 
And the following message in the CallAPI log is issued:
U03000000 Program 'UC4 Call Interface', version '12.0.0+build.3427', change list '7854944' started.
U00003413 Socket call '0' returned error code '0'.
U03000002 Program 'UC4 Call Interface' version '12.0.0+build.3427' ended abnormally.

Sometimes the message shows a different error code:
U00003413 Socket call '0' returned error code '1'.
 
Environment:
OS: MVS
Cause:
Cause type:
Defect
Root Cause:
The z/OS CallAPI uses an older encryption algorithm. Therefore messages from it were rejected by the CP as “unencrypted”.
 
Resolution:
Update to a version listed below or a newer version if available.

Note: The name of the CallAPI utility has changed, it’s necessary to adapt it, for example in jobs, own programs, etc. More about in can be found in the Documentation: 
Integration Guide > CallAPI > Platforms for CallAPIs > CallAPI for z/OS

Fix Status: Released
Fix Version(s): Automation Engine 12.1.1 HF3 - Available
Component(s): CallAPI MVS
 
Additional Information:
Workaround:
In the UC_AS_SETTINGS within client 0 set:
COMPATIBILITY=YES
 
If the parameter is not in the UC_AS_SETTINGS variable, add it.
Once that parameter is set the z/OS CallAPI messages are accepted.

Note: To activate the change a restart of the Automation Engine in necessary.