Sorry am I late into this thread and this may have already been offered.
Would the use of the SET Statement in JCL also be a solution? // SET P1='abc/def/ghi -sh' // SET P2='continue away' //STEP1 EXEC PGM=IEFBR14,PARM=(PARM1,'&P1&P1') I would think that so long as the concatenated &P1&P2 etc... does not exceed 100 characters, that this also might work. I use this technique with BPXBATCH because I like simple solutions. It also makes it easier when I have redundancy in the parms for multiple executions. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Chris Mason > Sent: Tuesday, August 05, 2008 8:37 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: PARM problem - HELP > > Bob Rutledge provided the answer - even if it obliged those interested > to > locate the manual reference. > > But it's very short so here goes: > > <quote> > > 3.4.1.2 Continuing Parameter Fields Enclosed in Apostrophes > > To continue a parameter that is enclosed in apostrophes: > > Extend the parameter to column 71. Do not code an apostrophe in column > 71 > of a JCL statement that is continued. > > The system interprets the apostrophe in column 71 as the final > character in > the statement and ignores the continuation. > > Code // in columns 1 and 2 of the following statement. > > Continue the parameter in column 16 of the following statement even if > this > splits the parameter. Trailing blanks or commas within the apostrophes > do not > indicate a continued statement; the system treats them as part of the > parameter. > > The following example shows the specification of a long file name in > the PARM > field: > > //STEP1 EXEC > PGM=IEFBR14,PARM=(PARM1,'/DIR1/DIR2 > // > /DIR3/DIR4/DIR5/DIR6/DIR7/DIR8/DIR9/DIR10/DIR11/DIR12/DI > // R13/FILENM') > > </quote> > > The example is a bit artificial so here's an example I found just about > a quarter > of an hour before spotting this thread[1] in a redbook and then > wondered > whether I should post it as a heads-up having had to deal with > something like > the same problem a little while ago where I used one of the alternative > techniques.[2] > > <quote> > > //NAMED9B PROC PARMS='-d 0' > //NAMED9B EXEC PGM=BPXBATCH,REGION=0K,TIME=NOLIMIT, > // PARM=('PGM /usr/lpp/tcpip/sbin/named -V v9 -c > /etc/dnsdatb&SYSCLONE.X > // /named9b.conf &PARMS') > > </quote> > > This example indicates that the column 71/column 16 technique can > handle > use of lower case which was the particular problem I had a while ago. > > What is fascinating about this technique - and shows that it is not a > "trick" > which is how I would normally describe it - is that it looks very much > as if it > dates from JCL as I first used it (see [3]). Then, apart from the "//" > in columns > 1 and 2, assembler rules were followed meaning that text had to be > extended > to column 71 and had to be continued in column 16. I seem to remember > that > you needed to put a "continuation punch" in column 72 but that > requirement > seems to have been dropped - in terms of column 72 being ignored I > suppose. > > It had not occurred to me until I saw that example in the redbook today > that > that old syntax could still apply. However there is that old IBM rule - > nearly > always valid - that what once worked will continue to work - "e'en to > the > edge of doom". > > > As a consequence, I don't think you will be able to specify this type > and > length of PARM field for this program via JCL. > > Well, of course, you can. Nevertheless there is still the 100 character > length > limit for the PARM field which Steve has confirmed still exists. > > Chris Mason > > On Mon, 4 Aug 2008 19:09:11 -0400, Bob Rutledge > <[EMAIL PROTECTED]> wrote: > > >http://publibz.boulder.ibm.com/cgi- > bin/bookmgr_OS390/BOOKS/IEA2B670/3.4.1.2? > SHELF=EZ2ZO10K&DT=20070427231644&CASE= > > > >Bob > > > >John Norgauer wrote: > >> Here's my error: > >> > >> 10 //PS082 EXEC PGM=BPXBATCH, > >> //****************************************************** > ************** > >> // PARM='SH echo sftp -b /u/bpxbatch/mccheckftp > >> // fis-depot-test.ucdavis.edu |su -s bpxbtch' > >> 11 //SYSPRINT DD SYSOUT=* > >> 12 //STDOUT DD SYSOUT=* > >> 13 //STDERR DD SYSOUT=* > >> MT NO. MESSAGE > >> > >> 10 IEF642I EXCESSIVE PARAMETER LENGTH IN THE PARM FIELD > >> > >> Thanks. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
