Displayed at startup of the offline utility.
None.
None.
STDOUT
EYU9EJDD
The deployment descriptor has been successfully read from the CICS-deployed JAR file.
None.
None.
STDOUT
EYU9EJDD
The CICS descriptor has been successfully read from the CICS-deployed JAR file or created in the CICS-deployed JAR file.
None.
None.
STDOUT
EYU9EJDD
Termination message displayed when the Offline utility completes.
None.
None.
STDOUT
EYU9EJDD
The offline utiltiy has started parsing the input XML file.
None.
None.
STDOUT
EYU9EJDD
The input XML file was parsed successfully.
None.
None.
STDOUT
EYU9EJDD
Set the environment entries in the deployment descriptor based upon the input XML file.
None.
None.
STDOUT
EYU9EJDD
Creating or updating the CICS resources in the CICS-deployed JAR file specified in the input XML file.
None.
None.
STDOUT
EYU9EJDD
Removing the CICS resources from the CICS-deployed JAR file specified in the input XML file.
None.
None.
STDOUT
EYU9EJDD
The CICS DFHCSDUP stream has been generated and written to HFS.
None.
None.
STDOUT
EYU9EJDD
The CICSPlex® System Manager BATCHREP stream has been generated and written to HFS.
None.
None.
STDOUT
EYU9EJDD
The resource and reference binding values are being updated in the CICS-deployed JAR file.
None.
None.
STDOUT
EYU9EJDD
Errors have been found while updating the CICS-deployed JAR file contents and no updates will be written to HFS.
None.
Correct errors in the input XML file and re-execute the offline utility.
STDOUT
EYU9EJDD
The value of the CONTEXT field in the input XML file is longer than 8 characters.
None.
Correct errors in the input XML file and re-execute the offline utility.
STDOUT
EYU9EJDD
The value of the RESDESC field in the input XML file is longer than 8 characters.
None.
Correct errors in the input XML file and re-execute the offline utility.
STDOUT
EYU9EJDD
The value of the RESGROUP field in the input XML file is longer than 8 characters.
None.
Correct errors in the input XML file and re-execute the offline utility.
STDOUT
EYU9EJDD
The value of the CSDLIST field in the input XML file is longer than 8 characters
None.
Correct errors in the input XML file and re-execute the offline utility.
STDOUT
EYU9EJDD
The value of the CSDGROUP field in the input XML file is longer than 8 characters.
None.
Correct errors in the input XML file and re-execute the offline utility.
STDOUT
EYU9EJDD
The offline utility is currently attempting to update the Environment entry name attached to enterprise bean currentbean.
None.
None.
STDOUT
EYU9EJDD
The enviroment entry attached to enterprise bean currentbean has previously been updated and is now being overwritten.
None.
None.
STDOUT
EYU9EJDD
The value value cannot be set within the current environment entry as it is invalid for the type of entry env-entry-type.
The environment entry is not updated.
Update the input XML file with a suitable value.
STDOUT
EYU9EJDD
The JNDI binding named refname attached to enterprise bean currentbean is being updated.
None.
None.
STDOUT
EYU9EJDD
The JNDI binding named refname attached to enterprise bean currentbean has previously been updated and is being overwritten.
None.
None.
STDOUT
EYU9EJDD
The utility is defining the CORBASERVER associated with this CICS-deployed JAR file as name name.
None.
None.
STDOUT
EYU9EJDD
The utility is overwriting the CORBASERVER definition associated with the CICS-deployed JAR file as name name.
None.
None.
STDOUT
EYU9EJDD
The utility is defining the DJAR definition associated with this CICS-deployed JAR file as name name.
None.
None.
STDOUT
EYU9EJDD
The utility is overwriting the DJAR definition associated with the CICS-deployed JAR file as name name.
None.
None.
STDOUT
EYU9EJDD
The utility is defining a request model associated with this CICS-deployed JAR file as name name.
None.
None.
STDOUT
EYU9EJDD
The CORBASERVER definition named name is being removed from the CICS-deployed JAR file.
None.
None.
STDOUT
EYU9EJDD
The DJAR definition named name is being removed from the CICS-deployed JAR file.
None.
None.
STDOUT
EYU9EJDD
The request model definition named name is being removed from the CICS-deployed JAR file.
None.
None.
STDOUT
EYU9EJDD
The input XML file has not been specified on the command line.
Utility terminates.
Specify a valid XML input file on the command line.
STDOUT
EYU9EJDD
The utility is unable to read the deployment descriptor from the CICS-deployed JAR file.
Utility terminates.
Resolve any errors in the deployment descriptor and re-execute the utility.
STDOUT
EYU9EJDD
The utility is unable to read the specified input XML file.
Utility terminates.
Ensure the input XML file is readable, has the correct encoding attribute and the user ID has the correct USS security access.
STDOUT
EYU9EJDD
The input XML file does not contain any usable data.
Utility terminates.
Edit the input XML file.
STDOUT
EYU9EJDD
The name of the source CICS-deployed JAR file in the XML file is blank.
Utility terminates.
Update the XML file and enter a valid source CICS-deployed JAR file name.
STDOUT
EYU9EJDD
The name of the destination CICS-deployed JAR file in the XML file is blank.
Utility terminates.
Update the XML file and enter a valid destination CICS-deployed JAR file name.
STDOUT
EYU9EJDD
The utility cannot find the named source CICS-deployed JAR file.
Utility terminates.
Update the XML file and enter an existing source CICS-deployed JAR file.
STDOUT
EYU9EJDD
The name for the destination CICS-deployed JAR file is invalid.
Utility terminates.
Update the destination CICS-deployed JAR file field in the XML file and re-execute the utility.
STDOUT
EYU9EJDD
The parameters specifed for CorbaServer name in the input XML file are invalid.
No updates posted to destination CICS-deployed JAR file.
Correct the parameters for CorbaServer name name in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The parameters specifed for DJAR name in the input XML file are invalid.
No updates posted to destination JAR.
Correct the parameters for DJAR name name in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The parameters specifed for request model name name in the input XML file are invalid.
No updates posted to destination CICS-deployed JAR file.
Correct the parameters for request model name name in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The data in the input XML file for field fieldname exceeds the maximum length for that field.
No updates posted to destination CICS-deployed JAR file.
Correct the field value in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The data in the input XML file for field fieldname is not within the valid range for that field
No updates posted to destination CICS-deployed JAR file.
Correct the field value in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The numeric value in the input XML file for field fieldname is invalid.
No updates posted to destination CICS-deployed JAR file.
Correct the field value in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The record extracted from the input XML file was empty.
No updates posted to destination CICS-deployed JAR file.
Correct the field value in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The data in the input XML file for field fieldname is an invalid CVDA value.
No updates posted to destination CICS-deployed JAR file.
Correct the field value in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The values in the fields SSLPORT and PORT must not be equal.
No updates posted to destination CICS-deployed JAR file.
Update the values in one or both of the SSLPORT and PORT fields in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The value in the SSLPORT field has been omitted.
No updates posted to destination CICS-deployed JAR file.
Enter a value in the SSLPORT field in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The value in the field SSLPORT is invalid in conjunction with the SSL value of NO.
No updates posted to destination CICS-deployed JAR file.
Update the value in the SSLPORT field to NO or another valid value in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field interface-type must be BOTH.
No updates posted to destination CICS-deployed JAR file.
Update the value of the interface-type field in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field OPERATION must be an asterisk.
No updates posted to destination CICS-deployed JAR file.
Update the value of the OPERATION field to an asterisk in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field BEANNAME must be blank.
No updates posted to destination CICS-deployed JAR file.
Update the value of the BEANNAME field to be blank in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field BEANNAME must be generic.
No updates posted to destination CICS-deployed JAR file.
Update the value of the BEANNAME field to be generic in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field INTERFACE must be blank.
No updates posted to destination CICS-deployed JAR file.
Update the value of the INTERFACE field to be blank in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field MODULE must be blank.
No updates posted to destination CICS-deployed JAR file.
Update the value of the MODULE field to be blank in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field INTERFACE must be an asterisk.
No updates posted to destination CICS-deployed JAR file.
Update the value of the INTERFACE field to be an asterisk in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field Corba-Server must not be generic.
No updates posted to destination CICS-deployed JAR file.
Update the value of the CORBASERVER field to identify a specific CorbaServer in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field MODULE must be an asterisk.
No updates posted to destination CICS-deployed JAR file.
Update the value of the MODULE field to be an asterisk in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field BEANNAME must be an asterisk.
No updates posted to destination CICS-deployed JAR file.
Update the value of the BEANNAME field to be an asterisk in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field OPERATION must be blank.
No updates posted to destination CICS-deployed JAR file.
Update the value of the OPERATION field to be blank in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field interface-type must not be blank.
No updates posted to destination CICS-deployed JAR file.
Update the value of the interface-type field to be blank in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field BEANNAME must not be blank.
No updates posted to destination CICS-deployed JAR file.
Update the value of the BEANNAME field to be blank in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
For the field values of this request model, the field interface-type must be blank.
No updates posted to destination CICS-deployed JAR file.
Update the value of the interface-type field to be blank in the input XML file and re-execute the utility.
STDOUT
EYU9EJDD
The enterprise bean currentbean does not exist in this CICS-deployed JAR file and the utility cannot update the binding or environment entry associated with it.
No updates posted to destination CICS-deployed JAR file.
Update the value of the BEANNAME field to an existing enterprise bean and re-execute the utility.
STDOUT
EYU9EJDD
The filename specified as the target for receiving the DFHCSDUP output stream is invalid.
No updates posted to destination CICS-deployed JAR file.
Update the value of the output-destination for the cics-info tag with a valid filename and re-execute the utility.
STDOUT
EYU9EJDD
The filename specified as the target for receiving the BATCHREP output stream is invalid.
No updates posted to destination CICS-deployed JAR file.
Update the value of the output-destination for the cpsm-info tag with a valid filename and re-execute the utility.
STDOUT
EYU9EJDD
The binding link specified is incorrect. The only valid links supported are EJBRef or RESRef.
No updates posted to destination CICS-deployed JAR file.
Update the value of the link to either RESRef or EJBRef and re-execute the utility.
STDOUT
EYU9EJDD
The access permissions of the CICS-deployed JAR file are such that they cannot be accessed using the current user ID.
No updates posted to destination CICS-deployed JAR file.
Change to a user ID which has permission to edit the CICS-deployed JAR file , change the CICS-deployed JAR file permissions or select a different CICS-deployed JAR file, and re-execute the utility.
STDOUT
EYU9EJDD
There is a lock held against the source CICS-deployed JAR file which prevents the utility from accessing it.
No updates posted to destination CICS-deployed JAR file.
Resolve the locking problem, or access a different CICS-deployed JAR file.
STDOUT
EYU9EJDD
The bindings document found in the CICS-deployed JAR file does not exist, but we cannot create a new one to work with.
No updates posted to destination CICS-deployed JAR file.
Remove any bindings document contained in the CICS-deployed JAR file and re-execute the utility.
STDOUT
EYU9EJDD
The CICS document does not exist in the CICS-deployed JAR file, and we cannot successfully create a new one.
No updates posted to destination CICS-deployed JAR file.
Redeploy the CICS-deployed JAR file using the development deployment tool then re-execute the utility.
STDOUT
EYU9EJDD
There are no class files in the source CICS-deployed JAR file, which make it ineligible for deployment.
No updates posted to destination CICS-deployed JAR file.
Re-execute the utility using a CICS-deployed JAR file that can be deployed.
STDOUT
EYU9EJDD
The environment entry named name does not exist under the bean named currentbean in the CICS-deployed JAR file.
No updates posted to destination CICS-deployed JAR file.
Update the input XML file to reference an existing environment entry, or add the bean to the CICS-deployed JAR file and re-execute the utility.
STDOUT
EYU9EJDD
The binding reference named refname does not exist under the bean named currentbean in the CICS-deployed JAR file.
No updates posted to destination CICS-deployed JAR file.
Update the input XML file to reference an existing reference, or add the enterprise bean.
STDOUT
EYU9EJDD