Before using this information, be sure to read the general information under Notices IBM Rational Developer for System z.
This edition applies to IBM® Rational® Developer for System z® Version 8.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.
This guide provides information about ...
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 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.
The record is invalid for one of the following reasons:
The attributes that caused the error are flagged on the result display window and one of the following messages that interpret the CICSPlex System Manager error code to provide an explanation for the attributes that are not valid. In all cases, the action is to correct the attribute value that is not valid and resubmit the request.
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.
Requests processed by the CICS Resource Definition (CRD) server return one of the following return codes. For the Warning and Error return codes an accompanying reason code is also provided.
The following messages indicate whether CICSPlex System Manager (CPSM) or CICS Configuration Manager (CCM) or both are installed.
The following messages indicate whether the CICS system programmer has authorized a CICS resource type to be installed:
At least one column must be defined.
The host editor encountered an internal error.
See the error log.
The host editor displays this error message whenever it cannot connect to the remote z/OS system that is specified in the current host connection.
The Generate Runtime Code wizard was unable to submit the JCL file to the remote z/OS system.
Make sure that you are logged onto the JES Connection using the Remote Systems View for the system you are deploying to. Make sure the data set you are moving your JCL files to is configured to support JCL files.
This error indicates that the specified pipeline was not successfully rescanned.
If the reason indicates that the selected CICS System/Region was not found, ensure the System/Region is defined using the connection preferences and that you are connected.
If the reason indicates that a CRD error has occurred, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).
This error indicates a failure to create a program resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while creating this resource.
If the reason indicates that it is a CRD error, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).
This error indicates a failure to create a transaction resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while creating this resource.
If the reason indicates that it is a CRD error, examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).
This error indicates a failure to create a process type resource on the selected CICS System/Region. The probable reason is that the CICS Resource Definition (CRD) server encountered a problem while creating this resource.
This message indicates that the connection to the CICS System/Region selected in the Generate Runtime Code Wizard was not found.
Ensure that the System/Region is defined using the connection preferences and that you are connected.
An error occurred while trying to run the CMIT transaction for the CICS Service Flow Runtime because the selected CICS System/Region is not CICS Transaction Server for z/OS V3.2 or later.
The CMIT transaction is installed only in CICS Transaction Server for z/OS V3.2 or later. Select the correct CICS System/Region in the Generate Runtime Code Wizard.
This message appears if you skip over replacing a pre-existing file or if the Application Deployment Manager subsystem encountered an error while creating the file at the specified location.
Ensure that your RSE Connections are connected. Ensure that your target directories or datasets are entered correctly and that you have write access to those destinations. Check the ADM log for additional details (the location of the Application Deployment Manager log is specified in the Preferences page for the Application Deployment Manager).
An error occurred while trying to run the CMIT transaction of the CICS Service Flow Runtime because the SFR flow scan program DFHMAINS abended.
Examine the CICS MSGUSR log and look for a message indicating that DFHMAINS has abended. The message will contain a specific 4-character abend code.
An error occurred while trying to run the CMIT transaction of the CICS Service Flow Runtime because of a program link failure.
See the RESP and RESP2 values for the LINK command in CICS Application Programming Reference (also see CICS response 2 (RESP2) codes in the online help for the Application Deployment Manager).
An error occurred while trying to run the CMIT transaction of the CICS Service Flow Runtime because the CICS System/Region selected in the Generate Runtime Code wizard could not be found.
Ensure that the System/Region was defined using the connection preferences and that the connection is open.
This is an internal error and normally should not occur.
The reason code returned by the Application Development Manager is a CICS Resource Definition server reason code (see CICS Resource Definition server reason codes in the online help for the Application Deployment Manager). Contact IBM Software Support to resolve the problem.
The Generate Runtime Code wizard was not able to retrieve the default values for RDO program resources from the CICS Resource Definition server.
The wizard uses these default values to create the program resources for the flow. These default values are set by the System Administrator.
Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).
The Generate Runtime Code wizard was not able to retrieve the default values for RDO transactions from the CICS Resource Definition (CRD) server.
The wizard uses these default values to create transaction resources for the flow and also when adding a transaction resource to a manifest file. These default values are set by the System Administrator.
Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).
The Generate Runtime Code wizard was not able to retrieve the default values for RDO ProcessType resources from the CICS Resource Definition (CRD) server.
The wizard uses these default values to create ProcessType resources for the flow. These default values are set by the System Administrator.
Examine the CICS MSGUSR log for error details and refer to the Application Deployment Manager documentation for steps to resolve the errors (see Client messages for Application Deployment Manager in the online help for the Application Deployment Manager).
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
The generation property specified by the error message contains an invalid value.
The flow you are attempting to generate contains more than one Receive node. Only one Receive node is allowed on a flow.
Modify your flow so that it contains only one Receive node.
This message appears when an ESQL expression associated with a Switch or While node is missing or has invalid contents.
Correct the problems with the referenced ESQL resource and run the Generate Runtime Code wizard again.
The Generate Runtime Code wizard did not find the specified resources in the specified containing resource as expected.
Open the referenced resource and correct the ESQL expression. The expression preventing successful generation is also listed as an error in the Problems view.
When generating a terminal service flow of flow type Link3270 Bridge, only fields named in the imported BMS maps can be referenced in the user-created screen descriptors.
The COBOL generator could not create a COBOL data structure from one of the messages used by the specified node.
Depending on the flow type of your service flow (Non Terminal, FEPI, Link3270 Bridge), only certain invoke types are supported. As specified in your Generation Properties, one of the invoke nodes in your Service Flow is of an invoke type that is not supported by the flow type of your flow (see About invoke types and About flow types).
Revise or remove from the flow any invoke node having an invoke type that is not supported by the flow type of the flow.
If the target runtime in the generation properties file is CICS Transaction Server for z/OS V3.1 and the flow type of the flow node in the generation properties file is Link3270 Bridge, each screen message referenced in the flow needs to contain BMS information (see When the flow type is Link3270 Bridge -- BMS map information).
When the target runtime is CICS Transaction Server for z/OS V3.1 and the flow type is Link3270 Bridge, each screen message must contain BMS map information.
To create a screen message that contains BMS map information, you can either import a BMS Map directly into the service flow project to create a screen message, or you can use the Assign BMS Field Names feature to update an existing screen messages (created by capturing a screen) with BMS information (see Working with information from BMS maps).
After doing these steps, you need to re-record the flow before generating runtime code.
There was an internal error generating the runtime code for your service flow.
This error message can occur if you accidentally delete a message resource referenced in your service flow. Resolve any errors or warning messages shown in the Problems view.
A length value was not specified for the String element. A default length value of 255 was used.
To set a value for the referenced message element:
In the editor area, select the Properties tab.
In the editor area, in the left pane, the flow message editor displays the Properties Hierarchy for this instance of the simple type xsd:string.
In the editor area, in the Properties Hierarchy, select .
In the right pane, in the Length Constraints group, in the Max field, type the maximum value that you want to use.
The maximum length for the element is set to the value that you typed in the Max field.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
This message can appear when a referenced file could not be found.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for the service flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your Service Flow.
Resolve any errors or warning messages shown in the Problems view.
An ESQL expression can have at most five CAST operations for a particular data type.
Rewrite your ESQL expressions so that they do not have more than the maximum number of CAST operations.
Only a subset of the ESQL Operations are supported by the service flow project tools at this time.
Consult the product documentation for the list of supported language elements (see ESQL reference). Remove the unsupported language element from the specified resource.
The service flow properties file has a maximum size limit of 32,600 characters. The size of the service flow properties file increases with each invoke node in the flow.
You will need to decrease the number of invoke nodes in your service flow until the size of the service flow properties file falls under its maximum size limit of 32,600 characters.
There was an internal error generating the runtime code for your Service Flow.
Resolve any errors or warning messages shown in the Problems view.
There was an internal error generating the runtime code for your Service Flow.
Resolve any errors or warning messages shown in the Problems view.
Depending on the target runtime you are generating to and whether you have specified a flow type of FEPI or Link3270, certain screen descriptors may or may not be supported.
Verify that the descriptors in the specified screen description are supported in the target runtime that you specified when you created the generation properties file (see Support for screen descriptors in the runtime environments).
There was an internal error generating the runtime code for your service flow.
Resolve any errors or warning messages shown in the Problems view.
Screen recognition criteria can only be matched against the first 160 characters of any field.
There is no workaround to this limitation. If this truncation results in a screen not being uniquely identified, add additional recognition criteria to the screen description.
The code page of a screen description must be the same as the code page specified in the generation properties file (also see CRRZE7333E).
All the screen descriptions in a terminal flow must use the same code page, and this code page must also be the same as the code page specified in the generation properties file for the flow (see CRRZE7332E).
The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files needed to invoke the generated service flow as a Web service. An error has been reported from the batch processor utility.
See troubleshooting information for single-service projects (see Batch processor).
The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files needed to invoke the generated service flow as a Web service. An error has been reported from the batch processor utility.
See troubleshooting information for single-service projects (see Batch processor).
The service flow project tools use the batch processor utility (from the single-service project tools) in bottom-up mode to create the WSDL and WSBind files needed to invoke the generated service flow as a Web service. An error has been reported from the batch processor utility.
See the troubleshooting information for single-service projects (see Batch processor). For more information about the error log see the topic "Error Log" in the top-level folder Eclipse documentation in the online help.
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.
A compile error will occur since the field is named the same as a COBOL reserved word.
A compile error will occur because references to two different data structures have the same name.
When you extract data from a screen message that has BMS information associated with it, you can extract data only from fields that were named in that BMS map. This holds true whether you are extracting from a single field or from a rectangular area.
Open the resource containing the reference to the non-named field. Remove any references to the non-named field. Fields which were not named are given default names during the import process based on the position they are found; for example, "Field30" is the default name given to an unnamed field at position 30 of an imported BMS map (see Default field name and Handling of String and Field Pattern descriptors when the flow type is Link3270 Bridge).
The Generate Runtime Code wizard could not calculate the COMMAREA length automatically for the Invoke nonterminal node specified in the error message.
In the generation properties editor, for the flow node specified in the error message, in the Maximum COMMAREA Length field, you selected Generate length value, a selection that should cause the Generate Runtime Code wizard to calculate the maximum length of the COMMAREA automatically. However, in this case the wizard could not calculate that length. Therefore you must calculate the length manually and type it into the field.
See Generation properties of the LINK with COMMAREA invoke type.
For the Invoke nonterminal application node specified in the error message, the length of the input messages or the length of the output messages (which are specified in the mappings for this node) is greater than the value specified in Maximum COMMAREA Length field for this node in the generation properties editor
Because this message is a warning rather than an error, no action is required. However, because this length discrepancy can cause a storage violation at runtime, you should consider making one of the following changes in the Maximum COMMAREA Length field in the generation properties editor:
Set the value to a number greater than calculated length of the input message and greater than the calculated length of the output message.
Select Generate length value and let the Generate Runtime Code wizard calculate the value automatically.
See Generation properties of the LINK with COMMAREA invoke type.
Restriction: When the Generate Runtime Code wizard creates COBOL source code for a Web service, and the flow from which the wizard creates the Web service contains a Throw node, then the wizard ignores the Throw node and does not create a return point for the Web service at the corresponding point in the COBOL source code.
The source code cannot contain additional return points associated with Throw nodes.
It is completely valid for a flow to contain one or more Throw nodes. But currently, when the Generate Runtime Code wizard is creating a Web service and encounters a Throw node, the wizard ignores the Throw node and does not create a corresponding return point in the COBOL source code.
Modify the design of the flow so that it does not rely on a Throw node as a return point to the program that invokes the flow.
An Invoke outbound Web service node in the flow is associated with an interface operation that does not contain an input message, or the Invoke outbound Web service node does not have an interface operation associated with it.
Open the .wsdl files in the Operations folder of your outbound Web service subproject with the operations editor until you find the operation that is missing an input message. Add an input message to that operation, save the operations file, and run the Generate Runtime Code wizard again.
An Invoke outbound Web service node in the flow is associated with an operation that has neither an output message nor a fault message. An outbound Web service operation must contain either an output message or a fault message, or can contain both.
Open the .wsdl files in the Operations folder of your outbound Web service subproject with the operations editor until you find the operation that lacks both an output message and a fault message. Add an output message or a fault message to that operation, save the operations file, and run the Generate Runtime Code wizard again.
An unexpected exception occurred during flow playback or during HATS macro generation.
Resolve any errors or warning messages shown in the Problems view.
An internal error occurred during flow playback or during HATS macro generation.
Resolve any errors or warning messages shown in the Problems view.
Flow playback and HATS macro generation do not support Switch nodes (see Limitations on features and capabilities when generating HATS macros or when playing flows).
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).
The interface operation for the flow does not contain an input message, or the flow is not associated with an interface operation.
The flow contains an invalid reference to the flow node specified in the error message. Either the reference is null or it refers to a flow node that could not be found in the flow.
The Invoke screen operation node specified in the error message is associated with a screen operation that has an invalid reference to an input screen message. Either the reference is null or it refers to an input screen message that could not be found in the flow.
Make sure the specified node is associated with a valid screen operation.
The Invoke screen operation node specified in the error message is associated with a screen operation that has an invalid reference to an output screen message. Either the reference is null or it refers to an output screen message that could not be found in the flow.
The flow node specified in the error message contained an instruction to write data into the specified variable, but the variable could not be found in the flow.
The mapping routine specified in the error message uses an element of ESQL syntax that is not supported in flow playback or in HATS macro generation (see Limitations on features and capabilities when generating HATS macros or when playing flows).
The macro routine specified in the error message contained the specified ESQL keyword. Most elements of ESQL are not supported during flow playback or HATS macro generation (see Restrictions on using ESQL).
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).
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).
The Batch Processor could not form a unique name for a converter driver file in the file container specified in DriverSpec/@fileContainer because no more unique 8-character file names could be generated from the specified prefix.
Specify a shorter prefix in DriverSpec/@fileNamePrefix to allow larger values of the ordinal used to resolve file name collisions.
If the empty message definition is intentional, no action is required, otherwise correct the XML schema and try again.
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.
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.
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.
Rational Developer for System z will shut down but you will not see any status. The product will restart automatically in a few minutes.
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).
The messages in this section are not shown to you on a workstation. They exist only in the CICS log on the host system.
The messages in this section are not shown to you on a workstation. They exist only in a log on the host system.
XML to language structure conversion makes use of the COBOL XML PARSE statement. When the XMLPARSE(COMPAT) compiler option is in effect, the return code is provided from the XML PARSE statement and is described in the Enterprise COBOL Programming Guide. When the XMLPARSE(XMLSS) compiler option is in effect, the return code is provided from the z/OS XML System Services Parser and is described in the XML System Services User's Guide and Reference.
Use the return code to determine the error and correct the input XML message.
XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
Correct the input XML message. Ensure that the message is valid according to the XML Schema upon which the XML to language structure converter is based.
XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
Correct the input XML message. Ensure that the message is valid according to the XML Schema upon which the XML to language structure converter is based.
XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
Correct the input XML message. Ensure that the message is valid according to the XML Schema upon which the XML to language structure converter is based.
XML to language structure conversion may encounter errors while transforming an XML message to a language structure that are distinct from XML PARSE errors.
Correct the input XML message. Ensure that the message is valid according to the XML Schema upon which the XML to language structure converter is based.
XML to language structure conversion imposes a limit on the length of XML documents that can be converted into language structures. The maximum length in bytes of the input XML document is 16MB when version 3 of Enterprise COBOL for z/OS is used and 32MB when version 4 of Enterprise COBOL for z/OS is used.
IBM Rational Developer for System z will normally prevent generation of XML to language structure converters when it is detected that an input XML message can exceed the 16MB or 32MB respective limit. Check that the input XML message conforms to the XML Schema upon which it is based and that any whitespace outside of element content has been trimmed.
XML to language structure conversion maintains a buffer for character content that has a maximum size equal to 10 times the size of the largest item in the target data structure. The content of an element was longer than expected.
Correct the input XML message. Ensure that the message is valid according to the XML Schema upon which the XML to language structure converter is based.
Language structure to XML conversion performs whitespace processing and entity reference expansion while generating the XML document. Entity reference expansion increases the length of data which is included as element content causing it to grow up to 6 times the original length of the data (the longest predefined entity is 6 characters long).
Ensure that the language structure has not changed since the Language structure to XML converter has been generated. Regenerate the XML converter if changes have been made to the language structure.
XML Conversion may convert XML and language data to and from Unicode during parsing and generation of XML if XML is expected to be exchanged in Unicode.
Check that conversion services is properly installed, and that the Unicode conversion attempted by the XML Converter is supported by the installation of conversion services on the target system.
Certain COBOL data declarations permit characters that are not legal in an XML document. The permitted characters are defined by the XML specification at http://www.w3c.org.
Ensure that the language structure member is properly initialized and does not contain any characters that are illegal in XML before attempting conversion.
Language structure to XML conversion has determined that the contents of the storage occupied by a numeric language structure member is invalid for the type.
Ensure that the numeric language structure member is properly initialized according to COBOL semantics.
The language structure to XML converter maintains an internal stack which represents the full qualification of the current element being processed in the XML document. If extraneous XML elements not described in the XML schema to which the converter is bound are present in the XML document, they may exceed the maximum supported element depth.
Ensure that the numeric language structure member is properly initialized according to COBOL semantics.
XML conversion uses Language Environment callable services to register a user-written handler to handle errors that occur during conversion. An attempt to register such a handler failed.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the XML converter which could prevent proper operation.
XML conversion uses Language Environment callable services to register a user-written handler to handle errors that occur during conversion. An attempt to unregister such a handler failed.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the XML converter which could prevent proper operation.
The converter detected that one or more of the parameters that were passed to its main entry point do not have valid storage addresses to which the converter could refer and obtain the value.
Ensure that each parameter passed to the XML converter has a valid non-null storage address unless a particular parameter can be null as defined by the converter call interface. For example, passing a null address for the XML buffer address to the language structure to XML converter will cause the required size of the XML buffer to be returned instead of performing XML conversion.
XML to language structure conversion makes use of an external module to handle bidirectional data conversions.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language structure to XML conversion makes use of an external module to handle bidirectional data conversions.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
XML to language structure conversion can optionally validate the namespace name of XML elements.
Correct the XML instance document such that the XML elements have namespace names consistent with those specified in the XML Schema.
XML to language structure conversion can optionally validate the namespace name of XML elements.
Correct the XML instance document such that the XML elements have namespace names consistent with those specified in the XML Schema.
XML to language structure conversion detected that the count of a language structure exceeds the maximum that was specified when the XML converter was generated.
Correct the XML document or replace the XML converter with one having a higher maximum.
Language structure to XML conversion detected that the language structure buffer it received contained fewer language structure instances in total than is required by the message layout.
Correct the language structure buffer so that each language structure occurs at least as many times as is required per the message layout.
Language structure to XML conversion detected that the length prefix of a language structure specified a length that is less than the minimum length of the structure. The minimum length of a language structure is computed as the sum of the bytes consumed by all subordinate fields. In the case of fields that specify OCCURS DEPENDING ON, the minimum number of occurrences is assumed.
Correctly set the two-byte length prefix of each language structure in the language structure buffer.
Language structure to XML conversion detected that the language structure buffer it received contained more language structure instances in total than is allowed by the message layout.
Correct the language structure buffer so that it contains no more than the maximum number of instances of each language structure in the message layout.
In the IMS top-down scenario XML to language structure conversion invokes an RDz-provided API named IRZXSETS to store one or more language structures into the IMS Connect message output buffer according to a symmetric protocol. A nonzero return code from IRZXSETS indicates that a language structure could not be stored in the IMS Connect message output buffer and therefore cannot be sent to the IMS application.
In the IMS top-down scenario language structure to XML conversion invokes an RDz-provided API named IRZXGETS to retrieve one or more language structures from the IMS Connect message input buffer according to a symmetric protocol. A nonzero return code from IRZXGETS indicates that a language structure could not be retrieved from the IMS Connect message input buffer and therefore cannot be converted to XML.
Refer to the IRZPWSIO module documentation, located in the RDz online help, for explanations of IRZXGETS return codes.
Explanation: In the top-down scenario language structure to XML conversion provides an application programmer the ability to specify the count of entries that XML conversion reads from an array through the use of generated counter variables. This message is issued if a counter variable is found to contain a value that exceeds the limit of its corresponding array.
Set the counter variable to a value that does not exceed the limit of the corresponding array.
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.
Increase the amount of storage available in the runtime environment in which language structure to XML conversion is executing.
XML to language structure conversion makes use of the PL/I PLISAXx built-in function. The return code provided is from the PL/I PLISAXx built in function as described in SC27-1457-05 (or later), "Enterprise PL/I for z/OS Programming Guide Version 3".
Use the return code to determine the error and correct the input XML message.
XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.
Correct the input XML message. Check that the input XML document has the correct number of occurrences of all entries that repeat.
XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.
Supply the correct XML message corresponding to this converter.
XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.
Correct the input XML message.
XML to language structure conversion may encounter errors that are distinct from PLISAXA/B errors.
Correct the input XML message.
XML to language structure conversion supports parsing XML messages whose length falls within certain compiler limits.
Correct the input XML message or define an auxiliary language structure(s) to process the XML in segments.
The XML converter maintains a buffer for character content whose size is equal to that of the largest character member in the language structure or 128, whichever is larger.
Correct the input XML message. Check for any excessive whitespace in the element content.
Language structure to XML conversion supports generation of XML messages whose length falls within certain compiler limits. Whitespace suppression and entity reference expansion is performed during creation of the XML document. Entity reference expansion increases the size of a message in relation to the number of special characters in the source language structure that need to be represented as one of the five predefined entity references in XML.
Avoid the use of the five predefined entires in XML when populating the language structure or define an auxiliary language structure(s) to generate the output XML in segments.
XML Conversion uses PL/I built-in support for UNICODE when the input XML or output XML is encoded in either UTF-16 or UTF-8.
Check that z/OS Support for UNICODE is properly installed and that the conversion attempted by the XML Conversion is supported by the current conversion image.
Certain language structure members permit storage of characters that are not legal in an XML document. The permitted characters are defined by the XML specification at http://www.w3c.org.
Ensure that the language structure member is properly initialized and does not contain any characters that are illegal in XML before attempting conversion.
Language structure to XML conversion has determined that the contents of the storage occupied by a numeric data structure member is invalid for the type.
Ensure that the numeric data structure member is properly initialized following the semantics of the language.
XML to language structure conversion maintains an internal stack which represents the full qualification of the current element being processed in the XML document. If extraneous XML elements not described in the XML schema to which the converter is bound are present in the XML document, they may exceed the maximum supported element depth.
Either supply XML documents to the converter that validate against the bound XML schema or remove the extraneous element that causes the failure from the input XML document.
The converter uses Language Environment callable services to handle errors that may occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the converter that would prevent proper operation.
The converter uses Language Environment callable services to handle errors that may occur during conversion. An attempt by the converter to register a Language Environment condition handler failed.
Ensure that Language Environment is configured properly and that no conditions exist in the chain of execution leading up to the converter that would prevent proper operation.
The converter detected that one or more of the parameters that were passed to its main entry point do not have valid storage addresses to which the converter could refer and obtain the value.
Ensure that each parameter passed to the converter has a valid storage address unless a particular parameter can be null as defined by the converter call interface. For example, a null message address passed to the outbound converter will be interpreted as a request for the maximum outbound message size to be returned instead of performing a conversion.
XML to language structure conversion makes use of an external module to handle bidirectional data conversions.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language structure to XML conversion makes use of an external module to handle bidirectional data conversions.
Refer to the bidirectional data conversion module documentation for explanations of return codes.
Language Structure to XML conversion detected that the length prefix of a language structure specified a length that is less than the minimum length of the structure. The minimum length of a language structure is computed as the sum of the bytes consumed by all subordinate fields.
Correctly set the two-byte length prefix of each language structure in the language structure buffer.
?? 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.
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Other product and service names might be trademarks of IBM or other companies.