Common problems

Certain common errors might be displayed while you are using applications on IBM® z/OS®.
Problem Solution
Cannot apply JDBC Stubbing rule: There are currently no JDBC agents registered.

The agent for z/OS is not running or is unable to communicate with HCL Quality Server. Verify that the agent was started. If it is running, verify that HCL Quality Server is running and that the steps in section Configuring the connection to HCL Quality Server were done correctly.
No events are recorded, and the recording studio Global Notifications window contains this message: No recorder/stub listening for SQL event from host hostname. The agent is receiving data for Db2® events from IBM Debug for z/OS, however, the EQA_DBG_RIT_ID does not match that of the agent for z/OS Filter that is used for recording.

Verify the host name and Db2® ssid are correct in the Db2® transport mapping. For batch jobs with EQA_DBG_RIT_ID in JCL, verify the value matches the Db2® z/OS agent filter.

No events are recorded, and the recording studio Global Notifications window contains this message: Failed to get connection using the url in the HCL OneTest™ API transport. Db2® returned the following message: Unrecognized SSL message, plain text connection? If the agent for z/OS is configured to use SSL for connections to Db2®, you must also enable SSL on the database transport in HCL OneTest™ API. Similarly, if the agent for z/OS is not configured to use SSL, you must ensure you did not select SSL on the database transport in HCL OneTest™ API.
Message +EQA9999W - z/OS Debugger TCPIP error within the job log for a batch program being recorded or stubbed. The batch job cannot connect to the agent for z/OS. If you are not using the Profile Service and Delay Debug mode, verify that the IP and port address specified within the CEEOPTS TEST DD statement are correct.
Table not created in the simulation database, and message Unable to create virtual table is displayed in the Recording Studio Global Notifications window. The integrated database does not support the same SQL functions and resource characteristics as Db2® for z/OS. For example, the integrated database only supports CHAR column lengths up to 254 characters, while the limit on Db2® for z/OS is higher. If possible, switch to using Db2® for z/OS as the simulation database.
OutOfMemoryException in the z/OS agent Increase the maximum amount of memory that the z/OS agent can access by adjusting the -Xmx parameter in the zosagent.ini file. The amount of memory required is dependent on the number of columns in the Db2 table being accessed, and the number of rows that can be queued to send to HCL OneTest™ API. For information on adjusting the maximum queue size, see HCL OneTest API and Agent for z/OS technical overview.
Message GC overhead limit exceeded when attempting to start a stub Increase the maximum amount of memory that HCL OneTest™ API can access. For more information. see JVM Arguments.