Before using this information, be sure to read the general information under Notices IBM Rational Developer for System z.
This edition applies to IBM Rational Developer for System z Version 8.5 (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 of Rational 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 in Rational 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 for Rational 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 attempt to create a CICS resource definition in a CICS system that is managed by CICSPlex System Manager might fail if the value associated with one or more resource table attributes is invalid. An error can occur for the following reasons:
The attributes that caused the error are flagged on the result display window and one of the following messages that interpret the CICSPlex System Manager error code to provide an explanation for the attributes that are not valid. In all cases, the action is to correct the attribute value that is not valid and resubmit the request.
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:
When an attempt to create a CICS resource definition with an invalid attribute is detected in a CICS system that is not managed by CICSPlex System Manager the following message is logged:
CRRZA1424E CRD Reason code: Not valid - create resource attribute string
The attributes that caused the error are flagged on the result display window and the CRRZA1424E message might be accompanied by one of the following messages that interpret the CICS RESP2 code to provide an explanation for the attributes that are not valid. In all cases, the action is to correct the attribute value that is not valid and resubmit the request.
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.
If you are using the Application Deployment Manager manifest editor then verify that all necessary attributes are specified for the CICS resource that is being defined. In other cases, have your system administrator verify that the program ADNSPAU was used to set defaults when the CICS Resource Definition (CRD) server was installed.
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.
These are the messages that pertain to the BMS Screen Designer (BMS Map Editor) in Rational Developer for System z.
This is typically used when doing some type of validation, and further explanation is provided.
Follow the instructions or look up the message provided as further explanation in the message dialog.
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 a 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 used for the row is not allowed.
Change the value to an allowed entry.
The value used for the column is not allowed.
Change the value to an allowed entry.
The value used for the row or column is not allowed.
Change the value to an allowed entry.
The value used for the field position or length is not allowed.
Change 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 used in field names must conform to the character set supported by the programming language of the application using 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 should be a numeric value.
Specify a row that is a numeric value.
A column should be a numeric value.
Specify a numeric value for the column.
At least one column must be defined.
At least one column must be defined.
Define a column.Define a column.
The sum of the width of the columns making up the table is greater than the table width.
Adjust the columns so that their sum is less than or equal to the table width. Alternatively, if possible, adjust the table width so that it is greater than or equal to the sum of the column width.
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 creating the Source page.
Try closing the BMS file and reopening it.
The BMS editor is expecting a different type of input.
Contact Rational Developer for System z support.
The map set does not contain any maps.
Using the palette 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 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 a particular value.
Specify a length that is not greater than the limit.
The length of the caption exceeds the available space in the caption.
No user action is needed. To display the entire caption, increase the length of the caption, or decrease the length of the caption.
The length of the initial value exceeds the available space.
No user action is required. To display the entire initial value, decrease the length of the initial value or increase the size of the field 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 a certain number of rows.
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 defined for a particular column 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 between 1 and 99.
The field length should be numeric and between 1 and 99.
Specify a numeric field length in the range 1 to 99.
The field distance must be between 1 and 99.
Specify a field distance in the range 1 to 99.
The structure is too big.
Make the structure smaller.
The values entered for the field positions overlap.
Enter values that do not overlap.
The value entered for the BMS file is already in use.
Specify a unique file name.
Something was added to an MVS subproject.
No user response is required.
The symbolic map was created successfully in the destination location you specified.
No user action required.
The symbolic map was created successfully in the destination location you specified.
No user action required.
The specified file name is not valid.
Specify a valid file name.
The specified file name has already been 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 alternate map name starts with an invalid character.
Remove the invalid character and ensure that the alternate map name begins with a character from the set [a-Z].
The name provided as the alternate map name is not valid.
Provide a valid alternate map name.
The alternate map name cannot contain spaces.
Remove all spaces from the alternate map name.
A newly generated BMS File was to the MVS subproject using the new BMS mapset wizard.
No user action required.
These are the messages that pertain to the Common Access Repository Manager (CARMA) in Rational Developer for System z.
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.
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.
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 will include 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 variable {0} will include the host name that returned the error. The variables {2} and {1} will include an error number and error message. The error message should provide 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 providing the local file system to which a file is downloaded..
Informational message providing the trace level of the connection.
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.
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.
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.
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.
These are the client messages that pertain to the Enterprise Service Tools (EST) component in Rational Developer for System z.
Note the following subdivisions:
Messages displayed by the single-service project tools:
1Message 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 host editor encountered an internal error.
See the error log.
The host editor displays this error message whenever it cannot connect to the remote z/OS system that is specified in the current host connection.
The connection can fail for any network reason. Therefore:
The Generate Runtime Code wizard was unable to submit the JCL file to the remote z/OS system.
Make sure that you are logged onto the JES Connection using the Remote Systems View for the system you are deploying to. 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 using the connection preferences and that you are connected.
If the reason indicates that a CRD error has occurred, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the 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 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 (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 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 (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 creating this resource.
If the trailing error message (represented by the words "{error message}" at the end of this message) 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 using the connection preferences and that you are connected.
An error occurred while trying to run 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 appears if you skip over replacing a pre-existing file or if the Application Deployment Manager subsystem encountered an error while creating the file at the specified location.
Ensure that your RSE Connections are connected. Ensure that your target directories or datasets are entered correctly and that you have write access to those destinations. Check the ADM log for additional details (the location of the Application Deployment Manager log is specified in the Preferences page for the Application Deployment Manager).
An error occurred while trying to run the CMIT transaction of the CICS Service Flow Runtime because the SFR flow scan program DFHMAINS abended.
Examine the CICS MSGUSR log and look for a message indicating that DFHMAINS has abended. The message will contain a specific 4-character abend code.
An error occurred while trying to run 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 CICS Application Programming Reference (also see CICS response 2 (RESP2) codes in the online help for the Application Deployment Manager).
An error occurred while trying to run 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 using the connection preferences and that the connection is open.
This is an internal error and normally should not occur.
The reason code returned by the Application Development Manager is a CICS Resource Definition server reason code (see CICS Resource Definition server reason codes 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 (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 when adding 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 (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 (see Chapter 2. Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
The generation property 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 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 appears 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.
There is a syntax error in one of the ESQL expressions in your service flow.
Open the referenced resource and correct the ESQL expression. The expression preventing successful generation is also listed as an error in the Problems view.
When generating a terminal service flow of flow type Link3270 Bridge, only fields named in the imported BMS maps can be referenced in the user-created screen descriptors.
The problem is that a descriptor in the screen description uses a default field name instead of a BMS field name (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 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 (see About invoke types and About flow types).
Revise or remove from the flow any invoke node having an invoke type that is not supported by the flow type of the flow.
If the target runtime 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 referenced in the flow needs to contain BMS information (see When the flow type is Link3270 Bridge -- BMS map information).
When the target runtime 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, you can either import a BMS Map directly into the service flow project to create a screen message, or you can use the Assign BMS Field Names feature to update an existing screen messages (created by capturing a screen) with BMS information (see Working with information from BMS maps).
After doing these steps, you need to re-record the flow before generating runtime code.
There was an internal error generating the runtime code for your service flow.
This error message can occur if you accidentally delete a message resource referenced in your service flow. Resolve any errors or warning messages 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.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
This message can appear when a referenced file could not be found.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for the service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your Service Flow.
Resolve any errors or warning messages 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 are supported by the service flow project tools at this time.
Consult the product documentation 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.
You will need to 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.
There was an internal error generating the runtime code for your Service Flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your Service Flow.
Resolve any errors or warning messages shown in the Problems view.
Depending on the target runtime you are generating to and whether you have specified a flow type of FEPI or Link3270, certain screen descriptors may or may not be supported.
Verify that the descriptors in the specified screen description are supported in the target runtime that you specified when you created the generation properties file (see Support for screen descriptors in the runtime environments).
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
Screen recognition criteria can only be matched against 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 additional 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 (also 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 (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 needed to invoke the generated service flow as a Web service. An error has been 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 needed to invoke the generated service flow as a Web service. An error has been 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 needed to invoke the generated service flow as a Web service. An error has been reported from the batch processor utility.
See the 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 will occur. (Note: 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 compile error will occur since the field is named the same as a COBOL reserved word.
Follow these steps:
A compile error will occur 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 associated with it, you can extract data only from fields that were named in that BMS map. This holds true whether you are extracting from a single field or from a rectangular area.
Open the resource containing the reference to the non-named field. Remove any references to the non-named field. Fields which were not named are given default names during the import process based on the position they are found; for example, "Field30" is the default name given to an unnamed field at position 30 of an imported BMS map (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 specified in the error message.
In the generation properties editor, for the flow node specified in the error message, in the Maximum COMMAREA Length field, you selected Generate length value, a selection that should cause 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:
See Generation properties of the LINK with COMMAREA invoke type.
For the Invoke nonterminal application node 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 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 runtime, you should 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 calculated length of the input message and greater than the calculated length of the output message.
Select Generate length value and let the Generate Runtime Code wizard calculate the value automatically.
See Generation properties of the LINK with COMMAREA invoke type.
Restriction: When the Generate Runtime Code wizard creates COBOL source code for a Web service, and the flow from which the wizard creates the Web service contains a Throw node, then the wizard ignores the Throw node and does not create a return point for the Web service at the corresponding point in the COBOL source code.
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 additional return points associated with Throw nodes.
It is completely 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.
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 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 has neither an output message nor 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 shown in the Problems view.
An internal error occurred during flow playback or during HATS macro generation.
Resolve any errors or warning messages shown in the Problems view.
Flow playback and HATS macro generation do not support Switch nodes (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 (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 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 the specified node is associated with a valid screen operation.
The Invoke screen operation node 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 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 specified in the error message uses an element of ESQL syntax that is not supported in flow playback or in HATS macro generation (see Limitations on features and capabilities when generating HATS macros or when playing flows).
The macro routine specified in the error message contained the specified ESQL keyword. Most elements of ESQL are not supported during flow playback or HATS macro generation (see Restrictions on using ESQL).
To resolve this problem:
Some mapping transforms are not supported by flow playback and HATS macro generation (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 (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 specified in DriverSpec/@fileContainer because no more unique 8-character file names could be generated from the specified prefix.
Specify a shorter prefix in DriverSpec/@fileNamePrefix to allow larger values of the ordinal used to resolve file name collisions.
WSDL2PLI has 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 has not been 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.
The following messages pertain to the System z LPEX Editor in Rational Developer for System z.
An error has occurred, possibly due to a custom extension or product bug.
If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support.
An error occurred while the embedded language parser was trying to display an annotation through the editor. The error might be caused by a custom extension.
If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support for assistance.
The error occurs when opening a declaration 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.
The error may occur if the F3 key is used to open a declaration when there is a parsing error.
Resolve any 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.
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. 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.
This occurs if the software is unable to resolve the selected item.
Select a different item. If the problem persists contact IBM Software Support for assistance.
The argument passed to the perform graph function is not valid.
Try the function again with a different selection. If the problem persists, contact IBM Software Support for assistance.
Listeners were not registered during startup. This can happen if the software is already running in displayless 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 checking of the Open Perform Hierarchy action.
Contact IBM Software Support for assistance.
An error occurred during the availability checking of a Refactor action.
Contact IBM Software Support for assistance.
An error while trying to populate or react to a Perform hierarchy and the location of the paragraph is declared cannot be determined.
Verify that the paragraph being referenced has been declared.
An incorrect argument was passed to the performgraph function.
Contact IBM Software Support for assistance.
The argument passed to the performgraph function is not valid.
Contact IBM Software Support for assistance.
These are the messages that 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 migrated 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 migrated. 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 migrated 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 migrated. 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 migrated 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 migration operation failed.
Contact IBM Software Support.
The Remote Error List view is not visible as part of the perspective in a workspace migrated 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 performing 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 has been 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 has been 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 has been made to delete a resource that might be under control of SCLM.
To continue deleting the resourse, click OK.
An attempt has been 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 indicated in the message might be under control of SCLM.
No response is required.
An attempt has been made to open an include macro by using the Open Include Macro action. The macro has not been added to the current workspace.
To add the macro to the current workspace, use the File > Import action.
An attempt has been 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 has been 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 has been 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 pop-up menu.
You have requested to add a copy member to a project from an edit session, but there is no current MVS Files 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 have requested to open a copy library from an edit session, but it has not yet been 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 have 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 has been allocated and that the copy member exists in this library. Try the action again.
You have 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 have 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 have 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 have 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 have 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 have 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 has been made to open an include file by using the Open Include File action. The file has not been added to the current workspace.
To add the include file to the current workspace, use the File > Import action.
An attempt has been 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 set(s) in the Remote Systems view by expanding 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 has been 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 pop-up menu.
An attempt has been made to perform a local syntax check on a file that has been opened for editing from the Remote Systems view.
An attempt has been made to perform a local syntax check on a file that has been opened for editing. The latest changes to the file cannot be saved, but the syntax check operation can be performed on the copy stored in the local cache.
Click Yes to perform the syntax check on the cached copy.
You have requested to delete a placeholder file in an offline project. A placeholder file represents a remote file that has not been 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 have 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 have requested to move a placeholder file in an offline project. A placeholder file represents a remote file that has not been 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 have 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 have requested to open a placeholder file in an offline project. A placeholder file represents a remote file that has not been 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 have 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 have requested to edit a placeholder file in an offline project. A placeholder file represents a remote file that has not been 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 have 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 retry the operation. 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 retry the operation. 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 retry the operation. 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 retry the operation. 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 has been made to a remote system on which host-based projects are defined. One or more workstation-based projects already 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 has been 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 has been 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 has been 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 has been 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 could have one of the following causes:
A connection has been 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 has been 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 has been 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 has failed because another resource by that name exists.
Retry the operation using a different name.
A subproject has been 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 refer to the correct remote system name.
A subproject has been 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 refer to the correct remote system.
A subproject has been 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 refer to 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.
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.
A JCL submission has failed because the job card is incomplete or invalid.
Modify the JCL job card and submit the JCL again. Contact your system administrator for help constructing a valid job card for your site.
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 pop-up 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 has 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 has been canceled.
To purge the job, do these steps:
While performing 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 operation, a line in the file indicated by {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 operation, multiple lines in the file indicated by {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.
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.
There is an APPC setup problem for the TSO Commands service.
Refer to the IBM Rational Developer for System z Host Configuration Reference (SC14-7290) for information about tuning considerations when using APPC to start the TSO Commands service.
This error occurs when downloading a load module or program object. The transfer types of the source and target data sets are different.
This error can occur while attempting to allocate a partitioned or sequential data set. This error message is issued when the user ID with which you are logged on to the remote system does not have the necessary permission and when 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 has failed. If you used the Compress with Backup action, then a backup copy of the data set is saved.
If you used the Compress with Backup action, 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.
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).
Select a partitioned data set and try the 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.
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 have 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}, could not 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}, could not 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 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 new workspace or property group with the characteristics you want.
During a property group import operation involving multiple property groups, some of the groups could not 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 could not 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.
During a property group import operation, the import file was found to have 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 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.
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 using the DB2 utility DCLGEN. This message indicates that the job has been 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 could not be created or saved.
To open the log file, navigate to 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 containing 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 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.
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 text 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.
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. The corrupt characters are highlighted in the editor.
Change the highlighted characters before trying to save the file.
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 open the file for editing, copy it to a local project in your workspace and change the corrupt characters before attempting to copy it back to the remote system.
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.
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 has been 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 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 will be generated and uploaded to the remote system.
No action is required. The new key mapping file will contain settings for only the configuration files included in the current export request.
You have 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 has been 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 will be shut down and IBM Installation Manager will be started to install the product updates. Restart Rational Developer for System z when the product installation has completed.
You have attempted to copy a partitioned data set member that is an alias. The copy operation cannot be completed because alias processing has been 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 have 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 have 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.
Retry the copy operation and specify a different target. For more information about copying data set aliases see Copying load modules.
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 have 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 you exported to 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 primary system, cancel the current export action, disconnect from primary system {1}, connect to primary system {0}, and reinitiate the export action.
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 because your user ID does not have the correct file permissions to write the configuration file to the parent directory where the configuration files are stored. 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, refer to 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 thatwere made on the remote system.
Click Yes to continue and overwrite the remote changes or No to cancel the request.
An inbound change could not be copied to the local project in the synchronize perspective.
Contact your system administrator.
An outbound change could not 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.
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.
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.
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 has been 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 have previously imported configuration files from group {0} and are now requesting to import configuration files from group {1}.
The remote system to which you have connected uses push-to-client access groups to control access to configuration updates. Since you last connected to this system you have been 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 have connected has previously used push-to-client access groups to distribute configuration updates. Since you last connected to this system, access groups have been 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 remote system to which you are connecting has been configured to automatically download product updates. during the process of shutting down Rational Developer for System z, the Java Virtual Machine (JVM) has failed to terminate in a short amount of time.
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 have typed a member name that does not exist in the partitioned data set.
On the Find Member window, you have typed a member name pattern that results in more matches than the current limit.
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 asks you to confirm the removal of a global variable.
Select Yes or No.
This message asks you to confirm the removal of a user variable.
Select Yes or No.
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 has been 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 has been 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 disconnect and reconnect to the remote system.
This message indicates a successful export z/OS project operation.
No response is required.
This message prompts you to confirm a Remove from Subproject request.
Click Yes to remove the resource from the subproject or No to cancel the request.
The push-to-client feature allows a workspace to be associated with only one access group. You have 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 have connected uses push-to-client access groups to control access to product updates. Since you last connected to this system you have been 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 have connected has previously used push-to-client access groups to distribute product updates. Since you last connected to this system, access groups have been 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.
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. In order to update the content-type file decoration, the Eclipse system must query the contents of the Eclipse File System resource representing one of the members of the added PDS, but it is using a scheduling rule that does not include the cached files folder to read it's contents. The request to add the resource to the subproject has completed successfully.
No action is required.
The remote system to which you are connecting has been 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 local preprocessor has been defined on the Local Preprocessors tab of the Local COBOL Settings or Local PLI Settings page of the property group editor. No Preprocessor Output File Name has been specified and this field is required.
Specify an output file name.
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 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 open the file for editing, copy it to a local project in your workspace and change the corrupt characters before attempting to copy it back to the remote system.
A connection to the debug tool could not 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 could not 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.
This error occurs when attempting to copy and paste 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.
This error occurs when attempting to copy and paste 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.
This warning appears when 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:
You have 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 has been migrated and is not available.
In the Remote Systems view, select the partitioned data set and then select HRECALL from the pop-up menu.
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 will still be 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 has been created for a file that could not be saved on the remote system.
No action is required.
These are the messages that 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 and 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 starting 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 using the port number shown on the remote system (host) shown.
You are not authorized to perform the requested action for the job number shown.
Verify that you selected the correct job ID. Select a job that you are authorized to perform the action on and try again.
A Cancel action has been issued for the job ID shown.
No action is required.
A Cancel action has been issued for the job ID shown, but the job has already completed.
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 has been issued for the job ID shown.
No action is required.
A Refresh Status action has been issued for the selected job, but no information is available. The job may have completed.
No action is required.
A filter string entered into the Retrieve Job window has resulted in no matches.
Enter another filter string and try again.
An Open action for the job ID shown has failed because the job has produced no output or has not yet completed.
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 into 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 has been issued for the job ID shown.
No action is required.
A Purge action has been issued for the job ID shown.
No action is required.
A Release action has been issued for the job ID shown.
No action is required.
A Restart action has been 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 has 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 between 1 and 2147483647.
Your password for the remote system to which you are trying to connect has 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 your site's security requirements.
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.
A RACF error occurred while attempting to log on to the remote system.
Contact your system administrator.
The connection to the remote system has ended because of inactivity.
Connect to the remote system again.
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.
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.
These are the messages that 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.
These are the messages that pertain to Common Access Repository Manager (CARMA) Endevor in Rational Developer for System z.
An invalid value was found in the source file.
Open the file in the text editor by right clicking, and selecting Open With > Text Editor. Remove the invalid value, and reopen the file in the Endevor Package Editor.
An invalid value was found in the source file.
Open the file in the text editor by right clicking, and selecting Open With > Text Editor. Remove the invalid value, and reopen the file in the Endevor Package Editor.
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 supported by the CA Endevor Package Editor. If you are working on a custom client, contact your client developer to investigate if 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 reopening the files in the Endevor Package Editor.
These are the messages that pertain to the CICS Service Component Architecture (SCA) in Rational Developer for System z.
This is an unexpected error that should not occur.
Retry the action that you were performing. If the error persists, contact your IBM representative to report the problem.
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 being invoked 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 program source, specifically the EXEC CICS command at the specified line and column numbers, to determine a proper 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 should have been defined by your CICS system administrator.
Verify with your CICS system administrator that this task was completed as described 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 transfer is complete the archive is unpacked.
Check the error log for more details, and retry the action. If the error persists, contact your IBM representative to report the problem.
The resources in a bundle are packaged into an archive file for transfer to z/OS. After transfer is complete the archive is unpacked.
Review the results of the unpacking operation, check the error log for more details, and retry the action. If the error persists, contact your IBM representative to report the problem.
You selected to delete the contents of the remote bundle prior to 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 retry the action. If the error persists, contact your IBM representative to report the problem.
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 following the unpack operation for the archive file containing 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 transfer is complete the archive is unpacked.
It is recommended that you review the results of the unpacking operation.
The remote folder must exist before transferring the bundle to z/OS.
Verify that the remote folder exists and that the permissions are configured correctly, check the error log for more details, and retry the action. If the error persists, contact your IBM representative to report the problem.
The attempt to verify the install 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 4.1 and higher.
Select a CICS system or region that supports BUNDLE resources.
This is an unexpected error that should not occur.
Retry the action that you were performing. If the error persists, contact your IBM representative to report the problem.
This is an unexpected error that should not occur.
Retry the action that you were performing. If the error persists, contact your IBM representative to report the problem.
Either the path name is incorrect or the file that should be there is missing.
Correct the path name or create the file that is referenced.
Either the path name is incorrect or the file that should be there 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 has been 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 already exists in a particular project.
To overwrite that file in that 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 needed to generate a test case.
Ensure that the zUnit feature is properly installed. The default location for the template file is com.ibm.etools.zunit.gen\template.
The z/OS Automated Unit Testing Framework (zUnit) test case wizard could not 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 could not 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 could not 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 could not correctly load the template file needed 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 could not 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 could not create the directory 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 needed to generate a test case.
Ensure that the zUnit feature is properly installed. The default location for the template file is com.ibm.etools.zunit.gen\template.
The test case program generated by the z/OS Automated Unit Testing Framework (zUnit) test case wizard 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 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 could not 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 could not 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 could not 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 could not 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 the Rational Developer for System z client fails to update a property of the local cache that is overwritten and whose remote member is modified with ISPF so that the local cache is out-of-date.
Update or delete the local cache and try the operation again.
This message indicates that the user clicked a hyperlink on the user interface 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 could not save the configuration file.
Ensure that you have write access to the target for the configuration file and try the operation again.
These are the messages that pertain to Code Review for COBOL and Code Review for PL/I in Rational Developer for System z.
This document contains information about the host and runtime messages for Rational Developer for System z.
Most host and runtime message IDs in Rational 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 the Rational 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).
The following 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 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 message ERROR-TEXT 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 and 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.
Check that the test case module is compiled and linked as a DLL and that the load module name matches the program name supplied in the test runner configuration XML.
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 and 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.
Check that the test case module is compiled and linked as a DLL and that the load module name matches the program name supplied in the test runner configuration XML.
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 execute 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, however either the AZUTCINI API was not started in the entry point or the invocation was unsuccessful.
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 message AZU1000S to determine whether invalid 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 thrown by the DOM implementation 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 parameter named PARM-NAME before calling the API named API-NAME.
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 parameter named PARM-NAME.
A test named TEST-NAME failed in the test case module named MODULE-NAME due to 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 named TEST-NAME and run the test case named MODULE-NAME again. Use the UUID to ensure that the test case module that was located by using standard MVS search order is the version that was intended to be 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 named TEST-NAME and run the test case module named MODULE-NAME again. Use the UUID to ensure that the test case module which was located by using the standard MVS search order is the most recent version or the version that was intended to be 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 named TEST-NAME and run the test case module named MODULE-NAME again. Use the UUID to ensure that the test case module which was located by using standard MVS search order is the most recent version or the version that was intended to be run.
A test case module named MODULE-NAME, which set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization, failed because at least one of its test members failed due to an assertion or an unexpected error.
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 test case module named MODULE-NAME and run the test case module again. At least one instance of message AZU1002S, AZU1003S, or AZU1004S is issued before this message. Refer to the instances of AZU1002S, AZU1003S, or AZU1004S that appear before this message to determine which tests failed within the test case module. Use the UUID to ensure that the test case module which was located by using standard MVS search order is the most recent version or the version that was intended to be 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 calling the AZUTCINI API. Use the UUID to ensure that the test case module which was located by using standard MVS search order is the most recent version or the version that was intended to be 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 which was located by using standard MVS search order is the most recent version or the version that was intended to be run.
A duplicate attempt to initialize a test case module failed because the test case token 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 which was located by using standard MVS search order is the most recent version or the version that was intended to be run.
A test case module named MODULE-NAME, which set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization, did not add any tests by using the AZUTCADD API when the ADDTESTS entry was called by the test runner.
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 test case module MODULE-NAME to add at least one test when the test runner calls the ADDTESTS entry. Use the UUID to ensure that the test case module which was located by using standard MVS search order is the most recent version or the version that was intended to be run
A test case module named MODULE-NAME, which set a test case name of TEST-CASE-NAME and a UUID of TEST-CASE-UUID when it started the AZUTCINI API during initialization, encountered an unexpected error outside of a test entry, possibly in the ADDTESTS, SETUP, or TEARDOWN entries.
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. Additionally 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 which was located by using standard MVS search order is the most recent version or the version that was intended to be run.
An API named API-NAME encountered an internal error. Internal API errors might 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 are the host messages that pertain to CRASTART in Rational Developer for System z.
A program started by CRASTART ended with an return code of aaaaa which may indicate an abend code of bbb.
This may not indicate a problem, but if work the started program did not complete correctly, diagnose the failing program using abend code bbb.
The content of this message is the message returned from dynamic allocation (BPXWDYN) called by CRASERV.
Response is dependent on the message contents.
This message shows the return code cccc from dynamic allocation (BPXWDYN) called by CRASERV.
Response is dependent on the message contents.
This message shows the configuration file name from which CRASERV receives the commands to run.
None.
This message shows the internal file number, hhhh, associated with a reading the CRASERV configuration file and is for diagnostic purposes only.
None.
This message displays the standard command read from the CRASERV configuration file. This is a diagnostic message.
None
This message displays the dynamic allocation command read from the CRASERV configuration file. This is a diagnostic message.
None
This message displays the ddname, dddddddd, that is used by CRASERV as a ddname.
If the ddname is not the same as is expected, verify that the correct ddname is specifie in the CRASERV configuration file.
This message displays the program invocation command read from the CRASERV configuration file. This is a diagnostic message.
The return code cccc was returned to CRASERV by the most recently called program.
None
This message displays the program name (cccccccc) and parameters (p1, p2, ) that are about to be run by CRASERV. This is a diagnostic message.
Verify that variable substitutions, if any, are correct.
A CARMA user explicitly ended their connection.
None
A CARMA users session timed out due to inactivity.
None
A dynamic allocation was done for data set dsname usung a referback.
See the previous allocation statement for details of the referback.
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.
These are the host messages that pertain to the Common Access Repository Manager (CARMA) in Rational Developer for System z.
The CARMA server encountered an unexpected internal error.
Confirm the VSAM files are correct. If you modified the VSAM file, check the correctness of the files based on the CARMA Developer's guide. Otherwise, verify that the files were created properly using the directions in the Host Configuration Guide.
There are no RAMs defined as associated with the current language.
In the client, change the language locale used by CARMA.
Alternatively, the systems programmer can update the host configuration VSAM files as defined in the CARMA Developer's Guide to support the additional locale.
The CARMA server was unable to open the CRADEF VSAM file for reading.
Have your systems programmer confirm the file exists and is accessible by the user's account.
The CARMA server was unable to open the CRASTRS VSAM file for reading.
Have your systems programmer confirm the file exists and is accessible by the user's account.
There are no RAMs defined in the CRADEF configuration VSAM on the host.
Have your systems programmer recreate the CRADEF VSAM from the source files as described in the Host Configuration Guide. Alternatively, define a RAM in the CARDEF as described in the CARMA Developer's guide.
The CARMA server encountered an error 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 by the user's account.
The specified VSAM record in the CRADEF file is invalid.
Have your systems programmer correct the specified record using the CARMA Developer's Guide for more information. 0
The Rational Developer for System z client attempted to connect to a RAM that is not defined on the host.
In the client, disconnect the CARMA connection and restart the workspace. Then connect to the CARMA connection before trying any other actions. If the RAM you require is no longer listed, contact the systems programmer. The RAM may be removed or the RAM ID number may be changed.
The CARMA server was unable to load the RAM load module.
Have your systems programmer confirm the RAM load module exists, it is accessible by CARMA, it is accessible by the user's ID, and that it is a properly compiled DLL.
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, refer to the CARMA Developer's guide.
The function was not called because the compiled RAM was not loaded by CARMA on the host.
Disconnect and try the action again. If you are using a custom host client, have your systems programmer verify that initRAM was called. If the problem persists, contact support.
The CRASTRS record specified is invalid.
Have your systems programmer or RAM developer, if using a custom RAM, verify that the CRASTRS VSAM file was properly created and the specified record is correct.
The initCARMA function was not.
Disconnect and try the action again. If you are using a custom host client, verify initCARMA was called. If the problem persists, contact support.
CARMA was unsuccessful loading the RAM list.
Disconnect from the CARMA and try the action again.
The CARMA address space is out of memory.
Have your systems programmer increase the memory allocated to CARMA address spaces.
The specified record is not defined in the CRASTRS file for the current locale.
This is only a warning and does not require any action by the user.
If local specific strings are required for this record, then an appropriate record should be created in the CRASTRS file to provide the strings. A CRASTRS record can also be created to stop this warning from appearing in the log files. Contact your systems programmer for these modifications.
If you are experiencing these errors while using the CA Endevor RAM, have your systems programmer install APAR PM56551 to fix this problem.
The specified record is not defined in the CRASTRS file for the current locale.
This is only a warning and does not require any action by the user.
If local specific strings are required for this record, then an appropriate record should be created in the CRASTRS file to provide the strings. A CRASTRS record can also be created to stop this warning from appearing in the log files. Contact your systems programmer for these modifications.
If you are experiencing these errors while using the CA Endevor RAM, have your systems programmer install APAR PM56551 to fix this problem.
One or more parameters 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 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 reading the CRASTRS configuration file.
On the client, disconnect from CARMA, reconnect, and try again. If the problem persists, have your systems programmer verify the file is accessible by the user's account.
CARMA could not find a locale to use for this RAM.
Have your systems programmer or RAM developer confirm the CRASTRS VSAM file was properly created. If the problem persists, have your RAM developer create the missing locales in the CRASTRS VSAM file or change the properties on the CARMA connection to use the locale specified by the RAM.
To change the language locale used by CARMA in the client:
CARMA was unable to find the CRAMSG VSAM file.
Have your systems programmer confirm the file exists and is accessible by the users account.
The CARMA server encountered an error 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 by the user's account.
Action 16 is the performAction function and is used to call custom actions in CARMA. The parameters associated with the called custom action are used as action 16's parameters. Providing your own custom parameters and returns interferes with the passing of the custom action called, and is not allowed.
Have the RAM developer remove the VSAM record for action 16 from CRADEF.
The type 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 the default value of the VSAM record matches with the type and length specified for that record.
The RAM was unable to allocate memory.
Have your systems programmer increase the memory allocated to CARMA address spaces.
The TSO or ISPF library function is not available to the RAM.
Have your systems programmer confirm the TSO and ISPF environments are properly started with the CARMA server. This process is explained in the Host Configuration Guide.
The member identifier 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 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 necessary.
The function 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 using a custom host client, notify the developer. If the problem persists, notify your RAM developer.
A parameter with an invalid value was passed to the action.
Try the action again and confirm all parameters contain the correct values.
The target member was unable to update successfully.
In the client, disconnect, reconnect, and try your action again. If the problem persists, try with a different target member. If the problem still persists, contact your RAM developer.
The member was not successfully created.
In the client, attempt to perform the following steps.
If the problem still persists, contact your RAM developer.
The user is not authorized to perform this action.
If you think this message is in error, disconnect 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 perform the action, have your systems programmer confirm that you have access to all files needed by the RAM. Finally, contact your RAM developer if you still experience problems.
The RAM was unable to terminate properly.
No action required.
The RAM is reporting 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 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 function, extractMember, which retrieves chunks of records starting with a starting 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 host client, contact your client developer.
The target member has a record format unsupported by this RAM.
If you are using the sample RAMs provided with CARMA, work with members using a record format of FB (fixed block) or VB (variable block).
LRECL is the length of the record. For RAM function, putMember, the client specifies the maximum length of the record. For RAM function, createMember, 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 response needed.
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 response needed.
The RAM attempted to open a member that was empty.
If you believe this message is in error, contact your RAM developer.
The repository instance was unable to expand because it was empty.
No action required.
The container was unable to expand because it was empty.
No action required.
An error occurred while 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 trying to perform a Delete.
In the client, refresh the parent container to confirm 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 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 required.
The RAM encountered an error trying to access ISPF variables.
In the client, disconnect from CARMA, reconnect, and try again. If the problem persists, confirm 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 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 the CARMALOG is properly set up and 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 CARMA server encountered an incorrectly formatted request.
Confirm that the host code page is correct, and that special characters are not being sent in custom parameters or IDs, such as member ID or instance ID.
The CARMA server received a request for a function it does not recognize.
Make sure that the host load modules for CARMA are at the same level as the UNIX System Services load modules.
CARMA was not initialized before the command was sent to the CARMA server.
In the client, disconnect, reconnect, and try the command again.
All or part of the command was canceled.
In the client, disconnect from CARMA, reconnect, and try again.
The CARMA server was unable to allocate memory.
In the client, disconnect and try again. If it persists, increase the amount of memory available in the address space.
The CARMA server encountered an error reading from the socket. This error was most likely caused by an ABEND in the remote system explorer.
In the client, disconnect, reconnect, and try again. If the problem persists, make sure that enough space is allocated to the remote system explorer for both the heap and stack. The Host Configuration Guide outlines the changes to resd.envvars.
The CARMA server was unexpectedly unable to write to the socket.
No action 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 the client attempting 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 attempting any CARMA actions.
The value 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 desired level.
The value specified for the local was invalid.
In the client, disconnect from CARMA, open the CARMA preferences, and specify a valid local parameter.
An expected parameter was not provided to the CARMA server from the client.
If you receive this error when 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 your problem persists, contact support.
The CARMA server was told to expect 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 waiting for a command.
No action 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 CARMA server expected a parameter that was not provided for the putMember command.
Disconnect from CARMA, reconnect, and try the action again
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 trying your 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.
JES Job Monitor does not have product-specific console messages. The server relies on z/OS and JES to generate console messages for actions done by Developer for System z clients. These are the messages that are posted in the log and pertain to the JES Job Monitor in Rational Developer for System z.
These are the host messages that 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 specified does not exist or does not contain /bin/java. This error may also occur if your TSO region size is too small and Java failed to execute.
Correct the Java directory name or ensure the TSO region size is 128M (SIZE=128000).
The directory name specified for Rational Developer for System z configuration files contains invalid syntax.
Correct the directory name.
The directory name specified for the installation does not exist.
Correct the directory name.
Unable to locate &RDZHLQ..SFEKLOAD. The high level qualifier specified may 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 required. This message is informational 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 has not been Actioned.
Action the work flow request.
This is an internal warning message.
Contact IBM software support if this message is issued in conjunction with an error.
This is an internal informational message only.
No action required.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
This is an internal informational message only.
No action required.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
This is an internal informational message only.
No action required.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
The work flow routine run has 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 has 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 has failed.
Review the work flow routine and any other associated messages. Make the necessary corrections and run the routine again.
An internal error has 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 is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
An internal error has occurred.
Contact IBM software support.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal warning message.
Contact IBM software support if this message is issued in conjunction with an error.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This message is issued in conjunction 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 is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
This is an internal informational message only.
No action required.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
This is an internal informational message only.
No action required.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
An internal error has occurred.
Contact IBM software support.
This is an internal informational message only.
No action required.
This is an internal warning message.
Contact IBM software support if this message is issued in conjunction with an error.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This message is issued in conjunction 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 in conjunction 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 is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
The work flow routine run has failed.
Review the work flow routine and any other associated messages. Correct the errors and run the routine again.
This is an internal informational message only.
No action required.
This is an internal informational message only.
No action required.
These are the host messages that pertain to the RSE daemon or the RSE server in Rational Developer for System z.
These are the runtime messages that pertain to the Enterprise Service Tools component (EST) in Rational Developer for System z.
The messages described in this section are not displayed in the workbench. They are written to a log on the host system.
These messages consist of a single group: the runtime messages that written by a COBOL or PL/I program that is created using the single-service project tools in Enterprise Service Tools.
Note 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 -- see the links below:
PDF format:
XML to language structure conversion makes use of 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.
Use the return code to determine the error and correct the input XML message.
XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
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 may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
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 may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
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 may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
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 16MB when version 3 of Enterprise COBOL for z/OS is used and 32MB when version 4 of Enterprise COBOL for z/OS is used.
IBM Rational Developer for System z will normally prevent generation of XML to language structure converters when it is detected that an input XML message can exceed the 16MB or 32MB respective limit. Check that the input XML message conforms to the XML Schema upon which it is based and that any whitespace outside of element content has been 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.
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 performs whitespace processing and entity reference expansion while generating the XML document. Entity reference expansion increases the length of data which is included as element content causing it to grow up to 6 times the original length of the data (the longest predefined entity is 6 characters long).
Ensure that the language structure has not changed since the Language structure to XML converter has been generated. Regenerate the XML converter if changes have been made to the language structure.
XML Conversion may convert XML and language data to and from Unicode during parsing and generation of XML if XML is expected to be exchanged in Unicode.
Check that conversion services is 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 permit characters that are not legal in an XML document. The permitted characters are defined by the XML specification at http://www.w3c.org.
Ensure that the language structure member is properly initialized and does not contain any characters that are illegal in XML before attempting conversion.
Language structure to XML conversion has determined that the contents of the storage occupied by a numeric language structure member is invalid for the type.
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 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 may exceed the maximum supported element depth.
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.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the XML converter which could prevent proper operation.
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.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the XML converter which could prevent proper operation.
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.
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 a null address for the XML buffer address to the language structure to XML converter will cause the required size of the XML buffer to be returned instead of performing XML conversion.
XML to language structure conversion makes use of an external module to handle bidirectional data conversions.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language structure to XML conversion makes use of an external module to handle bidirectional data conversions.
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.
Correct the XML instance document such that the XML elements have namespace names consistent with those specified in the XML Schema.
XML to language structure conversion can optionally validate the namespace name of XML elements.
Correct the XML instance document such that the XML elements have namespace names consistent with those 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.
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.
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. In the case of fields that specify OCCURS DEPENDING ON, the minimum number of occurrences is assumed.
Correctly set the two-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.
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 invokes an RDz-provided API named IRZXSETS to store one or more language structures into the IMS Connect message output buffer according to a symmetric protocol. A nonzero return code from IRZXSETS 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.
Refer to the IRZPWSIO module documentation, located in the RDz online help, for explanations of IRZXSETS return codes.
In the IMS top-down scenario language structure to XML conversion invokes an RDz-provided API named IRZXGETS to retrieve one or more language structures from the IMS Connect message input buffer according to a symmetric protocol. A nonzero return code from IRZXGETS indicates that a language structure could not be retrieved from the IMS Connect message input buffer and therefore cannot be converted to XML.
Refer to the IRZPWSIO module documentation, located in the RDz online help, for explanations of IRZXGETS return codes.
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 through the use of 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.
Set the counter variable to a value that does not exceed the limit of the corresponding array.
XML to language structure conversion makes use of the PL/I PLISAXx built-in function. The return code provided is from the PL/I PLISAXx built in function as described in SC27-1457-05 (or later), "Enterprise PL/I for z/OS Programming Guide Version 3".
Use the return code to determine the error and correct the input XML message.
XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.
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 may encounter errors that are distinct from PLISAXA/B errors.
Supply the correct XML message corresponding to this converter.
XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.
Correct the input XML message.
XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.
Correct the input XML message.
XML to language structure conversion supports parsing XML messages whose length falls within certain compiler limits.
Correct the input XML message or define an auxiliary language structure(s) 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.
Correct the input XML message. Check for any excessive whitespace in the element content.
Language structure to XML conversion supports generation of XML messages whose length falls within certain compiler limits. Whitespace suppression and entity reference expansion is 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 need to be represented as one of the five predefined entity references in XML.
Avoid the use of the five predefined entires in XML when populating the language structure or define an auxiliary language structure(s) 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.
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 permit storage of characters that are not legal in an XML document. The permitted characters are defined by the XML specification at http://www.w3c.org.
Ensure that the language structure member is properly initialized and does not contain any characters that are illegal in XML before attempting conversion.
Language structure to XML conversion has determined that the contents of the storage occupied by a numeric data structure member is invalid for the type.
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 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 may exceed the maximum supported element depth.
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 may occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the converter that would prevent proper operation.
The converter uses Language Environment callable services to handle errors that may occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the converter that would prevent proper operation.
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.
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 passed to the outbound converter will be interpreted as a request for the maximum outbound message size to be returned instead of performing a conversion.
XML to language structure conversion makes use of an external module to handle bidirectional data conversions.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language structure to XML conversion makes use of an external module to handle bidirectional data conversions.
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 consumed by all subordinate fields.
Correctly set the two-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 attempting to allocate storage using the Language Environment CEEGTST callable service.
The module will either signal a Language Environment condition or, if the optional feedback code argument is provided, a condition token representing the condition will be placed 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 executes.
The Compiled XML Conversion module cited in this message was unable to free storage using the Language Environment CEEFRST callable service.
The module will either signal a Language Environment condition or, if the optional feedback code argument is provided, a condition token representing the condition will be placed in the argument.
Ensure that all pointers and associated lengths supplied to the Compiled XML Conversion module mentioned in the message are valid. Additionally, check for and correct any storage allocation failures that may have occurred prior to the raising of this condition.
The Compiled XML Conversion module cited in this message encountered an error when using z/OS unicode services character conversion service CUNLCNV to perform a codepage conversion.
The module will either signal a Language Environment condition or, if the optional feedback code argument is provided, a condition token representing the condition will be placed 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, 2011
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.