001

01

N

N

MULTI-USER FACILITY IS NOT
UP

You could have received this return code if a program requiring MUF services is being initialized but the MUF is either not up, is in the
process of terminating, is not available, or cannot be
communicated with. If the
application is using the Multi-Guest Sharing option, the Inter-User Communication Vehicle (IUCV)
paths to the MUF probably cannot
be started. If you are using CAICCI
or XCF, the connection to the Multi-User Facility may have failed.

You could also have received this return code if you have
implemented external security and
are attempting to execute a
DBUTLTY function that needs to communicate through the MUF to determine, from the security
package, whether the client is authorized to execute the action.
The needed communication cannot occur, however, because the MUF
is not up.

If the first reason is the cause of your receiving this return code, rerun the job when the MUF has been initiated or restarted.

If the second possible reason just given is the cause, see the section in the CA Datacom Security Reference Guide about the DBUTLTY resource list for information about which DBUTLTY functions can execute with the MUF down.

002

02

N

N

An attempt to establish a connection to the CA Datacom Serverr failed.

Calling WGetErrInfo( ) provides a detailed error message.

003

03

N

N

The User Requirements Table
(URT) is closed and cannot be
opened because the CONNECTION
to the Multi-User Facility (MUF) for that URT is not established.

Issue an explicit CONNECT command to the MUF containing this URT.

004

04

N

N

The application DBSYSID
parameters have requested access
to a remote Multi-User Facility using
a particular XCF group name. The
named Multi-User Facility cannot be found within the named group.

Ensure that a Multi-User Facility exsits with the requested name, and that it includes a XCFFROM MUF startup option which names the local Multi-User Facility and the group name as defined in the DBSYSID TOGROUP parameter. Rerun the job after the Multi-User Facility has been initiated.

005

05

N

N

An attempt to send a request to
the remote Multi-User Facility
has failed.

This is probably due to the remote Multi-User Facility ending with a timing situation such that the sender has not yet been notified. Restart the remote Multi-User Facility.

010

0A

N

N

Multi-User Facility is not XCF
eligible.

Ensure that all LOADLIBs for EXEC DBMUFPR are authorized.

011

0B

N

N

The application DBSYSID
parameters have requested access
to a remote MUF using a particular XCF group name. The local
application is not able to join that
XCF group, because the maximum number of members in the group already exists. This condition is
based on IBM return code 12 with reason code 08.

Restart the application and try again. If the problem persists, consult with your systems programmer regarding your Sysplex definitions.

012

0C

N

N

The application DBSYSID
parameters have requested access
to a remote Multi-User Facility. The named Multi-User Facility cannot be found within the named group.

Ensure that a Multi-User Facility exists with the requested name, and that it includes the XCFFROM option which names the local Multi-User Facility and the group name from the TOGROUP DBSYSID parameter.

013

0D

N

N

An attempt to send a request to
the remote Multi-User Facility has failed.

This is probably due to the remote Multi-User Facility ending with a timing situation such that the sender has not been notified. Restart the remote Multi-User Facility.

014

0E

N

N

XCF environmental error such as "message buffer shortage" or "signalling 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.

16

10

N

N

At the time the initial OPEN
request was received by a remote Multi-User Facility (MUF), an EOJ
had been requested for that MUF.

Issue an EOJOFF for the remote MUF, or restart the MUF.

017

11

N

N

The application DBSYSID
parameters have requested access
to a remote MUF using a particular XCF group name. The local
application is not able to join that
XCF group, because the maximum number of XCF groups already
exist. This condition is based on
IBM return code 12 with reason
code 04.

Restart the application and try again. If the problem persists, consult with your systems programmer regarding your Sysplex definitions.

018

12

N

N

The application DBSYSID
parameters have requested access
to a remote MUF using a particular XCF group name. The local
application is not able to join that
XCF group, because of a
system-level XCF environmental
error. This condition is based on
IBM return code 12 with reason
code other than 04 or 08.

Restart the application and try again. If the problem persists, consult with your systems programmer regarding your Sysplex definitions and system conditions at the time of the error.

019

13

N

N

The application DBSYSID
parameters have requested access
to a remote MUF using a particular XCF group name. The local
application is not able to join that
XCF group because of an internal error. This condition is based on
IBM return code 08 with reason
code other than 08.

Restart the application and try again. If the problem persists, capture an IPCS/SVC dump of the application and contact CA Support. For information about contacting CA Support, see Troubleshooting.

020

14

N

N

An MVS error has occurred,
resulting in an XCF failure.

MVS systems programmer should investigate.

021

15

N

N

An attempt to send a request to the remote MUF has failed, even
though the MUF was apparently available at the time the request
was made. This is probably due to
the ending of a remote MUF
involving a timing situation related
to a MUF end-of-job, such that the sender has not yet been notified.

Restart the MUF and retry the application.

194

C2

N

N

(BAD_TRANS_ACTION)

An error occured in data translation.

Examine the data being sent to or received from the CA Datacom Server and correct it.

196

C4

N

N

(CCI_CONV_PROBLEM)

An error occurred in conversing with the CA Datacom Server.

Calling WGetErrInfo( ) obtains a detailed error message.

202

CA

N

N

(MSG_PART_OVERFLOW)

When receiving a reply from the CA Datacom Server, the client interface received a message that contained a component longer than expected.

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

207

CF

N

N

(BAD_LENGTH)

The total length of the message to
be sent to the CA Datacom Server exceeded 32767 bytes.

Modify the request to reduce the number of bytes transmitted from the client to the CA Datacom Server.

209

D1

N

N

(FLOAT_ERROR)

An error occurred during the translation of floating-point data.

Examine the data being sent to or received from the CA Datacom Server and correct it.

222

DE

N

N

The CA Datacom Server was
unable to obtain memory to fulfill
the request.

Increase the size of the partition/address space used by the CA Datacom Server.

223

DF

N

N

The request type received by the
CA Datacom Server was invalid.

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

224

E0

N

N

The attachment handle received
by the CA Datacom Server was unknown.

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

226

E2

N

N

The CA Datacom Server
encountered a communications (CAICCI) error.

Contact your CA Datacom Server Administrator.

233

E9

N

N

The CA Datacom Server could
not load the RAAT/CBS command processor (SVNATPR).

Contact your CA Datacom Server Administrator.

234

EA

N

N

The CA Datacom Server could not
load the Metadata command
processor (SVMDTPR).

Contact your CA Datacom Server Administrator.

235

EB

N

N

The CA Datacom Server could not
load the URT processor (SVURTPR).

Contact your CA Datacom Server Administrator.