BEA WebLogic Java Adapter for Mainframe Frequently Asked Questions

This document includes answers to Frequently Asked Questions (FAQ) for WebLogic JAM. For your convenience, the FAQs covered in this document are grouped into the following categories:

WebLogic Administration Console

The Java Adapter for Mainframe category does not appear in the left pane of the WebLogic Administration Console. Why?

The most probable cause is that the jam.jar and jam.ear files have not been deployed correctly. To correct this:

Gateway

How do I start/stop the Gateway?

You use the WebLogic Administration Console to start and stop a Gateway. For instructions, refer to Starting and Stopping a Gateway in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

How do I view Gateway statistics?

You use the WebLogic Administration Console to view Gateway statistics. For instructions, refer to Monitoring a Gateway in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

How do I enable Gateway tracing?

You use the WebLogic Administration Console to set the Gateway tracing levels. For instructions, refer to Modifying Trace Level Settings in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

The Gateway does not start. Why?

Check the following:

Why does the message "ERROR: Domain Name <domain_name> of connecting Gateway <Gateway_name> inconsistent with <text>" appear in the WebLogic log or the CRM standard error file?

The most probable cause is that Gateways from different administrative domains have attempted to connect to the same CRM. Verify that only Gateways from a single administrative domain are connecting to any CRM.

CRM

How do I start the CRM?

You can only start the CRM from the platform on which you installed the CRM. For instructions, refer to Starting the CRM in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

How do I stop the CRM?

You must stop the CRM from the platform on which you installed the CRM. For instructions, refer to Stopping the CRM in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

How do I start/stop a CRM link?

You use the WebLogic Administration Console to start and stop CRM links. For instructions, refer to Starting and Stopping CRM Links in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

How do I view CRM Link statistics?

You use the WebLogic Administration Console to view the statistics for a CRM link. For instructions, refer to Monitoring CRM Links in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

How do I enable CRM tracing?

You use the WebLogic Administration Console to set trace levels for the CRM. For instructions, refer to Modifying CRM Trace Level Settings in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

How do I view the CRM transaction logs?

You use the CRMLOGS command to view the CRM transaction logs. For instructions, refer to Viewing CRM Log Files in the BEA WebLogic Java Adapter for Mainframe Configuration and Administration Guide.

I cannot activate a CRM link. Why?

The most probable cause is incorrect values for the Maximum Session and Minimum Winner Session fields. The total of the Minimum Winner Session values on each peer of the connection must be less than or equal to the Maximum Session value.

Why does the message "ERROR: CRM Logical Unit <logical_unit> is probably inactive or unconfigured" appear in the WebLogic log or CRM standard error file?

The most probable cause is that the CRM logical unit is not active. To correct this:

Why does the message "ERROR: CRM Logical Unit <logical_unit> is already in use" appear in the WebLogic log or CRM standard error file?

The most probable cause is that the CRM logical unit is in use by another application. To correct this:

Why does the message "Socket listen failure!: EDC8115I Address already in use" appear in the CRM standard error file?

The most probable cause is that the listen port designated for the CRM is already in use. To correct this:

Why does the message "WARN: Synclevl on link <link_name> negotiated down to <number>" appear in the WebLogic log or the CRM standard error file?

The most probable cause is that the specified link is not configured for transactional operations. If this is not the desired behavior, do the following:

Why does the message "ERROR: CRM client message rejected -- incompatible software/protocol version (CRMAPI RC=<text>)" appear in the WebLogic log or the CRM standard error file?

The most probable cause is that different versions of the WebLogic JAM Gateway and CRM are being connected. Verify that current versions of both components are in use.

Why does the message "ERROR: Domain Name <domain_name> of connecting Gateway <Gateway_name> inconsistent with <text>" appear in the WebLogic log or the CRM standard error file?

The most probable cause is that Gateways from different administrative domains have attempted to connect to the same CRM. Verify that only Gateways from a single administrative domain are connecting to any CRM.

Why does the message "ERROR: Attempt to connect with incorrect CRM name (<CRM_Name>) refused!" appear in the WebLogic log or the CRM standard error file?

The most probable cause is that the name that was provided for the CRM at startup does not match the name provided in the WebLogic JAM configuration. To correct this:

WebLogic Log File

Why does the error message "JAM CRM Gateway: license has expired on <date>" appear in the WebLogic log?

Note: You may also see the error message "JAM CRM Gateway: License will expire within 30 days."

WebLogic JAM is delivered with a short-term evaluation license. Contact your Sales Representative for a long-term product license.

Why does the message "java.net.ConnectException: Connection refused: connect" appear in the WebLogic log?

The most probable cause is the Gateway was unable to connect to the CRM. To correct this:

Why does the message "WARN: Inbound Exchange Logs Rejected for <link_name>" appear in the WebLogic log or the CRM standard error file?

The most probable cause is that there is a discrepancy in the exchange logs. The affected links should be cold started.

Why does the message "9031 Unable to initialize link C10LINK2. Reason=AppcReturnCode::UnrecognizedModeName" appear in the WebLogic log or the CRM standard error file?

The most probable cause is that the mode name specified in the console is not recognized by the back-end system. To correct this:

For Additional Help

If you have any questions about using WebLogic JAM, or if you have problems installing and running WebLogic JAM, contact BEA Customer Support through BEA WebSupport at www.bea.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card that is included in the product package.

When contacting Customer Support, be prepared to provide the following information: