Use AOPBATCH or DTLSPAWN and you can use a spool file with STDIN and normal shell continuation syntax:
//STDIN DD * foo arg1 \ arg2 \ ag3 With DTLSPAWN, you can also set shell variables via JCL parms: // EXEC DTLSPAWN,ARG='a=my.dsn b=your.dsn' //STDIN DD * echo variable a is &a and b is &b foo &a &b // With either AOPBATCH or DTLSPAWN, you can also put a shell script in an HFS file rather than a STDIN spool file. Kirk Wolf Dovetailed Technologies http://dovetail.com On Tue, Mar 10, 2009 at 7:28 AM, Bonno, Tuco <t...@cio.sc.gov> wrote: > THANK YOU. this example [infra] of bpxbatch works very well in terms of > solving my original problem/issue. > but it's at the expense of making it much more complicated (imo) to > process long complicated commands that go across 3 or 4 lines of input. w/ > IKJEFT01, a continuation character at the end of each line ( + ) is > sufficient; w/ BPXBATCH, you've got to do the > " // SET PARM01= ........ " "// SET PARM02= .... " etc etc etc > routine, which, to me, is much more onerous than having the output in two > entities in sdsf. > > The Lord giveth, and Lord taketh away . > > Thanks to all who responded . > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On > Behalf Of Smith, Sean M > Sent: Monday, 09 March, 2009 05:37 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: one IKJEFT01 job, 2 outputs in sdsf - why? > > I would like to second the question...I understand that the second > execution is from the spawned task but is there a way to get the output to > come back into the originating execution? > > All that being said, in your example you could use this instead: > > //STEPNAME EXEC PGM=BPXBATCH,PARM='SH ls -la /etc/ | cat' > //STDOUT DD SYSOUT=* > //STDERR DD SYSOUT=* > > Sean Smith > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On > Behalf Of Bonno, Tuco > Sent: Monday, March 09, 2009 12:04 PM > To: IBM-MAIN@bama.ua.edu > Subject: one IKJEFT01 job, 2 outputs in sdsf - why? > > cross-posting to ibm-main, mvs-oe > > running z/os 1.9 > > > > when I run this job: > > //tucopgp1 job … msgclass=x ….. > > //abc exec pgm=IKJEFT01 > > //sysexec dd disp=shr, dsn=sys1.sbpxexec > > //systsprt dd sysout=* > > //systsin dd * > > OSHELL ls –la /etc/ | cat > > > > the output shows up as TWO entries in sdsf each w/ the same jobname and > jobid: > > (e.g.,) > > tucopgp1 job10694 ….. <tot-rec = 85 > > > tucopgp1 job10694 ….. <tot-rec =90 > > > > > the 90-line item is the conventional jes2 stuff (log, msg-s, jcl, systsprt) > ; > > the 85-line item contains the output proper of the omvs “cat” command. > > > > what should I add to my jcl to have all the ouput conflated into just one > item in sdsf ? > > thank you. > > > > > > /s/ tuco bonno > > graduate, College of Conflict Management > > University of Southeast Asia > > "I partied on the Ho Chi Minh Trail -- tiến lên ! " > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html