That makes sense. I guess you could use an MVS temporary dataset, and then "tee" it into an HFS file in your shell script....
But hey, submit a requirement for new system symbols ;-) More important, IMO, would be to have JCL PROC/SET symbols be saved in a ASASYMBM symbol table (not necessarily the primary system symbol table). Then, programs like Unix shells could use them. But we have discussed that to death I guess... Kirk Wolf Dovetailed Technologies FWIW - our free "catsearch" shell command can also be used to process catalogs from a shell script. It uses IGGCSI00 and F1 DSCBs under the covers, and supports things like tab-delimited output. http://dovetail.com/docs/coz/dsp-ref_catsearch.html On Tue, Apr 28, 2009 at 11:09 AM, John McKown <[email protected]> wrote: > On Tue, 28 Apr 2009 10:51:55 -0500, Kirk Wolf <[email protected]> wrote: > >>John, >> >>In this example, why not just use a temporary MVS dataset with >>DISP=PASS into the Unix step? >> >>Then use: >> >>fromdsn //DD:MYTEMP | process >> >>or: >> >>cp //DD:MYTEMP /dev/fd1 | process >> >>Kirk Wolf >>Dovetailed Technologies > > That's a possibility. I was wanting a "permanent" UNIX file. But I could do > it some other way, I guess. I guess I was wanting to easily relate the UNIX > file to the creating job for some reason. > > -- > John > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
