SQL code -430 from IBM Db2 Analytics Accelerator for z/OS stored procedures

A stored procedure of IBM Db2 Analytics Accelerator for z/OS ends abnormally, and you receive an error message with SQL code -430.

Symptoms

IBM Db2 Analytics Accelerator for z/OS stored procedures end abnormally. Your administration client returns a message window like this one:
Figure 1. SQL code -430 message window
Message window that is displayed in IBM Db2 Analytics Accelerator Studio when an SQL code -430 error occurs

Causes

This might be a configuration problem.

Diagnosing the problem

  1. Verify that the IBM Db2 Analytics Accelerator for z/OS stored procedures run in a separate Workload Manager (WLM) environment. Each application environment must be set up according to the instructions in Setting up a WLM application environment for IBM Db2 Analytics Accelerator. In particular, the ADMIN_INFO_SYSPARM and DSNUTILU stored procedures must run in different WLM environments and NUMTCB must be set to the correct value.
  2. If the problem persists, collect the following diagnostic information for IBM support:
    • CEEDUMP in the WLM job
    • Stored procedure trace files in the z/FS directory /tmp. The names of these files follow this pattern:
      aqt-trace-<YYYYMMDD-HHMM>-<procedure name>-*
      Example: 
      aqt-trace-20171113-1028-ACCEL_TEST_CONNECTION-ghbHxQ

    Transfer the trace files in binary mode.