Article - CS348594
Implementer trigger promotion abends with SQL9010 in job log and SQL7008 (reason code 8) in trigger compile listing
Modified: 08-Jul-2021
Applies To
- Implementer 10.1 to 12.4
Description
- Implementer trigger promotion abends when trying to create trigger in a library that is not in the same Auxiliary Storage Pool (ASP) as the file with which it is associated
- In job log: SQL9010 RUNSQLSTM or RUNSQL command failed
- In trigger compile listing: SQL7008 <file name> in <file's library name> not valid for operation
- Second level text shows "reason code is 8"
- Cause: 8 -- Based-on table resides in a different ASP than ASP of object being created.
- Recovery: 8 -- Use tables in the same ASP.
- If not getting second level text in compile listing
- RUNSQLSTM command needs the SECLVLTXT(*YES) parameter.
- Recommended to change the RUNSQLSTM command default via the CHGCMDDFT command
- CHGCMDDFT CMD(QSYS/RUNSQLSTM) NEWDFT('SECLVLTXT(*YES)')
- At this point, the failed request can be resubmitted to generate the failed trigger compile listing with second level text
- For future requests, SECLVLTXT(*YES) can be added to every object code definition for which the Creation command is RUNSQLSTM
- RUNSQLSTM command needs the SECLVLTXT(*YES) parameter.
- Second level text shows "reason code is 8"
This is a printer-friendly version of Article 348594 and may be out of date. For the latest version click CS348594