On Fri, 9 Dec 2016 09:47:17 -0700, Lizette Koehler wrote:
>What does your SYSUT2 DD statement look like?
>Typically SYSUT1 is copied to SYSUT2 JCL statements.
>I only see SYSUT1
>
The problem occured on SYSUT1 and the message mentioned SYSUT1.
I don't believe it ever wrote to SYSUT2, so I abbreviated. More fully:
// EXPORT SYMLIST=*
// SET TEST='This is the value of the substituted string.'
//STEP1 EXEC PGM=IEBGENER
//SYSUT1 DD DATA,SYMBOLS=JCLONLY,DCB=LRECL=222
This is a test of symbol use in instream data sets. Test here: &TEST
/* This is a test of symbol use in instream data sets. Test here: This is the
/*
//SYSUT2 DD SYSOUT=(,)
//SYSPRINT DD SYSOUT=(,)
//SYSIN DD DUMMY
If you believe a different specification of SYSUT2 changes the behavior,
I'd welcome the information.
>And if you need to raise an SR it would be to DFSMS Utilities.
>
Thanks, but does this seem to be a Utilities problem?
>> -----Original Message-----
>> From: Paul Gilmartin
>> Sent: Friday, December 09, 2016 9:40 AM
>> ...
>> Fails with SYSPRINT containing:
>>
>> 1DATA SET UTILITY - GENERATE
>> PAGE 0001
>> -IEB352I WARNING: ONE OR MORE OF THE OUTPUT DCB PARMS COPIED FROM INPUT
>> IEB351I I/O ERROR ,JCLSYM ,STEP1 ,JES ,D,SYSUT1 ,READ ,WRONG LEN
>> RECRD,**************,BSAM
Thanks again,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
