Try //ddname DD *,RECFM=VB,LRECL=259,BLKSIZE=0

On Mon, Jun 23, 2014 at 1:14 PM, Farley, Peter x23353
<[email protected]> wrote:
> I can confirm Gil's experiment as far as ISPF SUBMIT will allow me.  Even if 
> the submit is done from a RECFM=VB,LRECL=259 PDS, IEBGENER gets the "WRONG 
> LEN RECRD" error for SYSUT1 when the symbol-expanded input exceeds 80 
> characters.
>
> Similarly, if the symbol makes PARM exceed 100 characters you will get the 
> documented JCL error for that condition.  This is WAD and forever before, so 
> no difference there.  I intend to try PARMDD et. al. next.
>
> Here is my ISPF job in a PDS member (supply your own JOB and OUTPUT 
> statements).  The first line in the NOTUSED DD will generate the I/O error if 
> it is moved to SYSUT1:
>
> //* DOC: EXPERIMENT WITH INSTREAM SYMBOL SUBSTITUTION.
> //*
> //  EXPORT SYMLIST=*
> //  SET X='THIS IS A LONG SYMBOL VALUE.'
> //*
> //*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....|
> //SYMPARM  EXEC  PGM=IEFBR14,
> // PARM='LONG PARM VALUE TO FILL UP TO 100 CHARACTERS WITH SYMBOL VALUE*
> //             &X'
> //*
> //SYMTEST  EXEC  PGM=IEBGENER
> //SYSPRINT  DD  SYSOUT=*
> //SYSIN     DD  DUMMY
> //SYSUT2    DD  SYSOUT=*
> //LOGSYMS   DD  SYSOUT=*
> //SYSUT1    DD  *,SYMBOLS=(JCLONLY,LOGSYMS)
> LOTS OF DATA TO FILL UP A LINE, FOLLOWED BY A LONG SYMBOL TO SEE $X.
> $X ALONE
> LOTS OF DATA TO FILL UP A LINE, FOLLOWED BY A LONG: &X
> &X ALONE
> //NOTUSED   DD  *
> LOTS OF DATA TO FILL UP A LINE, FOLLOWED BY A LONG SYMBOL TO SEE &X.
> &X ALONE
> //*
> //*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....|
> //*
>
> BTW, the V2.1 ISPF editor highlighting for type JCL does not recognize EXPORT 
> as a valid JCL verb.  In my ISPF edit session, the word "EXPORT" is colored 
> green for a user-supplied word and not red for a JCL verb.  The entire EXPORT 
> parameter "SYMLIST=*" is pale blue indicating a JCL comment, rather than 
> green as I would expect (like all the parameters of a DD for instance).  No 
> doubt related to the failure to include EXPORT as a JCL verb.
>
> If some kind sysprog on the list would officially report that one to IBM as a 
> bug (I cannot, being only a humble application programmer), I think we would 
> all appreciate it.
>
> Regards,
>
> Peter
>
>
> 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 [email protected] with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to