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.
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.