1050

The RCQ chosen at startup is
not allowed by the Security Administrator.

Choose a correct value or contact your Security Administrator.

1051

The SCQ chosen at startup is
not allowed by the Security Administrator.

Choose a correct value or contact your Security Administrator.

1052

More than one RCQ option is allowed by the Security Administrator but none was
coded in the startup.

Choose a correct value or contact your Security Administrator.

1053

More than one SCQ option is allowed by the Security Administrator but none was
coded in the startup.

Choose a correct value or contact your Security Administrator.

1054

The RAQ chosen at startup is
not allowed by the Security Administrator.

Choose a correct value or contact your Security Administrator.

1055

The SQQ chosen at startup is
not allowed by the Security Administrator.

Choose a correct value or contact your Security Administrator.

1056

More than one RAQ option is allowed by the Security Administrator but none was
coded in the startup.

Choose a correct value or contact your Security Administrator.

1057

More than one SQQ option is allowed by the Security Administrator but none was
coded in the startup.

Choose a correct value or contact your Security Administrator.

1058

Level 05 security is not in place, yet a DG, DH, DP, or DQ table
class was specified in the
startup options, or, level 05 security is not in place and one
or more DQ paths were coded
on the startup with class codes
not identical to their
corresponding non-DQ
paths.

Correct the startup and resubmit.

1059

Multi-User Facility (MUF) attempts to enable with level 01 or level 02 security. These levels are no
longer supported.

Use the DTSYSTEM resource classes instead.

1060

The Master List is not for the current version.

Reassemble with the DBMSTLST macro for the current version, then initiate the Multi-User Facility.

1061

Unable to update the Directory (CXX) during MUF startup. The most likely cause is that the CXX has not been converted from an older version to the most
immediately previous
version.

If you determine that the cause is not because the CXX has not been converted from an older version to the most immediately previous version, contact CA Support. For information about contacting CA Support, see Troubleshooting.

1062

Data Sharing mode selected,
but Multi-User could not set up properly with the Coupling
Facility.

Review Data Sharing mode requirements and any other console messages to identify the problem and correct it.

1063

In z/VSE, the Master List was
not link-edited with an S
phase card (,S option).

Relink the Master List, then initiate the MUF.

1064

This is an environmental error.

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

1065

The subversion of the Master
List is not correct.

Reassemble the Master List being used with the current Master List macro.

1066

In z/VSE, the partition space is insufficient.

Allocate more space, then initiate the Multi-User Facility.

1067

In z/OS, a JCL PARM= was specified with an error in one
of the parameters or without
a leading slash (/) for the user parameter.

See the CA Datacom/DB Database and System Administration Guide for valid parameters.

1068

In z/OS, there was a failure in
the ATTACH of the subtask.

Review the specification of the DBMUFPR SUBTASK= parameter. If a z/OS message accompanies this message, see IBM documentation. If required, collect documentation and contact CA Support. For information about contacting CA Support, see Troubleshooting.

1069

When nnnn in the message is 1069, it is followed by:

aaaa MODULE - DByyyyy
where aaaa is one of the
following:

GVIS

(z/VSE). Not enough GETVIS
area space was available.

NFND

Stands for not found, referring
to the MODULE DByyyyy in
which the load was not found.

NOTV

Stands for not valid in some way. Verify the libraries are correct
and if not an obvious error,
contact CA Support.

The yyyyy field contains the
name of the related program.

Indicates that a module that needs to be loaded cannot be loaded. For information about contacting CA Support, see Troubleshooting.

1070

The MUF with external security enabled is attempting to run with unauthorized libraries.

Run the MUF from authorized libraries when using an external security product or remove the external security.

1071

The MUF is unable to sign on the user who submitted the Multi-User job.

Verify that the user is properly defined to the security system. If the problem persists, contact CA Support. For information about contacting CA Support, see Troubleshooting.

1072

Neither DB, AD, nor TR were specified in the DATACOM MUF startup option, or more than
one of the three were specified. Only the specification of one
of the three is valid.

If this is a CA Datacom/AD system, specify AD. If this is a CA Datacom TR system, specify TR. If this is a CA Datacom/DB system, specify DB. Then, restart the MUF.

1074

The specified libraries are not compatible with the MUF
startup option DATACOM
value.

The DATACOM MUF startup option must have AD specified for CA Datacom/AD or TR specified for CA Datacom TR. For a CA Datacom/DB system, you cannot use libraries built during the installation of a different system.

1075

A Statistics and Diagnostics
Area (PXX) open error
occurred.

Check for previous messages which might give further details. If there are no previous messages, contact CA Support. For information about contacting CA Support, see Troubleshooting.

1076

The DBxxRAT parameter
chosen for the MUF startup
option SECURITY is not
allowed by the Security Administrator.

Code an allowed value for this parameter.

1077

The DBxxSQL parameter
chosen for the MUF startup
option SECURITY is not allowed
by the Security Administrator.

Code an allowed value for this parameter.

1078

More than one option was
allowed by the Security Administrator for DBxxRAT,
but none was coded on the SECURITY MUF startup option.

Code an allowed value for this parameter.

1079

More than one option was
allowed by the Security Administrator for DBxxSQL,
but none was coded on the SECURITY MUF startup option.

Code an allowed value for this parameter.

1080

The operating system version/release is not
supported.

See the installation manual and the entries made when installing CA Datacom/DB. If everything seems correct, contact CA Support. For information about contacting CA Support, see Troubleshooting.

1082

The DBxxRCI parameter
chosen for the SECURITY MUF startup option is not allowed
by the Security Administrator.

Code an allowed value for this parameter.

1083

The DBxxSCI parameter chosen
for the SECURITY MUF startup option is not allowed by the Security Administrator.

Code an allowed value for this parameter.

1084

More than one option was
allowed by the Security Administrator for DBxxRCI,
but none was coded on the SECURITY MUF startup option.

Code an allowed value for this parameter.

1085

More than one option was
allowed by the Security Administrator for DBxxSCI,
but none was coded on the SECURITY MUF startup option.

Code an allowed value for this parameter.

1086

The DBxxRSR parameter
chosen for the SECURITY MUF startup option is not allowed
by the Security Administrator.

Code an allowed value for this parameter.

1087

The DBxxSSR parameter
chosen for the SECURITY MUF startup option is not allowed
by the Security Administrator.

Code an allowed value for this parameter.

1088

More than one option was
allowed by the Security Administrator for DBxxRSR,
but none was coded on the SECURITY MUF startup option.

Code an allowed value for this parameter.

1089

More than one option was
allowed by the Security Administrator for DBxxSSR,
but none was coded on the SECURITY MUF startup option.

Code an allowed value for this parameter.

1090

There is no room left in the
data space to enable this MUF.

Disable another MUF using this data space or lower the number of tasks being used.

1091

The MUF is attempting to use a data space but the Data Space
Owner (DBDSPPR) is not enabled.

Enable the Data Space Owner (DBDSPPR).

1092

A default of view security was specified in the MUF startup options, but either view security
is not active for this Multi-User
or the Security Administrator
has not allowed you to use this default option.

Either specify NO default view security on the SQLOPTION MUF startup option, or ensure that view security is active for this Multi-User and that the Security Administrator allows this default. For details about how both the default and view security are implemented in external security, see the CA Datacom Security Reference Guide.

1093

This MUF is being enabled in the same z/OS SYSPLEX as another MUF using the same CXX. This
is likely an error and could lead
to data corruption. The optional text data contains: MULTIPLE MUF'S THIS CXX NAME

If the situation is not planned and another MUF is enabled, then this error prevented a problem from occurring. If your requirements force having multiple MUFs enabled in the SYSPLEX with the same Directory (CXX) and you understand all of the way this can cause data corruption, then the MUF startup option X_CXX_ALLOW_SHARING must be set to YES.

1094

In z/OS there is another MUF enabled using the same CXX
that was not allowed for
sharing. The optional text
contains: UNSHARED MUF
THIS CXX NAME. Users are expected to have a single MUF
per CXX and the protection is
to prevent possible data
corruption if more are allowed
to execute in an unsafe way.

If not expecting multiple MUF executions in the same CXX, the error is correct and has protected you from possible data corruption. If you require multiple MUFs for one CXX and understand all the potential dangers of risk of possible data corruption, then all MUFs that need to run must have the MUF startup option X_CXX_ALLOW_SHARING must be set to YES.

1095

1101

Data Sharing mode is selected,
but the MUF could not set up properly with the Coupling Facility.

Review Data Sharing requirements and any other console messages to identify the problem and correct it.

1104

Data Sharing initialization failed during a List Lock operation.

Review Data Sharing requirements and any other console messages to identify the Coupling Facility error or MUF startup option parameter problem and correct it.

1105

Data Sharing initialization failed due to specification of a
mufname parameter on the
MUF startup option that is already in use for this instance
of the MUFplex.

Review MUF startup options and ensure that mufname is unique throughout the MUFplex.

1106

Data Sharing initialization failed due to specification of a number parameter on the MUFPLEX MUF startup option that is already
in use for this instance of the MUFplex.

Review MUF startup options and ensure that number is unique throughout the MUFplex.

1107

Data Sharing initialization failed due to specification of a locks parameter on the MUFPLEX
MUF startup option that is
different than previously
specified for active members
of the MUFplex.

Review MUF startup options and ensure that locks is identical throughout the MUFplex.

1108

Data Sharing initialization failed during a List Read operation.

Review Data Sharing requirements and any other console messages to identify the Coupling Facility error or MUF startup option parameter problem and correct it.

1109

You are attempting to enable
a MUF with the MUF startup option MUFPLEX specified, with the MUFplex number set to * (an asterisk), indicating dynamic selection is to pick the number.
At this time, however, all the possible MUFs are running, and therefore no specific number is available for dynamic selection to choose. In modes S and A the maximum is two MUFs. The maximum is seven in mode B.

None. This message is for information only. This new MUF is not appropriate. Its execution is probably a mistake.

1110

You are attempting to enable
a MUF with the MUF startup options MUFPLEX and CBS_DBID_TEMP specified, but not enough databases have been specified.

Specify enough databases as needed for the MUFPLEX number to be executed. For example, in mode S two bases should be specified.

1111

You are attempting to enable a Multi-User Facility (MUF) with
the MUF startup options
MUFPLEX and SQL_TTMID specified, but not enough databases have been specified.

Specify enough databases as needed for the MUFPLEX number to be executed. For example, in mode S two bases should be specified.

1112

You are attempting to enable a MUF with the MUF startup option MUFPLEX specified, and the DBSIDPR
module does not have enough
MUF names for the MUFplex number of this MUF as provided
in the DBSYSID parameter TARGET_MUF_LIST=.

The DBSYSID module needs enough MUF names to be specified for the MUFplex number that needs to be executed. For example, in mode S two names should be specified.

1114

An internal error occurred
during MUFplex initialization.

Contact CA Support about this internal error. For information about contacting CA Support, see Troubleshooting.

1115

Two A or S mode MUFs already exist in the MUFplex.

Ensure that only two A or S mode MUFs attempt to join the MUFplex.

1116

Two A or S mode MUFs already exist in the MUFplex.

Ensure that only two A or S mode MUFs attempt to join the MUFplex.

1117

Initial communication from a Shadow MUF (that is being
started) to a primary MUF has failed.

If you can verify that the primary MUF is active and in mode S, this is an internal error about which you should contact CA Support. For information about contacting CA Support, see Troubleshooting.

1118

Initial communication from a Shadow MUF (that is being
started) to a primary MUF has failed because the primary MUF
is not in mode S.

Check to see if the primary MUF is active and in mode S. If you can verify that the primary MUF is already active and in mode S, this is an internal error about which you should contact CA Support. For information about contacting CA Support, see Troubleshooting.

1119

Unable to join as member SHADOW.

If you can verify that MUFplex usage rules have been followed, this is an internal error about which you should contact CA Support. For information about contacting CA Support, see Troubleshooting.

1120

XCF Query function has failed.

If the error occurred in DBUTLTY, there are no members of the MUFplex for which DBUTLTY has requested reporting. If the error occurred in the MUF, there might have been a startup or restart error in another MUF in the MUFplex, in which case you should attempt to resubmit the failing MUF or MUFs. However, if that was not the case, contact CA Support about this internal error. For information about contacting CA Support, see Troubleshooting.

1121

There was an internal error
during Shadow MUF conversion.

Contact CA Support about this internal error. For information about contacting CA Support, see Troubleshooting.

1123

MUF is being executed on
hardware that is not set as z hardware as required.

Review the hardware being executed to determine its level.

1124

MUF requires a z/OS service
named IEAVAPE but it is not available or working.

Collect the documentation and contact CA Support.

1125

The MUF is not running
authorized in z/OS as required.

Authorize all the libraries used by the MUF and then execute it again.

1201

A MUF error occurred while registering or setting exit information with RRS. The message text includes whether the error occurred during the registering or setting of the exit information, and the return code received from the function.

See the return codes information documented in the appropriate IBM documentation dealing with resource recovery in MVS programming.

1202

The MUF attempted to register, with RRS, a resource manager
name that includes the current mufname specified in the Multi-User MUF startup option,
but RRS found that another MUF is already registered using that name.
The mufname must be unique within the Sysplex.

Specify a mufname in the Multi User MUF startup option that is unique within the Sysplex.

1203

The MUF attempted to set RRS exit information using the exit name of ATR.EXITMGR.IBM , which is the IBM supplied RRS exit manager. This exit manager is not
registered as an exit manager.

RRS is probably not active on this system. The MUF is invoking RRS because you specified the RRS MUF startup option. Either do not specify the RRS MUF startup option, or determine why the exit manager is not currently registered.

1204

The MUF with the RRS startup option specified is attempting to run with unauthorized libraries.

Run the MUF from authorized libraries, or do not specify the RRS MUF startup option.

1205

The CA Datacom DL1 Transparency has been requested but the modules appear invalid in content or invalid release level.

Research the transparency to see that it is the right release to allow correct MUF execution. The release of the transparency must match the release of the MUF.

1206

CACS CAAT ERROR nnn
Specifies an error nnn in finding or handling the CA Anchor Table.

Collect documentation and contact CA Support.

1207

INSTALL SYSTEM ANCHOR FAILED
Each unique MUF on a System must record its existence in a System Anchor Block. This has failed to complete and the MUF may not enable

Collect documentation and contact CA Support.

1208

DBSIDPR PC=INVALID
Specifies a bad DBSIDPR assembly that should not be possible.

Collect documentation and contact CA Support.

1209

UNABLE TO GET SYSTEM LINKAGE
Specifies an error in creating a system linkage.

Collect documentation and contact CA Support.

1210

UNABLE TO CREATE DATA SPACE
Each unique MUF on a System must create a data space for its communication on the System. This has failed to complete and the MUF may not enable.

Collect documentation and contact CA Support.

1211

CXXNAME xxxxxxxx VS yyyyyyyy
The x in the message is the CXX name as provided in the DBSIDPR module. The y is the CXX name in the CXX being used. The names do not match.

Collect documentation and contact CA Support.