001

01

N

N

If XCF is being used to request
access to a remote Multi-User
Facility, the remote Multi-User
Facility abended, or was canceled,
or XCF itself has failed.

Ensure that XCF is active and that the z/OS image on which the target Multi-User Facility was executing is available, then follow the procedure below given for internal return code 186 (hex BA) for the target Multi-User Facility.

002

02

N

N

An application was able to initially connect to the Remote Resource Manager (RRM), but currently it cannot communicate successfully
with RRM. The current CA Datacom/DB request was not processed.

Check the messages of the RRM job to determine the cause of the problem.

003

03

N

N

CA Datacom CICS Services
detected a Multi-User Facility (MUF) abend from a previous MUF
request.

This error can also be caused if a DISCONNECT IMMEDIATE is
issued while a CONNECT is being executed, because DISCONNECT IMMEDIATE requests always takes precedence. Examples of how this error could occur would be one
user issuing a DISCONNECT IMMEDIATE while a different user
is issuing a CONNECT, or if a user issues a DISCONNECT IMMEDIATE while an automatic connection is running.

Take action appropriate to the situation. The transaction to be performed in most cases is to issue a CICS ABEND. The same error code is received by all other requests from the task that is accessing this MUF.

004

04

N

N

If XCF is being used to request
access to a remote Multi-User
Facility, the remote Multi-User
Facility abended, or was canceled,
or XCF itself has failed.

Ensure that XCF is active and that the z/OS image on which the target Multi-User Facility was executing is available, then follow the procedure below given for internal return code 186 (hex BA) for the target Multi-User Facility.

013

0D

N

N

An attempt to send a request to
a MUF using XCF has failed. The
failure occurred with an XCF return code indicating that the target MUF does not exist. The request failed because the remote MUF
terminated after the last request
was successfully sent to the MUF
but before the current request was attempted.

Restart the MUF then retry the application.

014

0E

N

N

XCF environmental error such as "message buffer shortage" or "signaling paths busy." Send
request has been retried several
times and failed.

MVS systems programmer should investigate. Rerunning the job may be successful.

015

0F

N

N

Probable internal error trying to
send request/response via XCF.

Contact CA Support. For information about contacting CA Support, see Troubleshooting.

016

10

N

N

INCOMPLETE REQUEST

A request has been accepted inside the CA Datacom/DB interface, and initial processing has started. This internal return code can be received
in either of the following situations:

• If the application receives this internal return code after being returned from the interface, the request cannot be completed
  for various reasons. This error should be very rare and can
  only occur during serious error conditions, usually involving invalid memory overlay.
• This internal return code can
  also mean that the request has
  not been completed. This is the case when the application is canceled or terminated in some way while a request is in process in the Multi-User Facility. The return code then indicates
  that the request has been accepted, not that it has been returned by the interface or
  the Multi-User Facility.

If the first situation described in the explanation just given is the case, contact CA Support. If the second situation is the case, this internal return code is for information only.

018

12

N

N

The target Multi-User Facility has abended or was canceled.

Ensure that XCF is active and that the z/OS image on which the target Multi-User Facility was executing is available, then follow the procedure below given for internal return code 186 (hex BA) for the target Multi-User Facility.

019

13

N

N

An environmental error has
occurred within XCF. Either all
signal paths are busy/unavailable,
or there is an XCF buffer problem.

Retry the transaction. If this problem persists, a systems programmer may need to adjust XCF definition parameters.

020

14

N

N

There was a system error. XCF processing failed.

Retry the transaction. If the problem persists, the actual XCF return codes, which should be available in a SNAPCSA dump, should be provided to IBM support personnel.

056

38

N

N

CA Datacom CICS Services error.

None. This message is for information only.

186

BA

N

N

If the Multi-User Facility is inactive when this code is returned, the Multi-User Facility abended or was canceled with the operating system cancel command.

If the Multi-User Facility is active
when this code is returned and the application is using the Multi-Guest Sharing option or cross-partition communication (XPCC), the
Inter-User Communication Vehicle (IUCV) path or the XPCC path to
the Multi-User Facility failed.

If CA Datacom CICS Services is not being used, this code is returned to
all CA Datacom/DB program
requests until the job terminates.

Use the following procedure to recover from this type of Multi-User Facility abend.

• If MVS, execute the DBUTLTY COMM OPTION=SNAPCSA function to print a dump of the Common Storage Area.
• Execute DBMUFPR to initiate the Multi-User Facility.

197

C5

N

N

An application is executing a
request using an environment that allows the MUF to terminate during execution in special cases. One of those cases occurred.

Handle the rc 86 error by closing the existing URT and when desired, reopen the URT.