Hi Jeff, Couple of ideas:
-1- Try WRITESEQ instead of WRITESEQF so the system will buffer your output in memory and write it to disk in more efficient chunks. According to "HELP WRITESEQF", your command "forces UniData to immediately write the data to the disk" so you're taking an I/O hit. -2- Would this be easier? _HOLD_ is a DIR-type file, so you can just PRINT each data line you want. The data is then delimited by linefeeds (ASCII 10) at the Unix level. Unidata converts the linefeeds to attribute marks whenever you work with a DIR-type record from a Unidata command. There's an option in the SETPTR command to choose the output file name you want, but don't recall the exact syntax. Hope this helps, Tom >>> [EMAIL PROTECTED] 10/20/06 11:04 AM >>> I'm going to ask yet another dumb question - Unidata 6.1.4 on Solaris (soon to be 7.1.x). I'm selecting a bunch of records and then outputting data from them into an ascii file in _HOLD_. If I open a sequential file, write the data line-by-line (WRITESEQF) and close the file, it takes about 5 minutes. If I save the data in a @FM delimited record and then write the record out at the end, it takes about 3 seconds. <snip> ----------------------------------------- This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the LabCorp Privacy Officer at [EMAIL PROTECTED] or call (877) 23-HIPAA / (877) 234-4722. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
