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.
CRRZE2004E The host editor could not establish a
connection to the remote z/OS system.
CRRZE7200E
JCL file {file name} could not be submitted to remote system {host name}.
CRRZE7201E Pipeline {pipeline name} could not
be scanned: {error message}
CRRZE7202E Program resource {resource name} could not be created on CICS System/Region {resource name}: {error message}
CRRZE7204E Transaction resource {resource name} could not be created on CICS System/Region {resource name}: {error message}
CRRZE7206E Process type resource {resource name} could not be created on CICS System/Region {resource name}: {error message}
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.
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.
CRRZE7210E
An error occurred while creating file {file name} in {location}.
CRRZE7211E The service flow pickup directory could not
be rescanned, because the Service Flow Runtime flow scan program
DFHMAINS failed.
CRRZE7212E
The service flow
pickup directory could not be rescanned because a
program link failure occurred. RESP={value}
and RESP2={value}.
CRRZE7213E The service flow pickup directory could not
be rescanned because the CICS System/Region
{resource name} was not found.
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}.
CRRZE7218E The default Application Deployment Manager attributes
for RDO programs could not be downloaded.
CRRZE7219E The default Application Deployment Manager attributes
for RDO transactions could not be downloaded.
CRRZE7220E The default Application Deployment Manager attributes
for RDO process types could not be downloaded.
CRRZE7300E
COBOL generation stopped with an error.
An unknown exception occurred. Exception text: {error message}
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}
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.
CRRZE7303E An ESQL expression is
missing or invalid for {node type} node {node name}.
CRRZE7304E
COBOL generation stopped with an error.
{Resources} were not
found in the {containing resource}
named {resource name}. Method: {method name}
CRRZE7305E
Invalid syntax was found for {language}
in an expression in resource {resource
name}. Method: {method name}
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.
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}
CRRZE7311E
COBOL generation stopped with an error. The invoke type of node {invoke name} conflicts
with the flow type of the
flow.
CRRZE7312E
COBOL generation stopped with an error. A Link3270 Bridge flow requires the
use of imported BMS maps.
CRRZE7313E
COBOL generation stopped with an error. The generation of copybook {copybook name} failed in method: {method name}
CRRZE7315W String element {element name} in message {message name} does not have a length value. A default length value is assumed.
CRRZE7316E
COBOL generation stopped
with an error. The VectorElement named {element name} is not
a Command or a Navigator. Method: {method name}
CRRZE7317E
COBOL generation stopped
with an error. The VectorElement named {element name} does not
contain a Branch. Method: {method name}
CRRZE7318E
COBOL generation stopped
with an error. The MessageQualifier array
has no elements in node {node name}. Method:
{method name}
CRRZE7319E
COBOL generation stopped
with an error. The references array in a Branch is empty for node {node
name}. Method: {method name}
CRRZE7320E
COBOL generation stopped
with an error. A VectorReference was not found in a Branch
for node {node name}. Method: {method name}
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}
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}
CRRZE7323E
COBOL generation stopped
with an error. A VectorElement is not
of type {resource type} for {resource name}. Method: {method name}
CRRZE7324E
An ESQL expression contained
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.
CRRZE7326E
The flow is too large to document in the service flow properties
file. Please componentize segments of the flow as subflows.
CRRZE7327E An unexpected exception occurred because an index was out of bounds. Method:
{method name}
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.
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.
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.
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}.
CRRZE7333E
A code page conflict between screendescriptions 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}.
CRRZE7334E
An error occurred during Web service
generation in {method name}: {error message}
CRRZE7335E
Web service generation failed. File {file name} was not
generated. No additional information is available. Runtime code
was successfully generated.
CRRZE7336E
An error occurred during Web service
generation in method {method name}. See the error log for more information.
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.
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.
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.
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.
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.
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.
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
CRRZE7400E COBOL generation stopped with an error.
An input message was not found inthe interface operation associated
with an Invoke outbound Web service node.
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.
CRRZE7500E Flow playback or HATS macro generationstopped with an error. An unknown exception occurred.
Exception text: {0}
CRRZE7501E Flow playback or HATS macro generationstopped with an error. An internal error occurred.
CRRZE7502E Flow playback or HATS macro generationstopped with an error. Switch
nodes are not supported in this context.
CRRZE7503E Flow playback or HATS macro generationstopped with an error. Invoke
flow nodes are not supported in this context.
CRRZE7504E Flow playback or HATS macro generationstopped with an error. An input
message for the flow was not found.
CRRZE7505E Flow playback or HATS macro generationstopped with an error. Node {node
name} was not found or was null.
CRRZE7506E Flow playback or HATS macro generationstopped with an error. An input screen message
for the Invoke screen operation node {0} was not found or was null.
CRRZE7507E Flow playback or HATS macro generationstopped with an error. An output screen message
for the Invoke screen operation node {0} was not found or was null.
CRRZE7508E Flow playback or HATS macro generationstopped with an error. Variable updates for flow node {0} could not be generated because variable
{1} was not found.
CRRZE7509E Flow playback or HATS macro generationstopped with an error. Mapping routine {0} contains invalid ESQL syntax.
CRRZE7510W An unsupported ESQL keyword {0} was found in mapping routine {1} during
flow playback or HATS macro generation. The mapping expression
was ignored.
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.
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.
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}.
CRRZX0131W
No language structures were generated for global XSD element
{0} referenced by Operation {1} because no mappable elements or attributes
were found.
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.