Steve Coalbran wrote:... FREEs failed for SYSOUT every time.
Am I thinking inside a box?!
Most likely, yes. You must specify the SYSOUT class for IEBCOPY on the XMIT command. XMIT allocates and frees the SYSOUT data set for IEBCOPY. XMIT does not use a definition you have allocated yourself.
In addition, you must locate a "dummy" SYSOUT class in your installation, either by analyzing the JES2 startup parameters as I did, or by using $D OUTCLASS(x) commands until you find a "dummy" SYSOUT class.
$HASP842 OUTCLASS(Z)
$HASP842 OUTCLASS(Z) OUTPUT=DUMMY,BLNKTRNC=YES,
$HASP842 OUTDISP=(HOLD,HOLD),TRKCELL=YES
$HASP842 OUTCLASS(Z) OUTPUT=DUMMY,BLNKTRNC=YES,
$HASP842 OUTDISP=(HOLD,HOLD),TRKCELL=YES
h xmit op(sysout)
SYSOUT You may request the TRANSMIT command to direct
utility program messages (e.g. IEBCOPY) to a
specific sysout class or to your terminal. If
you specify SYSOUT(*), you will receive all
utility program messages on your terminal.
SYSOUT You may request the TRANSMIT command to direct
utility program messages (e.g. IEBCOPY) to a
specific sysout class or to your terminal. If
you specify SYSOUT(*), you will receive all
utility program messages on your terminal.
*** Added later: my bad. You already did. You specify the SYSOUT class on the XMIT and RECEIVE commands
XMIT ... SYSOUT(X)
RECEIVE ... SYSOUT(X)
