Is there a restriction that requires STDENVX to point to a data set rather than inline (that is DD *) or is there a defect that causes the S013 we are now encountering?
We moved STDENVX contents inline in the web viewer started task
//STDENVX DD *
....
which worked, but we recently encountered
08.33.06 STC21015 $HASP708 DDNAME STDENVX OPEN FAILED
335 RC=03 DATA SET ALREADY OPENED
335 DSNAME=HLQ.DNAME.STC21015.D0000103.?
08.33.06 STC21015 $HASP708 DDNAME STDENVX OPEN FAILED
08.33.06 STC21015 IEC141I 013-C0,IGG0199G,DDNAME,DDNAME,STDENVX 337
336 RC=03 DATA SET ALREADY OPENED
337 ERROR DESCRIPTION: IEC141I
337 An open failure occurred for a subsystem data set.Possible failures
336 DSNAME=HLQ.DNAME.STC21015.D0000103.?
337 follow:
337 * A SYSIN or SYSOUT data set opened by JES.
08.33.06 STC21015 IEC141I 013-C0,IGG0199G,DDNAME,DDNAME,STDENVX 338
337 * A SYSIN or SYSOUT data set opened under the master subystem.
338 ERROR DESCRIPTION: IEC141I
337 * A subsystem data set(such as an HFS data set) that uses the same
338 An open failure occurred for a subsystem data set.Possible failures
337 interface as JES.
338 follow:
337 * For JES2, a SYSOUT data set incurred a subsystem JCL failure(SJF),
338 * A SYSIN or SYSOUT data set opened by JES.
337 and JES2 might issue a $HASP708 message to further describe the error.
338 * A SYSIN or SYSOUT data set opened under the master subystem.
338 * A subsystem data set(such as an HFS data set) that uses the same
337 For JES3, a reserved DD name, such as JOURNAL, might have been
Release : 14.0
Without the CA-SPOOL product the STDENVX DD was not required. A user opening a second tab to the same report triggered the abend on STDENVX.