T.R | Title | User | Personal Name | Date | Lines |
---|
3712.1 | It's in the post ... | HOOPY::CARLINI | | Thu Oct 10 1996 22:39 | 4 |
3712.2 | Any test program available ? | LEMAN::SCHEIDEGGER | Raymond @GEO - DTN 821-5236 | Tue Jun 03 1997 15:33 | 15 |
| Hi,
I have a problem with PVC and application unable to reconnect/reuse
COORECTLY after the PSDN has reset or other unknown reases.
It seems we have in some buffer/variable some 'shift' and the other
site got 'garbage' infos.
Trying to stop the application, stop the DTE and restart don't
help. The problems happens every 2-4 weeks at night.
Any chance to get a 'demo' program to test a PVC ?
Thanks
Raymond
|
3712.3 | Trace and proper error report required | MARVIN::CARLINI | | Wed Jun 04 1997 06:57 | 14 |
| > I have a problem with PVC and application unable to reconnect/reuse
> COORECTLY after the PSDN has reset or other unknown reases.
You'll need a trace of what happens when the network does whatever it does to
upset your application. And you'll need a description of what goes worng with
your application.
> Any chance to get a 'demo' program to test a PVC ?
> Thanks
We do have a small program, but all it does is access a PVC and throw data down
it. You already have one of those tools: your application.
Antonio
|
3712.4 | Thanks | LEMAN::SCHEIDEGGER | Raymond @GEO - DTN 821-5236 | Wed Jun 04 1997 15:31 | 31 |
| Thanks
I've a little bit more infos for this problem :
1. CONFIG |----[coder]
|
VMS/AXP /DNSES |
|-----------PSDN------Remote DTE
2. Application :
1. Appli use PVC to access a Coder
2. The coder return a Key
3. Applic establish a connection over the PSDN using a key encrytion
to access a remote DTE (having also a similar coder)
For unknown reasons the applic can use the PVC to get a new key
encryption. No NW device can be established.
The DTE is ON-Running, disable enable the x25 prot <dte> did not
fix the pb. The problem did not occurs with DECnis.
The only solution was to reboot the system.
The problem happens twice last month. It seems difficult to
reproduce the problem. We have request a ctf trace, x25 accounting
and more info from the application with NCB ...
Thanks for your help
I'll update this entry as sson as i get new infos from customer
Raymond
|
3712.5 | Additional info to gather ... | MARVIN::CARLINI | | Thu Jun 05 1997 10:03 | 22 |
| > For unknown reasons the applic can use the PVC to get a new key
> encryption. No NW device can be established.
I take it that means that the application is unable to establish a new
SVC to talk to the remote DTE? In that case you need to ascertain the
point at which the process fails: is it the $ASSIGN or the $QIO
IO$_ACCESS? Check that the program verifies the return status onall
calls not forgetting the status in the IOSB from the $QIO (once the I/O
completes). If they are performing asynchronous I/O (i.e. $QIO rather
than $QIOW) then verify that the IOSB is unique (not reusing the same
IOSB anywhere else) and that it is not allocated on the stack (unless
they also issue a $SYNCH to let the I/O complete before exiting the
routine).
If they do all the above they should be able to report an error status
(and possibly a PSI-sepcific secondary error status). If the failure is
on the $ASSIGN, look at program quotas and sysgen parameters (e.g.
BYTLM, BUFIO, ASTLM, FILLM, CHANNELCNT etc.). If the failure is on the
$QIO IO$_ACCESS, look for an OPCOM message to tell you why the X25
Access Port has terminated.
Antonio
|