Testing with Db2 on z/OS systems

You can use workarounds to common problems that you might encounter when testing with DB2® on z/OS® systems.

Troubleshooting in the MVS Batch Db2 environment

When testing a batch program in the CICS® Db2 environment, the following events take place:
  1. The TEST(,,,RIT&my.clip.host%5555:) parameter in the CEEOPTS DD statement causes the Language Environment to start the CLIP back-end. To verify that the CLIP back-end is being started successfully, include the AQETRACE DD statement and AQE_DBG_TRACE=DD:AQETRACE in CEEOPTS within the batch job JCL.
    The following code snippet is an example:
    //AQETRACE DD SYSOUT=* 
    //CEEOPTS DD * 
    TEST(,,,RIT&my.clip.front.end.host%5555:) 
    ENVAR("AQE_DBG_DBRM=//'MY.COBOL.DBRM'",
    "AQE_DBG_TRACE=DD:AQETRACE", 
    "AQE_DBG_DB2SSID=MYDB") 
    After running the batch job, verify that messages have been written to AQETRACE. Look for messages referencing the CLIP SVC. If there is any error message related to SVC, ensure that the RITMGR started task is running.
  2. The CLIP back-end attempts to connect to the CLIP agent front-end. To verify that it was able to successfully connect, look for a message similar to the following, in the AQETRACE:
    openSocket(299): connect rc = 0, errno = 0 - EDC5000I No error occurred
    If the return code for the openSocket is not 0, ensure that the hostname or the IP address and port number specified on the CEEOPTS TEST parm are correct. You can find the port number used by the CLIP agent front-end from the CLIP front end start up messages:
    CRRDG7028I The Compiled Language Interception Processor Agent Daemon has started listening on port 5555
  3. With HCL OneTest™ API and HCL Quality Server, the CLIP agent front-end records the traffic between the batch program and Db2. If the SQL statements and results are not shown while recording within the Recording Studio, verify that the physical database definition in the Architecture School is properly set up.

    Within the Physical View of the Architecture School, open the physical database definition and click Test Connection. If it is not successful, ensure that the Database URL is correct. The last part of the URL should be the Db2 on z/OS Location name. Typically, the Location name can be found in the job log of the Db2 xxxxMSTR started task. If the Test Connection step is successful, verify that the z/OS system host name and Db2 subsystem ID are correctly specified in the Subsystem – Host Alias mappings tab.

  4. The CLIP agent front-end obtains a list of columns within the tables. If it cannot find this information, the Recording Studio might show that a SQL statement and the results are detected, but if a stub is created, no tables will be defined within the stub.

    If this problem occurs, verify with your Db2 support team if the Db2 installation jobs related to Db2 supplied stored procedures have been run. Also, verify that the associated WLM application environments have been defined and are available.

Troubleshooting in the CICS environment

When testing a program in the CICS environment, the following events take place:
  1. The CADP profiles are used to determine whether the CLIP back-end must to be invoked. To verify that the CLIP back-end is being invoked successfully, create a CADP profile manually and set the AQE_DBG_TRACE=3 environment variable. For instructions, see Setting up the CICS Db2 environment.

    To ensure that the manually created CADP profile is used, remove the URL of the profile manager web interface under the CADP URLs tab within the physical database definition in the Architecture School. After the CADP profile containing the environment variable has been created and activated, start the program under CICS. The CICS CEEMSG output dataset should contain messages from the CLIP back-end. If there are no messages in CEEMSG, review your CADP filter criteria, keeping in mind that the fields are case-sensitive.

    Verify that the CEEEVDBG module is being loaded from the HRELOAD dataset. You can do this by running the following CEMT command: CEMT I PROG(CEEEVDBG). A short form of the command output is displayed and looks similar to the following image:

    CEMT output

    Type ? to the left of Prog(CEEEVDBG) under the word Status to see the detailed output. Within the detailed output, the Library and Librarydsn identify the dataset containing CEEEVDBG. If CEEEVDBG has been loaded from somewhere other than HRELOAD, work with your support team to have the order of datasets in either DFHRPL or the LNKLST changed, so that HRELOAD is located before other datasets containing other versions of CEEEVDBG.

    CEMT output

  2. The CLIP back-end attempts to connect to the CLIP agent front-end. To verify that the connection was successful, look for a message similar to the following in the CEEMSG:
    openSocket(299): connect rc = 0, errno = 0 - EDC5000I No error occurred.
    If the return code for the openSocket is not 0, ensure that the hostname/IP address and port number mentioned in the CEEMSG messages are correct. You can find out the port number used by the CLIP agent front-end from the CLIP agent front-end start up messages:
    CRRDG7028I The Compiled Language Interception Processor Agent Daemon has started listening on port 5555
    For details about how to change the hostname (IP address) and the port number of the CLIP agent front-end within CADP, see Setting up the CICS Db2 environment.
  3. With HCL OneTest™ API and HCL Quality Server, the CLIP agent front-end records the traffic between the batch program and Db2. If the SQL statements and results are not shown while recording within the Recording Studio, verify that the physical database definition in the Architecture School is properly set up.

    Within the Physical View of the Architecture School, open the physical database definition and click Test Connection. If it is not successful, ensure that the Database URL is correct. The last part of the URL should be the Db2 on z/OS Location name. Typically, the Location name can be found in the job log of the Db2 xxxxMSTR started task. If the Test Connection step is successful, verify that the z/OS system host name and Db2 subsystem ID are correctly specified in the Subsystem – Host Alias mappings tab.

  4. The CLIP agent front-end obtains a list of columns within the tables. If it cannot find this information, the Recording Studio might show that a SQL statement and the results are detected, but if a stub is created, no tables will be defined within the stub.

    If this problem occurs, verify with your Db2 support team if the Db2 installation jobs related to Db2 supplied stored procedures have been run. Also, verify that the associated WLM application environments have been defined and are available.

Creating CADP profiles in the CICS environment automatically

The automatic creation of CADP profiles requires that the application debugging profile manager Web interface be available in the CICS system. In a web browser, open the same URL that you specify in the CADP URLs tab within the physical database definition to verify that the web interface is available.

Getting additional logs from the CLIP agent front-end

On Windows systems, the CLIP agent front-end is started by using clip.bat. To direct the debug log messages to the console from the CLIP agent front-end, add the following parameter to the end of the eclipse command within clip.bat:
-Dgreenhat.logappender.console.CONSOLE=layout:detailed,level:DEBUG
Feedback