Conference star::wizards

1553.0. "Open: dialup problem" by STAR::JKEENAN () Tue Feb 11 1997 08:34

Return-Path: "VMS001::WWW"@vms001.das-x.dec.com
Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
	Tue, 28 Jan 1997 19:41:06 -0500
Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id TAA17208; Tue, 28 Jan 1997 19:31:01 -0500 (EST)
Date: Tue, 28 Jan 1997 19:31:11 -0500
Message-Id: <[email protected]>
From: "VMS001::WWW"@vms001.das-x.dec.com (28-Jan-1997 1931)
To: [email protected], [email protected], [email protected]
Subject: Ask the Wizard: '[email protected]'
X-VMS-To: [email protected]

Remote Host: piweba4y-ext.prodigy.com
Browser Type: PRODIGY-WB/3.1d
Remote Info: <null>
Name: Jim Dio
Email Address: [email protected]
CPU Architecture: VAX
Version: v 6.2
Questions: 

Using dial up lines with Gateways, also using OPCOM
and SNAEVL to connect to an IBM System. OPCOM and SNAEVL are used to notify a Router when the line becomes acitive in order that the router can notify the Line Handler that the IBM SNA protocol has sent the ATCLU which would allow the Line Handler to send
 the BIND to the IBM System. When the DEC System is busy with receiving or sending data there are many times that by the time the line handler is notified that the ACTLU is received the BIND from the IBM is missed. Looking for what areas we can look into 
in order to determine why the line handler is being notified too late?

   This appears to be well outside the area of the OpenVMS operating
   system, please contact Digital customer support for assistance
   with the Digital SNA product(s) in use.