Paul, I don't know how to solve your IEB319I issue, but out of curiosity I tried submitting your symbol substitution test from a PDS on our z/OS 2.1 system, and nothing ever gets substituted. Whatever your ftp submission issues, I don't see the new symbol substitution working at all here.
Is there some system PARMLIB option needed to enable this feature that my sysprogs may not have set? I used the syntax SYMBOLS=(type-of-conversion,log-DDNAME) to see what was happening with the actual substitution process, and nothing ever happened. I made up more entries in SYSUT1 than you had to see any differences, but there were none, whether I used $X (I think that is not correct) or &X (which the V2.1 JCL reference uses in its example of SYMBOLS usage). Here is my JCL (minus the JOB and OUTPUT cards, add your own at the top): //* DOC: EXPERIMENT WITH INSTREAM SYMBOL SUBSTITUTION. //* // SET X='THIS IS A LONG SYMBOL VALUE.' //* //*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....| //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 SYMBOL TO SEE &X. &X ALONE //* //*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....| //* The LOGSYMS output was exactly the same for JCLONLY, EXECSYS and CNVTSYS as follows: SYSUT1 : RECORD 1 BEFORE SUBSTITUTION SYSUT1 : LOTS OF DATA TO FILL UP A LINE, FOLLOWED BY A LONG SYMBOL TO SEE $X. SYSUT1 : RECORD 1 AFTER SUBSTITUTION SYSUT1 : LOTS OF DATA TO FILL UP A LINE, FOLLOWED BY A LONG SYMBOL TO SEE $X. SYSUT1 : RECORD 2 BEFORE SUBSTITUTION SYSUT1 : $X ALONE SYSUT1 : RECORD 2 AFTER SUBSTITUTION SYSUT1 : $X ALONE SYSUT1 : RECORD 3 BEFORE SUBSTITUTION SYSUT1 : LOTS OF DATA TO FILL UP A LINE, FOLLOWED BY A LONG SYMBOL TO SEE &X. SYSUT1 : RECORD 3 AFTER SUBSTITUTION SYSUT1 : LOTS OF DATA TO FILL UP A LINE, FOLLOWED BY A LONG SYMBOL TO SEE &X. SYSUT1 : RECORD 4 BEFORE SUBSTITUTION SYSUT1 : &X ALONE SYSUT1 : RECORD 4 AFTER SUBSTITUTION SYSUT1 : &X ALONE Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Friday, June 20, 2014 6:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IEB319I INVALID SYSPRINT/SYSIN BLOCKSIZE My first experiment with symbol substitution in SYSIN: // //JCLSYM JOB 505303JOB,'Paul Gilmartin', // MSGLEVEL=(1,1),REGION=16385K //* //* Doc: experiment with instream symbol substitution. //* //USERC OUTPUT JESDS=ALL,DEFAULT=YES, // CLASS=R,PAGEDEF=V0648Z,CHARS=GT12 //* // SET X='This is a long symbol value.' //* //*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....| //STEP EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=(,) //SYSIN DD * //SYSUT2 DD SYSOUT=(,) //SYSUT1 DD *,SYMBOLS=CNVTSYS Lots of data to fill up a line, followed by a long symbol to see $X. //* //*.+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....| // :w ! JESRECFM=V JESLRECL=222 submit $ZOS21_HOST Submitted via FTP, fails with RC=12 and SYSPRINT containing: DATA SET UTILITY - GENERATE IEB319I INVALID SYSPRINT/SYSIN BLOCKSIZE What's really wrong here, and what must I do to fix it? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 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
