IDB2 Common Services - GSSIDUMP is not freeing output datasets in all cases

Document ID : KB000122709
Last Modified Date : 21/12/2018
Show Technical Document Details
Issue:
After running GSSIDUMP job, the GSS task still holds an allocation to some of the output files, subsequent runs of GSSIDUMP does not work unless new dataset names are used. 
Resolution:
 The problem is the result of a user error in the GSSIDUMP job. The job was mistakenly set up to dump 3 different ILOGs to the same output data set. Once corrected, this problem should not occur. However, there does appear to be some kind of problem with the GSS code following this error. When the I/O error occurs, the IMOD attempts to CLOSE the output file, but control is never returned to the IMOD.