EYUDDnnnn messages

EYUDD00I
CICS Production Deployment Tool for EJB Technology Offline utility.
Explanation:

Displayed at startup of the offline utility.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD01I
Deployment Descriptor read
Explanation:

The deployment descriptor has been successfully read from the CICS-deployed JAR file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD02I
CICS Descriptor read
Explanation:

The CICS descriptor has been successfully read from the CICS-deployed JAR file or created in the CICS-deployed JAR file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD03I
CICS Production Deployment Tool for EJB Technology Offline utility completed.
Explanation:

Termination message displayed when the Offline utility completes.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD04I
Extracting from input XML file.
Explanation:

The offline utiltiy has started parsing the input XML file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD05I
Finished extracting from input XML file.
Explanation:

The input XML file was parsed successfully.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD06I
Setting Environment Entries.
Explanation:

Set the environment entries in the deployment descriptor based upon the input XML file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD07I
Defining CICS resources.
Explanation:

Creating or updating the CICS resources in the CICS-deployed JAR file specified in the input XML file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD08I
Discarding CICS resources.
Explanation:

Removing the CICS resources from the CICS-deployed JAR file specified in the input XML file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD09I
CICS DFHCSDUP output generated.
Explanation:

The CICS DFHCSDUP stream has been generated and written to HFS.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD10I
CPSM BATCHREP output generated.
Explanation:

The CICSPlex® System Manager BATCHREP stream has been generated and written to HFS.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD11I
Binding resources and references.
Explanation:

The resource and reference binding values are being updated in the CICS-deployed JAR file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD12I
Errors found, JAR not updated and batch streams not generated.
Explanation:

Errors have been found while updating the CICS-deployed JAR file contents and no updates will be written to HFS.

System action:

None.

User response:

Correct errors in the input XML file and re-execute the offline utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD13E
CONTEXT is invalid, length exceeds 8 characters.
Explanation:

The value of the CONTEXT field in the input XML file is longer than 8 characters.

System action:

None.

User response:

Correct errors in the input XML file and re-execute the offline utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD14E
RESDESC is invalid, length exceeds 8 characters.
Explanation:

The value of the RESDESC field in the input XML file is longer than 8 characters.

System action:

None.

User response:

Correct errors in the input XML file and re-execute the offline utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD15E
RESGROUP is invalid, length exceeds 8 characters.
Explanation:

The value of the RESGROUP field in the input XML file is longer than 8 characters.

System action:

None.

User response:

Correct errors in the input XML file and re-execute the offline utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD16E
CSDLIST is invalid, length exceeds 8 characters.
Explanation:

The value of the CSDLIST field in the input XML file is longer than 8 characters

System action:

None.

User response:

Correct errors in the input XML file and re-execute the offline utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD17E
CSDGROUP is invalid, length exceeds 8 characters.
Explanation:

The value of the CSDGROUP field in the input XML file is longer than 8 characters.

System action:

None.

User response:

Correct errors in the input XML file and re-execute the offline utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD18I
Setting Environment Entry name in bean currentbean.
Explanation:

The offline utility is currently attempting to update the Environment entry name attached to enterprise bean currentbean.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD19I
Overwriting previously set Environment Entry name in bean currentbean.
Explanation:

The enviroment entry attached to enterprise bean currentbean has previously been updated and is now being overwritten.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD20E
Cannot set value to value, invalid for type env-entry-type.
Explanation:

The value value cannot be set within the current environment entry as it is invalid for the type of entry env-entry-type.

System action:

The environment entry is not updated.

User response:

Update the input XML file with a suitable value.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD21I
Setting JNDI binding named refname for bean currentbean.
Explanation:

The JNDI binding named refname attached to enterprise bean currentbean is being updated.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD22I
Overwriting previously set JNDI binding named refname in bean currentbean.
Explanation:

The JNDI binding named refname attached to enterprise bean currentbean has previously been updated and is being overwritten.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD23I
Defining CICS CORBAServer name.
Explanation:

The utility is defining the CORBASERVER associated with this CICS-deployed JAR file as name name.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD24I
Overwriting CICS CORBAServer definition as name
Explanation:

The utility is overwriting the CORBASERVER definition associated with the CICS-deployed JAR file as name name.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD25I
Defining CICS DJAR name.
Explanation:

The utility is defining the DJAR definition associated with this CICS-deployed JAR file as name name.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD26I
Overwriting CICS DJAR definition as name.
Explanation:

The utility is overwriting the DJAR definition associated with the CICS-deployed JAR file as name name.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD27I
Defining CICS Request Model name.
Explanation:

The utility is defining a request model associated with this CICS-deployed JAR file as name name.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD28I
Discarding CICS CORBAServer name.
Explanation:

The CORBASERVER definition named name is being removed from the CICS-deployed JAR file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD29I
Discarding CICS DJAR name.
Explanation:

The DJAR definition named name is being removed from the CICS-deployed JAR file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD30I
Discarding CICS Request Model name.
Explanation:

The request model definition named name is being removed from the CICS-deployed JAR file.

System action:

None.

User response:

None.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD31E
No input XML file specified.
Explanation:

The input XML file has not been specified on the command line.

System action:

Utility terminates.

User response:

Specify a valid XML input file on the command line.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD32E
Unable to read Deployment Descriptor.
Explanation:

The utility is unable to read the deployment descriptor from the CICS-deployed JAR file.

System action:

Utility terminates.

User response:

Resolve any errors in the deployment descriptor and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD33E
Unable to read/process input XML file.
Explanation:

The utility is unable to read the specified input XML file.

System action:

Utility terminates.

User response:

Ensure the input XML file is readable, has the correct encoding attribute and the user ID has the correct USS security access.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD34E
Empty input XML file. Finished extracting.
Explanation:

The input XML file does not contain any usable data.

System action:

Utility terminates.

User response:

Edit the input XML file.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD35E
Source JAR name is blank.
Explanation:

The name of the source CICS-deployed JAR file in the XML file is blank.

System action:

Utility terminates.

User response:

Update the XML file and enter a valid source CICS-deployed JAR file name.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD36E
Destination JAR name is blank.
Explanation:

The name of the destination CICS-deployed JAR file in the XML file is blank.

System action:

Utility terminates.

User response:

Update the XML file and enter a valid destination CICS-deployed JAR file name.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD37E
Cannot find source JAR.
Explanation:

The utility cannot find the named source CICS-deployed JAR file.

System action:

Utility terminates.

User response:

Update the XML file and enter an existing source CICS-deployed JAR file.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD38E
Invalid destination JAR.
Explanation:

The name for the destination CICS-deployed JAR file is invalid.

System action:

Utility terminates.

User response:

Update the destination CICS-deployed JAR file field in the XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD39E
Cannot define CICS CORBAServer name
Explanation:

The parameters specifed for CorbaServer name in the input XML file are invalid.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Correct the parameters for CorbaServer name name in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD40E
Cannot define CICS DJAR name.
Explanation:

The parameters specifed for DJAR name in the input XML file are invalid.

System action:

No updates posted to destination JAR.

User response:

Correct the parameters for DJAR name name in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD41E
Cannot define CICS RequestModel name.
Explanation:

The parameters specifed for request model name name in the input XML file are invalid.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Correct the parameters for request model name name in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD42E
Field(fieldname) exceeds maximum length.
Explanation:

The data in the input XML file for field fieldname exceeds the maximum length for that field.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Correct the field value in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD43E
Field(fieldname) Value out of range.
Explanation:

The data in the input XML file for field fieldname is not within the valid range for that field

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Correct the field value in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD44E
Field(fieldname) Invalid number entered.
Explanation:

The numeric value in the input XML file for field fieldname is invalid.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Correct the field value in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD45E
Null record entered.
Explanation:

The record extracted from the input XML file was empty.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Correct the field value in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD46E
Field(fieldname) Invalid selection.
Explanation:

The data in the input XML file for field fieldname is an invalid CVDA value.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Correct the field value in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD47E
SSLPORT and PORT must contain different values.
Explanation:

The values in the fields SSLPORT and PORT must not be equal.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the values in one or both of the SSLPORT and PORT fields in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD48E
SSLPORT value required.
Explanation:

The value in the SSLPORT field has been omitted.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Enter a value in the SSLPORT field in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD49E
SSLPORT value is not valid for SSL = NO.
Explanation:

The value in the field SSLPORT is invalid in conjunction with the SSL value of NO.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value in the SSLPORT field to NO or another valid value in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD50E
INTFACETYPE must be BOTH.
Explanation:

For the field values of this request model, the field interface-type must be BOTH.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the interface-type field in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD51E
OPERATION must be an asterisk.
Explanation:

For the field values of this request model, the field OPERATION must be an asterisk.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the OPERATION field to an asterisk in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD52E
BEANNAME must be blank.
Explanation:

For the field values of this request model, the field BEANNAME must be blank.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the BEANNAME field to be blank in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD53E
BEANNAME must be generic.
Explanation:

For the field values of this request model, the field BEANNAME must be generic.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the BEANNAME field to be generic in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD54E
INTERFACE must be blank.
Explanation:

For the field values of this request model, the field INTERFACE must be blank.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the INTERFACE field to be blank in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD55E
MODULE must be blank.
Explanation:

For the field values of this request model, the field MODULE must be blank.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the MODULE field to be blank in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD56E
INTERFACE must be an asterisk.
Explanation:

For the field values of this request model, the field INTERFACE must be an asterisk.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the INTERFACE field to be an asterisk in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD57E
CORBA Server must not be an asterisk.
Explanation:

For the field values of this request model, the field Corba-Server must not be generic.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the CORBASERVER field to identify a specific CorbaServer in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD58E
MODULE must be an asterisk.
Explanation:

For the field values of this request model, the field MODULE must be an asterisk.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the MODULE field to be an asterisk in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD59E
BEANNAME must be an asterisk.
Explanation:

For the field values of this request model, the field BEANNAME must be an asterisk.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the BEANNAME field to be an asterisk in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD60E
OPERATION must be blank.
Explanation:

For the field values of this request model, the field OPERATION must be blank.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the OPERATION field to be blank in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD61E
INTFACETYPE must not be blank.
Explanation:

For the field values of this request model, the field interface-type must not be blank.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the interface-type field to be blank in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD62E
BEANNAME must not be blank.
Explanation:

For the field values of this request model, the field BEANNAME must not be blank.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the BEANNAME field to be blank in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD63E
INTFACETYPE must be blank.
Explanation:

For the field values of this request model, the field interface-type must be blank.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the interface-type field to be blank in the input XML file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD64E
Bean (currentbean) does not exist in this JAR.
Explanation:

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.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the BEANNAME field to an existing enterprise bean and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD65E
Invalid filename for CICS DFHCSDUP output.
Explanation:

The filename specified as the target for receiving the DFHCSDUP output stream is invalid.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the output-destination for the cics-info tag with a valid filename and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD66E
Invalid filename for CICSPlex SM BATCHREP output.
Explanation:

The filename specified as the target for receiving the BATCHREP output stream is invalid.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the output-destination for the cpsm-info tag with a valid filename and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD67E
Invalid bindings link specified. "Must be EJBRef or RESRef only".
Explanation:

The binding link specified is incorrect. The only valid links supported are EJBRef or RESRef.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the value of the link to either RESRef or EJBRef and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD68E
You are not authorised to access the Source JAR
Explanation:

The access permissions of the CICS-deployed JAR file are such that they cannot be accessed using the current user ID.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

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.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD69E
Cannot read from the Source JAR
Explanation:

There is a lock held against the source CICS-deployed JAR file which prevents the utility from accessing it.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Resolve the locking problem, or access a different CICS-deployed JAR file.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD70E
Cannot create bindings document in Source JAR
Explanation:

The bindings document found in the CICS-deployed JAR file does not exist, but we cannot create a new one to work with.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Remove any bindings document contained in the CICS-deployed JAR file and re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD71E
Cannot create CICS document in Source JAR
Explanation:

The CICS document does not exist in the CICS-deployed JAR file, and we cannot successfully create a new one.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Redeploy the CICS-deployed JAR file using the development deployment tool then re-execute the utility.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD72E
Source JAR contains no classes and cannot be deployed
Explanation:

There are no class files in the source CICS-deployed JAR file, which make it ineligible for deployment.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Re-execute the utility using a CICS-deployed JAR file that can be deployed.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD73E
Environment Entry (name) in bean (currentbean) does not exist in this JAR
Explanation:

The environment entry named name does not exist under the bean named currentbean in the CICS-deployed JAR file.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

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.

Destination:

STDOUT

Module:

EYU9EJDD

EYUDD74E
Reference (refname) for bean (currentbean) does not exist in this JAR
Explanation:

The binding reference named refname does not exist under the bean named currentbean in the CICS-deployed JAR file.

System action:

No updates posted to destination CICS-deployed JAR file.

User response:

Update the input XML file to reference an existing reference, or add the enterprise bean.

Destination:

STDOUT

Module:

EYU9EJDD

[[ Contents Previous Page | Next Page Index ]]