CREATE PROCEDURE KCDWHUAT.truncate_table(IN sch_name VARCHAR(130),IN tab_name VARCHAR(130)) 
  LANGUAGE SQL
  BEGIN

    DECLARE stmt VARCHAR(1000);
    DECLARE param VARCHAR(1000);
    DECLARE full_name VARCHAR(1000);
    DECLARE a VARCHAR(130);

    IF sch_name IS NULL 
      THEN
        SET full_name = tab_name;

        SELECT tabname INTO a FROM SYSCAT.TABLES WHERE tabname = UCASE(tab_name);

    ELSE
      SET full_name = sch_name||'.'||tab_name;

      SELECT tabname INTO a FROM SYSCAT.TABLES WHERE tabname = UCASE(tab_name) AND tabschema = UCASE(sch_name);

    END IF;

    IF UCASE(a) = UCASE(tab_name) 
      THEN
   
        SET param = 'IMPORT FROM NUL OF DEL REPLACE INTO '||full_name;
  
        SET stmt = 'CALL SYSPROC.ADMIN_CMD (?)';
 
        PREPARE s1 FROM stmt;
        EXECUTE s1 USING param;

    ELSE

   END IF;

  END

SQL0444N Routine "<routine-name>" (specific name
          "<specific-name>") is implemented with code in library
          or path "<library-or-path>", function
          "<function-code-id>" which cannot be accessed.  Reason
          code: "<code>".

Explanation:

The DBMS is trying to access the body of the code that implements
routine "<routine-name>" (specific name "<specific-name>"),
and cannot access it for the reason given by reason code
"<code>" (the codes are listed below).  The file implementing the
routine is identified by "<library-or-path>", and the function by
"<function-code-id>".

 (Note that these last two tokens may be truncated, due to
limitations in the total token length which can be provided.  If
this happens, then the definition of the routine in the catalogs
may need to be accessed in order to determine the full library or
path and function code id that were defined for the routine.)