RPN01 wrote:
When you get down to just 3270 access, the sed command is your friend. Do it once to the terminal, if the file isn't too big, and check your results, then use > to put the results into a new file, rename the old, rename the new, and then start the cycle over again...
Where possible, I like to cp file-to-change saved-file-to-change sed <saved-file-to-change >file-to-change \ # whatever edit commands Repeat seds until done. This approach preserves relevant permissions on the original (mv does not). If the seds are at all complicated, they can be stored in a file (--file=script-file) or the whole thing placed in a shell script that might make the first copy command conditional: [ -f saved-file-to-change ] || cp file-to-change saved-file-to-change which greatly simplifies debugging. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
