DFS1965E APPC/MVS CALL FAILURE, FUNCTION=aaaaaaaa, REASON CODE=xxyy, RETURN CODE=xxxxxxxx, LUNAME=nnnnnnnn
Explanation
A call to APPC/MVS had an unexpected return code. The call aaaaaaaa was issued, and a return code xxxxxxxx from APPC/MVS was the result.
- -1
- Call unavailable (z/OS® entry point not defined; probable cause is bind error with level of z/OS that does not support APPC/MVS, for example, SP 4.1 or earlier).
- -2
- Call not known (probable cause is incorrect installation of IMS resulting in running modules from 2 separate IMS releases).
See z/OS: APPC/MVS Allocate Queue Services for the meaning of positive values for this return code. Error return codes that represent anticipated conditions are handled by IMS, and do not result in this message. This message is produced when an unexpected result is encountered, which might represent an abnormal condition in some system component.
The reason code variable xx is a decimal number that identifies the module associated with the code. See APPC/IMS diagnostic aids in IMS Version 15.3 Diagnosis. Variable yy is the internal reason code.
If you contact the IBM® support center, be prepared to supply the module number and reason code given in the message, and if requested, the output from LU manager trace.
If the LU name is network-qualified, it can be up to 17 bytes long.
Programmer response
Determine the error and whether the failing component is either IMS, APPC/MVS, or VTAM®. Check that IMS is running with the correct level of APPC/MVS.
Problem determination
Check for any accompanying APPC/MVS and VTAM error messages. Check the SYS1.LOGREC data set for software failure records that might accompany this condition.