RC=17 and RC=99 trying to generate Gen 8.6 RI Triggers

Products

• Gen - Host Encyclopedia
• Gen

Issue/Introduction

Unable to generate Gen 8.6 RI Triggers. 2 job logs SYS1 and SYS2 show:

DSN NOT ACTIVE, PROCESS TERMINATED
***** GENERATION ERROR, RC = 17 *****

CLIST TIUDSN, PGM: TICEBG, ABEND S0C4
***** GENERATION ERROR, RC = 99 *****

They also show corresponding COND CODE values 0017 and 0099.

Resolution

SYS1:
The return code of 17 is reported when the DB2 subsystem is not available. This can be because the DB2 subsystem is not actually started or it can be that the DB2 subsystem specified in the TIUDB2S variable in the TIUHE PARMLIB member is not the correct one.

SYS2:
The return code of 99 is usually reported when a non-numeric return code is received.
The reference to TICEBG indicates that the EBG RI Trigger generator got an S0C4 abend. From the CEEDUMP output in the log, the TICEBGX generator has a date of 2010/04/29 which is not Gen 8.6 but a much earlier version of Gen.

It could be that the user is not executing the code that he intended. This might be due to the logon clist not including the correct Gen 8.6 datasets or maybe the PARMLIB doesn't contain the correct values. The advice is to:

1. Execute the 'TSO ISRDDN' command after logging into the Host Encyclopedia. This command should show what datasets were allocated to the TSO session. If the expected Gen 8.6 datasets are not seen in the TSO ISRDDN command output, then check the logon clist. 

2. If this does not help to resolve, please run the batch jobs again after setting the TIUDEBUG parameter in the JCL to 'CDPS', instead of 'X', in order to get more information. The TIUDEBUG output should at least show what values were found in the PARMLIB.

In this particular scenario the user made manual changes to the job to resolve the problem.
The main differences were that they added the Gen 8.6 CEHBPLD0 and CEHBPLD1 datasets and a DB2 dataset to the STEPLIB concatenation. They also commented out some datasets in the SYSPROC, ISPPLIB, ISPMLIB, ISPSLIB, and ISPTLIB concatenations. It is suspected that the STEPLIB changes allowed the RI Triggers to generate successfully.
In the original failing SYS1 and SYS2 jobs, it was not clear where the Gen and DB2 load modules were being found (the user may have been executing an old version of the Gen load modules).