The error (in part) is: ERROR 25-04-2019 16:23:20 [NSProcessJob] -- While job executing org.springframework.dao.DataIntegrityViolationException: could not prepare statement ; SQL [update SLA _CHANGEACTIONS set THREAD_ID=? where ID in (
When the “IF (&TCMD NE ‘+’)” statement is present in the panel code, all statements are aligned within the ‘IF’ statement so they only executed when the '+' is not used as first character on the command line.
CMNDB2DD does not apply the template to a DROP PROCEDURE or GRANT EXECUTE statement that is included in the member with the CREATE PROCEDURE statement . For example, if a customer creates their SPD (stored procedure definition) to contain the following statements, templating is only applied to the CREATE PROCEDURE statement. DROP PROCEDURE JUNK.STPROC99 RESTRICT;
Run a compare that executes SERCMPAR with more than 1500 FORIN statements and the job finishes with RC=16 and the following message: SER80I - TIME OF DAY AT END OF JOB: 17:59:12 - CONDITION CODE ON EXIT: 16 Run SERCMPAR with 1200 FORIN statements the job completes with a RC=00
Inclusion of an incorrectly formatted comment in a bind statement (format: /*ONLY_IN_DEV*/) caused the entire member to be omitted from the generated bind cards subsequently executed .
Program CMNDB2DD, executed during promote and install, is not templating the WLM ENVIRONMENT under the following conditions. WLM Env template is defined as DB90EN01 in DB2 Admin (producing CMNDB2DD sysin as: TGTWLMTEMPLATE=DB90EN01) The stored procedure definition in the SPQ source code is...
It selects HPSZCNTL module which then in turn calls the HPSTRANS module. When the customer does this the REXX abends on the SELECT CMD(HPSZCNTL HPSTRANS) statement with an S047-04 abend. This is false as they have APF authorised the SSM libraries.
Full error message is "IEC130I STG DD STATEMENT MISSING". This results in an empty &&LCT dataset being generated. Since the &&LCT dataset is empty, the link step executes and creates a member (TEMPNAM*) in the SYSLMOD dataset.
