Thanks to everyone who replied on and off list. We've been looking at all the suggestions. Now it looks like we may have a resolution.
One of our server guys has been working with McKesson on the problem. Yesterday they found a 4 gig log file on the server that bothered them. They renamed the log file and made a new one. We stayed in communication all night with the server and everyone's reports were ready this morning. I'll still be keeping my fingers crossed for a few days. Quite a coincidence that we start having this problem the night we converted to 1.7 with IBM TCPIP, huh? Thanks again to a great bunch of folks... Robert Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
