Messages for Common Access Repository Manager (CARMA)

These are the messages that pertain to the Common Access Repository Manager (CARMA).

CRRZC0201E CRASERV: The communication is not formatted correctly.

Explanation

The communication to the CARMA server was not formatted correctly. A non-EBCDIC host code page that is set for the CARMA connection can cause incorrectly formatted communication.

User response

Disconnect from the CARMA server, check the host code page setting for the CARMA connection, reconnect, and try the action again.

CRRZC0202E CRASERV: Unknown function

Explanation

The CARMA server received a request for an unknown function. Version mismatch between the CASERV load module and the CARMA RSE miner can cause unknown functions to be called.

System programmer response

Verify that all host PTFs are properly installed and configured.

User response

Contact your system programmer.

CRRZC0203E CRASERV: CARMA has not been initialized.

Explanation

A CARMA function was called before CAMA was initialized.

User response

Disconnect from CARMA, reconnect, and try the action again.

CRRZC0204E CRASERV: The command was canceled.

Explanation

The CARMA server received a request to cancel the command.

User response

No action required.

CRRZC0205E CRASERV: Could not allocate enough memory.

Explanation

The CARMA server was unable to allocate memory.

User response

In the client, disconnect, reconnect, and try again. If it persists, increase the amount of memory available in the address space.

CRRZC0207E CRASERV: Error encountered writing to the socket.

Explanation

The CARMA server was unexpectedly unable to write to the socket.

User response

No action is required. CARMA automatically attempts to reconnect. If this problem persists, have your system programmer check your TCP/IP settings.

CRRZC0208E CRASERV: The RAM id is not valid.

Explanation

The client attempted to connect to a RAM ID that is not valid. Most likely, this error is caused when the client attempts to connect to or perform an action against a RAM ID that is not valid. A change in the host RAM configuration can cause a RAM ID to become invalid.

User response

Restart the workbench and connect to CARMA before you attempt any CARMA actions.

CRRZC0209E CRASERV: The trace level is not valid.

Explanation

The value that is specified for the trace level is invalid.

User response

In the client, disconnect from CARMA, open the CARMA connection properties, and set the trace level to the correct level. Reconnect and try your action again.

CRRZC0210E CRASERV: A valid locale was not provided.

Explanation

The value that is specified for the local was invalid.

User response

In the client, disconnect from CARMA, open the CARMA preferences, and specify a valid local parameter. Reconnect and try your action again.

CRRZC0211E CRASERV: Expected parameters were not passed.

Explanation

An expected parameter was not provided to the CARMA server from the client.

User response

If you receive this error when you are performing an action against a repository instance or the RAM itself, make sure the CARMA host components (CARMA server) are updated to the same level as the client. If you are using a custom client, have your client developer confirm the custom action ID is properly provided to the perform action method.

CRRZC0212E CRASERV: The contents were not provided.

Explanation

CRASERV did not receive contents from the CARMA server for the putMember action.

User response

Try your upload again, possibly with a different code page. You can change the host code page for an individual member in the properties for that member.

CRRZC0213E CRASERV: Internal error

Explanation

An unexpected, internal error occurred.

User response

Disconnect from CARMA, reconnect, and try your action again. If the problem persists, contact support.

CRRZC0214E CRASERV: The instance ID or filter was not provided.

Explanation

The CARMA server did not receive the expected instance ID or filter.

User response

Disconnect from CARMA, reconnect, and try the action again.

CRRZC0215E CRASERV: The instance ID or member ID was not provided.

Explanation

The CARMA server did not receive the expected instance ID or member ID.

User response

Disconnect from CARMA, reconnect, and try the action again.

CRRZC0216E CRASERV: The lrecl or numRecords is not valid.

Explanation

lrecl
the length of a record (a line in a host file)
numRecords
the number of records (lines in the host file) being sent
This error happens either when a putMember action is called on a record that has a file length of less than 0 or when the number of records sent is less than 0.

User response

Disconnect from CARMA, reconnect, and try your upload again. If the problem persists, contact support.

CRRZC0217E CRASERV: There were fewer records than specified.

Explanation

The CARMA server expected more records than the number provided for the putMember action

User response

Disconnect from CARMA, reconnect, and try your action again. If the problem persists, try with a different host code page. You can change the host code page for an individual member in the properties for that member.

CRRZC0218E CRASERV: The line is longer than the specified record length.

Explanation

A line is the member is longer than the maximum line length (lrecl).

User response

Ensure that all lines are within length limits and try the upload again.

CRRZC0219E CRASERV: The instance ID, member ID, metadata key name, or metadata value was not provided.

Explanation

The CARMA server did not receive the expected instance ID, member ID, metadata key name, or metadata value.

User response

Disconnect from CARMA, reconnect, and try the action again.

CRRZC0220E CRASERV: A timeout occurred while waiting for data on the socket.

Explanation

The CARMA server timed out while it was waiting for a command.

User response

No action is required. The CARMA server is scheduled to timeout after a certain time to keep host resources available for other users.

If the CARMA server is timing out too frequently, have your system programmer increase the timeout value. If the system uses CRASTART, modify the crastart.timeout value in CRASRV.properties. If the system uses batch submit, change the PROC 1 PORT TIMEOUT(420) line in the CRASUB* CLIST.

For more information about increasing the timeout value, see the Host Configuration Guide.

CRRZC0221E CRASERV: An expected parameter is missing for the putMember command.

Explanation

The expected parameter for the putMember function was not provided to the CARMA server from the client.

User response

If you receive this error when you are performing an action against a repository instance or the RAM itself, make sure the CARMA host components (CARMA server) are updated to the same level as the client. If you are using a custom client, have your client developer confirm the custom action ID is properly provided to the perform action method.

CRRZC0222E CRASERV: Error retrieving the Custom Action Framework parameter list.

Explanation

The CARMA server was unable to retrieve the custom action framework parameter list for the RAMtext.

User response

Disconnect from CARMA, reconnect, and try again. If the problem persists, confirm that the CRADEF VSAM file is properly setup.

CRRZC0223E CRASERV: An expected Custom Action Framework parameter is missing.

Explanation

An action was called that required a custom action framework parameter that was not provided.

User response

Shut down and restart the client. Reconnect to CARMA and the RAM before you try the action again. If you are using a custom client, have your client programmer confirm the client is providing all required parameters.

CRRZC0224E CRASERV: Unknown type specified for the Custom Action Framework parameter.

Explanation

An invalid type was specified for a parameter or return value in the CRADEF configuration VSAM.

User response

Confirm that the CRADEF VSAM file is properly set up and contains valid types for parameters and return values. Valid types are STRING, DOUBLE, LONG, and INT. For more information about valid parameter and return value types, see the CARMA Developer's Guide.

CRRZC0225E CRASERV: Error gathering Custom Action Framework returns

Explanation

The CARMA server encountered an error while reading the custom return values from the RAM.

User response

Have your system programmer confirm that the CRADEF VSAM file is properly set up and that the RAM is returning the expected results. For more information about formatting return values, see the CARMA Developer's Guide.

CRRZC0299E CRASERV: Unknown error

Explanation

An unknown error occurred in the CARMA server.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC0301E The required RAMID is missing.

Explanation

The CARMA Miner received a command that requires a RAM ID but one was not supplied by the client.

User response

Disconnect from the CARMA host, reconnect, and try the command again. If you are using a custom client, confirm that the client is calling the command correctly.

CRRZC0302E The CARMA protocol is not identified properly in the header: {0}

Explanation

{0}
the unexpected protocol provided
The communication between the CARMA Server and the CARMA Miner was corrupted. CARMA Miner was expecting a protocol that begins with "CARMA/" and instead received {0}.

User response

Disconnect from the CARMA host, reconnect, and try the command again. If you are using a custom RAM, confirm that you are not experiencing a buffer overflow condition.

CRRZC0303E Unsupported CARMA Protocol version: {0}

Explanation

{0}
the unsupported CARMA protocol version
CARMA expected a protocol version of 2 or greater, but received {0}.

User response

Disconnect from the CARMA host, reconnect, and try the command again. If you are using a custom RAM, confirm that you are not experiencing a buffer overflow condition.

CRRZC0304E Server Error: Unsupported CARMA return code {0}.

Explanation

{0}
the unexpected integer return code
CARMA expected an integer return code, but instead received {0}

User response

Disconnect from the CARMA host, reconnect, and try the command again. If you are using a custom RAM, confirm that you are not experiencing a buffer overflow condition.

CRRZC0305E The CARMA response header could not be read.

Explanation

The response header from the CARMA Server contains an unexpected character.

User response

Disconnect from the CARMA host, reconnect, and try the command again. If you are using a custom RAM, confirm that you are not experiencing a buffer overflow condition.

CRRZC0306E An unexpected end of server response has been reached.

Explanation

The server response ended unexpectedly. An unexpected end of server response can occur when the socket disconnects prematurely.

User response

Disconnect from the CARMA host, reconnect, and try the command again. If you are using a custom RAM, confirm that you are not experiencing a buffer overflow condition.

CRRZC0310E The RAM initialization state could not be located.

Explanation

The CARMA Miner does not have the initialization information that is needed to restart a connection to the RAM.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and then try your action again.

CRRZC0311W The file code-page conversion mapping is missing. Assuming the client is using the default UTF-8:LocalCP.

Explanation

The local and code page information was not sent to the host, so the default code page was used.

User response

This situation is most likely caused by an outdated client. No response is required. To remove this message, update the client.

CRRZC0312E The file code-page conversion mapping is formatted incorrectly.

Explanation

The code page conversion information that is used to download a file from CARMA is incorrectly formatted.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try your operation again. If the problem persists, verify that there is not a problem with custom client code.

CRRZC0313E Illegal CARMA object type. Expecting {0}, received {1}

Explanation

{0}
the object type that is expected by CARMA
{1}
the invalid object type provided
CARMA expected an object of type {0}, but instead had an object of type {1}

User response

Disconnect from the CARMA host at the Remote Systems view, refresh the parent container, reconnect, and try again. Confirm that any custom client code is sending the correct object types.

CRRZC0315E CARMA Expected {0,number,integer} attributes and received {1,number,integer} attributes.

Explanation

{0}
the expected number of attributes from the CARMA server
{1}
the number of attributes that are received from the CARMA server
The CARMA Miner received the incorrect number of attributes from the CARMA server. This situation can be caused by a socket communication error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try the command again. If the problem persists, ensure that all host components of CARMA are at the same level.

CRRZC0316E A duplicate item (Id={0}) was encountered in the response.

Explanation

{0}
the id that has a duplicate
A list was returned from the RAM that included duplicates of the same ID.

User response

The RAM developer must update the RAM to ensure that duplicate elements are not returned with the same ID.

CRRZC0317E Internal error: The response body is empty.

Explanation

The CARMA Miner received an empty response body from the CARMA server, possibly caused by a socket communication error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try the command again. If the problem persists, ensure that all host components of CARMA are at the same level.

CRRZC0318E Internal error: The response processor is not set.

Explanation

The CARMA Miner was not able to parse a response from the CARMA Server because of an internal error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try the command again. If the problem persists, contact technical support.

CRRZC0320E Server Error: The metadata key could not be read.

Explanation

The CARMA Miner was unable to read a metadata key.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try again. If you are using a custom RAM, ensure that the RAM does not return any special characters within metadata keys.

CRRZC0321E Server Error: The metadata value could not be read.

Explanation

The CARMA Miner was unable to read a metadata value.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try again. If you are using a custom RAM, ensure that the RAM does not return any special characters within metadata values.

CRRZC0350E Server Error: The return contents size from the response could not be determined.

Explanation

The CARMA Miner received an invalid response from the CARMA server, possibly caused by a socket communication error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try again. If the problem persists, ensure that all host components are at the same level.

CRRZC0351E Server Error: The returns contents size "{0}" is improperly formatted.

Explanation

{0}
The CARMA Miner received an invalid response from the CARMA server, possibly caused by a socket communication error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try again. If the problem persists, ensure that all host components are at the same level.

CRRZC0352E Server Error: The CARMA Response Body could not be processed.

Explanation

The CARMA Miner received an invalid response from the CARMA server, possibly caused by a socket communication error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try again. If the problem persists, ensure that all host components are at the same level.

CRRZC0360E Server Error: The Container check failed due to an improperly formatted CARMA response body.

Explanation

While the CARMA Miner was getting container contents, it received an invalid response from the CARMA server. This situation can be caused by a socket communication error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try again. If the problem persists, confirm that all host components are at the same level. If you are using a custom RAM, ensure that control characters are not used in MemberIDs.

CRRZC0370E Expected {0} attributes and received {1} attributes.

Explanation

{0}
the expected number of attributes
{1}
the received number of attributes
While the CARMA Miner was getting custom action framework information, it received an invalid response from the CARMA server. This situation can be caused by a socket communication error.

User response

Disconnect from the CARMA host at the Remote Systems view, reconnect, and try again. If the problem persists, ensure that all host components are at the same level. Ensure that no newline characters are used in the VSAM configuration files.

CRRZC0371E A duplicate item (Id={0}) encountered in the response. Error in CARMA's Custom Action Framework configuration.

Explanation

{0}
the duplicate id
Two items in the CARMA VSAM configuration files have the same id, {0}.

User response

Have your system programmer or Custom RAM Developer check the CRADEF VSAM file and modify it so that the id provided is not duplicated. More information about the VSAM configuration files can be found in the Common Access Repository Manager (CARMA) Developer's Guide.

CRRZC0385E Improper custom action configuration section count ({0}).

Explanation

{0}
the number of custom action information received
Not enough custom action information was returned by the CARMA server, possibly due to a socket error. At least four sections of information was expected, but only {0} were received.

User response

Disconnect from the CARMA host, reconnect, and try again. If the problem persists, ensure that all CARMA files on the host are at the same level.

CRRZC0392E Invalid custom parameter type "{1}"

Explanation

{0}
the custom parameter
{1}
the invalid type
A custom parameter or return value has an invalid type. Valid types are "STRING", "DOUBLE", "LONG", and "INT".

User response

Have your system programmer or Custom RAM Developer check the CRADEF VSAM file and modify it so the custom parameters and return values all have valid types. More information about the VSAM configuration files can be found in the Common Access Repository Manager (CARMA) Developer's Guide.

CRRZC0393E The default value does not match with given type: type={0}, value={1}.

Explanation

{0}
A specified type that is required for the value
{1}
The default value of a custom parameter
A custom parameter has a default value of {1}, which is not a valid example of the type specified.

User response

Have your system programmer or Custom RAM Developer check the CRADEF VSAM file and modify it so the custom parameters all have valid default values that are based on their type. More information about the VSAM configuration files can be found in the Common Access Repository Manager (CARMA) Developer's Guide.

CRRZC0394E The parameter length for (Parameter Id={0}) is not an Integer: {1}.

Explanation

{0}
the parameter id
{1}
1
A custom parameter has a non-integer value for length in the CARMA configuration VSAM file.

User response

Have your system programmer or Custom RAM Developer check the CRADEF VSAM file and modify it so the custom parameters all have valid lengths. More information about the VSAM configuration files can be found in the Common Access Repository Manager (CARMA) Developer's Guide.

CRRZC0398E Invalid custom parameter identifier ({1}) associated with action "{2}".

Explanation

{0}
the custom parameter
{1}
the custom return value
{2}
the action
An action defined in the CARMA configuration VSAM file does not have a valid custom parameter or return value. The ID is not a valid integer or is not defined.

User response

Have your system programmer or Custom RAM Developer check the CRADEF VSAM file and modify it so all actions have valid ids for the custom parameters and return values. All parameters or return values must also be defined in the VSAM file. More information about the VSAM configuration files can be found in the Common Access Repository Manager (CARMA) Developer's Guide.

CRRZC0400E The method has already been executed. The method cannot be executed twice.

Explanation

The CARMA miner attempted to run the same command twice.

User response

Disconnect from RSE, reconnect, and try your CARMA command again.

CRRZC0401E Server Error: The Command subject could not be located on the host

Explanation

The CARMA object (member, container, repository instance) was not found on the host.

User response

Refresh the parent container, and try the action again.

CRRZC0402E The required parameters are missing.

Explanation

The CARMA client did not provide the required parameters to the CARMA miner.

User response

Disconnect from RSE, reconnect RSE, reconnect CARMA, reconnect to the RAM, and then try your command again. If you are using a custom client, ensure that all required parameters are being sent to the RAM.

CRRZC0403E The CARMA connection was not initialized.

Explanation

CARMA was not initialized before a CARMA command was issued.

System programmer response

Check the CARMA startup configuration on the host.

User response

Disconnect from the CARMA connection, reconnect, and try the action again.

CRRZC0405E The server is not loaded properly. Contact the system programmer.

Explanation

The CARMA miner was unable to start the CARMA server.

User response

Have your system programmer check the CARMA startup configuration. More information about configuring CARMA can be found in the Host Configuration Guide.

CRRZC0407E The server startup was interrupted.

Explanation

While the CARMA Server was waiting to connect to the CARMA Miner, there was an interruption, possibly caused by a socket error or the RSE Miner shutting down unexpectedly.

User response

Disconnect from the CARMA host, reconnect, and try your command again.

CRRZC0408E Too many parameters to the REXX startup script.

Explanation

More parameters than expected were passed to the carma.startup.rex script.

User response

Confirm that all of the CARMA host code is at the same level. If the carma.startup.rex was modified for your installation, confirm that it is working as expected.

CRRZC0409E Could not access the configured CLIST.

Explanation

The CLIST defined in CRASRV.properties was not found by the carma.startup.rex script. The user might not have the required permissions to access the CLIST, or the location is incorrect.

User response

Confirm that the correct CLIST is defined in CRASRV.properties and that the user has permission to access it.

CRRZC0410E Server Error: The command is not supported.

Explanation

CARMA miner encountered a command that was unsupported.

System programmer response

Verify that the host and client versions of the product are the same.

User response

Disconnect from CARMA, reconnect, and try the action again.

CRRZC0411E Missing the port argument for the CARMA Host server.

Explanation

The carma.startup.rex script did not receive a port parameter, most likely caused by a modified or out of date carma.startup.rex.

User response

Confirm that all of the CARMA host code is at the same level. If the carma.startup.rex was modified for your installation, confirm that it is working as expected

CRRZC0412E Could not locate the REXX startup script.

Explanation

The CARMA Rexx script was not found. Possibly caused by the location not being an absolute location.

User response

Check the location that is defined for the CARMA startup script name in the CRASRV.properties file. "startup.script.name" provides the absolute location of the startup script.

CRRZC0413E Missing the CLIST argument for the CARMA Host server.

Explanation

The carma.startup.rex script did not receive a CLIST parameter, most likely caused by a modified or out of date carma.startup.rex.

User response

Confirm that all of the CARMA host code is at the same level. If the carma.startup.rex was modified for your installation, confirm that it is working as expected.

CRRZC0415E Starting the CARMA Host server encountered an unknown error. Please check the log.

Explanation

The CARMA startup script encountered an unknown error while it was trying to start the CARMA Server.

User response

Check the rsecomm.log file for output from the CARMA startup script. This error can be caused by errors in the CARMA Server configuration or the user not having the required permissions to start the CARMA server.

CRRZC0420E The upload did not complete successfully. Disconnect and retry the upload.

Explanation

An I/O error occurred while the file was uploading from the CARMA RSE Miner to the CARMA server. Check the rsecomm.log for more information.

User response

Disconnect from CARMA, reconnect, and try the action again.

CRRZC0421E Codepage mapping is not supported by the CARMA host.

Explanation

The local or remote code page that is set for the target CARMA member is not supported by the Host system.

User response

The code page settings for the CARMA Member can be modified on its properties page. Change the remote code page to something supported by the host system and try your file download or upload again.

CRRZC0430E The key/value set on the member could not be retrieved.

Explanation

The CARMA Miner encountered an invalid key or value while it was setting or retrieving metadata info. This situation can be caused by a socket error on the host.

User response

Disconnect from the CARMA host, reconnect, and try your command again. If you were retrieving metadata information, make sure the RAM that you are using does not use special characters for keys or values for metadata information. If you were setting metadata information, make sure that all values were non-null and did not use special characters.

CRRZC0433E DataStore State Exception: The Instance container was not found in the required location.

Explanation

The datastore that is used by the CARMA Miner has incorrect entries and an appropriate container cannot be found for the CARMA Object being worked against.

User response

Disconnect from the CARMA host, reconnect, and try your action again. If you are using custom client code, confirm it is operating correctly. If the problem persists, delete the CARMA connect, re-create it, and try your action again.
Note: Deleting the CARMA connect breaks any associations between CARMA members and local or z/OS® projects.

CRRZC0450E The download location argument could not be found.

Explanation

The CARMA Miner did not receive the location to download the member to, most likely caused by an out of date client or host.

User response

Make sure that your client and host are both at the same level. A difference greater than two levels apart is not supported

CRRZC0451E LRECL changed value during the download.

Explanation

The RAM reported a different LRECL value for the CARMA member while in the process of downloading the member.

User response

Have your RAM developer correct this error in the extractMember function.

CRRZC0452E RECFM changed value during the download.

Explanation

While the CARMA miner was chunking a file download, it received a different LRECL (logical record length) value than the download started with.

User response

Disconnect from the CARMA host, reconnect, and try transferring the file again. If you are using a custom RAM or client, make sure that LRECL is handled correctly.

CRRZC0480E The Upload handler is in an invalid state. You need to reset.

Explanation

While the CARMA miner was trying to upload a member from the client to the host, it encountered an invalid state.

User response

Disconnect from the CARMA host, reconnect, and try the upload again. If the problem persists, have your systems programmer restart the product on the host.

CRRZC0490E Error in checking container property.

Explanation

While the CARMA miner was trying to refresh the contents of a CARMA container or Repository Instance, it was not able to verify the container information.

User response

Disconnect from the CARMA host, reconnect, and try your command again. If the problem persists, try to refresh the container's container first. This problem can also be caused by incompatible versions of CARMA on the host and client. Make sure that your host and client are on the same level.

CRRZC0499E An unidentified error occurred during upload.

Explanation

An unexpected error occurred while the file was uploading to CARMA.

User response

Check the rsecomm.log file for more information about what caused the error. Disconnect from the CARMA host, reconnect, and try your upload again.

CRRZC1010E Invalid member Id search parameter: null or ""

Explanation

A find resource, or a query for a container or element supported on CARMA container or repository instances, was called with an empty or null parameter ID.

User response

Refresh the parent container and try again.

CRRZC1100E Required parameters (LRecl or RecFM) are not set. The contents cannot be uploaded.

Explanation

The file was not transferred in the proper format.

User response

Verify that the transfer format is specified correctly and try again.

CRRZC1101E Custom actions are not available: Not synchronized

Explanation

The CARMA and RAM connections are no longer synchronized.

User response

You need to disconnect and reconnect your CARMA and RAM connection.

CRRZC1102E Custom actions are not available: Not synchronized

Explanation

The CARMA and RAM connections are no longer synchronized.

User response

You need to disconnect and reconnect your CARMA and RAM connection.

CRRZC1103E An Error occurred while writing new member contents. See the Error log for more details.

Explanation

The specified character encoding is not supported when creating the new CARMA member.

User response

Change the character encoding of the source member and try again.

CRRZC1201E The RAM connect method is disabled.

Explanation

In the RAM configuration, "Connect to RAM" has been disabled.

User response

Enable "Connect to RAM" in the RAM configuration. For additional information on enabling "Connect to RAM", see "Customizing a RAM API using the CAF" in the Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).

CRRZC1202E Could not load the Repository Instances. The operation is not supported by the host Repository.

Explanation

In the RAM configuration, "Get Instances" has been disabled.

User response

Enable "Get Instances" in the RAM configuration. For additional information on enabling "Get Instances", see "Customizing a RAM API using the CAF" in the Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).

CRRZC1300E The CARMA Transport Service was not initiated.

Explanation

The transport service is the communication bridge between CARMA and the Remote System Explorer (RSE) on the client. In this case, this communication bridge was not initialized.

User response

Restart the workbench with the -clean flag.

CRRZC1304E Problems loading configuration for '{0}'

Explanation

{0}
0
Either there was a connection problem while trying to load the custom action framework (CAF) for the RAM or the configuration VSAMs (CRADEF and CRASTRS) are incorrect.

User response

Disconnect and reconnect from CARMA/RSE and try again. Additionally, have your systems administrator check the RAM setup on the host by verifying the CRADEF and CRASTRS files.

CRRZC1400E The transport layer connection was not created properly.

Explanation

The transport service is the connection bridge between CARMA and the Remote System Explorer (RSE) on the client. In this case, this communication bridge was not create properly.

User response

Restart the workbench with the -clean flag.

CRRZC1401E The Repository Manager transport service connection was not created properly.

Explanation

Your CARMA connection is no longer working.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC1402E The repository instances were not found because CARMA is not properly connected.

Explanation

Your CARMA connection is no longer working.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC1403E The CARMA transport service could not be accessed.

Explanation

The transport service is the communication bridge between CARMA and the Remote System Explorer (RSE) on the client. In this case, this communication bridge could not be accessed.

User response

Restart the workbench with the -clean flag.

CRRZC1404E Could not access Repository transport service: {0}

Explanation

{0}
0
The transport service is the communication bridge between CARMA and the Remote System Explorer (RSE) on the client. In this case, this communication bridge was not accessible.

User response

Restart the workbench with the -clean flag.

CRRZC1450E The repository managers were not loaded because CARMA is not properly connected.

Explanation

Your CARMA connection is no longer working.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC1490W Skipping extension '{0}' because of an invalid property priority: {1}. Priority must be an integer greater than 0.

Explanation

{0}
0
{1}
1,number,integer
If a transport layer has an invalid priority, then the transport layer will not be loaded.

User response

If the process works, then ignore the message. Otherwise, restart the workbench and try again.

CRRZC1501E The back end transport service could not be located using key: {0}

Explanation

{0}
0
CARMA is no longer associated with the RSE connection.

User response

Delete the CARMA connection and Create a new CARMA connection.

CRRZC1502E Could not load the TransportServiceFactory extension

Explanation

The TransportServiceFactory, which contains all loaded transport layers, was not loaded.

User response

If the process works, then ignore the message. Otherwise, restart the workbench and try again.

CRRZC1550W Could not load the CARMA compare configuration, using the default (file) compare criteria.

Explanation

The CARMA compare configuration file, syncConfig.xml cannot be found.

User response

None needed, CARMA will check the bytes of the compare files.

CRRZC1551W Could not load the CARMA compare configuration, using the default (file) compare criteria.

Explanation

The CARMA compare configuration file, syncConfig.xml cannot be found.

User response

None needed, CARMA will check the bytes of the compare files.

CRRZC1601W Could not load the structured type value ({0}): {1}

Explanation

{0}
0
{1}
1
CARMA stores its model containing the CARMA connections and any cached containers and members to disk at workspace shut down and reloads at workspace startup. In this case, there was a problem reloading this CARMA model.

User response

If CARMA connections appear broken, recreate them and try again. Otherwise, restart your workbench and try again.

CRRZC1602W Could not convert the structured type value ({0}): {1}

Explanation

{0}
0
{1}
1
CARMA stores its model containing the CARMA connections and any cached containers and members to disk at workspace shut down and reloads at workspace startup. In this case, there was a problem reloading this CARMA model.

User response

If CARMA connections appear broken, recreate them and try again. Otherwise, restart your workbench and try again.

CRRZC2001E Could not locate the CARMA Project for temporary downloads.

Explanation

When editing through the CAMRA editor, CARMA makes use of a temporary location to store temporary downloads. While processing, CARMA could not locate this temporary location.

User response

Retry opening the file. If reopening the file does not work, restart the workbench.

CRRZC2002E An error occurred creating and opening the CARMA download project.

Explanation

CARMA stores temporary downloaded files to a hidden CARMA download project. In this case, there was a problem creating or opening this project.

User response

Restart the workbench and try again. If this doesn't work, create a new workspace and try again.

CRRZC2003E An error occurred retrieving the file from the server.

Explanation

There was an error retrieving the file, and more information should be provided in an accompanying error message.

User response

Check error log for accompanying messages.

CRRZC2004E Communication error[LRecl Format]-- See the error log for details.

Explanation

CARMA has returned an invalid record length when trying to open a member.

User response

If the problem persists, have the RAM developer confirm an integer is returned for the LRecl or open the file in binary transfer mode.

CRRZC2005E The temporary element type is not valid.

Explanation

CARMA encountered an error when making a temporary element for communication with the host.

User response

Refresh the parent of the current item, and try again.

CRRZC2007E Error uploading file: {0}

Explanation

{0}
File name
There was an error uploading a file to CARMA.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC2008E The CARMA command timed out. The operation was cancelled.

Explanation

While CARMA was waiting for a response from the host, it timed out.

User response

Disconnect from RSE, reconnect, and try again. If the problem persists, it could be a configuration problem on the host.

CRRZC2009E Error uploading file: {0}

Explanation

{0}
0
There was an error uploading the file.

User response

Refresh the parent of the current item, and try again.

CRRZC2010E Error uploading file: {0} {1}

Explanation

{0}
0
{1}
1
There was an error uploading the file, and an additional message with more information will be provided.

User response

Follow the steps in the additional message. If still unsuccessful, then disconnect from CARMA, reconnect, and try again.

CRRZC2011E The key to find is not set.

Explanation

There was an unexpected error during file upload. Please report this error to technical support.

User response

Please report this error to technical support.

CRRZC2012E The line length is greater than the record size of {2} (line {0} is {1} characters long).

Explanation

{0}
2
{1}
0
{2}
1
The file could not be uploaded as the specified line number is longer than the line record length.

User response

Modify the given line of the file so that the length is shorter than the given record size.

CRRZC2013E Error uploading file: {0} {1}

Explanation

{0}
0
{1}
1
There was an error uploading the file, and an additional message with more information will be provided.

User response

Follow the steps in the additional message. If still unsuccessful, then disconnect from CARMA, reconnect, and try again.

CRRZC2014I Interrupted while waiting for the upload return

Explanation

CARMA finished sending the file to the host but was interrupted before it could get final confirmation.

User response

Confirm the contents of the file on the host, or perform the upload again.

CRRZC2017E Error uploading file: {0}

Explanation

{0}
0
There was an error uploading the text file.

User response

Disconnect from CARMA, reconnect and try again.

CRRZC2018E The LRecl is not formatted correctly: {0}

Explanation

{0}
The value for LRecl received from the RAM
The logical record length (LRecl) is not properly defined in the RAM.

User response

Contact the RAM developer to modify the RAM to return the LRecl in the proper format. For additional information on RAMs, see the Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).

CRRZC2027E Error uploading file: {0}

Explanation

{0}
0
There was an error uploading the binary file.

User response

Disconnect from CARMA, reconnect and try again.

CRRZC2044E Communication error[LRecl Format]-- See the error log for details.

Explanation

The value for the logical record length (LRecl) is not valid.

User response

Contact the RAM developer to modify the RAM to return the LRecl in the proper format. For additional information on RAMs, see the Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).

CRRZC2070E StatusChangeListener.{0} communications diagnostic started.

Explanation

{0}
0
A time out occurred while waiting for an update from the host.

User response

Disconnect from RSE, reconnect, and try again. If the problem persists, have your system's administrator check your host configuration and tune the server for the number of users connecting concurrently.

CRRZC2071E StatusChangeListener.{0}: done = {1}; cancelled = {2}; _networkDown = {3}

Explanation

{0}
status of the listener; possible values: started, working, done
{1}
true or false, if the upload completed
{2}
true or false, if the upload was canceled
{3}
true or false, if the network is down
This message provides the diagnostic information for message CRRZC2070E.

CRRZC2072E StatusChangeListener.{0}(DataStore): isConnected = {1}; isWaiting = {2}

Explanation

{0}
status of the listener; possible values: started, working, done
{1}
true or false, if the connection to the host is active
{2}
true or false, if the connection
This message provides the diagnostic information for message CRRZZC2070E.

CRRZC2073E StatusChangeListener.{0}.child{1}(DataElement): {2}

Explanation

{0}
status of the listener; possible values: started, working, done
{1}
index of the child data element (member, member attribute, container)
{2}
underlying data element representation of the CARMA object
This message provides the diagnostic information for message CRRZZC2070E.

CRRZC2074E StatusChangeListener.{0}.child{1}(Descriptor): {2}

Explanation

{0}
status of the listener; possible values: started, working, done
{1}
index of child data element (member, member attributes, container)
{2}
description of child data element, such as the attribute data that describes the child data element
This message provides the diagnostic information for message CRRZZC2070E.

CRRZC2075E StatusChangeListener.ICommunicationsDiagnostic exception

Explanation

A timeout occurred and an exception was caught while running diagnostics.

User response

Follow the user response for any messages included in the exception; otherwise, disconnect from RSE, reconnect, and try again. If the problem persists, have systems administrator check your host configuration and tune the server for the number of users connecting concurrently.

CRRZC2101E An object found in the DataStore is not valid.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2102E An object found in the DataStore is not valid.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2103E An object that is not valid was found in the CARMA Transport.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2104E An object that is not valid was found in the CARMA Transport.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2105E CARMA Transport State Exception: The member information referenced by key ({0}) was not found.

Explanation

{0}
0
CARMA requested member information for a given key, which was not found for this CARMA resource.

User response

No user response is required. The particular piece of information is not set or valid on the CARMA resource.

CRRZC2106E An object that is not valid was found in the CARMA Transport.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2107E The temporary element was not created properly.

Explanation

An error occurred that prevented the temporary element from being created properly.

User response

Disconnect you CARMA connection, reconnect, and try again.

CRRZC2108E The DataStore transport was not synchronized with CARMA. Re-create your connection.

Explanation

The CARMA connection could not be synchronized with the underlying host transport layer.

User response

Remove the CARMA connection, recreate the connection, and try again.

CRRZC2109E The command was not found: {0}

Explanation

{0}
0
The CARMA command could not be located on the host.

User response

Disconnect from the remote system explorer, reconnect, and try again. If the problem persists, confirm with a system programmer that CARMA is installed on the host and is the correct version.

CRRZC2110E The file transfer conversion mapping is not set.

Explanation

A third-party plug-in tried to set the contents of a CARMA member using internal API's.

User response

Make use of the method CARMAMember.setMemberContents() when setting the contents of a CARMA member in a third-party CARMA plug-in.

CRRZC2111E The CARMA transport cannot locate the element. Refresh at a higher level in the hierarchy.

Explanation

The host side temporary cache of the resource is missing.

User response

Try the following:
  • refreshing the object again
  • refreshing the parent object
  • disconnect and reconnect to the CARMA connection

CRRZC2112E RAM Error: The resource returned from the host changed type. The attempted command is no longer available.

Explanation

A record in the member is too long. The member has not been saved on the host.

User response

Modify the length of the line and save again.

CRRZC2113E Could not initialize. CARMA is not connected.

Explanation

CARMA is unable to connect to the Host. This can occur when CARMA is not properly configured.

User response

Check the log to see if an error was received from the CARMA Host (CRRZC2220E). If this error has occurred, contact your system programmer to verify that the host is properly configured as outline in the Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).

CRRZC2114E A temporary element for the CARMA resource, {0}, was not created.

Explanation

{0}
0
Could not create a temporary object to communicate with the host for the given resource.

User response

Refresh the resources parent, and try again.

CRRZC2115E The CARMA Transport element associated with the CARMA member is not set.

Explanation

A third-party plugin tried to set or get the contents of a CARMA member using internal API's.

User response

Use the CARMAMember.setMemberContents() and CARMAMember.getMemberContents() methods to set and get CARMA member contents respectively.

CRRZC2116E The CARMA connect operation was not successful.

Explanation

CARMA is unable to connect to the Host. This can occur when CARMA is not properly configured.

User response

Check the log to see if an error was received from the CARMA Host (CRRZC2220E). If this error has occurred, contact your system programmer to verify that the host is properly configured as outline in the Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).

CRRZC2117E The CARMA system did not connect properly after calling the connect operation.

Explanation

CARMA is unable to connect to the Host. This can occur when CARMA is not properly configured.

User response

Check the log to see if an error was received from the CARMA Host (CRRZC2220E). If this error has occurred, contact your system programmer to verify that the host is properly configured as outline in the Common Access Repository Manger (CARMA) Developers Guide.

CRRZC2118W The terminate CARMA job command did not succeed. Attempting to disconnect the system.

Explanation

There was an error trying to terminate the CARMA job during disconnect.

User response

No user action is necessary.

CRRZC2119E The CARMA disconnect operation was not successful.

Explanation

CARMA is unable to disconnect from the Host. This can occur when CARMA is not properly configured.

User response

Check the log to see if an error was received from the CARMA Host (CRRZC2220E). If this error has occurred, contact your system programmer to verify that the host is properly configured as outline in the Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).

CRRZC2122E Could not execute {0}: {1}

Explanation

{0}
the CARMA command name
{1}
a message describing the problem
The first part of the error message will provide the CARMA command name. The second part of the message includes a meaningful message of the problem.

User response

Follow the user response instruction for the second part of the message to resolve the problem.

CRRZC2123E An object that is not valid was found in the CARMA Transport.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2124E An object that is not valid was found in the CARMA Transport.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2126E An object that is not valid was found in the CARMA Transport.

Explanation

The host returned an invalid type of object for CARMA.

User response

Disconnect from the remote system explorer, reconnect, and try again.

CRRZC2128E Could not retrieve the member contents from CARMA.

Explanation

There was an error retrieving the file, and more information should be provided in an accompanying error messages.

User response

Check the error log for additional messages.

CRRZC2129E Could not upload the file to the host.

Explanation

There was an error uploading the file to the host.

User response

Follow the user response in the additional message provided.

CRRZC2200E An error was received from the CARMA Host [{0}]: [{2}] {1}

Explanation

{0}
host name
{1}
error number
{2}
error message
The error message provides more information about the problem.

CRRZC2201E CARMA Initialization is not supported.

Explanation

CARMA has been configured with the initialization function disabled and cannot start.

User response

Have the system programmer or RAM developer modify the CRADEF configuration VSAM on the host to not disable action ID 80.

CRRZC2202E The custom action framework description could not be located: This operation is not supported.

Explanation

CARMA has been configured with the custom action framework function disabled.

User response

Have the system programmer modify the CRADEF configuration VSAM on the host not to disable action ID 83.

CRRZC2203E RAM Initialization is not supported: The RAM could not be initialized.

Explanation

The RAM has been configured with the RAM initialization function disabled and cannot start.

User response

Have the system programmer modify or RAM developer the CRADEF configuration VSAM on the host not to disable action ID 0. Additionally, the intRAM() function in the RAM should not return 107 or RAM_ERR_FUNC_NOT_SUPPORTED, which states a function is not supported.

CRRZC2205E Binary Transfer is not supported.

Explanation

The version of CARMA installed on the host is out of date, and it does not support binary transfers. This error can occur when you attempt to retrieve the binary version of a file from CARMA rather than the text version.

User response

Set the transfer type to text. Alternatively, if you need the file in binary, have your system programmer update the host installation.

CRRZC2220E CARMA is not available on the specified host.

Explanation

The required CARMA jar file is not found in the class path in the Server. The server was not properly installed and configured.

User response

Contact your system programmer and report the the problem. For information on installation and configuration, see the Host Configuration Guide.

CRRZC2230E An error was encountered while processing the custom action descriptions from the host.

Explanation

When connecting to CARMA, there was an error getting the custom action descriptions.

User response

Disconnect from RSE, reconnect, and try again. Additionally, if there is an additional message included, follow the user response for that particular error message.

CRRZC2300W Could not access the key '{0}' from the RAM.

Explanation

{0}
0
CARMA could not find the stated metadata key when refreshing the metadata information.

User response

No action needs to be taken as this is an informational warning.

CRRZC2301E The connection alias name is not specified.

Explanation

CARMA could not find the stated metadata key when refreshing the metadata information.

User response

No action needs to be taken as this is an informational error message.

CRRZC2301W Could not access the key '{0}' from the RAM.

Explanation

{0}
0
CARMA is no longer associated with the RSE connection.

User response

Delete the existing CARMA connection and Create a new CARMA connection.

CRRZC2302E The connection with alias, '{0}', was not found.

Explanation

{0}
0
CARMA is no longer associated with the RSE connection.
0
The name of the connection

User response

Delete the existing CARMA connection and Create a new CARMA connection.

CRRZC2303E Connection ({0}) does not have a CARMA subsystem established.

Explanation

{0}
0
The CARMA connection is no longer associated with an RSE connection. The RSE connection could have been deleted or renamed.

User response

Recreate an RSE connection with the same name and host, and try connecting to CARMA again. Alternatively, you can remove the CARMA connection and create a new CARMA connection. Removing the CARMA connection will remove the associations between CARMA and any members extracted to remote and local projects.

CRRZC2304E The repository manager {0} was not found in the DataStore.

Explanation

{0}
0
The local Cache does not match what is on the host.

User response

Disconnect, reconnect, and refresh CARMA.

CRRZC2305E The repository instance {0} was not found in the DataStore.

Explanation

{0}
0
The local Cache does not match what is on the host.

User response

Disconnect, reconnect, and refresh the repository manager.

CRRZC2401E Invalid parameter default value '{0}' for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})

Explanation

{0}
0
{1}
1,choice,0#custom parameter|1#custom return value|2#custom field
{2}
2
The default value set in the configuration VSAM is not of the proper type.

User response

The RAM developer should modify the configuration VSAMs to have a default value of the proper type for the parameterID listed in the message.

CRRZC2402E Invalid parameter default value '{0}' for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})

Explanation

{0}
0
{1}
1,choice,0#custom parameter|1#custom return value|2#custom field
{2}
2
The default value set in the configuration VSAM is not of the proper type.

User response

The RAM developer should modify the configuration VSAMs to have a default value of the proper type for the parameterID listed in the message.

CRRZC2403E Invalid parameter default value '{0}' for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})

Explanation

{0}
invalid type that is specified in the configuration VSAM file; valid types are STRING, INT, LONG, and DOUBLE
{1}
values can be "custom parameter", "custom return value", or "custom field"
custom parameter
a parameter that is passed to the RAM
custom return value
a return value that is passed back from the RAM
custom field
a field that is defined by the RAM
{2}
The parameter id that is specified in the configuration VSAM files.
The default value set in the configuration VSAM is the wrong type.

User response

The RAM developer should modify the configuration VSAMs to have a default value of the proper type for the parameterID listed in the message.

CRRZC2405E DataStore state exception: An element type that is not allowed was found in parameter container: {0}

Explanation

{0}
0
A custom parameter, custom return value, or CARMA field is being reported as having an unsupported type.

User response

Disconnect CARMA, reconnect, and try again. If the problem persists, have the RAM developer change the parameter type to a supported one, or update the client to the same version as the host to support the new parameter type.

CRRZC2406E Cannot create the resource: The LRecl(record length) or recFM (record format) is missing from the command returns.

Explanation

CARMA or the RAM did not provide a valid for LRecl or recFM when the create member call was made.

User response

Refresh the parent container to see if the member was created by the RAM. If not, then retry the action. If the problem persists, confirm the RAM developer is setting these values.

CRRZC2407E Cannot create the resource: The name or member Id is missing from the command returns.

Explanation

CARMA or the RAM did not provide a valid name or memberID when the create member call was made.

User response

Refresh the parent container to see if the member was created by the RAM. If not, then retry the action. If the problem persists, confirm the RAM developer is setting these values.

CRRZC2410E Invalid parameter length ({0}) for {1,choice,0#custom parameter|1#custom return value|2#custom field} (parameterId={2})

Explanation

{0}
0
{1}
1,choice,0#custom parameter|1#custom return value|2#custom field
{2}
2
The length set for the parameter in the VSAM configuration is not a valid number.

User response

The RAM developer should modify the configuration VSAMs to have the parameter of the proper length for the parameterID listed in the message.

CRRZC2900W The CARMA miner version, {0}, was not parsed.

Explanation

{0}
0
Could not parse the CARMA

User response

Disconnect from RSE, reconnect, and try again. If the message persists or other problems arise, then update your client to the same version as the host.

CRRZC2901W Could not load the Repository Managers. The operation is not supported by the host Repository.

Explanation

CARMA has been configured not load the repository manager.

User response

Have the system programmer or RAM developer modify the CRADEF configuration VSAM on the host not to disable action ID 82.

CRRZC2902E RAM disconnect Unsupported: Could not disconnect from the RAM.

Explanation

The terminate RAM action is disabled, so CARMA returned with an error when trying to disconnect from the RAM.

User response

Have the system programmer or RAM developer modify the CRADEF configuration VSAM on the host not to disable action ID 01.

CRRZC2903E A RAM termination exception occurred.

Explanation

An error occurred when disconnecting the RAM.

User response

If there is an associated exception, follow the user response in that. Otherwise, no action is required.

CRRZC2904I Requesting file download to: {0}

Explanation

{0}
Location to which the file is downloaded to
Informational log message that provides the location in the local file system to which a file is downloaded.

CRRZC2905I Setting the trace level for the connection to {0}.

Explanation

{0}
Integer value that represents the host CARMA trace level
Informational message that provides the trace level of the connection. This message is expected to be logged at every CARMA connection.

CRRZC2950E The compare with action on {0} encountered an error.

Explanation

{0}
0
Unexpected error trying to perform a compare with action. The CARMA member might not exist.

User response

Refresh the parent of the CARMA member in the CARMA view, and try again.

CRRZC2951E The compare with action on {0} encountered an error.

Explanation

{0}
0
Unexpected error trying to perform a compare with. The CARMA member might not exist.

User response

Refresh the parent of the CARMA member in the CARMA view, and try again.

CRRZC5000E The subproject '{0}' is already associated with another Repository Instance: {1}

Explanation

{0}
The name of a subproject
{1}
The name of a repository
A subproject can only be associated with one repository instance. This error message shouldn't appear in versions 8.0.1 or later.

User response

Remove the association of the subproject from CARMA before trying to associate it with a new repository instance.

CRRZC5001E Extracting to a z/OS project resulted in an error. See the error log for more details.

Explanation

The local cache for CARMA is out of sync with the local host, which has caused an error during extract.

User response

Refresh the parent in the CARMA view, and try again.

CRRZC5002E Extracting to a z/OS project resulted in an error. See the error log for more details.

Explanation

CARMA unexpectedly lost connection to the host during an extract.

User response

Check your network connection, reconnect to CARMA, and try again.

CRRZC5004E The subproject '{0}' is already associated with another Repository Manager: {1}

Explanation

{0}
The name of a subproject
{1}
The name of a repository
CARMA unexpectedly lost connection to the host during an extract.

User response

Check your network connection, reconnect to CARMA, and try again.

CRRZC5010E The z/OS resource was not located on the host: {0}. Verify that the resource exists.

Explanation

{0}
The name of a remote system
During an extract from CARMA, the host resource could not be found after the RAM was instructed to create it.

User response

During an extract, the RAM must create the host resource before returning control back to CARMA. If this problem persists, talk to your RAM developer.

CRRZC5100E All the resources could not be copied into the RAM.

Explanation

When trying to copy multiple resources into the RAM a subset of the resources did not copy.

User response

Verify which resources did not copy into the RAM and retry. Also check the log for messages regarding the resources that did not copy successfully.

CRRZC5101E The CARMA resource associated with '{0}' was not found.

Explanation

{0}
0
The mapping between the resource and the CARMA resource is incorrect.

User response

Reassociate the resource with CARMA.

CRRZC5102E Could not copy the resource: {0}

Explanation

{0}
Resource name
The local cache for CARMA is out of sync with the local host, which has caused an error.

User response

Refresh the parent in the CARMA view, and try again.

CRRZC5103E Could not copy the resource: {0}

Explanation

{0}
0
CARMA unexpectedly lost connection to the host during extract.

User response

Check your network connection, reconnect to CARMA, and try again.

CRRZC5111E The z/OS project resource, {0}, was not created.

Explanation

{0}
0
Error adding the host resource to the z/OS sub project.

User response

Disconnect from RSE and reconnect, then try extracting again.

CRRZC5200E The project properties could not be retrieved for all members.

Explanation

There was an error receiving project properties for one or more of the members.

User response

Check for associated error messages and follow their user response.

CRRZC5201E The CARMA resource associated with '{0}' was not found.

Explanation

{0}
0
When attempting to retrieve properties for the listed resource, CARMA could not find the associated CARMA object. This could be caused by the identifier changing for CARMA object, possibly because of an update to the RAM.

User response

Refresh the parent of the CARMA object, and extract it again to the same location.

CRRZC5202E The properties for resource {0} were not retrieved.

Explanation

{0}
0
The mapping between the resource and the CARMA resource is incorrect.

User response

Reassociate the resource with CARMA.

CRRZC5303E The properties for resource {0} were not retrieved.

Explanation

{0}
0
CARMA unexpectedly lost connection to the host while retrieving project properties.

User response

Check your network connection, reconnect to CARMA, and try again.

CRRZC5305W Project properties cannot be copied from {0} because the SubProject is associated with {1}. Properties will still be copied from below this level and any previously copied project properties have not been changed.

Explanation

{0}
0
{1}
1

User response

CRRZC5400E The remote member was not located. Verify that the remote member or dataset exists and try again.

Explanation

The sequential data set or PDS member that is selected for extract into a z/OS project or upload into CARMA was not found.

User response

Verify that the remote member or data set exists, and try the action again.

CRRZC5950E The z/OS Subproject could not be associated with CARMA. See the error log for more details.

Explanation

CARMA encountered one or more errors when trying to associate the z/OS subproject with CARMA.

User response

Check for associated messages and follow their UR. Otherwise disconnect/reconnect RSE and try the extract again.

CRRZC7001I Views have been exported successfully.

Explanation

Information message that states that the CARMA views that were selected for export were successfully exported.

CRRZC7002W The identifier of this repository does not match the identifier of the repository from which this file was exported. Importing this file can create invalid views. Are you sure that you want to import these views?

Explanation

The views were exported from a CARMA RAM that represented views differently that the RAM into which you are importing the view.

User response

Choose to import the view if you want. Importing the view can cause unexpected errors to occur in the RAM. If problems occur, remove the imported views from the RAM.

CRRZC7003E Invalid view file selected.

Explanation

The file that was selected for import is not correctly formatted as a CARMA view file.

User response

Try the import again with a file of the correct format.

CRRZC7004I Views have been imported successfully.

Explanation

Informational message that the CARMA views that were selected for import were successfully imported.

CRRZC7005E An error occurred while CARMA was trying to save the view-export file.

Explanation

CARMA encountered an error while it was saving the view-export file.

User response

Verify that you have the correct access to the save location on the client. Check the client error log for more information.