Before using this information, be sure to read the general information under Notices for IBM Rational Developer for System z documentation.
This edition applies to IBM Rational Developer for System z Version 9.0.1 (program number 5724-T07) and to all subsequent releases and modifications until otherwise indicated in new editions.
Order publications by phone or fax. IBM Software Manufacturing Solutions takes publication orders between 8:30 a.m. and 7:00 p.m. eastern standard time (EST). The phone number is (800) 879-2755. The fax number is (800) 445-9269. Faxes should be sent Attn: Publications, 3rd floor.
You can also order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address below.
IBM welcomes your comments. You can send your comments by mail to the following address:
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Note to U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This guide provides information about the messages in Rational® Developer for System z®. This document contains information about client messages and host messages.
This book is intended for all users ofRational Developer for System z who want information about messages that the product displays.
This section of the document contains information about the client messages in Rational Developer for System z.
Most client message IDs inRational Developer for System z have the format CRRZxnnnnL, where CRRZ is the prefix for Rational Developer for System z, x is the component identifier, nnnn is a message number unique to that message, and L is the message level. The message level can have values S for severe errors, E for error, W for warning, and I for informational.
This additional information is also included in the information center forRational Developer for System z (http://publib.boulder.ibm.com/infocenter/ratdevz/v8r0/index.jsp?topic=/com.ibm.etools.rdz.messages.doc/reference/rdzmesgs.html).
These are the messages that pertain to the Debug Tool for z/OS® in Rational Developer for System z.
These are the client messages that pertain to Application Deployment Manager in Rational Developer for System z.
Messages are logged to the Application Deployment Manager activity log and optionally to the Eclipse console. You can find the name and location of the Application Deployment Manager activity log by accessing the Application Deployment Manager preferences window.
Connection to the system or region has been initiated.
No action is required.
The action listed has been performed.
No action is required.
An error was encountered while performing the specified action.
Verify that the system is active and that server code (CRD, RSE, and so on) is up and running on the remote system or region.
The action listed is being performed.
No action is required.
Connection to the system or region has been initiated.
No action is required.
An error was encountered while performing the specified action.
Verify that the system is active and that server code (CRD, RSE, and so on) is up and running on the remote system or region.
An error was encountered while performing the specified action.
Contact support.
An error was encountered while performing the specified action.
Verify that the deployment manifest file that is currently being opened had been created by Application Deployment Manager and has not been modified by a process outside of Application Deployment Manager.
An error was encountered while performing the specified action.
Verify that newly added contributors to the Application Deployment Manager framework are operational. If they are, contact support and provide this log.
An error was encountered while performing the specified action.
Contact Customer Support.
An error was encountered while performing the specified action.
Contact Customer Support.
An error was encountered while performing the specified action.
Contact Customer Support.
An error was encountered while performing the specified action.
Verify that the file system is not full and that you have permission to write to it.
An error was encountered while performing the specified action.
Verify that newly added contributors to the Application Deployment Manager framework are operational. If they are, contact Customer Support and provide this log.
The action listed is being performed.
No action is required.
The action listed has been performed.
No action is required.
An error was encountered while deploying the manifest. The error message indicates the cause.
Verify that the system is active and that server code (CRD, RSE, and so on) is up and running on the remote system or region.
An error was encountered while performing the specified action.
Verify that the system is active and that server code (CRD, RSE, and so on) is up and running on the remote system or region.
The action listed is being performed.
No action is required.
An error was encountered while performing the specified action.
Verify that the file system is not full and that you have permission to delete the manifest files from the location where it resides.
The action listed is being performed.
No action is required.
An error was encountered while performing the specified action.
Verify that newly added contributors to the Application Deployment Manager framework are operational. If they are, contact Customer Support and provide this log.
The current communications protocol might not support the requested action.
If the current communications protocol does not support the requested action, perform a different action or switch to a communication protocol that supports that action.
The messages in this section might be logged if the CICSPlex® System Manager is installed to manage CICS® resources.
You can find additional information in the following CICSPlex System Manager manuals:
All CICSPlex System Manager functions completed normally.
No action is required.
The CICSPlex System Manager command has been scheduled for processing. This condition should not occur.
Contact Customer Support.
Either an action or an attribute is not found to be associated with the CICSPlex System Manager resource table for this resource.
Contact Customer Support.
A CICSPlex System Manager Get Object command was issued, but no records were found that matched the specified search criteria.
Verify that a CICSPlex System Manager resource definition has not been inadvertently deleted.
A CICSPlex System Manager command was issued and an invalid parameter was detected. The parameter that is not valid is returned as the reason value.
Use the reason code to determine the identity of the parameter.
A CICSPlex SM command failed because of an abend or an exception condition.
Use the reason code to determine whether an abend or exception condition occurred.
A CICSPlex System Manager command failed because of an environment error.
The error occurred for one of the following reasons:
Use the reason code to determine whether a No Service, No Storage, Request Time Out, or Soc Resource condition occurred.
A CICSPlex System Manager command was not permitted because of an expired, sign-on parameter, or user ID condition.
The condition occurred for one of the following reasons:
Use the reason code to determine whether an expired, sign-on parameter, or user ID condition occurred.
A CICSPlex System Manager command failed because the result set specified on the RESULT option is being processed by another command.
Retry the operation. If the condition persists, notify Customer Support.
The CMAS to which the processing thread was connected is no longer active.
CMAS may have ended. Retry the operation. If the condition persists, notify Customer Support.
A not-available condition occurred because of an APITASK, CMAS, CPSMAPI, or MAINTPOINT error.
These errors occur for the following reasons:
CMAS may have ended. Retry the operation. If the condition persists, notify Customer Support.
A version conflict occurred.
It occurred for one of the following reasons:
Use the reason code to determine whether a NOTSUPPORTED or NOTVSNCONN condition occurred.
A CICSPlex System Manager command that is not valid was issued.
The command is not valid for one of the following reasons:
Use the reason code to determine whether a Filter or Length condition occurred.
A CICSPlex System Manager command completed processing with a warning.
The warning occurred for one of the following reasons:
Use the reason code to determine whether a MAXRECORDS, RESULT, or ACTION condition occurred.
A CICSPlex System Manager command failed because a resource table record is not valid.
The record is invalid for one of the following reasons:
Use the reason code to determine whether a DATAERROR, INVALIDATTR, or INVALIDVER condition occurred. If a DATAERROR occurred, the attributes that caused the error are flagged on the result display window.
A CICSPlex System Manager command failed because the target result set specified on the RESULT option is not compatible with the output of this command. This condition should not occur.
Contact Customer Support.
A CICSPlex System Manager DISCARD command failed because an in-use condition occurred.
The condition occurred for one of the following reasons:
Use the reason code to determine whether a FILTER or VIEW condition occurred.
A CICSPlex System Manager command failed because data that is not valid was detected.
The parameter that contains data that is not valid is returned as the reason value:
Use the reason code to determine whether a PARM or CRITERIA condition occurred.
A CICSPlex System Manager command failed because the specified view already exists and cannot be built. This condition should not occur.
Contact Customer Support.
An error message in this group is logged when a CICS system managed by CICSPlex System Manager rejects a request to create a CICS resource definition, and the returned CICSPlex SM error code indicates that the request includes an invalid attribute value. The Application Deployment Manager typically handles this error as follows:
Each of the messages in this group corresponds to a particular value of the returned CICSPlex SM error code. For more information about individual error codes see the following publication:
The proper user response is to correct the invalid attribute value and submit the request again.
The data supplied for a resource table attribute is invalid for that attribute.
Review the description of the attributes in the IBM® CICSPlex SM documentation. Then correct the error and send the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected a request because the requested resource was not found.
Verify that the requested resource exists, then send the request again. Contact your system administrator if the problem is not resolved. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected a request to create a CICS resource because the resource already exists.
Specify a different resource name, then send the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected a request because the resource has already changed.
Verify the status of the resource, then send the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected the request because the resource type is not valid.
Verify that the resource type is correct, then send the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected the request because the resource version is not valid.
Correct the error, then send the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
An attempt to create a resource definition has failed because the maintenance point CMAS for the CICSPlex is not available. Either the maintenance point CMAS itself, or the link to it, has failed.
Wait for the maintenance point CMAS for the CICSPlex to become available, then retry the action. If necessary, contact your system administrator. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected the request because the CICSPlex was not found.
Verify that the specified CICSPlex exists, then send the request again. Contact your system administrator if the problem is not resolved. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected a request to create a CICS resource because the request would create an inconsistent set of resources.
Review the information in this message to determine why the attempted update would cause an inconsistent set of resources. If the message indicates that an override expression was specified for the resource assignment, the expression might be the cause of the conflict. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected a request to create a CICS resource because the specified resource group was not found.
Verify that the requested resource exists, then send the request again. Contact your system administrator if the problem is not resolved. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The CICSPlex System Manager rejected the request because the action is not valid in this context.
Verify the system environment and the availability of resources, then send the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code INV_RECADDR was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code INV_RECLEN was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code DIFF_VERSION was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code EARLY_NAMELIST_END was returned.
Correct the error and submit the request again.
The error code INV_NAMELIST was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code INV_NAME was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code INV_MINNAME was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code NOTIFY was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code PARTIAL_INSTALL was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
The error code NOTHING_INSTALLED was returned.
Correct the error and submit the request again. See Explanations and user responses for messages CRRZA1100E - CRRZA1143E.
You must specify a target.
Specify a target.
You must specify a related system.
Specify a related system.
This message indicates that an error occurred during a request made to CPSM.
See the CPSM documentation to determine the cause for scope conflicts.
A WSBIND file must be selected before you can use the View function.
Select a WSBIND file.
An active RSE connection must be available to retrieve the WSBIND file.
Create an active RSE connection.
Resource {0} must be loaded to determine the name of the physical data set in which {0} resides.
Load Resource {0}.
Only selected CICS RESP2 codes are documented in this publication. For additional information see the following books:
These error messages can occur only if the remote CICS system is not managed by a CICSPlex System Manager. When this type of remote CICS system rejects a request to create a CICS resource because the request contains an invalid attribute value, the Application Deployment Manager handles the error as follows:
CRRZA1424E CRD Reason code: Not valid - create resource attribute string
For each of these error messages, the explanation is that the CICS request contained a particular type of invalid attribute value. The user response is to correct the invalid attribute value and submit the request again.
CICS rejected a request to create a CICS resource because the request does not contain a required keyword.
Specify the required keyword and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request does not contain a keyword that is required by another keyword.
Add the required keyword and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request contains multiple instances of the same keyword.
Resolve the problem and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request contains conflicting keywords.
Resolve the conflicting keywords and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request contains an invalid operand.
Resolve the problem and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request specifies an operand for a keyword that does not have operands.
Delete the incorrect operand and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because a keyword in the request does not contain a required operand. This error can be the result either of incomplete attributes specified in the Application Deployment Manager manifest editor or of incorrect CICS resource defaults defined on the CICS Resource Definition (CRD) server.
See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request contains keywords having conflicting operands.
Resolve the conflicting operands and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request contains a keyword having an operand whose value is too small.
Correct the problem and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request contains a keyword having a pair of operands in which the value of the second operand is greater than the value of the first.
Correct the operands and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the request contains a keyword having a string operand that matches the resource name.
Specify a different string value for the operand and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
CICS rejected a request to create a CICS resource because the DESCRIPTION keyword does not have a closing parenthesis.
Add a closing parenthesis and send the request again. See Explanations and user messages for CRRZA1200E - CRRZA1211E.
Requests processed by the CICS Resource Definition (CRD) server return one of the following return codes. For the Warning and Error return codes an accompanying reason code is also provided.
The communication area passed to the CICS Resource Deployment (CRD) server from the CRD client was too short to contain the response.
Contact Customer Support.
More array items existed than could be returned.
Contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE WEBSERVICE START command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE WEBSERVICE topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE WEBSERVICE NEXT command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE WEBSERVICE topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE WEBSERVICE END command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE WEBSERVICE topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE PIPELINE START command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE PIPELINE topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE PIPELINE NEXT command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE PIPELINE topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE PIPELINE END command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE PIPELINE topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE URIMAP START command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE URIMAP topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE URIMAP NEXT command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE URIMAP topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE URIMAP END command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE URIMAP topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE CONNECTION START command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE CONNECTION topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE CONNECTION NEXT command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE CONNECTION topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
The CICS Resource Definition server received an error from CICS while processing an INQUIRE CONNECTION END command. For more information about the error, see the CICS logs. For more information about the command, see the INQUIRE CONNECTION topic in the information center for CICS Transaction Server for z/OS, Version 4.1.
Try the operation again. If the condition persists, contact Customer Support.
Before resource creation and installation an existing resource with the same name was found.
Decide whether to replace the current definition, skip the current definition, try again, skip all definitions for this system, skip all definitions for this category, or stop the entire operation.
An Uninstall request failed.
Use the accompanying CICS response codes, or the CPSM return, reason, and error codes to determine the cause.
A request to retrieve a CICS resource definition failed because the resource was not found.
Check that the correct resource name and resource type were specified.
An invalid request type was received by the CRD server from the CRD client. This should not occur.
Contact Customer Support.
An attempt to read the CRD repository failed.
Use the accompanying CICS response codes to determine the cause.
An attempt to write to the CRD repository failed.
Use the accompanying CICS response codes to determine the cause.
An attempt to rewrite to the CRD repository failed.
Use the accompanying CICS response codes to determine the cause.
An invalid artifact type was received by the CRD server from the CRD client. This should not occur.
Contact Customer Support.
A Create resource command was issued with an invalid log parameter. This should not occur.
Contact Customer Support.
A Create resource command was issued in a program defined with an EXECUTIONSET value of DPLSUBSET. This should not occur.
Contact Customer Support.
A Create resource command was issued that contained a syntax error in the ATTRIBUTES string. The attributes that caused the error are flagged on the result display window.
Use the CICS RESP2 code to determine the specific cause for the flagged attribute.
An INQUIRE DB2TRAN command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
An INQUIRE DOCTEMPLATE command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
An INQUIRE FILE command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
An INQUIRE PROCESSTYPE command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
An INQUIRE PROGRAM command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
An INQUIRE TDQUEUE command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
An INQUIRE TRANSACTION command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
A CPSM Connect command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A CPSM Get Object command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A CPSM Create command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A CPSM Perform Object with Install action command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A CPSM Delete command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A CPSM Perform Object with AddtoGroup action command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A CPSM Perform Object with Remove action command failed.
Use the CPSM return, reason, and error codes to determine the cause.
An Assign command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
The check for CICS resource security is no longer performed. This should not occur.
Contact Customer Support.
An attempt was made to define a CICS transaction with the program attribute equal to the CRD server program name. This is not allowed.
Change the name of the program.
An INQUIRE TCPIPSERVICE command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
A CPSM Fetch command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A CPSM Feedback command failed.
Use the CPSM return, reason, and error codes to determine the cause.
A Discard command failed.
Use the CICS RESP and RESP2 codes to determine the cause of the failure.
A CPSM Connect command failed because the user ID did not have authorization to issue the command.
Check with the security administrator.
CICSPlex SM is installed but the CICSPlex SM name is not in the CRD repository.
The CICS system programmer should use Application Deployment Manager to provide the CICSPlex name to the CRD repository.
CICSPlex System Manager is installed, but the Applid field contains a value that is not a valid CICSPlex System Manager CICS system name because it cannot be found in the CICSPlex System Manager topology data space.
Correct the name in the Applid field.
A request to run the NEWCOPY command on a program or map set was performed, but the new load module size is the same as the old load module size.
Check that the updated program source was compiled and linked to the correct load library. The load module size may be the same and is common when only modifying a single instruction.
Certain requests require function not supported in all levels of CICS.
No action is required.
The CRD server has abnormally ended.
Contact Customer Support and refer to the handle abend code returned with the message.
A Program Link command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.
An Inquire resource Start Browse command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.
Use the accompanying CICS response code to determine the cause. An Inquire resource Next command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.
An Inquire resource End Browse command failed.
Try the operation again. If the condition persists, contact Customer Support.
An attempt to read the manifest repository failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. Use the accompanying CICS response codes to determine the cause.
An attempt to write to the manifest repository failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. Use the accompanying CICS response codes to determine the cause.
An attempt to rewrite to the manifest repository failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. Use the accompanying CICS response codes to determine the cause.
An Inquire resource Start Browse command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.
An Inquire File Next command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.
An Inquire File Prev command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.
An Inquire File End Browse command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists, contact Customer Support.
A Delete File command failed.
Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists, contact Customer Support.
A retrieve request was issued for a manifest, but the manifest was checked out by a developer.
Request that the developer export the checked out manifest back to the repository and try the operation again.
A retrieve request was issued for a manifest, but the manifest was checked out by a system programmer.
Request that the system programmer complete processing on the checked out manifest to check it back in to the repository, and try the operation again.
A retrieve request was issued for a manifest, but the manifest was checked out by another system programmer.
Request that the system programmer complete processing on the checked out manifest to check it back in to the repository, and try the operation again.
The following messages indicate whether CICSPlex System Manager (CPSM) or CICS Configuration Manager (CCM) or both are installed.
CICSPlex System Manager is not installed.
Install CICSPlex System Manager if you want it installed. Otherwise no action is required.
CICSPlex System Manager is installed.
No action is required.
CICS Configuration Manager is not installed.
No action is required.
CICS Configuration Manager is installed.
No action is required.
The following messages indicate whether the CICS system programmer has authorized a CICS resource type to be installed:
You are not authorized to access the requested CICS resource.
Try a different resource, or check with your CICS administrator.
You are authorized to access the specified CICS resource.
No action is required.
The messages in this section are issued by the Resource Definition Editor.
The named resource was already installed in the CICS region and will not be reinstalled. However, a PHASEIN (NEWCOPY) command will be issued to refresh the load module. The refresh is to occur whether the module is in use. If it is, the copy or copies in use remain until they are no longer in use, but all requests that occur after the refresh use the new copy. This message can be issued for a program or map set. They are the only resources that Application Deployment Manager installs that can also be phased in.
Check for possible mismatch between the resource definition in the manifest and the installed resource definition.
The named resource was not found to be installed in the CICS region. It is issued when checking for naming conflicts. This message can be issued for a DB2TRAN, DOCTEMPLATE, FILE, MAPSET, PROCESSTYPE, PROGRAM, TDQUEUE, or TRANSACTION resource type.
No action is required.
The named resource could not be found in the CICS region. Therefore the action cannot be performed. For a PHASEIN action this message can be issued for a program or map set. For a scan action this message can be issued for a Pipeline or Service Flow Repository file.
Check that the correct resource name was specified in the manifest.
The named resource was successfully installed in the CICS region. This message can be issued for a DB2TRAN, DOCTEMPLATE, FILE, PROCESSTYPE, TDQUEUE, or TRANSACTION resource type. Message CRRZA1608I is issued for a program or map set, because they can be phased in.
No action is required.
The errors were encountered trying to install the named resource in the CICS region. This message can be issued for a DB2TRAN, DOCTEMPLATE, FILE, MAPSET, PROCESSTYPE, PROGRAM, TDQUEUE, or TRANSACTION resource type.
Double-clicking this message in the problem area opens the Resource Definition Editor for the named resource where offending resource attributes are flagged.
The specified action was successfully performed for the named resource in the CICS region. For a PHASEIN action this message can be issued for a program or map set. For a scan action this message can be issued for a Pipeline or Service Flow Repository file.
No action is required.
The errors were encountered attempting to perform the specified action on the named resource in the CICS region. For a PHASEIN action this message can be issued for a program or map set. For a scan action this message can be issued for a Pipeline or Service Flow Repository file.
Check any associated messages to determine the problem.
The named resource was already installed in the CICS region and will not be reinstalled. This message can be issued for a DB2TRAN, DOCTEMPLATE, FILE, PROCESSTYPE, TDQUEUE, or TRANSACTION resource type. Message CRRZA1600W is issued for a program or map set, because they can be phased in.
Check possible mismatch between the resource definition in the manifest and the installed resource definition.
The named resource was successfully installed in the CICS region. This message can be issued for a map set or program.
No action is required.
The named manifest was successfully exported to the CICS region.
No action is required.
A request to phase-in a program or map set completed successfully. However, the load module size did not change.
A phase-in is normally issued after compiling a program or assembling a map set. Verify that the link edit step placed the load module in the correct load library. The size might not have changed if a single instruction was modified.
An attempt was made to export a manifest of CICS resource definitions to the manifest repository on zOS. The export failed for the specified reason.
If the manifest in the repository is marked as processed, then close and reopen the manifest file on the workstation. This retrieves the processed manifest from the repository. Then apply any necessary updates before exporting. If the manifest in the repository is marked as checked out, have the person identified by the user ID complete their update, then close and reopen the manifest file on the workstation. This retrieves the updated manifest from the repository. Then apply any necessary updates before exporting.
The named resource was successfully discarded from the CICS region.
No action is required.
An attempt was made to discard a resource. However, the resource did not exist in the specified region. Either the resource was previously discarded, or the resource was not installed. Resources installed using the CICS Create command are not reinstalled on a CICS cold start.
No action is required.
An attempt was made to discard a resource. However, the resource type was not DB2TRAN, DOCTEMPLATE, FILE, MAPSET, PROCESSTYPE, PROGRAM, TDQUEUE, or TRANSACTION.
Insure the resource is valid for discard.
An attempt was made to discard a resource. However, an error occurred.
Check the error log to determine the specific error.
The {2} action issued for a resource type of {0} encountered errors on region {1}.
For most actions, ensure that the necessary resources exist on region {1} in order to perform the an action type of {2} for a CICS {0} resource. You may find additional information about this error in the CICS log allocated to DD name MSGUSR in the CICS job or started task.
The CICS Resource Definition server does not implement all of the services or resource types that are available in the views provided by CICS. The {0} service is not available for resource type {1} while using a connection to the CICS Resource Definition server.
Use the Host Connections view to create a different type of connection. Click Window > Manage Connections to open the view.
A NEWCOPY action was requested for program {0} on region {1}, using a CICS Resource Definition connection. The CICS Resource Definition server does not implement the NEWCOPY action and has instead issued a PHASEIN.
In most cases no user action is required. If you need to perform a NEWCOPY, use the Host Connections view to create a different type of connection. Click Window > Manage Connections to open the view.
A NEWCOPY action was requested for program {0} on region {1}, using a CICS Resource Definition connection. The CICS Resource Definition server does not implement the NEWCOPY action and has instead issued a PHASEIN. The PHASEIN operation encountered errors. The most common reason for a PHASEIN error is that the program does not exist in the CICS DFHRPL concatenation.
Verify that your program exists in the DFHRPL concatenation of the CICS server. You may find additional information about this error in the CICS log allocated to DD name MSGUSR in the CICS job or started task.
An error was encountered while performing the specified action.
Verify that the data set or folder that is being accessed exists on the file system.
An error was encountered while performing the specified action.
Verify that the data-set member or file that is being accessed exists on the file system.
An error was encountered while performing the specified action.
Follow the action in the message prompt. Either use a new member name or file name, overwrite the existing one, or skip the current one as instructed in the message prompt.
An error was encountered while performing the specified action.
Verify that the file system is not full, that the data set or folder exists, and that you have permission to create members or files.
An error was encountered while performing the specified action.
Verify that the data set or folder exists and that you have permission to read members or files.
A new manifest file was created.
No action is required.
Due to the error displayed in the message the file could not be saved.
Retry the action or check the error log for more details.
The manifest editor could not be opened correctly, likely due to invalid file contents.
Retry the action or check the error log for more details.
The manifest file could not be created.
Retry the action or check the error log for more details.
The following messages pertain to the BMS Screen Designer (BMS Map Editor) in Rational Developer for System z.
This message is typically displayed when some type of validation is in progress, and further explanation is provided.
Follow the instructions or look up the message that is provided in the message window as further explanation.
The field name is the same as another field name in the map.
Change the field name to a unique field name.
The length of a field name cannot exceed 30 characters.
Specify a field name whose length is 30 or fewer characters.
A field name cannot contain the @ character.
Specify a field name that does not contain the @ character.
A field name cannot contain spaces.
Specify a field name that does not contain spaces.
The field name must start with an alphabetic character.
Choose a field name that starts with an alphabetic character.
The length of the initial value cannot exceed the field length.
Specify an initial value whose length does not exceed the field length.
A row cannot be empty.
Specify content for the row.
A column cannot be empty.
Specify content for the column.
The value that is used for the row is not allowed.
Change the value to an allowed entry.
The value that is used for the column is not allowed.
Change the value to an allowed entry.
The value that is used for the row or column is not allowed.
Change the value to an allowed entry.
The value that is used for the field position or length is not allowed.
Change the value to an allowed entry.
A group name cannot exceed 30 characters.
Specify a group name whose length is 30 or fewer characters.
You cannot specify an OCCURS value if a group name is specified.
Specify either an OCCURS value or a group name.
The characters in field names must conform to the character set that is supported by the programming language of the application that uses the map.
Refer to the appropriate Language Reference manual for information about supported characters.
A name cannot contain spaces.
Specify a name that does not contain spaces.
The map name must be unique.
Specify a unique map name.
The length of a map name cannot exceed 30 characters.
Specify a map name whose length is 30 or fewer characters.
A map name cannot contain the @ character.
Specify a map name that does not contain the @ character.
A row must be a numeric value.
Specify a row that is a numeric value.
A column must be a numeric value.
Specify a numeric value for the column.
At least one column must be defined.
Define a column.
The sum of the width of the columns in the table is greater than the table width.
Do one of the following steps:
You must select at least one map.
Select one or more maps.
A nested text editor is a text editor that is part of a multi-page editor in Rational Developer for System z. For the BMS editor, the Source page is the nested text editor. In this case, there was a problem when the Source page was created.
Try closing the BMS file and opening it again.
The BMS editor is expecting a different type of input.
Contact IBM Software Support.
The map set does not contain any maps.
Using the palette that is associated with the editor, select the map, and then select the design canvas to create a map.
A map in the map set does not contain any fields.
Using the palette that is associated with the editor, select a field, and then select the design canvas to create a field.
A map set name that contains one or more invalid characters was specified.
Specify a map set name that contains any of the following characters: letters; digits; the symbols #, $, and @
A name must be specified for the map set.
Specify a name for the map set.
The file name must end in the particular file name extension.
Specify a file name that ends in the required file name extension.
A valid location must be selected.
Select a valid location.
You must enter a valid field name.
Enter a valid field name.
You must specify a valid input field length.
Specify a valid input field length.
You must specify a valid label field length.
Specify a valid label field length.
The length of the fields cannot be greater than the limit that is shown in the message.
Specify a length that is not greater than the limit.
The length of the caption exceeds the available space in the caption.
No action is required. To display the entire caption, increase the length of the Caption field, or decrease the length of the caption text.
The length of the initial value exceeds the available space.
No action is required. To display the entire initial value, decrease the length of the initial value or increase the size of the field that is associated with the initial value.
You must create a dynamic web project first.
Create a dynamic web project.
Save the file to prevent losing any changes.
You must select at least one map.
Select one or more maps.
The number of rows cannot exceed the maximum that is shown in the message.
Specify a number of rows that does not exceed the maximum.
The defined number of rows must be an integer.
Define the number of rows to be an integer.
The prefix that is defined for the column that is shown in the message is not valid.
Specify a valid field prefix.
The content of the table is too wide for the table.
Make the table wider or the contents narrower.
An OCCURS clause entry has an invalid value.
Determine the position of the invalid value and enter a numerical value 1 - 99.
The field length must be numeric and 1 - 99.
Specify a numeric field length in the range 1 - 99.
The field distance must be 1 - 99.
Specify a field distance in the range 1 - 99.
The structure is too large.
Make the structure smaller.
The values that are entered for the field positions overlap.
Enter values that do not overlap.
The value that is entered for the BMS file is already in use.
Specify a unique file name.
A symbolic map was generated and added to the specified MVS subproject.
No action is required.
The symbolic map was created successfully in the destination location you specified.
No action is required.
The symbolic map was created successfully in the destination location you specified.
No action is required.
The specified file name is not valid.
Specify a valid file name.
The specified file name is already used.
Specify a unique file name.
Input other than numeric characters was provided to a numeric field.
Remove any non-numeric characters in the numeric field.
The alternative map name starts with an invalid character.
Remove the invalid character and ensure that the alternative map name begins with a character from the set [a-Z].
The name that is provided as the alternative map name is not valid.
Provide a valid alternative map name.
The alternative map name cannot contain spaces.
Remove all spaces from the alternative map name.
A newly generated BMS file was added to the MVS subproject by the new BMS map set wizard.
No action is required.
These are the messages that pertain to the Common Access Repository Manager (CARMA) in Rational Developer for System z.
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.
Disconnect from the CARMA server, check the host code page setting for the CARMA connection, reconnect, and try the action again.
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.
Verify that all host PTFs are properly installed and configured.
Contact your system programmer.
A CARMA function was called before CAMA was initialized.
Disconnect from CARMA, reconnect, and try the action again.
The CARMA server received a request to cancel the command.
No action required.
The CARMA server was unable to allocate memory.
In the client, disconnect, reconnect, and try again. If it persists, increase the amount of memory available in the address space.
The CARMA server was unexpectedly unable to write to the socket.
No action is required. CARMA automatically attempts to reconnect. If this problem persists, have your system programmer check your TCP/IP settings.
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.
Restart the workbench and connect to CARMA before you attempt any CARMA actions.
The value that is specified for the trace level is invalid.
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.
The value that is specified for the local was invalid.
In the client, disconnect from CARMA, open the CARMA preferences, and specify a valid local parameter. Reconnect and try your action again.
An expected parameter was not provided to the CARMA server from the client.
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.
CRASERV did not receive contents from the CARMA server for the putMember action.
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.
An unexpected, internal error occurred.
Disconnect from CARMA, reconnect, and try your action again. If the problem persists, contact support.
The CARMA server did not receive the expected instance ID or filter.
Disconnect from CARMA, reconnect, and try the action again.
The CARMA server did not receive the expected instance ID or member ID.
Disconnect from CARMA, reconnect, and try the action again.
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.
Disconnect from CARMA, reconnect, and try your upload again. If the problem persists, contact support.
The CARMA server expected more records than the number provided for the putMember action
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.
A line is the member is longer than the maximum line length (lrecl).
Ensure that all lines are within length limits and try the upload again.
The CARMA server did not receive the expected instance ID, member ID, metadata key name, or metadata value.
Disconnect from CARMA, reconnect, and try the action again.
The CARMA server timed out while it was waiting for a command.
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.
The expected parameter for the putMember function was not provided to the CARMA server from the client.
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.
The CARMA server was unable to retrieve the custom action framework parameter list for the RAMtext.
Disconnect from CARMA, reconnect, and try again. If the problem persists, confirm that the CRADEF VSAM file is properly setup.
An action was called that required a custom action framework parameter that was not provided.
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.
An invalid type was specified for a parameter or return value in the CRADEF configuration VSAM.
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.
The CARMA server encountered an error while reading the custom return values from the RAM.
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.
An unknown error occurred in the CARMA server.
Disconnect from CARMA, reconnect, and try again.
The CARMA Miner received a command that requires a RAM ID but one was not supplied by the client.
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.
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}.
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.
CARMA expected a protocol version of 2 or greater, but received {0}.
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.
CARMA expected an integer return code, but instead received {0}
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.
The response header from the CARMA Server contains an unexpected character.
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.
The server response ended unexpectedly. An unexpected end of server response can occur when the socket disconnects prematurely.
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.
The CARMA Miner does not have the initialization information that is needed to restart a connection to the RAM.
Disconnect from the CARMA host at the Remote Systems view, reconnect, and then try your action again.
The local and code page information was not sent to the host, so the default code page was used.
This situation is most likely caused by an outdated client. No response is required. To remove this message, update the client.
The code page conversion information that is used to download a file from CARMA is incorrectly formatted.
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.
CARMA expected an object of type {0}, but instead had an object of type {1}
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.
The CARMA Miner received the incorrect number of attributes from the CARMA server. This situation can be caused by a socket communication error.
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.
A list was returned from the RAM that included duplicates of the same ID.
The RAM developer must update the RAM to ensure that duplicate elements are not returned with the same ID.
The CARMA Miner received an empty response body from the CARMA server, possibly caused by a socket communication error.
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.
The CARMA Miner was not able to parse a response from the CARMA Server because of an internal error.
Disconnect from the CARMA host at the Remote Systems view, reconnect, and try the command again. If the problem persists, contact technical support.
The CARMA Miner was unable to read a metadata key.
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.
The CARMA Miner was unable to read a metadata value.
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.
The CARMA Miner received an invalid response from the CARMA server, possibly caused by a socket communication error.
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.
The CARMA Miner received an invalid response from the CARMA server, possibly caused by a socket communication error.
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.
The CARMA Miner received an invalid response from the CARMA server, possibly caused by a socket communication error.
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.
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.
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.
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.
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.
Two items in the CARMA VSAM configuration files have the same id, {0}.
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 Rational Developer for System z Common Access Repository Manager (CARMA) Developer's Guide.
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.
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.
A custom parameter or return value has an invalid type. Valid types are "STRING", "DOUBLE", "LONG", and "INT".
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 Rational Developer for System z Common Access Repository Manager (CARMA) Developer's Guide.
A custom parameter has a default value of {1}, which is not a valid example of the type specified.
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 Rational Developer for System z Common Access Repository Manager (CARMA) Developer's Guide.
A custom parameter has a non-integer value for length in the CARMA configuration VSAM file.
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 Rational Developer for System z Common Access Repository Manager (CARMA) Developer's Guide.
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.
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 Rational Developer for System z Common Access Repository Manager (CARMA) Developer's Guide.
The CARMA miner attempted to run the same command twice.
Disconnect from RSE, reconnect, and try your CARMA command again.
The CARMA object (member, container, repository instance) was not found on the host.
Refresh the parent container, and try the action again.
The CARMA client did not provide the required parameters to the CARMA miner.
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.
CARMA was not initialized before a CARMA command was issued.
Check the CARMA startup configuration on the host.
Disconnect from the CARMA connection, reconnect, and try the action again.
The CARMA miner was unable to start the CARMA server.
Have your system programmer check the CARMA startup configuration. More information about configuring CARMA can be found in the Rational Developer for System z Host Configuration Guide.
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.
Disconnect from the CARMA host, reconnect, and try your command again.
More parameters than expected were passed to the carma.startup.rex script.
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.
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.
Confirm that the correct CLIST is defined in CRASRV.properties and that the user has permission to access it.
CARMA miner encountered a command that was unsupported.
Verify that the host and client versions of the product are the same.
Disconnect from CARMA, reconnect, and try the action again.
The carma.startup.rex script did not receive a port parameter, most likely caused by a modified or out of date carma.startup.rex.
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
The CARMA Rexx script was not found. Possibly caused by the location not being an absolute location.
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.
The carma.startup.rex script did not receive a CLIST parameter, most likely caused by a modified or out of date carma.startup.rex.
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.
The CARMA startup script encountered an unknown error while it was trying to start the CARMA Server.
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.
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.
Disconnect from CARMA, reconnect, and try the action again.
The local or remote code page that is set for the target CARMA member is not supported by the Host system.
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.
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.
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.
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.
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.
The CARMA Miner did not receive the location to download the member to, most likely caused by an out of date client or host.
Make sure that your client and host are both at the same level. A difference greater than two levels apart is not supported
The RAM reported a different LRECL value for the CARMA member while in the process of downloading the member.
Have your RAM developer correct this error in the extractMember function.
While the CARMA miner was chunking a file download, it received a different LRECL (logical record length) value than the download started with.
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.
While the CARMA miner was trying to upload a member from the client to the host, it encountered an invalid state.
Disconnect from the CARMA host, reconnect, and try the upload again. If the problem persists, have your systems programmer restart Developer for System z on the host.
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.
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.
An unexpected error occurred while the file was uploading to CARMA.
Check the rsecomm.log file for more information about what caused the error. Disconnect from the CARMA host, reconnect, and try your upload again.
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.
Refresh the parent container and try again.
The file was not transferred in the proper format.
Verify that the transfer format is specified correctly and try again.
The CARMA and RAM connections are no longer synchronized.
You need to disconnect and reconnect your CARMA and RAM connection.
The CARMA and RAM connections are no longer synchronized.
You need to disconnect and reconnect your CARMA and RAM connection.
The specified character encoding is not supported when creating the new CARMA member.
Change the character encoding of the source member and try again.
In the RAM configuration, "Connect to RAM" has been disabled.
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 Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
In the RAM configuration, "Get Instances" has been disabled.
Enable "Get Instances" in the RAM configuration. For additional information on enabling "Get Instances", see "Customizing a RAM API using the CAF" in the Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
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.
Restart the workbench with the -clean flag.
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.
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.
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.
Restart the workbench with the -clean flag.
Your CARMA connection is no longer working.
Disconnect from CARMA, reconnect, and try again.
Your CARMA connection is no longer working.
Disconnect from CARMA, reconnect, and try again.
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.
Restart the workbench with the -clean flag.
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.
Restart the workbench with the -clean flag.
Your CARMA connection is no longer working.
Disconnect from CARMA, reconnect, and try again.
If a transport layer has an invalid priority, then the transport layer will not be loaded.
If the process works, then ignore the message. Otherwise, restart the workbench and try again.
CARMA is no longer associated with the RSE connection.
Delete the CARMA connection and Create a new CARMA connection.
The TransportServiceFactory, which contains all loaded transport layers, was not loaded.
If the process works, then ignore the message. Otherwise, restart the workbench and try again.
The CARMA compare configuration file, syncConfig.xml cannot be found.
None needed, CARMA will check the bytes of the compare files.
The CARMA compare configuration file, syncConfig.xml cannot be found.
None needed, CARMA will check the bytes of the compare files.
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.
If CARMA connections appear broken, recreate them and try again. Otherwise, restart your workbench and try again.
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.
If CARMA connections appear broken, recreate them and try again. Otherwise, restart your workbench and try again.
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.
Retry opening the file. If reopening the file does not work, restart the workbench.
CARMA stores temporary downloaded files to a hidden CARMA download project. In this case, there was a problem creating or opening this project.
Restart the workbench and try again. If this doesn't work, create a new workspace and try again.
There was an error retrieving the file, and more information should be provided in an accompanying error message.
Check error log for accompanying messages.
CARMA has returned an invalid record length when trying to open a member.
If the problem persists, have the RAM developer confirm an integer is returned for the LRecl or open the file in binary transfer mode.
CARMA encountered an error when making a temporary element for communication with the host.
Refresh the parent of the current item, and try again.
There was an error uploading a file to CARMA.
Disconnect from CARMA, reconnect, and try again.
While CARMA was waiting for a response from the host, it timed out.
Disconnect from RSE, reconnect, and try again. If the problem persists, it could be a configuration problem on the host.
There was an error uploading the file.
Refresh the parent of the current item, and try again.
There was an error uploading the file, and an additional message with more information will be provided.
Follow the steps in the additional message. If still unsuccessful, then disconnect from CARMA, reconnect, and try again.
There was an unexpected error during file upload. Please report this error to technical support.
Please report this error to technical support.
The file could not be uploaded as the specified line number is longer than the line record length.
Modify the given line of the file so that the length is shorter than the given record size.
There was an error uploading the file, and an additional message with more information will be provided.
Follow the steps in the additional message. If still unsuccessful, then disconnect from CARMA, reconnect, and try again.
CARMA finished sending the file to the host but was interrupted before it could get final confirmation.
Confirm the contents of the file on the host, or perform the upload again.
There was an error uploading the text file.
Disconnect from CARMA, reconnect and try again.
The logical record length (LRecl) is not properly defined in the RAM.
Contact the RAM developer to modify the RAM to return the LRecl in the proper format. For additional information on RAMs, see the Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
There was an error uploading the binary file.
Disconnect from CARMA, reconnect and try again.
The value for the logical record length (LRecl) is not valid.
Contact the RAM developer to modify the RAM to return the LRecl in the proper format. For additional information on RAMs, see the Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
A time out occurred while waiting for an update from the host.
Disconnect from RSE, reconnect, and try again. If the problem persists, have your system's administrator check your host configuration and tune Rational Developer for System z for the number of users connecting concurrently.
This message provides the diagnostic information for message CRRZC2070E.
This message provides the diagnostic information for message CRRZZC2070E.
This message provides the diagnostic information for message CRRZZC2070E.
This message provides the diagnostic information for message CRRZZC2070E.
A timeout occurred and an exception was caught while running diagnostics.
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 Rational Developer for System z for the number of users connecting concurrently.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
CARMA requested member information for a given key, which was not found for this CARMA resource.
No user response is required. The particular piece of information is not set or valid on the CARMA resource.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
An error occurred that prevented the temporary element from being created properly.
Disconnect you CARMA connection, reconnect, and try again.
The CARMA connection could not be synchronized with the underlying host transport layer.
Remove the CARMA connection, recreate the connection, and try again.
The CARMA command could not be located on the host.
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.
A third-party plug-in tried to set the contents of a CARMA member using internal API's.
Make use of the method CARMAMember.setMemberContents() when setting the contents of a CARMA member in a third-party CARMA plug-in.
The host side temporary cache of the resource is missing.
Try the following:
A record in the member is too long. The member has not been saved on the host.
Modify the length of the line and save again.
CARMA is unable to connect to the Host. This can occur when CARMA is not properly configured.
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 Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
Could not create a temporary object to communicate with the host for the given resource.
Refresh the resources parent, and try again.
A third-party plugin tried to set or get the contents of a CARMA member using internal API's.
Use the CARMAMember.setMemberContents() and CARMAMember.getMemberContents() methods to set and get CARMA member contents respectively.
CARMA is unable to connect to the Host. This can occur when CARMA is not properly configured.
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 Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
CARMA is unable to connect to the Host. This can occur when CARMA is not properly configured.
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 Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
There was an error trying to terminate the CARMA job during disconnect.
No user action is necessary.
CARMA is unable to disconnect from the Host. This can occur when CARMA is not properly configured.
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 Rational Developer for System z Common Access Repository Manger (CARMA) Developers Guide (SC23-7660).
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.
Follow the user response instruction for the second part of the message to resolve the problem.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
The host returned an invalid type of object for CARMA.
Disconnect from the remote system explorer, reconnect, and try again.
There was an error retrieving the file, and more information should be provided in an accompanying error messages.
Check the error log for additional messages.
There was an error uploading the file to the host.
Follow the user response in the additional message provided.
The error message provides more information about the problem.
CARMA has been configured with the initialization function disabled and cannot start.
Have the system programmer or RAM developer modify the CRADEF configuration VSAM on the host to not disable action ID 80.
CARMA has been configured with the custom action framework function disabled.
Have the system programmer modify the CRADEF configuration VSAM on the host not to disable action ID 83.
The RAM has been configured with the RAM initialization function disabled and cannot start.
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.
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.
Set the transfer type to text. Alternatively, if you need the file in binary, have your system programmer update the host installation.
The required CARMA jar file is not found in the class path in the Server. The Rational Developer for System z server was not properly installed and configured.
Contact your system programmer and report the the problem. For information on installation and configuration, see the Rational Developer for System z Host Configuration Guide (SC23-7658).
When connecting to CARMA, there was an error getting the custom action descriptions.
Disconnect from RSE, reconnect, and try again. Additionally, if there is an additional message included, follow the user response for that particular error message.
CARMA could not find the stated metadata key when refreshing the metadata information.
No action needs to be taken as this is an informational warning.
CARMA could not find the stated metadata key when refreshing the metadata information.
No action needs to be taken as this is an informational error message.
CARMA is no longer associated with the RSE connection.
Delete the existing CARMA connection and Create a new CARMA connection.
CARMA is no longer associated with the RSE connection.
Delete the existing CARMA connection and Create a new CARMA connection.
The CARMA connection is no longer associated with an RSE connection. The RSE connection could have been deleted or renamed.
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.
The local Cache does not match what is on the host.
Disconnect, reconnect, and refresh CARMA.
The local Cache does not match what is on the host.
Disconnect, reconnect, and refresh the repository manager.
The default value set in the configuration VSAM is not of the proper type.
The RAM developer should modify the configuration VSAMs to have a default value of the proper type for the parameterID listed in the message.
The default value set in the configuration VSAM is not of the proper type.
The RAM developer should modify the configuration VSAMs to have a default value of the proper type for the parameterID listed in the message.
The default value set in the configuration VSAM is the wrong type.
The RAM developer should modify the configuration VSAMs to have a default value of the proper type for the parameterID listed in the message.
A custom parameter, custom return value, or CARMA field is being reported as having an unsupported type.
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.
CARMA or the RAM did not provide a valid for LRecl or recFM when the create member call was made.
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.
CARMA or the RAM did not provide a valid name or memberID when the create member call was made.
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.
The length set for the parameter in the VSAM configuration is not a valid number.
The RAM developer should modify the configuration VSAMs to have the parameter of the proper length for the parameterID listed in the message.
Could not parse the CARMA
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.
CARMA has been configured not load the repository manager.
Have the system programmer or RAM developer modify the CRADEF configuration VSAM on the host not to disable action ID 82.
The terminate RAM action is disabled, so CARMA returned with an error when trying to disconnect from the RAM.
Have the system programmer or RAM developer modify the CRADEF configuration VSAM on the host not to disable action ID 01.
An error occurred when disconnecting the RAM.
If there is an associated exception, follow the user response in that. Otherwise, no action is required.
Informational log message that provides the location in the local file system to which a file is downloaded.
Informational message that provides the trace level of the connection. This message is expected to be logged at every CARMA connection.
Unexpected error trying to perform a compare with action. The CARMA member might not exist.
Refresh the parent of the CARMA member in the CARMA view, and try again.
Unexpected error trying to perform a compare with. The CARMA member might not exist.
Refresh the parent of the CARMA member in the CARMA view, and try again.
A subproject can only be associated with one repository instance. This error message shouldn't appear in versions 8.0.1 or later.
Remove the association of the subproject from CARMA before trying to associate it with a new repository instance.
The local cache for CARMA is out of sync with the local host, which has caused an error during extract.
Refresh the parent in the CARMA view, and try again.
CARMA unexpectedly lost connection to the host during an extract.
Check your network connection, reconnect to CARMA, and try again.
CARMA unexpectedly lost connection to the host during an extract.
Check your network connection, reconnect to CARMA, and try again.
During an extract from CARMA, the host resource could not be found after the RAM was instructed to create it.
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.
When trying to copy multiple resources into the RAM a subset of the resources did not copy.
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.
The mapping between the resource and the CARMA resource is incorrect.
Reassociate the resource with CARMA.
The local cache for CARMA is out of sync with the local host, which has caused an error.
Refresh the parent in the CARMA view, and try again.
CARMA unexpectedly lost connection to the host during extract.
Check your network connection, reconnect to CARMA, and try again.
Error adding the host resource to the z/OS sub project.
Disconnect from RSE and reconnect, then try extracting again.
There was an error receiving project properties for one or more of the members.
Check for associated error messages and follow their user response.
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.
Refresh the parent of the CARMA object, and extract it again to the same location.
The mapping between the resource and the CARMA resource is incorrect.
Reassociate the resource with CARMA.
CARMA unexpectedly lost connection to the host while retrieving project properties.
Check your network connection, reconnect to CARMA, and try again.
The sequential data set or PDS member that is selected for extract into a z/OS project or upload into CARMA was not found.
Verify that the remote member or data set exists, and try the action again.
CARMA encountered one or more errors when trying to associate the z/OS subproject with CARMA.
Check for associated messages and follow their UR. Otherwise disconnect/reconnect RSE and try the extract again.
Information message that states that the CARMA views that were selected for export were successfully exported.
The views were exported from a CARMA RAM that represented views differently that the RAM into which you are importing the view.
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.
The file that was selected for import is not correctly formatted as a CARMA view file.
Try the import again with a file of the correct format.
Informational message that the CARMA views that were selected for import were successfully imported.
CARMA encountered an error while it was saving the view-export file.
Verify that you have the correct access to the save location on the client. Check the client error log for more information.
The following client messages pertain to the Enterprise Service Tools (EST) component in Rational Developer for System z.
The EST messages are grouped into the following subdivisions:
CRRZX0047E-CRRZX0132E: Messages that are displayed by the single-service project tools
1WebSphere Message Broker error messages begin with the characters BIP, as in BIP2001E. For information about these messages, see Diagnostic messages in the WebSphere® Message Broker Version 6.1 Information Center.
The remote system editor encountered an internal error.
See the error log.
The remote system editor displays this error message whenever it cannot connect to the remote z/OS system that is specified in the current remote system connection.
The connection can fail for any network reason. To troubleshoot connection problems:
The Generate Runtime Code wizard was unable to submit the JCL file to the remote z/OS system.
Make sure that you are logged on to the JES connection for the system you are deploying to by using the Remote Systems view. Make sure the data set you are moving your JCL files to is configured to support JCL files.
This error indicates that the specified pipeline was not successfully rescanned.
If the reason indicates that the selected CICS System/Region was not found, ensure the System/Region is defined by using the connection preferences and that you are connected.
If the reason indicates that a CRD error occurred, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about these errors, see Chapter 2. Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.
This error indicates a failure to create a program resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while it was creating this resource.
If the reason indicates that it is a CRD error, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about these errors, see Chapter 2. Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.
This error indicates a failure to create a transaction resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while it was creating this resource.
If the reason indicates that it is a CRD error, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about these errors, see Chapter 2. Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.
This error indicates a failure to create a process type resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while it was creating this resource.
If the error message that is represented by {1} indicates that the error occurred in the CICS Resource Definition (CRD) server, then follow these steps:
This message indicates that the connection to the CICS System/Region selected in the Generate Runtime Code wizard was not found.
Ensure that the System/Region is defined by using the connection preferences and that you are connected.
An error occurred in the CMIT transaction for the CICS Service Flow Runtime because the selected CICS System/Region is not CICS Transaction Server for z/OS V3.2 or later.
The CMIT transaction is installed only in CICS Transaction Server for z/OS V3.2 or later. Select the correct CICS System/Region in the Generate Runtime Code wizard.
This message is displayed if you skip over replacing a pre-existing file or if the Application Deployment Manager subsystem encountered an error while it was creating the file at the specified location.
Ensure that your remote systems are connected. Ensure that your target directories or data sets are entered correctly and that you have write access to those destinations. Check the Application Deployment Manager log for more details. The location of the Application Deployment Manager log is specified in the Preferences page for the Application Deployment Manager.
An error occurred in the CMIT transaction of the CICS Service Flow Runtime because the SFR flow scan program DFHMAINS ended abnormally.
Examine the CICS MSGUSR log and look for a message that indicates that DFHMAINS ended abnormally. The message contains a specific four-character abend code.
An error occurred in the CMIT transaction of the CICS Service Flow Runtime because of a program link failure.
See the RESP and RESP2 values for the LINK command in the CICS Application Programming Reference. For more information about the CICS response 2 codes, see also CICS response 2 (RESP2) codes: CRRZA1200E - CRRZA1211E in the online help for the Application Deployment Manager).
An error occurred in the CMIT transaction of the CICS Service Flow Runtime because the CICS System/Region selected in the Generate Runtime Code wizard could not be found.
Ensure that the System/Region was defined by using the connection preferences and that the connection is open.
This message indicates an internal error.
The reason code that is returned by the Application Development Manager is a CICS Resource Definition server reason code. For more information about the reason code, see CICS Resource definition server reason codes: CRRZA1400E - CRRZA1469E in the online help for the Application Deployment Manager. Contact IBM Software Support to resolve the problem.
The Generate Runtime Code wizard was not able to retrieve the default values for RDO program resources from the CICS Resource Definition server.
The wizard uses these default values to create the program resources for the flow. These default values are set by the system administrator.
Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about the errors, see Chapter 2. Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.
The Generate Runtime Code wizard was not able to retrieve the default values for RDO transactions from the CICS Resource Definition (CRD) server.
The wizard uses these default values to create transaction resources for the flow and also to add a transaction resource to a manifest file. These default values are set by the system administrator.
Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about the errors, see Chapter 2. Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.
The Generate Runtime Code wizard was not able to retrieve the default values for RDO ProcessType resources from the CICS Resource Definition (CRD) server.
The wizard uses these default values to create ProcessType resources for the flow. These default values are set by the system administrator.
Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors. For more information about the errors, see Chapter 2. Client messages for Application Deployment Manager in the online help for the Application Deployment Manager.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
The generation property that is specified by the error message contains an invalid value.
The node type element in the error message can be either of the following node types:
To resolve this problem:
The flow that you are attempting to generate contains more than one Receive node. Only one Receive node is allowed on a flow.
Modify your flow so that it contains only one Receive node.
This message is displayed when an ESQL expression associated with a Switch or While node is missing or has invalid contents.
Correct the problems with the referenced ESQL resource and run the Generate Runtime Code wizard again.
The Generate Runtime Code wizard did not find the specified resources in the specified containing resource as expected.
One of the ESQL expressions in your service flow contains a syntax error.
Open the referenced resource and correct the ESQL expression. The expression that prevented successful generation is also listed as an error in the Problems view.
When you generate a terminal service flow of flow type Link3270 Bridge, only fields that are named in the imported BMS maps can be referenced in the user-created screen descriptors.
A descriptor in the screen description uses a default field name instead of a BMS field name. For more information about field names and descriptors, see Default field name and Handling of String and Field Pattern descriptors when the flow type is Link3270 Bridge. Follow these steps:
The COBOL generator could not create a COBOL data structure from one of the messages that are used by the specified node.
To resolve this problem:
Depending on the flow type of your service flow (Non-Terminal, FEPI, Link3270 Bridge), only certain invoke types are supported. As specified in your Generation Properties, one of the invoke nodes in your service flow is of an invoke type that is not supported by the flow type of your flow. For more information about invoke types and flow types, see About invoke types and About flow types.
Revise or remove from the flow any invoke node that has an invoke type that is not supported by the flow type of the flow.
If the target runtime environment in the generation properties file is CICS Transaction Server for z/OS V3.1 and the flow type of the flow node in the generation properties file is Link3270 Bridge, each screen message that is referenced in the flow must contain BMS information. For more information about this requirement, see When the flow type is Link3270 Bridge -- BMS map information.
When the target runtime environment is CICS Transaction Server for z/OS V3.1 and the flow type is Link3270 Bridge, each screen message must contain BMS map information.
To create a screen message that contains BMS map information, do one of the following steps:
For more information about these steps, see Working with information from BMS maps.
After you do these steps, you must re-record the flow before you generate runtime code.
An internal error occurred during the process to generate the runtime code for your service flow.
This error message can occur if you accidentally delete a message resource that is referenced in your service flow. Resolve any errors or warning messages that are shown in the Problems view.
A length value was not specified for the String element. A default length value of 255 was used.
To set a value for the referenced message element:
In the editor area, select the Properties tab.
In the Outline view, in the Types hierarchy, select the type specification of the element that was specified in the error message:
In the editor area, in the left pane, the flow message editor displays the Properties Hierarchy for this instance of the simple type xsd:string.
In the editor area, in the Properties Hierarchy, select Logical properties > Value Constraints.
In the right pane, in the Length Constraints group, in the Max field, type the maximum value that you want to use.
The maximum length for the element is set to the value that you typed in the Max field.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
This message can be displayed when a referenced file could not be found.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during the process to generate the runtime code for the service flow.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
An ESQL expression can have at most five CAST operations for a particular data type.
Rewrite your ESQL expressions so that they do not have more than the maximum number of CAST operations.
Only a subset of the ESQL Operations is supported by the service flow project tools.
For the list of supported language elements, see ESQL reference. Remove the unsupported language element from the specified resource.
The service flow properties file has a maximum size limit of 32,600 characters. The size of the service flow properties file increases with each invoke node in the flow.
Decrease the number of invoke nodes in your service flow until the size of the service flow properties file falls under its maximum size limit of 32,600 characters.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
Depending on the target runtime environment and whether you specified a flow type of FEPI or Link3270, certain screen descriptors might not be supported.
Verify that the descriptors in the specified screen description are supported in the target runtime environment that you specified when you created the generation properties file. For more information about supported screen descriptors, see Support for screen descriptors in the runtime environments.
For more information about the descriptors, see Handling of Number of Fields, Number of Input Fields, Fields Checksum, and Cursor Position descriptors when the flow type is Link3270 Bridge.
An internal error occurred during the process to generate the runtime code for your service flow.
Resolve any errors or warning messages that are shown in the Problems view.
Screen recognition criteria can be matched against only the first 160 characters of any field.
There is no workaround to this limitation. If this truncation results in a screen not being uniquely identified, add more recognition criteria to the screen description.
The code page of a screen description must be the same as the code page specified in the generation properties file. For more help with this error, see CRRZE7333E.
If the code page in the generation properties file is incorrect:
If the code page in one or more screen descriptions is incorrect, then follow these steps:
All the screen descriptions in a terminal flow must use the same code page, and this code page must also be the same as the code page specified in the generation properties file for the flow. For more help with this error, see CRRZE7332E.
The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files that are needed to invoke the generated service flow as a web service. An error was reported from the batch processor utility.
The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files that are needed to invoke the generated service flow as a web service. An error was reported from the batch processor utility.
The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files that are needed to invoke the generated service flow as a web service. An error was reported from the batch processor utility.
For troubleshooting information for single-service projects, see Batch processor. For more information about the error log, see the topic "Error Log" in the top-level folder Eclipse documentation in the online help.
Because the field and the PROGRAM-ID have the same name, the following compile error occurs. In the program output, the following error message is printed all on one line.
IGYDS1266-E The name xxxxxxxx was used for an
item that was not defined as a data-name.
References to this name may be resolved
incorrectly.
Follow these steps:
A compilation error occurs because the field is named the same as a COBOL reserved word.
Follow these steps:
A compilation error occurs because references to two different data structures have the same name.
Follow these steps:
When you extract data from a screen message that has BMS information that is associated with it, you can extract data only from fields that were named in that BMS map. This situation holds true whether you are extracting from a single field or from a rectangular area.
Open the resource that contains the reference to the non-named field. Remove any references to the non-named field. During the import process, fields that were not named are given default names that are based on the position where they are found. Field30, for example, is the default name that is given to an unnamed field at position 30 of an imported BMS map. For more information about field names, see Default field name and Handling of String and Field Pattern descriptors when the flow type is Link3270 Bridge.
The Generate Runtime Code wizard could not calculate the COMMAREA length automatically for the Invoke nonterminal node that is specified in the error message.
In the generation properties editor, for the flow node that is specified in the error message, in the Maximum COMMAREA Length field, you selected Generate length value, a selection that usually causes the Generate Runtime Code wizard to calculate the maximum length of the COMMAREA automatically. However, in this case the wizard could not calculate that length. Therefore, you must calculate the length manually and type it into the field.
In the generation properties editor:
For more information about the generation properties, see Generation properties of the LINK with COMMAREA invoke type.
For the Invoke nonterminal application node that is specified in the error message, the length of the input messages or the length of the output messages (which are specified in the mappings for this node) is greater than the value specified in the Maximum COMMAREA Length field for this node in the generation properties editor
Because this message is a warning rather than an error, no action is required. However, because this length discrepancy can cause a storage violation at run time, consider making one of the following changes in the Maximum COMMAREA Length field in the generation properties editor:
Set the value to a number greater than the calculated length of the input message and greater than the calculated length of the output message.
Select Generate length value so that the Generate Runtime Code wizard calculates the value automatically.
For more information about generation properties, see Generation properties of the LINK with COMMAREA invoke type.
The reason is that the generated COBOL source code for a web service can include only two interface points with the invoking program:
The source code cannot contain more return points that are associated with Throw nodes.
It is valid for a flow to contain one or more Throw nodes. But currently, when the Generate Runtime Code wizard is creating a web service and encounters a Throw node, the wizard ignores the Throw node and does not create a corresponding return point in the COBOL source code.
Modify the design of the flow so that it does not rely on a Throw node as a return point to the program that invokes the flow.
For more information about this restriction, see Restrictions on execution within flows.
An Invoke outbound web service node in the flow is associated with an interface operation that does not contain an input message, or the Invoke outbound web service node does not have an interface operation that is associated with it.
Open the .wsdl files in the Operations folder of your outbound web service subproject with the operations editor until you find the operation that is missing an input message. Add an input message to that operation, save the operations file, and run the Generate Runtime Code wizard again.
An Invoke outbound web service node in the flow is associated with an operation that does not have an output message or a fault message. An outbound web service operation must contain either an output message or a fault message, or can contain both.
Open the .wsdl files in the Operations folder of your outbound web service subproject with the operations editor until you find the operation that lacks both an output message and a fault message. Add an output message or a fault message to that operation, save the operations file, and run the Generate Runtime Code wizard again.
An unexpected exception occurred during flow playback or during HATS macro generation.
Resolve any errors or warning messages that are shown in the Problems view.
An internal error occurred during flow playback or during HATS macro generation.
Resolve any errors or warning messages that are shown in the Problems view.
Flow playback and HATS macro generation do not support Switch nodes. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.
To resolve this problem:
Flow playback and HATS macro generation do not support Invoke flow nodes. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.
To resolve this problem:
The interface operation for the flow does not contain an input message, or the flow is not associated with an interface operation.
The flow contains an invalid reference to the flow node specified in the error message. Either the reference is null or it refers to a flow node that could not be found in the flow.
The Invoke screen operation node that is specified in the error message is associated with a screen operation that has an invalid reference to an input screen message. Either the reference is null or it refers to an input screen message that could not be found in the flow.
Make sure that the specified node is associated with a valid screen operation.
The Invoke screen operation node that is specified in the error message is associated with a screen operation that has an invalid reference to an output screen message. Either the reference is null or it refers to an output screen message that could not be found in the flow.
The flow node that is specified in the error message contained an instruction to write data into the specified variable, but the variable could not be found in the flow.
The mapping routine that is specified in the error message uses an element of ESQL syntax that is not supported in flow playback or in HATS macro generation. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.
The macro routine that is specified in the error message contained the specified ESQL keyword. Most elements of ESQL are not supported during flow playback or HATS macro generation. For more information about this restriction, see Restrictions on using ESQL.
To resolve this problem:
Some mapping transforms are not supported by flow playback and HATS macro generation. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.
To resolve this problem:
Flow playback and HATS macro generation do not support conditions in mapping transforms. For more information about this limitation, see Limitations on features and capabilities when generating HATS macros or when playing flows.
To resolve this problem:
The Batch Processor could not form a unique name for a converter driver file in the file container that is specified in DriverSpec/@fileContainer because no more unique eight-character file names could be generated from the specified prefix.
Specify a shorter prefix in DriverSpec/@fileNamePrefix to allow larger values of the ordinal that is used to resolve file name collisions.
WSDL2PLI determined that a global XSD element referenced by an operation in the WSDL defines a message that is empty. This message is issued to indicate that a language binding was not provided and to ensure that the empty message definition is intentional.
If the empty message definition is intentional, no action is required, otherwise correct the XML schema and try again.
WSDL2PLI and Compiled XML Conversion do not support the concept of a generic binding. Therefore, when a global XSD element describes the contents of the detail element of a fault message, it cannot be of an empty complex type. The complex type must contain at least one mappable XML element or XML attribute.
Add at least one XML element or XML attribute to the complex type referenced by the global XSD element.
XsdSpecIn and XsdSpecOut specifications in the ServiceSpecification.xml file contained identical values for element specification (xsdElemName="{0}") and identical target namespace values (targetNamespace="{1}").
Check the correlator file to ensure that it is valid and that it was upgraded to the current release.
The following messages pertain to the System z LPEX Editor in Rational Developer for System z.
This error might be caused by a custom extension to the editor or a product defect.
If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support.
The embedded language parser was attempting to display an annotation through the editor, but an error caused the process to stop. A custom extension to the editor might cause such an error.
If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support for assistance.
The error occurs when a declaration is opened in an item where parsing did not occur. The error can occur if annotations and tools are disabled and the F3 key is pressed to open a declaration.
Verify that the tools or annotations are enabled. Try the process again. If the tools and annotations are enabled or the problem persists, contact IBM Software Support.
This error might occur if the F3 key is used to open a declaration when there is a parsing error.
Resolve parsing errors and try the process again. If the problem persists, contact IBM Software Support.
The selected item is not valid.
Select a different item, and try the operation again.
This error occurs if you try to open the perform hierarchy in an item where parsing did not occur.
Enable tools or annotations and tools, and try the operation again. Contact IBM Software Support to report the problem.
An error occurred when opening the perform hierarchy because of a parsing error.
Resolve the parsing errors, and try the action again. Contact IBM Software Support for assistance.
The selected item cannot be used because it cannot be resolved.
Select a different item. If the problem persists, contact IBM Software Support for assistance.
The argument that was passed to the perform graph function is incorrect.
Try the function again with a different selection. If the problem persists, contact IBM Software Support for assistance.
To add listeners to the workbench, they must be registered during startup. Listeners were not registered during startup. This situation can happen if the software is already running in nondisplay mode when the product is started.
If the error occurs during normal use, contact IBM Software Support for assistance.
An unknown error occurred during the availability checking of the Open Declaration action.
Contact IBM Software Support for assistance.
An error occurred during the availability check of the Open Perform Hierarchy action.
Contact IBM Software Support for assistance.
An error occurred during the availability check of a Refactor action.
Contact IBM Software Support for assistance.
The editor cannot locate a declaration for the {0} paragraph. The location of the declared paragraph cannot be determined.
Verify that the paragraph being referred to is declared, and try the operation again.
An incorrect argument was passed to the perform graph function.
Contact IBM Software Support for assistance.
The argument passed to the perform graph function is incorrect.
Contact IBM Software Support for assistance.
These messages pertain to the z/OS Integrated Development Environment (zIDE) in Rational Developer for System z.
Workspaces from WebSphere Developer 6.0 or 7.0 or Rational Developer for System z 7.1 are updated to work in the latest version of Rational Developer for System z when you open the workspace in Rational Developer for System z. The workspace is backed up before it is updated. This message indicates that the backup operation failed.
Contact IBM Software Support.
Workspaces from WebSphere Developer 6.0 or 7.0 or Rational Developer for System z 7.1 are updated to work in the latest version of Rational Developer for System z when you open the workspace in Rational Developer for System z. The workspace is backed up before it is updated. This message indicates the location of the backup copy.
No response is required.
Workspaces from WebSphere Developer 6.0 or 7.0 or Rational Developer for System z 7.1 are updated to work in the latest version of Rational Developer for System z when you open the workspace in Rational Developer for System z. This message indicates that the update operation failed.
Contact IBM Software Support.
The Remote Error List view is not visible in the perspective in a workspace updated from a release older than IBM WebSphere Developer for zSeries 6.0.1. This message explains how to open the Remote Error List view, which was introduced in WebSphere Developer for zSeries 6.0.1 to replace the Problems view.
Select Window>Show View>Remote Error List or Window>Reset Perspective to open the Remote Error list view.
The CICS suboption CTS31, CTS32, or CTS41 was specified for a local build. These suboptions are valid only in the context of syntax check.
If you are running a local build, remove the CICS suboption CTS31, CTS32, or CTS41.
The CICS suboption CTS32 was specified for a local build. This suboption is valid only in the context of syntax check when the source code is being checked against the syntax of CICS Transaction Server for z/OS 3.2.
If you are building a local application, remove the CTS32 suboption from the CICS compiler option.
The CICS suboption CTS41 was specified for a local build. This suboption is valid only in the context of syntax check when the source code is being checked against the syntax of CICS Transaction Server for z/OS 4.1.
If you are building a local application, remove the CTS41 suboption from the CICS compiler option.
An attempt was made to delete a data set that might be under control of SCLM.
To continue deleting the data set, type your user ID and password for the SCLM system and click OK.
An attempt was made to edit a resource that is under control of SCLM.
To edit the resource, access it by using the SCLM Developer Toolkit.
An attempt was made to delete a resource that might be under control of SCLM.
To continue deleting the resource, click OK.
An attempt was made to modify a resource that is under control of SCLM.
To modify the resource, access it by using the SCLM Developer Toolkit.
The resource that is indicated in the message might be under control of SCLM.
No response is required.
An attempt was made to open an include macro by using the Open Include Macro action. The macro was not added to the current workspace.
To add the macro to the current workspace, use the File > Import action.
An attempt was made to open an include macro by using the Open Include Macro action. The macro cannot be found in the SYSLIB library.
To verify that the file was allocated properly, locate the file in the Remote Systems view by expanding the MVS Files subsystem in the remote system connection.
To verify that the SYSLIB is specified correctly, do these steps:
An attempt was made to open an include macro by using the Open Include Macro action. The macro cannot be opened because the remote system on which it is located is not connected.
To connect to the remote system, open the Remote Systems view, select the remote system connection, and click Connect on the menu.
You requested to add a copy member to a project from an edit session, but there is no current filter for the data set name.
In the Remote Systems view, select MVS Files, and then select New > Filter to add a filter for the data set name.
You requested to open a copy library from an edit session, but it is not yet added to your workspace.
From the menu bar, click File > Import and browse to the copy library location to import it into your workspace.
You requested to open or browse a remote copy member from an edit session, but the file cannot be found in the SYSLIB.
In the Remote Systems view, verify that the SYSLIB library was allocated and that the copy member exists in this library. Try the action again.
You requested to open or browse a remote copy member from an edit session, but there is no connection to the remote system.
In the Remote Systems view, select the remote system and click Connect. After a connection is established, try the action again.
You requested to open a copy member in an edit session, but no copy member was highlighted.
Highlight the copy member name and try the action again.
You requested to open a data set or partitioned data set member from a JCL edit session, but the file cannot be found.
Verify that you selected a member name. In the Remote Systems view, verify that the data set and member exist on the remote system. Try the action again.
You requested to edit a file that is already open for editing.
Look for the file name in another editor session and edit it in that session.
You requested to edit a file that is already open for editing.
Look for the file name in another editor session and edit it in that session.
An attempt was made to open an include file by using the Open Include File action. The file is not added to the current workspace.
To add the include file to the current workspace, use the File > Import action.
An attempt was made to open an include file by using the Open Include File action. The file cannot be found in the SYSLIB library.
To verify that the file exists in one of the data sets specified in the SYSLIB concatenation, locate the data sets in the Remote Systems view. Expand the MVS Files subsystem in the remote system connection. Expand each data set in SYSLIB to find the member.
To verify that the SYSLIB is specified correctly, do these steps:
An attempt was made to open an include file by using the Open Include File action. The file cannot be opened because the remote system on which it is located is not connected.
To connect to the remote system, open the Remote Systems view, select the remote system connection, and click Connect on the menu.
An attempt was made to run a local syntax check on a file that was opened for editing from the Remote Systems view.
An attempt was made to run a local syntax check on a file that was opened for editing. The latest changes to the file cannot be saved, but the syntax check operation can be run on the copy stored in the local cache.
Click Yes to run the syntax check on the cached copy.
You requested to delete a placeholder file in an offline project. A placeholder file represents a remote file that is not downloaded and does not exist in the local workspace. This message usually results from an API operation rather than a user-interface operation.
Move the project to online state and try the operation again.
You requested to delete a file in a remote project, but you are not connected to the remote system.
Connect to the remote system and try the operation again.
You requested to move a placeholder file in an offline project. A placeholder file represents a remote file that is not downloaded and does not exist in the local workspace. This message usually results from an API operation rather than a user-interface operation.
Move the project to online state and try the operation again.
You requested to move a file in a remote project, but you are not connected to the remote system.
Connect to the remote system and try the operation again.
You requested to open a placeholder file in an offline project. A placeholder file represents a remote file that is not downloaded and does not exist in the local workspace. This message usually results from an API operation rather than a user-interface operation.
Move the project to online state and try the operation again.
You requested to open a file in a remote project, but you are not connected to the remote system.
Connect to the remote system and try the operation again.
You requested to edit a placeholder file in an offline project. A placeholder file represents a remote file that is not downloaded and does not exist in the local workspace. This message usually results from an API operation rather than a user-interface operation.
Move the project to online state and try the operation again.
You requested to edit a file in a remote project, but you are not connected to the remote system.
Connect to the remote system and try the operation again.
An error occurred while accessing the contents of a remote resource in a z/OS project.
If the error occurs during normal use, contact IBM Software Support to report the problem.
Rational Developer for System z failed to download the file from the remote system to the local cache.
Check connection and try the operation again. If the problem still occurs, contact IBM Software Support to report the problem.
Rational Developer for System z failed to find the local cache file when reading or writing contents of a remote resource in a z/OS project.
If the project is online, check the remote system connection and try the operation again. If the problem persists, contact IBM Software Support to report the problem.
Rational Developer for System z failed to upload the file from local cache to the remote system.
Check the remote system connection and try the operation again. If the problem still occurs, contact IBM Software Support to report the problem.
An error occurred while writing contents to a file in a z/OS project.
Check the remote system connection and try the operation again. If the problem still occurs, contact IBM Software Support to report the problem.
An error occurred while accessing an internal resource in a z/OS project.
Contact IBM Software Support to report the problem.
An error occurred while creating an internal resource.
Contact IBM Software Support to report the problem.
An error occurred while creating an internal resource.
Contact IBM Software Support.
A connection was made to a remote system on which host-based projects are defined. One or more workstation-based projects exist in the workspace. Host-based projects and workstation-based projects associated with the same remote system cannot exist in the same workspace.
Delete the workstation-based projects. Reconnect to the remote system.
A connection was made to a remote system on which host-based projects are defined. A host-based project cannot be loaded into the z/OS Projects view because of an I/O error in the configuration file shown.
Contact your system administrator.
A connection was made to a remote system on which host-based projects are defined. A host-based project cannot be loaded into the z/OS Projects view because of a workbench error.
Contact your system administrator.
A connection was made to a remote system on which host-based projects are defined. A host-based project cannot be loaded into the z/OS Projects view because of an I/O error in the configuration file shown.
Contact your system administrator.
A connection was made to a remote system on which host-based projects are defined. A host-based project cannot be loaded into the z/OS Projects view because the project definition file shown cannot be found.
Contact your system administrator. The error can have one of the following causes:
A connection was made to a remote system on which host-based projects are defined. A host-based project cannot be loaded into the z/OS Projects view because of a workbench error.
Contact your system administrator.
A connection was made to a remote system on which host-based projects are defined. A host-based project cannot be loaded into the z/OS Projects view because of an I/O error in the configuration file shown.
Contact your system administrator.
A connection was made to a remote system on which host-based projects are defined. A host-based project cannot be loaded into the z/OS Projects view because of a workspace error.
Contact your system administrator.
An attempt to rename a resource failed because another resource by that name exists.
Try the operation again with a different name.
A subproject was loaded from a host-based project. The remote system with which the subproject is associated does not exist among the currently defined remote system connections.
Contact your system administrator to modify the subproject definition file to specify the correct remote system name.
A subproject was loaded from a host-based project. The subproject is not associated with a remote system.
Contact your system administrator to modify the subproject definition file to specify the correct remote system.
A subproject was loaded from a host-based project. The subproject is not associated with a remote system.
Contact your system administrator to modify the subproject definition file to specify the correct remote system name.
This message reports the results of a generate JCL action. In this message, {0} is the JCL file that is generated and {1} is the name of the partitioned data set to which the JCL file is added.
No action is necessary.
This message displays in response to an attempt to update a locked resource.
You can see the lock status of a remote file by looking in the Properties view for the file. A locked file shows a user ID in the Lock Owner row of the properties table. An unlocked file shows no user ID in this row.
A request was made to generate a JCL file, but the target data set does not exist.
Request a different data set or allocate the target data set and resubmit the generation request.
You submitted a generate JCL request and specified a JCL file name that exists in the partitioned data set.
To generate the JCL and overwrite the existing JCL file, click Yes. To cancel the generate JCL request, click No.
The JES subsystem is not connected.
In the Remote Systems view, locate the remote system on which the resource you are working with is located. Expand the remote system connection, select JES, and then click Connect on the menu.
A submitted job ended abnormally. This message also includes the following message text:Click {0} to view the job output or click {1} to view the build properties currently in use.In this message {0} is a link to the job output and {1} is a link to the property group associated with the resource.
To check the job output, click the job output link. To check the build properties for the resource, click the property group link.
The submitted job failed because of a JCL error. This message also includes the following message text:
Click {0} to view the job output or click {1}
to view the build properties currently in use.
In this message {0} is a link to the job output and {1} is a link to the property group associated with the resource.
To check the job output, click the job output link. To check the build properties for the resource, click the property group link.
The execution of a job submission action was canceled.
To purge the job, do these steps:
While running a build request for a subproject, the system detected that no property group is associated with the subproject. A property group is required to build a subproject. In this message, {0} is the subproject name.
A request to edit an alias or the file it refers to was made, but the file is already open in an editor.
No response is required.
This message displays in response to a Delete menu action when the resource selected in the view is a data set alias.
The number of members in the partitioned data set exceeds the warning threshold set in the MVS Files preference page. This message gives you an opportunity to cancel the expansion request.
During a file comparison, a line in file {0} was modified so that its line length exceeds the maximum length allowed by the data set characteristics. This message warns that the line is truncated when the file is saved.
During a file comparison, multiple lines in file {1} were modified so that their line length exceeds the maximum length allowed by the data set characteristics. This message warns that the lines are truncated when the file is saved.
During a file comparison operation, the system found that the file indicated by {0} is already open in an edit session or locked by another user. This message gives you an opportunity to cancel the file comparison operation or to continue the operation with the file in read-only mode. If you continue with the comparison operation, you are not able to edit the locked file.
During a file comparison operation, the system found that both files are already open in an edit session or locked by another user. This message gives you an opportunity to cancel the file comparison operation or to continue the operation with the files in read-only mode. If you continue with the comparison operation, you are not able to edit the locked files.
During a file comparison, the record format of file {0} and record format of file {2} are displayed. If the record formats of both files do not match, then the user is prompted to confirm whether to continue with the file comparison.
To continue with the file comparison, click Yes. To cancel the file comparison operation, click No.
During a file comparison, the record length of file {0} and record length of file {2} are displayed. If the record lengths of both files do not match, then the user is prompted to confirm whether to continue with the file comparison.
To continue with the file comparison, click Yes. To cancel the file comparison operation, click No.
The requested operation requires access to a remote subsystem, such as MVS Files, z/OS UNIX Files, or JES.
Connect to the subsystem and try the operation again.
The Compress or Compress with Backup action was requested for a data set of type LIBRARY(PDSE). These actions are not supported for this type of data set.
No action is required.
The installation verification procedure completed successfully.
No action is required.
An I/O error occurred when gathering data set information.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
An I/O error occurred while uploading the file.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
An I/O error occurred while downloading a file or finding a record in it.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The process failed to initialize output while writing to a file.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The process failed to initialize a file while reading the file.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
A request to allocate a data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
A request to open a data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The data set cannot be updated because it is being updated by another user.
Wait for the data set to become available, and try the operation again.
The data set cannot be updated because it is being opened by other task.
Disconnect from the remote system, and try the update operation again. If the update fails again, collect the product log files and contact IBM Software Support.
The LOCATE macro failed while retrieving information from the catalog.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return codes from LOCATE.
The ESTAE or GETMAIN macro failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 164.
An attempt to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 168.
An attempt to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 184.
A request to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 24.
A request to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Code, code 4.
A request to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 40.
A request to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 44.
A request to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 48.
A request to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 56.
A request to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 8.
An attempt to locate a catalog entry failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Catalog Processor Return Codes, code 84.
A request to read a data set control block (DSCB) failed with a return code of 4, 8, 12 or 16.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
A request to read a data set control block (DSCB) failed with return code 12. This error can occur for the following reasons:
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
A request to read a data set control block (DSCB) failed with return code 16. This error is caused by an invalid work area pointer.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
A request to read a data set control block (DSCB) failed with return code 4. This error can occur when the required volume is not mounted.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
A request to read a data set control block (DSCB) failed with return code 8. This error occurs when the format-1 DSCB is not found in the VTOC of the specified volume.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMSdfp Advanced Services (SC26-7400): Return Codes from OBTAIN (Reading by Data Set Name).
A request to retrieve a migrated data set failed. Retrieval of migrated data sets is not supported because of long recall and transmission times.
No action is required.
During a request to rename or delete a file, the close file operation failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
During a request to rename or delete a file, the termination operation failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
The DFSMS macro DESERV GET_ALL function failed.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
This error results from an APPC setup problem for the TSO Commands service.
For information about tuning considerations when using APPC to start the TSO Commands service, see the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
During a request to connect to a remote system server, the process to create a thread failed.
For more information about this error, see the following topic in z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821): pthread_create()-Create a Thread.
During a request to connect to a remote system server, the process to create a thread failed.
For more information about this error, see the following topic in z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821): pthread_create()-Create a Thread, error code EAGAIN.
During a request to connect to a remote system server, the process to create a thread failed.
For more information about this error, see the following topic in z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821): pthread_create()-Create a Thread, error code EINVAL.
During a request to connect to a remote system server, the process to create a thread failed.
For more information about this error, see the following topic in z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821): pthread_create()-Create a Thread, error code ENOMEM.
An attempt was made to connect to a remote system server from a version of the client that is not supported on that server.
Verify the client and server versions of Rational Developer for System z. Install the correct version of the client or connect to a remote system that is compatible with the client.
This error occurs when downloading a load module or program object. The transfer types of the source and target data sets are different.
A request to delete a data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
A request to rename a data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The STOW macro, update Partitioned Data Set Directory (BPAM), failed.
Ensure that you have write authority for the data set. Contact your system administrator if you need assistance with obtaining write authority.
The STOW macro, updating partitioned data set directory (BPAM), failed because there is no space left in the directory.
Verify the amount of space in the directory. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. A permanent input or output error was detected. Control is not given to the error analysis (SYNAD) routine.
Contact IBM Software Support. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The system found an I/O error while trying to read or write the VTOC.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. A permanent I/O error occurred while attempting to write the EOF mark after the member. Control is not given to the error analysis (SYNAD) routine.
Contact IBM Software Support. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The system was unable to update the VTOC.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. Either no secondary space is available or a DADSM user exit error occurred. The error occurred when trying to write an EOF; all primary space is used.
Verify the availability of secondary space. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes. For more information about abend codes X'737', X'B37', X'D37', and X'E37', see z/OS V1R10.0 MVS System Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. Either no secondary space is available or a DADSM user exit error occurred.
Verify the availability of secondary space. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes. For more information about abend codes X'737', X'B37', X'D37', and X'E37', see z/OS V1R10.0 MVS System Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. An error occurred while writing data buffered in system buffers. Control is not given to the error analysis (SYNAD) routine.
Contact IBM Software Support. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The specified data control block is not open or is opened for input, or a DEB error occurred.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The initialize function was specified, but the PDSE was allocated with DISP=SHR.
Use DISP=OLD or DISP=MOD. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. Insufficient virtual storage was available to run the STOW function.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The caller attempted to issue add or replace for a member of the Program Management Library, which is a PDSE that contains program objects.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The alias has an invalid TTR.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The directory already contains the specified new name.
Verify the directory name. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. User-supplied TTRs are in the user data field of the directory entry (PDSEs only).
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The request to replace the file failed because you cannot replace an alias name if it is the same name as the primary member (PDSEs only).
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The add or replace failed when attempting to add or replace an alias, but the member identified by the TTR did not exist (PDSEs only).
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The replace failed when attempting to replace a primary member name. The PDSE is open for update and the member name identified an existing alias (PDSEs only).
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The replace failed when attempting to replace a primary member name. The PDSE is open for update, but the input TTR is not defined for that member (PDSEs only).
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The add failed because you cannot add a primary member name while the PDSE is open for update (PDSEs only).
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The replace failed because you cannot replace a primary member name while the PDSE is open for update and the specified name does not exist (PDSEs only).
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. One or more members were placed in a pending delete state; the space taken by those modules is not immediately available for reuse.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
The STOW macro, updating partitioned data set directory (BPAM), failed. The specified name cannot be found.
Verify the name. For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets: STOW Completion Codes.
Allocating a data set by using dynalloc() failed.
For more information about this error, see the following topic in z/OS V1R10.0 XL C/C++ Run-Time Library Reference (SA22-7821): dynalloc() -- Allocate a Data Set.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The DESERV macro GET_ALL function failed. The ID, length, or level of the parameter list is invalid. This function retrieves all member names and directory entries from a PDSE or PDS.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. It requires a PDSE data set.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS, failed. The concatenation number specified is greater than the concatenation number of the last data set in the concatenation.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The address of the DEB is 0 or the DEB is input but the DCB that the DEB points to does not point back to it.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The passed DCB is not open.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The address of the DCB is zero.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. To pass the DEB the caller must be in supervisor state or a system key.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The FUNC value is incorrect.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The gap specified is too large. The gap must be larger than DESP_ENTRY_GAP_MAX.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The address of the AREAPTR is 0.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The DESERV macro GET_ALL function failed This function retrieves all member names and directory entries from a PDSE or PDS. The connect intent specified is not valid with this function.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The CONN_INTENT(HOLD) requires the caller of function GET_ALL to be in supervisor state or system key.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. The DEBCHK macro failed. The DCB or DEB is invalid.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV Functions Common Reason Codes.
The DESERV macro GET_ALL function failed. This function retrieves all member names and directory entries from a PDSE or PDS. FREEMAIN failure.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The DESERV GET_ALL function failed. This function retrieves SMDEs for all member names (primary and alias) of a PDSE and can establish connections to members. The directory contains no members.
For more information about this error, see the following topic in z/OS V1R10.0 DFSMS Macro Instructions for Data Sets (SC26-7408): DESERV GET_ALL Function Reason Codes.
The BLDL macro failed. This macro obtains a list of information from the directory of a partitioned data set or partitioned data set extended (PDSE).
For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
The BLDL macro failed. This macro obtains a list of information from the directory of a partitioned data set or partitioned data set extended (PDSE). One or more entries in the list cannot be filled; the list supplied can be invalid.
For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
The BLDL macro failed. This macro obtains a list of information from the directory of a partitioned data set or partitioned data set extended (PDSE). A permanent I/O error was detected when the system attempted to search the directory.
For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
The BLDL macro failed. This macro obtains a list of information from the directory of a partitioned data set or partitioned data set extended (PDSE). Insufficient virtual storage was available.
For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
The BLDL macro failed. This macro obtains a list of information from the directory of a partitioned data set or partitioned data set extended (PDSE). This error has one of the following causes:
For more information about this error, see the following topic in z/OS DFSMS Macro Instructions for Data Sets (SC26-7408): BLDL--Build a Directory Entry List (BPAM).
A Language Environment operation failed.
Verify that you are using the correct version of Language Environment and that it is set up correctly. For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
A system ABEND occurred.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed when renaming data set.
Determine whether there is a resource shortage and try the operation again.
An I/O operation failed because the TGET macro failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the TPUT macro failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because an attempt to provide a relative position failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the DEVTYPE macro failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the RDJFCB macro failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the TRKCALC macro failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because an attempt to catalog a non-VSAM data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because of an attempt to uncatalog a non-VSAM data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because an attempt to rename a data set in the VTOC failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because no volume that contains any part of the data set was mounted and no unit was available for mounting.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because an unusual condition was encountered on one or more volumes.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because an attempt to delete a data set from the VTOC failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because a request for the position for access failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because of duplicate data set names on the volume.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed for one of the following reasons:
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because space on the direct access storage device (DASD) containing the requested volume cannot be obtained.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the requested absolute track is not available.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed for one of the following reasons:
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the average block length on text unit key DALAVGR (key 0009) was greater than the track capacity of the requested DASD volume.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because of an invalid DADSM REALLOC parameter list.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the system did not allocate the directory for a new partitioned data set (PDS). The space requested for the directory on text unit key DALDIR (key 000C) exceeded the space available on the specified volume.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because no space parameter was given for a new data set or zero space was requested at absolute track zero.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because a profile for the specified data set on this volume exists in the Resource Access Control Facility (RACF) data set.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the user is not authorized to define this data set. The user has the automatic data set protection characteristic without the RACF authorization to define data sets.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the installation exit rejected this request.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because a space request was rejected by the installation exit.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems", in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because a non-SMS managed data set cannot be created on an SMS-managed volume.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because a required CATALOG volume is currently not mounted.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because either the existing catalog structure is inconsistent with the operation, or the program was not authorized to run the operation.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the index structure necessary to catalog the data set does not exist.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because CATALOG space is exhausted on the control volume.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because a CATALOG I/O error occurred.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed, because of a CATALOG error.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed, because the data set was not on the volume as indicated in the catalog or volume text unit.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because of an OBTAIN I/O error. During data set allocation, an uncorrectable I/O error occurred when the system attempted to obtain a data set control block (DSCB).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because an invalid work area pointer was supplied.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the absolute address passed was not within the boundaries of the VTOC.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because virtual storage is unavailable.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because a request for exclusive use of a shared data set cannot be completed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the requested data set is unavailable. The data set is allocated to another job and its usage attribute conflicts with this request.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because one or more devices are not available.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed. The specified volume or an acceptable volume is not mounted, and the user is not authorized to mount a volume through the DYNALLOC request.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the device name specified is undefined.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the requested volume is not available.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because eligible device types do not contain enough devices.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the specified volume or device is in use by the system.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the volume is mounted on an ineligible permanently resident or reserved device.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because a permanently resident or reserved volume is on the required device.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because more than one device is required for a request that specifies a device.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because space is unavailable in the task input/output table (TIOT).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because the required catalog is not mounted, and the user is not authorized to mount a volume.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because of a CATALOG LOCATE error. Either the data set name specified is in error, or a system error occurred when processing the data set name.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because of a permanent I/O error while processing the cataloged data set.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because of insufficient real or virtual storage for processing the cataloged data set.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because an unsuccessful attempt was made to access a catalog that was locked for recovery. The job does not have authorization to run this function.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
Dynamic allocation failed because an unexpected return code was returned by catalog LOCATE.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the output data was truncated.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the file control block is corrupted.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because there was no room left in a physical record for any more DBCS characters.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed for one of the following reasons:
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because there was not enough room to start a DBCS string and data was written anyway with an SI to end it.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because an SI was written before the last double byte character was completed. z/OS must complete the last byte of the DBCS string with a padding byte X'FE'.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because an attempt was made to extend a file that allows writing, but the file cannot be extended.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the OPEN macro failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
An I/O operation failed because the CLOSE macro failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Consult with your system administrator. If you cannot solve the problem, contact IBM Software Support.
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. The data set name was not found.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. The PDSE is open for output and the FIND macro was issued to point to a member other than the one currently processing.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. The caller has only RACF execute authority to the PDSE.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. The share options of the PDSE member do not allow you to access it.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. A permanent I/O error occurred during the directory search.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. An I/O error occurred while flushing system buffers containing member data.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. No DCB address was provided.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. Insufficient virtual storage is available.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
The FIND macro, Establish the Beginning of a Data Set Member (BPAM), failed when finding a data set member. The DEB is invalid or not owned by a TCB in the current family of TCBs.
For more information about this error, see the following topic in z/OS V1R10 DFSMS Macro Instructions for Data Sets (SC26-7408): FIND--Establish the Beginning of a Data Set Member (BPAM).
An out of memory error occurred.
Verify memory usage and increase the memory heap size.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The code page conversion failed because the code page is not supported.
Verify that the correct code page is used. If correcting the code page does not resolve the error, contact IBM Software Support.
An attempt to lock the requested file failed. Another user might have a lock on the file.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file.
An attempt to lock the requested file failed. Another user might have a lock on the file.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file.
An attempt to lock the requested file failed. The resource name that was provided is invalid.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file. If these actions do not solve the problem, contact IBM Software Support.
An attempt to lock the requested file failed. Another user might have a lock on the file.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file.
An attempt to lock the requested file failed. Another user might have a lock on the file.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file.
An attempt to lock the requested file failed. Another user might have a lock on the file.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file.
An attempt to lock the requested file failed. Another user might have a lock on the file.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file.
An attempt to lock the requested file failed. Another user might have a lock on the file.
Verify whether another user locked the file and try the operation again. If the file is not locked by another user, verify that you have authority to lock the file.
An unexpected internal server error occurred.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Contact IBM Software Support.
An unexpected server error occurred.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
This error can occur while attempting to allocate a partitioned or sequential data set. Your user ID does not have the necessary permission and there is no ISPF Client Gateway in /var/rdz/WORKAREA. This work area must be allocated and all Rational Developer for System z users must have permission to write to the work area.
cd /var/rdz
ls -al
mkdir WORKAREA
chmod 777 /var/rdz/WORKAREA
cd /var/rdz
ls -al
mkdir logs
chmod 777 logs
A request to compress a partitioned data set failed. If you used the Compress with Backup action, then a backup copy of the data set is saved. In some cases, the failure might occur before the data set is backed up. In this case, a backup copy is not created.
If you used the Compress with Backup action and the failure occurred after the backup, then you can restore the data set from the backup copy.
A request to compress a partitioned data set failed because the target data set cannot be found. A backup data set is not created.
Select a valid data set and try the operation again.
A request to compress a data set failed because the target data set is not a partitioned data set. The compress action is not valid for data sets of type sequential or PDSE (Library). A backup data set is not created.
Select a partitioned data set and try the operation again.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
A request to compress a data set failed. An attempt to back up the data set before compressing it failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
A copy command failed, because the request to allocate the SYSUT data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Contact IBM Software Support.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
An HRECALL command failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
An HDelete operation for a migrated data set failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The TSO command server did not start normally.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290). Collect the ffs*.log files and contact IBM Software Support.
The TSO command server returned a bad response.
Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290)
An internal command that was sent by the Rational Developer for System z client is incomplete. This message indicates an internal logic error.
Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290)
File Manager Integration detected an unsupported command sent by the Rational Developer for System z client.
Contact IBM Software Support.
A server internal error occurred, but the message number is not defined in the resource file. This error might be caused by an inconsistency between the installed modules.
Check that the installation finished correctly. If completing the installation does not solve the problem, contact IBM Software Support.
A severe internal error occurred while synchronizing the Rational Developer for System z client and server.
Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290)
A severe internal error occurred.
Collect the fek*.log files and contact IBM Software Support. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290)
The target data set is not supported as a target data set for a COPY or MOVE operation.
Select the correct target data set for the COPY or MOVE operation.
An internal server error occurred.
Contact IBM Software Support.
An internal error occurred while the product was opening a file in an editor.
No action is required.
Copybook or include files changed since the last syntax check.
Request the Check Dependencies action and then try the operation again.
The product must gather information that pertains to the copybooks or include files that are used by the source program.
Request the Check Dependencies action.
An internal error occurred when the product was opening a remote resource.
No action is required.
An internal error occurred.
No action is required.
An internal error occurred.
No action is required.
An internal error occurred.
No action is required.
A request was made to open a file, but the user is not authorized to write to the file.
Obtain write access to file and try the operation again. If you cannot obtain write access, copy the file to a partitioned data set that you have write access to and edit the copied file.
The job that was submitted to the remote system failed.
To determine whether the job completed or JCL errors occurred, examine the job output under the JES node in the Remote Systems view. If there are JCL errors, the entry fields in the compilation step of the Procedures and Steps page might point to data sets that do not exist. To verify that the specified data sets exist, click Validate Data Sets.
The product relies on error feedback from the compiler to check syntax remotely. When error feedback is not available, a remote syntax check cannot be completed.
Verify that the DB2 precompiler or the CICS translator options are required. If so, then remote syntax check cannot be completed.
The compilation job that was submitted to the remote system failed.
To verify that the job completed successfully, look in the job output under the JES node in the Remote Systems view. If there is a syntax error, verify that the entry fields in the compilation step on the Procedure and Steps page are correct. To verify that the partitioned data sets that are specified exist, click Validate Data Sets.
The job that was submitted to the remote system failed.
Examine the job output to see whether the job completed or JCL errors occurred. If JCL errors occurred, the entry fields in the compilation step of the Procedures and Steps page might point to data sets that do not exist. To verify that the specified data sets exist, click Validate Data Sets.
An internal error occurred while the product was opening a file in an editor.
No action is required.
An internal error occurred while the product was opening a file in an editor.
No action is required.
A Rational Developer for System z administrator can configure site-specific defaults for particular properties in a property group. This message indicates that the default values were changed for the remote system indicated by {0}.
Click Yes to accept the updates or No to leave your property groups unchanged.
A Rational Developer for System z administrator can set up predefined property groups for a remote system. These property groups are downloaded to your workspace when you connect to the remote system. This message indicates that the system property groups were changed for the remote system indicated by {0}.
Click Yes to accept the updates or No to leave your property groups unchanged.
An error occurred during an import of a local project properties file that was requested on the Import Property Group window. The import file is not in the expected format.
Although project properties are stored in property groups, the product still supports the local project properties file for backward compatibility.
An error occurred during an import of an MVS subproject properties file that was requested on the Import Property Group window. The import file is not in the expected format.
Although project properties are stored in property groups, the product still supports the MVS subproject project properties file for backward compatibility.
An error occurred during an import of a property group file that was requested on the Import Property Group window. The import file is not in the expected format.
This message confirms a Property Group > Delete Overrides request.
Click Yes to delete the property group overrides defined for the resource or No to cancel the request and leave the overrides in place.
This message confirms a property group Delete request.
Click Yes to delete the property group or No to cancel the request.
An attempt was made to create a property group with the same name as an existing property group
Specify a new name for the property group.
The current Rational Developer for System z version uses property groups to define the build properties for z/OS resources. The file you are importing contains properties from an earlier release. This message indicates that the properties are to be imported into a property group.
Click Yes to import the properties into a property group or No to cancel the import request.
You requested an operation that requires the resource to have a property group associated with it. No property group is associated with the resource.
Choose one of the following options:
During a property group export operation, the target export file, indicated by {0}, cannot be opened.
Ensure that the file name specified is valid and that you have write access to the target location. Try the operation again. If the error persists, contact your system administrator.
During a property group export operation, the target export file, indicated by {0}, cannot be written to.
Ensure that the file name specified is valid and that you have write access to the target location. Try the operation again. If the error persists, contact your system administrator.
The .xml file that is being imported during a property group or workspace import operation contains an invalid category. The property group or workspace is not imported. The following sample messages show examples of this error:
CRRZI0443E USE_LOCAL_PREPROCESSORS is not a
registered category.
CRRZI0443E RUN_FOR_CODECOVERAGE is not a
registered category.
This error can occur when you try to import a property group or workspace from a later Rational Developer for System z version into an earlier version, for example, importing a version 8.0 property group into a version 7.6 workspace. Later versions of Rational Developer for System z clients are not compatible with earlier versions.
Manually create a workspace or property group with the characteristics you want.
During a property group import operation that involves multiple property groups, some of the groups cannot be imported because groups with the same names exist. The groups that do not present name conflicts are imported
No action is required.
In an attempt to import property groups from the file indicated by {0}, the import file cannot be read.
Ensure that the file you specified is a valid property group .xml file. Try the operation again. If the error persists, contact your system administrator.
A property group import file has more than one instance of a property group category for the property group indicated by {1}. The property group is not imported.
Remove the duplicate category instance and try importing the property group again.
The .xml file that is being imported during a property group import operation contains an invalid property name. The property group is not imported.
Correct the property name and try the import operation again.
A Rational Developer for System z administrator can configure site-specific defaults for particular properties in a property group. This message indicates that the default values were changed for the remote system indicated by {0}.
Click Yes to accept the updates or No to leave your property groups unchanged.
A Rational Developer for System z administrator can set up predefined property groups for a remote system. These property groups are downloaded to your workspace when you connect to the remote system. This message indicates that the system property groups were changed for the remote system indicated by {0}.
Click Yes to accept the updates or No to leave your property groups unchanged.
A Check Dependencies request was made, but could not be completed.
For more information about the errors that occurred during this operation, click Details.
This message displays in response to an attempt to copy a folder or a partitioned data set into an MVS subproject by dragging it.
To copy the contents from a source folder or partitioned data set into an MVS subproject:
A remote resource cannot be deleted if it is locked by another user or program.
To determine the lock owner of a remote resource, open the properties view and expand the Info category to see the Lock owner property.
A name specified for a new local project exists in the workspace. Because names are not case-sensitive, the names "MyNewProject" and "Mynewproject", for example, conflict.
Choose a unique name for the project.
An internal error occurred during creation of local project '{0}'.
Contact IBM Software Support.
During execution of the DCLGEN utility wizard, Rational Developer for System z generates and submits JCL to generate copybooks, include files, macros, and C/C++ header files from database table information by using the DB2 utility DCLGEN. This message indicates that the job was submitted.
To check the job output, do these steps:
The Job Monitor server must be started before jobs can be submitted.
Contact your system administrator to start the Job Monitor server
During an export properties operation, the export file cannot be created or saved.
To open the log file, open workspace/.metadata/.log (Windows) or workspace\.metadata\.log (Linux) on your workstation file system.
To import a remote z/OS project, you must be connected to the remote system that contains the project resources.
During a project import operation, an existing project with the same name was found in the workspace. Projects must have unique names.
Specify a new name for the project.
A work online operation found a file with the same name, but without the file extension, in the current folder.
Make sure that the file names in the folder are unique with or without the extensions. Specify a new unique name for the files in the folder.
During a work online upload operation, an invalid MVS name was found. Member names cannot be more than eight characters.
Correct any member names that do not confirm to data set member naming rules and try the operation again.
During a work online upload operation, an invalid MVS name was found. The member name must not have a period.
Correct any member names that do not confirm to data set member naming rules and try the operation again.
When a project is offline, you can rename data sets or add new data sets to it. This message indicates that a new or renamed data set does not conform to data set naming rules.
Be sure that any new or renamed data sets use no more than 8 characters in each segment of the data set name. Correct any data set names that do not conform to data set naming rules and try the operation again.
The work online upload operation checks for any encoding mismatch between a local resource and the corresponding remote resource. If encoding for SO/SI is specified for a local resource, the operation compares it to the host encoding of the remote resource. If the encodings do not match, the user is asked to override the host encoding with the SO/SI encoding or cancel the operation.
The encoding mismatch must be resolved. To change the host code page of the remote resource to the SO/SI encoding of the local resource, click Yes. To leave the host code page of the remote resource unchanged and cancel the operation, click No.
A team provider plug-in can add properties to resources owned by Rational Developer for System z by registering its own properties provider. The message indicates that the registration failed because another properties provider is already registered.
Contact IBM Software Support.
A team provider plug-in can add properties to resources owned by Rational Developer for System z by registering its own properties provider. The message indicates that the registration failed because the specified resource does not support properties.
Contact IBM Software Support.
A setting on the remote system is causing z/OS UNIX Files and Shells to be hidden on the client user interface.
If you believe this setting is incorrect, contact your systems administrator.
This message displays in response to a Check Data Sets request on a Procedures and Steps page of the property group editor. It indicates that the data set name specified does not exist.
Specify another data set name and try again.
This message displays in response to a Check Data Sets request on a Procedures and Steps page of the property group editor. It indicates that the data set name specified was already added to the field.
Specify another data set name and try again.
This message displays in response to a drag operation on a Procedures and Steps page of the property group editor. It indicates that an object other than a data set was dragged to the field.
Drag a data set name into the field.
This message displays in response to a drag operation on a Procedures and Steps page of the property group editor. It indicates that the field to which a data set name was dragged can contain only one data set name.
To replace the data set name already in the field, clear the filed and then drag another name to the field.
Data set names in the fields on the Procedures and Steps page of the property group editor are limited to 44 characters. This warning indicates that the current data set name is nearing this limit and might exceed it if the high-level qualifier is too long.
Check the length of the high-level qualifier to ensure that it does not result in a data set name that exceeds the maximum length.
Data set validation for a property group requires a connection to a remote system.
Connect to the remote system and try the operation again. To connect to the remote system:
During a property group create operation, the property group name was found to be missing.
Specify a name for the property group on the Property Group Information page and try saving the property group again.
The Rational Developer for System z editors are able to preserve the integrity of characters as they are transferred from the remote system to the workstation and back again. For some code pages, however, it is not possible to preserve round-trip integrity of certain characters. This message warns that the file under edit contains characters whose round-trip integrity cannot be preserved.
To save the file with corrupted characters, click Yes. To close the file without saving your changes, click No.
The Rational Developer for System z editors are able to preserve the integrity of characters as they are transferred from the remote system to the workstation and back again. For some code pages, however, it is not possible to preserve round-trip integrity of certain characters. This message warns that the file under edit contains characters whose round-trip integrity cannot be preserved. One cause of this message can be the definition of an inappropriate alternative logical NOT symbol. Because the file is being edited from the remote system, it is opened in read-only mode.
To edit the file, copy it to a local project in your workspace and change the corrupted characters before you copy it to the remote system. For instructions for setting an alternative logical NOT symbol, see the related topics.
An error occurred while a remote resource was being shared with a team provider and creating a local copy of the resource.
For details about this error, see the .log file in the .metadata folder of the current workspace.
When you load a team resource into the remote file system, the remote resource must be added to a subproject. A subproject was not specified by the team provider application.
Contact your systems administrator.
When you load a team resource into the remote file system, a local copy of the remote resource is also downloaded to the client. The remote resource was not found.
Contact your systems administrator.
When you load a team resource into the remote file system, the remote system is inferred from the target subproject. No remote system was associated with the subproject.
Contact your systems administrator.
When you load a team resource into the remote file system, the remote resource must be added to a subproject. An error occurred when the remote resource was added to the subproject.
For details about this error, see the .log file in the .metadata folder of the current workspace.
When you share a remote resource with a team provider, a local copy of the remote resource is downloaded to the client. The team provider application specified an invalid local destination.
Contact your systems administrator.
During a resource check-in operation, a sandbox prefix was provided when the remote sandbox file name was expected.
Try the operation again. Specify the remote sandbox file name.
This message displays in response to a Check Data Sets request on a Procedures and Steps page of the property group editor. It indicates that the data set names specified are valid.
No response is required.
This message displays in response to a Check Data Sets request on a Procedures and Steps page of the property group editor. It indicates that the data set names specified cannot be validated because they contain the <HLQ> variable. The data set names might or might not be valid.
No response is required.
The target of the copy or rename operation exists, but the option to replace an existing data set was not specified.
Try the operation again and either choose a different target name or specify the replace option.
A target data set was found, but its characteristics do not match the characteristics of the source data set.
Specify a different source or target data set so that the characteristics match or specify a target that does not exist so that it can be allocated with the same characteristics as the source data set.
The target of the copy or rename operation exists but the option to replace an existing data set was not specified.
Try the operation again and either choose a different target name or specify the replace option.
During a property group edit operation, for the property group indicated by {0}, the property group was found to be open for a property group override request. You cannot edit a property group while it is open for overrides.
Close the Property Group Editor and then try the edit operation again.
During a property group override operation for the property group indicated by {0}, the property group was found to be open for a property group edit request. You cannot override a property group while it is open for edit.
Close the Property Group Editor and then try the override operation again.
An attempt to create a CICS debug configuration failed. A possible reason for the failure is an invalid CICS Debug profile server port number specified on the CICS Debug Configuration preference page.
Contact your system administrator to obtain the correct CICS Debug profile server port number. Specify the port number on the CICS Debug Configuration preference page and then try to create the debug configuration again.
An attempt was made to create a debug configuration, but there is no CICS Debug profile server port associated with the CICS region.
Contact your system administrator to obtain the correct CICS Debug profile server port number. Specify the port number on the CICS Debug Configuration preference page and then try to create the debug configuration again.
The number of members in the partitioned data set exceeds the warning threshold set in the MVS Files preference page. This message gives you an opportunity to cancel the request to add the partitioned data set to the subproject.
The region specified on the CICS page of the Debug Configurations > Remote CICS Application wizard does not exist.
On the CICS page of the Debug Configurations > Remote CICS Application wizard, click the Define CICS Connection link to open the CICS Explorer > Connections preference page. Use this page to connect to a CICS region and then try again to define the CICS debug configuration.
The Rational Developer for System z preferences provide a warning threshold for opening large files. This warning helps to prevent out-of-memory errors.
The property group that is being imported contains property group categories that are not supported by the current version. The supported categories are imported and the unsupported categories are ignored.
No response is required.
The operation requires the error feedback compilation option to be specified.
Enable the error feedback option and try the operation again. To enable the error feedback option:
The Rational Developer for System z editors are able to preserve the integrity of characters as they are transferred from the remote system to the workstation and back again. For some code pages, however, it is not possible to preserve round-trip integrity of certain characters. This message warns that the file under edit contains characters whose round-trip integrity cannot be preserved.
To open the file in the comparison editor, click Yes. To cancel the file comparison request, click No.
The Rational Developer for System z editors are able to preserve the integrity of characters as they are transferred from the remote system to the workstation and back again. For some code pages, however, it is not possible to preserve round-trip integrity of certain characters. This message warns that the files under edit contain characters whose round-trip integrity cannot be preserved.
To open the files in the comparison editor, click Yes. To cancel the file comparison request, click No.
While attempting to export configuration files, Rational Developer for System z encountered problems with the keymapping.xml file and cannot update the file. A new keymapping.xml file is generated and uploaded to the remote system.
No action is required. The new key mapping file contains settings for only the configuration files included in the current export request.
You requested to export configuration files, but none of the remote systems to which you are connected are enabled for push-to-client.
Connect to a remote system that has the push-to-client function enabled and try again. Contact your system administrator if you do not know which remote systems are enabled for push-to-client.
The file specified in the Error Feedback XML File Name field of the Local Preprocessor page of the current property group contains formatting or content errors.
The remote system to which you are connecting is configured to automatically install product updates when you connect to it. Product updates are available for installation.
Click OK to install the product updates. Your workbench is shut down and IBM Installation Manager is started to install the product updates. Restart Rational Developer for System z when the product installation is complete.
You attempted to copy a partitioned data set member that is an alias. The copy operation cannot be completed because alias processing is disabled.
To enable alias processing, click Window > Preferences, then expand the Remote Systems and z/OS sections and click MVS Files. On the MVS Files preference page, select the Process member aliases on module copy option. For more information about enabling alias processing, see MVS Files.
You attempted to copy a partitioned data set member that is an alias. The copy operation cannot be completed because the primary member does not exist.
For more information about copying data set aliases, see Copying load modules. For more information about enabling alias processing, see MVS Files.
You attempted to copy a partitioned data set member that is an alias or has an alias defined. The copy operation cannot be completed because the copy source and the copy target are the same.
Try the copy operation again and specify a different target. For more information about copying data set aliases, see Copying load modules.
The copy command failed because the request to allocate a data set before the IEBCOPY command failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The comparison editor does not support edit of bidirectional file content.
To open the files in the comparison editor, click Yes. To cancel the file comparison request, click No.
The comparison editor does not support edit of double-byte character set (DBCS) file content.
To open the file in the comparison editor, click Yes. To cancel the file comparison request, click No.
The comparison editor does not support edit of double-byte character set (DBCS) file content.
To open the files in the comparison editor, click Yes. To cancel the file comparison request, click No.
The comparison editor does not support edit of bidirectional file content.
To open the file in the comparison editor, click Yes. To cancel the file comparison request, click No.
You are currently connected to primary system {1} and initiated an export configuration files action. The last time you requested this action, you were connected to primary system {0}. This message is a reminder to verify that you intend to export configuration files to a different primary system than the one to which you exported previously.
If you intend to export to a different primary system, no action is required. You can continue with the export action.
If you did not intend to export to a different system:
You are connected to two or more remote systems that are defined as the primary system in a push-to-client environment. The push-to-client feature allows only one connection to a primary remote system.
Disconnect from all but one primary remote system. Contact your system administrator if you do not know which remote systems are primary.
An attempt to export a configuration file to a remote system failed. Your user ID does not have the correct file permissions to write to the parent directory. To export system or global configuration settings to the remote system, you must have write access to the push-to-client configuration directories on the remote system. File permissions for the push-to-client directory on the remote system are set by using the file.permission directive in the pushtoclient.properties file.
For more information about push-to-client file permissions and configuring push-to-client support on z/OS, see the IBM Rational Developer for System z Host Configuration Guide (SC23-7658).
This message displays in response to a Team > Synchronize with remote request. It indicates that the local and remote resources are synchronized.
No response is required.
This message displays in response to a Team > Synchronize with remote request. It indicates that an error occurred while synchronizing the local and remote files.
Contact your system administrator.
This message displays in response to a Team > Synchronize with remote request. It indicates that no remote system is defined.
Define a connection to a remote system, connect to the system, and try the operation again.
A Mark as Merged request in the Synchronize perspective failed.
Contact your system administrator.
For some operations, such as Enable Remote Synchronization, you can type the <HLQ> variable in the high-level qualifier field of the user interface. Use of this variable requires a connection to a remote system for the variable to be correctly substituted.
Connect to a remote system and try the operation again.
Synchronizing the local project with the remote system results in overwriting changes that were made on the remote system.
Click Yes to continue and overwrite the remote changes or No to cancel the request.
An inbound change cannot be copied to the local project in the synchronize perspective.
Contact your system administrator.
An outbound change cannot be copied to the remote system in the synchronize perspective.
Contact your system administrator.
The remote system specified in the Pushable Manifest Editor differs from the remote system associated with the local project.
To change the remote system associated with the local project, click Yes. To leave the remote system associated with the project unchanged, click No.
A local file extension specified in the Pushable Manifest Editor is already added to the mapping.
Specify a different file extension.
Synchronizing the local project with the remote system results in overwriting changes that were made on the local system.
Click Yes to continue and overwrite the local changes or No to cancel the request.
During a remote synchronization operation, the product could not connect to the remote system.
Ensure that the remote system connection is defined in the Remote Systems view and that the connection properties are defined correctly. Contact your systems administrator for the correct connection properties.
A request was made to copy a local resource to the remote system by using the push-to-host Remote > Copy to Remote or Remote > Synchronize with Remote operation. The target data set was not found on the remote system.
You must allocate the target remote data set before you can copy a local resource to it. Allocate the data set on the remote system. Ensure that the remote data set name and the remote system are specified correctly in the remote mapping. Try the operation again.
A file referenced in the .RemoteMapping pushable manifest editor file is in an unsupported format. A non-path item was found when a path was expected.
Open the .RemoteMapping file in a text editor and correct the line in error.
An error occurred while a mapping for remote synchronization was being created. The remote system name is missing.
Open the Pushable Manifest Editor and specify a valid remote system location.
An error occurred while a mapping for remote synchronization was being created. The local resource that is specified in a mapping does not exist.
Either create the local resource or clear the mapping from the editor.
An error occurred while a mapping for remote synchronization was being created. The remote resource type is incorrect for a mapping. Valid resource types are MVS and USS.
Open the Pushable Manifest Editor and set a valid remote resource type, or clear the mapping for that item.
An error occurred while a mapping for remote synchronization was being created. The remote resource type is missing.
Open the Pushable Manifest Editor and specify a remote resource type, or clear the remote location.
An error occurred while a mapping for remote synchronization was being created. More than one local resource is mapped to the same remote resource.
Open the Pushable Manifest Editor and specify a different remote resource for each local resource, or remove duplicate entries from the manifest.
An error occurred while a mapping for remote synchronization was being created. The remote resource that is specified in a mapping cannot be found.
Open the Pushable Manifest Editor and set a valid remote resource location, or allocate the remote data set that is specified in the mapping.
This message prompts you to confirm a Restore Defaults action on the Features preference page for COBOL.
Click OK to remove all COBOL feature customization or Cancel to cancel the restore defaults request.
This message prompts you to confirm a delete action on the Features preference page for COBOL.
Click Yes to delete the feature or No to cancel the delete request.
A request was made to export the customizable features for COBOL programs to an XML, but the file exists in the same location on the file system.
To replace the file, click Yes. To cancel the export operation, click No.
During an import operation, a feature was found to exist.
To replace the feature, click Yes. To cancel the import operation, click No.
While a COBOL code template was being edited, an invalid COBOL comment was provided.
Type a valid COBOL comment and save the template.
While a code template was being edited, a required variable was omitted.
Type a variable or select one by clicking Insert Variable.
While a code template was being edited, one of the following situations occurred:
Use a different variable and save the changes to the template.
The remote system to which you are connected uses the push-to-client feature to distribute workspace configuration updates to Rational Developer for System z clients. Your workspace was updated with new configurations.
No action is required. If you would like to suppress this message the next time you connect to the remote system, click Do not show this message again on the message window.
The push-to-client feature allows a workspace to be associated with only one access group. You previously imported configuration files from group {0} and are now requesting to import configuration files from group {1}.
The remote system to which you connected uses push-to-client access groups to control access to configuration updates. Since you last connected to this system, you were removed from access group {0}. While you can still connect to this remote system, you can no longer receive push-to-client updates from it.
If you do not need any configuration updates from this remote system, then no action is required. If, however, you need to receive updates from this remote system, contact your system administrator.
The remote system to which you connected previously used push-to-client access groups to distribute configuration updates. Since you last connected to this system, access groups were disabled. While you can still connect to this remote system, you can no longer receive push-to-client updates from group {0}.
No action is required.
When you open a workspace that was created in an earlier version of the product, it is migrated to the current version. Before the migration, the workspace is backed up. This message indicates that the backup operation failed.
To continue migrating the workspace without backing it up, click Yes. To stop the migration and correct the problems, click No.
A local build or syntax check operation was requested, but the database connection in the Data Source Explorer is not connected
Switch to the Data Perspective. In the Data Source Explorer, connect to the database that matches the database that is specified in the Local Compiler Options page of the property group that is associated with the resource for which the operation was requested.
An operation that requires a database connection opened the database connection window. A connection cannot be made with the credentials that were used.
Switch to the Data Perspective. In the Data Source Explorer verify the database name, IP address, port number, user ID, and password. Try to connect to the database again.
One or more errors occurred while the product was attempting to determine the build dependencies of the selected resource. The detailed message for each error was collected and associated with the original error message.
Examine the detailed error message for each error and take the appropriate remedial action.
The current action was expecting the input resource to be a member of an MVS subproject.
Select an MVS subproject or one of its members and try the action again.
Because of the specified error, the dependency list of the selected resource might be incomplete.
Correct the condition that caused the specified error and try the action again.
A validation error occurred when you attempted one of the following actions:
You might not have the correct authority to do these actions.
Make sure that you have the correct authority on the remote system to do the operation. Ask your systems administrator to grant you the authority that you need.
The remote system to which you are connecting is configured to automatically download product updates. During the process of shutting down Rational Developer for System z, the Java virtual machine (JVM) failed to terminate in a short amount of time.
The specified symbol cannot be used as the PL/I logical NOT symbol.
Refer to the PL/I language reference for a list of valid symbols and try the action again.
A problem was encountered while attempting to carry out the requested operation which prevents the operation from completing.
Examine the detailed error message for the problem and take the appropriate remedial action.
A problem was encountered when trying to set the path of the bidirectional conversion table (BCT) file.
For details about this error, see the .log file in the .metadata folder of the current Rational Developer for System z workspace.
A problem was encountered when trying to read the specified MVS mapping root file.
For details about this error, see the .log file in the .metadata folder of the current Rational Developer for System z workspace.
The current operation requires an exclusive lock on the specified file but the file is already locked.
If you are not already working with the file, contact your systems administrator for assistance locating the source of the lock.
The current operation requires a DataStore log, but one was not available.
Disconnect from the remote system and connect again. Try the operation again. If you continue to receive this error, contact your systems administrator.
The high-level qualifier that is associated with the target of the move or copy operation cannot be found.
Check that you entered the correct target name and try the operation again.
A problem occurred while attempting to upload the file contents to the remote system.
Examine the detailed error message for the problem and take the appropriate remedial action.
An unexpected error occurred when attempting to validate the requested file operation.
For details about this error, see the .log file in the .metadata folder of the current Rational Developer for System z workspace.
A problem occurred while attempting to set the browse request session property on the file.
Examine the detailed error message for the problem and take the appropriate remedial action.
The current operation requires an exclusive lock on the specified file, but an alias of or reference to the file is already locked.
If you are not already working with the alias or reference, contact your systems administrator for assistance locating the source of the lock.
An unexpected error occurred when Rational Developer for System z attempted to download the requested remote file.
For details about this error, see the .log file in the .metadata folder of the current Rational Developer for System z workspace.
A remote error marker cannot be created because the selected resource is not an MVS resource.
Select an MVS resource and try the action again.
Certain operations are not allowed when a resource is under SCLM control, but the Rational Developer for System z server code does not support this check.
Contact your systems administrator.
A problem occurred when Rational Developer for System z attempted to save the current file system mappings.
Examine the detailed error message for the problem and take the appropriate remedial action.
You must be connected to a remote system to work with remote z/OS resources.
Connect to the remote system and try the operation again.
On the Find Member window, you typed a member name that does not exist in the partitioned data set.
On the Find Member window, you typed a member name pattern that results in more matches than the current limit.
The requested action for the data set indicated by {0} completed successfully.
No action is required.
The requested action for the number of data sets indicated by {0} completed successfully.
No action is required.
The requested action for some data sets completed successfully. The action was requested for the number of data sets indicated by {1} and completed successfully for the number of data sets indicated by {0}.
No action is required.
The requested action for the selected data set did not complete successfully.
Try the operation again. If the failure recurs, contact your systems programmer.
This message prompts you to confirm a request to delete a z/OS file system mapping.
Click Yes to delete the mapping or No to cancel the request.
In the Retrieve Data Set window a maximum of {1} matching data sets can be displayed. The data set name pattern entered matches more data set names than the maximum allowed.
Use a data set name pattern that results in fewer matches. For example, if you previously typed USERID.TEST.C*, typing USERID.TEST.COB* might result in fewer matches.
This message indicates that the Compress action for the data set indicated by {0} completed successfully.
No action is required.
This message indicates that the Compress action for a number of data sets indicated by {0} completed successfully.
No action is required.
This message indicates that the Compress action for some data sets completed successfully. The action was requested for the number of data sets indicated by {1} and completed successfully for the number of data sets indicated by {0}.
No action is required.
This message indicates that the Compress action for the data set indicated by {0} did not complete successfully.
Attempt the compress again. If the failure recurs, contact your systems programmer.
This message is a prompt to confirm the removal of a global variable.
Select Yes or No.
This message is a prompt to confirm the removal of a user variable.
Select Yes or No.
This message is displayed when you remove a local preprocessor on the Local Preprocessor page of the property group editor. There is no undo action for removing a local preprocessor.
To delete the local preprocessor, click OK. To keep the local preprocessor, click Cancel.
This message is displayed when you remove a step from a Procedures and Steps table in the property group editor. There is no undo action for removing a step.
To remove the step, click OK. To keep the step, click Cancel.
Ensure that the z/OS UNIX file exists. Try the operation again.
For the operation to work successfully for this copybook, the copybook must not have any dependencies.
Make sure that the copybook does not have any dependencies. Try the operation again.
This message displays in response to successful creation of a new project. It prompts you to switch to the perspective that is most commonly used to work with the project type.
Click Yes to switch to the perspective or No to remain in the current perspective.
This message displays in response to successful creation of a new project. It prompts you to switch to the z/OS Projects perspective, which is most commonly used to work with this project type.
Click Yes to switch to the z/OS Projects perspective or No to remain in the current perspective.
A build request was submitted for an offline project. A project must be online to be built.
Move the project to online state and try the build operation again.
A build request was submitted, but the build server cannot be found.
Contact your system administrator.
An edit request was submitted for a locked file. The file can be opened for read-only access, but it cannot be edited.
To determine the lock owner of a remote resource, open the properties view and expand the Info category to see the Lock owner property.
An edit request was submitted for the specified file, which is locked by the specified user. The file can be opened for read-only access, but it cannot be edited.
No response is required.
An edit request was submitted for a locked file. The file can be opened for read-only access, but it cannot be edited.
You can continue to browse the file in read-only mode, but to correct the file lock problem you need to reconnect to the remote system.
A request was made to export a property group, z/OS project, or z/OS file system mapping to a file, but the target file exists.
To overwrite the file, click Yes. To cancel the export operation, click No.
A Rebuild Project or Rebuild Subproject request cannot be completed.
Before building a project or subproject:
The editor tried to open the file, but the open operation failed with an exception. The file cannot be opened.
Verify that the file exists and try the operation again.
The editor tried to open a file, but failed with an exception. The file cannot be opened
Verify that the file exists and try the operation again.
This message indicates a successful export z/OS project operation.
No response is required.
A request to drag a local file into a local folder in the z/OS Projects view failed. The file cannot be copied because a resource with the same name but in a different case exists in the target folder.
Verify the source file name and target folder and try the operation again.
A problem occurred during the download action of a work online operation. A local copy of the resource cannot be created in the offline project.
No action is required.
As part of a work offline operation, all the selected remote resources are downloaded to a local project and all the properties that are associated with the remote resource are migrated to the local resource. An error occurred while the operation was migrating a property.
Check the property for which the migration failed and make sure to set it before you run operations like syntax check, which uses the properties of the local resource.
Before you take a project online by using the Work Online action, you must upload the changes that you made to the resources when the project was offline. If you click Work Online without uploading the changes that were made locally (while the project was offline), the changes are lost. You must confirm that the work online operation can continue, which causes the local changes to be lost.
When a project is offline, the resources on the remote system are still accessible to others. You must merge your changes with any changes other users made to resources.
To upload and changes that you made while the project was offline, select them in the Changes and then select Upload from the menu. After you upload all the changes you want to save, click Work Online.
During the upload action of a work online operation, a problem occurred while the operation was uploading the local resource and creating a remote resource.
No action is required.
The push-to-client feature allows a workspace to be associated with only one access group. You previously exported configuration files to group {0} and are now requesting to export these configuration files to group {1}.
The remote system to which you connected uses push-to-client access groups to control access to product updates. Since you last connected to this system, you were removed from access group {0}. While you can still connect to this remote system, you can no longer receive push-to-client updates from it.
If you do not need any product updates from this remote system, then no action is required. If, however, you need to receive updates from this remote system, contact your system administrator.
The remote system to which you connected previously used push-to-client access groups to distribute product updates. Since you last connected to this system, access groups were disabled. While you can still connect to this remote system, you can no longer receive push-to-client updates from group {0}.
No action is required.
The System z Data Editor could not open the specified file. This error occurs when the downloaded cache files are not valid.
Clear the local downloaded cache and open the dataset again.
The System z Data Editor cannot save the data set and the editing content cannot be saved to the remote system.
Confirm that the data set is not locked by another editor. If the data set is open in another editor, close the editor and the System z Data Editor. Reopen the data set with the System z Data Editor.
Getting the contents of a LogicalFSFileStore is valid only when the resource associated with the store is a file.
No action is required.
This message can occur when you add a remote partitioned data set (PDS) to a subproject. To update the content-type file decoration, the Eclipse system must query the contents of the Eclipse file system resource that represents one of the members of the added PDS. To read its contents, however, it is using a scheduling rule that does not include the cached files folder. The request to add the resource to the subproject completed successfully.
No action is required.
The remote system to which you are connecting is configured to automatically download product updates. You are not allowed to reject these updates. When you click OK, your workbench is shut down and IBM Installation Manager is started to install the product updates. The workbench is automatically restarted after the product update completes.
If you are operating Rational Developer for System z on a Linux platform, the following message text also displays:
Rational Developer for System z will shut down but
you will not see any status. The product will
restart automatically in a few minutes.
Click OK.
A request to update a remote file failed.
For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The product attempts to download the remote preprocessor output after it runs the remote preprocessor. An error while the product was downloading the output.
Verify that you are still connected to the system on which the remote preprocessor runs and that you have read access to the data set that contains the preprocessor output.
The script that runs the remote preprocessor finished with an error.
To see the error, click Details.
The product ran the script that starts the remote preprocessor, but cannot find the preprocessor output.
Verify that you are running the script that you intend to run. If so, verify that the script is executing correctly.
The product cannot find the remote preprocessor that is specified in the property group.
Verify that the remote preprocessor has the data set and member name that is specified in the property group and that you have read access to the data set that contains the preprocessor.
To build a project, you need associate a property group with it. No property group is associated with the project.
Use the Associate Property Group action to associate a property group with a subproject and then try the build operation again.
A New > Allocate VSAM Data Set operation failed to allocate the data set. The most common reason for this failure is missing values for the space unit, primary unit, and secondary unit parameters.
Check the allocation parameters on page 3 of the wizard and try the operation again. Contact your system administrator for guidance on specific allocation parameter values.
The CICS suboption CTS42 was specified for a local build. This suboption is valid only in the context of syntax check when the source code is being checked against the syntax of CICS Transaction Server for z/OS 4.2.
If you are building a local application, remove the CTS42 suboption from the CICS compiler option.
The record length information is not available from the property associated with the data set.
Check the status of the server to see if there are errors. Try connecting to the server again.
The file cannot be open because the data set record is defined as RECFM=U. The System z Data Editor cannot open a data set whose record format is undefined because the editor uses the record format and length to determine each record of the sequential data set.
Use a different editor to open the data set.
The Rational Developer for System z editors are able to preserve the integrity of characters as they are transferred from the remote system to the workstation and back again. For some code pages, however, it is not possible to preserve round-trip integrity of certain characters. This message warns that the file under edit contains characters whose round-trip integrity cannot be preserved. Because the file is being edited from the remote system, it is opened in read-only mode.
To edit the file, copy it to a local project in your workspace and change the corrupted characters before you copy it to the remote system.
A connection to the debug tool cannot be made.
Verify the port number and try the operation again.
This message displays when you save a new DB2 and IMS debug configuration. It prompts you to define connection settings for the DB2 and IMS debug configuration.
Click OK. The DB2 and IMS Debug Configuration preferences window opens. Use this window to define connection settings.
The Debug Configurations wizard cannot update the debug profile data set.
Ensure that you have write access to the debug profile data set and that it is not in use and try the operation again.
When you export a configuration file from a workspace to a configuration group, the workspace is bound to that group. All subsequent export requests from this workspace are exported to the same group.
No response is required.
Access to remote libraries requires access to the remote system on which they are located.
Connect to the remote system.
This error occurs when attempting to copy and paste from a local text file with a large record length to a new MVS sequential data set. Rational Developer for System z cannot allocate a data set with a record length that is longer than the maximum block size. The data set is not created.
No response is required.
An attempt was made to copy a binary file (such as a load module) from one remote system to another or between local and remote systems. This operation is not supported.
No response is required.
An attempt was made to copy a binary file (such as a load module) from one remote system to another or between local and remote systems. This operation is not supported.
No response is required.
The number of data sets in a filter exceeds the threshold set in the Default expansion page size for filters and data sets field of the MVS Files preferences page.
Click Yes to continue expanding the filter or No to cancel the operation. To change the warning threshold:
On the Add Include Library, Edit Include Library, Add Copy Library, or Edit Copy Library window, the remote system that is selected is not connected.
Connect to the remote system and try the operation again.
An attempt was made to open, browse, or view a data set with a block size of 0.
Modify the data set characteristics to specify a valid block size and try the operation again.
Remote files that are edited with an external editor cannot be saved to the remote system.
To edit a remote file and save the changes to the remote system, use an internal editor, such as the System z LPEX Editor, COBOL Editor, or PL/I Editor.
The JCL procedure lookup path contains a data set that is migrated. Migrated data sets are not accessible for JCL navigation.
To recall a migrated data set, select the data set name in the Remote Systems view and then select HRECALL from the menu.
A data set highlighted in the editor cannot be found by using the Navigate to data set action.
Verify the data set name and try the action again.
A JCL procedure name highlighted in the editor cannot be found by using the Open JCL Procedure action.
Verify that the libraries specified in the Include and procedure search libraries property are correct and that the member name is correct. Try the action again.
When you open a file in an editor, it checks for a property group associated with the file. Property groups contain settings that enable the editor the resolve dependencies, such as copybooks and include files. This message prompts you to either open the file without a property group or to create or associate a property group with the file.
To open the file without associating a property group, click OK. To create or associate a property group, click one of the following links:
If you choose to associate an existing property group, the file is opened after the association is made. If you choose to create a property group, you need to request the file open action again.
No action is required. For more information about submitting multiple jobs, see the related topics.
The remote system is configured to deny permission to work offline.
Consult your systems administrator if you have questions about offline permissions on a remote system.
Systems administrators have the ability to configure remote systems to deny permission to work offline. To determine if working offline is allowed on the remote system, you must be connected to the remote system before you request the Work Offline action.
Connect to the remote system and try the Work Offline action again.
Configuration groups are created and administered on the remote system. If a configuration group name contains invalid characters, then the configurations that it controls cannot be downloaded to the workstation.
Contact your systems administrator. For more information about configuration groups, see the Rational Developer for System z Host Configuration Reference (SC14-7290).
A partitioned data set member is tool large for the server to search.
Do one of the following actions:
A data set is tool large for the server to download.
Expand the server memory size. Specify a larger value for the Java maximum heap size in the rsed.envvars file on the server. For more information about this file, see the Rational Developer for System z Host Configuration Guide (SC23-7658).
This error occurs when you create or save a remote file that uses characters that are not supported by the host code page of the container.
Modify the host code page property of the remote container:
This error occurs when you create or save a local or remote file that uses characters that are not supported by the local code page of the container.
To modify the local code page property of a remote container:
To modify the local code page property of a local container:
An attempt to obtain the characteristics of the data set, such as DSN type, data set organization, or record format, failed. This error might be caused by a TSO command server error.
Try the operation again. For more information about this error, see the rsecomm.log and ffs*.log files on the remote system. For more information about these files, see Chapter 12, "Troubleshooting configuration problems," in the IBM Rational Developer for System z Host Configuration Reference (SC14-7290).
The stored procedure file in the Data Development project no longer contains the name of a valid source file on a valid MVS System.
A deployment operation was attempted, but you are not connected to an MVS system in the Remote Systems view.
Connect to the MVS system in the Remote Systems view and try the operation again.
The source file that is associated with the stored procedure is no longer available on the remote system. It might be in a different location on your MVS system or renamed to a different data set member name.
Delete the stored procedure from the Data Development project and re-create the stored procedure. If the source file is available on the remote system, copy the source file to the location of the default source file that was created by the Stored Procedure Creation Wizard.
The data set member that is associated with the stored procedure belongs to an MVS system in the Remote Systems Explorer with the name {0}. The system no longer exists.
Switch to the z/OS Projects perspective and define {0} as a z/OS system with the appropriate IP address.
You submitted a generate JCL request and specified the partitioned data set name indicated by {0} as the target data set for the generated JCL file. This data set is migrated and is not available.
In the Remote Systems view, select the partitioned data set and then select HRECALL from the menu.
an edit or deploy operation for a stored procedure was requested, but the MVS system that is associated with the stored procedure is not connected. The source file cannot be accessed.
in the Remote Systems Explorer, connect to the remote system. Try the operation again.
The stored procedure source is in a data set that is offline or migrated.
Contact your systems programmer to bring the volume online.
Whenever you save a file in the System z LPEX Editor, COBOL Editor, or PL/I Editor, it checks for any lines that exceed the record length limit. This warning opens when a line in the file exceeds the record length limit.
Click Yes to continue with the file save operation or No to return to the editor to fix the line in question. The editor positions the file at the line that exceeds the record length limit.
Whenever you save a file in the System z LPEX Editor, COBOL Editor, or PL/I Editor, it checks for any lines that exceed the record length limit. This warning opens when more than one line in the file exceeds the record length limit.
Click Yes to continue with the file save operation or No to return to the editor to fix the lines in question. The editor positions the file at the first line that exceeds the record length limit.
Rational Developer for System z has an autosave function that creates a backup copy of editor files on the local system. This warning indicates that the backup copy created by an autosave operation is based on an earlier copy of the source. The backup copy is opened in the editor.
Use File > Save As to save the backup to a different location and then use the compare tool to merge changes from the backup with the source.
Rational Developer for System z has an autosave function that creates a backup copy of editor files on the local system.
Click Yes to open the backup copy.
Rational Developer for System z has an autosave function that creates a backup copy of editor files on the local system. This warning indicates that a backup copy is created for a file that cannot be saved on the remote system.
No action is required.
A file was changed in another editor on the file system. Its contents no longer match the contents that are shown in the System z LPEX Editor.
Click Yes to update the contents in the System z LPEX Editor. Click No to keep the current contents of the editor. If you save the file without refreshing the contents, the changes that are made in the other editor are lost.
These messages pertain to the Job Entry System (JES) Job Monitor in Rational Developer for System z.
This message displays as a result of the Open from line action in the Remote Systems view. It shows the number of lines in the currently selected job output. It also prompts you to enter the starting line and the number of lines of the job output to display.
Type the starting line number in the Retrieve output starting at line field and the number of lines to display in the Number of lines to retrieve field and click OK. To display 100 lines of output that start at line 500, for example, type 500 in the Retrieve output starting at line field and 100 in the Number of lines to retrieve field and click OK.
This message displays when you request to open job output for a job whose number of lines exceeds the Max Number of Lines to Download setting in the JES preferences. It prompts you to specify how you want to open the output.
You can choose from the following two options for displaying job output:
Rational Developer for System z was unable to establish a connection to JES on the port number shown on the remote system (host) shown.
You are not authorized to do the requested action for the job number shown.
Verify that you selected the correct job ID. Select a job that you are authorized to do the action on and try again.
A Cancel action was issued for the job ID shown.
No action is required.
A Cancel action was issued for the job ID shown, but the job is complete.
No action is required.
The Job class field on the New JES Job Filter window is required, but this field is empty.
Specify a value in the Job class field.
A Hold action was issued for the job ID shown.
No action is required.
A Refresh Status action was issued for the selected job, but no information is available. The job might be complete.
No action is required.
A filter string entered into the Retrieve Job window resulted in no matches.
Enter another filter string and try again.
An Open action for the job ID shown failed because the job produced no output or is not yet complete.
Wait for the job to complete or select another job and try again.
The Job output class field on the New JES Job Filter window is required, but this field is empty.
Specify a value in the Job output class field.
The Job 0wner field on the New JES Job Filter window is required, but this field is empty or the value specified is not valid.
Specify a value in the Job owner field. To specify the user ID with which you logged in to the remote system, specify &USERID.
The Job name prefix field on the New JES Job Filter window is required, but this field is empty.
Specify a value in the Job name prefix field.
A Print action was issued for the job ID shown.
No action is required.
A Purge action was issued for the job ID shown.
No action is required.
A Release action was issued for the job ID shown.
No action is required.
A Restart action was issued for the job ID shown.
No action is required.
The Job status field on the New JES Job Filter window is required, but this field is empty.
Specify a value in the Job status field.
An attempt to log on to the JES subsystem failed because the password specified is incorrect.
Specify a different password and try again.
The value specified in the Max Number of Lines to Download field of the Properties for JES window is invalid.
Specify a value 1 - 2147483647.
Your password for the remote system to which you are trying to connect expired.
Enter a new password when prompted. If you are not able to reset your password, contact your system administrator.
The password entered does not match the security requirements of your site.
Consult with your system administrator to obtain valid password requirements and try again.
The value specified in the JES Job Monitor Port field of the Properties for JES window is invalid.
Consult your system administrator for the correct port number and try again.
The Job Monitor server and the RSE JES Miner were unable to negotiate an acceptable command protocol level.
Either the Job Monitor server (load module FEJJMON) or the RSE JES Miner (jesminers.jar) is not at the latest level. Make sure that you correctly installed these components.
A RACF error occurred while attempting to log on to the remote system.
Contact your system administrator.
The connection to the remote system ended because of inactivity.
Connect to the remote system again.
The Job Monitor server (JMON) attempted to allocate a code page converter, but the allocation failed.
Make sure that enough memory is available to the Job Monitor server (JMON).
The host code page cannot be set to the value specified in the system code page mapping.
Check that the JMON job is running on the host, and that it is at the correct level.
These messages pertain to the common program analysis tools for deep program analysis of COBOL and .PL/I code.
The Source > Identify Unreachable Code action was requested, but the file contains no unreachable code.
No action is required.
The Open Program Control Flow function was requested in the COBOL Editor or System z LPEX Editor. This function uses an internal COBOL parser to analyze program control flow in a source file. Either the analysis cannot be completed because of syntax errors in the source file, or the analysis is still in progress.
Check for syntax errors in the file. Correct the errors, and try the operation again.
An internal error occurred in the Program Control Flow diagram.
Try the operation again. If the problem persists, contact IBM Software Support.
An internal error occurred during a request to open the Program Control Flow view.
Try the operation again. If the problem persists, contact IBM Software Support.
An internal error occurred during an Identify Unreachable Code request
Try the operation again. If the problem persists, contact IBM Software Support.
Because the Identify Unreachable Code feature uses a static analysis of the program source to identify potential dead code, it is not a reflection of the actual execution path.
Before you delete any code, verify that the code is correctly identified as unreachable.
This message is displayed each time that you use the Identify Unreachable Code function. To prevent this message from being displayed, click Do not show this message again.
The Identify Unreachable Code function was requested in the COBOL Editor or System z LPEX Editor. This function uses an internal COBOL parser to analyze a source file. The analysis cannot be completed because of syntax errors in the source file.
Check for syntax errors in the file. Correct the errors, and try the operation again.
An internal error occurred during a request to show the source file in the Data Elements view.
An internal error occurred in the Program Control Flow diagram.
Try the operation again. If the problem persists, contact IBM Software Support.
The program control flow diagram does not display control flow nodes for control transfers that are generated by the following statements:
Use the Show In > Program Control Flow function in programs that do not contain these statements.
The Identify Unreachable Code function has several restrictions:
Use the Identify Unreachable Code function in programs that do not contain these statements.
These are the messages that pertain to the MFS Screen Designer (MFS Map Editor) in Rational Developer for System z.
The input is not valid.
Remove the invalid input, and provide valid input.
The initial value that was provided is not valid.
Remove the invalid initial value, and provide a valid initial value.
The row value in the definition of a new MFS Device field was left null.
Provide a row value when defining a new MVS Device field.
The selected position is not within the map boundaries.
Select a position that is within the map boundaries.
You must define at least one column.
Define one or more columns.
The group name entered is too long/short.
Enter a shorter/longer group name.
A syntax error in the source caused an error.
Open the Source Page and modify the source so that the error is resolved.
The specified name is either invalid or empty.
Specify a valid name.
The specified name is either invalid or empty.
Specify a valid name.
The location for the destination of a process is not specified.
Provide the destination location for the process.
The file name is required to perform the process.
Specify a valid file name.
The file extension is not correct.
Change the file extension to mfs.
The device format name is not defined or not correct.
Enter a valid device format name.
The device name is missing.
Enter a valid device format name.
The message definition name is not defined or not correct.
Enter a valid message definition name.
The message definition name is missing.
Enter a valid message definition name.
A file name cannot be null.
Specify a file name that is not null.
The file name used is not correct.
Change the file name.
The file name entered is already in use.
Enter a different file name.
Table does not have a defined column.
Select a valid column or insert a column into the table.
Size of insert is greater than table width..
Insert a smaller selection.
The width value is not valid.
Enter a valid value in the range of 1-120.
The features value is missing.
Enter a valid features value.
The exit value i snot defined or not correct.
Enter a valid exit number value.
The exit vector value is missing.
Enter a valid exit vector value.
The literal value is over 255 characters.
Enter a literal value of less than 255 characters.
An extended attribute value is not in the range 1-10.
Specify an extended attribute value in the range 1-10.
The length of the value does not equal the field length.
Enter a valid length value.
The length of the value does not equal the field length.
Enter a valid length value.
You must define at least one row.
Define one or more rows.
You must define at least one column.
Define one or more columns.
The entry used is not correct.
Change or delete the field position value.
The entry is not correct.
Change or delete the offset value.
The entry used is not correct.
Change or delete the division name value.
The entry used is not correct.
Change or delete the PAGE value.
The entry used is not correct.
Change and delete the Device Field value.
The COPY keyword is not supported.
Remove any instance of the COPY keyword.
The statement is a read-only statement and cannot be modified.
No action required.
The path to the field is not valid or the file name is not valid.
Verify both the path to the file and the file name.
An error occurred that kept the file from opening.
This message is the header to additional messages. See the documentation for the additional message.
The character you entered is not allowed at the indicated location.
Change or delete the character.
A parse error was found at the indicated location.
Change or delete the parse statement.
A lexical error was found at the indicated location.
Change or delete the character.
The location that is selected is not valid.
Select a valid location.
The field name that is entered is not valid.
Enter a valid field name.
The requested copybook file was created successfully.
No action required.
The requested copy book file was created successfully.
No action required.
A file name was specified that is not valid.
Specify a valid file name.
The EGCS value that was provided does not fall within the range X'40' and X'FE'.
Change the EGCS value so that it falls within the range X'40' and X'FE'.
The Programmed Symbol value range that was provided does not fall within the valid range of X'40' and X'FE'.
Change the Programmed Symbol value range so that it falls within the range of X'40' to X'FE'.
The FILL value that is specified violates the valid format.
Replace the specified fill value with a correctly formatted hex value, for example FILL X'00'.
The FILL value that is specified violates the valid format.
Replace the specified fill value with a correctly formatted character, for example FILL C'c'.
Names in MFS must be unique, and the name that is specified is not unique.
Modify the name that you entered to be unique.
A physical page was attempted to be created on a device page that already had a single physical page and did not specify the MULT=YES attribute.
To specify that the device page can accept multiple physical pages, select the device page in the outline view. In the properties view, mark the Multiple physical pages check box. The MULT=YES attribute is added to the device page in the source and physical pages can be added without error.
The file that is selected as the target for the created MFS message is not a correctly formatted MFS file.
Select a file that has a MFS extension and contains no parse errors when opened with the MFS editor.
The file that is selected as the target for the MFS message creation contains syntax errors. Syntax errors in the MFS source prevent the MFS message from being appended to the file.
Open the file in the MFS editor, view the source page, and correct any syntax errors. After you correct any syntax errors, save the file and try creating the MFS message again.
A field is modified with new a new location that, if placed, will overlap with an existing field in the specified physical page. This overlap can happen when the row, column, or physical page attributes of a field are updated.
Correct the position attribute, or attributes, that causes the overlap.
The following messages pertain to generating source code in Rational Developer for System z.
The specified container was not found.
Create the specified container, or specify another container.
The following messages pertain to Common Access Repository Manager (CARMA) Endevor in Rational Developer for System z.
The input type is an unsupported type for the CA Endevor Package Editor. The Endevor Package Editor requires any custom editor to implement org.eclipse.ui.IStorageEditorInput.
Change the input type to a type that is supported by the CA Endevor Package Editor. If you are working on a custom client, contact your client developer to investigate whether the package editor is implementing org.eclipse.ui.IStorageEditorInput.
The source file was not open and read successfully.
In the client, close the file and try again. If the problem persists, restart the workbench.
The file is not valid SCL and cannot be opened by the CA Endevor Package Editor.
If you believe that the file is valid SCL, open the file in the text editor by right-clicking the file and selecting Open With > Text Editor. Fix any errors before you open the files again in the Endevor Package Editor.
The Endevor search did not complete successfully.
Verify that the current version of the Endevor RAM is installed and running on the remote system.
Verify that you are connected to the remote system. If the problem persists, contact the system programmer.
The following messages pertain to the CICS Service Component Architecture (SCA) in Rational Developer for System z.
This message indicates an unexpected error.
Try the action again. If the error persists, contact IBM Software Support.
The New CICS Component Type wizard examines the program source and creates a component reference element for each occurrence of EXEC CICS INVOKE SERVICE or EXEC CICS INVOKE WEBSERVICE that is found. If the name of the service that is started by the EXEC CICS command cannot be determined because a data item is being used instead of a string literal, this warning is logged.
Examine the EXEC CICS command at the specified line and column numbers in the program source to determine a correct name to use for the newly created component reference. After you determine the value, update the component reference name by using the Properties view.
The default attributes for RDO bundles must be defined by your CICS system administrator.
Verify with your CICS system administrator that the default attributes for RDO bundles are defined. This task is described in the topic about the CICS administrative utility in the chapter that explains the Application Deployment Manager in the Rational Developer for System z Host Configuration Guide.
The resources in a bundle are packaged into an archive file for transfer to z/OS. After the transfer is complete, the archive is unpacked.
Check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
The resources in a bundle are packaged into an archive file for transfer to z/OS. After the transfer is complete, the archive is unpacked.
Review the results of the unpacking operation, check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
You selected to delete the contents of the remote bundle before deployment; however, an error occurred.
Verify that the remote folder exists and that the permissions are configured correctly, check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
The resources in a bundle are packaged into an archive file for transfer to z/OS.
Verify that a connection to the remote system exists, that the remote folder exists, and that the permissions are configured correctly.
No response was received from the remote shell after the unpack operation for the archive file that contains the bundle resources.
Verify that all the bundle resources exist in the remote folder.
The resources in a bundle are packaged into an archive file for transfer to z/OS. After the transfer is complete, the archive is unpacked.
Review the results of the unpacking operation.
The remote folder must exist before the bundle is transferred to z/OS.
Verify that the remote folder exists and that the permissions are configured correctly, check the error log for more details, and try the action again. If the error persists, contact IBM Software Support.
The attempt to verify the installation operation did not return a valid response.
Verify that the BUNDLE resource was installed.
The selected CICS system or region does not support BUNDLE resources. BUNDLE resources are supported in CICS TS version 4.1 and later.
Select a CICS system or region that supports BUNDLE resources.
This message indicates an unexpected error.
Try the action again. If the error persists, contact IBM Software Support.
This message indicates an unexpected error.
Try the action again. If the error persists, contact IBM Software Support.
Either the path name is incorrect or the file is missing.
Correct the path name or create the file that is referenced.
Either the path name is incorrect or the file is missing.
Correct the path name or create an appropriate file at the specified location.
The value of the call type attribute must be COMMAREA or CHANNEL.
Specify a value of either COMMAREA or CHANNEL.
You must specify a program attribute in a component's CICS Implementation properties.
Specify a program attribute in a component's CICS Implementation properties.
Policy sets are not supported for CICS SCA 1.0 resources.
Remove the policy set.
An intent is defined for the CICS SCA 1.0 resource.
Remove the intent from the CICS SCA 1.0 resources.
Properties are not supported for CICS SCA 1.0 resources.
Remove the property from the CICS SCA 1.0 resources.
The specified file exists in a particular project.
To overwrite the file in the project, click Yes. To keep the existing file, click No.
The project contains errors.
To deploy the project anyway, click Yes. Otherwise, click No.
The project contains warnings.
To deploy the project anyway, click Yes. Otherwise, click No.
The following messages pertain to the z/OS Automated Unit Testing Framework (zUnit) in Rational Developer for System z.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot locate the template file that is needed to generate a test case.
Ensure that the zUnit feature is installed correctly. The default location for the template file is com.ibm.etools.zunit.gen\template. Verify that the template file is in the default directory, and try to generate the test case again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot save the generated test-case file.
Ensure that you have write access to the target for the test-case program, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the generated test-case file.
Ensure that you have access to the target for the test-case program, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot open the generated test-case file.
Ensure that you have access to the target for the test-case program, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot correctly load the template file that is required to generate a test-case program.
Ensure that the zUnit feature is correctly installed, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot write to the generated test-case file.
Ensure that you have write access to the target for the test-case program, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the directory that is specified in the File container field of the wizard.
Ensure that you have write access to the target for the test-case program, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard generated an internal error.
Contact IBM Software Support.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot locate the template file that is required to generate a test case.
Ensure that the zUnit feature is installed correctly. The default location for the template file is com.ibm.etools.zunit.gen\template.
The test-case program that the z/OS Automated Unit Testing Framework (zUnit) test-case wizard generated by using the default template file has formatting errors.
Ensure that the zUnit feature is correctly installed, and try the operation again.
One of the tags that are needed to correctly generate a test case program was not found in the default template file.
Ensure that the zUnit feature is correctly installed, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the generated test-case file.
Ensure that you have write access to the target for the test-case program, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot create the data set member for the generated test-case file.
Ensure that you have write access to the target for the test-case program, and try the operation again.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot update the properties of the target data set for the generated test-case file.
Ensure that you have write access to the target for the test-case program, and try the operation again.
This error occurs when the z/OS Automated Unit Testing Framework (zUnit) test-case source-code generator throws an exception. The content of the exception is in the detail area of the error window.
For more information about responding to this error, see the error details.
The z/OS Automated Unit Testing Framework (zUnit) test-case wizard cannot obtain a lock on the data set member for the generated test-case file.
Ensure that the member is not open in another program or locked by another user, and try the operation again.
This error can occur when a remote member is modified with Interactive System Productivity Facility (ISPF) so that the local cache is out-of-date. The Rational Developer for System z client fails to update a property of the local cache that is overwritten.
Update or delete the local cache, and try the operation again.
This message indicates that a hyperlink on the user interface was clicked and the system has no information to display for that item.
No action is required.
The z/OS Automated Unit Testing Framework (zUnit) test runner configuration editor cannot save the configuration file.
Ensure that you have write access to the target for the configuration file, and try the operation again.
By clicking File > Save As in the z/OS Automated Unit Testing Framework (zUnit) Runner Configuration editor and Runner Results editor, you can create a copy of the current file on a local or remote file system. Loss of connectivity, storage constraints, or other conditions can cause the copy operation to fail. This message reports other messages that are received from the local or remote file system when the operation fails.
This message is normally accompanied by messages from the local or remote file system. Use the accompanying messages to determine the appropriate corrective actions. For example, when you attempt a Save As operation that targets a z/OS partitioned data set that is out of space, the CRZZI0197E and CRZZI0198E messages might be received. For help with resolving the problem, see the documentation for the accompanying messages.
The Run As Test Case and Run All As Test Case actions require certain options to be set in a property group. The property group that is associated with the resource does not include the z/OS Automated Unit Testing Framework (zUnit) category.
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a JES job to run the test runner on the remote system. zUnit then polls JES at varying intervals, 1-6 seconds, to check whether the job finished. If a general communication error occurs with the JES job monitor during job submission or polling, the zUnit Eclipse task is canceled and this message is issued.
If the error message returned by the JES job monitor indicates a communication error, such as java.net.SocketException: Connection reset, verify that the JES job monitor is running on the remote system.
To verify that you are connected to JES on the remote system:
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a Job Entry Subsystem (JES) job that runs on the remote system. The job submission failed. The most common cause is a bad or missing JOB card.
To verify that the property group that is associated with the resource includes the zUnit category, edit the property group, open the Categories page, and verify that z/OS Automated Unit Testing Framework (zUnit) is selected.
To edit the job card, open the JCL page of the property group and edit the job card in the JCL job card field.
When you request a test case, zUnit submits a JES job to run the test runner on the remote system. zUnit then polls JES at varying intervals, 1-6 seconds, to check whether the job finished. The job can no longer be found on the remote system. It might be purged by another user or process.
Inspect the z/OS system log (SYSLOG) or JES job monitor log on the remote system to determine why the JES job was purged.
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a JES job that runs on the remote system. If you cancel the test case operation either by clicking Cancel on the job submission window or by clicking Stop on the Progress view and the JES job is already submitted to the remote system, this warning message is displayed.
To cancel or purge the job on the remote system:
While you run a test case, the z/OS Automated Unit Testing Framework (zUnit) generates a configuration file and uploads it to the remote system. If the upload fails, this message reports the message that is received from the remote system.
Verify that the MVS data set or z/OS UNIX folder that is specified in the Runner configuration destination container field of the property group has sufficient space and that you have write access to it.
When you run a zUnit test case, the test runner generates a test result file and opens it in the Runner Results viewer. The test result file was not found on the remote system.
Verify that the MVS data set or z/OS UNIX folder that is specified on the zUnit page of the property group exists on the remote system, that it has sufficient space, and that you have write access to it. Verify that no other process or user is concurrently using the MVS data set or z/OS UNIX folder.
When you run a z/OS Automated Unit Testing Framework (zUnit) test case, zUnit submits a JES job that runs on the remote system and polls JES until the job finishes. If a JES job fails, this error is raised and the high-level cause is given in the return information: JCLERROR, ABENDED, CANCELED, or SECERROR.
To diagnose the failed job, inspect the return information and the output of the job on the remote system. If the return information is JCLERROR or SECERROR, verify that the value that is specified in JCL job card on the JCL Job Card and Data Set page of the property group category is correct and specifies user credentials that are required by your site.
When you request a test case, the z/OS Automated Unit Testing Framework (zUnit) submits a JES job that runs on the remote system. The test runner encountered a severe problem and the JES job ended with a return code higher than U0008.
Inspect the JES job to determine the cause of the error. Search for messages that begin with the prefix AZU, which are issued by the test runner, for example AZU0006S.
By default, the test runner does not generate a Language Environment® memory dump if it can consume the exception that caused the severe error. To cause a limited memory dump to be generated along with detailed English-only tracing, select the Enable runner trace output option in the zUnit property group category.
If the test runner generated a result file, discard the file because the test results are not reliable.
When you run a test case by using the Run As Test Case or Run All As Test Case action, zUnit generates a runner configuration file and starts an Eclipse task that submits the test runner job. A unique ID is included in the runner configuration file. This ID is also included in the runner result file for the job. zUnit verifies that the runner configuration file and the runner result file are a matched pair because the runner result file is not created by the test runner until the run finishes. To ensure that the runner configuration file and runner result file are a matched pair, zUnit saves the value of the runner configuration ID attribute before it uploads the runner configuration file to the remote system. When zUnit opens the runner result file, it compares the value of the runner result ID attribute to the value of the runner configuration ID attribute. If the IDs do not match, the zUnit Eclipse task is canceled.
This error most likely occurs when multiple Run As Test Case or Run All As Test Case actions are started concurrently and the names of the runner result files for each task are not unique.
To prevent this error, specify unique runner result file names for each concurrent action instance, for example USER.AZURES(RUN01) and USER.AZURES(RUN02) or /u/zunit/result/run01.azures and /u/zunit/result/run02.azures.
These are the messages that pertain to Code Review for COBOL and Code Review for PL/I.
Verify that other program is using the COBOL source code file, and then try running the code review again.
Verify that the COBOL source code file does not contain any syntax errors, and then try running the code review again.
Verify that no other program is using the launch configuration file. Restart the product and accept the push-to-client updates if prompted.
Verify that no other program is using the launch configuration files. Restart the product and accept any push-to-client updates if prompted.
Verify that no other program is using the launch configuration files. Then try exporting the launch configuration files again.
Verify that no other program is using the launch configuration files. Restart the product and accept any push-to-client updates if prompted.
Verify that no other program is using files in the local workspace, then try running the code review again.
Verify that no other program is using the launch configuration file. Restart the product and accept any push-to-client updates if prompted.
Restart the product. If the problem persists, contact your system administrator.
The code review program detected syntax errors in the specified COBOL source code files.
Verify that no other program is using the PL/I source code file, and then try running the code review again.
Verify that the PL/I source code file does not contain any syntax errors, and then try running the code review again.
Verify that the program does not contain unresolved references. Verify that all the required copy books are present. Then try running the code review again.
These are the messages that pertain to TPF Toolkit Core.
These are the messages that pertain to TPF Toolkit Connection Manager.
These are the messages that pertain to TPF Toolkit Utilities.
This is a sample validation message.
No user response is required.
These messages pertain to the zSeries Utility.
This is a sample validation message.
No user response is required.
The remote system is unknown.
Verify that the host name is correct and that the host is available.
The remote system sent the message that is displayed.
Verify that the host is available and that the host name and port number are correct.
The connection failed because the host name or user ID is unknown.
Verify that the host name and user ID are correct and available.
The entered password for user {1} for the {2} host is incorrect.
Verify that the password for the specified user ID is correct.
The Remote System Explorer is starting with the SSH proxy.
No user response is required.
Secure Shell key authentication could not be completed. A password is required to establish the SSH session and exchange public keys so that the next key authentication request can be completed.
Enter the password to exchange keys and continue.
The provided password is incorrect.
Enter the correct password for authentication.
An SSH connection does not exist at the specified port.
Verify that the host system has an SSH server running at the specified port.
A Secure Shell server on the specified host at the specified port could not be found.
Very that the host system has an SSH server running at the specified port.
The version of SSH server that was found is not compatible with TPF Toolkit.
Check the version of the SSH server that is running on the host. TPF Toolkit requires the SSH server to be compliant with OpenSSH 3.4 or later.
Try your request again. If the connection fails again, obtain a trace by following the instructions in the information center, and analyze the output in the TPF_Toolkit_installaton_directory\eclipse\workspace\.metadata\ssh.log file.
If you are using password authentication, an incorrect user ID or password was used to access the system. If you are using key authentication, an invalid key or user ID was used.
Correct the user ID or password, and try your request
again.
If you use key authentication, correct the user
ID, delete the TPF_Toolkit_installaton_directory\eclipse\workspace\.metadata\id_dsa file,
and try your request again.
Try your request again. If the connection fails again, obtain a trace by using the instructions in the information center, and analyze the output in the TPF_Toolkit_installaton_directory\eclipse\workspace\.metadata\ssh.log file.
An error was encountered when disconnecting from the remote system.
Try to disconnect again. If disconnection attempt fails again, contact IBM Software Support.
The name of a remote system is not specified.
Specify the name of a remote system.
A system that already exists has been specified. You must specified an unused system.
Specify another system.
This document contains information about the host and runtime messages for Rational Developer for System z.
Most host and runtime message IDs inRational Developer for System z have the format prefixnnnnL, where prefix is a prefix such as CRAZ or FEK, nnnn is a message number unique to that message, and L is the message level. The message level can have values S for severe errors, E for error, W for warning, and I for informational.
For additional information on theRational Developer for System z host messages, see the product information center (http://publib.boulder.ibm.com/infocenter/ratdevz/v8r0/index.jsp?topic=/com.ibm.etools.rdz.messages.doc/reference/rdzmesgs.html).
These host messages pertain to the zUnit component of Rational Developer for System z.
zUnit uses the XML Toolkit for z/OS XML Parser, C++ Edition, to parse the test runner configuration XML file. Errors that are produced by the XML parser are detected by zUnit and converted to Language Environment conditions.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1.
Look up the ERROR-TEXT error message in the XML System Services User's Guide and Reference to diagnose and correct the problem.
zUnit uses the XL C/C++ dlopen and dlsym library functions to load zUnit test case modules. The dlopen library function loads the test case module into memory. The dlsym library function locates an entry point whose name matches the test case module name.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 2.
Verify these items:
The following options are expected:
zUnit uses the XL C/C++ dlopen and dlsym library functions to load zUnit test case modules. The dlopen library function loads the test case module into memory. The dlsym library function locates the entry point whose name matches the test case module name.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 3.
Verify these items:
The following options are expected:
The supplied test runner configuration XML file was successfully parsed, but no valid RunnerConfiguration/testCase elements were found.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 4.
Add at least one element with XPath RunnerConfiguration/testCase to the test runner configuration XML file, and start the test runner again. Ensure that each RunnerConfiguration/testCase element contains a RunnerConfiguration/testCase/@moduleName attribute.
The test runner successfully called an entry point in the test case module MODULE-NAME, whose name matches MODULE-NAME, to allow for test case initialization. Either the AZUTCINI API was not started in the entry point or the call failed.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 5.
Ensure that a call to the AZUTCINI API exists in the entry point whose name matches MODULE-NAME. If a call to the AZUTCINI API exists, check for an instance of the AZU1000S message to determine whether incorrect parameters were supplied to AZUTCINI.
zUnit uses the XML Toolkit for z/OS DOM implementation, C++ Edition, to model and generate the test runner results XML file. Exceptions that the DOM implementation throws are caught by zUnit and converted to Language Environment conditions.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 6.
Look up the error message ERROR-TEXT in the XML Toolkit for z/OS User's Guide to diagnose and correct the problem.
An API named API-NAME detected that the pointer value supplied in a parameter named PARM-NAME was invalid.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1000.
Assign a valid pointer value to the PARM-NAME parameter before you call the API-NAME API.
An API named API-NAME detected that the value given in PARM-VALUE is not valid or is out of range for the parameter named PARM-NAME.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1001.
Assign a valid value to the PARM-NAME parameter.
A test named TEST-NAME failed in the test case module named MODULE-NAME because of a call to the AZUASTFA assertion API. The test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1002.
Modify the TEST-NAME test and run the MODULE-NAME test case again. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the version that you intended to run.
A test named TEST-NAME started the AZUASTFM assertion API in a test case module named MODULE-NAME. The text USER-TEXT was supplied on the call to the AZUASTFM API. The test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1003.
Modify the TEST-NAME test and run the MODULE-NAME test case module again. Use the UUID to ensure that the test case module that was located by using the standard MVS search order is the most recent version or the version that you intended to run.
A test named TEST-NAME encountered an unexpected error (for example, SOC4) in a test case module named MODULE-NAME. The text of the error is given as ERROR-TEXT. The test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1004.
Modify the TEST-NAME test and run the MODULE-NAME test case module again. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
A test case module named MODULE-NAME failed because at least one of its test members failed because of an assertion or an unexpected error. This test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1005.
Modify the tests in the MODULE-NAME test case module and run the test case module again. At least one instance of message AZU1002S, AZU1003S, or AZU1004S is issued before this message. See the instances of AZU1002S, AZU1003S, or AZU1004S that are displayed before this message to determine which tests failed within the test case module. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
A test with name TEST-NAME was previously added to the test case module named MODULE-NAME in a prior call to the AZUTCINI API.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1006.
Supply a unique name for each test within a test case module when you call the AZUTCINI API. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
A test with entry address ENTRY-ADDR was previously added to the test case module named MODULE-NAME in a prior call to the AZUTCINI API.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1007.
Supply the address of an entry that was not already referenced in a prior call to the AZUTCINI API. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
A duplicate attempt to initialize a test case module failed. The test case token that is supplied to the AZUTCINI API indicates that the test case module MODULE-NAME was successfully initialized on a previous call to the API.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1008.
Correct the test case module so that it does not call the AZUTCINI API multiple times. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
A test case module named MODULE-NAME did not add any tests by using the AZUTCADD API when the ADDTESTS entry was called by the test runner. This test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1009.
Modify the MODULE-NAME test case module to add at least one test when the test runner calls the ADDTESTS entry. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
A test case module named MODULE-NAME encountered an unexpected error outside of a test entry, possibly in the ADDTESTS, SETUP, or TEARDOWN entries. This test case module set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization,
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1010.
Check for logic errors in the ADDTESTS, SETUP, and TEARDOWN entries. Check the entry whose name matches MODULE-NAME (the entry that is expected to call the AZUTCINI API) for logic errors. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the most recent version or the version that you intended to run.
An API named API-NAME encountered an internal error. This error can occur when an interface mismatch exists between the calling program and the API; for example, a by-value parameter that is accidentally passed by-reference.
The system signals a Language Environment exception with a facility ID of AZU, a severity of 3, and a message number of 1011.
Check that all required parameters are passed to the API by the calling program. Confirm that by-value parameters are passed by-value and that by-reference parameters are passed by-reference.
These messages pertain to the SCLM Development Toolkit in Rational Developer for System z.
An attempt to write the client parameter input to a temporary data set has failed.
Review the operations log to further determine any errors.
Indicates which function or operation request failed.
Review additional error messages and the operations log to determine error.
The ISPF/SCLM session has failed to initialize. Processing is terminated.
Review additional error messages and the operations log to determine error.
This is an additional error message to indicate a reason for ISPF/SCLM initialization failure.
The Systems programmer should review the ISPF.conf configuration file in the directory pointed to by CGI_ISPCONF in rsed.envvars to determine the correct ISPF data set allocations have been set.
The SCLM Developer Toolkit Loadlib data set may not be APF-authorized, resulting in ISPF/SCLM initialization failure.
The Systems programmer should ensure that the Loadlib is APF-authorized or that no non-APF authorized data sets have been included in the STEPLIB configured in rsed.envvars.
An ISPF/SCLM internal error has caused the session to terminate. The function request is cancelled.
Review the operations log to further determine any errors.
Review the Client operations log for further messages or error analysis.
To review the operations log, right click in the SCLM View and select Operations Log.
ISPF.conf should be located in the directory that is specified by CGI_ISPCONF in rsed.envvars.
The Systems Programmer should check the specified directory to ensure ISPF.conf exists and the user has read access to it.
Configuration files such as ISPF.conf should be located in the directory specified by CGI_ISPCONF in rsed.envvars.
The Systems Programmer should check the specified directory to ensure ISPF.conf exists and the user has read access to it.
Two concurrent sessions have been initiated and are using the same ISPF profile data set.
Check that another session is not running concurrently and preventing this session to establish.
An error in one of the ISPF data set allocations. Specific allocation error messages follow.
The Systems Programmer should check ISPF.conf to ensure valid ISPF DD names and correct ISPF data sets.
The following data set could not be allocated to that DD name.
The Systems Programmer should review the DD and data set allocation (ISPF.conf).
An error in the ISPF data set allocations has occurred.
The Systems Programmer should check ISPF.conf to ensure valid ISPF DD names and correct ISPF data sets.
EDIT processing has been cancelled due to an error.
Review additional error messages and the operations log to determine error.
The group selected is not valid because it does not reside in the user's development hierarchy.
Choose a valid group or operate from a different development group.
An error has occurred in locating a valid data set for that particular project/group/type.
The SCLM administrator should check that a valid data set exists for that project/group/type.
An error has occurred in EDIT/BROWSE and the function is cancelled.
Review additional error messages and the operations log to determine error.
The member can not be edited from the selected group because a member of the same name exists in the hierarchy at a lower group.
Select member from lower hierarchy group. You might also want to synchronize the IDE view with the SCLM repository, or repopulate the SCLM Developer View or SCLM Explorer View.
Additional message indicating which member should be selected for this operation.
Select recommended member and repeat function.
The user's repository view and SCLM are not synchronized.
Synchronize the IDE view with the SCLM repository, or repopulate the SCLM Developer View or SCLM Explorer View.
The repository view or IDE view are not synchronized with SCLM.
Re-populate project if explorer mode or developer mode are not synchronized. Otherwise re-synchronize IDE view.
The Add new member function has been cancelled due to errors.
Review additional error messages and the operations log to determine error.
An invalid SCLM operation has occurred as the member does not reside in the user's development group.
Select a valid member.
A valid SCLM member with text was not found.
None
The operation involves copying the member to the z/OS HFS. This operation failed.
The Systems programmer should review the operations log for further explanation of this error.
As part of the EDIT function a copy of the SCLM member to a temporary data set has failed.
Review additional error messages and the operations log for further information.
SCLM lock on member for edit failed. Member may already be locked for edit by another user.
Use the View SCLM status action to determine if member is locked for EDIT by another user.
Binary object type members of NON-EDIT are not eligible to be selected for EDIT. Function cancelled.
None
The operation involves copying the member to the z/OS HFS. This operation failed.
The Systems programmer should review the operations log for further explanation of this error.
An error has occurred in the translation from ASCII to EBCDIC when checking in a file.
Ensure the file to be checked in is not empty and contains no invalid characters. Otherwise the ASCII EBCDIC code pages used should be verified.
The member being checked in wasn't successfully copied into the MVS data set. The operation has failed.
The Systems programmer should review the operations log for further explanation of this error.
The SAVE function has failed.
Review additional error messages and the operations log to determine error.
The check-in function to SCLM was cancelled.
Review additional error messages and the operations log to determine reason.
Associated with the SAVE / CHECK-IN function where a member has to be SCLM locked or checked out first.
The user should lock or check-out the member first using the EDIT function.
The requested function internally performs an SCLM ACCTINFO request which has failed.
Review additional error messages and the operations log to determine error. Check the validity of the member.
The SAVE or Check-in operation was successful.
None.
Lists member details for the failed SAVE request.
Review additional error messages and the operations log to determine error.
The selected member was deleted successfully.
None.
Delete function failed for requested member.
Review additional error messages and the operations log to determine error.
The SCLM delete command has returned a non-zero return code.
Review additional error messages and the operations log to determine error.
Additional messaging may be contained in the operations log.
To review the operations log, right click and select operations log.
The SCLM unlock command on a cancel EDIT request has failed.
Review the SCLM status of the member.
A member previously locked for EDIT has been successfully unlocked.
None.
The temporary data set userid.SCLMDT.VCMISPF.IDnnnnnn containing the build parameters could not be allocated. Processing terminated.
The Systems programmer should review the operations log for additional error messages.
The temporary data set containing the build parameters was allocated but an error occurred while reading or the data set was empty.
The Systems programmer should review the operations log for further explanation of this error.
The specified Build message data set could not be allocated. Processing continued.
Review the Build messages data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
The specified Build report data set could not be allocated. Processing continued.
Review the Build report data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
The specified Build list data set could not be allocated. Processing continues.
Review the Build list data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
The specified Build exit data set could not be allocated. Processing continues.
Review the Build exit data set that was user specified from the Build request. Review MVS SYSLOG for any security violations.
The build request has failed.
Review additional error messages and the operations log to determine error.
The Build messages data set could not be read.
Review operations log for successful data set allocation.
The Build report data set could not be read.
Review operations log for successful data set allocation.
The Build listing data set could not be read.
Review operations log for successful data set allocation.
The Build J2EEBLD report data set could not be read.
Review operations log for successful data set allocation.
The SCLM batch skeletons FLMDSU$ FLMB$ could not be included. Build processing terminates.
Review message BWB00057.
Extended messaging from message BWB00056.
The Systems programmer should check that the base SCLM skeletons are allocated to ISPSLIB in the HFS configuration file ISPF.conf.
No BATCH Job information was returned or captured from TSO.
Review the MVS SYSLOG to determine if a batch job was submitted successfully or the Job resides in an SDSF queue.
The Promote function has been cancelled.
Review message BWB00016.
The temporary data set to receive SCLM messages USERID.SCLMDT.DTnnnn.FLMMSGS could not be allocated. Processing continues.
The Systems programmer should review the operations or MVS log for additional error messages.
The temporary data set userid.SCLMDT.VCMISPF.IDnnnnnn containing the promote parameters could not be allocated. Processing terminates.
The Systems programmer should review the operations log for additional error messages.
The temporary data set containing the promote parameters was allocated but an error occurred while reading or the data set was empty.
The Systems programmer should review the operations log for further explanation of this error.
The specified Promote message data set could not be allocated. Processing continues.
Review the Promote messages data set that was user specified from the promote request. Review MVS SYSLOG for any security violations.
The specified Promote report data set could not be allocated. Processing continues.
Review the Promote report data set that was user specified from the promote request. Review MVS SYSLOG for any security violations.
The specified Promote exit data set could not be allocated. Processing continues.
Review the Promote exit data set that was user specified from the promote request. Review MVS SYSLOG for any security violations.
The temporary authcode messages data set USERID.SCLMDT.AUTHMSG could not be allocated. Processing continues.
Review MVS SYSLOG for any security violations.
Promote failed. Possible reason is invalid Build map.
Review previous build request or view build map.
The Breeze flag is set, review additional Breeze messages in operations log.
None.
The Promote messages data set could not be read.
Review operations log for successful data set allocation.
Error reading promote report.
Review operations log for successful data set allocation.
Either Project Initialization has failed or the development group specified is invalid for the project.
Review any additional SCLM messages in the operation log and check your development group, Project and filter parameters.
Populate project by ARCHDEF will generate the request using DBUTIL and the build map for the ARCHDEF. If no build map exists (i.e. the ARCHDEF has not been built) then members will be read directly from the ARCHDEF.
None.
Additional to message BWB00072. As there is no ARCHDEF build map from which to generate the report, the populate will only report on members at the lowest group in the hierarchy.
If not acceptable then use a populate project filter other than ARCHDEF or build the ARCHDEF first to populate full list.
No project information was returned using the specified filters.
Review your filter parameters.
Information for message BWB00074.
None.
An INCLD statement for a member was found in the selected ARCHDEF but the member was not found in any group up the development hierarchy.
If the member is invalid, remove it from the ARCHDEF.
The update function failed as the member could not be locked for edit/update.
Review SCLM status of member.
Unable to obtain lock on member for EDIT or Update. Member may already be locked (checked out) by another user.
Review SCLM status of member.
Update is cancelled as member was not previously locked for edit.
Review SCLM status of member.
This is an informational message.
Retry function.
The function completed successfully.
None.
Unable to retrieve authcode on selected member.
Review SCLM status of member. Review any SCLM messages in operation log.
The update of authcode on the member has failed. Processing terminates.
Review SCLM status of member. Review any SCLM messages in operations log.
The VERINFO request failed with a return code > 8.
Review any SCLM messages in operations log.
This is an informational message.
No action is required.
A version recover request has failed with a return code > 0.
Review any SCLM messages in operations log.
A version delete request has failed with return code > 0.
Review any SCLM messages in operations log.
An error has occurred in the IGGCSI00 Catalog search program with a project list request.
The Systems programmer should review the operations and MVS log for further error messages. Retry request.
This is an informational message.
Review project filter request.
An error has occurred reading the translate table. Processing continues, but there will be errors in the longname to shortname retrieval and updates.
The Systems Programmer should verify correct translate table name: _SCLMDT_TRANTABLE variable in the rsed.envvars configuration file. Run the installation IVP to also verify installation.
A previous error with the Longname to shortname translation file has occurred.
The Systems programmer should review the operations log for further error messages.
The displayed HFS file contained the files to migrate could not be read. Migration terminates.
Review the operations log for further error messages.
Error on allocation of new temporary data set userid.vcm.temp.projinf DCB: SPACE(1,1,20) TRKS RECFM(FB) LRECL(40) BLKSIZE(27960) VIO
Review the MVS SYSLOG for additional messages for data set allocation failure.
Unable to allocate DISP=SHR to the data set Project.projdefs.load.
Determine the data set Project.projdefs.load exists, where project is the project name specified.
Unable to call ISPF/SCLM module ISRFLMGI for retrieving group information for project.
None.
Unable to allocate temporary data set for project group information retrieval.
Review the operations log for further error messages.
Unable to read allocated SCLMINFO temporary data set. No project information will be returned.
Review the operations log for further error messages.
No group information for selected project is returned due to function failure.
Review the operations log for further error messages.
The delete request was successful. Build map deleted.
None.
No Jobname was passed through in JOB status request with JOBID.
Retry with valid JOB Name specified.
No Jobname or Jobid details were passed. Function will report on all jobs starting with USERID as Jobname.
None.
No valid Jobname / Jobid was passed for Job output retrieval.
Retry with valid Jobname / Jobid.
The requested Batch job was not found on the SDSF queue.
Check on z/OS in SDSF if the batch job still resides on an output queue or has been purged.
Additional SCLM warning messages have been issued.
View additional SCLM messages in operations log.
Error on SCLMINFO call for project/Project definition.
Check Project and project definition are valid.
Extends message BWB00105.
Check Project and project definition are valid.
SCLMINFO request has returned return code 12.
Check Project and project definition are valid. Inform SCLM administrator of error.
Extends message BWB00107.
Reference message BWB00107.
SCLMINFO request has returned return code 16.
Check Project and project definition are valid. Inform SCLM administrator of error.
SCLMINFO request has returned return code 32.
Check Project and project definition are valid. Inform SCLM administrator of error.
The SCLM messages manual will give additional information on the SCLMINFO return codes.
Review the SCLM messages manual.
The SITE.conf file has not been tailored for use.
None.
The Temporary MIGRATE data set USERID.SCLMDT.VCMISPF.IDnnnnnn could not be allocated. Processing terminates.
The Systems programmer should review the operations log for additional error messages.
Error reading allocated parameter data set.
The Systems programmer should review the operations log for additional error messages.
Error in creating or locating specified directory in HFS which is used to process the current function.
The Systems programmer should review the operations log for additional error messages.
A copy of a member from an SCLM data set into a HFS directory has failed.
Check SCLM status of member. Review the operations log for additional error messages.
An error threshold of 5 bad member copies between SCLM and the HFS directory has occurred in the Java/J2ee build translators. Processing terminates.
Review the operations log for additional error messages. Rectify problem and retry function request.
Errors have occurred in the ASCII / EBCDIC codepage conversions.
Review the operations log for additional error messages.
An error has occurred in creating a Java JAR file. This function uses Java to JAR up a zip file for transferring files across the network.
Review the operations log for additional error messages. The Systems Programmer should ensure a valid Java path exists in rsed.envvars and check for space problems within the users WORKAREA directory.
An error occurred starting a Java™ command.
The Systems Programmer should ensure a valid java path exists in httpd.env for the HTTP server.
A failure has occurred with an SCLM DBUTIL request for producing a member list. Further error messages may be displayed.
Review the operations log for additional error messages.
The USER specified filter list has returned no project information.
Review your filter parameters and retry.
This is an informational message only.
None.
No files were found to be migrated.
If an error review the operations log for additional error messages.
The file to be stored is being stored with a language that does not allow long names but the file has a name that is not a valid host member name. Host member names must be characters or less.
If the file needs to be stored as a long language type i.e. converted to a short name then ensure the language type matches the LONGLANG keywords in TRANSLATE.conf (see the administrator).
An error occurred when translating a long file name to a short name. The short name is used by SCLM to store the file as a member of an SCLM library.
Review the operations log for further errors. Report this problem to the systems programmer or SCLM administrator.
Redundant message.
Ignore.
The error threshold of 5 shortname error conversions has been reached, the migrate process terminates.
Review the operations log for further errors. Report this problem to the systems programmer or SCLM administrator.
An attempt to migrate in a member was made where the member already exists in the group hierarchy and the force option was not used.
If needed, members can be force migrated by setting the 'force' flag on from the migrate panel. Warning: this is not advised because normal checkout/checkin processing should be used. Forced migration can cause members which are already in SCLM to be overwritten.
A copy of an SCLM member from the HFS to an SCLM data set has failed.
The Systems Programmer should check the output data set is valid and there are no space problems or security violations.
Informational: extends BWB00130.
Inform Systems Programmer of this message.
For a migrate or import the error threshold of 20 has been reached for copy failures from HFS to/from SCLM. Processing terminates.
Review the operations log for further errors. Report this problem to the systems programmer or SCLM administrator.
In Migrate processing an error occurred when reading the Messages data set. Processing continues but Migrate messages will not be included in the display output.
Review the operations log for additional error messages.
This is an informational message.
None.
This is an informational message.
None.
This is an informational message.
None.
Errors occurred with a number of files during migration processing and are listed here. Migration may have only partially succeeded for some files/members.
Review the operations log for additional error messages.
Migration messages have been written to this data set on z/OS for reference.
Review the migration data set if required.
An ARCHDEF was selected which was to be updated with the names of the members that were migrated, but the ARCHDEF could not be updated.
Check the ARCHDEF selected within SCLM for errors and review the operations log for further errors. Archdef may have to be manually updated with members if required.
Informational: The ARCHDEF was successfully updated with the names of the members that were migrated.
None.
The ARCHDEF member to be updated with migrating members already exists but the read has failed. Migration continues without ARCHDEF update.
Check the validity of the selected ARCHDEF. Archdef may have to be manually updated with members if required.
An ARCHDEF was selected to add migrating members to but the SCLM update to the ARCHDEF has failed. Bad allocation of ARCHDEF member at the development level.
Check the ARCHDEF selected within SCLM for errors and review the operations log for further errors. Archdef may have to be manually updated with members if required.
An error has occurred in unzipping a file using the Java JAR command. This function uses Java to UNJAR a zip file for transferring files across the network.
Review the operations log for additional error messages. The Systems Programmer should ensure a valid Java path exists in rsed.envvars and check for space problems within the user's WORKAREA directory.
The variable _SCLMDT_CONF_HOME specified in the rsed.envvars file may not be correct. This Environment variable determines the directory path where the configuration files reside for SCLM Developer Toolkit.
Systems programmer should investigate the _SCLMDT_CONF_HOME setting in rsed.envvars.
This message is not valid for Rational Developer for z and should be ignored.
Ignore this message.
Files to be migrated are contained in a HFS listing file. An error occurred while reading this file and migration processing terminates.
Systems programmer should check HFS file permissions for specified user and available space.
An error has occurred during an ASCII to EBCDIC file conversion. DT uses the iconv routine within HFS to codepage convert.
Systems programmer should check ASCII/EBCDIC customization parameters in TRANSLATE.conf. Check file being converted for special characters or empty file.
Host file structure does not contain a '/' as first character.
Review operations log to view Host File name passed to transfer routine.
The direction keyword is not valid for file transfer. Valid direction keywords are TOHOST or FROMHOST.
Review operations log for direction keyword passed and retry.
The filetype keyword for transfer is not valid. Valid filetype is BINARY or TEXT.
Review operations log for filetype keyword passed and retry.
ZIP option (ZIP = yes) is only valid for transfer direction TOHOST.
Retry operation without ZIP flag set if transferring from host.
ZIP = YES has been set for transferring a file other than of filetype BINARY. This is not valid.
Retry operation without ZIP flag set if transferring text file.
Accompanies message BWB00130. Copy has failed.
Review that the file permissions on the HFS directories or Host file name are valid.
The host directory is part of the HOSTFILE name specified. The HFS directory does not exist.
Systems programmer should check the HFS directory name specified.
An unzip has failed on the transferred file. SCLM DT uses the Java JAR command to unzip (unjar) this file.
The Systems Programmer should ensure a valid Java path exists in rsed.envvars and check for space problems within the user's WORKAREA directory.
This is an informational message.
None.
The cleanup routine to delete HFS workarea files after operation has completed has failed.
Systems programmer should check listed file and delete/remove manually if desired.
This is an informational message.
Select DETAILS to view build messages, reports and listings.
This is an informational message.
Select DETAILS to view promote messages, reports and listings.
The temporary skeleton file that is used for creating the batch job could not be read: USERID.SCLMDT.DTSKEL. Migration processing terminates.
Review the operations log for additional error messages.
In version processing a temporary recovery data set: USERID.SCLMDT.FORMAT.DTnnnn could not be allocated.
Systems programmer should review the MVS log for any data set allocation failures.
In a Java or J2EE build an error has occurred running the ANT script in HFS. This may just be Java compile errors.
Review the ANT build listing returned in the operations log to resolve any build errors.
This is an informational message.
Review the listing.
A copy of a member from an MVS data set to a HFS file has failed. Build processing continues.
Review the operations log for further error messages.
During a checkout (lock) an SCLM member account record was created in the development group. The unlock or lock failure results in the account record being deleted.
None.
An add new member was attempted but the member already resides up the group hierarchy chain. Processing terminates.
None.
An error has occurred in translating the longname file to an SCLM host shortname. This is often the result if a error in the installation of the SCLM Developer Toolkit components on the host, or an inability to read the translation file (LSTRANS) at the host.
Review the operations log for further error messages.
A codepage translation error occurred when saving a file/member. Ensure the file saved was not an empty file.
Check that the file was not empty. Otherwise, review operations log for further error messages.
A member was selected to be migrated but already exists in the group hierarchy chain.
Use normal EDIT/checkout processing, otherwise use the migrate command with the force flag set. Warning: This is not advised, because previous versions of the member may be overwritten.
An error threshold of 5 members being migrated has resulted in codepage conversion errors. Migrate processing terminates.
Review the operations log to determine errors with migrated members.
There were no valid members selected to be migrated into SCLM. Processing terminates.
If this is an error then review the operations log for further error messages.
The promote has failed. Promote messages will be returned in the log or reside in the promote messages data set if specified in the request.
Review the failing messages.
For migrate and import the files requiring long/short name conversion are written to a temporary sequential data set DD LSTRNPRC of attributes SPACE(1,1) RECFM=VB LRECL=1036 UNIT=VIO. This data set could not be allocated. Processing terminates.
Systems Programmer should check the MVS SYSLOG for any data set allocation errors or violations.
A shortname longname translation has occurred calling the translate module FLMLSTRAN. Additional error messages will be displayed.
Review the operations log for additional error messages and reasons provided.
A previous error in retrieving longnames has occurred and any longnames associated with an SCLM host shortname will not be displayed in the project view.
Review the operations log for other error messages pertaining to translation services.
An EBCDIC to ASCII codepage translation error has occurred. Likely causes are unprintable special characters or an empty file.
View the member being translated. Special characters or null characters (X'00') may cause this error when browsing/editing a file.
Failure in allocating data set on z/OS host.
Review operations and MVS systems log for further error messages . Contact your SCLM administrator for assistance.
An SCLM DBUTIL report was run for this function call but failed to return any records.
Warning only - Review your filters or parameters in request.
The SCLM accounting record and build map have been deleted for that member at the requested group.
None. This is an informational message only.
Failure in allocating data set userid.SCLMDT.VCMISPF.IDnnnnnn on z/OS host. Function failed.
Review operations and MVS systems log for further error messages. Contact your SCLM administrator for assistance.
Failure in read of temporary data set userid.SCLMDT.VCMISPF.IDnnnnnn. Function failed.
Review operations and MVS systems log for further error messages. Contact your SCLM administrator for assistance.
The CLASS, JAR, WAR, or EAR specified in the request was not located in the SCLM project hierarchy.
Review your file name requested . Re-run the request.
The CLASS, JAR, WAR, or EAR specified in the request was not located in the SCLM project hierarchy.
Ask the System administrator to check in the z/OS Unix systems services that the directory specified exists. Also check that write access permissions on that data set for your userid are set.
Failure in trying to read the member $GLOBAL that should reside in SCLM type J2EEBLD.
Ensure a $GLOBAL member exists in the SCLM project hierarchy in SCLM type J2EEBLD. Contact your SCLM administrator for assistance.
One of the above property variables is not set in $GLOBAL. Function cancelled.
Check that all property variables are set and the format is correct. Re-run the request. Contact your SCLM administrator for assistance.
There was a failure on reading the J2EE build script member specified in Type J2EEBLD.
Review the operations log for further details on the build script. Ensure that build script which is referenced by the ARCHDEF keyword SINC exists in the SCLM project in type J2EEBLD. Contact your SCLM administrator for assistance.
The property variable SCLM_ARCHDEF is not set in the J2EE build script or the format is incorrect.
Review the operations log to read the J2EE build script mentioned. Ensure that property is set and re-run the function request.
The JAVA/J2EE build has failed in the ANT build step on z/OS.
Review the ANT listing which will list the compilation or build errors . Rectify project errors and re-run.
The property variable SCLM_ANTXML was not set in the build script or the format was wrong.
Ensure the variable is set. SCLM_ANTXML should reference a skeleton ANT XML member in type J2EEBLD.
An error occurred while copying the ANT XML member into the z/OS Unix file system for processing.
Review the operations log for further errors. This copy is part of the build process. Contact your SCLM administrator for assistance.
There was an error in reading the TRANSLATE.conf configuration file located in the SCLM DT CONFIGURATION directory in the z/OS Unix file system.
Ask the systems administrator to check that a valid TRANSLATE.conf exists at the configuration directory (by default /var/rdz/sclmdt/CONFIG ). Contact your SCLM administrator for assistance.
There was an error in copying SCLM source members into the z/OS Unix file system for processing.
Review the operations log to determine the members that failed. Ensure these members exist in SCLM . Review the MVS systems log for further error messages. Contact your SCLM administrator for assistance.
Errors occurred while processing an INCL ARCHDEF within the ARCHDEF.
Check with the SCLM administrator that the included ARCHDEF is valid. Review the operations log for further error messages.
Error occurred on an SCLM ACCTINFO function request on the member.
Ensure the member has a valid SCLM account record. It is possible the member may be corrupted. Contact your SCLM administrator for assistance.
The function was expecting either JAR_FILE_NAME, WAR_NAME, or EAR_NAME properties to be set in build script.
Check the nature of the project and ensure a valid property variable is set for that project in the build script.
Internal error in build process occurred while storing archive file information in an ISPF profile variable.
Review operations log for further error messages such as JAR, WAR or EAR was not created or other build failures. Contact your SCLM administrator for assistance.
The ARCHDEF translator J2EEOBJ could not locate a generated JAR WAR or EAR to store back into SCLM.
Review the operations log for other build failure messages. Contact your SCLM administrator for assistance.
Error encountered in copying build listing file into SCLM . Error occurred in ARCHDEF translator J2EEOBJ.
Review the operations log for other build failure messages. Contact your SCLM administrator for assistance.
There is an error in the copy of the generated archive object (JAR, WAR,EAR) from z/OS Unix file system into SCLM.
Review the operations log for other build failure messages. Contact your SCLM administrator for assistance.
An error occurred during the copy from SCLM of a class, JAR, WAR, or EAR into the classpath directory specified as part of the function request.
Review the operations log for other error messages. From the log determine the SCLM file and ensure the member is valid. Check that the destination classpath directory in the z/OS Unix Systems file system exists and write permissions are set. Contact your SCLM administrator for assistance.
An error occurred while copying the customized ANT script referenced by property SCLM_ANTXML from SCLM into the z/OS Unix Services file system in the ANTCOPY procedure of the build.
Review the operations log for further error messages. Ensure the member referenced by property SCLM_ANTXML in the build script exists in the SCLM hierarchy. Contact your SCLM administrator for assistance.
The selected member was not found in the users development group but retrieved from further up the group hierarchy in SCLM.
This is an informational message. The Messages or operations log should detail what group the member was retrieved from.
An INCL ARCHDEF was found inside the J2EE ARCHDEF which was not a valid J2EE ARCHDEF. This was determined not to be a valid JAVA/J2EE ARCHDEF because the SINC keyword was missing. Processing terminates.
Validate that the INCL ARCHDEF is a JAVA/J2EE ARCHDEF . Ensure the format of the ARCHDEF is correct (Valid SINC , LKED, & OUT1 keywords).
The member referenced by property variable SCLM_ANTXML in the JAVA/J2EE build script was not found in the SCLM hierarchy.
Ensure a valid member exists in the SCLM hierarchy and resides in SCLM type of J2EEBLD.
A change code verification user exit (CCVFY or VERCC) indicated that an invalid change code was entered for the operation.
Check the log for any messages the local user exit may have provided. If the problem is not visible from the messages returned by the user exit, contact your SCLM project administrator for assistance.
The user has initiated a DEPLOY in report mode only. Information on the Deploy script, destination, and selected options will be returned. No Deploy processing takes place.
None. This is an informational message only.
Error reading J2EE Deploy script member
Ensure the selected Deploy script exists and is valid in the SCLM hierarchy and resides in SCLM type J2EEBLD. Contact your SCLM administrator for assistance.
The EAR file was successfully deployed from the selected group.
None. This is an informational message only.
The Deploy of the selected EAR file has failed.
Review the operations log for further error details. Contact your SCLM administrator for assistance.
The Deploy listing is the listing output from the ANT deploy script.
Review the Deploy listing in the operations log for detailed information regarding success or failure of the deploy operation.
The Deploy of the selected EAR has been successful.
Review the messages or operations log for further information regarding the Deploy operation.
An error occurred while copying the dynamically customized deploy ANT script from SCLM into the z/OS Unix Services file system for processing.
Review the operations log for further error messages. Contact your SCLM administrator for assistance.
An error occurred while trying to allocate the short name / long name translate table in the deploy function.
Reason messages regarding this error will be found in the operations log. Either ensure variable TRANTABLE in $GLOBAL is set, or check the data set referenced by variable TRANTABLE is correct. Contact your SCLM administrator for assistance.
The catalog search routine failed to return any data sets on the user's requested data set filter.
Revise the data set filter used and re-run.
No members were returned from the data set using the selected member filter.
This is an informational message. If required, revise selected filters.
While trying to list members by filter from the selected data set, the Library managements services routines returned an error.
Review the Operations log for further error messages. Review your member filter and re-run. Contact your SCLM administrator for assistance.
Build security is on for this project, and the requesting userid does not have security access for this selected build request. Processing terminates.
Check with the SCLM security administrator.
Promote security is on for this project, and the requesting user ID does not have security access for this selected promote request. Processing terminates.
Check with the SCLM security administrator.
These host messages pertain to CRASTART in Rational Developer for System z.
This message shows the configuration file name from which CRASERV receives the commands to run.
No response is required.
This message shows the hhhh internal file number, which is associated with a reading of the CRASERV configuration file. The config handle is for diagnostic purposes only.
No response is required.
This message displays the standard command that is read from the CRASERV configuration file. This is a diagnostic message.
No response is required.
This message displays the dynamic allocation command that was read from the CRASERV configuration file. This is a diagnostic message.
No response is required.
This message displays the dddddddd value that CRASERV uses as a ddname.
If the ddname is not the same as is expected, verify that the correct ddname is specified in the CRASERV configuration file.
This message displays the program invocation command that was read from the CRASERV configuration file. This is a diagnostic message.
No response is required.
No response is required.
This message displays the program name (cccccccc) and parameters (p1 and p2) that CRASERV is about to run. This is a diagnostic message.
Verify that any variable substitutions are correct.
A CARMA user explicitly ended his or her connection.
No response is required.
A CARMA user's session timed out after inactivity.
No response is required.
A dynamic allocation was completed for the dsname data set by using a referback.
See the previous allocation statement for details about the referback.
A program started by CRASTART ended with an aaaaa return code, which might indicate a bbb abend code.
This might not indicate a problem, but if the started program did not complete correctly, diagnose the failing program by using the bbb abend code.
The content of this returned message comes from dynamic allocation (BPXWDYN) that CRASERV called.
Your response depends on the message contents.
This message shows the cccc return code from dynamic allocation (BPXWDYN) that CRASERV called.
Your response depends on the message contents.
These are the host messages that pertain to Application Deployment Manager (ADM) in Rational Developer for System z.
The messages in this section are not shown to you on a workstation. They exist only in the CICS log on the host system.
An error occurred while processing a web service request.
No user response is required.
See the CICS documentation for RESP and RESP2 codes of the GET CONTAINER service.
An error occurred while processing a web service request.
No user response is required.
See the CICS documentation for RESP and RESP2 codes of the PUT CONTAINER service.
An error occurred writing an HTTP header.
No user response is required.
See the CICS documentation for WEB WRITE to evaluate the RESP and RESP2 codes.
An error occurred writing an HTTP header.
No user response is required.
See the CICS documentation for WEB SEND to evaluate the RESP and RESP2 codes.
An error occurred writing an HTTP header.
No user response is required.
See the CICS documentation for LINK to evaluate the RESP and RESP2 codes.
An error occurred during an ASSIGN USERID() operation.
No user response is required.
See the CICS documentation for ASSIGN to evaluate the RESP and RESP2 codes.
An error occurred during a WEB EXTRACT operation.
No user response is required.
See the CICS documentation for WEB EXTRACT to evaluate the RESP and RESP2 codes.
An error occurred during a WEB READ operation.
No user response is required.
See the CICS documentation for WEB READ to evaluate the RESP and RESP2 codes.
The following host messages pertain to the Common Access Repository Manager (CARMA) in Rational Developer for System z.
The CARMA server encountered an unexpected internal error.
Confirm that the VSAM files are correct. If you modified the VSAM file, verify that you followed the guidelines in the CARMA Developer's Guide. Otherwise, verify that the files were created properly by using the directions in the Host Configuration Guide.
There are no RAMs defined that are associated with the current language.
Do one of the following actions:
The CARMA server was unable to open the CRADEF VSAM file for reading.
Have your systems programmer confirm that the file exists and is accessible from the user's account.
The CARMA server was unable to open the CRASTRS VSAM file for reading.
Have your systems programmer confirm that the file exists and is accessible from the user's account.
No RAMs are defined in the CRADEF configuration VSAM file on the remote system.
Do one of the following actions:
The CARMA server encountered an error while it was reading the CRADEF configuration file.
On the client, disconnect from CARMA, reconnect, and try again. If the problem persists, have your systems programmer verify that the file is accessible from the user's account.
The specified VSAM record in the CRADEF file is invalid.
Have your systems programmer correct the specified record. For more information about the correct record format, see the CARMA Developer's Guide.
The Rational Developer for System z client tried to connect to a RAM that is not defined on the remote system.
In the client, disconnect the CARMA connection and restart the workspace. Then, connect to the CARMA connection before you try any other actions. If the RAM you require is no longer listed, contact the systems programmer. The RAM might be removed or the RAM ID number might be changed.
The CARMA server was unable to load the RAM load module.
Have your systems programmer confirm the following information:
The RAM does not have the specified function.
If the function is required, recompile the RAM with the required function. For more information about developing a RAM, see the CARMA Developer's Guide.
The function was not called because the compiled RAM was not loaded by CARMA on the remote system.
Disconnect, reconnect, and try the action again. If you are using a custom remote system client, have your systems programmer verify that the initRAM function was called. If the problem persists, contact IBM Software Support.
The CRASTRS record that is specified is invalid.
Have your systems programmer or RAM developer, if you are using a custom RAM, verify that the CRASTRS VSAM file was properly created and that the specified record is correct.
The initCARMA function was not initialized.
Disconnect, reconnect, and try the action again. If you are using a custom remote system client, verify that the initCARMA function was called. If the problem persists, contact IBM Software Support.
CARMA did not successfully load the RAM list.
Disconnect, reconnect, and try the action again.
The CARMA address space is out of memory.
Have your systems programmer increase the memory that is allocated to CARMA address spaces.
The specified record is not defined in the CRASTRS file for the current locale.
This message is only a warning and does not require any action by the user.
If local specific strings are required for this record, then create an appropriate record in the CRASTRS file to provide the strings. A CRASTRS record can also be created to stop this warning from being written to the log files. Contact your systems programmer for these modifications.
If you are experiencing these errors while you are using the CA Endevor RAM, have your systems programmer install APAR PM56551 to fix this problem.
One or more parameters that are referenced by the specified action do not exist in the CRADEF VSAM file.
Have your RAM developer add any missing parameters to the CRADEF VSAM file.
One or more return types that are referenced by the specified action do not exist in the CRADEF VSAM file.
Have your RAM developer add any missing return types to the CRADEF VSAM file.
The CARMA server encountered an error while it was reading the CRASTRS configuration file.
On the client, disconnect from CARMA, reconnect, and try again. If the problem persists, have your systems programmer verify that the file is accessible from the user's account.
CARMA could not find a locale to use for this RAM.
Have your systems programmer or RAM developer confirm that the CRASTRS VSAM file was properly created. If the problem persists, do one of the following actions:
To change the language locale that is used by CARMA in the client:
CARMA was unable to find the CRAMSG VSAM file.
Have your systems programmer confirm that the file exists and is accessible from the users account.
The CARMA server encountered an error white it was reading the CRAMSG configuration file.
On the client, disconnect from CARMA, reconnect, and try again. If the problem persists, have your systems programmer verify that the file is accessible from the user's account.
Action 16 is the performAction function and is used to call custom actions in CARMA. The parameters that are associated with the called custom action are used as parameters to action 16. Providing your own custom parameters and returns interferes with the passing of the custom action that is called, and is not allowed.
Have the RAM developer remove the VSAM record for action 16 from CRADEF.
The type that is specified in the VSAM record is invalid.
Have your RAM developer update the VSAM record file to have one of the following types: "STRING", "DOUBLE", "LONG", or "INT."
The default value for the VSAM record is invalid.
Have your RAM developer ensure that the default value of the VSAM record matches the type and length that is specified for that record.
The RAM was unable to allocate memory.
Have your systems programmer increase the memory that is allocated to CARMA address spaces.
The TSO or ISPF library function is not available to the RAM.
Have your systems programmer confirm that the TSO and ISPF environments are properly started with the CARMA server. This process is explained in the Host Configuration Guide.
The member identifier that is provided to the RAM is incorrect or out of date. This problem can occur because the RAM was updated, or the RAM developer changed the way RAM IDs are represented to the CARMA server.
In the client, refresh the parent container and try the action again. If the problem persists, contact your RAM developer.
The RAM was unable to allocate memory.
Have your systems programmer increase the memory that is allocated to CARMA address spaces.
The RAM was unable to locate the requested number.
In the client, refresh the parent container and try again. If the problem persists, contact your RAM developer.
The RAM was unable to locate the requested instance.
In the client, refresh the RAM and try again. If the problem persists, contact the RAM developer.
The requested function is not supported by the RAM.
No action is required.
The function that was called expected a container as a parameter, and instead it received a member.
In the client, refresh the parent container and try the action again. If you are using a custom remote system client, notify the developer. If the problem persists, notify your RAM developer.
A parameter with an invalid value was passed to the action.
Confirm that all parameters contain the correct values and try the action again.
The target member was unable to update successfully.
In the client, disconnect, reconnect, and try the action again. If the problem persists, specify a different target member. If the problem still persists, contact your RAM developer.
The member was not successfully created.
In the client, attempt to do the following steps:
If the problem persists, contact your RAM developer.
The user is not authorized to do this action.
If you think this message is in error, disconnect, reconnect, and try the action again. If the problem persists, contact your RAM developer.
The RAM did not initialize.
In the client, disconnect from CARMA, reconnect, and try again. If you are still unable to do the action, have your systems programmer confirm that you have access to all files that are needed by the RAM. If you still experience problems, contact your RAM developer.
The RAM was unable to terminate properly.
No action is required.
The RAM is reporting that the resource is out of sync.
Refresh the parent container, and try the action again. If the problem persists, contact your RAM developer.
The file is locked and is most likely in use by another user or process.
You can wait until the file is freed and try again. Additionally, verify that you have the correct permissions to access the file.
The client is requesting a starting record number that does not exist. The client is calling the extractMember function, which retrieves chunks of records that start with a specific record number. In this case, the starting record number parameter is an invalid number that does not correspond with a record number.
In the client, attempt to open the file again. If the problem persists, contact your RAM developer. If you are using a custom remote system client, contact your client developer.
The target member has a record format that is unsupported by this RAM.
If you are using the sample RAMs provided with CARMA, work with members that have a record format of FB (fixed block) or VB (variable block).
LRECL is the length of the record. For the RAM putMember function, the client specifies the maximum length of the record. For the RAM createMember function, the length of the record of the created member is returned. For some reason, the length of the record is invalid.
Download a new copy of the file from the RAM, and try the action again. If the problem persists, contact your RAM developer.
The metadata key is the key in a key-value pair to a property of a CARMA resource. The requested key is not valid.
Refresh the properties of the CARMA resource. If the problem persists, contact the RAM developer.
The property value was unable to update. It is most likely read only.
No action is required.
The metadata value was invalid.
Try the operation again with a valid metadata value. If you are unsure of correct metadata values, contact your RAM developer.
The target metadata value is read-only and cannot be updated.
No action is required.
The RAM attempted to open a member that was empty.
If you believe that this message is in error, contact your RAM developer.
The repository instance was unable to expand because it was empty.
No action is required.
The container was unable to expand because it was empty.
No action is required.
An error occurred while the CARMA server was resetting the RAM.
In the client, disconnect and reconnect from CARMA and try the action again. If the problem persists, contact your RAM developer.
The RAM encountered an error it was trying to complete a Delete operation.
In the client, refresh the parent container to confirm that the delete was unsuccessful and try again.
Version is a previous view of the member in the CARMA Version History view. The target member or version is read-only.
No action is required.
The selected CARMA member does not support the Show History action. This message does not mean that the Show History action is disabled for all members.
No action is required.
The RAM encountered an error it was trying to access ISPF variables.
In the client, disconnect from CARMA, reconnect, and try again. If the problem persists, confirm that the ISPF system is properly set up at CARMA startup by reviewing the Host Configuration Guide.
The RAM encountered an error from an ISPF or LMF system call. This ISPF or LMF error message is provided by the RAM.
Check the response to the ISPF or LMF message that is included. Additionally, confirm that the ISPF or LMF system is properly set up at CARMA startup by reviewing the Host Configuration Guide.
The RAM was unable to access the log file.
Confirm that the CARMALOG is properly set up and that the user has access to the log file. If the problem persists, contact your RAM developer.
The RAM encountered an unexpected error.
In the client, disconnect from CARMA, reconnect, and try again. If the problem persists, contact your RAM developer.
The initRAM function call cannot be completed successfully, so the RAM was not loaded.
If the failed RAM is not required, no action is required. Otherwise, make sure that the VSAM configuration is correct and that the target RAM is accessible to the CARMA user. If you are using a custom RAM, make sure that the initRAM function is operating as expected. Check the CARMALOG or job spool for RAM initialization errors.
The terminateRAM function call returned an error from the RAM. If the RAM has state information that must be saved, this error can cause problems.
If you are using a non-custom RAM, no action is required . If you are using a custom RAM, check with your RAM developer to verify that this error is not a problem.
The action with the displayed action ID was disabled in the configuration VSAM file.
No action is required. You can find a list of action IDs in the Rational Developer for System z CARMA Developer's Guide.
The specified VSAM action record does not have a '|' character after the list of parameters, or has an empty parameter and return list. Earlier versions of CARMA required the separating character even if a return list was not specified.
No action is required.
The VSAM configuration erroneously tries to disable the performAction call, which is used to call custom actions. This action cannot be disabled in the VSAM configuration.
Have your RAM developer remove the record to disable action 16. Have your RAM developer confirm that the record to disable action 16 was not a typographical error and that the correct action IDs are disabled. A list of action IDs can be found in the Rational Developer for System z CARMA Developer's Guide.
The VSAM configuration erroneously tries to disable an action that does not exist. This situation can occur when you are using an earlier version of the CARMA remote system code, where the disabled action is not yet supported.
Have your RAM developer confirm that the correct action IDs are disabled.
A prompt was not supplied for the custom parameter. CARMA uses the custom parameter name in place of the prompt when it is asking for the custom parameter.
If you want a prompt, have your RAM developer add it to the VSAM record.
A description was not provided for the custom parameter.
No action is required, but if you want a description, have your RAM developer add it to the custom parameter.
No RAMs were found that use the specified locale. CARMA is using the default locale instead. A RAM is enabled only for the locales specified. This action allows RAM developers to release multiple versions for different locales, and display only one at a time to the user.
Specify a different locale under the CARMA connection properties. If you do not want to use RAMs for the default locale, have your RAM developer add support for your locale.
The specified function is not supported by the RAM. New functions added to the CARMA API can cause this condition. This condition is not an error.
No action is required. To remove this error message, have your RAM developer either implement the new functions or disable them in the configuration VSAM files.
These are the host messages that pertain to Code Review in Rational Developer for System z.
The messages in this section are not shown to you on a workstation. They exist only in the CICS log on the host system.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
The following host messages pertain to the Configuration Utility in Rational Developer for System z.
The Java location field does not contain a valid directory name, or the directory that is specified does not exist or does not contain /bin/java. This error might also occur if your TSO region size is too small and Java failed to run.
Correct the Java directory name or ensure that the TSO region size is 128M (SIZE=128000).
The directory name that is specified for Rational Developer for System z configuration files contains invalid syntax.
Correct the directory name.
The directory name that is specified for the installation does not exist.
Correct the directory name.
Unable to locate &RDZHLQ..SFEKLOAD. The high-level qualifier that is specified might be invalid.
Correct the high-level qualifier for the SFEKLOAD data set.
The data set name does not comply with z/OS standards.
Specify a valid data set name.
The DEFAULT user ID cannot be deleted.
No action is required. This message is for informational purposes only.
The DEFAULT user ID does not have a work flow.
Run the G Generate configuration jobs to create a work flow.
Valid prefix commands are C, D, F, L, N, S, or W.
Use a valid prefix command.
Valid prefix commands are C or V.
Use a valid prefix command.
Valid prefix commands are A, C, or E
Use a valid prefix command.
Valid prefix commands are N or S until configured.
Use a valid prefix command.
There is no log available for this work flow request because the request was not Actioned.
Action the work flow request.
This message is an internal warning.
If this message is issued with an error, contact IBM Software Support.
This message is for informational purposes only.
No action is required.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
This message is for informational purposes only.
No action is required.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
This message is for informational purposes only.
No action is required.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
The work flow routine run failed.
Review the work flow routine and any other associated error messages. Make the necessary corrections and run the routine again.
The work flow routine run failed.
Review the work flow routine and any other associated messages. Make the necessary corrections and run the routine again.
The work flow routine run failed.
Review the work flow routine and any other associated messages. Make the necessary corrections and run the routine again.
An internal error occurred.
Contact IBM Software Support.
The selected value is invalid.
Select a valid command.
The copy to the user directory failed.
Be sure that the user has write access to the specified directory or that there is available space in that directory.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
An internal error occurred.
Contact IBM Software Support.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is an internal warning.
If this message is issued with an error, contact IBM Software Support.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is issued with message FEK1024I. The specified directory could not be created.
The systems programmer must modify user authority so the user can create this directory.
This message is issued in conjunction with message FEK1023I. The specified directory could not be created.
The systems programmer must modify user authority so the user can create this directory.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
This message is for informational purposes only.
No action is required.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
This message is for informational purposes only.
No action is required.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
An internal error occurred.
Contact IBM Software Support.
This message is for informational purposes only.
No action is required.
This message is an internal warning.
If this message is issued with an error, contact IBM Software Support.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is issued with message FEKR124I. The specified directory could not be created.
The systems programmer must modify user authority so the user can create this directory.
This message is issued with message FEKR123I. The specified directory could not be created.
The systems programmer must modify user authority so the user can create this directory.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
The work flow routine run failed.
Review the work flow routine and any other associated messages. Correct the errors and run the routine again.
This message is for informational purposes only.
No action is required.
This message is for informational purposes only.
No action is required.
These host messages pertain to the RSE daemon or the RSE server in Rational Developer for System z.
This message is shown when the Rational Developer for System z daemon is started. It provides information about the addressing mode: 31 or 64.
No action is required.
This message indicates that the Rational Developer for System z daemon was started successfully and provides information about the daemon port for each Rational Developer for System z client user to log on.
No action is required.
The operator entered the Rational Developer for System z STOP command.
No action is required.
This message provides the JVM maximum heap size and the private address space size of the application.
No action is required.
This message provides information about the process ID with which the started server process is associated
No action is required.
This message is issued every time that it takes more than 30 seconds for the server process to start.
If the server process never starts, contact IBM Software Support.
This message provides the location of the active rsed.envvars file.
No action is required.
This message provides the location of rsedaemon.log and rseserver.log. When the enable.standard.log parameter is set to true in rsed.envvars, the standard out and error logs are also in the same directory.
No action is required.
This message provides the location of the active modules that are related to Rational Developer for System z.
No action is required.
The daemon port and timeout values are provided as a parameter of the JVM start command and must be digits.
Correct the daemon port and timeout value in the Rational Developer for System z started procedure.
This message provides the minimum level of the JRE that is required to run the Rational Developer for System z daemon.
Change the rsed.envvars file to use the JRE that the error message indicates.
The console command contains invalid arguments.
Enter the correct process ID for the command.
The z/OS UNIX System Services directory that is shown in the message is almost full.
Enlarge the size of the directory that is shown in the message.
The maximum number of Rational Developer for System z server processes was reached.
Increase the value that is specified for the maximum.threadpool.process parameter in the rsed.envvars file.
An error occurred when the Rational Developer for System z server process tried to send audit data to the Rational Developer for System z daemon process.
Contact IBM Software Support.
The TCP/IP socket failed for the reason code that is specified in the message.
Contact IBM Software Support.
The TCP/IP setsockopt call failed for the reason code that is specified in the message.
Contact IBM Software Support.
The TCP/IP bind call failed for the reason that is specified in the message.
Contact IBM Software Support.
The TCP/IP listen call failed for the reason that is specified in the message
Contact IBM Software Support.
The TCP/IP accept call failed for the reason that is specified in the message.
Contact IBM Software Support.
The TCP/IP write call failed for the reason that is specified in the message
Contact IBM Software Support.
The PIPE that is used between the Rational Developer for System z daemon and server processes failed for the reason that is specified in the message.
Contact IBM Software Support.
The socketpair call failed for the reason that is specified in the message.
Contact IBM Software Support.
The select call failed for the reason that is specified in the message.
Contact IBM Software Support.
The _console() call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_environment_open() system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_enum(GSK_PROTOCOL_SSLV2) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_enum(GSK_PROTOCOL_SSLV3) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_enum(GSK_PROTOCOL_TLSV1) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_buffer(GSK_KEYRING_FILE) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_buffer(GSK_KEYRING_PW) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_environment_init() system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_secure_socket_open() system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_numeric_value(GSK_FD) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_buffer(GSK_KEYRING_LABEL) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_enum(GSK_SESSION_TYPE) system SSL call failed for the reason code that is specified in the message.
Contact IBM Software Support.
The gsk_attribute_set_callback(GSK_IO_CALLBACK) system SSL call failed for the reason that is specified in the message.
Contact IBM Software Support.
The gsk_secure_socket_init() system SSL call failed for the reason that is specified in the message.
A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
The gsk_attribute_set_enum(GSK_CLIENT_AUTH_TYPE) system SSL call failed for the reason that is specified in the message.
A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
The gsk_attribute_get_cert_info system SSL call failed for the reason that is specified in the message.
A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
The gsk_secure_socket_read() system SSL call failed for the reason that is specified in the message.
A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
The gsk_secure_socket_write() system SSL call failed for the reason that is specified in the message.
A system SSL trace might be needed to solve the problem. Contact IBM Software Support.
The RSE daemon terminated because of an unrecoverable TCP/IP error.
Contact IBM Software Support.
A Rational Developer for System z command was processed successfully.
No action is required.
An invalid Rational Developer for System z command was issued.
Correct the command parameters and issue the command again.
An invalid Rational Developer for System z Display command was entered. The Display command must be Display Process or Display Client.
Correct the command and try again.
An invalid Rational Developer for System z Cancel command was entered. The command must be Cancel ID=nnnn or Cancel User=userid, where nnnn is a user display ID that is shown in the Display Client command.
Correct the Cancel command parameters and try again.
The SWITCH audit log command cannot be processed because a previous SWITCH command is not yet processed.
Wait for the completion of the previous SWITCH command and try again.
The SWITCH audit log command was entered, but the audit log facility is not active.
Verify the settings that are related to the audit log in the rsed.envvars file and try again.
A Rational Developer for System z Display Client command was issued, but there is no client that the Rational Developer for System z server serves.
No action is required.
The specified user was successfully canceled by a Rational Developer for System z Cancel User command.
No action is required.
The Rational Developer for System z Display Process command was issued, but no server process is running.
No action is required.
The client user who logged on was canceled because the single logon capability is enabled.
No action is required unless you want to disable the single logon capability. To disable the single logon capability, change the settings for the single.logon parameter in the rsed.envvars file. The FEK010I message shows the location of the rsed.envvars file.
A cancel ID command was invalid because the user ID is not logged on. This warning is sometimes issued when a cancel ID command is issued for a user ID that has not yet been logged on.
No action is required.
A Display Process or Display Process,CPU command with an invalid command option was entered.
Correct the command option and issue the command again.
When a command is issued to multiple thread pool processes, the DaemonMonitor receives confirmations from each process and displays the command results. If the timer expires before the DaemonMonitor receives all of the confirmations, then the DaemonMonitor issues this message to show that some processes timed out before processing the command.
No action is required.
A command was entered before the system completed processing a previous instance of the same command.
Wait for the system to process the previous command and then enter the second command again.
This message is a response that is issued when an operator runs the IVP program by using a Rational Developer for System z console command.
No action is required.
This message shows the exit code that is provided by the IVP program.
No action is required.
This message is a response for an audit exit program or logon exit program.
No action is required.
This message is a response for a lock daemon query command.
No action is required.
This message is a response for the lock daemon query command. The specified data set was locked by the specified user ID.
No action is required.
An invalid lock daemon command was entered.
Correct the lock daemon command and try again.
An argument for the lock daemon command is missing.
Supply the missing argument for the lock daemon command and try again.
An invalid argument was specified for the lock daemon command.
Correct the argument for the lock daemon command and try again.
The following runtime messages pertain to the Enterprise Service Tools component (EST) in Rational Developer for System z.
The IRZ runtime messages for Enterprise Service Tools are not displayed in the workbench. They are written to a log on the remote system.
These runtime messages are written by a COBOL or PL/I program that is created by using the single-service project tools in Enterprise Service Tools.
The IRZ messages are grouped into the following subdivisions:
For more information about COBOL and PL/I runtime messages, see z/OS V1R10.0 Language Environment Run-Time Messages (SA22-7566-09), chapters 6 and 7. These documents are available through the following links:
PDF format:
XML to language structure conversion detected that the content of an XML element or attribute that is of type xsd:boolean did not match 'true', 'false', '1', or '0'.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.
XML to language structure conversion uses the COBOL XML PARSE statement. When the XMLPARSE(COMPAT) compiler option is in effect, the return code is provided from the XML PARSE statement and is described in the Enterprise COBOL Programming Guide. When the XMLPARSE(XMLSS) compiler option is in effect, the return code is provided from the z/OS XML System Services Parser and is described in the XML System Services User's Guide and Reference.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Use the return code to determine the error and correct the input XML message.
XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.
XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.
XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.
XML to language structure conversion might encounter errors when it transforms an XML message to a language structure. These errors are distinct from XML PARSE errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.
XML to language structure conversion imposes a limit on the length of XML documents that can be converted into language structures. The maximum length in bytes of the input XML document is 16 MB when version 3 of Enterprise COBOL for z/OS is used and 32 MB when version 4 of Enterprise COBOL for z/OS is used.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
IBM Rational Developer for System z normally prevents generation of XML to language structure converters when it is detected that an input XML message can exceed the 16 MB or 32 MB limit. Check that the input XML message conforms to the XML schema upon which it is based and that any white space outside of element content is trimmed.
XML to language structure conversion maintains a buffer for character content that has a maximum size equal to 10 times the size of the largest item in the target data structure. The content of an element was longer than expected.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Ensure that the message is valid according to the XML schema upon which the XML to language structure converter is based.
Language structure to XML conversion processes white space processing and expands entity references expansion when it generates the XML document. Entity reference expansion increases the length of data which is included as element content and can cause it to grow up to six times the original length of the data (the longest predefined entity is six characters long).
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that the language structure was not changed after the Language structure to XML converter was generated. Regenerate the XML converter if changes were made to the language structure.
XML Conversion might convert XML and language data to and from Unicode during parsing and generation of XML if XML is expected to be exchanged in Unicode.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Check that conversion services are properly installed, and that the Unicode conversion attempted by the XML Converter is supported by the installation of conversion services on the target system.
Certain COBOL data declarations allow characters that are not allowed in an XML document. The allowed characters are defined by the XML specification at http://www.w3c.org.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that the language structure member is properly initialized and does not contain any characters that are not allowed in XML before you attempt conversion.
Language structure to XML conversion determined that the contents of the storage that is occupied by a numeric language structure member is invalid for the type.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that the numeric language structure member is properly initialized according to COBOL semantics.
The language structure to XML converter maintains an internal stack which represents the full qualification of the current element that is being processed in the XML document. If extraneous XML elements not described in the XML schema to which the converter is bound are present in the XML document, they might exceed the maximum supported element depth.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that the numeric language structure member is properly initialized according to COBOL semantics.
XML conversion uses Language Environment callable services to register a user-written handler to handle errors that occur during conversion. An attempt to register such a handler failed.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that Language Environment is configured correctly and that no conditions that could prevent correct operation exist in the chain of execution that leads up to the XML converter.
XML conversion uses Language Environment callable services to register a user-written handler to handle errors that occur during conversion. An attempt to unregister such a handler failed.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that Language Environment is configured correctly and that no conditions that could prevent correct operation exist in the chain of execution that leads up to the XML converter.
The converter detected that one or more of the parameters that were passed to its main entry point do not have valid storage addresses to which the converter could refer and obtain the value.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that each parameter passed to the XML converter has a valid non-null storage address unless a particular parameter can be null as defined by the converter call interface. For example, passing the XML converter a null value for the XML buffer address to the language structure does not perform XML conversion, but returns the required size of the XML buffer instead.
XML to language structure conversion uses an external module to handle bidirectional data conversions.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language structure to XML conversion uses an external module to handle bidirectional data conversions.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
XML to language structure conversion can optionally validate the namespace name of XML elements.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the XML instance document such that the XML elements have namespace names consistent with the names specified in the XML schema.
XML to language structure conversion can optionally validate the namespace name of XML elements.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the XML instance document such that the XML elements have namespace names consistent with the names specified in the XML schema.
XML to language structure conversion detected that the count of a language structure exceeds the maximum that was specified when the XML converter was generated.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the XML document or replace the XML converter with one having a higher maximum.
Language structure to XML conversion detected that the language structure buffer it received contained fewer language structure instances in total than is required by the message layout.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the language structure buffer so that each language structure occurs at least as many times as is required per the message layout.
Language structure to XML conversion detected that the length prefix of a language structure specified a length that is less than the minimum length of the structure. The minimum length of a language structure is computed as the sum of the bytes consumed by all subordinate fields. For fields that specify OCCURS DEPENDING ON, the minimum number of occurrences is assumed.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correctly set the 2-byte length prefix of each language structure in the language structure buffer.
Language structure to XML conversion detected that the language structure buffer it received contained more language structure instances in total than is allowed by the message layout.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the language structure buffer so that it contains no more than the maximum number of instances of each language structure in the message layout.
In the IMS top-down scenario, XML to language structure conversion starts an API named DFSXSETS to store one or more language structures into the IMS Connect message output buffer according to a symmetric protocol. A nonzero return code from DFSXSETS indicates that a language structure could not be stored in the IMS Connect message output buffer and therefore cannot be sent to the IMS application.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
For explanations of DFSXSETS return codes, see the IRZPWSIO module documentation, which is located in the Rational Developer for System z online help.
In the IMS top-down scenario, language structure to XML conversion starts an RDz-provided API named DFSXGETS to retrieve one or more language structures from the IMS Connect message input buffer according to a symmetric protocol. A nonzero return code from DFSXGETS indicates that a language structure could not be retrieved from the IMS Connect message input buffer and therefore cannot be converted to XML.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
For explanations of DFSXGETS return codes, see the IRZPWSIO module documentation, which is located in the Rational Developer for System z online help, .
Explanation: In the top-down scenario language structure to XML conversion provides an application programmer the ability to specify the count of entries that XML conversion reads from an array by using generated counter variables. This message is issued if a counter variable is found to contain a value that exceeds the limit of its corresponding array.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Set the counter variable to a value that does not exceed the limit of the corresponding array.
XML to language structure conversionuses the PL/I PLISAXx built-in function. The return code that is provided is from the PL/I PLISAXx built-in function as described in Enterprise PL/I for z/OS Programming Guide Version 3, SC27-1457-05 (or later).
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Use the return code to determine the error and correct the input XML message.
XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Check that the input XML document has the correct number of occurrences of all entries that repeat.
XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Supply the correct XML message corresponding to this converter.
XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message.
XML to language structure conversion might encounter errors that are distinct from PLISAXA/B errors.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message.
XML to language structure conversion supports parsing XML messages whose length falls within certain compiler limits.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message or define an auxiliary language structure to process the XML in segments.
The XML converter maintains a buffer for character content whose size is equal to that of the largest character member in the language structure or 128, whichever is larger.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correct the input XML message. Check for any excessive white space in the element content.
Language structure to XML conversion supports generation of XML messages whose length falls within certain compiler limits. White space suppression and entity reference expansion are performed during creation of the XML document. Entity reference expansion increases the size of a message in relation to the number of special characters in the source language structure that must be represented as one of the five predefined entity references in XML.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Avoid the use of the five predefined entries in XML when you populate the language structure or define an auxiliary language structure to generate the output XML in segments.
XML Conversion uses PL/I built-in support for UNICODE when the input XML or output XML is encoded in either UTF-16 or UTF-8.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Check that z/OS Support for UNICODE is properly installed and that the conversion attempted by the XML Conversion is supported by the current conversion image.
Certain language structure members allow storage of characters that are not valid in an XML document. The allowed characters are defined by the XML specification at http://www.w3c.org.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that the language structure member is properly initialized and does not contain any characters that are not allowed in XML before you attempt conversion.
Language structure to XML conversion determined that the contents of the storage that is occupied by a numeric data structure member is invalid for the type.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that the numeric data structure member is properly initialized following the semantics of the language.
XML to language structure conversion maintains an internal stack which represents the full qualification of the current element that is being processed in the XML document. If extraneous XML elements not described in the XML schema to which the converter is bound are present in the XML document, they might exceed the maximum supported element depth.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Either supply XML documents to the converter that validate against the bound XML schema or remove the extraneous element that causes the failure from the input XML document.
The converter uses Language Environment callable services to handle errors that might occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that Language Environment is configured properly and that no conditions that would prevent correct operation exist in the chain of execution that leads up to the converter.
The converter uses Language Environment callable services to handle errors that might occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that Language Environment is configured properly and that no conditions that would prevent correct operation exist in the chain of execution that leads up to the converter.
The converter detected that one or more of the parameters that were passed to its main entry point do not have valid storage addresses to which the converter could refer and obtain the value.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that each parameter passed to the converter has a valid storage address unless a particular parameter can be null as defined by the converter call interface. For example, a null message address that is passed to the outbound converter is interpreted as a request for the maximum outbound message size to be returned instead of a conversion.
XML to language structure conversion uses an external module to handle bidirectional data conversions.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language structure to XML conversion uses an external module to handle bidirectional data conversions.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language Structure to XML conversion detected that the length prefix of a language structure specified a length that is less than the minimum length of the structure. The minimum length of a language structure is computed as the sum of the bytes used by all subordinate fields.
The converter either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Correctly set the 2-byte length prefix of each language structure in the language structure buffer.
The Compiled XML Conversion module cited in this message encountered an error when it attempted to allocate storage by using the Language Environment CEEGTST callable service.
The module either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Increase the amount of storage available to Compiled XML Conversion by increasing the maximum size of the region in which the module runs.
The Compiled XML Conversion module cited in this message was unable to free storage by using the Language Environment CEEFRST callable service.
The module either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Ensure that all pointers and associated lengths that are supplied to the Compiled XML Conversion module mentioned in the message are valid. Additionally, check for and correct any storage allocation failures that might occur before the raising of this condition.
The Compiled XML Conversion module cited in this message encountered an error when it used z/OS unicode services character conversion service CUNLCNV to convert a code page.
The module either signals a Language Environment condition or, if the optional feedback code argument is provided, places a condition token that represents the condition in the argument.
Determine the cause of the error by looking up the return and reason codes in the z/OS Unicode Services User's Guide and Reference.
Copyright IBM Corporation - 2009, 2013
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Programming interfaces: Intended programming interfaces allow the customer to write programs to obtain the services of Rational Developer for System z.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Other product and service names might be trademarks of IBM or other companies.