Rational Developer for System z

IBM Rational Developer for System z Version 8.0.3

Messages and Codes


SC14-7497-00

Note!

Before using this information, be sure to read the general information under Notices IBM Rational Developer for System z.

First edition (October 2011)

This edition applies to IBM® Rational® Developer for System z® Version 8.0.3 (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:

IBM Corporation
Attn: Information Development Department 53NA
Building 501 P.O. Box 12195
Research Triangle Park NC 27709-2195.
USA

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.

About this book

This guide provides information about ...

This document contains information on the following tasks:
  • ...

Who should read this book

This book is intended for ...

Client messages in Rational Developer for System z

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).

Messages for the Debug Tool for z/OS

These are the messages that pertain to the Debug Tool for z/OS® in Rational Developer for System z.

CRRDG1001E

Source file not found.

CRRDG1002I

To add a new source lookup path location, click the button below.

CRRDG1003E

Source file {0} was not found.

CRRDG1010E

Selection already on source lookup path.

CRRDG1011E

Invalid selection.

CRRDG1012E

Error occurred.

CRRDG1013E

Selection must be a jar or zip.

CRRDG1014E

Selection must be a folder.

CRRDG1015E

Selected project is closed.

CRRDG1016E

Unable to add source location to lookup path.

CRRDG1017E

Unsupported action.

CRRDG1018E

Could not save launch configuration.

CRRDG1019E

Unable to initialize source location.

CRRDG1020W

More than one source was found for '{0}'.

CRRDG1030E

Variable name cannot contain the '=' character

CRRDG1031E

Variable name is already defined

CRRDG2001E

Value must be an integer between {0} and {1}

CRRDG2002E

Value must be an integer between the current pace value and {0}

CRRDG2003E

Value must be an integer between {0} and the maximum pace value

CRRDG2201E

"{0}" is not a valid group for this layout.

CRRDG2202E

The group named "{0}" is reserved and cannot be used.

CRRDG2203E

Unable to build map from {0}: address is of mixed endianness.

CRRDG2204E

Unable to open {0}: the file no longer exists.

CRRDG2211E

File {0} could not be opened.

CRRDG2212E

File {0} could not be parsed.

CRRDG2213E

File {0} has an incorrect layout format.

CRRDG2214E

Invalid Hex Value

CRRDG2221E

Address Error

CRRDG2222E

An incorrect layout format was encountered while building layout elements.

CRRDG2223E

Bit {0} does not belong to a valid Bit Mask Field

CRRDG2224E

Specified length of layout is incorrect

CRRDG2225E

This element is out of the bounds of the layout:

CRRDG2226E

Edit failed

CRRDG2227E

Unable to retrieve all the bytes from address 0x{0}

CRRDG2228E

Failed to build memory map:

CRRDG2229E

Unable to create memory map:

CRRDG2230E

Failed to edit the selected field:

CRRDG2231E

Directory {0} does not exist.

CRRDG2232E

Set Directory Failed

CRRDG2233E

Unable to set to the specified directory.

CRRDG2234E

Unable to refresh the base address of the memory block.

CRRDG2241E

The memory map cannot be copied to the clipboard.

CRRDG2251E

The group name is reserved and cannot be used:

CRRDG2252E

The group already exists:

CRRDG2253E

Error adding group:

CRRDG2254E

Unable to save file:

CRRDG2255E

File(s) already exist:

CRRDG2256E

Export map file failed.

CRRDG2261E

Minimum block size must be greater than 256 and less than the maximum.

CRRDG2262E

Maximum block size must be less than {0} and greater than the minimum.

CRRDG2263E

Block sizes must be valid integers

CRRDG2271E

Unable to continue expanding the map

CRRDG2272E

Could not continue full expansion because of the following error:

CRRDG2273W

Note: Due to this error, the Find dialog may not contain all the elements in the map.

CRRDG2281E

Cannot export {0} because you do not have write permissions for this file.

CRRDG2282W

This rendering shares one or more files with other renderings. If the following files are overwritten, those renderings will be affected. {0} Continue?

CRRDG2283E

You cannot edit groups or descriptions because the file {0} is read-only.

CRRDG2284E

Malformed offset: offset must be a positive integer.

CRRDG2285E

Malformed offset: absolute offsets must be a positive integer.

CRRDG2286E

Specify an org element, offset, or '*none'. The offset must evaluate to an integer >= 0.

CRRDG2287E

Expression {0} does not evaluate to a positive offset.

CRRDG2291E

The selected element instance does not support memory mapping

CRRDG3001E

Communications failure

CRRDG3002E

Connection with the debug engine was lost

CRRDG3003W

Connection to engine was terminated by user

CRRDG3004W

The program has been terminated.

CRRDG3011E

Source file {0} was not found.

CRRDG3012E

The source file {0} was found by an unsupported source container type and cannot be displayed by this editor. The result of this source lookup was an object of type {1}

CRRDG3013E

Unsupported action.

CRRDG3021W

Request not supported.

CRRDG3031E

File {0} could not be opened

CRRDG3041E

Base address not set

CRRDG3042E

Length requested not supported

CRRDG3043E

Invalid address

CRRDG3044E

Unable to retrieve memory contents

CRRDG3045E

Unable to write changes to memory

CRRDG3046W

Memory operations are not supported by this debug engine

CRRDG3047E

Invalid parameters used to request memory

CRRDG3048E

Location for address expression is invalid

CRRDG3049W

Enhanced memory support not available

CRRDG3050E

Unable to convert expression to address

CRRDG3060E

Failed to register the breakpoint {0} with the client breakpoint manager.

CRRDG3061W

Engine is busy.

CRRDG3062E

Request to engine failed.

CRRDG3063E

Unsupported debug engine. Connection terminated.

CRRDG3064E

The debug engine reported an error, but no error message text was provided. The error return code was {0}

CRRDG3065E

Debug engine failed to start.

CRRDG3066W

Debug engine is terminated.

CRRDG3067I

The program {0} was not compiled with debug information.

CRRDG3071E

Invalid library name.

CRRDG3072E

Invalid address or expression.

CRRDG3073E

Invalid program location.

CRRDG3074E

Invalid line number.

CRRDG3075E

Invalid resource specified. Check that the project and source names are correct.

CRRDG3076E

Macro "{0}" not found.

CRRDG3077E

Function or entry point must be specified.

CRRDG3078E

Invalid address or expression.

CRRDG3079E

Invalid number of bytes monitored. Enter a positive integer value.

CRRDG3080E

No debug session available.

CRRDG3081E

From must be an integer greater than or equal to 1

CRRDG3082E

To must be an integer greater than or equal to From

CRRDG3083E

Every must be an integer between 1 and (To - From + 1)

CRRDG3091W

A compiled language debug target must be selected to use this function.

Client messages for Application Deployment Manager

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.

Transfer messages

CRRZA0002I

Trying to connect to a system or region: {0}

Explanation

{0}
System name or region name
Connection to the system or region has been initiated.

User response

No action is required.

CRRZA0003I

A connection is successfully established with a system or region: {0}

Explanation

{0}
System name or region name
The action listed has been performed.

User response

No action is required.

CRRZA0004E

A connection failed trying to communicate with a system or region: {0}

Explanation

{0}
System name or region name
An error was encountered while performing the specified action.

User response

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.

CRRZA0005I

Sending request {0} to system or region: {1}

Explanation

{0}
Request name
{1}
System name or region name
The action listed is being performed.

User response

No action is required.

CRRZA0006I

Request {0} was sent successfully to a system or region: {1}

Explanation

{0}
Request name
{1}
System name or region name
Connection to the system or region has been initiated.

User response

No action is required.

CRRZA0007E

Application Deployment Manager is unable to send request {0} to a system or region: {1}

Explanation

{0}
Request name
{1}
System name or region name
An error was encountered while performing the specified action.

User response

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.

CRRZA0008E

An error was encountered while retrieving deployment system categories: {0}

Explanation

{0}
The text of a Java exception that occurred
An error was encountered while performing the specified action.

User response

Contact support.

Build messages

CRRZA0009E

An error was encountered while retrieving the deployment manifest: {0}

Explanation

{0}
The name of an XML error tag that could not be found or correctly parsed in a manifest file
An error was encountered while performing the specified action.

User response

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.

CRRZA0010E

An error was encountered while trying to create a persistable object from the deployment manifest: {0}

Explanation

{0}
The name of the deployment manifest
An error was encountered while performing the specified action.

User response

Verify that newly added contributors to the Application Deployment Manager framework are operational. If they are, contact support and provide this log.

CRRZA0011E

An error was encountered while creating the interactive deployment page: {0}

Explanation

{0}
Cause
An error was encountered while performing the specified action.

User response

Contact Customer Support.

CRRZA0012E

An error was encountered while creating the deployment manifest page: {0}

Explanation

{0}
Cause
An error was encountered while performing the specified action.

User response

Contact Customer Support.

CRRZA0013E

An error was encountered while creating the deployment systems page: {0}

Explanation

{0}
Cause
An error was encountered while performing the specified action.

User response

Contact Customer Support.

CRRZA0014E

An error was encountered while saving the deployment manifest file: {0}

Explanation

{0}
Cause
An error was encountered while performing the specified action.

User response

Verify that the file system is not full and that you have permission to write to it.

CRRZA0015E

The object type that was provided as input to the deployment manifest editor is not valid. The object type must implement interface IFileEditorInput.

Explanation

An error was encountered while performing the specified action.

User response

Verify that newly added contributors to the Application Deployment Manager framework are operational. If they are, contact Customer Support and provide this log.

CRRZA0016I

The deployment of the manifest has started.

Explanation

The action listed is being performed.

User response

No action is required.

CRRZA0017I

The deployment of the manifest has been completed.

Explanation

The action listed has been performed.

User response

No action is required.

CRRZA0018E

An error was encountered while deploying the manifest: {0}

Explanation

{0}
Cause
An error was encountered while deploying the manifest. The error message indicates the cause.

User response

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.

CRRZA0019E

The deployment of the manifest could not be completed because the deployment operation was interrupted.

Explanation

An error was encountered while performing the specified action.

User response

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.

CRRZA0020I

The existing registry file is being replaced by the newly imported registry.

Explanation

The action listed is being performed.

User response

No action is required.

CRRZA0021E

An error was encountered while trying to export the registry to an existing file. This is due to being unable to delete the existing registry file: {0}

Explanation

{0}
Cause
An error was encountered while performing the specified action.

User response

Verify that the file system is not full and that you have permission to delete the manifest files from the location where it resides.

CRRZA0022I

Writing the systems registry to {0}

Explanation

{0}
File name
The action listed is being performed.

User response

No action is required.

CRRZA0023E

An error was encountered while creating a duplicate copy of a deployment system. A default deployment system is instead created: {0}

Explanation

{0}
Cause
An error was encountered while performing the specified action.

User response

Verify that newly added contributors to the Application Deployment Manager framework are operational. If they are, contact Customer Support and provide this log.

CRRZA0027E

A server request received no response. The current communications protocol might not support the requested action.

Explanation

The current communications protocol might not support the requested action.

User response

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.

CICSPlex System Manager return codes, error codes, and messages

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:
  • CICSPlex SM Application Programming Reference (SC34-7031)
  • CICSPlex SM Application Programming Guide (SC34-7030)
  • CICSPlex SM Resource Tables Reference (SC34-7032)

CICSPlex System Manager return codes

CRRZA1050I
CPSM Return code: OK

Explanation

All CICSPlex System Manager functions completed normally.

User response

No action is required.
CRRZA1051E
CPSM Return code: Scheduled

Explanation

The CICSPlex System Manager command has been scheduled for processing. This condition should not occur.

User response

Contact Customer Support.
CRRZA1052E
CPSM Return code: Not found

Explanation

Either an action or an attribute is not found to be associated with the CICSPlex System Manager resource table for this resource.

User response

Contact Customer Support.
CRRZA1053E
CPSM Return code: No data

Explanation

A CICSPlex System Manager Get Object command was issued, but no records were found that matched the specified search criteria.

User response

Verify that a CICSPlex System Manager resource definition has not been inadvertently deleted.
CRRZA1054E
CPSM Return code: Not valid - parameter

Explanation

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.

User response

Use the reason code to determine the identity of the parameter.
CRRZA1055E
CPSM Return code: Failed

Explanation

A CICSPlex SM command failed because of an abend or an exception condition.

User response

Use the reason code to determine whether an abend or exception condition occurred.
CRRZA1056E
CPSM Return code: Environment error

Explanation

A CICSPlex System Manager command failed because of an environment error.
The error occurred for one of the following reasons:
  • No Service: The application stub program could not load the API service module.
  • No Storage: The application stub program could not obtain the necessary storage in the address space where the processing thread is running.
  • Request Time out: One of the CMASs or MASs to which the request was directed did not respond.
  • Soc Resource: A required resource that is owned by the CMAS is not available.

User response

Use the reason code to determine whether a No Service, No Storage, Request Time Out, or Soc Resource condition occurred.
CRRZA1057E
CPSM Return code: Not permitted

Explanation

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:
  • Expired: The security authorization of the specified user ID has expired.
  • Sign-on parameter: The specified signon parameter is not authorized for the user ID.
  • User ID: The specified user ID does not have the required security authorization.

User response

Use the reason code to determine whether an expired, sign-on parameter, or user ID condition occurred.
CRRZA1058E
CPSM Return code: Busy

Explanation

A CICSPlex System Manager command failed because the result set specified on the RESULT option is being processed by another command.

User response

Retry the operation. If the condition persists, notify Customer Support.
CRRZA1059E
CPSM Return code: Server gone

Explanation

The CMAS to which the processing thread was connected is no longer active.

User response

CMAS may have ended. Retry the operation. If the condition persists, notify Customer Support.
CRRZA1060E
CPSM Return code: Not available

Explanation

A not-available condition occurred because of an APITASK, CMAS, CPSMAPI, or MAINTPOINT error.
These errors occur for the following reasons:
  • APITASK: The API control subtask is not active.
  • CMAS: A CMAS to which the request was directed is not available.
  • CPSMAPI: The CMAS to which the processing thread is connected is not available for API processing.
  • MAINTPOINT: The maintenance point for the current context is not available.

User response

CMAS may have ended. Retry the operation. If the condition persists, notify Customer Support.
CRRZA1061E
CPSM Return code: Not valid - version

Explanation

A version conflict occurred.
It occurred for one of the following reasons:
  • NOTSUPPORTED: The version of the application stub program used for this command is not supported.
  • NOTVSNCONN: The version of the application stub program used for this command is not the same as the version used with the CONNECT command.

User response

Use the reason code to determine whether a NOTSUPPORTED or NOTVSNCONN condition occurred.
CRRZA1062E
CPSM Return code: Not valid - command

Explanation

A CICSPlex System Manager command that is not valid was issued.
The command is not valid for one of the following reasons:
  • FILTER: The filter expression passed on the operation is too large or complex.
  • LENGTH: The total length of all the options on the command exceeds the maximum limit.

User response

Use the reason code to determine whether a Filter or Length condition occurred.
CRRZA1063E
CPSM Return code: Warning

Explanation

A CICSPlex System Manager command completed processing with a warning.
The warning occurred for one of the following reasons:
  • MAXRECORDS: The number of records added to the result set by a MAS would have exceeded the MAXHISTRECS value for that MAS.
  • RESULT: During the building of the result set to be used on the command, a non-OK response was received. However some result set records were available and the requested action was successfully performed against them.
  • During the building of the result set to be used on the command, a non-OK response was received. However some result set records were available and the requested action was attempted.

User response

Use the reason code to determine whether a MAXRECORDS, RESULT, or ACTION condition occurred.
CRRZA1064E
CPSM Return code: Table error

Explanation

A CICSPlex System Manager command failed because a resource table record is not valid.

The record is invalid for one of the following reasons:

DATAERROR
The value associated with one or more resource table attributes is not valid. This error can occur if either of the following conditions is true:
  • The resource table is missing required attributes, contains one or more conflicting attributes, or is a duplicate.
  • A CICS resource definition contains attributes that would cause the EXEC CICS CREATE command to issue warnings.
Use the FEEDBACK command to retrieve additional data about this error.
INVALIDATTR
One of the resource table attributes is invalid.
INVALIDVER
The specified version of the resource table is not supported by System Manager.

User response

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.
CRRZA1065E
CPSM Return code: Incompatible

Explanation

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.

User response

Contact Customer Support.
CRRZA1066E
CPSM Return code: In use

Explanation

A CICSPlex System Manager DISCARD command failed because an in-use condition occurred.
The condition occurred for one of the following reasons:
  • FILTER: The specified filter is currently in use and cannot be discarded.
  • VIEW: The specified view is currently in use and cannot be discarded.

User response

Use the reason code to determine whether a FILTER or VIEW condition occurred.
CRRZA1067E
CPSM Return code: Not valid - data

Explanation

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:
  • PARM: An attribute value listed in the PARM buffer is not valid for the specified attribute.
  • CRITERIA: An attribute value listed in the CRITERIA buffer is not valid for the specified attribute.

User response

Use the reason code to determine whether a PARM or CRITERIA condition occurred.
CRRZA1068E
CPSM Return code: Duplicate

Explanation

A CICSPlex System Manager command failed because the specified view already exists and cannot be built. This condition should not occur.

User response

Contact Customer Support.

CICSPlex System Manager error codes

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 resource table is missing required attributes, contains one or more conflicting attributes, or is a duplicate.
  • A CICS resource definition contains attributes that would cause the EXEC CICS CREATE command to issue warnings.

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.

CRRZA1100E
CPSM Error code: The attribute data is not valid.
CRRZA1101E
CPSM Error code: The requested resource was not found.
CRRZA1102E
CPSM Error code: The resource already exists.
CRRZA1103E
CPSM Error code: The resource definition has already changed.
CRRZA1104E
CPSM Error code: The resource type is not valid.
CRRZA1105E
CPSM Error code: The resource version is not valid.
CRRZA1106E
CPSM Error code: The maintenance point CMAS is not available.
CRRZA1107E
CPSM Error code: The context was not found.
CRRZA1108E
CPSM Error code: An inconsistent set condition exists.
CRRZA1109E
CPSM Error code: The resource group was not found.
CRRZA1110E
CPSM Error code: The action is not valid.
CRRZA1111E
CPSM Error code: The record address is not valid.
CRRZA1112E
CPSM Error code: The record length is not valid.
CRRZA1113E
CPSM Error code: Different version
CRRZA1114E
CPSM Error code: The name list ended early.
CRRZA1115E
CPSM Error code: The name list is not valid.
CRRZA1116E
CPSM Error code: The name is not valid.
CRRZA1117E
CPSM Error code: The minor name is not valid.
CRRZA1118E
CPSM Error code: Notify
CRRZA1119E
CPSM Error code: The software is partially installed.
CRRZA1120E
CPSM Error code: Nothing is installed.
CRRZA1121E
CPSM Error code: No targets are specified.

Explanation

You must specify a target.

User response

Specify a target.
CRRZA1122E
CPSM Error code: No related systems are specified.

Explanation

You must specify a related system.

User response

Specify a related system.
CRRZA1123E
CPSM Error code: The target scope is not valid.
CRRZA1124E
CPSM Error code: The related scope is not valid.
CRRZA1125E
CPSM Error code: The usage is not valid.
CRRZA1126E
CPSM Error code: The mode is not valid.
CRRZA1127E
CPSM Error code: Not valid - state check
CRRZA1128E
CPSM Error code: Not valid - force install
CRRZA1129E
CPSM Error code: Not valid - notify
CRRZA1130E
CPSM Error code: Not valid - overtype
CRRZA1131E
CPSM Error code: Not valid - override block
CRRZA1132E
CPSM Error code: Not valid - override string
CRRZA1133E
CPSM Error code: The string terminator is not valid.
CRRZA1134E
CPSM Error code: Not valid - embedded terminator
CRRZA1135E
CPSM Error code: The attribute is not valid.
CRRZA1136E
CPSM Error code: The literal is not valid.
CRRZA1137E
CPSM Error code: Not valid - override string
CRRZA1138E
CPSM Error code: Scope required
CRRZA1139E
CPSM Error code: A usage conflict exists.
CRRZA1140E
CPSM Error code: No definitions are selected.
CRRZA1141E
CPSM Error code: More than one related system was specified.
CRRZA1142E
CPSM Error code: The related-system identifier is missing.
CRRZA1143E
CPSM Error code: A scope conflict exists.

Explanation

This message indicates that an error occurred during a request made to CPSM.

User response

See the CPSM documentation to determine the cause for scope conflicts.

CICSPlex System Manager messages

CRRZA3001I
No WSBIND file has been selected.

Explanation

A WSBIND file must be selected before you can use the View function.

User response

Select a WSBIND file.
CRRZA3002E
No active RSE connection is available to retrieve the WSBIND file {0}.

Explanation

{0}
The name of a WSBIND file
An active RSE connection must be available to retrieve the WSBIND file.

User response

Create an active RSE connection.
CRRZA3003E
Resource {0} is defined but is not loaded. The name of the physical data set in which {0} resides was not determined.

Explanation

{0}
The name of a resource
Resource {0} must be loaded to determine the name of the physical data set in which {0} resides.

User response

Load Resource {0}.

CICS response 2 (RESP2) codes

Only selected CICS RESP2 codes are documented in this publication. For additional information see the following books:
  • CICS System Programming Reference (SC34-7024)
  • CICS Application Programming Reference (SC34-7023)
  • CICS Application Programming Guide (SC34-7022)

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.

CRRZA1200E

CICS RESP2: A required keyword is omitted.

CRRZA1201E

CICS RESP2: One specified keyword requires another one to be specified.

CRRZA1202E

CICS RESP2: A keyword occurs more than once.

CRRZA1203E

CICS RESP2: Conflicting keywords are specified.

CRRZA1204E

CICS RESP2: An invalid operand is supplied.

CRRZA1205E

CICS RESP2: An operand is supplied for a keyword that does not need one.

CRRZA1206E

CICS RESP2: A required operand for a keyword is omitted.

Explanation

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.

User response

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.

CRRZA1207E

CICS RESP2: The operands of two or more keywords conflict with one another.

CRRZA1208E

CICS RESP2: The value of the operand of a keyword is too small.

CRRZA1209E

CICS RESP2: In the pair of values specified as the operand of a keyword the second value must not exceed the first.

CRRZA1210E

CICS RESP2: The value of the operand must be different from the name of the resource.

CRRZA1211E

CICS RESP2: A closing parenthesis has been omitted from the DESCRIPTION keyword.

CICS Resource Definition server return codes

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.

CRRZA1300I

CRD Return code: OK

CRRZA1301W

CRD Return code: Warning

CRRZA1302E

CRD Return code: Error

CICS Resource Definition server reason codes

CRRZA1400E

CRD Reason code: The COMMAREA length is too short for the response.

Explanation

The communication area passed to the CICS Resource Deployment (CRD) server from the CRD client was too short to contain the response.

User response

Contact Customer Support.

CRRZA1401E

CRD Reason code: There are too many items to return.

Explanation

More array items existed than could be returned.

User response

Contact Customer Support.

CRRZA1402E

CRD Reason code: The INQUIRE WEBSERVICE START command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1403E

CRD Reason code: The INQUIRE WEBSERVICE NEXT command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1404E

CRD Reason code: The INQUIRE WEBSERVICE END command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1405E

CRD Reason code: The INQUIRE PIPELINE START command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1406E

CRD Reason code: The INQUIRE PIPELINE NEXT command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1407E

CRD Reason code: The INQUIRE PIPELINE END command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1408E

CRD Reason code: The INQUIRE URIMAP START command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1409E

CRD Reason code: The INQUIRE URIMAP NEXT command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1410E

CRD Reason code: The INQUIRE URIMAP END command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1411E

CRD Reason code: The INQUIRE CONNECTION START command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1412E

CRD Reason code: The INQUIRE CONNECTION NEXT command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1413E

CRD Reason code: The INQUIRE CONNECTION END command failed.

Explanation

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.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1414E

CRD Reason code: The resource was found.

Explanation

Before resource creation and installation an existing resource with the same name was found.

User response

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.

CRRZA1415E

CRD Reason code: Uninstallation failed.

Explanation

An Uninstall request failed.

User response

Use the accompanying CICS response codes, or the CPSM return, reason, and error codes to determine the cause.

CRRZA1416E

CRD Reason code: The resource was not found.

Explanation

A request to retrieve a CICS resource definition failed because the resource was not found.

User response

Check that the correct resource name and resource type were specified.

CRRZA1417E

CRD Reason code: The command type is not valid.

Explanation

An invalid request type was received by the CRD server from the CRD client. This should not occur.

User response

Contact Customer Support.

CRRZA1418E

CRD Reason code: An error occurred while reading a repository file.

Explanation

An attempt to read the CRD repository failed.

User response

Use the accompanying CICS response codes to determine the cause.

CRRZA1419E

CRD Reason code: An error occurred while writing a repository file.

Explanation

An attempt to write to the CRD repository failed.

User response

Use the accompanying CICS response codes to determine the cause.

CRRZA1420E

CRD Reason code: An error occurred while rewriting a repository file.

Explanation

An attempt to rewrite to the CRD repository failed.

User response

Use the accompanying CICS response codes to determine the cause.

CRRZA1421E

CRD Reason code: The artifact type is not valid.

Explanation

An invalid artifact type was received by the CRD server from the CRD client. This should not occur.

User response

Contact Customer Support.

CRRZA1422E

CRD Reason code: The value of the log message is not valid.

Explanation

A Create resource command was issued with an invalid log parameter. This should not occur.

User response

Contact Customer Support.

CRRZA1423E

CRD Reason code: The EXECUTIONSET value, DPLSUBSET, is not valid.

Explanation

A Create resource command was issued in a program defined with an EXECUTIONSET value of DPLSUBSET. This should not occur.

User response

Contact Customer Support.

CRRZA1424E

CRD Reason code: The ATTRIBUTES string of a CREATE RESOURCE command is not valid.

Explanation

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.

User response

Use the CICS RESP2 code to determine the specific cause for the flagged attribute.

CRRZA1425E

CRD Reason code: INQUIRE DB2TRAN failure

Explanation

An INQUIRE DB2TRAN command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1426E

CRD Reason code: INQUIRE DOCTEMPLATE failure

Explanation

An INQUIRE DOCTEMPLATE command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1427E

CRD Reason code: INQUIRE FILE failure

Explanation

An INQUIRE FILE command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1428E

CRD Reason code: INQUIRE PROCESSTYPE failure

Explanation

An INQUIRE PROCESSTYPE command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1429E

CRD Reason code: INQUIRE PROGRAM failure

Explanation

An INQUIRE PROGRAM command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1430E

CRD Reason code: INQUIRE TDQUEUE failure

Explanation

An INQUIRE TDQUEUE command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1431E

CRD Reason code: INQUIRE TRANSACTION failure

Explanation

An INQUIRE TRANSACTION command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1432E

CRD Reason code: CPSM connection error

Explanation

A CPSM Connect command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1433E

CRD Reason code: CPSM error getting object

Explanation

A CPSM Get Object command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1434E

CRD Reason code: CPSM creation error

Explanation

A CPSM Create command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1435E

CRD Reason code: CPSM installation error

Explanation

A CPSM Perform Object with Install action command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1436E

CRD Reason code: CPSM deletion error

Explanation

A CPSM Delete command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1437E

CRD Reason code: CPSM error adding resource to group

Explanation

A CPSM Perform Object with AddtoGroup action command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1438E

CRD Reason code: CPSM error removing resource from group

Explanation

A CPSM Perform Object with Remove action command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1439E

CRD Reason code: The ASSIGN command failed.

Explanation

An Assign command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1440E

CRD Reason code: CICS resource security checking is not in effect.

Explanation

The check for CICS resource security is no longer performed. This should not occur.

User response

Contact Customer Support.

CRRZA1441E

CRD Reason code: Not valid - attempt to define a CICS transaction with program = CRD server

Explanation

An attempt was made to define a CICS transaction with the program attribute equal to the CRD server program name. This is not allowed.

User response

Change the name of the program.

CRRZA1442E

CRD Reason code: INQUIRE TCPIPSERVICE failure

Explanation

An INQUIRE TCPIPSERVICE command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1443E

CRD Reason code: A CPSM fetch resource error occurred.

Explanation

A CPSM Fetch command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1444E

CRD Reason code: A CPSM feedback error occurred.

Explanation

A CPSM Feedback command failed.

User response

Use the CPSM return, reason, and error codes to determine the cause.

CRRZA1445E

CRD Reason code: An error occurred while running the DISCARD command.

Explanation

A Discard command failed.

User response

Use the CICS RESP and RESP2 codes to determine the cause of the failure.

CRRZA1446E

CRD Reason code: A CPSM connection authorization error occurred.

Explanation

A CPSM Connect command failed because the user ID did not have authorization to issue the command.

User response

Check with the security administrator.

CRRZA1447E

CRD Reason code: The CPSM CICSPlex name is not in the repository.

Explanation

CICSPlex SM is installed but the CICSPlex SM name is not in the CRD repository.

User response

The CICS system programmer should use Application Deployment Manager to provide the CICSPlex name to the CRD repository.

CRRZA1448E

CRD Reason code: The CPSM CICS system name not in the topology data space.

Explanation

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.

User response

Correct the name in the Applid field.

CRRZA1449W

CRD Reason code: The module size is the same after a NEWCOPY command.

Explanation

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.

User response

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.

CRRZA1450E

CRD Reason code: The CICS release level does not support the request.

Explanation

Certain requests require function not supported in all levels of CICS.

User response

No action is required.

CRRZA1454E

CRD Reason code: The CICS program has abnormally ended.

Explanation

The CRD server has abnormally ended.

User response

Contact Customer Support and refer to the handle abend code returned with the message.

CRRZA1455E

CRD Reason code: A CICS program link failure occurred.

Explanation

A Program Link command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.

CRRZA1456E

CRD Reason code: Resource list START failure

Explanation

An Inquire resource Start Browse command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.

CRRZA1457E

CRD Reason code: Resource list NEXT failure

Explanation

Use the accompanying CICS response code to determine the cause. An Inquire resource Next command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.

CRRZA1458E

CRD Reason code: Resource list END failure

Explanation

An Inquire resource End Browse command failed.

User response

Try the operation again. If the condition persists, contact Customer Support.

CRRZA1459E

CRD Reason code: An error occurred while reading the manifest file.

Explanation

An attempt to read the manifest repository failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. Use the accompanying CICS response codes to determine the cause.

CRRZA1460E

CRD Reason code: An error occurred while writing the manifest file.

Explanation

An attempt to write to the manifest repository failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. Use the accompanying CICS response codes to determine the cause.

CRRZA1461E

CRD Reason code: An error occurred while rewriting the manifest file.

Explanation

An attempt to rewrite to the manifest repository failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. Use the accompanying CICS response codes to determine the cause.

CRRZA1462E

CRD Reason code: Manifest START failure

Explanation

An Inquire resource Start Browse command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.

CRRZA1463E

CRD Reason code: Manifest NEXT failure

Explanation

An Inquire File Next command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.

CRRZA1464E

CRD Reason code: Manifest PREVIOUS failure

Explanation

An Inquire File Prev command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists contact Customer Support.

CRRZA1465E

CRD Reason code: Manifest END failure

Explanation

An Inquire File End Browse command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists, contact Customer Support.

CRRZA1466E

CRD Reason code: An error occurred while deleting the manifest file.

Explanation

A Delete File command failed.

User response

Use the accompanying CICS response code to determine the cause. Try the operation again. If the condition persists, contact Customer Support.

CRRZA1467E

CRD Reason code: The manifest is checked out by a developer.

Explanation

A retrieve request was issued for a manifest, but the manifest was checked out by a developer.

User response

Request that the developer export the checked out manifest back to the repository and try the operation again.

CRRZA1468E

CRD Reason code: The manifest is checked out by a system programmer.

Explanation

A retrieve request was issued for a manifest, but the manifest was checked out by a system programmer.

User response

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.

CRRZA1469E

CRD Reason code: The manifest is checked out by another system programmer.

Explanation

A retrieve request was issued for a manifest, but the manifest was checked out by another system programmer.

User response

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.

Installation indicators for CICS management tools

The following messages indicate whether CICSPlex System Manager (CPSM) or CICS Configuration Manager (CCM) or both are installed.

CRRZA1500I

CPSM Indicator: CPSM is not installed.

Explanation

CICSPlex System Manager is not installed.

User response

Install CICSPlex System Manager if you want it installed. Otherwise no action is required.

CRRZA1501I

CPSM Indicator: CPSM is installed.

Explanation

CICSPlex System Manager is installed.

User response

No action is required.

CRRZA1502I

CCM Indicator: CCM is not installed.

Explanation

CICS Configuration Manager is not installed.

User response

No action is required.

CRRZA1503I

CCM Indicator: CCM is installed.

Explanation

CICS Configuration Manager is installed.

User response

No action is required.

CICS resource definition authorization indicator

The following messages indicate whether the CICS system programmer has authorized a CICS resource type to be installed:

CRRZA1504E

CRD Resource Authorization: Not authorized

Explanation

You are not authorized to access the requested CICS resource.

User response

Try a different resource, or check with your CICS administrator.

CRRZA1505I

CRD Resource Authorization: Authorized

Explanation

You are authorized to access the specified CICS resource.

User response

No action is required.

Resource Definition Editor messages

The messages in this section are issued by the Resource Definition Editor.

CRRZA1600W

{0}({1}) was found already installed on {2}; a PHASEIN command will be issued.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
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.

User response

Check for possible mismatch between the resource definition in the manifest and the installed resource definition.

CRRZA1601I

{0}({1}) does not have a naming conflict on {2}; installation is being attempted.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
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.

User response

No action is required.

CRRZA1602W

{0}({1}) does not exist on region {3}. The {2} action could not be performed.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of action
{3}
Name of region
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.

User response

Check that the correct resource name was specified in the manifest.

CRRZA1603I

{0}({1}) was successfully installed on {2}.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
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.

User response

No action is required.

CRRZA1604W

{0}({1}) was not successfully installed on {2}.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
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.

User response

Double-clicking this message in the problem area opens the Resource Definition Editor for the named resource where offending resource attributes are flagged.

CRRZA1605I

{0}({1}) exists on region {2}. The {3} action was successfully performed.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
{3}
Name of action
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.

User response

No action is required.

CRRZA1606W

{0}({1}) exists on region {2}. The {3} action encountered errors.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
{3}
Name of action
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.

User response

Check any associated messages to determine the problem.

CRRZA1607W

{0}({1}) was found already installed on {2}.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
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.

User response

Check possible mismatch between the resource definition in the manifest and the installed resource definition.

CRRZA1608I

{0}({1}) was successfully installed on {2}; a PHASEIN command will be issued.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
The named resource was successfully installed in the CICS region. This message can be issued for a map set or program.

User response

No action is required.

CRRZA1609I

Manifest file {0} was successfully exported to {1}.

Explanation

{0}
Manifest file name
{1}
Name of region
The named manifest was successfully exported to the CICS region.

User response

No action is required.

CRRZA1610W

The size of the {0} ({1}) load module did not change after a PHASEIN command was processed on {2}.

Explanation

{0}
Resource name
{1}
Resource type
{2}
Name of region
A request to phase-in a program or map set completed successfully. However, the load module size did not change.

User response

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.

CRRZA1611E

Manifest file {0} could not be exported to {1}. The user is {3}. The reason: {2}

Explanation

{0}
Manifest file name
{1}
Name of region
{2}
Reason
{3}
User ID
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.

User response

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.

CRRZA1612I

CICS resource definition {0} exists on CICS region {1}. The DISCARD action was successfully performed.

Explanation

{0}
Resource name
{1}
Name of region
The named resource was successfully discarded from the CICS region.

User response

No action is required.

CRRZA1613E

CICS resource definition {0} does not exist on CICS region {1}. The DISCARD action could not be performed.

Explanation

{0}
Resource name
{1}
Name of CICS region
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.

User response

No action is required.

CRRZA1614E

CICS resource definition {0} {1} is not a valid resource type for a DISCARD action. The DISCARD action could not be performed.

Explanation

{0}
Resource name
{1}
Resource type
An attempt was made to discard a resource. However, the resource type was not DB2TRAN, DOCTEMPLATE, FILE, MAPSET, PROCESSTYPE, PROGRAM, TDQUEUE, or TRANSACTION.

User response

Insure the resource is valid for discard.

CRRZA1615E

CICS resource definition {0} could not be discarded on CICS region {1}.

Explanation

{0}
Resource name
{1}
Name of CICS region
An attempt was made to discard a resource. However, an error occurred.

User response

Check the error log to determine the specific error.

CRRZA1616E

The {2} action encountered errors for {0} ({1}).

Explanation

{0}
A resource type
{1}
A region name
{2}
The name of an action
The {2} action issued for a resource type of {0} encountered errors on region {1}.

User response

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.

CRRZA1617E

The {0} action is not available when using a connection to the CICS Resource Definition server. (The resource type is {1}.) If other connection types are available, use the Connections preference page to connect to a different connection type.

Explanation

{0}
The name of an action
{1}
A resource type
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.

User response

Use a different type of connection to access CICS Explorer functions. Connections are defined in the Connections section of the preference page, available in the Windows pull-down menu.

CRRZA1618I

A PHASEIN action was successfully performed in place of NEWCOPY for program {0} on region {2}.

Explanation

{0}
The name of a program
{2}
The name of a region
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.

User response

In most cases, you do not need to take any action. If you need to use NEWCOPY instead of PHASEIN, use a different type of connection to access CICS Explorer functions. Connections are defined in the Connections section of the preference page, available in the Windows pull-down menu.

CRRZA1619W

A PHASEIN action was attempted for program {0} in place of NEWCOPY on region {2} but did not complete successfully.

Explanation

{0}
Program name
{2}
Region name
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.

User response

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.

Validation messages

CRRZA2001E

The data set or folder {0} does not exist.

Explanation

{0}
The name of a data set or folder
An error was encountered while performing the specified action.

User response

Verify that the data set or folder that is being accessed exists on the file system.

CRRZA2002E

The member or file {0} does not exist.

Explanation

{0}
The name of a data-set member or file
An error was encountered while performing the specified action.

User response

Verify that the data-set member or file that is being accessed exists on the file system.

CRRZA2003E

The member or file {0} already exists in the data set or folder: {1}

Explanation

{0}
The name of a data-set member or file
{1}
The name of a data set or folder
An error was encountered while performing the specified action.

User response

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.

CRRZA2004E

An error was encountered while creating the member or file {0} in the data set or folder: {1}

Explanation

{0}
The name of a data-set member or file
{1}
The name of a data set or folder
An error was encountered while performing the specified action.

User response

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.

CRRZA2005E

An error was encountered while retrieving the member or file {0} from the data set or folder: {1}

Explanation

{0}
The name of a data-set member or file
{1}
The name of a data set or folder
An error was encountered while performing the specified action.

User response

Verify that the data set or folder exists and that you have permission to read members or files.

Manifest messages

CRRZA2006I

A new manifest file was created in the z/OS project named {0}. You can edit the new manifest by selecting {1} from the z/OS project pop-up menu.

Explanation

{0}
The name of a z/OS project
{1}
Deploy CICS Resources, a specific option that is displayed when you right-click a z/OS project name
A new manifest file was created.

User response

No action is required.

CRRZA2007E

An error was encountered during a file save operation: {0}

Explanation

{0}
The name of a file
Due to the error displayed in the message the file could not be saved.

User response

Retry the action or check the error log for more details.

CRRZA2008I

Editor open failed for {0}.

Explanation

{0}
The name of a file
The manifest editor could not be opened correctly, likely due to invalid file contents.

User response

Retry the action or check the error log for more details.

CRRZA2009I

Manifest {0} could not be created.

Explanation

{0}
The name of a manifest
The manifest file could not be created.

User response

Retry the action or check the error log for more details.

Messages for BMS Screen Designer (BMS Map Editor)

These are the messages that pertain to the BMS Screen Designer (BMS Map Editor) in Rational Developer for System z.

CRRZB0136E

Errors occurred.

CRRZB0137E

The field name is a duplicate.

CRRZB0138E

The length of the field name exceeds 30 characters.

Explanation

The length of a field name cannot exceed 30 characters.

User response

Specify a field name whose length is 30 or fewer characters.

CRRZB0139E

The field name contains an invalid @ character.

Explanation

A field name cannot contain the @ character.

User response

Specify a field name that does not contain the @ character.

CRRZB0140E

The field name contains one or more spaces.

Explanation

A field name cannot contain spaces.

User response

Specify a field name that does not contain a spaces.

CRRZB0141E

The field name does not start with an alphabetic character.

Explanation

The field name must start with an alphabetic character.

User response

Choose a field name that starts with an alphabetic character.

CRRZB0142E

The length of the initial value exceeds the field length.

Explanation

The length of the initial value cannot exceed the field length.

User response

Specify an initial value whose length does not exceed the field length.

CRRZB0143E

The row is empty.

Explanation

A row cannot be empty.

User response

Specify content for the row.

CRRZB0144E

The column is empty.

Explanation

A column cannot be empty.

User response

Specify content for the column.

CRRZB0145E

The row value is not valid.

Explanation

The value used for the row is not allowed.

User response

Change the value to an allowed entry.

CRRZB0146E

The column value is not valid.

Explanation

The value used for the column is not allowed.

User response

Change the value to an allowed entry.

CRRZB0147E

Row or column values are not valid.

Explanation

The value used for the row or column is not allowed.

User response

Change the value to an allowed entry.

CRRZB0148E

The field position or length is not valid.

Explanation

The value used for the field position or length is not allowed.

User response

Change value to an allowed entry.

CRRZB0149E

The group name exceeds 30 characters.

Explanation

A group name cannot exceed 30 characters.

User response

Specify a group name whose length is 30 or fewer characters.

CRRZB0150E

An OCCURS value is specified when a group name is specified.

Explanation

You cannot specify an OCCURS value if a group name is specified.

User response

Specify either an OCCURS value or a group name.

CRRZB0151E

The field name contains an invalid character not supported by the Mapset language.

Explanation

The characters used in field names must conform to the character set supported by the programming language of the application using the map.

User response

Refer to the appropriate Language Reference manual for information about supported characters.

CRRZB0153E

The name contains one or more spaces.

Explanation

A name cannot contain spaces.

User response

Specify a name that does not contain spaces.

CRRZB0154E

The map name is a duplicate.

Explanation

The map name must be unique.

User response

Specify a unique map name.

CRRZB0155E

The length of the map name exceeds 30 characters.

Explanation

The length of a map name cannot exceed 30 characters.

User response

Specify a map name whose length is 30 or fewer characters.

CRRZB0156E

The map name contains an invalid @ character.

Explanation

A map name cannot contain the @ character.

User response

Specify a map name that does not contain the @ character.

CRRZB0157E

The row is not a numeric value.

Explanation

A row should be a numeric value.

User response

Specify a row that is a numeric value.

CRRZB0158E

The column is not a numeric value.

Explanation

A column should be a numeric value.

User response

Specify a numeric value for the column.

CRRZB0182E

No column is defined.

Explanation

At least one column must be defined.

At least one column must be defined.

User response

Define a column.Define a column.

CRRZB0183E

The total width exceeds the defined table width.

CRRZB0192E

No map has been selected.

Explanation

You must select at least one map.

User response

Select one or more maps.

CRRZB0270E

An error occurred when creating a nested text editor.

CRRZB0271E

The input is not valid; it must be IFileEditorInput.

CRRZB0272W

This map set will not assemble correctly. A map must be specified for this map set.

Explanation

The map set does not contain any maps.

User response

Using the palette associated with the editor, select the map, and then select the design canvas to create a map.

CRRZB0273W

This map set will not assemble correctly. At least one field must be specified for each map.

Explanation

A map in the map set does not contain any fields.

User response

Using the palette associated with the editor, select a field and then select the design canvas to create a field.

CRRZB0296E

The specified map set name is not valid.

Explanation

A map set name that contains one or more invalid characters was specified.

User response

Specify a map set name that contains any of the following characters: letters; digits; the symbols #, $, and @

CRRZB0297E

No name has been specified for the map set.

Explanation

A name must be specified for the map set.

User response

Specify a name for the map set.

CRRZB0299E

The file name does not end in ".{0}".

Explanation

The file name must end in the particular file-name extension.

User response

Specify a file name that ends in the required file-name extension.

CRRZB0306E

No valid location is selected.

Explanation

A valid location must be selected.

User response

Select a valid location.

CRRZB0360E

No valid field name is entered.

Explanation

You must enter a valid field name.

User response

Enter a valid field name.

CRRZB0361E

No valid input field length is specified.

Explanation

You must specify a valid input field length.

User response

Specify a valid input field length.

CRRZB0362E

No valid label field length is specified.

Explanation

You must specify a valid label field length.

User response

Specify a valid label field length.

CRRZB0363E

The length of the fields is greater than {0}.

Explanation

The length of the fields cannot be greater than a particular value.

User response

Specify a length that is not greater than the limit.

CRRZB0364I

A portion of the caption will be trunctated.

CRRZB0367I

A portion of the initial value will be truncated.

CRRZB0377I

A dynamic Web project has not been created.

Explanation

You must create a dynamic Web project first.

User response

Create a dynamic Web project.

CRRZB0381I

It is recommended that you save this file. Would you like to save it now?

CRRZB0396E

No map has been selected.

Explanation

You must select at least one map.

User response

Select one or more maps.

CRRZB0401E

The number of rows exceeds {0} rows.

Explanation

The number of rows cannot exceed a certain number of rows.

User response

Specify a number of rows that does not exceed the maximum.

CRRZB0402E

The defined number of rows is not an integer.

Explanation

The defined number of rows must be an integer.

User response

Define the number of rows to be an integer.

CRRZB0403E

Column {0} has an invalid field prefix defined.

Explanation

The prefix defined for a particular column is not valid.

User response

Specify a valid field prefix.

CRRZB0404W

The total width exceeds the defined table width. {0} characters will be truncated.

Explanation

The content of the table is too wide for the table.

User response

Make the table wider or the contents narrower.

CRRZB0441E

An invalid value was specified for an OCCURS clause. Enter a numeric value between 1 and 99.

Explanation

An OCCURS clause entry has an invalid value.

User response

Determine the position of the invalid value and enter a numerical value between 1 and 99.

CRRZB0442E

The field length is not numeric and between 1 and 99.

Explanation

The field length should be numeric and between 1 and 99.

User response

Specify a numeric field length in the range 1 to 99.

CRRZB0443E

The field distance is not between 1 and 99.

Explanation

The field distance must be between 1 and 99.

User response

Specify a field distance in the range 1 to 99.

CRRZB0444E

The dimensions of the structure exceed the available space.

Explanation

The structure is too big.

User response

Make the structure smaller.

CRRZB0448W

The field positions specified will cause overlapping.

Explanation

The values entered for the field positions overlap.

User response

Enter values that do not overlap.

CRRZB0449E

The BMS file name is a duplicate.

Explanation

The value entered for the BMS file is already in use.

User response

Specify a unique file name.

CRRZB0450I

{0} was added to the MVS subproject {1}.

Explanation

Something was added to an MVS subproject.

User response

No user response is required.

CRRZB0455I

A symbolic map has been created.

CRRZB0456I

The symbolic map file has been created.

CRRZB0457E

The file name is not valid.

Explanation

The specified file name is not valid.

User response

Specify a valid file name.

CRRZB0458E

A duplicate file name was specified.

Explanation

The specified file name has already been used.

User response

Specify a unique file name.

CRRZB0459E

The initial value can only contain numeric characters for a Numeric only field.

CRRZB0460E

The first character in the alternate map name entered is invalid.

CRRZB0466I

A file has been added to the MVS subproject.

Messages for Common Access Repository Manager (CARMA)

These are the messages that pertain to the Common Access Repository Manager (CARMA) in Rational Developer for System z.

CRRZC1010E

Invalid member Id search parameter: null or ""

Explanation

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

User response

Refresh the parent container and try again.

CRRZC1100E

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

Explanation

The file was not transferred in the proper format.

User response

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

CRRZC1101E

Custom actions are not available: Not synchronized

Explanation

the CARMA and RAM connections are no longer synchronized.

User response

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

CRRZC1102E

Custom actions are not available: Not synchronized

Explanation

the CARMA and RAM connections are no longer synchronized.

User response

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

CRRZC1103E

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

Explanation

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

User response

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

CRRZC1201E

The RAM connect method is disabled.

Explanation

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

User response

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

CRRZC1202E

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

Explanation

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

User response

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

CRRZC1300E

The CARMA Transport Service was not initiated.

Explanation

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

User response

Restart the workbench with the -clean flag.

CRRZC1304E

Problems loading configuration for '{0}'

Explanation

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

User response

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

CRRZC1400E

The Transport Layer connection was not created properly.

Explanation

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

User response

Restart the workbench with the -clean flag.

CRRZC1402E

Could not find the Repository Instances because CARMA is not properly connected.

Explanation

Your CARMA connection is no longer working.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC1403E

The CARMA transport service could not be accessed.

Explanation

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

User response

Restart the workbench with the -clean flag.

CRRZC1404E

Could not access Repository transport service: {0}

Explanation

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

User response

Restart the workbench with the -clean flag.

CRRZC1450E

The Repository Managers could not be loaded because CARMA is not properly connected.

Explanation

Your CARMA connection is no longer working.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC1490W

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

Explanation

If a transport layer has an invalid priority, then the transport layer will not be loaded.

User response

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

CRRZC1501E

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

Explanation

CARMA is no longer associated with the RSE connection.

User response

Delete the CARMA connection and Create a new CARMA connection.

CRRZC1502E

Could not load the TransportServiceFactory extension

Explanation

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

User response

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

CRRZC1550W

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

Explanation

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

User response

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

CRRZC1551W

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

Explanation

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

User response

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

CRRZC1601W

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

Explanation

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

User response

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

CRRZC1602W

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

Explanation

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

User response

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

CRRZC2001E

Could not locate the CARMA Project for temporary downloads.

Explanation

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

User response

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

CRRZC2002E

An error occurred creating and opening the CARMA download project.

Explanation

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

User response

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

CRRZC2003E

An error occurred retrieving the file from the server.

Explanation

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

User response

Check error log for accompanying messages.

CRRZC2004E

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

Explanation

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

User response

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

CRRZC2005E

The Temporary element type is not valid.

Explanation

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

User response

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

CRRZC2007E

Error uploading file: {0}

Explanation

There was an error uploading a file to CARMA.

User response

Disconnect from CARMA, reconnect, and try again.

CRRZC2008E

The CARMA command timed out. The operation was cancelled.

Explanation

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

User response

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

CRRZC2009E

Error uploading file: {0}

Explanation

There was an error uploading the file.

User response

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

CRRZC2010E

Error uploading file: {0} {1}

Explanation

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

User response

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

CRRZC2011E

The Key to find is not set.

Explanation

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

User response

Please report this error to technical support.

CRRZC2012E

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

Explanation

The file could not be uploaded as the specified line number is longer than the line record length.

User response

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

CRRZC2013E

Error uploading file: {0} {1}

Explanation

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

User response

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

CRRZC2014I

Interrupted while waiting for upload return

Explanation

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

User response

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

CRRZC2017E

Error uploading file: {0}

Explanation

There was an error uploading the text file.

User response

Disconnect from CARMA, reconnect and try again.

CRRZC2018E

The LRecl is not formatted correctly: {0}

Explanation

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

User response

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

CRRZC2027E

Error uploading file: {0}

Explanation

There was an error uploading the binary file.

User response

Disconnect from CARMA, reconnect and try again.

CRRZC2044E

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

Explanation

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

User response

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

CRRZC2070E

StatusChangeListener.{0} Communications Diagnostic started.

Explanation

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

User response

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

CRRZC2071E

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

Explanation

This message provides the diagnostic information for message CRRZC2070E.

CRRZC2072E

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

Explanation

This message provides the diagnostic information for message CRRZZC2070E.

CRRZC2073E

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

Explanation

This message provides the diagnostic information for message CRRZZC2070E.

CRRZC2074E

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

Explanation

This message provides the diagnostic information for message CRRZZC2070E.

CRRZC2075E

StatusChangeListener.ICommunicationsDiagnostic exception

Explanation

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

User response

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

CRRZC2101E

An object found in the DataStore is not valid.

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2102E

An object found in the DataStore is not valid.

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2103E

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

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2104E

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

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2105E

CARMA Transport State Exception: The Member Information referenced by key ({0}) was not found.

Explanation

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

User response

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

CRRZC2106E

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

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2107E

The temporary element was not created properly.

User response

Disconnect you CARMA connection, reconnect, and try again.

CRRZC2108E

The Datastore Transport could not be synchronize to CARMA. Recreate your connection.

Explanation

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

User response

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

CRRZC2109E

The command could not be located: {0}

Explanation

The CARMA command could not be located on the host.

User response

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

CRRZC2110E

The File transfer conversion mapping is not set.

Explanation

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

User response

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

CRRZC2111E

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

Explanation

The host side temporary cache of the resource is missing.

User response

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

CRRZC2112E

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

Explanation

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

User response

Modify the length of the line and save again.

CRRZC2113E

Could not initialize. CARMA is not connected.

Explanation

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

User response

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

CRRZC2114E

Cannot create a temporary element for the CARMA Resource: {0}

Explanation

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

User response

Refresh the resources parent, and try again.

CRRZC2115E

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

Explanation

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

User response

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

CRRZC2116E

The CARMA connect operation was not successful.

Explanation

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

User response

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

CRRZC2117E

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

Explanation

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

User response

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

CRRZC2118W

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

Explanation

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

User response

No user action is necessary.

CRRZC2119E

The CARMA disconnect operation was not successful.

Explanation

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

User response

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

CRRZC2122E

Could not execute {0}: {1}

Explanation

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.

User response

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

CRRZC2123E

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

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2124E

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

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2126E

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

Explanation

The host returned an invalid type of object for CARMA.

User response

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

CRRZC2128E

Could not retrieve the member contents from CARMA.

Explanation

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

User response

Check the error log for additional messages.

CRRZC2129E

Could not upload the file to the host.

Explanation

There was an error uploading the file to the host.

User response

Follow the user response in the additional message provided.

CRRZC2200E

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

Explanation

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.

CRRZC2201E

CARMA Initialization is not supported.

Explanation

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

User response

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

CRRZC2202E

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

Explanation

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

User response

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

CRRZC2203E

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

Explanation

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

User response

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

CRRZC2205E

Binary Transfer is not supported.

Explanation

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

User response

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

CRRZC2220E

CARMA is not available on the specified host.

Explanation

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

User response

Contact your system programmer and report the the problem. For information on installation and configuration, see the Rational Developer for System z Host Configuration Guide (SC23-7658).

CRRZC2230E

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

Explanation

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

User response

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

CRRZC2300W

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

Explanation

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

User response

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

CRRZC2301E

The connection alias name is not specified.

Explanation

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

User response

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

CRRZC2301W

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

Explanation

CARMA is no longer associated with the RSE connection.

User response

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

CRRZC2302E

Could not locate connection with alias '{0}'

Explanation

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

User response

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

CRRZC2303E

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

Explanation

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

User response

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

CRRZC2304E

Could not find Repository Manager ({0}) in the DataStore.

Explanation

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

User response

Disconnect, reconnect, and refresh CARMA.

CRRZC2305E

Could not find Repository Instance {0} in the DataStore.

Explanation

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

User response

Disconnect, reconnect, and refresh the repository manager.

CRRZC2401E

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

Explanation

The default value set in the configuration VSAM is not of the proper type.

User response

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

CRRZC2402E

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

Explanation

The default value set in the configuration VSAM is not of the proper type.

User response

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

CRRZC2403E

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

Explanation

The default value set in the configuration VSAM is the wrong type.

User response

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

CRRZC2405E

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

Explanation

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

User response

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

CRRZC2406E

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

Explanation

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

User response

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

CRRZC2407E

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

Explanation

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

User response

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

CRRZC2410E

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

Explanation

The length set for the parameter in the VSAM configuration is not a valid number.

User response

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

CRRZC2900W

Could not parse the CARMA miner version: {0}

Explanation

Could not parse the CARMA

User response

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

CRRZC2901W

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

Explanation

CARMA has been configured not load the repository manager.

User response

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

CRRZC2902E

RAM disconnect Unsupported: Could not disconnect from the RAM.

Explanation

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

User response

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

CRRZC2903E

A RAM termination exception occurred.

Explanation

An error occurred when disconnecting the RAM.

User response

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

CRRZC2904I

Requesting file download to: {0}

Explanation

Informational log message providing the local file system to which a file is downloaded..

CRRZC2905I

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

Explanation

Informational message providing the trace level of the connection.

CRRZC2950E

Attempting to compare {0} with remote encountered an error.

Explanation

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

User response

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

CRRZC2951E

Attempting to compare {0} with remote encountered an error.

Explanation

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

User response

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

CRRZC5000E

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

Explanation

A subproject can only be associated with one repository instance. This error message shouldn't appear in versions 8.0.1 or later.

User response

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

CRRZC5001E

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

Explanation

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

User response

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

CRRZC5002E

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

Explanation

CARMA unexpectedly lost connection to the host during an extract.

User response

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

CRRZC5003E

Multiple items can only be extracted to a PDS.

Explanation

,

User response

CRRZC5010E

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

Explanation

During an extract from CARMA, the host resource could not be found after the RAM was instructed to create it.

User response

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

CRRZC5100E

All the resources could not be copied into the RAM.

Explanation

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

User response

Verify which resources did not copy into the ram and retry – also check the log for messages regarding the resources that did not copy successfully.

CRRZC5101E

Could not locate the CARMA resource associated with '{0}'.

Explanation

The mapping between the resource and the CARMA resource is incorrect.

User response

Reassociate the resource with CARMA.

CRRZC5102E

Could not copy the resource: {0}

Explanation

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

User response

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

CRRZC5103E

Could not copy the resource: {0}

Explanation

CARMA unexpectedly lost connection to the host during extract.

User response

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

CRRZC5111E

Remote project error. Could not create a z/OS project resource: {0}

Explanation

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

User response

Disconnect from RSE and reconnect, then try extracting again.

CRRZC5200E

The project properties could not be retrieved for all members.

Explanation

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

User response

Check for associated error messages and follow their user response.

CRRZC5201E

Could not locate the CARMA resource associated with '{0}'.

Explanation

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

User response

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

CRRZC5202E

Could not retrieve the properties for resource: {0}

Explanation

The mapping between the resource and the CARMA resource is incorrect.

User response

Reassociate the resource with CARMA.

CRRZC5303E

Could not retrieve the properties for resource: {0}

Explanation

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

User response

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

CRRZC5950E

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

Explanation

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

User response

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

Client messages for Enterprise Service Tools

These are the client messages that pertain to Enterprise Service Tools (EST) in Rational Developer for System z.

CRRZE2000E

An internal error has occurred. See the error log for more details.

Explanation

The host editor encountered an internal error.

User response

See the error log.

CRRZE2004E

The host editor could not establish a connection to the remote z/OS system.

Explanation

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.

User response

The connection can fail for any network reason. Therefore:
  1. Verify that the properties of the host connection are correct (see Modifying the properties of a host connection).
  2. Determine whether the remote z/OS system is accessible using another program such as a browser. If not then re-run any programs that you customarily use to prepare your local system for a connection with a remote z/OS system.
  3. Retry the connection (see Opening a host connection).

CRRZE7200E

JCL file {file name} could not be submitted to remote system {host name}.

Explanation

The Generate Runtime Code wizard was unable to submit the JCL file to the remote z/OS system.

User response

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.

CRRZE7201E

Pipeline {pipeline name} could not be scanned: {error message}

Explanation

This error indicates that the specified pipeline was not successfully rescanned.

User response

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 Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).

CRRZE7202E

Program resource {resource name} could not be created on CICS System/Region {resource name}: {error message}

Explanation

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.

User response

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 Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).

CRRZE7204E

Transaction resource {resource name} could not be created on CICS System/Region {resource name}: {error message}

Explanation

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.

User response

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 Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).

CRRZE7206E

Process type resource {resource name} could not be created on CICS System/Region {resource name}: {error message}

Explanation

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.

User response

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:
  1. Find the CICS Resource Definition server reason code and the CICS RESP2 code corresponding to the error. These codes begin with the letters CRRZA (new style) or WZAD (old style).
    • Typically the reason code and the CICS RESP2 code are included in the "{error message}" section of this message.
    • If not, then examine the CICS MSGUSR log for error details and determine the reason code and the CICS RESP2 code.
  2. See the online help for the CICS Resource Definition server reason code and the CICS RESP2 code for steps to resolve the error:

CRRZE7208E

A program, transaction, or process type resource could not be created on CICS System/Region {resource name} because the CICS System/Region {resource name} was not found.

Explanation

This message indicates that the connection to the CICS System/Region selected in the Generate Runtime Code Wizard was not found.

User response

Ensure that the System/Region is defined using the connection preferences and that you are connected.

CRRZE7209E

The service flow pickup directory could not be rescanned, because the selected CICS System/Region is not CICS Transaction Server for z/OS V3.2 or later.

Explanation

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.

User response

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.

CRRZE7210E

An error occurred while creating file {file name} in {location}.

Explanation

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.

User response

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).

CRRZE7211E

The service flow pickup directory could not be rescanned, because the Service Flow Runtime flow scan program DFHMAINS failed.

Explanation

An error occurred while trying to run the CMIT transaction of the CICS Service Flow Runtime because the SFR flow scan program DFHMAINS abended.

User response

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.

CRRZE7212E

The service flow pickup directory could not be rescanned because a program link failure occurred. RESP={value} and RESP2={value}.

Explanation

An error occurred while trying to run the CMIT transaction of the CICS Service Flow Runtime because of a program link failure.

User response

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).

CRRZE7213E

The service flow pickup directory could not be rescanned because the CICS System/Region {resource name} was not found.

Explanation

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.

User response

Ensure that the System/Region was defined using the connection preferences and that the connection is open.

CRRZE7214E

The service flow pickup directory could not be rescanned because the Application Deployment Manager encountered an error. The Application Development Manager reason code is: {code}.

Explanation

This is an internal error and normally should not occur.

User response

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.

CRRZE7218E

The default Application Deployment Manager attributes for RDO programs could not be downloaded.

Explanation

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.

User response

Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).

CRRZE7219E

The default Application Deployment Manager attributes for RDO transactions could not be downloaded.

Explanation

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.

User response

Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).

CRRZE7220E

The default Application Deployment Manager attributes for RDO process types could not be downloaded.

Explanation

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.

User response

Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).

CRRZE7300E

COBOL generation stopped with an error. An unknown exception occurred. Exception text: {error message}

Explanation

There was an internal error generating the runtime code for your service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7301E

COBOL generation stopped with an error. The {node type} named {node name} contains an invalid value for generation property {property name}. Method: {method name}

Explanation

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:
  • Invoke: The node is an Invoke nonterminal node, an Invoke screen operation node, or an Invoke outbound Web service node.
  • Subflow: The node is an Invoke flow node.

User response

To resolve this problem:
  1. Specify a valid value for the generation property in the generation properties file for the flow.
  2. If the problem persists, resolve any errors or warning messages shown in the Problems view.

CRRZE7302E

COBOL generation stopped with an error.There are too many Receive nodes. A flow can contain only one Receive node. Remove the extra Receive nodes and run the Generate Runtime Code wizard again.

Explanation

The flow you are attempting to generate contains more than one Receive node. Only one Receive node is allowed on a flow.

User response

Modify your flow so that it contains only one Receive node.

CRRZE7303E

An ESQL expression is missing or invalid for {node type} node {node name}.

Explanation

This message appears when an ESQL expression associated with a Switch or While node is missing or has invalid contents.

User response

Correct the problems with the referenced ESQL resource and run the Generate Runtime Code wizard again.

CRRZE7304E

COBOL generation stopped with an error. {Resources} were not found in the {containing resource} named {resource name}. Method: {method name}

Explanation

The Generate Runtime Code wizard did not find the specified resources in the specified containing resource as expected.

User response

  1. Provide the missing value and run the Generate Runtime Code wizard again.
  2. If the problem persists, resolve any errors or warning messages shown in the Problems view.

CRRZE7305E

Invalid syntax was found for {language} in an expression in resource {resource name}. Method: {method name}

Explanation

There is a syntax error in one of the ESQL expressions in your service flow.
Note: The {language} element in the error message is always "ESQL".

User response

Open the referenced resource and correct the ESQL expression. The expression preventing successful generation is also listed as an error in the Problems view.

CRRZE7307E

COBOL generation stopped with an error. A field that does not have a BMS name cannot be used in a screen descriptor for screen description {screen description name}. Change the screen descriptors associated with this screen description to use only fields with BMS names.

Explanation

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.

User response

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:
  1. Open the referenced screen message in the screen messages editor.
  2. Select the Screen Descriptions tab.
  3. Expand the relevant screen description.
  4. Identify any descriptor that uses a default field name (such as Field30) instead of a BMS field name (see Default field name).
  5. For each descriptor that uses a default field name, either modify the descriptor so that it uses a BMS field name or else delete the descriptor.
Note: The restriction that screens in a Link3270 Bridge flow cannot use String or Field pattern descriptors for non-BMS-named fields as recognition criteria has been lifted when generating for CICS Transaction Server for z/OS V3.2 or later.

CRRZE7310E

COBOL generation stopped with an error. A message used in node {node name} having node type {node type} is not valid for use as a flow {node type} message. Method: {method name}

Explanation

The COBOL generator could not create a COBOL data structure from one of the messages used by the specified node.

User response

To resolve this problem:
  1. Specify a valid message for the node.
  2. If the problem persists, resolve any errors or warning messages shown in the Problems view.

CRRZE7311E

COBOL generation stopped with an error. The invoke type of node {invoke name} conflicts with the flow type of the flow.

Explanation

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).

User response

Revise or remove from the flow any invoke node having an invoke type that is not supported by the flow type of the flow.

CRRZE7312E

COBOL generation stopped with an error. A Link3270 Bridge flow requires the use of imported BMS maps.

Explanation

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).

User response

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.

Note: This limitation has been removed when the target runtime is CICS Transaction Server for z/OS V3.2 and later (see When the flow type is Link3270 Bridge -- BMS map information).

CRRZE7313E

COBOL generation stopped with an error. The generation of copybook {copybook name} failed in method: {method name}

Explanation

There was an internal error generating the runtime code for your service flow.

User response

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.

CRRZE7315W

String element {element name} in message {message name} does not have a length value. A default length value is assumed.

Explanation

A length value was not specified for the String element. A default length value of 255 was used.

User response

To set a value for the referenced message element:

  1. Use the flow message editor to open the message file that contains the message.

  2. In the editor area, select the Properties tab.

  3. In the Outline view, in the Types hierarchy, select the type specification of the element that was specified in the error message:
    1. In the Outline view, expand Types.
    2. Expand the complex type to which the element specified in the error message belongs.
    3. Within the complex type, expand the element that was specified in the error message.
    4. Within the element, select the simple type xsd:string.

    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.

  4. In the editor area, in the Properties Hierarchy, select Logical properties > Value Constraints.

  5. 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.

CRRZE7316E

COBOL generation stopped with an error. The VectorElement named {element name} is not a Command or a Navigator. Method: {method name}

Explanation

There was an internal error generating the runtime code for your service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7317E

COBOL generation stopped with an error. The VectorElement named {element name} does not contain a Branch. Method: {method name}

Explanation

There was an internal error generating the runtime code for your service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7318E

COBOL generation stopped with an error. The MessageQualifier array has no elements in node {node name}. Method: {method name}

Explanation

There was an internal error generating the runtime code for your service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7319E

COBOL generation stopped with an error. The references array in a Branch is empty for node {node name}. Method: {method name}

Explanation

There was an internal error generating the runtime code for your service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7320E

COBOL generation stopped with an error. A VectorReference was not found in a Branch for node {node name}. Method: {method name}

Explanation

There was an internal error generating the runtime code for your service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7321E

COBOL generation stopped with an error. An element was not found or is null for {resource type} in node {node name}. Method: {method name}

Explanation

This message can appear when a referenced file could not be found.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7322E

COBOL generation stopped with an error. A value was not found or is null for an expression in node {node name}. Method: {method name}

Explanation

There was an internal error generating the runtime code for the service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7323E

COBOL generation stopped with an error. A VectorElement is not of type {resource type} for {resource name}. Method: {method name}

Explanation

There was an internal error generating the runtime code for your Service Flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7324E

An ESQL expression contained more than the maximum number of CAST operations.

Explanation

An ESQL expression can have at most five CAST operations for a particular data type.

User response

Rewrite your ESQL expressions so that they do not have more than the maximum number of CAST operations.

CRRZE7325E

The {resource type} named {resource name} contained elements of ESQL that are not supported by the COBOL generator.

Explanation

Only a subset of the ESQL Operations are supported by the service flow project tools at this time.

User response

Consult the product documentation for the list of supported language elements (see ESQL reference). Remove the unsupported language element from the specified resource.

CRRZE7326E

The flow is too large to document in the service flow properties file. Please componentize segments of the flow as subflows.

Explanation

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.

User response

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.

CRRZE7327E

An unexpected exception occurred because an index was out of bounds. Method: {method name}

Explanation

There was an internal error generating the runtime code for your Service Flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7328E

An unexpected exception occurred involving component {component name}. Exception: {error message}. Method: {method name}

Explanation

There was an internal error generating the runtime code for your Service Flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7329W

The {resource type} in the screen description {screen description name} in screen message {screen message name} is not supported for screen recognition in this context. The {resource type} is ignored.

Explanation

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.

User response

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).

Note: For the Number of Fields, Number of Input Fields, and Fields Checksum descriptors: If the flow type specified in the generation properties file is Link3270 Bridge, and a screen message contains no BMS map information, and the screen description contains one of these three descriptors, then the Generate Runtime Code wizard processes the descriptor differently depending on the target runtime specified in the generation properties file:
(See Handling of Number of Fields, Number of Input Fields, Fields Checksum, and Cursor Position descriptors when the flow type is Link3270 Bridge.)

CRRZE7330W

The field pattern descriptor or string descriptor in screen description {screen description name} in screen message {screen message name} contains invalid data for screen recognition. The field pattern descriptor or string descriptor is ignored.

Explanation

There was an internal error generating the runtime code for your service flow.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7331W

Field {field name} in screen description {screen description name} in screen message {screen message name} has a length greater than the maximum of 160 characters. Screen recognition will be performed using only the first 160 characters.

Explanation

Screen recognition criteria can only be matched against the first 160 characters of any field.

User response

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.

CRRZE7332E

A code page conflict occurred. The host code page for the flow is {code page} but the host code page for screen description {screen description name} is {code page}.

Explanation

The code page of a screen description must be the same as the code page specified in the generation properties file (also see CRRZE7333E).

User response

  • If the code page in the generation properties file is incorrect:
    1. Open the generation properties file in the generation properties editor.
    2. Set the Host Code Page field to the correct code page.
  • If the code page in one or more screen descriptions is incorrect, then follow these steps:
    1. For each screen description that has the incorrect code page:
      1. If the screen description contains BMS map information:
        1. Specify the correct code page in the BMS map.
        2. Re-import the screen description using the Import BMS Map wizard.
      2. If the screen description does not contain BMS map information:
        1. Set the correct code page in Windows > Preferences > Enterprise Service Tools > Service Flow Projects > Code Page Settings.
        2. Re-capture the screen description.
    2. Re-record the service flow.

CRRZE7333E

A code page conflict between screen descriptions occurred. Screen description {screen description name} has a code page of {code page}, but screen description {screen description name} has a code page of {code page}.

Explanation

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).

User response

  1. For each screen description that has the incorrect code page:
    1. If the screen description contains BMS map information:
      1. Specify the correct code page in the BMS map.
      2. Re-import the screen description using the Import BMS Map wizard.
    2. If the screen description does not contain BMS map information:
      1. Set the correct code page in Windows > Preferences > Enterprise Service Tools > Service Flow Projects > Code Page Settings.
      2. Re-capture the screen description.
  2. Re-record the service flow.

CRRZE7334E

An error occurred during Web service generation in {method name}: {error message}

Explanation

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.

User response

See troubleshooting information for single-service projects (see Batch processor).

CRRZE7335E

Web service generation failed. File {file name} was not generated. No additional information is available. Runtime code was successfully generated.

Explanation

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.

User response

See troubleshooting information for single-service projects (see Batch processor).

CRRZE7336E

An error occurred during Web service generation in method {method name}. See the error log for more information.

Explanation

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.

User response

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.

CRRZE7337E

The field named {field name} in the message {message name} generates to the same value as the COBOL PROGRAM-ID {id}. This name conflict will cause a compile error.

Explanation

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.

User response

Follow these steps:
  1. Make either of the following changes:
    • Modify the value of the Program Name specified for the flow in the generation properties file.
    • Rename and Refactor the field in the message.
  2. Re-run the Generate Runtime Code wizard.

CRRZE7338E

The field {field name} in message {message name} generates to the same value as the COBOL keyword {keyword}. This name conflict will cause a compile error.

Explanation

A compile error will occur since the field is named the same as a COBOL reserved word.

User response

Follow these steps:
  1. Rename and Refactor the field in the message.
  2. Re-run the Generate Runtime Code wizard.

CRRZE7339E

Two messages with different data structures have the same name: {message name}. This conflict will cause data reference errors at compile time. Rename and refactor one of the messages.

Explanation

A compile error will occur because references to two different data structures have the same name.

User response

Follow these steps:
  1. Rename and refactor one of the messages.
  2. Run the Generate Runtime Code wizard again.

CRRZE7340E

The {resource type} named {resource name} references the field {field name}. This field does not have a BMS name and therefore cannot be used in a Link3270 Invoke screen operation node.

Explanation

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.

User response

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).

CRRZE7341E

COBOL generation stopped with an error. The maximum COMMAREA length for Invoke node {invoke name} cannot be calculated. Manually enter a valid length value in the generation properties editor.

Explanation

The Generate Runtime Code wizard could not calculate the COMMAREA length automatically for the Invoke nonterminal node specified in the error message.

User response

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:
  1. Select the flow node specified in the error message.
  2. Calculate the maximum length required for the COMMAREA that is passed to the program specified in the Link to Program Name field.
  3. Type the length value into the Maximum COMMAREA Length.

See Generation properties of the LINK with COMMAREA invoke type.

CRRZE7342W

The length {numeric value} of a message specified for use with the Invoke nonterminal node {node name} is greater than the maximum COMMAREA length specified for this node in the generation properties editor. This problem can cause a storage violation error at runtime.

Explanation

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

User response

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.

CRRZE7343W

The flow contains multiple output paths. Web service artifacts can be generated only for a single input path and a single output path. Web service artifacts for the output path resulting in a Reply node were generated, and the other output paths were ignored

Explanation

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:
  • One input point, corresponding to the Receive node in the flow.
  • One output point, corresponding with the Reply node in the flow.

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.

User response

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.

See Restrictions on execution within flows.

CRRZE7400E

COBOL generation stopped with an error. An input message was not found in the interface operation associated with an Invoke outbound Web service node.

Explanation

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.

User response

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.

CRRZE7401E

COBOL generation stopped with an error. Neither an output message nor a fault message were found in the interface operation associated with an Invoke outbound Web service node.

Explanation

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.

User response

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.

CRRZE7500E

Flow playback or HATS macro generation stopped with an error. An unknown exception occurred. Exception text: {0}

Explanation

An unexpected exception occurred during flow playback or during HATS macro generation.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7501E

Flow playback or HATS macro generation stopped with an error. An internal error occurred.

Explanation

An internal error occurred during flow playback or during HATS macro generation.

User response

Resolve any errors or warning messages shown in the Problems view.

CRRZE7502E

Flow playback or HATS macro generation stopped with an error. Switch nodes are not supported in this context.

Explanation

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).

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to make any changes in the flow at all, because Switch nodes are supported in the Service Flow Runtime context.
  • However, if you are required to use flow playback or HATS macro generation, and the Switch node is an essential component, then modify the flow to fix the problem:
    1. Delete the Switch node from the flow.
    2. Modify the flow so that the Switch node is not required.

CRRZE7503E

Flow playback or HATS macro generation stopped with an error. Invoke flow nodes are not supported in this context.

Explanation

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).

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to make any changes in the flow at all, because Invoke flow nodes are supported in the Service Flow Runtime context.
  • However, if you are required to use flow playback or HATS macro generation, and the invoked flow is an essential component, then modify the flow to fix the problem:
    1. Delete the Invoke flow node from the flow.
    2. Modify the flow so that the Invoke flow node is not required.

CRRZE7504E

Flow playback or HATS macro generation stopped with an error. An input message for the flow was not found.

Explanation

The interface operation for the flow does not contain an input message, or the flow is not associated with an interface operation.

User response

  1. Determine why the input message was not found and modify the flow to fix the problem. Some of the possible causes are:
    • The interface operation for the flow does not include an input message.
    • No interface operation is associated with the flow.
    • The interface operation that was previously associated with the flow has been deleted from the flow.
  2. Resolve any errors or warning messages shown in the Problems view.

CRRZE7505E

Flow playback or HATS macro generation stopped with an error. Node {node name} was not found or was null.

Explanation

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.

User response

  1. Determine why the reference to the flow node failed and then modify the flow to fix the problem. Some of the possible causes are:
    • The reference is null.
    • In the reference the name of the flow node is misspelled.
    • The flow node has been renamed or has been deleted from the flow.
  2. Resolve any errors or warning messages shown in the Problems view.

CRRZE7506E

Flow playback or HATS macro generation stopped with an error. An input screen message for the Invoke screen operation node {0} was not found or was null.

Explanation

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.

User response

  1. Determine why the reference to the input screen message failed and then modify the flow to fix the problem. Some of the possible causes are:
    • The screen operation associated with the Invoke screen operation node is invalid.
    • The screen message referenced by the screen operation has been deleted.
  2. Resolve any errors or warning messages shown in the Problems view.

Make sure the specified node is associated with a valid screen operation.

CRRZE7507E

Flow playback or HATS macro generation stopped with an error. An output screen message for the Invoke screen operation node {0} was not found or was null.

Explanation

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.

User response

  1. Determine why the reference to the output screen message failed and then modify the flow to fix the problem. Some of the possible causes are:
    • The screen operation associated with the Invoke screen operation node is invalid.
    • The screen message referenced by the screen operation has been deleted.
  2. Resolve any errors or warning messages shown in the Problems view.

CRRZE7508E

Flow playback or HATS macro generation stopped with an error. Variable updates for flow node {0} could not be generated because variable {1} was not found.

Explanation

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.

User response

  1. Determine why the reference to the variable failed and then modify the flow to fix the problem. Some of the possible causes are:
    • The variable was renamed without refactoring.
    • The variable was moved into a different data structure in the same message, or into another message in the same message file, or into another message file.
    • The variable was deleted.
  2. Resolve any errors or warning messages shown in the Problems view.
  3. If the error still occurs, try rebuilding the service flow project (see Problem determination).

CRRZE7509E

Flow playback or HATS macro generation stopped with an error. Mapping routine {0} contains invalid ESQL syntax.

Explanation

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).

User response

  1. Modify the flow to fix the problem:
    1. In the mapping routine, modify the ESQL syntax so that it is valid for flow playback or in HATS macro generation.
  2. Resolve any errors or warning messages shown in the Problems view.

CRRZE7510W

An unsupported ESQL keyword {0} was found in mapping routine {1} during flow playback or HATS macro generation. The mapping expression was ignored.

Explanation

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).

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to make any changes in the mapping routine at all, because some elements of ESQL are supported in the Service Flow Runtime context (see ESQL reference).
  • However, if you are required to use flow playback or HATS macro generation , and the macro routine is an essential component, then modify the mapping routine to fix the problem:
    1. Delete the ESQL keyword (and any other ESQL elements) from the mapping routine.
    2. Modify the mapping routine or the flow so that the ESQL is not required.

CRRZE7511W

An unsupported mapping transform {0} was found in mapping routine {1} during flow playback or HATS macro generation. The transform was changed to a simple Move.

Explanation

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).

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime environment, you might not need to make any changes in the mapping routine at all, because all mapping transforms are supported in the Service Flow Runtime context (see ESQL reference).
  • However, if you are required to use flow playback or HATS macro generation, and the macro routine is an essential component, then modify the mapping routine to fix the problem:
    1. Remove the unsupported mapping transform.
    2. Modify the mapping routine or the flow so that the unsupported mapping transform is not required.

CRRZE7512W

A unsupported mapping condition was found in mapping routine {0} during flow playback or HATS macro generation. The mapping condition was assumed to be true.

Explanation

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).

User response

To resolve this problem:
  • If you plan to generate runtime code for the Service Flow Runtime, you might not need to make any changes in the mapping routine at all, because mapping conditions are supported in the Service Flow Runtime context (see Working with transforms and conditions).
  • However, if you are required to use flow playback or HATS macro generation, and the macro routine is an essential component, then modify the mapping routine to fix the problem:
    1. Delete the condition from the mapping transform.
    2. Modify the mapping transform or the flow so that the condition not required.

CRRZX0047E

Element WSDL2ELSSpec must include the required attribute fileContainer.

CRRZX0130E

Unique driver file names with prefix {0}, suffix {1}, and maximum length {2} have been exhausted in file container {3}.

Explanation

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.

User response

Specify a shorter prefix in DriverSpec/@fileNamePrefix to allow larger values of the ordinal used to resolve file name collisions.

CRRZX0131W

No language structures were generated for global XSD element {0} referenced by Operation {1} because no mappable elements or attributes were found.

Explanation

{0}
Global element name
{1}
Operation name
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.

User response

If the empty message definition is intentional, no action is required, otherwise correct the XML schema and try again.

CRRZX0132E

No language structures could be generated for global XSD element qualifiedElementName referenced by Fault qualifiedFaultName in Operation operationName because no mappable elements or attributes exist.

Explanation

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.

User response

Add at least one XML element or XML attribute to the complex type referenced by the global XSD element.

Messages for File Manager Integration

These are the messages that pertain to File Manager Integration in Rational Developer for System z.

CRRZF0000I

Moving the data set to the download position.

CRRZF0001I

Stepping through the data set.

CRRZF0002I

Opening an edit session.

CRRZF0003I

Opening a browse session.

CRRZF0004I

Downloading the data set.

CRRZF0005E

An internal error has occurred. The array length is too large.

CRRZF0006E

An exception has occurred while converting a long value to an integer.

CRRZF0007E

The resources cannot be opened.

CRRZF0008E

Formatted Data Editor failed to load the file {0}.

CRRZF0009E

Formatted Data Editor failed to load the template associated with the dataset {0}.

CRRZF0010E

No matching layout found for the records in the dataset.

CRRZF0011E

Formatted Data Editor failed to save the file {0}.

CRRZF0012E

Formatted Data Editor failed to save the file {0} on the host.

CRRZF0013E

Update of changes to the record failed.

CRRZF0014E

Failed to initialize a new record in Formatted Editor.

CRRZF0015E

Cannot move to the specified record.

CRRZF0016I

Number of records searched:{0}

CRRZF0018I

A possible match has been found:{0}

CRRZF0019E

A file can only be opened in one instance of the Formatted Data Editor at a time.

CRRZF0020E

Dataset could not be found.

CRRZF0021E

System is not connected. Please connect to the system and try your action again.

CRRZF0022I

You must save your changes before switching to a different template. Save changes now?

CRRZF2000I

Template Data Editor.

CRRZF2001I

Downloading Template.

CRRZF2002E

An exception occurred while setting the VSAM property value.

CRRZF2003E

A template association error has occurred.

CRRZF2004E

An unexpected exception has occurred.

CRRZF2005E

A core exception has occurred. The current status is: {0}.

CRRZF2006E

An error was detected while loading {0}: {1} : Line {2} Column {3}.

CRRZF2007E

The Template Editor could not open because the template file was not found.

CRRZF2008E

The Template Editor failed to load the file {0}.

CRRZF2009E

The Template Editor could not open due to an internal error.

CRRZF2010E

The Template Editor failed to convert string data to the code page {0}. String: {1}.

CRRZF2011E

The Template Editor failed to save the file {0}.

CRRZF2012E

The Template Editor failed to save the file {0} on the host.

CRRZF2013E

The Template Editor can only be used to edit templates of type BASE or DYNAMIC. The template in file {0} is of type {1}.

CRRZF2014E

The Template Editor failed to validate the layout due to an internal error. {0}

CRRZF2015E

The Create Template wizard failed to load {0}.

CRRZF2016E

The Create Template wizard failed to save the new template.

CRRZF2017E

A template can only be opened in one instance of the Template Editor at a time.

CRRZF2018E

A compilation failure has been reported. Check the File Manager compilation settings in the associated Property Group.

CRRZF2019E

The Update Template wizard failed to save the updated template.

CRRZF4000E

Unable to copy the VSAM cluster. IBM File Manager is either unavailable or this operation is not supported in the current version of IBM File Manager.

CRRZF4001E

The data set could not be copied.

CRRZF4002W

There is a limit of 10 additional SYSLIB data sets. Only {0} of the selected SYSLIB data sets could be added.

CRRZF4003E

{0} is an invalid source for this table. Drag and drop a valid data set into this table.

CRRZF6001E

File Manager is unavailable on the target system. Verify the system configuration settings and try again.

CRRZF6002E

The client failed to send the {0} command to the host.

CRRZF6003E

An exception was generated by an invalid file resource.

CRRZF6004W

The file name is null.

CRRZF6005I

Updating the template.

CRRZF6006E

An incorrect version of File Manager was detected. Version found: {0} Version required: {1}

CRRZF6007E

An incorrect version of the File Manager Integration server was detected. Version found: {0} Version required: {1}

CRRZF6008E

An unknown version of File Manager has been detected.

CRRZF6009E

Multiple errors were reported during this operation.

CRRZF6500I

User ID: {0}

CRRZF6500W

Cannot search. No target Dataset provided.

CRRZF6501I

Port: {0}

CRRZF6502I

CRRZF6502I=CRRZF6502I: File Manager Integration Server Extension Version: {0}

CRRZF6503I

Using the Listener Connection to File Manager.

CRRZF6504E

Unsupported command: {0}.

CRRZF6505E

Cannot connect to File Manager port: {0}.

CRRZF6506E

An error occurred while handling the File Manager command: {0}.

CRRZF6507E

The File Manager extension is not available.

CRRZF6508E

The data provider connection could not be opened.

CRRZF6509E

An error occurred while converting the criteria expression to the host code page.

CRRZF6510E

An exception occurred while converting the version message.

CRRZF6511E

The following code was returned from the template edit request: {0}.

CRRZF6512I

Starting the read thread.

CRRZF6513I

Waiting on the read thread.

CRRZF6514W

Could not read the initial message.

CRRZF6515I

Receiving a response from File Manager.

CRRZF6516I

Additional data is available.

CRRZF6517E

The data set exceeds the maximum size limit and cannot be downloaded.

CRRZF6518E

A response from File Manager was not received.

CRRZF6519E

The response type from File Manager does not match: {0}.

CRRZF6520E

The request was stopped.

CRRZF6521W

The request was interrupted.

CRRZF6522E

An exception occurred while receiving additional data.

CRRZF6523E

An exception occurred while receiving a response from initSession.

CRRZF6524E

The Init session returned the following error code: {0}.

CRRZF6525E

Cannot connect to File Manager.

CRRZF6526E

An IO connection exception occurred.

CRRZF6527E

Could not complete the transaction with File Manager. The transaction has been canceled.

CRRZF6528E

Multiple connections to the same data set or template pair are not supported.

CRRZF6529E

A connection was not found for path: {0}. Verify that the path is valid.

CRRZF6530E

The following request code made to File Manager is invalid: {0}.

CRRZF6531E

File Manager get template request returned error code: {0}.

CRRZF6532E

Data records were returned instead of template records.

CRRZF6533E

A message with an invalid length was received.

CRRZF6534E

The following unexpected exception was received: {0}.

CRRZF6535E

An invalid function was provided to the File Manager listener.

CRRZF6536E

An invalid request was made to the File Manager listener.

CRRZF6537E

An invalid user ID or password was provided to the File Manager listener.

CRRZF6538E

An unknown error occurred while processing the request.

CRRZF6539E

An invalid or unsupported version was specified to the File Manager listener.

CRRZF6540E

The maximum number of File Manager listener clients has been reached. Try again later.

CRRZF6541I

Sending authorization information.

CRRZF6542I

Receiving a TCP/IP connection for the File Manager port communication.

CRRZF6543I

Using File Manager port: {0}.

CRRZF6544W

Not able to connect to the File Manager listener.

CRRZF6545I

Connected to a File Manager listener at port: {0}.

CRRZF6546I

Sending an initialize message to File Manager.

CRRZF6547I

Parsing the authorization response.

CRRZF6548E

The UNIX user authentication request failed.

CRRZF6549W

The following invalid message was received: {0}.

CRRZF6550I

Request number: {0}

CRRZF6551I

Command: {0}

CRRZF6552E

An unexpected data type was received.

CRRZF6553E

An invalid File Manager response was received.

CRRZF6554E

The following invalid record type was received: {0}.

CRRZF6555E

While loading the following template, an invalid number of records were received: {0}.

CRRZF6556E

File Manager error: {0}.

CRRZF6557E

Record not found.

CRRZF6558W

Not enough storage space.

CRRZF6559I

Record OK.

CRRZF6560E

Modification is not allowed on this data set.

CRRZF6561E

Record length error.

CRRZF6562I

Number of records sent.

CRRZF6563E

Failed validation.

CRRZF6564E

The segment failed validation.

CRRZF6565I

Received an invalid offset into the error segment.

CRRZF6566E

Failure code: {0}

CRRZF6567E

Template error.

CRRZF6568E

The initial message length is incorrect.

CRRZF6569E

The message length is set to an incorrect value: {0}.

CRRZF6570E

Invalid connection status. Not connected.

CRRZF6571E

The host name contains invalid characters.

CRRZF6572E

A critical error occurred while saving records.

CRRZF6573E

Total bytes in reply header: {0}

CRRZF6574E

Response offset in header: {0}

CRRZF6575E

The return code was: {0}

CRRZF6576E

Return code was REPROMPT.

CRRZF6577I

Segment bytes: {0}

CRRZF6578E

After allocation, the segment bytes were null.

CRRZF6579E

The FMIEXT.properties file is not configured properly. Ask the system administrator to configure this file.

CRRZF6580E

Could not end the edit session, code: {0}.

CRRZF6581E

Cannot rename the file. The target data set was not provided.

CRRZF6582E

Could not search message: {0}.

CRRZF6583E

Cannot rename a data set without a name.

CRRZF6584E

Could not download the following data set: {0}.

CRRZF6585E

Invalid header received.

CRRZF6586E

An exception occurred while refreshing the contents of the data set.

CRRZF6587W

Cannot start an edit session without a data set name.

CRRZF6588E

Could not open an edit session. The File Manager Integration listener might not be running. Failure code: {0}.

CRRZF6589E

An exception occurred while opening an edit session.

CRRZF6590E

Cannot get data set information without the data set name.

CRRZF6591E

An invalid number of arguments were passed in the version request.

CRRZF6592E

A File Manager Integration server exception occurred while requesting version information.

CRRZF6593E

An invalid value was specified for the segment type: {0}.

CRRZF6594E

An invalid value was specified for the symbol number: {0}.

CRRZF6595E

The expression length does not match.

CRRZF6596E

The request for criteria validation was improperly formed.

CRRZF6597E

Validation failed: {0}

CRRZF6598E

Invalid arguments, input length: {0}

CRRZF6599E

An exception occurred while downloading the contents of the data set.

CRRZF6600E

Cannot reposition. An invalid position change parameter was provided.

CRRZF6601E

An exception occurred while downloading the contents of the template.

CRRZF6602E

Cannot force UserId for authentication.

CRRZF6603E

UserId forced to value: {0}

CRRZF6604E

Error performing Save As operation:

CRRZF6605E

Cannot reposition. No target data set provided.

CRRZF6607E

Could not download the data set: {0}.

CRRZF6608E

An exception occurred while opening a browse session.

CRRZF6609E

FMIEXT.properties file was not found. Ask the system administrator to configure this file.

CRRZF6610E

Could not download the compiled listing for: {0}

CRRZF6611E

An exception occurred while downloading listing contents.

CRRZF6612I

Enabled: {0}.

CRRZF6613E

An exception occurred while downloading the contents of the template.

CRRZF6614W

Cannot perform task, the data set is in use.

CRRZF6615E

An exception occurred while downloading the contents of the template.

CRRZF6616E

The template was not provided.

CRRZF6617E

The workstation path was not supplied.

CRRZF6618E

An exception occurred while downloading the contents of the data set.

CRRZF6619E

Cannot start an edit session without a data set name.

CRRZF6620E

Cannot delete: {0}.

CRRZF6621W

Cannot delete. The target data set was not provided.

CRRZF6623E

Cannot search: {0}.

CRRZF6624E

Cannot copy. The target data set was not provided.

CRRZF6625E

Cannot clone the data set: {0}.

CRRZF6626E

Cannot change the layout: {0}.

CRRZF6627E

An exception occurred while changing layouts.

CRRZF6628E

Cannot upload the data set: {0}.

Messages for the System z LPEX Editor

The following messages pertain to the System z LPEX Editor in Rational Developer for System z.

CRRZG0001E

The editor is unable to find the lexer from the stream.

Explanation

An error has occurred, possibly due to a custom extension or product bug.

User response

If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support.

CRRZG0010E

The editor could not display the message "{0}" at position {1}.

Explanation

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.
{0}
Message text
{1}
The current position in the file that you are editing.

User response

If you are using a custom extension to the editor, disable it. Otherwise, contact IBM Software Support for assistance.

CRRZG0050E

Due to a null parsing job the editor is unable to perform the action.

Explanation

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.

User response

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.

CRRZG0051E

Due to parsing errors the editor is unable to perform the action.

Explanation

The error may occur if the F3 key is used to open a declaration when there is a parsing error.

User response

Resolve any parsing errors and try the process again. If the problem persists, contact IBM Software Support.

CRRZG0052E

Due to an invalid selection the editor is unable to perform the action.

Explanation

The selected item is not valid.

User response

Select a different item.

CRRZG0053E

Due to a null parsing job the editor is unable to perform the action.

Explanation

This error occurs if you try to open the perform hierarchy in an item where parsing did not occur.

User response

Enable tools or annotations and tools. Contact IBM Software Support to report the problem.

CRRZG0054E

Due to parsing errors the editor is unable to perform the action..

Explanation

An error occurred when opening the perform hierarchy because of a parsing error.

User response

Resolve the parsing errors and try the action again. Contact IBM Software Support for assistance.

CRRZG0055E

Due to an invalid selection the editor is unable to perform the action.

Explanation

This occurs if the software is unable to resolve the selected item.

User response

Select a different item. If the problem persists contact IBM Software Support for assistance.

CRRZG0056E

The editor is unable to create a perform graph..

Explanation

The argument passed to the perform graph function is not valid.

User response

Try the function again with a different selection. If the problem persists, contact IBM Software Support for assistance.

CRRZG0057E

An attempt to add a part listener to the workbench failed.

Explanation

Listeners were not registered during startup. This can happen if the software is already running in displayless mode when the product is started.

User response

If the error occurs during normal use, contact IBM Software Support for assistance.

CRRZG0060I

An availability check failed.

Explanation

An unknown error occurred during the availability checking of the Open Declaration action.

User response

Contact IBM Software Support for assistance.

CRRZG0061I

An availability check failed.

Explanation

An error occurred during the availability checking of the Open Perform Hierarchy action.

User response

Contact IBM Software Support for assistance.

CRRZG0062I

An availability check failed.

Explanation

An error occurred during the availability checking of a Refactor action.

User response

Contact IBM Software Support for assistance.

CRRZG0100E

The editor is unable to locate a declaration for {0}.

Explanation

An error while trying to populate or react to a Perform hierarchy and the location of the paragraph is declared cannot be determined.
{0}
The name of the paragraph being referenced.

User response

Verify that the paragraph being referenced has been declared.

CRRZG0101E

The editor is unable to add performee {0} to the perform graph..

Explanation

An incorrect argument was passed to the performgraph function.
{0}
Performee name

User response

Contact IBM Software Support for assistance.

CRRZG0102E

The editor is unable to add a performer to the perform graph, node {0}, with declaration {1}..

Explanation

The argument passed to the performgraph function is not valid.

User response

Contact IBM Software Support for assistance.

Messages for the z/OS Integrated Development Environment (zIDE)

These are the messages that pertain to the z/OS Integrated Development Environment (zIDE) in Rational Developer for System z.

CRRZI0001E

The backup of an existing workspace has failed. Contact your IBM technical support representative.

Explanation

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.

Response

Contact your IBM technical support representative.

CRRZI0002I

A copy of your old workspace has been saved. It can be found at '{0}'.

Explanation

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.

Response

No response is required.

CRRZI0003E

The workspace migration has failed. A backup copy of the original workspace can be found in '{0}'. Contact your IBM technical support representative.

Explanation

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.

Response

Contact your IBM technical support representative.

CRRZI0004I

In IBM WebSphere Developer for zSeries 6.0.1, the Remote Error List view replaces the Problems view. Select Window->Show View->Other...->TPF Toolkit->Remote Error List or Window->Reset Perspective to open this view.

Explanation

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.

Response

Select Window>Show View>Remote Error List or Window>Reset Perspective to open the Remote Error list view.

CRRZI0005E

The {0} environment variable is not set. Set the environment variable in the System Variables table of your operating system's environment variables. The value should point to the Developer for System z installation directory.

CRRZI0006E

The compiler option "CICS({0})" is not applicable for a build operation. Remove the suboption "{0}" and try again.

Explanation

The CICS suboption CTS31, CTS32, or CTS41 was specified for a local build. These suboptions are valid only in the context of syntax check.

Response

If you are performing a local build, remove the CICS suboption CTS31, CTS32, or CTS41.

CRRZI0007E

The compiler option "CICS('CTS32')" is not applicable for a build operation. Remove the suboption "CTS32" and try again.

Explanation

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.

Response

If you are building a local application, remove the CTS32 suboption from the CICS compiler option.

CRRZI0008E

The compiler option "CICS('CTS41')" is not applicable for a build operation. Remove the suboption "CTS41" and try again.

Explanation

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.

Response

If you are building a local application, remove the CTS41 suboption from the CICS compiler option.

CRRZI0009W

Data set {0} may be under SCLM control. To continue, type your user ID for the system.

Explanation

An attempt has been made to delete a data set that might be under control of SCLM.

Response

To continue deleting the data set, type your user ID and password for the SCLM system and click OK.

CRRZI0010I

Resource {0} is under SCLM control. The file will be opened in read-only mode.

Explanation

An attempt has been made to edit a resource that is under control of SCLM.

Response

To edit the resource, access it by using the SCLM Developer Toolkit.

CRRZI0011W

Resource {0} may be under SCLM control. Are you sure you want to proceed?

Explanation

An attempt has been made to delete a resource that might be under control of SCLM.

Response

To continue deleting the resourse, click OK.

CRRZI0012E

{0} is under control of SCLM and cannot be modified.

Explanation

An attempt has been made to modify a resource that is under control of SCLM.

Response

To modify the resource, access it by using the SCLM Developer Toolkit.

CRRZI0013I

An SCLM project definition module is found for {0}.

Explanation

The resource indicated in the message might be under control of SCLM.

Response

No response is required.

CRRZI0014E

The include file cannot be opened until it is added to the current workspace. To import this file, select File -> Import.

Explanation

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.

Response

To add the macro to the current workspace, use the File > Import action.

CRRZI0015E

The macro file cannot be found in the SYSLIB library. Verify that both the file and the library are allocated properly.

Explanation

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.

Response

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:
  1. Edit the property group associated with the resource.
  2. Click the Assembler tab in the property group editor.
  3. Expand the procedure, select the step name, and click Edit in the Step Options area of the page.
  4. Verify that the data set(s) specified in the Macro Libraries field is correct.

CRRZI0016E

The macro file could not be opened. Connect to the system before attempting this action.

Explanation

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.

Response

To connect to the remote system, open the Remote Systems view, select the remote system connection, and click Connect on the pop-up menu.

CRRZI0017I

You must add a corresponding filter for the data set before the member can be added to the project.

Explanation

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.

User response

In the Remote Systems view, select MVS Files, and then select New > Filter to add a filter for the data set name.

CRRZI0018E

The copy library cannot be opened until it is added to the current workspace. To import this file, select File -> Import.

Explanation

You have requested to open a copy library from an edit session, but it has not yet been added to your workspace.

User response

From the menu bar, click File > Import and browse to the copy library location to import it into your workspace.

CRRZI0019E

The copy file cannot be found in the SYSLIB library. Verify that both the file and the library are allocated properly.

Explanation

You have requested to open or browse a remote copy member from an edit session, but the file cannot be found in the SYSLIB.

User response

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.

CRRZI0020E

The copy member could not be opened. Connect to the system before attempting this action.

Explanation

You have requested to open or browse a remote copy member from an edit session, but there is no connection to the remote system.

User response

In the Remote Systems view, select the remote system and click Connect. After a connection is established, try the action again.

CRRZI0021I

No text was highlighted. Highlight the copy member name.

Explanation

You have requested to open a copy member in an edit session, but no copy member was highlighted.

User response

Highlight the copy member name and try the action again.

CRRZI0022E

The selected member cannot be found. Verify that the data set and member exist on the remote system.

Explanation

You have requested to open a data set or partitioned data set member from a JCL edit session, but the file cannot be found.

User response

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.

CRRZI0023I

The selected file '{0}' is already open in another edit session as a stored procedure. As a result, no additional edit session will be opened.

Explanation

You have requested to edit a file that is already open for editing.

User response

Look for the file name in another editor session and edit it in that session.

CRRZI0024I

The selected file '{1}' is already open in the editor under a different project as '{0}'. As a result, no additional edit session will be opened.

Explanation

You have requested to edit a file that is already open for editing.

User response

Look for the file name in another editor session and edit it in that session.

CRRZI0025E

The include file cannot be opened until it is added to the current workspace. To import this file, select File -> Import.

Explanation

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.

Response

To add the include file to the current workspace, use the File > Import action.

CRRZI0026E

The include file cannot be found in the SYSLIB library. Verify that both the file and the library are allocated properly.

Explanation

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.

Response

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:
  1. Edit the property group associated with the resource.
  2. Click the PL/I tab in the property group editor and then select Procedures and Steps.
  3. Expand the procedure, select the step name, and click Edit in the Step Options area of the page.
  4. Verify that the data set(s) specified in the Include Libraries field is correct.

CRRZI0027E

The include file could not be opened. Connect to the system before attempting this action.

Explanation

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.

Response

To connect to the remote system, open the Remote Systems view, select the remote system connection, and click Connect on the pop-up menu.

CRRZI0029I

Local syntax check of a remote file is available only if the file is opened or edited from an MVS subproject.

Explanation

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.

Response

  1. Close the current edit session.
  2. Add the file to an MVS subproject.
  3. Retry the local syntax check request.

CRRZI0030W

The file cannot be saved. Do you want to check the syntax on the last saved copy of this file?

Explanation

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.

Response

Click Yes to perform the syntax check on the cached copy.

CRRZI0031E

This file cannot be deleted because this is an offline remote file that has not been downloaded. To delete the file, you must move the project back online.

Explanation

You have requested to delete a file in an offline project. A remote z/OS project must be in online state before you can delete files from it.

User response

Move the project to online state and try the operation again.

CRRZI0032E

This file cannot be deleted because this is an online remote file and the associated system is not connected. To delete the file, you must connect to the associated system.

Explanation

You have requested to delete a file in a remote project, but you are not connected to the remote system.

User response

Connect to the remote system and try the operation again.

CRRZI0033E

This file cannot be moved because this is an offline remote file that has not been downloaded. To move the file contents you must move the project back online.

Explanation

You have requested to move a file in an offline project. A remote z/OS project must be in online state before you can move files in it.

User response

Move the project to online state and try the operation again.

CRRZI0034E

This file cannot be moved because this is an online remote file and the associated system is not connected. To move the file, you must connect to the associated system.

Explanation

You have requested to move a file in a remote project, but you are not connected to the remote system.

User response

Connect to the remote system and try the operation again.

CRRZI0035E

This file's contents are not available because this is an offline remote file that has not been downloaded. To view the file's contents, you must move the project back online.

Explanation

You have requested to open a file in an offline project. A remote z/OS project must be in online state before you can open files in it.

User response

Move the project to online state and try the operation again.

CRRZI0036E

This file's contents are not available because this is an online remote file and the associated system is not connected. To view the file's contents, you must connect to the associated system.

Explanation

You have requested to open a file in a remote project, but you are not connected to the remote system.

User response

Connect to the remote system and try the operation again.

CRRZI0037E

This file's contents cannot be modified because this is an offline remote file that has not been downloaded. To update the file's contents, you must move the project back online.

Explanation

You have requested to edit a file in an offline project. A remote z/OS project must be in online state before you can edit files in it.

User response

Move the project to online state and try the operation again.

CRRZI0038E

This file's contents cannot be modified because this is an online remote file and the associated system is not connected. To update the file's contents, you must connect to the associated system.

Explanation

You have requested to edit a file in a remote project, but you are not connected to the remote system.

User response

Connect to the remote system and try the operation again.

CRRZI0041E

Could not create IResources for {0}.

Explanation

An error occurred while accessing the contents of a remote resource in a z/OS project.

Response

  1. Check the connection to determine if the project is an online project and then retry the operation.
  2. Clear the remote system cache files by selecting Window > Preferences > Remote Systems > File Cache > Clear Cached Files, and then retry the operation.
  3. Recreate the project.
If the error occurs during normal use, contact your IBM technical support representative to report the problem.

CRRZI0042E

Could not download {0}.

Explanation

Rational Developer for System z failed to download the file from the remote system to the local cache.

Response

Check connection and retry the operation. If the problem still occurs, contact your IBM technical support representative to report the problem.

CRRZI0043E

Could not find file {0}.

Explanation

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.

Response

If the project is online, check the remote system connection and retry the operation. If the problem persists, contact your IBM technical support representative to report the problem.

CRRZI0046E

Could not upload {0}.

Explanation

Rational Developer for System z failed to upload the file from local cache to the remote system.

Response

Check the remote system connection and retry the operation. If the problem still occurs, contact your IBM technical support representative to report the problem.

CRRZI0047E

Could not write to {0}.

Explanation

An error occurred while writing contents to a file in a z/OS project.

Response

Check the remote system connection and retry the operation. If the problem still occurs, contact your IBM technical support representative to report the problem.

CRRZI0048E

{0} is not a valid URL.

Explanation

An error occurred while accessing an internal resource in a z/OS project.

Response

Contact your IBM technical support representative to report the problem.

CRRZI0049E

The class '{0}' is not a valid classifier.

Explanation

An error occurred while creating an internal resource.

Response

Contact your IBM technical support representative to report the problem.

CRRZI0050E

The data type '{0}' is not a valid classifier.

Explanation

An error occurred while creating an internal resource.

Response

Contact your IBM technical support representative to report the problem.

CRRZI0051E

The system '{0}' is currently under host-based control but one or more remote projects associated with the same system already exist in this workspace. The non-host-based projects must be deleted before any host-based projects can be opened.

Explanation

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.

Response

Delete the workstation-based projects. Reconnect to the remote system.

CRRZI0052E

An I/O error occurred while loading the host-based project configuration file: '{0}'.

Explanation

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.

Response

Contact your system administrator.

CRRZI0053E

A workbench error occurred while loading the host-based project configuration file: '{0}'.

Explanation

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.

Response

Contact your system administrator.

CRRZI0054E

An I/O error occurred while loading the host-based project definition file: '{0}'.

Explanation

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.

Response

Contact your system administrator.

CRRZI0055E

Unable to find the project definition file '{0}' specified by the configuration file '{1}'.

Explanation

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.

Response

Contact your system administrator. The error could have one of the following causes:
  • The project definition file does not exist.
  • The path name for the project definition file is specified incorrectly in the configuration file.

CRRZI0056E

A workbench error occurred while loading the host-based project definition file: '{0}'.

Explanation

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.

Response

Contact your system administrator.

CRRZI0058E

An I/O error occurred while loading the host-based subproject definition file: '{0}'.

Explanation

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.

Response

Contact your system administrator.

CRRZI0060E

A workbench error occurred while loading the host-based subproject definition file: '{0}'.

Explanation

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.

Response

Contact your system administrator.

CRRZI0062E

A resource with the name '{0}' already exists in '{1}'. Make sure all the resources have a unique name and try again.

Explanation

An attempt to rename a resource has failed because another resource by that name exists.

Response

Retry the operation using a different name.

CRRZI0063E

The system name '{0}' found in the subproject definition file for subproject '{1}' does not match any currently defined systems.

Explanation

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.

Response

Contact your system administrator to modify the subproject definition file to refer to the correct remote system name.

CRRZI0065E

The subproject definition file for subproject '{0}' did not contain a system name.

Explanation

A subproject has been loaded from a host-based project. The subproject is not associated with a remote system.

Response

Contact your system administrator to modify the subproject definition file to refer to the correct remote system.

CRRZI0066E

The subproject definition file for subproject '{0}' did not contain any system information.

Explanation

A subproject has been loaded from a host-based project. The subproject is not associated with a remote system.

Response

Contact your system administrator to modify the subproject definition file to refer to the correct remote system name.

CRRZI0068I

The JCL member '{0}' is generated in data set '{1}'.

CRRZI0069E

The operation did not complete because resource '{0}' is locked. Another person or program might be using the resource. Retry the operation when the resource is available.

CRRZI0070E

The specified data set for the generated JCL does not exist. Verify the name of the target data set and try again.

CRRZI0071I

A member by this name already exists. Do you want to replace the existing member?

CRRZI0072E

The job submission failed because the job card is incomplete or invalid. Verify the job card and submit the job again.

Explanation

A JCL submission has failed because the job card is incomplete or invalid.

Response

Modify the JCL job card and submit the JCL again. Contact your system administrator for help constructing a valid job card for your site.

CRRZI0073E

The system submitted a job based on your current user ID to perform a syntax check or a build. The status of this job cannot be determined because the JES filter might be incorrect or the job card might be invalid. Create a JES filter that matches this user ID, verify the job card, and try again.

CRRZI0074E

The JES subsystem is not connected. Connect to the subsystem and retry the operation.

Explanation

The JES subsystem is not connected.

Response

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.

CRRZI0075E

The submitted job has ended abnormally.

Explanation

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.

Response

To check the job output, click the job output link. To check the build properties for the resource, click the property group link.

CRRZI0076E

The submitted job ended with a JCL error.

Explanation

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.

Response

To check the job output, click the job output link. To check the build properties for the resource, click the property group link.

CRRZI0077W

The operation has been canceled on the workstation. The job {0} might need to be purged from JES.

Explanation

The execution of a job submission action has been canceled.

Response

To purge the job, do these steps:
  1. In the Remote Systems view, locate the remote system on which the resource you are working with is located.
  2. Expand the remote system connection and then expand JES > My Jobs.
  3. Select the job name indicated in the message and then select Purge from the pop-up menu.

CRRZI0078E

There is no property group associated with the subproject '{0}'. Associate a property group with the subproject and try the operation again.

CRRZI0079I

The alias, or the file it refers to, is already open in the editor.

CRRZI0080W

This action will delete the alias '{0}'. Deleting an alias will not delete the referenced data set. Do you want to proceed?

CRRZI0081W

This data set contains {0} members, and the expansion of the data set might take a long time. Do you want to proceed?

CRRZI0082W

There is 1 line in the file '{0}' on the {1} with contents exceeding the maximum line length (see Details). Saving the file will result in truncation of this line. Do you want to continue?

CRRZI0083W

There are {0} lines in the file '{1}' on the {2} with contents exceeding the maximum line length (see Details). Saving the file will result in truncation of these lines. Do you want to continue?

CRRZI0084W

The file '{0}' is locked. It is either open in another edit session or locked by another user. This file will be opened in read-only mode. Do you want to continue?

CRRZI0085W

Both files are locked. They are either open in other edit sessions or locked by other users. The files will be opened in read-only mode. Do you want to continue?

CRRZI0086W

The file '{0}' has a record format of '{1}' and the file '{2}' has a record format of '{3}'. The record formats do not match. Do you still want to continue?

CRRZI0087W

The file '{0}' has a record length of '{1}' and the file '{2}' has a record length of '{3}'. The record lengths do not match. Do you still want to continue?

CRRZI0088E

The associated subsystem is not connected. Connect to the subsystem and retry the operation.

CRRZI0089I

The data set is of type LIBRARY(PDSE). Compression is not required.

CRRZI0090I

Success

CRRZI0091E

I/O Error

CRRZI0092E

Write failed

CRRZI0093E

Read failed

CRRZI0094E

Write Initialization failed

CRRZI0095E

Read Initialization failed

CRRZI0096E

Dynamic allocation failed.

CRRZI0097E

Open failed

CRRZI0098E

Create a socket failed.

CRRZI0099E

The socket type is not supported by the protocol.

CRRZI0100E

Permission to create a socket of the specified type or protocol is denied.

CRRZI0101E

The protocol is not supported in this domain or this protocol is not supported for this socket type.

CRRZI0102E

The protocol does not allow for the creation of socket pairs.

CRRZI0103E

The address family is not supported.

CRRZI0104E

Resource temporarily unavailable.

CRRZI0105E

Insufficient system resources are available to complete the call.

CRRZI0106E

sv is not in the writable part of the user's address space.

CRRZI0107E

The request is invalid or not supported.

CRRZI0108E

There has been a network or transport failure.

CRRZI0109E

Too many files are open for this process.

CRRZI0110E

Too many files are open in the system.

CRRZI0111E

There was no NETWORK statement in the parmlib member to match the specified domain.

CRRZI0112E

Connect a socket failed.

CRRZI0113E

O_NONBLOCK is set for the file descriptor for the socket, and the connection cannot be immediately established. The connection will be established asynchronously. The EINPROGRESS value does not indicate an error condition.

CRRZI0114E

The socket descriptor socket is marked nonblocking, and a previous connection attempt has not completed.

CRRZI0115E

The descriptor refers to a file, not a socket.

CRRZI0116E

The protocol is the wrong type for this socket.

CRRZI0117E

The socket parameter is not of type SOCK_STREAM.

CRRZI0118E

The address family is not supported.

CRRZI0119E

The specified address is not available from the local machine.

CRRZI0120E

The network cannot be reached from this host.

CRRZI0121E

The socket descriptor socket is already connected.

CRRZI0122E

The connection establishment timed out before a connection was made.

CRRZI0123E

The connection request was rejected by the destination host.

CRRZI0124E

The socket parameter is not a valid socket descriptor.

CRRZI0125E

Using address and address_len would result in an attempt to copy the address into a portion of the caller's address space to which data cannot be written.

CRRZI0126E

The attempt to establish a connection was interrupted by delivery of a signal that was caught. The connection will be established asynchronously.

CRRZI0127E

The address_len parameter is not a valid length.

CRRZI0128E

There has been a network or a transport failure.

CRRZI0129E

connect() caller was attempting to extract a user's identity and the caller's process was not verified to be a server. To be server-verified, the caller's process must have permission to the BPX.SERVER profile (or superuser and BPX.SERVER is undefined) and have called either the __passwd() or pthread_security_np() services prior to calling connect() to propagate identity.

CRRZI0130E

Locate a catalog entry failed

CRRZI0131E

ESTAE or GETMAIN return code was nonzero.

CRRZI0132E

DELETE failed because of unmatched device type causing a SCRATCH failure.

CRRZI0133E

DELETE failed because of data set being currently open, causing a SCRATCH failure.

CRRZI0134E

There was an I/O or unrecoverable error.

CRRZI0135E

Unable to allocate a required catalog.

CRRZI0136E

Insufficient space was supplied. The size of the calculated space is returned in the CTGFDBK area of the catalog parameter list.

CRRZI0137E

Insufficient space was supplied. The size required is not known.

CRRZI0138E

The function was not valid.

CRRZI0139E

Security or password verification failure.

CRRZI0140E

Either the data set was not found or the catalog could not be opened.

CRRZI0141E

DELETE failed because of unexpired purge date causing a SCRATCH failure.

CRRZI0142E

Read a DSCB failed

CRRZI0143E

A permanent I/O error was encountered, or an invalid format-1 DSCB was found when processing the specified volume, or an unexpected error return code was received from CVAF (common VTOC access facility).

CRRZI0144E

Invalid work area pointer.

CRRZI0145E

The required volume was not mounted.

CRRZI0146E

The format-1 DSCB was not found in the VTOC of the specified volume.

CRRZI0147E

Migrated Data Set failed

CRRZI0148E

Close failed

CRRZI0149E

Termination failed

CRRZI0150E

ESTAE Exit failed

CRRZI0151E

Get Directory failed

CRRZI0152E

Start Command Server failed

Explanation

There is an APPC setup problem for the TSO Commands service.

Response

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.

CRRZI0153E

Set environment failed

CRRZI0154E

A request to write data to a socket failed.

CRRZI0155E

socket is in nonblocking mode and no data buffers are available.

CRRZI0156E

The descriptor is for a file, not for a socket.

CRRZI0157E

The socket is not connection-oriented and no peer address is set.

CRRZI0158E

The message was too big to be sent as a single datagram.

CRRZI0159E

The socket argument is associated with a socket that does not support one or more of the values set in flags.

CRRZI0160E

A connection was forcibly closed by a peer.

CRRZI0161E

Buffer space is not available to send the message.

CRRZI0162E

The socket is not connected.

CRRZI0163E

socket is not a valid socket descriptor.

CRRZI0164E

Using the msg and length parameters would result in an attempt to access storage outside the caller's address space.

CRRZI0165E

A signal interrupted send() before any data was transmitted.

CRRZI0166E

There has been a network or transport failure.

CRRZI0167E

For a connected stream socket the connection to the peer socket has been lost. A SIGPIPE signal is sent to the calling process.

CRRZI0168E

A request to read data from a socket failed.

CRRZI0169E

socket is in nonblocking mode and data is not available to read.

CRRZI0170E

The descriptor is for a file, not for a socket.

CRRZI0171E

The specified flags are not supported for this socket type or protocol.

CRRZI0172E

A connection was forcibly closed by a peer.

CRRZI0173E

Insufficient system resources are available to complete the call.

CRRZI0174E

A receive is attempted on a connection-oriented socket that is not connected.

CRRZI0175E

The connection timed out during connection establishment, or due to a transmission timeout on an active connection.

CRRZI0176E

socket is not a valid socket descriptor.

CRRZI0177E

Using the buf and len parameters would result in an attempt to access storage outside the caller's address space.

CRRZI0178E

The recv() call was interrupted by a signal that was caught before any data was available.

CRRZI0179E

The request is invalid or not supported. The MSG_OOB flag is set and no out-of-band data is available.

CRRZI0180E

There has been a network or transport failure.

CRRZI0181E

Read control lock failed.

CRRZI0182E

The mutex could not be acquired because the maximum number of recursive locks for mutex has been exceeded. This errno will only occur in the shared path.

CRRZI0183E

The current thread already owns the mutex, and the mutex has a kind attribute of __MUTEX_NONRECURSIVE.

CRRZI0184E

The value specified by mutex is not valid.

CRRZI0185E

Read control unlock failed.

CRRZI0186E

The value specified by mutex is not valid.

CRRZI0187E

The current thread does not own the mutex.

CRRZI0188E

Create a thread failed.

CRRZI0189E

The system lacks the necessary resources to create another thread.

CRRZI0190E

The value specified by thread is not valid.

CRRZI0191E

There is not enough memory to create the thread.

CRRZI0192E

Get read response failed.

CRRZI0193E

Client/Server version mismatch

CRRZI0194E

Record format not allowed

Explanation

This error occurs when downloading a load module or program object. The transfer types of the source and target data sets are different.

User response

Diagnosing the problem
  1. Left-click the destination data set. Look at the Property view (the two-column table with headings Property and Value). Expand the Mapping property. You must see Transfer Binary in both the source data set and the destination data set.
  2. This feature requires the client and server to be at least at version 8.0.1.
Solving the problem
If the destination data set is Transfer Text, change it to Transfer Binary by doing one of the following:
  • For a single file:
    1. Right-click the destination data file and click Properties.
    2. Click Mapping.
    3. Click the Other radio button beneath Transfer mode, click binary, and then click OK.
  • For all files with a particular low-level qualifier:
    1. Click Window > Show View > z/OS file System Mapping. The view opens near the bottom of the workspace window.
    2. Right-click in the view and click Add data set mapping.
    3. Type a pattern in the Mapping Criterion field, for example, **LOADMOD. This mapping will apply to all future data sets with that low level qualifier.
    4. Click the Other radio button beneath the Transfer mode, click binary, and then click OK.

CRRZI0195E

Unable to delete file

CRRZI0196E

Unable to rename file

CRRZI0197E

Directory update failed

CRRZI0198E

No space left in the directory.

CRRZI0199E

A permanent input or output error was detected. Control is not given to the error analysis (SYNAD) routine.

CRRZI0200E

The system found an I/O error while trying to read or write the VTOC.

CRRZI0201E

A permanent I/O error occurred while attempting to write the EOF mark after the member. Control is not given to the error analysis (SYNAD) routine.

CRRZI0202E

The system was unable to update the VTOC.

CRRZI0203E

Either no secondary space is available or a DADSM user exit error occurred. The error occurred when trying to write an EOF; all primary space has been used.

CRRZI0204E

Either no secondary space is available or a DADSM user exit error occurred.

CRRZI0205E

An error occurred while writing data buffered in system buffers. Control is not given to the error analysis (SYNAD) routine.

CRRZI0206E

The specified data control block is not open or is opened for input, or a DEB error occurred.

CRRZI0207E

The initialize function was specified but the PDSE was allocated with DISP=SHR. Use DISP=OLD or DISP=MOD.

CRRZI0208E

Insufficient virtual storage was available to perform the STOW function.

CRRZI0209E

The caller attempted to issue add or replace for a member of the Program Management Library, which is a PDSE that contains program objects.

CRRZI0210E

The alias has an invalid TTR.

CRRZI0211E

The directory already contains the specified new name.

CRRZI0212E

User-supplied TTRs are in the user data field of the directory entry.

CRRZI0213E

The replace failed because you cannot replace an alias name if it is the same name as the primary member.

CRRZI0214E

The add or replace failed when attempting to add or replace an alias, but the member identified by the TTR did not exist.

CRRZI0215E

The replace failed when attempting to replace a primary member name while the PDSE is open for update and the member name identified an existing alias.

CRRZI0216E

The replace failed when attempting to replace a primary member name while the PDSE is open for update, but the input TTR has not been defined for that member.

CRRZI0217E

The add failed because you cannot add a primary member name while the PDSE is open for update.

CRRZI0218E

The replace failed because you cannot replace a primary member name while the PDSE is open for update and the specified name does not exist.

CRRZI0219E

One or more members were placed in a pending delete state; the space taken by those modules is not immediately available for reuse.

CRRZI0220E

The specified name could not be found.

CRRZI0221E

Dynamic allocation failure for PDS directory

CRRZI0222E

Get all member names from PDS failed.

CRRZI0223E

The id, length, or level of the parameter list is invalid.

CRRZI0224E

This function requires a PDSE data set.

CRRZI0225E

The concatenation number specified is greater than the concatenation number of the last data set in the concatenation.

CRRZI0226E

Address of the DEB is 0 or DEB is input but the DCB pointed to by the DEB does not point back to the DEB.

CRRZI0227E

The passed DCB is not open.

CRRZI0228E

The address of the DCB is zero.

CRRZI0229E

To pass the DEB the caller must be supervisor state or a system key.

CRRZI0230E

The FUNC value is incorrect.

CRRZI0231E

The gap specified is too large. The gap must be larger than DESP_ENTRY_GAP_MAX.

CRRZI0232E

The address of the AREAPTR is 0.

CRRZI0233E

The connect intent specified is not valid with this function.

CRRZI0234E

The CONN_INTENT(HOLD) requires the caller of function GET_ALL to be in supervisor state or system key.

CRRZI0235E

The DEBCHK macro failed. The DCB or DEB is invalid.

CRRZI0236E

FREEMAIN failure.

CRRZI0237E

No members in directory.

CRRZI0238E

Get PDS directory information failed.

CRRZI0239E

One or more entries in the list could not be filled; the list supplied can be invalid.

CRRZI0240E

A permanent I/O error was detected when the system attempted to search the directory.

CRRZI0241E

Insufficient virtual storage was available.

CRRZI0242E

Invalid data extent block (DEB), or the DEB is not owned by a TCB in the current family of TCBs, or the UCB address in the DEB is zero.

CRRZI0243E

Monitor activity on sockets failed.

CRRZI0244E

One of the bit sets specified an invalid socket. FD_ZERO() was probably not called to clear the bit set before the sockets were set.

CRRZI0245E

One of the parameters contained an invalid address.

CRRZI0246E

The select() function was interrupted before any of the selected events occurred and before the timeout interval expired.

CRRZI0247E

One of the fields in the timeval structure is invalid, or there was an invalid nmsgsfds value.

CRRZI0248E

One of the descriptors in the select mask has become inoperative.

CRRZI0249E

Bind a name to a socket failed.

CRRZI0250E

The descriptor is for a file, not for a socket.

CRRZI0251E

Permission denied.

CRRZI0252E

The socket type of the specified socket does not support binding to an address.

CRRZI0253E

The address family is not supported.

CRRZI0254E

The address is already in use.

CRRZI0255E

The address specified is not valid on this host.

CRRZI0256E

bind() is unable to obtain a buffer due to insufficient storage.

CRRZI0257E

The socket parameter is not a valid socket descriptor.

CRRZI0258E

The socket is already bound to an address--for example, trying to bind a name to a socket that is already connected. Or the socket was shut down.

CRRZI0259E

There has been a network or transport failure.

CRRZI0260E

The user is not authorized to bind to the port specified.

CRRZI0261E

Prepare the server for incoming client requests failed.

CRRZI0262E

The descriptor is for a file, not for a socket.

CRRZI0263E

The socket is not bound to a local address, and the protocol does not support listening on an unbound socket.

CRRZI0264E

The socket parameter is not a socket descriptor that supports the listen() call.

CRRZI0265E

Insufficient system resources are available to complete the call.

CRRZI0266E

The socket parameter is not a valid socket descriptor.

CRRZI0267E

An invalid argument was supplied. The socket is not named (a bind() has not been done), or the socket is ready to accept connections (a listen() has already been done). The socket is already connected.

CRRZI0268E

Get the name of a socket failed.

CRRZI0269E

The descriptor is for a file, not for a socket.

CRRZI0270E

The operation is not supported for the socket protocol.

CRRZI0271E

getsockname() is unable to process the request due to insufficient storage.

CRRZI0272E

The socket is not in the connected state.

CRRZI0273E

The socket parameter is not a valid socket descriptor.

CRRZI0274E

Using the name and namelen parameters as specified would result in an attempt to access storage outside of the caller's address space.

CRRZI0275E

Operation terminated.

CRRZI0276E

Data set must be empty to be deleted

CRRZI0277E

System ABEND {0}.

CRRZI0278E

The OPEN/EOV volume security exit requested that the volume be rejected.

CRRZI0279E

An OPEN was issued for a RACF-protected data set to which the caller was not authorized.

CRRZI0280E

A data set opened for output used all the primary space, and no secondary space was requested.

CRRZI0281E

An installation DADSM exit, IGGPRE00, rejected the extend request.

CRRZI0282E

A data set opened for output used all space available to or on the current volume, and no more volumes were available.

CRRZI0283E

A multi-volume physical sequential data set was being written on a direct access device. All space was filled on the volume, and an attempt was made to obtain space on the next specified volume. Either the space was not available on that volume, the data set already existed on that volume, or there is no space available in the VTOC or the VTOC index.

CRRZI0284E

I/O operation failed.

CRRZI0285E

TGET macro failed.

CRRZI0286E

TPUT macro failed.

CRRZI0287E

Provide relative position failed.

CRRZI0288E

DEVTYPE macro failed.

CRRZI0289E

RDJFCB macro failed.

CRRZI0290E

TRKCALC macro failed.

CRRZI0291E

Cataloging a non-VSAM data set failed.

CRRZI0292E

Uncataloging a non-VSAM data set failed.

CRRZI0293E

Renaming a data set in the VTOC failed.

CRRZI0294E

No volume containing any part of data set was mounted, nor was there a unit available for mounting.

CRRZI0295E

An unusual condition was encountered on one or more volumes.

CRRZI0296E

Deleting a data set from the VTOC failed.

CRRZI0297E

Position for access failed.

CRRZI0298E

Dynamic allocation failed.

CRRZI0299E

Duplicate data set name on the volume.

CRRZI0300E

The volume table of contents (VTOC) for the specified or defaulted volume for a new data set request had insufficient space in the VTOC index for a new entry, or did not have the minimum number of data set control blocks (DSCBs) required to allocate the data set.

CRRZI0301E

Space on the direct access storage device (DASD) containing the requested volume could not be obtained.

CRRZI0302E

Requested absolute track is not available.

CRRZI0303E

More space was requested than is available on the DASD volume, or the DASD volume's VTOC is full, or the DASD volume's VTOC Index (VTOCIX) is full.

CRRZI0304E

The average block length specified on text unit key DALAVGR (key 0009) was greater than the track capacity of the requested DASD volume.

CRRZI0305E

Invalid DADSM REALLOC parameter list.

CRRZI0306E

The system did not allocate the directory for a new partitioned data set (PDS) because the space requested for the directory on text unit key DALDIR (key 000C) exceeded the space available on the specified volume.

CRRZI0307E

No space parameter given for a new data set or zero space requested at absolute track zero.

CRRZI0308E

A profile for the specified data set on this volume already exists in the Resource Access Control Facility (RACF) data set.

CRRZI0309E

User is not authorized to define this data set. The user has the automatic data set protection characteristic without the RACF authorization to define data sets.

CRRZI0310E

Installation exit rejected this request.

CRRZI0311E

Space request was rejected by installation exit.

CRRZI0312E

Non-SMS managed data set cannot be created on an SMS-managed volume.

CRRZI0313E

An unexpected or internal error code was received by Allocation.

CRRZI0314E

Required CATALOG volume is currently not mounted.

CRRZI0315E

Either the existing catalog structure is inconsistent with the operation, or the program was not authorized to perform the operation.

CRRZI0316E

The index structure necessary to catalog the data set does not exist.

CRRZI0317E

CATALOG space is exhausted on the control volume.

CRRZI0318E

A CATALOG I/O error has occurred.

CRRZI0319E

CATALOG error.

CRRZI0320E

Data set not on volume as indicated in the catalog or volume text unit.

CRRZI0321E

OBTAIN I/O error. During data set allocation, an uncorrectable I/O error occurred when the system attempted to obtain a data set control block (DSCB).

CRRZI0322E

An invalid work area pointer was supplied.

CRRZI0323E

The absolute address passed was not within the boundaries of the VTOC.

CRRZI0324E

Virtual storage unavailable.

CRRZI0325E

Request for exclusive use of a shared data set cannot be honored.

CRRZI0326E

Requested data set is unavailable. The data set is allocated to another job and its usage attribute conflicts with this request.

CRRZI0327E

Device(s) not available.

CRRZI0328E

Specified volume or an acceptable volume is not mounted, and user does not have volume mounting authorization through the DYNALLOC request.

CRRZI0329E

Device name specified is undefined.

CRRZI0330E

Requested volume is not available.

CRRZI0331E

Eligible device types do not contain enough devices.

CRRZI0332E

Specified volume or device in use by system.

CRRZI0333E

Volume mounted on ineligible permanently resident or reserved device.

CRRZI0334E

Permanently resident or reserved volume on required device.

CRRZI0335E

More than one device required for a request specifying a specific device.

CRRZI0336E

Space unavailable in task input output table (TIOT).

CRRZI0337E

Required catalog is not mounted, and user does not have volume mounting authorization.

CRRZI0338E

CATALOG LOCATE error. Either the data set name specified is in error, or a system error occurred when processing the data set name.

CRRZI0339E

Permanent I/O error processing cataloged data set.

CRRZI0340E

Insufficient real or virtual storage for processing cataloged data set.

CRRZI0341E

An unsuccessful attempt was made to access a catalog that was locked for recovery. The job does not have the proper authorization to perform this function.

CRRZI0342E

An unexpected return code was returned by catalog LOCATE.

CRRZI0343E

Dynamic allocation of new file failed.

CRRZI0344E

Dynamic deallocation failed.

CRRZI0345E

Output data was truncated.

CRRZI0346E

FCB is corrupted.

CRRZI0347E

There was no room left in a physical record for anymore DBCS characters.

CRRZI0348E

There was not enough room in a record to start any DBCS string or else when a redundant SO was written to the file before an SI.

CRRZI0349E

There was not enough room to start a DBCS string and data was written anyway, with an SI to end it.

CRRZI0350E

An SI was written before the last double byte character is completed, thereby forcing z/OS to fill in the last byte of the DBCS string with a padding byte X'FE'.

CRRZI0351E

An attempt was made to extend a file that allows writing, but cound not be extended.

CRRZI0352E

OPEN macro failed.

CRRZI0353E

CLOSE macro failed.

CRRZI0354E

Find a data set member failed.

CRRZI0355E

Name not found.

CRRZI0356E

The PDSE is open for output and the FIND macro was issued to point to a member other than the one currently processing.

CRRZI0357E

The caller has only RACF execute authority to the PDSE.

CRRZI0358E

The PDSE member's share options do not allow you to access it.

CRRZI0359E

Permanent I/O error during directory search.

CRRZI0360E

An I/O error occurred while flushing system buffers containing member data.

CRRZI0361E

No DCB address was input.

CRRZI0362E

Insufficient virtual storage available.

CRRZI0363E

Invalid DEB, or DEB is not owned by a TCB in the current family of TCBs.

CRRZI0364E

Create a process failed.

CRRZI0365E

Out of memory.

CRRZI0366E

Code page conversion failed with {0}.

CRRZI0367E

Code page {0} is not supported.

CRRZI0368E

Server initialization failed.

CRRZI0369E

Lock failed.

CRRZI0370E

A previous request for control of the same resource has been made for the same task. The task does not have control of the resource.

CRRZI0371E

Invalid resource name.

CRRZI0372E

The resource is not immediately available.

CRRZI0373E

A previous request for control of the same resource has been made for the same task. The task has control of the resource.

CRRZI0374E

Unlock failed.

CRRZI0375E

The resource has been requested for the task, but the task has not been assigned control of it. The task continues waiting.

CRRZI0376E

Control of the resource has not been requested by the active task, or the resource has already been released.

CRRZI0377E

Internal server error occurred.

CRRZI0378E

Exception occurred.

CRRZI0379E

The request has timed out because there is no response from the server.

CRRZI0380E

No response from TSO command server.

CRRZI0381E

ALLOCATE failed.

CRRZI0382E

FREE failed.

CRRZI0383E

The data set compression has failed.

CRRZI0384E

The data set compression has failed. Data Set is missing.

CRRZI0385E

The data set compression has failed. The data set is not a PDS.

CRRZI0386E

Data set compression has failed. Problems in allocating SYSUT data set. See the Error log for more details.

CRRZI0387E

Data set compression has failed. Problems creating the backup data set. See the Error log for more details.

CRRZI0388E

The data set compression has failed. See the Error log for more details.

CRRZI0389E

Copy command has failed..

CRRZI0390E

Copy command has failed. Problem in allocating SYSUT data set. See the Error log for more details.

CRRZI0391E

Copy command has failed. See the Error log for more details.

CRRZI0392E

ALLOCATE failed. No data set created.

CRRZI0393E

ALLOCATE failed. Record length is inconsistent with block size for this record format.

CRRZI0394E

Server initialization failed.

CRRZI0395E

Migrate failed.

CRRZI0396E

Recall failed.

CRRZI0397E

Delete failed.

CRRZI0398E

Server internal error. TSO server cannot be located.

CRRZI0399E

Server internal error. Bad TSO server response {0}.

CRRZI0400E

Server internal error. Command target is not set.

CRRZI0401E

Server internal error. Unsupported command {0}.

CRRZI0402E

Server internal error. Undefined message number {0}.

CRRZI0403E

Server internal error. System cannot be located.

CRRZI0404E

Server internal error. HLQ cannot be located.

CRRZI0405E

Server internal error. Bad resource type {0}.

CRRZI0406E

Server internal error. Partitioned data set cannot be located.

CRRZI0407E

Server internal error. Remote resource cannot be located.

CRRZI0408E

Server internal error. Exception occurred.

CRRZI0409E

Server internal error. Target container cannot be located.

CRRZI0410E

Server internal error. Unknown target container type.

CRRZI0411E

Server internal error. Bad ENQUEUE name {0}.

CRRZI0412E

Failed to open file {0} in the editor.

CRRZI0413E

Failed to open file {0} in editor {1}. {2}

CRRZI0414W

The build dependencies might have changed since the last syntax check. You might want to recheck its dependencies before proceeding with the syntax check.

CRRZI0415W

Check the dependencies before proceeding with the syntax check.

CRRZI0416W

File type {0} is not a local file.

CRRZI0417E

Could not retrieve an editable file for resource {0} of type {1}.

CRRZI0418E

Could not retrieve an editor object for resource {0} of type {1}.

CRRZI0419E

Could not retrieve a remote file for resource {0} of type {1}.

CRRZI0420I

The file {0} will be opened for read only.

CRRZI0421E

Could not perform the refresh dependencies operation.

CRRZI0422I

For local syntax check to perform correctly, make sure that all the dependent libraries referenced by this file are also added to this MVS subproject. You can use "Show Dependencies" to reveal the dependent libraries, and then add them to your MVS subproject.

CRRZI0423E

This operation cannot be performed because error feedback is not supported when either the DB2 precompiler or the CICS translator option is set.

CRRZI0424E

Could not perform the remote syntax check operation.

CRRZI0425E

Could not perform the show dependencies operation.

CRRZI0426E

The property group associated with this resource does not have the "Support Error Feedback" option selected. Modify the property group and try again.

CRRZI0427E

Could not retrieve a USS file for resource {0} of type {1}.

CRRZI0428E

Could not retrieve a remote file for resource {0} of type {1}.

CRRZI0429I

The system default values have been updated for system {0}. Do you want to replace the previous defaults with the new ones?

CRRZI0430I

The system property groups have been updated for system {0}. Do you want to replace the ones that were already loaded?

CRRZI0431W

The file {0} already exists. Do you want to overwrite it?

CRRZI0432E

'{0}' is not a valid local project properties file. Make sure the file you are trying to import defines properties for a local project.

CRRZI0433E

'{0}' is not a valid MVS subproject properties file. Make sure the file you are trying to import defines properties for an MVS subproject.

CRRZI0434E

'{0}' is not a valid MVS Files subsystem properties file. Make sure the file you are trying to import defines properties for an MVS Files subsystem.

CRRZI0435E

Unable to import properties from file '{0}'. Make sure the file you are trying to import is a valid .xml or .properties file.

CRRZI0436W

Are you sure you want to delete the overrides for this resource?

CRRZI0437W

Are you sure you want to delete property group {0}?

CRRZI0438E

A property group exists with name {0}. Change the name to a unique name.

CRRZI0439W

The property file you are importing is an old version. Property group {0} will be created to hold the values. Do you want to proceed?

CRRZI0440E

The resource '{0}' does not have a property group associated with it. Choose an action and then try the operation again:

Explanation

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.

Response

Choose one of the following options:
  • To choose an existing property group to associate with the resource, click Associate an existing property group. After making this selection and associating the property group, try the operation again.
  • To create a new property group and associate it with the resource, click Associate a new property group. After making this selection, creating a property group, and associating it with the resource, try the operation again.
  • To cancel the operation, click Do not associate a property group.

CRRZI0441E

Could not open file {0}.

CRRZI0442E

Error writing to file {0}.

CRRZI0443E

{0} is not a registered category.

CRRZI0444W

Some property groups cannot be imported due to name conflicts.

CRRZI0445E

Error reading from file {0}.

CRRZI0446E

A duplicate category instance was detected in property group {0}. The category of the instance is {1}.

CRRZI0447E

{0} is not a registered property.

CRRZI0448W

The system default values have been updated for system {0}. Do you want to replace the previous defaults with the new ones?

CRRZI0449W

The system property groups have been updated for system {0}. Do you want to replace the ones you previously loaded?

CRRZI0450E

The check dependencies operation could not be performed. See details for more information.

CRRZI0451E

Copying a partitioned data set using drag-and-drop is not supported.

CRRZI0452E

Resource '{0}' is locked and cannot be deleted. Another person or program might be using the resource. Retry the operation when the resource is available.

CRRZI0454E

The operation did not complete because resource '{0}' is locked. Another person or program might be using the resource. Retry the operation when the resource is available.

CRRZI0455E

The operation did not complete because resources '{0}' and '{1}' are locked. Another person or program might be using the resources. Retry the operation when the resources are available.

CRRZI0456E

Local project names are case insensitive. There is an existing project that conflicts with '{0}'. Choose another name for the project.

CRRZI0457E

An internal error occured during creation of local project '{0}'. Contact your IBM technical support representative.

CRRZI0458I

'{0}' has been submitted to remote system '{1}'. Use JES on the Remote Systems view to view its output.

Explanation

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.

Response

To check the job output, do these steps:
  1. In the Remote Systems view, locate the remote system on which the DB2 table you are working with is located.
  2. Expand the remote system connection and then expand JES > My Jobs.
  3. Look for the job name indicated in the message and expand it to see the job output.

CRRZI0459E

The job has not been submitted because the Job Monitor server is not connected. Contact your System Administrator to start the Job Monitor server. After the server is started, you may resubmit the job.

CRRZI0460E

A problem occurred while creating or saving the properties. See the log for further information.

CRRZI0461E

No connection is defined for '{0}'. Define a connection and import the project again.

CRRZI0462E

The project to be imported is named '{0}'. There is already a project in the workspace with this name. Specify a unique name for the new project and try again.

CRRZI0463E

A file with the name '{0}' already exists in '{1}'. Make sure all the files have a unique name (excluding extension) and try again.

CRRZI0464E

Invalid MVS name. A member name cannot be more than 8 characters. Return to the offline project, rename the member, and retry the operation.

CRRZI0465E

Invalid MVS name. The member name must not have a period. Return to the offline project, rename the member, and retry the operation.

CRRZI0466E

Invalid MVS name. Each segment of a data set name must not have more than 8 characters. Return to the offline project, rename the member, and retry the operation.

CRRZI0467W

{0} has the following encoding mismatch:

CRRZI0468E

Another properties provider is registered for the resource.

Explanation

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.

Response

Contact your IBM technical support representative.

CRRZI0469E

The object does not have properties.

Explanation

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.

Response

Contact your IBM technical support representative.

CRRZI0470I

z/OS UNIX Files and Shells are hidden by the server setting.

CRRZI0471E

While synchronizing changes resulting from a request to rename a shared folder from {1} to {2}, the rename operation for the sandbox resource {0} failed. The sandbox resource will be unloaded from the z/OS project. Resolve the error described below and reload the shared resource to the project.

CRRZI0472E

While synchronizing changes resulting from a request to delete the shared resource {1}, the delete operation for sandbox resource {0} failed. The sandbox resource will be disconnected. Resolve the error described below or the sandbox might not be available for use.

CRRZI0473E

While synchronizing changes resulting from a request to rename a shared resource from {1} to {2}, the rename operation for the sandbox resource {0} failed. The sandbox resource will be unloaded from the z/OS project. Resolve the error described below and reload the shared resource to the project.

CRRZI0474E

While synchronizing changes resulting from a request to update Failed to update the shared resource {1}, the update operation for the sandbox resource {0} failed. The sandbox resource will be unloaded from the z/OS project. Resolve the error described below and reload the shared resource to the project.

CRRZI0475E

The data set {0} does not exist.

CRRZI0476E

The data set {0} is already specified in the text field.

CRRZI0477E

Invalid source {0} for this text field. Drag and drop a valid data set onto this text field.

CRRZI0478E

This text field specifies one data set name. Drag and drop one data set onto this text field.

CRRZI0479W

The length of the data set name might exceed the maximum of 44 characters, depending on the length of the high-level qualifier.

CRRZI0480E

The system {0} is not connected. Connect to the system and try again.

CRRZI0481E

There is no name for the property group.

CRRZI0482E

An attempt to set contents to resource {0} failed because the resource is locked. Another person or program might be using the resource. Retry the operation when the resource is available.

CRRZI0483E

While synchronizing changes to the sandbox resource {1}, a delete operation for the shared resource {0} failed. The resource is not synchronized. Resolve the error described below and share the sandbox or reload the shared resource.

CRRZI0484E

While synchronizing changes resulting from a request to rename the sandbox from {1} to {2}, the rename operation for the shared resource {0} failed. The resource is not synchronized. Resolve the error described below and share the sandbox or reload the shared resource.

CRRZI0485E

The editor contains characters that cannot be transferred correctly between the local and remote systems. Saving the file on the remote system will cause these characters to become corrupted. Do you want to continue?

Explanation

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.

Response

To save the file with corrupted characters, click Yes. To close the file without saving your changes, click No.

CRRZI0486E

Characters have been introduced that cannot be transferred correctly between the local and remote systems. These characters have been highlighted. Change these characters before saving the file.

Explanation

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.

Response

Change the highlighted characters before trying to save the file.

CRRZI0487E

File '{0}' contains characters that cannot be transferred correctly between the local and remote systems. These characters will be highlighted. The file will be opened in read-only mode.

Explanation

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.

Response

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.

CRRZI0488E

An attempt to download resource '{0}' to the shadow file area has failed.

CRRZI0489E

An attempt to move the logical resource '{0}' to '{1}' has failed.

CRRZI0490E

The logical resource '{0}' is not a subproject.

CRRZI0491E

The remote sandbox file path name '{0}' is not found on the system '{1}'.

CRRZI0492E

There are no systems found for the logical subproject '{0}'.

CRRZI0493E

An attempt to load resource '{0}' to the subproject '{1}' has failed.

CRRZI0494E

The local sandbox path '{0}' specified for the team resource '{1}' is invalid.

CRRZI0495E

The resource '{0}' is already registered with a team provider. Registering a resource with multiple team providers in not allowed.

CRRZI0496E

The resource '{0}' is already shared with a team provider. Sharing a resource with multiple team providers is not allowed.

CRRZI0497E

The resource '{0}' is not shared with a team provider. The disconnect operation can be performed only on a shared resource.

CRRZI0498E

The sandbox prefix has been specified for '{0}', but the remote sandbox file name is required. Specify the remote sandbox file name and retry the operation.

CRRZI0499I

Data set validation is complete. All validated data sets exist.

CRRZI0500W

Data set validation is complete. One or more data set names contain the variable <HLQ> and these data sets cannot be validated.

CRRZI0501E

Data set {0} already exists.

CRRZI0502E

Data set {0} has conflicting attributes.

CRRZI0503E

Member {0} already exists.

CRRZI0504I

The closed project {0} contained one or more shared resources. They have been unloaded. You will need to reload them when you reopen the project later.

CRRZI0505E

Overrides are being edited for property group '{0}'. Close the edit session for the overrides before editing the property group.

CRRZI0506E

The property group '{0}' is being edited. Close the edit session for the property group before attempting to override it.

CRRZI0507E

Possible reason for failure: An invalid CICS Debug profile server port ({0}) is being used for the CICS region {1}. Contact the administrator for the valid port and update the port in the CICS Debug Configuration preference page.

Explanation

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.

Response

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.

CRRZI0508I

Specify the CICS Debug profile server port for the CICS region {0}.

Explanation

An attempt has been made to create a debug configuration, but there is no CICS Debug profile server port associated with the CICS region.

Response

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.

CRRZI0509E

The remote sandbox resource {0} has been updated by another person or program. Resolve the conflict and then retry the operation.

CRRZI0510W

The data set '{0}' contains {1} members. Working with a large number of members in a subproject might take a long time. To improve performance, add only required members to the subproject. Do you want to proceed?

CRRZI0511E

CICS region ({0}) does not exist. Make sure the appropriate CICS connection is connected.

Explanation

The region specified on the CICS page of the Debug Configurations > Remote CICS Application wizard does not exist.

Response

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.

CRRZI0512W

The size of file '{0}' is {1} KB, which exceeds the threshold defined in the z/OS Solutions preferences. Opening large files can cause out-of-memory errors leading to a forced shutdown of the workbench. Do you want to continue?

CRRZI0513W

Some categories will not be imported because this version of Rational Developer for System z does not support them.

CRRZI0514E

The operation did not complete successfully. Verify that the JCL procedure on the host has the error feedback compile options configured correctly to support this operation.

CRRZI0515W

The file '{0}' contains characters that cannot be transferred correctly between the local and remote systems. This file will be opened in read-only mode. Do you want to continue?

CRRZI0516W

Both files contain characters that cannot be transferred correctly between the local and remote systems. The files will be opened in read-only mode. Do you want to continue?

CRRZI0518W

A decoding error occurred while fetching the keymapping file. The system will be processed as though there were no keymapping file.

Explanation

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.

User response

No action is required. The new key mapping file will contain settings for only the configuration files included in the current export request.

CRRZI0519I

There are no connected remote systems with the push-to-client function enabled. Connect to a remote system with the push-to-client function enabled and try again.

Explanation

You have requested to export configuration files, but none of the remote systems to which you are connected are enabled for push-to-client.

User response

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.

CRRZI0521E

The error feedback file cannot be parsed because its format or content is invalid or incomplete. Check the build properties and view the job output for unrecoverable errors.

Explanation

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.

User response

  • Open the property group in the Property Group Editor and verify that the Error Feedback XML File Name field refers to the correct file.
  • To view the job output, expand the JES subsystem in the Remote Systems view and look for the job name.

CRRZI0522W

The Rational Developer for System z server has been configured to automatically download product updates to the client when you connect to the remote system. Current Product Version shows the product version currently installed on your workstation. A new version will be installed when you click OK.

Explanation

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.

User response

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.

CRRZI0523E

The member {0} is the alias of {1}. Support for copying aliases has been disabled in the preference settings. Copying an alias without copying its primary is not supported.

Explanation

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.

User response

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.

CRRZI0524E

The member {0} is the alias of {1}, which does not exist. Copying an alias without copying its primary is not supported.

Explanation

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.

User response

For more information about copying data set aliases see Copying load modules. For more information about enabling alias processing, see MVS Files.

CRRZI0525E

The member {0} is an alias or has one or more aliases. The copy target cannot be the same as the copy source.

Explanation

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.

User response

Retry the copy operation and specify a different target. For more information about copying data set aliases see Copying load modules.

CRRZI0526E

IEBCOPY has failed. See {0} for more details.

CRRZI0527W

Both files use an encoding that permits bidirectional characters. The files will be opened in read-only mode. Do you want to continue?

CRRZI0528W

The file '{0}' uses an encoding that permits DBCS characters. The file will be opened in read-only mode. Do you want to continue?

CRRZI0529W

Both files use an encoding that permits DBCS characters. The files will be opened in read-only mode. Do you want to continue?

CRRZI0530W

The file '{0}' uses an encoding that permits bidirectional characters. The file will be opened in read-only mode. Do you want to continue?

CRRZI0532I

You are requesting to export to primary system {1}. Primary system {0} was used last to export the configuration files. Verify that {1} is the correct primary system.

Explanation

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.

User response

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.

CRRZI0533I

Two or more primary systems are connected. Only one connection to a primary system is allowed. Disconnect from all but one primary system.

Explanation

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.

User response

Disconnect from all but one primary remote system. Contact your system administrator if you do not know which remote systems are primary.

CRRZI0534E

Insufficient permission to the directory {0} when exporting {1}.

Explanation

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.

User response

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).

CRRZI0535I

There are no changes between the workstation copy and the remote copy.

CRRZI0536E

Errors occurred moving changed files

CRRZI0537E

No remote systems are defined. Cancel this action, define a remote system, and retry the operation.

CRRZI0538E

Could not mark {0} as merged

CRRZI0539E

You must be connected to the remogte system and have at least one filter defined to use the <HLQ> variable.

CRRZI0540E

You are going to overwrite changes that have been made on the remote system. Commit these changes?

CRRZI0541E

Error copying {0} to the local workspace

CRRZI0542E

Error copying {0} to the remote system

CRRZI0543W

The chosen remote system location differs from the project's target remote system. Would you like to change the project's target remote system to match the chosen remote system location?

CRRZI0544W

The extension is already in the mapping.

CRRZI0545W

You are going to overwrite changes that have been made in the local workspace. Update the workspace?

CRRZI0546E

Failed to connect to {0}.

CRRZI0547E

Could not find {0} on {1}.

CRRZI0548E

Failure to retrieve modification stamp.

CRRZI0549E

Contents cannot be retrieved from {0}.

CRRZI0550E

Failure to retrieve member contents {0}.

CRRZI0551E

Contents cannot be set on {0}.

CRRZI0552E

Failure to write member contents.

CRRZI0553E

Failed to connect to {0}.

CRRZI0554E

Could not find {0} on {1}.

CRRZI0555E

Contents cannot be retrieved from {0}.

CRRZI0556E

Contents cannot be set on {0}.

CRRZI0557E

Could not access properties.

CRRZI0558E

Syntax check not successful.

CRRZI0559W

Some project resources are not synchronized. Would you like to stop the syntax check and open the Team Synchronizing perspective?

CRRZI0560E

Invalid Format. Expected a path, but found {0}.

Explanation

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.

User response

Open the .RemoteMapping file in a text editor and correct the line in error.

CRRZI0562E

A remote system must be specified.

CRRZI0563E

The local resource does not exist.

CRRZI0564E

Unrecognized remote resource type {0}.

CRRZI0565E

Unspecified remote resource type.

CRRZI0566E

The same remote resource is specified multiple times.

CRRZI0567E

Unrecognized remote resource location.

CRRZI0568E

Could not determine if the project is pushable: {0}

CRRZI0569W

This will remove all COBOL feature customization and return to the product defaults. Are you sure?

CRRZI0570W

This action will delete the selected feature(s). Are you sure?

CRRZI0571W

The file already exists. Do you want to replace it?

CRRZI0572W

Overwrite '{0}' ?

CRRZI0573E

Not a valid COBOL comment.

CRRZI0574E

Missing required variable '{0}'.

CRRZI0575W

Unrecognized or illegal variable '{0}'.

CRRZI0576I

The selected configuration file updates have been downloaded.

Explanation

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.

User response

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.

CRRZI0577I

You are requesting to import configuration files from the group {1}. The group {0} was used last to import the configuration files. Verify that {1} is the correct group.

Explanation

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}.

User response

  • If you intended to import the configuration files a different group, click OK.
  • If you intended to import configuration files from group {1} to a different workspace, click Cancel, switch to a different workspace, and then try the import operation again from that workspace.

CRRZI0579W

Your authorization to access group {0} has changed since you last connected to this remote system. The configuration updates will not be imported into this workspace.

Explanation

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.

User response

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.

CRRZI0580W

Configuration groups have been disabled since you last connected to this remote system. The configuration updates for group {0} will not be imported into this workspace.

Explanation

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}.

User response

No action is required.

CRRZI0582E

The backup of an existing workspace has failed. Make sure that there is sufficient free disk space and that none of the files in the workspace has a path that is too long. Do you want to continue without backing up the workspace?

CRRZI0583E

A NullPointerException was encountered during migration of the workspace.

CRRZI0584E

Workstation folder {0} under the offline project cannot be migrated.

CRRZI0585E

Unable to find the VisualAge CICS Translator or the Transaction Server Translator

CRRZI0586E

Unable to find the CICS TX Series Translator. If you are using Windows, install the CICS TX Series Translator. Support for the CICS TX Series Translator is not available on Linux platforms.

CRRZI0587E

Local build and local syntax check require an application driver JDBC connection. The driver associated with connection {0} is not an application driver connection. The operation will continue. The SQL coprocessor will not be invoked.

CRRZI0588E

Local build and local syntax check require a database connection. The database for connection {0} is not connected. The operation will continue. The SQL coprocessor will not be invoked.

CRRZI0589E

A valid database connection is required for this operation. Make sure that you have the correct connection properties, a valid user ID, and a valid password.

CRRZI0590E

Problems occurred while determining build dependencies.

CRRZI0591W

Resource type {0} is not supported.

CRRZI0592E

'{0}' was found while processing file '{1}' at line '{2}'. The dependency list might be incomplete.

CRRZI0593E

An exception occurred during file operation validation.

CRRZI0594E

An error occurred while reading file {0}. See the log file for details.

CRRZI0595I

The Java Virtual Machine (JVM) has not yet terminated. Click OK to terminate the JVM, wait 30 seconds for it to terminate on its own, or click Cancel to cancel the installation of Rational Developer for System z product updates.

Explanation

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.

User response

  • To terminate the Java Virtual Machine immediately, click OK. Rational Developer for System z shuts down and IBM Installation Manager starts to begin the product update. After the product update completes, Rational Developer for System z restarts automatically.
  • To cancel the product update and shut down Rational Developer for System z, click Cancel. The next time you start Rational Developer for System z and connect this remote system, you are prompted to install the product update again.
  • To allow more time for the Java Virtual Machine to terminate, wait 30 seconds. If it has not terminated within 30 seconds, click OK or Cancel.

CRRZI0596E

'{0}' is not a valid PL/I logical NOT symbol.

CRRZI0597E

The file operation type {0} for resource {1} is not valid.

CRRZI0598E

Failed to load BCT file {0}. See log file for details.

CRRZI0599E

Failed to load mapping from file {0}.

CRRZI0600E

Could not obtain a lock object for {0}.

CRRZI0601E

Resource {0} is already locked.

CRRZI0602E

Could not find the log in DataStore.

CRRZI0603E

The high-level qualifier {0} cannot be added.

CRRZI0604E

The upload failed.

CRRZI0605E

An unexpected error occurred during exception handling. {0}

CRRZI0606E

Failed to set the browse request for file {0}.

CRRZI0607E

The file is already locked by alias or reference.

CRRZI0608E

The file cannot be downloaded.

CRRZI0609E

Resource type {0} is not supported.

CRRZI0610E

SCLM status unknown.

CRRZI0611E

Failed to store mapping to file {0}.

CRRZI0612E

The system is not connected. Connect to the remote system and retry the operation.

CRRZI0613I

The specified member '{0}' does not exist in the data set '{1}'. Do you want to create this new member?

Explanation

On the Find Member window, you have typed a member name that does not exist in the partitioned data set.

User response

  • To create a new member, click Yes. The new member is created in the data set.
  • To close this message and return to the Find Member window without creating a new member, click No. If you mistyped the member name, you can try the search again.

CRRZI0614W

The result set contains {0} matches. A maximum of {1} matches can be displayed. Refine the member name pattern or change the preference and try again.

Explanation

On the Find Member window, you have typed a member name pattern that results in more matches than the current limit.

User response

  • To refine the member name pattern, try including more characters in the name. Instead of searching for MY*, for example, search for MYFIL*.
  • To increase the result set limit:
    1. Click Window > Preferences. The Preferences window opens.
    2. Expand the Remote Systems and z/OS sections and click MVS Files.
    3. In the Maximum results for Find Member field, specify the maximum number of search results to return with the Find Member action. The default value is 1000 members.

CRRZI0615I

Request was submitted for '{0}'.

CRRZI0616I

Request was submitted for {0} data sets.

CRRZI0617I

Request was submitted for {0} of {1} selected data sets.

CRRZI0618E

Request was not submitted.

CRRZI0619W

Are you sure you want to delete mapping '{0}'?

CRRZI0620W

The result set contains {0} matches. A maximum of {1} matches can be displayed. Refine the data set name pattern and try again.

CRRZI0621I

'{0}' has been compressed successfully.

CRRZI0622I

{0} data sets have been compressed successfully.

CRRZI0623I

{0} of {1} data sets have been compressed successfully.

CRRZI0624E

The data set was not compressed.

CRRZI0625I

A maximum of ten preprocessors is supported.

CRRZI0626I

Are you sure you want to remove the selected global variable?

Explanation

This message asks you to confirm the removal of a global variable.

User response

Select Yes or No.

CRRZI0627I

Are you sure you want to remove the selected user variable?

Explanation

This message asks you to confirm the removal of a user variable.

User response

Select Yes or No.

CRRZI0628I

Are you sure you want to remove the preprocessor?

CRRZI0629I

Are you sure you want to remove the step?

CRRZI0630E

Cannot open a null resource.

CRRZI0631E

Cannot find {0}.

CRRZI0632I

For successful generation from this copybook, the copybook should be self-contained.

CRRZI0633E

The data set name {0} associated with the resource is not valid.

CRRZI0634E

No mapping exists for the member or file type associated with resource {0}.

CRRZI0635I

This kind of project is associated with the {0} perspective. Do you want to switch to this perspective now?

CRRZI0636I

This kind of project, including MVS subprojects, workstation COBOL projects, and workstation PL/I projects, is associated with the z/OS Projects perspective. Do you want to switch to this perspective now?

CRRZI0637W

The project {0} cannot be built because it is offline.

CRRZI0638W

Contact your administrator to ensure that the build server is running on the remote system and that the correct port is specified.

CRRZI0639W

Unable to find the distributed build dll. Check the path settings.

CRRZI0640E

Resource {0} already exists.

CRRZI0641W

Failed to acquire lock.

CRRZI0642W

The file {0} is locked by another user and will be opened in read-only mode.

CRRZI0643W

The file {0} is locked by '{1}' and will be opened in read-only mode.

CRRZI0644W

An error occurred while attempting to obtain a file lock. The file {0} will be opened in read-only mode. Disconnect and reconnect all z/OS remote systems.

CRRZI0645W

'{0}' already exists. Would you like to overwrite it?

CRRZI0647E

Problems occurred while building the selected resources.

CRRZI0648E

Problems occurred launching the selected resource.

CRRZI0649I

Do you want to apply this property to all the members?

CRRZI0661E

File {0} cannot be added to the collection.

CRRZI0662E

Null java.io.File object.

CRRZI0663E

Null IPath object.

CRRZI0664E

Null Resource object.

CRRZI0665E

Could not perform project build operation.

CRRZI0666W

Could not open file {0}.

CRRZI0667W

Could not open file {0}: {1}.

CRRZI0668I

The z/OS project has been exported successfully. Note that the source files in the project are not exported in this operation. Only the project structure and the associated property groups are exported.

CRRZI0669E

A resource exists with a different case:

CRRZI0670W

Do you really want to remove the selected resource(s) from the subproject?

CRRZI0671W

Failed to download {0}.

CRRZI0672W

Unable to migrate property {0}.

CRRZI0673W

Any non-uploaded changes will be lost. Are you sure you want to continue?

CRRZI0674W

At least one of the values of your SYSLIB or local compiler options has changed since the project was taken offline. These changes will be lost once the project is online. Press OK to continue, or press Cancel to return to the wizard.

CRRZI0675W

Failed to upload {0}.

CRRZI0676I

You are requesting to export configuration files to group {1}, which is different from the group {0} currently associated with your workspace. Click OK to continue or Cancel to return to the Export wizard.

Explanation

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}.

User response

  • If you intended to export the same configuration files to both groups, click OK.
  • If you intended to export configuration files to group {1} from a different workspace, click Cancel, switch to a different workspace, and then try the export operation again from that workspace.

CRRZI0677W

Your authorization to access product group {0} has changed since you last connected to this remote system. The product updates will not be imported into this workspace.

Explanation

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.

User response

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.

CRRZI0678W

Product groups have been disabled since you last connected to this remote system. The product updates for group {0} will not be imported into this workspace.

Explanation

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}.

User response

No action is required.

CRRZI0679I

Moving the data set to the download position.

CRRZI0680I

Stepping through the data set.

CRRZI0681I

Opening an edit session.

CRRZI0682I

Opening a browse session.

CRRZI0683I

Downloading the data set.

CRRZI0684E

An internal error has occurred. The array length is too large.

CRRZI0685E

An exception has occurred while converting a long value to an integer.

CRRZI0686E

The resources cannot be opened.

CRRZI0687E

Formatted Data Editor failed to load the file {0}.

CRRZI0688E

Formatted Data Editor failed to load the template associated with the data set {0}.

CRRZI0689E

No matching layout found for the records in the data set.

CRRZI0690E

Formatted Data Editor failed to save the file {0}.

CRRZI0691E

Formatted Data Editor failed to save the file {0} on the remote system.

CRRZI0692E

Update of changes to the record failed.

CRRZI0693E

Failed to initialize a new record in Formatted Editor.

CRRZI0694E

Cannot move to the specified record.

CRRZI0695I

Number of records searched:{0}

CRRZI0696I

Replaced {0} strings in {1} records.

CRRZI0697I

A possible match has been found:{0}

CRRZI0698E

A file can be opened in only one instance of the Formatted Data Editor at a time.

CRRZI0699I

Template Data Editor.

CRRZI0700I

Downloading Template.

CRRZI0701E

An exception occurred while setting the VSAM property value.

CRRZI0702E

A template association error has occurred.

CRRZI0703E

An unexpected exception has occurred.

CRRZI0704E

A core exception has occurred. The current status is: {0}.

CRRZI0705E

An error was detected while loading {0}: {1} : Line {2} Column {3}.

CRRZI0706E

The Template Editor could not open because the template file was not found.

CRRZI0707E

The Template Editor failed to load the file {0}.

CRRZI0708E

The Template Editor could not open due to an internal error.

CRRZI0709E

The Template Editor failed to convert string data to the code page {0}. String: {1}.

CRRZI0710E

The Template Editor failed to save the file {0}.

CRRZI0711E

The Template Editor failed to save the file {0} on the remote system.

CRRZI0712E

The Template Editor can only be used to edit templates of type BASE or DYNAMIC. The template in file {0} is of type {1}.

CRRZI0713E

The Template Editor failed to validate the layout due to an internal error. {0}

CRRZI0714E

The Create Template wizard failed to load {0}.

CRRZI0715E

The Create Template wizard failed to save the new template.

CRRZI0716E

A template can be opened in only one instance of the Template Editor at a time.

CRRZI0717E

A compilation failure has been reported. Check the File Manager compilation settings in the associated property group.

CRRZI0718E

The Update Template wizard failed to save the updated template.

CRRZI0719E

Unable to copy the VSAM cluster. Either IBM File Manager is unavailable or this operation is not supported in the current version of IBM File Manager.

CRRZI0720E

The data set could not be copied.

CRRZI0721W

There is a limit of 10 additional SYSLIB data sets. Only {0} of the selected SYSLIB data sets could be added.

CRRZI0722E

{0} is an invalid source for this table. Drag and drop a valid data set into this table.

CRRZI0723E

File Manager is unavailable on the target system. Verify the system configuration settings and try again.

CRRZI0724E

The client failed to send the {0} command to the host.

CRRZI0725E

An exception was generated by an invalid file resource.

CRRZI0726W

The file name is null.

CRRZI0727I

Updating the template.

CRRZI0728E

An incorrect version of File Manager was detected. Version found: {0} Version required: {1}

CRRZI0729E

An incorrect version of the File Manager Integration server was detected. Version found: {0} Version required: {1}

CRRZI0730E

An unknown version of File Manager has been detected.

CRRZI0731E

Multiple errors were reported during this operation.

CRRZI0732E

Data set could not be found.

CRRZI0733E

System is not connected. Connect to the system and try your action again.

CRRZI0734I

You must save your changes before switching to a different template. Save changes now?

CRRZI0735I

A folder was passed to the LogicalFSFileStore#getContents() method, which requires a file as input.

Explanation

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.

User response

No action is required.

CRRZI0736I

This file's contents are not available because the scheduling rule for the current job does not contain all the necessary resources.

Explanation

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.

User response

No action is required.

CRRZI0737W

The Rational Developer for System z server has been configured to automatically download product updates to the client when you connect to the remote system. Current Product Version shows the product version currently installed on your workstation. A new version cannot be rejected and will be installed when you click OK.

Explanation

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.

User response

Click OK.

CRRZI0738E

Update of a remote file failed.

CRRZI0739E

An error occurred when downloading the preprocessor output.

CRRZI0740E

The remote preprocessor ended with an error.

CRRZI0741E

The preprocessor output {0} was not found.

CRRZI0742E

The remote preprocessor {0} was not found.

CRRZI0743E

There is no preprocessor output location.

CRRZI0744E

There is no REXX invoking preprocessor.

CRRZI0745E

The project '{0}' does not have a property group associated with it. Associate a property group and then try the project build operation again.

Explanation

To build a project, you need associate a property group with it. No property group is associated with the project.

Response

Use the Associate Property Group action to associate a property group with a subproject and then try the build operation again.

CRRZI0746E

VSAM data set allocation failed.

Explanation

A New > Allocate VSAM Data Set operation failed to allocate the data set.

User response

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.

CRRZI8501E

A connection to {0} is required to complete this action.

CRRZI8502E

The format of the stored procedure source location is invalid.

CRRZI8503E

The source file is not available. You might need to connect a z/OS system.

CRRZI8504E

Unable to locate source file '{0}' on system '{1}'.

CRRZI8505E

The z/OS system definition for '{0}' does not exist. Switch to the z/OS Projects perspective and define '{0}' as a z/OS system with the approriate IP address.

CRRZI8506E

The data set '{0}' is migrated. Select the data set in the Remote Systems view and perform the HRECALL action.

CRRZI8507E

'{0}' already exists in '{1}'. Select a different source data set.

CRRZI8508E

'{0}' is not connected. Switch to the z/OS Projects perspective and connect to the z/OS system.

CRRZI8509E

The volume '{0}' is offline. Contact your systems programmer to bring the volume online.

CRRZI8510I

The selected file '{0}' is already open in another edit session. Close the edit session before opening this file as a stored procedure.

CRRZI8511W

The stored procedure already exists. Replace the existing stored procedure?

CRRZI9001I

This job output contains {0} lines. Specify the starting line and number of lines to retrieve.

Explanation

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.

User response

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.

CRRZI9002I

This job output contains {0} lines, which exceeds your specified job output retrieval limit. How would you like to proceed?

Explanation

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.

User response

You can choose from the following two options for displaying job output:
  • Show output from the first line to line number: Choose this option to open a portion of the job output. Specify a line number in the input field to open output from line 1 to the line number entered.
  • Show the complete job output: Choose this option to open the complete job output.

CRRZI9003E

Unable to connect to the JES Job Monitor on port {1} of host {0}.

Explanation

Rational Developer for System z was unable to establish a connection to JES using the port number shown on the remote system (host) shown.

User response

  1. Verify with your system administrator that the remote system is available and that the JES Job Monitor is installed and running.
  2. Open the JES properties page by selecting JES in the Remote Systems view and then selecting Properties. Verify with your system administrator that the correct port is specified.

CRRZI9004E

Not authorized for job {0}.

Explanation

You are not authorized to perform the requested action for the job number shown.

User response

Verify that you selected the correct job ID. Select a job that you are authorized to perform the action on and try again.

CRRZI9005I

Cancel has been issued for job {0}.

Explanation

A Cancel action has been issued for the job ID shown.

User response

No action is required.

CRRZI9006E

Job {0} cannot be canceled.

Explanation

A Cancel action has been issued for the job ID shown, but the job has already completed.

User response

No action is required.

CRRZI9007E

The entry for Job class is an empty string.

Explanation

The Job class field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job class field.

CRRZI9008I

Hold has been issued for job {0}.

Explanation

A Hold action has been issued for the job ID shown.

User response

No action is required.

CRRZI9009W

No information is available for job {0}. Unable to update the status.

Explanation

A Refresh Status action has been issued for the selected job, but no information is available. The job may have completed.

User response

No action is required.

CRRZI9010W

No jobs match the search criteria.

Explanation

A filter string entered into the Retrieve Job window has resulted in no matches.

User response

Enter another filter string and try again.

CRRZI9011W

No output for job {0}.

Explanation

An Open action for the job ID shown has failed because the job has produced no output or has not yet completed.

User response

Wait for the job to complete or select another job and try again.

CRRZI9012E

The entry for Job output class is an empty string.

Explanation

The Job output class field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job output class field.

CRRZI9013E

The entry for Job owner is invalid.

Explanation

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.

User response

Specify a value in the Job owner field. To specify the user ID with which you logged into the remote system, specify &USERID.

CRRZI9014E

The entry for Job name prefix is an empty string.

Explanation

The Job name prefix field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job name prefix field.

CRRZI9015I

Print has been issued for job {0}.

Explanation

A Print action has been issued for the job ID shown.

User response

No action is required.

CRRZI9016I

Purge has been issued for job {0}.

Explanation

A Purge action has been issued for the job ID shown.

User response

No action is required.

CRRZI9017I

Release has been issued for job {0}.

Explanation

A Release action has been issued for the job ID shown.

User response

No action is required.

CRRZI9018I

Restart has been issued for job {0}.

Explanation

A Restart action has been issued for the job ID shown.

User response

No action is required.

CRRZI9019E

The entry for Job status is an empty string.

Explanation

The Job status field on the New JES Job Filter window is required, but this field is empty.

User response

Specify a value in the Job status field.

CRRZI9020E

Login failed. The user ID or password is incorrect.

Explanation

An attempt to log on to the JES subsystem has failed because the password specified is incorrect.

User response

Specify a different password and try again.

CRRZI9021E

The entry for the maximum number of lines to download ({0}) is invalid.

Explanation

The value specified in the Max Number of Lines to Download field of the Properties for JES window is invalid.

User response

Specify a value between 1 and 2147483647.

CRRZI9022E

The password has expired.

Explanation

Your password for the remote system to which you are trying to connect has expired.

User response

Enter a new password when prompted. If you are not able to reset your password, contact your system administrator.

CRRZI9023E

The new password is not valid. Reenter a valid password.

Explanation

The password entered does not match your site's security requirements.

User response

Consult with your system administrator to obtain valid password requirements and try again.

CRRZI9024E

The entry for port {0} is invalid.

Explanation

The value specified in the JES Job Monitor Port field of the Properties for JES window is invalid.

User response

Consult your system administrator for the correct port number and try again.

CRRZI9025E

Unsupported server protocol level {0}.

CRRZI9026E

Unexpected RACF error encountered.

Explanation

A RACF error occurred while attempting to log on to the remote system.

User response

Contact your system administrator.

CRRZI9027I

The session has been idle more than {0} seconds. The connection has been terminated.

Explanation

The connection to the remote system has ended because of inactivity.

User response

Connect to the remote system again.

CRRZI9028E

Unable to allocate session code page conversion ({0}). Continue using default conversion.

CRRZI9029E

Unable to set the JES Job Monitor host code page to {0}. Continuing with the default host code page.

CRRZI9501W

There is 1 line with contents that exceed the maximum line length. Saving the file will result in truncation of this line. Do you want to continue?

Explanation

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.

Response

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.

CRRZI9502W

There are {0} lines with contents that exceed the maximum line length. Saving the file will result in truncation of these lines. Do you want to continue?

Explanation

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.

Response

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.

CRRZI9503W

The source has been modified since the backup copy was saved.

Explanation

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.

Response

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.

CRRZI9504I

A backup copy from {0} exists for the source you are opening. This occurred when your previous editing session ended abnormally. Would you like to open the backup copy in the editor?

Explanation

Rational Developer for System z has an autosave function that creates a backup copy of editor files on the local system.

Response

Click Yes to open the backup copy.

CRRZI9505W

The file cannot be saved on the host system. A backup copy has been created locally. You will be prompted to restore from this backup file the next time you open the remote file.

Explanation

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.

Response

No action is required.

CRRZI9506W

The file has been changed on the file system. Do you want to replace the editor contents with these changes?

Messages for MFS Screen Designer (MFS Map Editor)

These are the messages that pertain to the MFS Screen Designer (MFS Map Editor) in Rational Developer for System z.

CRRZM0159E

The input is not valid.

CRRZM0161E

The initial value not valid.

CRRZM0162E

The row is null.

CRRZM0163E

The position is not valid.

CRRZM0164E

The column is null.

Explanation

You must define at least one column.

User response

Define one or more columns.

CRRZM0165E

The length of the group name is not valid.

Explanation

The group name entered is too long/short.

User response

Enter a shorter/longer group name.

CRRZM0176E

An error occurred while opening the editor.

CRRZM0177E

An error occurred while parsing the source.

CRRZM0178E

An invalid name was specified.

CRRZM0178E

An invalid name was specified.

CRRZM0241E

File container must be specified

CRRZM0242E

File name must be specified

CRRZM0243E

File extension must be mfs

Explanation

The file extension is not correct.

User response

Change the file extension to mfs.

CRRZM0323E

Device format name is not valid.

Explanation

The device format name is not defined or not correct.

User response

Enter a valid device format name.

CRRZM0324E

The device format name is null.

Explanation

The device name is missing.

User response

Enter a valid device format name.

CRRZM0325E

The message definition name is not valid.

Explanation

The message definition name is not defined or not correct.

User response

Enter a valid message definition name.

CRRZM0326E

The message definition name is null.

Explanation

The message definition name is missing.

User response

Enter a valid message definition name.

CRRZM0331E

The file name is null.

Explanation

A file name cannot be null.

User response

Specify a file name that is not null.

CRRZM0332E

The file name is not valid.

Explanation

The file name used is not correct.

User response

Change the file name.

CRRZM0333E

A duplicate file name has been specified.

Explanation

The file name entered is already in use.

User response

Enter a different file name.

CRRZM0350E

No column has been defined.

Explanation

Table does not have a defined column.

User response

Select a valid column or insert a column into the table.

CRRZM0370E

The total width exceeds the defined table width.

Explanation

Size of insert is greater than table width..

User response

Insert a smaller selection.

CRRZM0437E

The width value is not valid. It must be in the range 1-120.

Explanation

The width value is not valid.

User response

Enter a valid value in the range of 1-120.

CRRZM0438E

The Features value is not set.

Explanation

The features value is missing.

User response

Enter a valid features value.

CRRZM0450E

The exit number value is not valid.

Explanation

The exit value i snot defined or not correct.

User response

Enter a valid exit number value.

CRRZM0451E

The exit vector value is not valid.

Explanation

The exit vector value is missing.

User response

Enter a valid exit vector value.

CRRZM0452E

A literal is longer than 255 characters.

Explanation

The literal value is over 255 characters.

User response

Enter a literal value of less than 255 characters.

CRRZM0453E

An extended attribute value is not between 1 and 10.

Explanation

An extended attribute value is not in the range 1-10.

User response

Specify an extended attribute value in the range 1-10.

CRRZM0454E

The length of the value does not equal the field length.

Explanation

The length of the value does not equal the field length.

User response

Enter a valid length value.

CRRZM0455E

The field length is 0.

Explanation

The length of the value does not equal the field length.

User response

Enter a valid length value.

CRRZM0456E

The row is null.

Explanation

You must define at least one row.

User response

Define one or more rows.

CRRZM0457E

The column is null.

Explanation

You must define at least one column.

User response

Define one or more columns.

CRRZM0458E

The field position is not valid.

Explanation

The entry used is not correct.

User response

Change or delete the field position value.

CRRZM0459E

The value of the offset is not valid.

Explanation

The entry is not correct.

User response

Change or delete the offset value.

CRRZM0460E

An invalid division name was entered.

Explanation

The entry used is not correct.

User response

Change or delete the division name value.

CRRZM0463E

The value of PAGE is not valid.

Explanation

The entry used is not correct.

User response

Change or delete the PAGE value.

CRRZM0464E

The value entered for Device Field cannot be used.

Explanation

The entry used is not correct.

User response

Change and delete the Device Field value.

CRRZM0465I

The COPY keyword is not supported.

CRRZM0467I

The selected statement cannot be edited. It is read-only.

CRRZM0470E

Copy file {0} was not found at the specified location.

Explanation

The path to the field is not valid or the file name is not valid.

User response

Verify both the path to the file and the file name.

CRRZM0471E

An error occurred when opening the file.

CRRZM0474E

Invalid character {0} was found after {1} at line {2} and column {3}..

Explanation

The character you entered is not allowed at the indicated location.

User response

Change or delete the character.

CRRZM0475E

The editor failed to parse statement {0} at line {1} column {2}.

Explanation

A parse error was found at the indicated location.

User response

Change or delete the parse statement.

CRRZM0476I

The specified value is not one of the following values: {0}

CRRZM0477E

A lexical error was encountered at line {0} and column {1}.

Explanation

A lexical error was found at the indicated location.

User response

Change or delete the character.

CRRZM0480E

An invalid location is selected.

Explanation

The location that is selected is not valid.

User response

Select a valid location.

CRRZM0481E

An invalid field name is entered.

Explanation

The field name that is entered is not valid.

User response

Enter a valid field name.

CRRZM0482I

A copybook file was created.

CRRZM0483I

The copybook file has been created.

CRRZM0484E

The file name is not valid.

Explanation

A file name was specified that is not valid.

User response

Specify a valid file name.

Messages for source code generation in Rational Developer for System z

These are the messages that pertain to generating source code in Rational Developer for System z.

CRRZP0001E

Container {0} does not exist.

Explanation

{0}
The name of a container
The specified container was not found.

User response

Create the specified container, or specify another container.

Messages for CICS Service Component Architecture (SCA)

These are the messages that pertain to the CICS Service Component Architecture (SCA) in Rational Developer for System z.

CRRZS1000E

An internal error occurred while parsing the source code for SCA references.

Explanation

This is an unexpected error that should not occur.

User response

Retry the action that you were performing. If the error persists, contact your IBM representative to report the problem.

CRRZS1001W

A reference was found in the source code at line {0}, column {1} for which a name could not be determined.

Explanation

{0}
Line number
{1}
Column number
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.

User response

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.

CRRZS1002E

An error occurred while trying to download the default Application Deployment Manager attributes for RDO bundles.

Explanation

The default attributes for RDO bundles should have been defined by your CICS system administrator.

User response

Verify with your CICS system administrator that this task was completed as described in the Rational Developer for System z Host Configuration Guide.

CRRZS1003E

An error occurred while creating the bundle archive file. Deployment stopped.

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS. After transfer is complete the archive is unpacked.

User response

Check the error log for more details, and retry the action. If the error persists, contact your IBM representative to report the problem.

CRRZS1004E

An error occurred while unpacking the bundle archive.

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS. After transfer is complete the archive is unpacked.

User response

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.

CRRZS1005E

An error occurred while deleting the contents of the remote folder.

Explanation

You selected to delete the contents of the remote bundle prior to deployment; however, an error occurred.

User response

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.

CRRZS1006E

An error occurred while transferring the bundle archive to the remote system.

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS.

User response

Verify that a connection to the remote system exists, that the remote folder exists and that the permissions are configured correctly.

CRRZS1007W

Unable to retrieve the complete results of the unpack operation from the remote shell.

Explanation

No response was received from the remote shell following the unpack operation for the archive file containing the bundle resources.

User response

Verify that all the bundle resources exist in the remote folder.

CRRZS1008I

Review the results of the unpacking operation:

Explanation

The resources in a bundle are packaged into an archive file for transfer to z/OS. After transfer is complete the archive is unpacked.

User response

It is recommended that you review the results of the unpacking operation.

CRRZS1009E

An error occurred while validating the existence of the remote folder.

Explanation

The remote folder must exist before transferring the bundle to z/OS.

User response

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.

CRRZS1010W

Unable to retrieve the complete results of the install BUNDLE resource operation.

Explanation

The attempt to verify the install operation did not return a valid response.

User response

Verify that the BUNDLE resource was installed.

CRRZS1011E

The selected CICS system or region does not support BUNDLE resources.

Explanation

The selected CICS system or region does not support BUNDLE resources. BUNDLE resources are supported in CICS TS 4.1 and higher.

User response

Select a CICS system or region that supports BUNDLE resources.

CRRZS1012E

An internal error occurred while removing the CICS Service Component Architecture 1.0 facet.

Explanation

This is an unexpected error that should not occur.

User response

Retry the action that you were performing. If the error persists, contact your IBM representative to report the problem.

CRRZS1013E

An internal error occurred while adding the CICS Service Component Architecture 1.0 facet.

Explanation

This is an unexpected error that should not occur.

User response

Retry the action that you were performing. If the error persists, contact your IBM representative to report the problem.

CRRZS2001E

The "Component type" attribute defined in the CICS Implementation properties of the component contains a path to a file that does not exist.

Explanation

Either the path name is incorrect or the file that should be there is missing.

User response

Correct the path name or create the file that is referenced.

CRRZS2002E

The "Bind file" attribute defined in the CICS Binding properties contains a path to a file that does not exist.

Explanation

Either the path name is incorrect or the file that should be there is missing.

User response

Correct the path name or create an appropriate file at the specified location.

CRRZS2003E

The "Call type" attribute defined in the CICS Implementation properties of the component contains an invalid value.

Explanation

The value of the call type attribute must be COMMAREA or CHANNEL.

User response

Specify a value of either COMMAREA or CHANNEL.

CRRZS2004E

The "Program" attribute defined in the CICS Implementation properties of the component is blank.

Explanation

You must specify a program attribute in a component's CICS Implementation properties.

User response

Specify a program attribute in a component's CICS Implementation properties.

CRRZS2005W

A policy set has been defined for the CICS SCA resource.

Explanation

Policy sets are not supported for CICS SCA resources.

User response

Remove the policy set.

CRRZS2006W

An intent has been defined for the CICS SCA resource.

Explanation

An intent has been defined for the CICS SCA resource.

User response

Remove the intent from the CICS SCA resources.

CRRZS2007W

A property has been defined for the CICS SCA resource.

Explanation

Properties are not supported for CICS SCA resources.

User response

Remove the property from the CICS SCA resources.

CRRZS3001W

File {0} already exists. To confirm overwriting of {1} to project {2}, select Yes. To use the existing file {0}, select No.

Explanation

{0}
The name of a file
{1}
The name of a file
{2}
The name of an MVS subproject
The specified file already exists in a particular project.

User response

To overwrite that file in that project, click Yes. To keep the existing file, click No.

CRRZS3002E

Errors exist in the project. Proceed with deployment?

Explanation

The project contains errors.

User response

To deploy the project anyway, click Yes. Otherwise click No.

CRRZS3003W

Warnings exist in the project. Proceed with deployment?

Explanation

The project contains warnings.

User response

To deploy the project anyway, click Yes. Otherwise click No.

Messages for code analysis for COBOL

These are the messages that pertain to code analysis for COBOL in Rational Developer for System z.

CRRZV0000E

An error occurred while closing the COBOL source file {0}. Error message: {1}

Explanation

{0}
File name
{1}
Message ID

CRRZV0001E

An error occurred while parsing the COBOL source file {0}. Error message: {1}

Explanation

{0}
File name
{1}
Message ID

CRRZV0002E

An error occurred while backing up the launch configuration file {0}. Error message: {1}

Explanation

{0}
File name
{1}
Message ID

CRRZV0003E

An error occurred while copying launch configuration files. Error message: {0}

Explanation

{0}
Message ID

CRRZV0004E

An error occurred while exporting the launch configuration files. Error message: {0}

Explanation

{0}
Message ID

CRRZV0005E

An error occurred while loading the launch configuration files. Error message: {0}

Explanation

{0}
Message ID

CRRZV0006E

An error occurred during the refreshing of the local workspace. Error message: {0}

Explanation

{0}
Message ID

CRRZV0007E

An error occurred while copying launch configuration file {0} to {1}. Error message: {2}

Explanation

{0}
File name
{1}
File name
{2}
Message ID

CRRZV0008E

An error occurred while loading a metadata collector plug-in. Error message: {0}

Explanation

{0}
Message ID

Host messages in Rational Developer for System z

This document contains information about the host messages for Rational Developer for System z.

Most host 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 client 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).

Host messages for CRASTART

These are the host messages that pertain to CRASTART in Rational Developer for System z.

CRAD1001W

Returned aaaaa. May be ABEND bbb.

Explanation

A program started by CRASTART ended with an return code of aaaaa which may indicate an abend code of bbb.

Response

This may not indicate a problem, but if work the started program did not complete correctly, diagnose the failing program using abend code bbb.

CRAD1002W

mmm

Explanation

The content of this message is the message returned from dynamic allocation (BPXWDYN) called by CRASERV.

Response

Response is dependent on the message contents.

CRAD1003W

DYNALLOC return cccc

Explanation

This message shows the return code cccc from dynamic allocation (BPXWDYN) called by CRASERV.

Response

Response is dependent on the message contents.

CRAD0001I

Configuration File Name

Explanation

This message shows the configuration file name from which CRASERV receives the commands to run.

Response

None.

CRAD0002I

Config handle hhhh

Explanation

This message shows the internal file number, hhhh, associated with a reading the CRASERV configuration file and is for diagnostic purposes only.

Response

None.

CRAD0003I

Echo of allocation line while reading configuration file

Explanation

This message displays the standard command read from the CRASERV configuration file. This is a diagnostic message.

Response

None

CRAD0004I

Echo of -COMMAND line while reading configuration file

Explanation

This message displays the dynamic allocation command read from the CRASERV configuration file. This is a diagnostic message.

Response

None

CRAD0005I

dddddddd OPEN

Explanation

This message displays the ddname, dddddddd, that is used by CRASERV as a ddname.

Response

If the ddname is not the same as is expected, verify that the correct ddname is specifie in the CRASERV configuration file.

CRAD0006I

Echo of program invocation line while reading configuration file

Explanation

This message displays the program invocation command read from the CRASERV configuration file. This is a diagnostic message.

CRAD0007I

Attach cccc

Explanation

The return code cccc was returned to CRASERV by the most recently called program.

Response

None

CRAD0008I

cccccccc p1 p2

Explanation

This message displays the program name (cccccccc) and parameters (p1, p2, ) that are about to be run by CRASERV. This is a diagnostic message.

Response

Verify that variable substitutions, if any, are correct.

CRAD0009I

CRASERV ended by user initiated disconnect.

Explanation

A CARMA user explicitly ended their connection.

Response

None

CRAD0010I

CRASERV ended due to a normal timeout.

Explanation

A CARMA users session timed out due to inactivity.

Response

None

CRAD0011I

Referback: dsname

Explanation

A dynamic allocation was done for data set dsname usung a referback.

Response

See the previous allocation statement for details of the referback.

Host messages for Application Deployment Manager

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.

CRAZ1650E

Router GET CONTAINER failure

Explanation

An error occurred while processing a web service request.

User response

No user response is required.

Administrator response

See the CICS documentation for RESP and RESP2 codes of the GET CONTAINER service.

CRAZ1651E

Router PUT CONTAINER failure

Explanation

An error occurred while processing a web service request.

User response

No user response is required.

Administrator response

See the CICS documentation for RESP and RESP2 codes of the PUT CONTAINER service.

CRAZ1652E

ADNREST Write HTTP header error

Explanation

An error occurred writing an HTTP header.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB WRITE to evaluate the RESP and RESP2 codes.

CRAZ1653E

ADNREST Web Send error

Explanation

An error occurred writing an HTTP header.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB SEND to evaluate the RESP and RESP2 codes.

CRAZ1654E

ADNREST CRDserver Link error

Explanation

An error occurred writing an HTTP header.

User response

No user response is required.

Administrator response

See the CICS documentation for LINK to evaluate the RESP and RESP2 codes.

CRAZ1655E

ADNREST Assign error

Explanation

An error occurred during an ASSIGN USERID() operation.

User response

No user response is required.

Administrator response

See the CICS documentation for ASSIGN to evaluate the RESP and RESP2 codes.

CRAZ1656E

ADNREST Extract error

Explanation

An error occurred during a WEB EXTRACT operation.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB EXTRACT to evaluate the RESP and RESP2 codes.

CRAZ1657E

ADNREST Read HTTP header error

Explanation

An error occurred during a WEB READ operation.

User response

No user response is required.

Administrator response

See the CICS documentation for WEB READ to evaluate the RESP and RESP2 codes.

Host messages for Common Access Repository Manager (CARMA)

These are the host messages that pertain to the Common Access Repository Manager (CARMA) in Rational Developer for System z.

CRRZC0020E

Internal Error: %s

CRRZC0022E

No RAMs defined for this locale

CRRZC0024E

CRADEF could not be opened for reading

CRRZC0025E

CRASTRS could not be opened for reading

CRRZC0026E

No RAM records found in CRADEF

CRRZC0028E

CRADEF read error

CRRZC0032E

Invalid CRADEF record found: %.8s

CRRZC0034E

Requested RAM not found: %i

CRRZC0036E

Could not load RAM module: %s

CRRZC0038E

Could not load pointer to RAM function: %s

CRRZC0040E

Requested RAM (%i) has not been loaded

CRRZC0042E

Invalid CRASTRS record found: %s

CRRZC0044E

CARMA has not been initialized

CRRZC0046E

Failed attempting to load the RAM list

CRRZC0048E

Out of memory

CRRZC0050E

Record %.8s in CRADEF does not have equivalent in CRASTRS for this locale

CRRZC0052E

Action %s references unknown parameter

CRRZC0054E

Action %s references unknown return type

CRRZC0056E

CRASTRS read error

CRRZC0058E

Neither the specified locale nor EN_US 00037 could be found in CRASTRS

CRRZC0060E

CRAMSG not found

CRRZC0062E

CRAMSG read error

CRRZC0064E

CRADEF error: Action 16 can not have custom parameters and/or returns

CRRZC0066E

Invalid type specified in VSAM record %s

CRRZC0068E

Invalid default value in VSAM record %s

CRRZC0101E

Could not allocate memory

CRRZC0102E

TSO/ISPF Library functions not available

CRRZC0103E

Invalid member identifier

CRRZC0104E

Cannot allocate (out of space)

CRRZC0105E

Member not found

CRRZC0106E

Instance not found

CRRZC0107E

Function not supported

CRRZC0108E

Member is not a container

CRRZC0109E

Invalid parameter value

CRRZC0110E

Member cannot be updated

CRRZC0111E

Member cannot be created

CRRZC0112E

Not authorized

CRRZC0113E

Could not initialize

CRRZC0114E

Could not terminate

CRRZC0115E

Resource out of sync

CRRZC0116E

File locked

CRRZC0117E

Specified next record out of range

CRRZC0118E

Unsupported record format

CRRZC0119E

Invalid LRECL

CRRZC0120E

Invalid metadata key

CRRZC0121E

Cannot update property value

CRRZC0122E

Invalid metadata value

CRRZC0123E

Property value is read-only

CRRZC0124E

Requested member is empty

CRRZC0125E

Empty instance

CRRZC0126E

No members found

CRRZC0127E

Reset error

CRRZC0128E

Delete error

CRRZC0129E

Member/Version is read-only

CRRZC0130E

Versioning not supported on member

CRRZC0196E

Could not setup ISPF variables

CRRZC0197E

(encapsulated ISPF/LMF error message)

CRRZC0198E

Unable to access log file

CRRZC0199E

Unknown RAM error

CRRZC0201E

CRASERV: The communication is not formatted correctly.

CRRZC0202E

CRASERV: Unknown function

CRRZC0203E

CRASERV: CARMA has not been initialized.

CRRZC0204E

CRASERV: The command was canceled.

CRRZC0205E

CRASERV: Could not allocate enough memory.

CRRZC0206E

CRASERV: Error encountered reading from the socket.

CRRZC0207E

CRASERV: Error encountered writing to the socket.

CRRZC0208E

CRASERV: The RAM id is not valid.

CRRZC0209E

CRASERV: The trace level is not valid.

CRRZC0210E

CRASERV: A valid locale was not provided.

CRRZC0211E

CRASERV: Expected parameters were not passed.

CRRZC0212E

CRASERV: The contents were not provided.

CRRZC0213E

CRASERV: Internal error

CRRZC0214E

CRASERV: The instance ID or filter was not provided.

CRRZC0215E

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

CRRZC0216E

CRASERV: The lrecl or numRecords is not valid.

CRRZC0217E

CRASERV: There were fewer records than specified.

CRRZC0218E

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

CRRZC0219E

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

CRRZC0220E

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

CRRZC0221E

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

CRRZC0222E

CRASERV: Error retrieving the Custom Action Framework parameter list.

CRRZC0223E

CRASERV: An expected Custom Action Framework parameter is missing.

CRRZC0224E

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

CRRZC0225E

CRASERV: Error gathering Custom Action Framework returns

CRRZC0299E

CRASERV: Unknown error

CRRZC0301E

The required RAMID is missing.

CRRZC0302E

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

CRRZC0303E

Unsupported CARMA Protocol version: {0}

CRRZC0304E

Server Error: Unsupported CARMA return code {0}.

CRRZC0305E

The CARMA response header could not be read.

CRRZC0306E

An unexpected end of server response has been reached.

CRRZC0310E

The RAM initialization state could not be located.

CRRZC0311W

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

CRRZC0312E

The file code-page conversion mapping is formatted incorrectly.

CRRZC0313E

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

CRRZC0315E

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

CRRZC0316E

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

CRRZC0317E

Internal error: The response body is empty.

CRRZC0318E

Internal error: The response processor is not set.

CRRZC0320E

Server Error: The metadata key could not be read.

CRRZC0321E

Server Error: The metadata value could not be read.

CRRZC0350E

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

CRRZC0351E

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

CRRZC0352E

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

CRRZC0360E

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

CRRZC0370E

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

CRRZC0371E

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

CRRZC0385E

Improper custom action configuration section count ({0,number,integer}).

CRRZC0392E

Invalid {0,choice,0#custom parameter|1#custom return value} type "{1}"

CRRZC0393E

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

CRRZC0394E

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

CRRZC0398E

Invalid {0,choice,0#custom parameter|1#custom return value} identifier ({1}) associated with action "{2}".

CRRZC0400E

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

CRRZC0402E

The required parameters are missing.

CRRZC0405E

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

CRRZC0406E

The server could not be loaded in an appropriate time frame. Contact the system programmer.

CRRZC0407E

The server startup was interrupted.

CRRZC0408E

Too many parameters to the REXX startup script.

CRRZC0409E

Could not access the configured CLIST.

CRRZC0411E

Missing the port argument for the CARMA Host server.

CRRZC0412E

Could not locate the REXX startup script.

CRRZC0413E

Missing the CLIST argument for the CARMA Host server.

CRRZC0415E

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

CRRZC0420E

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

CRRZC0421E

Codepage mapping is not supported by the CARMA host.

CRRZC0430E

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

CRRZC0431E

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

CRRZC0432E

DataStore State Exception: The Member Info container was not found in the required location.

CRRZC0433E

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

CRRZC0434E

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

CRRZC0450E

The download location argument could not be found.

CRRZC0451E

LRECL changed value during the download.

CRRZC0452E

RECFM changed value during the download.

CRRZC0480E

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

CRRZC0490E

Error in checking container property.

CRRZC0499E

An unidentified error occurred during upload.

CRRZC4011W

Could not load RAM. Not adding it to the list.

CRRZC4038W

Could not terminate the RAM.

CRRZC4039I

Custom action %s disabled.

CRRZC4040I

VSAM record %s requires '|' after parameter list for 6.0.1.x compatibility

CRRZC4041W

Warning: %s Perform Action (id=16) can not be disabled

CRRZC4042W

Warning: Attempt to disable action that does not exist in VSAM record %s

CRRZC4043W

Warning: No prompt given for VSAM record %s

CRRZC4044W

Warning: No description given for VSAM record %s

CRRZC4045W

Warning: Could not find RAM(s) for locale %s, using default locale of EN_US 00037

CRRZC4050I

RAM %i does not support function %s (%i)

Host messages for JES Job Monitor

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.

JM200I

Initialization complete.

JM201I

Could not allocate code page conversion tables.

JM202I

TCP/IP may have failed or been recycled. Server stopped.

JM203I

Session %d protocol %i initiated from <%s>:%d.

JM204I

Session ID is %d (protocol %i).

JM205I

Warning: Session limit exceeded.

JM206I

Session %d (%s) disconnected.

JM207I

SIGTERM received by main thread; server initiating shutdown.

JM208I

SIGUSR1 received on session %d (%s); thread will exit.

JM209I

SIGINT received by main thread.

JM211I

Server ready to accept connections.

JM212I

Notice: Server command %s issued by %s.

JM213I

Notice: Failed login attempt by %s on session %d.

JM214I

Login session %d (%s).

JM215I

Notice: Access to server command %s denied to %s.

JM216I

Session %d (user %s) was killed by %s.

JM217I

Logout session %d (%s).

JM221I

START JOB MONITOR CONFIGURATION

JM222I

%20s: %.88s

JM223I

Job Monitor " JOB_MONITOR_VERSION " initialization beginning. (Built: %s %s)

JM224I

Logout session %d (%s) due to idle timeout.

JM225I

Idle timeout thread starting (ThreadID=%x).

JM226I

Unexpected RACF error for user %s.

JM227I

Error on %s, SAF %d, RACF %d, Reason %d, User %s %s

JM228I

Unable to initialize security system. %s may be set incorrectly.

JM229I

Warning: Write to internal reader failed for user %s.

JM230I

%s

JM231I

Warning: Allocation of intrdr %s failed. Error 0x%08X, Reason 0x%08X.

JM232I

Thread creation failed for %s. Error 0x%08X, Reason 0x%08X.

JM233I

POSIX environment not available. Server cannot continue.

JM234I

This task must be run APF authorized.

JM235I

The specified JES does not support SSI request 54.

JM236I

The specified JES is not active.

JM237I

The specified JES is not defined to MVS.

JM238I

Internal SSI call library error.

JM249I

HOLD job %s from %s.

JM240I

Unknown SSI error: %d

JM243I

END JOB MONITOR CONFIGURATION

JM244I

Unexpected SAPI error: SSOBRETN %d, SSS2REAS %d

JM245I

SIGHUP received by main thread; server will reboot.

JM246I

CANCEL job %s from %s.

JM248I

GET SYSOUT dataset %s for job %s from %s (max %u lines)

JM249I

HOLD job %s from %s.

JM250I

PURGE job %s from %s.

JM251I

RELEASE job %s from %s.

JM252I

SEARCH jobs prefix=%s owner=%s status=%s class=%s outputclass=%s jobid=%s from %s.

JM253I

STATS for job %s from %s.

JM254I

SUBMIT from %s.

JM255I

Get SYSOUT dataset names for job %s from %s.

JM256I

SIGPIPE received on session %d (%s); thread will exit.

JM257I

Attempting to connect to %s:%d.

JM258I

Connect to client failed with rc=%d errno=%d.

JM259I

Session %d successfully connect to %s on port %d.

JM260I

Unable to create socket.

JM261I

Error reading socket, rc: %d, port: %d (remaining retries: %i).

JM262I

Expecting CONNECT.. request from %s, instead received: %s)

JM263I

PURGE failed with return code %d, %s.

JM264I

Out of storage.

JM265I

SVC 99 failed with error code = %d Information code = %d.

JM266I

pthread_detach() failed with errno %d.

JM267I

Open failed for data set %.44s.

JM268I

Allocate for dataset %s failed. Error: %d Reason: %d

JM269I

RELEASE failed with return code %d, %s.

JM270I

CANCEL failed with return code %d, %s.

JM271I

HOLD failed with return code %d, %s.

JM272I

Error: login %s(%s) on session %d (pthread_security_np() errno=%i errno2=%x).

JM273I

Session %i begins user thread (ThreadID=%x).

JM274I

Caller's IP address after ACCEPT is NULL (remaining retries %i).

JM275I

Accept failed rc=%i, errno=%i (remaining retries %i).

JM276I

Console thread starting (ThreadID=%x).

JM277I

Session %i received from client. (command=%s)

JM278I

Session %i UNKNOWN command from client. (command=%s)

JM279I

Server thread waiting for connection.

JM280I

%s received on thread (%x). But thread is NOT found in the session table, thread will exit now.

JM281I

SETCP clientCP=%s serverCP=%s.

JM282I

SUBMIT/DS: SUBMITMETHOD=%s, TSO_TEMPLATE=%s.

JM283I

Connect request from <%s>:%d (%s).

JM284I

Socket read success <%s>:%d.

JM285I

Socket contents available <%s>:%d.

JM286I

Socket read timeout <%s>:%d.

JM287I

SIGALRM received by main thread.

JM288I

CONSOLE_NAME is incorrect. Default value will be used: %s.

JM289I

DYNALLOC ddname %s, dsname %.44s

JM290I

DYNFREE ddname %s.%c

JM291I

DYNALLOC failed ddname %s, dsname %.44s, rc=%d, error code x%04x, info code x%04x.

JM292I

DYNFREE failed ddname %s, rc=%d, error code x%04x, info code x%04x.

JM293I

GETJCL %s from %s

JM294I

%20s: %.88s

Host messages for Configuration Utility

These are the host messages that pertain to the Configuration Utility in Rational Developer for System z.

FEKM001A

Java directory invalid

Explanation

The Java location field does not contain a valid directory name or the directory specified does not

FEKM002A

Directory invalid

Explanation

The directory name specified for RDZ configuration files contains invalid syntax.

FEKM003A

Directory invalid

Explanation

The directory name specified for the install does not exist.

FEKM004A

HLQ invalid

Explanation

Warning: Unable to locate RDZHLQ.SFEKLOAD. HLQ specified may be invalid.

FEKM006A

Data set name invalid

Explanation

The data set name does not comply with z/OS standards.

FEKM007I

Invalid Delete

Explanation

The DEFAULT user ID cannot be deleted.

FEKM011I

Invalid Work Flow

Explanation

The DEFAULT user ID does not have a Work Flow

FEKM015I

Invalid Prefix Command

Explanation

Valid Prefix commands are C, D, F, L, N, S, or W.

FEKM016I

Invalid Prefix Command

Explanation

Valid Prefix commands are C or V.

FEKM017I

Invalid Prefix Command

Explanation

Valid Prefix commands are A, C or E

FEKM019I

Invalid Prefix Command

Explanation

Valid Prefix commands are N or S until configured

FEKM020I

No Log Available

Explanation

There is no Log available for this Work Flow request because the request has not been Actioned.

FEK0000W

Message &1 Undefined

FEK0001I

&1

FEK0002E

Malformed XML header: line=&1 text=&2

FEK0003E

Malformed XML attribute: line=&1 text=&2

FEK0004E

Incorrect XML class terminator: line=&1 text=&2

FEK0005E

New XML class started before class end: line=&1 text=&2

FEK0006I

XML &1 class processing complete

FEK0007E

Unknown XML class specified: line=&1 text=&2

FEK0008E

Invalid command environment attribute: environment=&1 xmlid=&2

FEK0009E

EXECIO for &1 failed: rc=&2

FEK0010E

'&1' Trapped on line &2, rc &3 - '&4'

FEK0011E

Fatal error - Unable to continue

FEK0012I

FEK Processing completed successfully for &1

FEK0013E

EXECIO DISKR from &1 failed: rc=&2

FEK0014E

EXECIO DISKW to &1 failed: rc=&2

FEK0015W

FEK routine &1 gave bad return code &2

FEK0016E

USS command &1 gave bad return code &2

FEK0017E

TSO command &1 gave bad return code &2

FEK0018E

Member &1 of data set &2 not found

FEK0019E

Invalid selection

FEK0020I

Copy attempt FAILED, attempt to copy to user directory

FEK0030I

Work Flow actioned by &1 on &2 &3

FEK0031I

Work Flow processing commands from: &1

FEK0032I

Copy from &1 to &2 completed successfully

FEK0033E

Copy from &1 to &2 failed , rc=&3

FEK1001I

File &1 created.

FEK1002I

HFS file &1 created.

FEK1003I

Panel &1 displayed

FEK1004I

PDS file &1 created.

FEK1005I

OCOPY &1 to &2

FEK1006I

&1

FEK1007I

Unknown file type specified in file class.

FEK1008I

Run REXX exec &1

FEK1009I

Include ISPF skeleton &1

FEK1010I

Job &1

FEK1011I

... submitted

FEK1013I

Command &1

FEK1014I

...issued in environment &1, rc= &2

FEK1015I

Action manually completed by &1 on &3 &3

FEK1016I

Command response: &1

FEK1017I

Syscall environment not available.

FEK1018I

All returns are 0, this means the dir exists.

FEK1019I

Retval= &1 errono= &2

FEK1020I

The directory probably doesnt exist, attempting to create directory

FEK1021I

After mkdir rc= &1, retval= &2, errorno= &3

FEK1022I

lrc= &1, retval= &2, errorno= &3

FEK1023I

Could not create &1.

FEK1024I

...ensure you have authority to create this directory.

FEK1025I

Directory &1 created.

FEKR000W

Message &1 Undefined

FEKR001I

&1

FEKR002E

Malformed XML header: line=&1 text=&2

FEKR003E

Malformed XML attribute: line=&1 text=&2

FEKR004E

Incorrect XML class terminator: line=&1 text=&2

FEKR005E

- New XML class started before class end: line=&1 text=&2

FEKR006I

XML Class parsing complete for &1 name &2

FEKR007E

Unknown XML class specified: line=&1 text=&2

FEKR008E

Invalid command environment attribute: environment=&1 xmlid=&

FEKR009E

EXECIO for &1 failed: rc=&2

FEKR010E

'&1' Trapped on line &2, rc &3 - '&4'

FEKR011E

Fatal error - Unable to continue

FEKR012I

- RDZ Processing completed: RC=&1

FEKR013E

EXECIO DISKR from &1 failed: rc=&2

FEKR014E

EXECIO DISKW to &1 failed: rc=&2

FEKR015W

RDZ routine &1 gave bad return code &2

FEKR101I

File &1 created.

FEKR117I

Syscall environment not available.

FEKR118I

All returns are 0, this means the dir exists.

FEKR119I

Retval= &1 errono= &2

FEKR120I

The directory probably doesnt exist, attempting to create directory

FEKR121I

After mkdir rc= &1, retval= &2, errorno= &3

FEKR122I

lrc= &1, retval= &2, errorno= &3

FEKR123I

Could not create &1.

FEKR124I

...ensure you have authority to create this directory.

FEKR125I

Directory &1 created.

FEKR201I

Java &1 ICSF and RACF

FEKR202I

Java &1 ICSF and no RACF

FEKR204E

USS command &1 failed.

FEKR205I

USS command &1 Returned:

FEKR206I

--&gt;&1

Host messages for RSE daemon and RSE server

These are the host messages that pertain to the RSE daemon or the RSE server in Rational Developer for System z.

FEK001I

RseDaemon being initialized. in {0} bit mode.

FEK002I

RseDaemon started. (port={0})

FEK003I

Stop command being processed.

FEK004I

RseDaemon: Max Heap Size={0}MB and private AS Size={1}MB

FEK005I

Server process started. (processId={0})

FEK009I

RseDaemon is waiting for the server process to start.

FEK010I

(rsed.envvars location = {0})

FEK011I

(log directory = {0})

FEKO11I

(RSE home directory = {0})

FEK100E

Daemon port/timeout value must be digits

FEK101E

JRE {0} or higher required.

FEK102E

Invalid arguments received: {0}

FEK103E

Almost Disk-Full in {0}

FEK104E

Maximum number of processes has been reached.

FEK105E

Error in sending audit data (rc={0})

FEK110E

socket() failed. reason=({0})

FEK111E

setsockopt() failed. reason=({0})

FEK112E

bind() failed. reason=({0})

FEK113E

listen() failed. reason=({0})

FEK114E

accept() failed. reason=({0})

FEK115E

write() failed. reason=({0})

FEK116E

pipe() failed. reason=({0})

FEK117E

socketpair() failed. reason=({0})

FEK118E

select() failed. reason=({0})

FEK119E

_console() failed. reason=({0})

FEK130E

gsk_environment_open() failed. reason=({0})

FEK131E

gsk_attribute_set_enum(GSK_PROTOCOL_SSLV2) failed. reason=({0})

FEK132E

gsk_attribute_set_enum(GSK_PROTOCOL_SSLV3) failed. reason=({0})

FEK133E

gsk_attribute_set_enum(GSK_PROTOCOL_TLSV1) failed. reason=({0})

FEK134E

gsk_attribute_set_buffer(GSK_KEYRING_FILE) failed. reason=({0})

FEK135E

gsk_attribute_set_buffer(GSK_KEYRING_PW) failed. reason=({0})

FEK136E

gsk_environment_init() failed. reason=({0})

FEK137E

gsk_secure_socket_open() failed. reason=({0})

FEK138E

gsk_attribute_set_numeric_value(GSK_FD) failed. reason=({0})

FEK139E

gsk_attribute_set_buffer(GSK_KEYRING_LABEL) failed. reason=({0})

FEK140E

gsk_attribute_set_enum(GSK_SESSION_TYPE) failed. reason=({0})

FEK141E

gsk_attribute_set_callback(GSK_IO_CALLBACK) failed. reason=({0})

FEK142E

gsk_secure_socket_init() failed. reason=({0})

FEK143E

gsk_attribute_set_enum(GSK_CLIENT_AUTH_TYPE) failed. reason=({0})

FEK144E

gsk_get_cert_info failed. reason=({0})

FEK145E

gsk_secure_socket_read() failed. reason=({0})

FEK146E

gsk_secure_socket_write() failed. reason=({0})

FEK150E

RseDaemon abnormally terminated; {0}

FEK201I

{0} Command has been processed.

FEK202E

Invalid Command Entered.

FEK203E

Invalid Display Command: Display Process$$Client

FEK204E

Invalid Cancel Command: Cancel ID=$$User=

FEK205E

Command was not processed owing to consecutive SWITCHs

FEK206E

Audit Log facility is not active

FEK207I

No Client to be displayed

FEK208I

{0} canceled

FEK209I

No Process to be displayed.

FEK210I

{0} canceled owing to duplicate logo.

FEK501I

Lock daemon started, port={0}, cleanup interval={1}, log level={2}

FEK502I

Lock daemon terminating

FEK510E

Lock daemon, missing port

FEK511E

Lock daemon, wrong port, port={0}

FEK512E

Lock daemon, socket error, port={0}

FEK513W

Lock daemon, registration failed, ASID={0}, TCB={1}, USER={2}

FEK514W

Lock daemon, wrong log level, log level={0}

FEK900I

{0} IVP: {1}

FEK901I

{0} IVP Exit code = {1}

FEK910I

{0} EXIT : {1}

BPXM023

(stclock) dataset[(member)] NOT LOCKED

BPXM023

(stclock) dataset[(member)] LOCKED BY userid

BPXM023

(stclock) command, WRONG COMMAND

BPXM023

(stclock) command, MISSING ARGUMENT

BPXM023

(stclock) argument, WRONG ARGUMENT

Host messages for Enterprise Service Tools

These are the host messages that pertain to Enterprise Service Tools (EST) in Rational Developer for System z.

The messages in this section are not shown to you on a workstation. They exist only in a log on the host system.

IRZ0280S

XML to language structure conversion could not complete in program PROGRAM-NAME because an error return code of RETURN-CODE was received from the XML PARSE statement. The error occurred at XML path XML-PATH with the character content CHARACTER-CONTENT.

Explanation

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.

System programmer response

Use the return code to determine the error and correct the input XML message.

System action:
The converter 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.

IRZ0281S

XML to language structure conversion could not complete in program PROGRAM-NAME because the valid range of a repeating group or repeating data item was exceeded. The error occurred at XML path XML-PATH.

Explanation

XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.

System programmer response

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.

System action:
The converter 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.

IRZ0282S

XML to language structure conversion could not complete in program PROGRAM-NAME because none of the elements in the input XML document matched a mapped element in the XML Schema upon which the XML converter is based.

Explanation

XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.

System programmer response

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.

System action:
The converter 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.

IRZ0283S

XML to language structure conversion could not complete in program PROGRAM-NAME because the character content for XML path XML-PATH was longer than the mapped language structure member's maximum of LIMIT characters.

Explanation

XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.

System programmer response

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.

System action:
The converter 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.

IRZ0284S

XML to language structure conversion could not complete in program PROGRAM-NAME because conversion of the character content of an XML path that is mapped as numeric failed. The error occurred at XML path XML-PATH with the character content CHARACTER-CONTENT.

Explanation

XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.

System programmer response

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.

System action:
The converter 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.

IRZ0285S

XML to language structure conversion could not complete in program PROGRAM-NAME because the length of the XML document is LENGTH characters, which exceeds the maximum of MAXIMUM characters for this converter.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0286S

XML to language structure conversion could not complete in program PROGRAM-NAME because the character content for XML path XML-PATH had a length greater than or equal to LENGTH characters, which was too long for the converter to process.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0287S

Language structure to XML conversion could not complete in program PROGRAM-NAME because the maximum output message length of LENGTH characters was exceeded while generating the XML document.

Explanation

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).

System programmer response

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.

System action:
The converter 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.

IRZ0288S

Conversion could not complete in program PROGRAM-NAME because a non-zero return code was received from the Unicode Conversion Service CUNLCNV while converting from CCSID SOURCE-CCSID to CCSID TARGET-CCSID.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0289S

Language structure to XML conversion could not complete in program PROGRAM-NAME because the content of non-numeric member MEMBER-NAME of language structure STRUCTURE-NAME contained characters that are not legal in an XML document.

Explanation

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.

System programmer response

Ensure that the language structure member is properly initialized and does not contain any characters that are illegal in XML before attempting conversion.

System action:
The converter 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.

IRZ0290S

Language structure to XML conversion could not complete in program PROGRAM-NAME because the content of numeric member MEMBER-NAME of language structure STRUCTURE-NAME is invalid.

Explanation

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.

System programmer response

Ensure that the numeric language structure member is properly initialized according to COBOL semantics.

System action:
The converter 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.

IRZ0291S

XML to language structure conversion could not complete in program PROGRAM-NAME because the maximum XML element nesting depth was exceeded. The error occurred at XML path XML-PATH with character content CHARACTER-CONTENT.

Explanation

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.

System programmer response

Ensure that the numeric language structure member is properly initialized according to COBOL semantics.

System action:
The converter 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.

IRZ0292S

XML conversion could not complete in program PROGRAM-NAME because an attempt to register an exception handler failed with Language Environment error LE-ERROR.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0293S

XML conversion could not complete in program PROGRAM-NAME because an attempt to unregister an exception handler failed with Language Environment error LE-ERROR.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0294S

XML conversion could not complete in program PROGRAM-NAME because the address of one or more required parameters to the main entry point did not have valid addresses.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0295S

XML to language structure conversion could not complete in program PROGRAM-NAME because a response code of RESPONSE-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing the XML path XML-PATH.

Explanation

XML to language structure conversion makes use of an external module to handle bidirectional data conversions.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

System action:
The converter 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.

IRZ0296S

Language structure to XML conversion could not complete in program PROGRAM-NAME because a return code of RETURN-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing member MEMBER-NAME of language structure STRUCTURE-NAME.

Explanation

Language structure to XML conversion makes use of an external module to handle bidirectional data conversions.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

System action:
The converter 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.

IRZ0298S

XML to language structure conversion could not complete in program PROGRAM-NAME because the target namespace of XML path XML-PATH was NAMESPACE-ACTUAL which is inconsistent with the expected target namespace of NAMESPACE-EXPECTED.

Explanation

XML to language structure conversion can optionally validate the namespace name of XML elements.

System programmer response

Correct the XML instance document such that the XML elements have namespace names consistent with those specified in the XML Schema.

System action:
The converter 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.

IRZ0299S

XML to language structure conversion could not complete in program PROGRAM-NAME because the target namespace of XML path XML-PATH was NAMESPACE-ACTUAL which is inconsistent with the expected target namespace of NAMESPACE-EXPECTED.

Explanation

XML to language structure conversion can optionally validate the namespace name of XML elements.

System programmer response

Correct the XML instance document such that the XML elements have namespace names consistent with those specified in the XML Schema.

System action:
The converter 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.

IRZ0300S

XML to language structure conversion could not complete in program PROGRAM-NAME because the maximum count of language structure STRUCT-NAME was exceeded.

Explanation

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.

System programmer response

Correct the XML document or replace the XML converter with one having a higher maximum.

System action:
The converter 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.

IRZ0301S

Language structure to XML conversion could not complete in program PROGRAM-NAME because the total count of language structure instances received was ACTUAL-COUNT which is less than the minimum of MINIMUM-COUNT instances required by the message layout.

Explanation

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.

System programmer response

Correct the language structure buffer so that each language structure occurs at least as many times as is required per the message layout.

System action:
The converter 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.

IRZ0302S

Language structure to XML conversion could not complete in program program-name because the length prefix of language structure STRUCTURE-NAME specified a length of SPECIFIED-LENGTH bytes, which is less than the structure's minimum length of MINIMUM-LENGTH bytes.

Explanation

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.

System programmer response

Correctly set the two-byte length prefix of each language structure in the language structure buffer.

System action:
The converter 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.

IRZ0303S

Language structure to XML conversion could not complete in program PROGRAM-NAME because the total count of language structure instances received was ACTUAL-COUNT which is greater than the maximum of MAXIMUM-COUNT instances allowed by the message layout.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0500S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because a return code of RETURN-CODE was received from the API IRZXSETS when attempting to store language structure STRUCTURE-NAME into the IMS Connect message output buffer.

Explanation

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.

System programmer response

Refer to the IRZPWSIO module documentation, located in the RDz online help, for explanations of IRZXSETS return codes.
System action:
There are two possibilities:
  • If the optional feedback code argument is provided then the converter places in the argument a condition token representing the condition.
  • Otherwise the converter signals an IBM z/OS Language Environment® condition.

IRZ0501S

Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because a return code of RETURN-CODE was received from the API IRZXGETS when attempting to retrieve language structure STRUCTURE-NAME from the IMS Connect message input buffer.

Explanation

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.

System programmer response

Refer to the IRZPWSIO module documentation, located in the RDz online help, for explanations of IRZXGETS return codes.

System action:
There are two possibilities:
  • If the optional feedback code argument is provided then the converter places in the argument a condition token representing the condition.
  • Otherwise the converter signals an IBM z/OS Language Environment condition.

IRZ0502S

Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because the array counter variable COUNTER-NAME for array ARRAY-NAME specified a value of COUNTER-VALUE which exceeds the limit of the array, which is ARRAY-LIMIT.

Explanation

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.

System programmer response

Set the counter variable to a value that does not exceed the limit of the corresponding array.

System action:
There are two possibilities:
  • If the optional feedback code argument is provided then the converter places in the argument a condition token representing the condition.
  • Otherwise the converter signals an IBM z/OS Language Environment condition.

IRZ0503S

Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because an attempt to increase the size of the XML output buffer from OLD-SIZE to NEW-SIZE bytes failed with return code RETURN-CODE and runtime message RUNTIME-MESSAGE.

Explanation

In the top-down scenario, language structure to XML conversion allocates an initial XML output buffer that is reallocated to a larger size whenever a write would exceed the currently allocated space. How reallocation of the XML output buffer is performed depends on the target runtime environment. When language structure to XML conversion is executed in IMS Connect, reallocation of the XML output buffer is performed by having the XML converter call an IMS Connect XML Adapter API that supports buffer pooling and allows IMS Connect to maintain the lifetime of the storage.

System programmer response

Increase the amount of storage available in the runtime environment in which language structure to XML conversion is executing.

System action:
There are two possibilities:
  • If the optional feedback code argument is provided then the converter places in the argument a condition token representing the condition.
  • Otherwise the converter signals an IBM z/OS Language Environment condition.

IRZ0960S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because an error return code of RETURN-CODE was received from the PLISAX FUNCTION-SUFFIX built-in function. The error occurred at element ELEMENT-NAME with the character content CHARACTER-CONTENT.

Explanation

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".

System programmer response

Use the return code to determine the error and correct the input XML message.

System action:
The converter 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.

IRZ0961S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the valid range of a repeating group or repeating data item was exceeded. The error occurred at element ELEMENT-NAME.

Explanation

XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.

System programmer response

Correct the input XML message. Check that the input XML document has the correct number of occurrences of all entries that repeat.

System action:
The converter 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.

IRZ0962S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because no element names in the XML document were recognized by the converter.

Explanation

XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.

System programmer response

Supply the correct XML message corresponding to this converter.

System action:
The converter 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.

IRZ0963S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the character content for element ELEMENT-NAME was longer than the element's maximum of LIMIT characters.

Explanation

XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.

System programmer response

Correct the input XML message.

System action:
The converter 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.

IRZ0964S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the character content for element ELEMENT-NAME was longer than the element's maximum of LIMIT characters.

Explanation

XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.

System programmer response

Correct the input XML message.

System action:
The converter 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.

IRZ0965S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the size of the input XML message was LENGTH characters, which exceeds the maximum of MAXIMUM characters for this converter.

Explanation

XML to language structure conversion supports parsing XML messages whose length falls within certain compiler limits.

System programmer response

Correct the input XML message or define an auxiliary language structure(s) to process the XML in segments.

System action:
The converter 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.

IRZ0966S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the character content for element ELEMENT-NAME had a length equal to or greater than LENGTH characters which was too long for the converter to process.

Explanation

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.

System programmer response

Correct the input XML message. Check for any excessive whitespace in the element content.

System action:
The converter 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.

IRZ0967S

Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because the maximum output message size of SIZE characters was exceeded while creating the outbound XML document.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0968S

XML Conversion could not complete in procedure PROCEDURE-NAME because a non-zero return code was received from the Unicode Conversion Service CUNLCNV while converting from CCSID SOURCE-CCSID to CCSID TARGET-CCSID.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0969S

Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because the content of non-numeric member MEMBER-NAME of language structure STRUCTURE-NAME contained characters that are not legal in an XML document.

Explanation

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.

System programmer response

Ensure that the language structure member is properly initialized and does not contain any characters that are illegal in XML before attempting conversion.

System action:
The converter 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.

IRZ0970S

Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because the content of numeric member MEMBER-NAME of language structure STRUCTURE-NAME is invalid.

Explanation

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.

System programmer response

Ensure that the numeric data structure member is properly initialized following the semantics of the language.

System action:
The converter 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.

IRZ0971S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because the maximum XML element nesting depth was exceeded. The error occurred at element ELEMENT-NAME with character content CHARACTER-CONTENT.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0972S

XML conversion could not complete in procedure PROCEDURE-NAME because an attempt to register an exception handler failed with Language Environment error LE-ERROR.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0973S

XML conversion could not complete in procedure PROCEDURE-NAME because an attempt to unregister an exception handler failed with Language Environment error LE-ERROR.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0974S

XML conversion could not complete in procedure PROCEDURE-NAME because the address of one or more parameters was not valid.

Explanation

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.

System programmer response

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.

System action:
The converter 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.

IRZ0975S

XML to language structure conversion could not complete in procedure PROCEDURE-NAME because a response code of RESPONSE-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing element ELEMENT-NAME.

Explanation

XML to language structure conversion makes use of an external module to handle bidirectional data conversions.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

System action:
The converter 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.

IRZ0976S

Language structure to XML conversion could not complete in procedure PROCEDURE-NAME because a response code of RESPONSE-CODE with reason code REASON-CODE was received from the bidirectional data conversion module MODULE-NAME while processing member MEMBER-NAME of language structure STRUCTURE-NAME.

Explanation

Language structure to XML conversion makes use of an external module to handle bidirectional data conversions.

System programmer response

Refer to the bidirectional data conversion module documentation for explanations of return codes.

System action:
The converter 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.

IRZ0977S

Language Structure to XML conversion could not complete in procedure PROCEDURE-NAME because the length prefix in the language structure STRUCTURE-NAME specified a length of SPECIFIED-LENGTH bytes, which is less than the structure's minimum length of MINIMUM-LENGTH bytes.

Explanation

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.

System programmer response

Correctly set the two-byte length prefix of each language structure in the language structure buffer.

System action:
The converter 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.

IRZ1000S

CEEGTST failed in Compiled XML Conversion module MODULE-NAME with message number MESSAGE-NUMBER when attempting to allocate COUNT-BYTES bytes of storage for STORAGE-USAGE.

Explanation

The Compiled XML Conversion module cited in this message encountered an error when attempting to allocate storage using the Language Environment CEEGTST callable service.

System action

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.

Programmer response

Increase the amount of storage available to Compiled XML Conversion by increasing the maximum size of the region in which the module executes.

IRZ1001S

CEEFRST failed in Compiled XML Conversion module MODULE-NAME with message number when attempting to free storage for STORAGE-USAGE located at address STORAGE-ADDRESS.

Explanation

The Compiled XML Conversion module cited in this message was unable to free storage using the Language Environment CEEFRST callable service.

System action

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.

Programmer response

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.

IRZ1002S

CUNLCNV failed in Compiled XML Conversion module MODULE-NAME with return code RETURN-CODE and reason code REASON-CODE when attempting to convert from CCSID FROM-CCSID to CCSID TO-CCSID.

Explanation

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.

System action

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.

Programmer response

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.

Notices IBM Rational Developer for System z

?? 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.

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan, Ltd.
3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 Japan

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:

Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, Massachusetts 02421-3112
U.S.A.

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.

Copyright license

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.

Trademark acknowledgments

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.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)