> -----Original Message-----
> From: Robyn Noble [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 30, 2001 11:06 AM
> To: [EMAIL PROTECTED]
> Subject: Gentran questions
>
>
> We currently are using Gentran Server for Windows NT running on
> Windows 98 for EDI and we have an AS400 that everything else is
> on.
>
> 2) Right now Gentran is running extremely slow, even just to
> look up trading partner information and translating even one
> document is painfully slow.
1. Configure GENTRAN to archive old documents and purge them
from your Server about once a week. How often you should
do this depends on your transaction volume. If it is around
5,000 per week, a weekly archive will do. If it is much
higher, it may be necessary to archive more often.
2. Configure the Mailbox Server in GENTRAN to purge old messages.
I set this to purge anything older than 24 hours every day.
3. Run GICheck regularly. GENTRAN keeps transaction content data
as files in its STORE subdirectory - thousands of them,
interchanges, documents, translation reports, mailbox messages.
These files are tracked with records in the GENTRAN database.
Some are purged automatically, or by operator action or by
script (see 1). But the purges don't always quite work. GENTRAN
accumulates 'orphan' files and records - tens of thousands of
them, if one lets things go long enough. 20,000 or 30,000
'orphans' will run the server into the ground.
GICheck scans the database and STORE directory, and locates all
files with no record or records pointing to no file. Then (if
commanded) it deletes the 'orphans'.
4. Clear out the TEMP directory and any .TMP files in the WINNT
directory. Or the equivalent for Win98; GENTRAN creates lots
of .TMP files and doesn't get rid of them.
5. Check the TransIn directory. A copy of every inbound Interchange
gets stored here and is never deleted by GENTRAN, even when
documents or messages are purged. 10,000 or 20,000 files in a
directory tends to slow things down.
6. Check the drive on which GENTRAN and its data reside. If 'stuff'
has been allowed to accumulate (especially if the drive is
formatted for FAT and not NTFS or Win98 equivalent), the drive
may be nearly filled. This would lead to extreme fragmentation
of files, and later on a crash.
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
