$ cp output "//'existing.output.file.with.correct.dcb'" cp: FSUMF133 source "output" is not a supported type of file for this operation
So apparently cp can't handle a fifo as the source file. Thanks for thinking OOB on this. That's not "cheating", that's looking for solutions that work. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Tuesday, January 08, 2013 12:55 PM To: [email protected] Subject: Re: SuperC utility loses its place when comparing text files with many differences How about cheating? I mean, _really_ cheating? I know that I like to. You can try the following from a z/OS UNIX shell. I don't use BPXBATCH, but I think you can put in multiple lines via STDPARM. mkdir ~/diff #create a new directory, just for fun cd ~/diff #go into it mkfifo file1 #make a named pipe for input #1 mkfifo file2 #and another for input #2 mkfifo output #and another for output cp "//'zos.file.one'" file1 & cp "//'zos.file.two'" file2 & diff file1 file2 >output & cp output "//'existing.output.file.with.correct.dcb'" #copy output to z/OS dsn cd ~ #back to ${HOME} rm -rf diff #get rid of junk files subdirectory On Tue, Jan 8, 2013 at 11:40 AM, Farley, Peter x23353 <[email protected]> wrote: > Unix diff (well, GNUWIN32 diff on my laptop anyway) finds all the differences > correctly. I'm also trying to use z/OS Unix diff from JCL with BPXBATSL > without much success. I don't have a lot of space in my userid HFS > directory, so copying large MVS files into there is problematic. And no CoZ > tools available nor possible for me to install (not authorized). > > I may try to see if the local /tmp space is large enough to /bin/cp them into > and then diff those copies. > > Peter > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Tuesday, January 08, 2013 12:13 PM > To: [email protected] > Subject: Re: SuperC utility loses its place when comparing text files with > many differences > > On Tue, 8 Jan 2013 12:00:49 -0500, Thomas Conley wrote: >> >>I've seen this behavior myself, even on smaller files. It stops >>recognizing that lines are the same and just has huge blocks as inserts >>and deletes, even though the lines are the same. SUPERC support was >>unimpressed, I got the WAD. >> > I'm curious: How does this compare with the behavior of "diff", both > on z/OS and on other UNICES. I've not had the bad experience. > > How small is "smaller"? > > I know that SuperC and/or diff will find unintended matches on lines > that are identical by happenstance (such as "begin" and "end") and > be badly out of sync as a result. > -- -- Maranatha! <>< John McKown -- 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
