| From: SMTP%"[email protected]" 3-APR-1997 06:04:43.32
To: [email protected]
CC:
Subj: Re: A: more info about DECnet/OSI
Return-Path: [email protected]
Received: by vaxsim.mro.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
Thu, 3 Apr 1997 06:04:39 -0500
Received: from mail.swip.net by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV)
id FAA16470; Thu, 3 Apr 1997 05:59:53 -0500 (EST)
Received: by mail.swip.net (8.6.8/3.01)
id MAA20424; Thu, 3 Apr 1997 12:44:51 +0200
Received: by front.se (DECUS UUCP ///2.0/);
Thu, 3 Apr 97 12:27:52 MET
Received: from osf07.front.se by berlin.front.se (MX V4.1 VAX) with SMTP; Thu,
03 Apr 1997 12:27:48 MET-DST
Sender: [email protected]
Message-ID: <[email protected]>
Date: Thu, 03 Apr 1997 12:27:57 +0200
From: Per Lindberg <[email protected]>
X-Mailer: Mozilla 3.01Gold (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: [email protected]
Subject: Re: A: more info about DECnet/OSI
References: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
[email protected] wrote:
>
> Regards,
>
> I'm trying to learn more about the problem you are experiencing with the
> DECnet/OSI API. Please detail the environment where it works and does not work.
>
> Architecture: VAX or Alpha
> Operating system version:
> DECnet/OSI version:
>
> I've given your preliminary problem report to DECnet engineering and hope to
> hear what they say about the problem.
>
> Thank you,
>
> Mark Schafer
> Alpha Developer Support
Here is the supplemental information you asked for.
Architecture: Alpha (AlphaStation 250 4/266)
Operating system version: OpenVMS 6.2-1H3
DECnet/OSI version: 6.3
The last question makes me think that you perhaps have not received
the problem decription I mailed to Francois Notre. I therefore
include my original problem description once again below.
Please pass it to DECnet engineering without changes.
-----------
We have migrated our client-server applications from DECnet IV
to DECnet/OSI. It works fine on DECnet/OSI version 6.1, but
not on DECnet/OSI version 6.3.
The software runs on VMS, is written in C, and uses the
VMS QIO API to DECnet, using what DEC calls "non-transparant
task-to-task communication".
The problem is this: when the DECnet connection is physically
broken, a SYSTEM-F-PATHLOST event is signalled. As per the
API documentation, I have both a VMS I/O channel and an
associated VMS Mailbox. I also have an asynchronous QIO READ
operation pending on both, with associated AST callback functions.
When an event like SYSTEM-F-PATHLOST occurs, both AST functions
should be called. The AST for the channel read QIO should have
SYSTEM-F-PATHLOST in the associated IOSB I/O Status Block.
The AST for the mailbox read QIO should read a MSG$_PATHLOST
message.
This happens on DECnet IV, DECnet/OSI 6.1 but *not* on DECnet/OSI
6.3, where the mailbox message never arrives. This confuses our
software, since the DECnet channel now is in an unspecified state.
(I can go into lots of more detail on the latter subject, if needed).
----------
Hope this helps.
Best regards,
--
Per Lindberg ([email protected]) ! __!__ Ceci n'est pas
Front Capital Systems, Box 70351, ! _____(_)_____ un Piper
10724 Stockholm Sweden. 46-84540000 ! ! ! !
|
| From: SMTP%"[email protected]" 3-APR-1997 16:01:20.45
To: [email protected]
CC:
Subj: Re: A: more info about DECnet/OSI
Return-Path: [email protected]
Received: by vaxsim.mro.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
Thu, 3 Apr 1997 16:01:16 -0500
Received: from mail.swip.net by mail13.digital.com (8.7.5/UNX 1.5/1.0/WV)
id PAA10797; Thu, 3 Apr 1997 15:50:27 -0500 (EST)
Received: by mail.swip.net (8.6.8/3.01)
id VAA12117; Thu, 3 Apr 1997 21:36:43 +0200
Received: by front.se (DECUS UUCP ///2.0/);
Thu, 3 Apr 97 18:01:52 MET
Received: from osf07.front.se by berlin.front.se (MX V4.1 VAX) with SMTP; Thu,
03 Apr 1997 18:01:50 MET-DST
Sender: [email protected]
Message-ID: <[email protected]>
Date: Thu, 03 Apr 1997 18:01:59 +0200
From: Per Lindberg <[email protected]>
X-Mailer: Mozilla 3.01Gold (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: [email protected]
Subject: Re: A: more info about DECnet/OSI
References: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
[email protected] wrote:
>
> Thanks for the additional info. I presume that this is the environment that is
> not working.
Yep.
> Did it work on the same system when it was running DECnet/OSI V6.1?
I presume that you mean the exact same piece of hardware.
I *beleive* that we first ran the tests on the same machine with 6.1,
and failed to see the problem. Then we upgraded to 6.3 and then the
problem could be seen. I'm not 100% sure on this, but quite sure.
> Please note that there are ECOs for DECnet/OSI V6.3 available in the public
> patch area on the Internet at
> ftp://ftp.service.digital.com/public/vms/axp/v6.2/decnetosi/6.3/
> It would appear to me that the problem you describe is listed in the README.
Thank you, I'll have a look!
> Please consider this patch, or upgrading to a later version.
We will. If there are any official recommendations from DEC on
later versions, please let me know.
Thanks for the quick reply. I will mail you again to let you know
if your suggested solution works.
Best regards,
--
Per Lindberg ([email protected]) ! __!__ Ceci n'est pas
Front Capital Systems, Box 70351, ! _____(_)_____ un Piper
10724 Stockholm Sweden. 46-84540000 ! ! ! !
|