RE: FW: IFS symbolic link library mapping

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Uros

I have a tendency to see the hard way to do things. ;-)

This is an interesting, tough problem. There is also, as you probably know, 
the 'cmp' command in QShell, which also has some kind of limit.

As for 'split', if you know the record length of the IFS copy from 
CPYTOIMPF, maybe a multiple of that could be the split size. Seems that the 
CPYTOIMPF should be fixed, not delimited, for this to work. But the VAX 
file may be delimited?

Is there anything in PASE that has better limits?

Good luck

Vern

At 11:39 PM 4/11/2003 -0400, you wrote:
> Vern,
>
> Aware of all of these, thanks anyhow... My goal was to get a IFS
> symbolic link to work in order to use the file inside an app by just
> mapping a network drive to the link and pulling up the file. The
> applications that I am using (file comparison utilities) do not
> inherenetly know anything about these things, unless I write something
> using ODBC myself and then use a command line executable for file
> comparison. What I am trying to do is have two drives mapped: a AS400
> and a DEC VAX drive (we did this with Samba). Then, convert the files to
> the point they are comparable (all fields Signed and alpha) and
> reference by mapped drive location. We are currently having to use FTP
> to get them to a single location and that is very tedious in some cases
> (we are talking gigs). Even when we do get them to the AS400, the CMPPFM
> has a size limitation of 16 (or 32) Meg, so we have to either write
> programs or use the split command inside the qshell environment (which
> does not know about records, most likely, so it probably splits in the
> middle of the record at times) and then compare...
>
> Regards,
> Uros