Re: I/O error substituting symbols in sysin

[Paul Gilmartin]

On Tue, 13 Dec 2016 15:29:53 -0500, John Clifford wrote:

>I was always under the impression that any DD * implied lrecl=80 only.
>Adding a lrecl=222 should cause the i/o error. No 
>
I believe that restriction was removed about z/OS 1.5 JES2.  Just
TSO SUBMIT hasn't heard about it yet.  And earlier today I posted
a case that works only with the LRECL=222.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[John Clifford]

I was always under the impression that any DD * implied lrecl=80 only.
Adding a lrecl=222 should cause the i/o error. No 

John Clifford

On Mon, Dec 12, 2016 at 8:40 PM, Anthony Thompson <
anthony.thomp...@nt.gov.au> wrote:

> Pardon for getting the input wrong. New JCL:
> //
> //  EXPORT SYMLIST=*
> //  SET TEST='THIS IS THE VALUE OF THE SUBSTITUTED STRING.'
> //STEP1EXEC PGM=IEBGENER
> //SYSUT1   DD   DATA,SYMBOLS=JCLONLY,DCB=LRECL=222
>   This is a test of symbol use in instream data sets. Test here: 
> /*
> //SYSUT2   DD   SYSOUT=(,)
> //SYSPRINT DD   SYSOUT=(,)
> //SYSINDD   DUMMY
>
> I'm supposing you used the TSO SUBMIT command to submit the job. A foible
> of TSO SUBMIT is that it doesn't do input greater than 80 characters.
>
> So you've got an 80-byte SYSUT1 input but you're telling the system it's
> really 222 bytes. Bang. I/O error.
>
> I put the same JCL above into a dataset with LRECL 222 and submitted it to
> an internal reader via IEBGENER (ICEGENER). Job Finished with RC 0.
>
> Ant.
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Paul Gilmartin
> Sent: Tuesday, 13 December 2016 1:14 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: I/O error substituting symbols in sysin
>
> On 2016-12-12, at 00:56, Anthony Thompson wrote:
>
> > Ran this JCL :
> >
> > //
> > //  EXPORT SYMLIST=*
> > //  SET TEST='THIS IS THE VALUE OF THE SUBSTITUTED STRING.'
> > //STEP1EXEC  PGM=IEBGENER
> > //SYSUT1DD  DATA,SYMBOLS=JCLONLY
> > 
> > /*
> > //SYSUT2DD  SYSOUT=(,)
> > //SYSPRINT  DD  SYSOUT=(,)
> > //SYSIN DD  DUMMY
> >
> > Only removed the DCB on SYSUT1. Job worked.
> >
> Than's not "only".  You also changed the content of SYSUT1 in my example.
> Try it with the SYSUT1 I cited, with or without DCB:
>
> //SYSUT1DD  *,SYMBOLS=JCLONLY,DCB=LRECL=222
>This is a test of symbol use in instream data sets.   Test here: 
>
>
> On 2016-12-12, at 02:50, Anthony Thompson wrote:
>
> > Just so. But anyone can frig around with invalid DCB's and make any
> utility break.
>
> What do you claim was invalid about my DCB.  Cite Reference.
>
> -- gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Paul Gilmartin]

On Tue, 13 Dec 2016 01:40:07 +, Anthony Thompson wrote:
>
>So you've got an 80-byte SYSUT1 input but you're telling the system it's 
>really 222 bytes. Bang. I/O error.
>
>I put the same JCL above into a dataset with LRECL 222 and submitted it to an 
>internal reader via IEBGENER (ICEGENER). Job Finished with RC 0.  
>
And now I recall how I came to have a proclivity for specifying DCB parameters
The following job submitted via IEBGENER to INTRDR with RECFM=VB,LRECL=250:

user@OS/390.25.00: cat jclsym2  
   
//
//JCLSYM2   JOB  505303JOB,'Paul Gilmartin',
// MSGLEVEL=(1,1),REGION=16385K
//*
//* Doc: experiment with instream symbol substitution.
//*
//USERCOUTPUT JESDS=ALL,DEFAULT=YES,
//  CLASS=R,PAGEDEF=V0648Z,CHARS=GT12
//*
//  EXPORT SYMLIST=*
//  SET TEST='This is the value of the substituted string.'
//STEP1EXEC  PGM=IEBGENER
//SYSUT1DD  *,SYMBOLS=(JCLONLY,LOGDD)  ,DCB=(LRECL=222),BLKSIZE=444
This is a test of symbol use in instream data sets.  Test here: 
+|+|+|+|+|+|+|+|1
//* This is a test of symbol use in instream data sets.  Test here: This is the 
value of the substituted string.
//SYSUT2DD  SYSOUT=(,)
//SYSPRINT  DD  SYSOUT=(,)
//SYSIN DD  DUMMY
//LOGDD DD  SYSOUT=(,)
//*.+|+|+|+|+|+|+|+|
//
 :w ! JESRECFM=V JESLRECL=250 submit $MVS_HOST
user@OS/390.25.00: 

... fails as is, but succeeds if I enable the DCB parameters.  But if I then
remove the second line in SYSUT1, it fails again.

The rules are complicated.  They need to be explained clearly.  They are not.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Paul Gilmartin]

On Tue, 13 Dec 2016 01:40:07 +, Anthony Thompson 
 wrote:

>Pardon for getting the input wrong. New JCL: 
>//
>//  EXPORT SYMLIST=*
>//  SET TEST='THIS IS THE VALUE OF THE SUBSTITUTED STRING.' 
>//STEP1EXEC PGM=IEBGENER
>//SYSUT1   DD   DATA,SYMBOLS=JCLONLY,DCB=LRECL=222  
>  This is a test of symbol use in instream data sets. Test here: 
>/*  
>//SYSUT2   DD   SYSOUT=(,)  
>//SYSPRINT DD   SYSOUT=(,)  
>//SYSINDD   DUMMY   
>
>I'm supposing you used the TSO SUBMIT command to submit the job. A foible of 
>TSO SUBMIT is that it doesn't do input greater than 80 characters. 
> 
Actually, I used FTP which allows up to 254.

>So you've got an 80-byte SYSUT1 input but you're telling the system it's 
>really 222 bytes. Bang. I/O error.
>
Is there any documented restriction I'm violating?  Since I see none, I'm 
pressing my SR for an APAR.

What was your RECFM.  Try it with RECFM=VB.

>I put the same JCL above into a dataset with LRECL 222 and submitted it to an 
>internal reader via IEBGENER (ICEGENER). Job Finished with RC 0.  
>
It seems that the only thing one can specify as LRECL is what it already is.  
Why is
the option explicitly supported?

Actually, by experiment, it's very complicated.  Which is why I have an RCF in
asking for a detailed explanation, and why IBM has been unable to supply the
information for 15 months.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Anthony Thompson]

Pardon for getting the input wrong. New JCL: 
//
//  EXPORT SYMLIST=*
//  SET TEST='THIS IS THE VALUE OF THE SUBSTITUTED STRING.' 
//STEP1EXEC PGM=IEBGENER
//SYSUT1   DD   DATA,SYMBOLS=JCLONLY,DCB=LRECL=222  
  This is a test of symbol use in instream data sets. Test here: 
/*  
//SYSUT2   DD   SYSOUT=(,)  
//SYSPRINT DD   SYSOUT=(,)  
//SYSINDD   DUMMY   

I'm supposing you used the TSO SUBMIT command to submit the job. A foible of 
TSO SUBMIT is that it doesn't do input greater than 80 characters. 

So you've got an 80-byte SYSUT1 input but you're telling the system it's really 
222 bytes. Bang. I/O error.

I put the same JCL above into a dataset with LRECL 222 and submitted it to an 
internal reader via IEBGENER (ICEGENER). Job Finished with RC 0.  

Ant.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Tuesday, 13 December 2016 1:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: I/O error substituting symbols in sysin

On 2016-12-12, at 00:56, Anthony Thompson wrote:

> Ran this JCL :
> 
> //
> //  EXPORT SYMLIST=*   
> //  SET TEST='THIS IS THE VALUE OF THE SUBSTITUTED STRING.'
> //STEP1EXEC  PGM=IEBGENER  
> //SYSUT1DD  DATA,SYMBOLS=JCLONLY   
> 
> /* 
> //SYSUT2DD  SYSOUT=(,) 
> //SYSPRINT  DD  SYSOUT=(,) 
> //SYSIN DD  DUMMY  
> 
> Only removed the DCB on SYSUT1. Job worked.
> 
Than's not "only".  You also changed the content of SYSUT1 in my example.  Try 
it with the SYSUT1 I cited, with or without DCB:

//SYSUT1DD  *,SYMBOLS=JCLONLY,DCB=LRECL=222
   This is a test of symbol use in instream data sets.   Test here: 


On 2016-12-12, at 02:50, Anthony Thompson wrote:

> Just so. But anyone can frig around with invalid DCB's and make any utility 
> break.

What do you claim was invalid about my DCB.  Cite Reference.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Bill Woodger]

Urban Dictionary (one of several definitions)

 frig

(Term used by engineers) To make a rough-and-ready, quick-and-dirty adjustment 
to something to make it work or to make it operate in a particular way. To 
adjust manually for a particular purpose. Can be used of a physical device but 
also of a computer program, etc.
"Since I'd figured out how it worked, I decided to frig it so it output the 
data exactly how *I* wanted it." 

I have to say it is over 20 years since I heard it in that context.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Paul Gilmartin]

On 2016-12-12, at 00:56, Anthony Thompson wrote:

> Ran this JCL :
> 
> //
> //  EXPORT SYMLIST=*   
> //  SET TEST='THIS IS THE VALUE OF THE SUBSTITUTED STRING.'
> //STEP1EXEC  PGM=IEBGENER  
> //SYSUT1DD  DATA,SYMBOLS=JCLONLY   
> 
> /* 
> //SYSUT2DD  SYSOUT=(,) 
> //SYSPRINT  DD  SYSOUT=(,) 
> //SYSIN DD  DUMMY  
> 
> Only removed the DCB on SYSUT1. Job worked.
> 
Than's not "only".  You also changed the content of SYSUT1 in
my example.  Try it with the SYSUT1 I cited, with or without DCB:

//SYSUT1DD  *,SYMBOLS=JCLONLY,DCB=LRECL=222
   This is a test of symbol use in instream data sets.   Test here: 


On 2016-12-12, at 02:50, Anthony Thompson wrote:

> Just so. But anyone can frig around with invalid DCB's and make any utility 
> break.

What do you claim was invalid about my DCB.  Cite Reference.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Charles Mills]

Um, the Oxford English (as in England) Dictionary lists the same meaning I know 
here across the pond.

https://en.oxforddictionaries.com/definition/frig 

Charles

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Bill Woodger
Sent: Monday, December 12, 2016 2:02 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: I/O error substituting symbols in sysin

More computing history. "Frig". No, it doesn't mean what those across the water 
may think. A particular UK-computing term, not sure of the origins, and it 
certainly "surprised" me when I cam across the use of the word as a 17-year-old 
trainee who happened to know the "other" meaning. "I'm going to run a little 
frig", "can you frig it?", "I put in a little frig last night, and now we need 
to fix it proper(ly)". 

Now, I'm off for a quick fag.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Bill Woodger]

More computing history. "Frig". No, it doesn't mean what those across the water 
may think. A particular UK-computing term, not sure of the origins, and it 
certainly "surprised" me when I cam across the use of the word as a 17-year-old 
trainee who happened to know the "other" meaning. "I'm going to run a little 
frig", "can you frig it?", "I put in a little frig last night, and now we need 
to fix it proper(ly)". 

Now, I'm off for a quick fag.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Anthony Thompson]

Just so. But anyone can frig around with invalid DCB's and make any utility 
break.

Ant.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Bill Woodger
Sent: Monday, 12 December 2016 7:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: I/O error substituting symbols in sysin

So that would be an ordinary 80-byte SYSIN, data within 80 bytes. Not what Paul 
is trying.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Bill Woodger]

So that would be an ordinary 80-byte SYSIN, data within 80 bytes. Not what Paul 
is trying.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Anthony Thompson]

Ran this JCL :

//
//  EXPORT SYMLIST=*   
//  SET TEST='THIS IS THE VALUE OF THE SUBSTITUTED STRING.'
//STEP1EXEC  PGM=IEBGENER  
//SYSUT1DD  DATA,SYMBOLS=JCLONLY   
  
/* 
//SYSUT2DD  SYSOUT=(,) 
//SYSPRINT  DD  SYSOUT=(,) 
//SYSIN DD  DUMMY  

Only removed the DCB on SYSUT1. Job worked.

Ant.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Saturday, 10 December 2016 5:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: I/O error substituting symbols in sysin

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.'
//STEP1EXEC  PGM=IEBGENER
//SYSUT1DD  DATA,SYMBOLS=JCLONLY,DCB=LRECL=222
This is a test of symbol use in instream data sets.  Test here: 
/*  This is a test of symbol use in instream data sets.  Test here: This is the
/*
//SYSUT2DD  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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Paul Gilmartin]

On 2016-12-09, at 09:56, Farley, Peter x23353 wrote:
> 
> For myself, I have no need to explore or use such edge cases.  All my symbol 
> substitutions stay within the "classic DD *" limit of 80 bytes after 
> substitution (IDCAMS input to delete/define VSAM files with special 
> characteristics not covered by the JCL LIKE parameter in my most common use 
> cases, sometimes SORT control cards too for parameterized record 
> selection/modification).
>  
Yet a programmer who discovers a problem in such an edge case and
fails to report it so it can be fixed is doing his peers a disservice.
I opened the SR as JES2.  I already have a related one on SDSF.

It's dismaying that such problems are not discovered in product test.
I'd expect a high priority of a test team would be to explore edge
cases that developers might have overlooked in unit test.

I have an RCF, now 15 months old requesting documentation:

Please provide an explanation of what determines the attributes
(RECFM, LRECL, BLKSIZE) merged into the DCB by OPEN.  ...

The answer so far:

Hi, Paul, thanks for your note. Our Development team has this
service item in their queue. I can send you a note when we have
some updates ready. This suggested update will take some time
for Development to complete and won't appear in the V2R2 GA
document.

(I wish they could send me a preview.  If they do, I'll test against
it and probably generate more SRs.)

> "Doctor! Doctor! It hurts when I do that! --- Well, don't do that!"
>  
Is that in the Reference Manual anywhere?  Part of the specification?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Paul Gilmartin]

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.'
//STEP1EXEC  PGM=IEBGENER
//SYSUT1DD  DATA,SYMBOLS=JCLONLY,DCB=LRECL=222
This is a test of symbol use in instream data sets.  Test here: 
/*  This is a test of symbol use in instream data sets.  Test here: This is the
/*
//SYSUT2DD  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

Re: I/O error substituting symbols in sysin

[Farley, Peter x23353]

Paul,

That's an old problem with substituting "long" symbols in "DD *" input that 
result in records that exceed the "classic DD *" length of 80 bytes.  You and I 
had an email conversation and actual testing in z/OS V2.1 about this issue 
quite a while back, and it was broken then.

I would think the component would be the JCL converter/interpreter. Which 
should either truncate or not depending on your preference.

For myself, I have no need to explore or use such edge cases.  All my symbol 
substitutions stay within the "classic DD *" limit of 80 bytes after 
substitution (IDCAMS input to delete/define VSAM files with special 
characteristics not covered by the JCL LIKE parameter in my most common use 
cases, sometimes SORT control cards too for parameterized record 
selection/modification).

"Doctor! Doctor! It hurts when I do that! --- Well, don't do that!"

Peter

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Friday, December 09, 2016 11:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: I/O error substituting symbols in sysin

A job step containing:

//  EXPORT SYMLIST=*
//  SET TEST='This is the value of the substituted string.'
//STEP1EXEC  PGM=IEBGENER
//SYSUT1DD  *,SYMBOLS=JCLONLY,DCB=LRECL=222
This is a test of symbol use in instream data sets.  Test here: 
//* This is a test of symbol use in instream data sets.  Test here: This is the 
value of the substituted string.

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

Against which component should I submit the SR?  I doubt that it's Utilities;
perhaps JES2 or DfSMS?
--


This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: I/O error substituting symbols in sysin

[Lizette Koehler]

What does your SYSUT2 DD statement look like?

Typically SYSUT1 is copied to SYSUT2 JCL statements.

I only see SYSUT1

And if you need to raise an SR it would be to DFSMS Utilities.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Paul Gilmartin
> Sent: Friday, December 09, 2016 9:40 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: I/O error substituting symbols in sysin
> 
> A job step containing:
> 
> //  EXPORT SYMLIST=*
> //  SET TEST='This is the value of the substituted string.'
> //STEP1  EXEC  PGM=IEBGENER
> //SYSUT1DD*,SYMBOLS=JCLONLY,DCB=LRECL=222
> This is a test of symbol use in instream data sets.Test here: 
> 
> //* This is a test of symbol use in instream data sets.Test here: This
> is the value of the substituted string.
> 
> 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
> 
> Against which component should I submit the SR?  I doubt that it's Utilities;
> perhaps JES2 or DfSMS?
> 
> -- gil
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN