Ronald K. Ellis III wrote on 09/14/2004 06:25:21 PM: > <snip> The goal of the script > I'm writing is to report back about UniData file. I'm going to use FILE.STAT > to gather most the info I think. What is the modulo of the file? What is the > separation? What is the blocksize? Where does the file live? Also It'll do > some simple math to try and figure out what we should resize the file to.
This isn't really asking the question you're asking, but I believe it may be a better approach. Since you're starting out at the operating system level, you can get the desired information by running the guide utility. It will even provide you with suggestions for resizing the file. That should be much simpler - and quicker - than launching a UniData session and parsing its output. You also save yourself the effort of determining the file sizing yourself. In newer releases of UniData, guide can go through files very quickly. Now, if you have other reasons for launching UniData processes and capturing their output from within a script, that can be done as well. But if the sole reason is to get file information, try guide first. Tim Snyder IBM Information Management Consulting I/T Specialist , U2 Professional Services ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
