We currently have an intermittent problem of handling our "BSC Line Failed" problem. Sometimes we get a Drop Error and sometimes we get a Communications Session that is stuck in STRD status. We are on the AS400 and use of course the Inovis Translator TLi ver 5.4.1.
The Drop Error Communication status does not present a problem because it does not hold up the job queue. But when the BSC line fails and we get a STRD that goes nowhere, of course if holds up all of the jobs in the queue. Does anyone know why the STRD status occurs and the Communication does not go to the Drop Status? And if anyone has found a way to force the Communication Status to go to Dropped I'd like to know how you handled it. Currently our ICF file has a waitime of 1200 seconds. Kathy Bowden Cels Enterprises, Inc. ------------------------ Yahoo! Groups Sponsor --------------------~--> $9.95 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/OIFolB/TM --------------------------------------------------------------------~-> . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
