8.3 -> 8.4 FTAM stop working

[Ruslan R. Laishev]

Hello All!

Is there some one who use FTAM & X.25 under OpenVMS 8.4 ?


We discover a problem after upgrading OpenVMS 8.3 to 8.4:

$ directory/appl=ftam/out=tempfile.tmp L5ESS""::*.*
%FTAM-E-INVAEI, Presentation -- The application entity invocation is invalid
%FTAM-E-NOTDIR, *.* not found
%FTAM-E-ERR_PROTOCOL_SP, initialize: protocol error on Receiving an FTAM Association response
%DIRECT-W-NOFILES, no files found
%RMS-E-FNF, file not found
$


@sys$test:OSask_ivp.COM - takes errors.

We don't change and installing anything after upgrade OpenVMS.


Any ideas ?

[Ruslan R. Laishev]

Some additions:

$ directory/appl=ftam/out=tempfile.tmp L5ESS""::*.*
$
%%%%%%%%%%% OPCOM 13-NOV-2010 14:01:17.19 %%%%%%%%%%% (from node DTV1 at 13-NOV-2010 14:01:17.19)
Message from user SYSTEM on DTV1
Event: Port Terminated from: Node LOCAL:.DTV1 X25 Access,
at: 2010-11-13-14:01:17.192+03:00Iinf
Client=OSI Transport Template OSI$TMP_00000061,
Type=Switched,
State=Open,
Call Direction=Outgoing,
Call Association=X25 Access Template "OSI Transport",
Protocol Identifier='00000000'H,
Channel=0,
Reverse Charging=False,
Redirect Reason=Not Redirected,
Fast Select=Not Specified,
Data Octets Received=0,
Data Octets Sent=0,
PDUs Received=0,
PDUs Sent=0,
Segments Received=0,
Segments Sent=0
eventUid 7BFA0455-EF2E-11DF-A1A6-001321E9098B
entityUid 9C8D56D8-CC94-11DF-83E4-AA0004000304


$
%%%%%%%%%%% OPCOM 13-NOV-2010 14:01:17.19 %%%%%%%%%%% (from node DTV1 at 13-NOV-2010 14:01:17.19)
Message from user SYSTEM on DTV1
streamUid 9ED0BCAE-CC94-11DF-84A0-AA0004000304


$

$ define OSAK_TRACE ON
$ directory/appl=ftam/out=tempfile.tmp L5ESS""::*.*
%FTAM-E-NOTDIR, *.* not found
%FTAM-E-TRC_INVFUNC, TRC -- Trace file in invalid state for requested operation
%FTAM-E-TRC_OPEN, Error opening trace file OSIF$RESPONDER.TRACE
%DIRECT-W-NOFILES, no files found
%RMS-E-FNF, file not found
$

[JohnDite]

Hi Ruslan,

i have customers using FTAM and X.25 but to date none of these have upgraded to V8.4.
With respect to your problem have you checked this layer for layer? Ie. can you tell us whether you get an X.25 connection, followed by an OSI Transport connection (CTF Trace).

What does your configuration look like? Do you use local synchronous interfaces or does your system act as an X.25 access system?

John

[Shriniketan Bhagwat]

Hi,

Below are the few links to the documentation. If you search for â FTAM X.25 vmsâ in the internet you will get many links about the FTAM. May be help full in resolving your problem.

http://h71000.www7.hp.com/doc/73final/6501/6501pro_002.html
http://h71000.www7.hp.com/doc/73final/6501/6501pro_003.html

Regards,
Ketan

[Bhadresh]

>>>@sys$test:OSask_ivp.COM - takes errors.

OSAK installation verification procedure (IVP) produces a log file called OSAK$IVP.LOG in the default directory, SYS$TEST. Can you please check the log file to identify the source of the problem?

Regards,
Bhadresh

[Ruslan R. Laishev]

$ typ OSAK$IVP.LOG


***** IVP Initiator Tests - Blocking Mode *****

Select OSAK call timed out

IVP blocking initiator tests completed with 1 failures
- Tests performed = 4
- Tests successful = 3
- Serial numbers of tests that failed = 4


***** IVP Initiator Tests - Non-blocking Mode *****

OSAK status block value failed
Select OSAK call timed out

IVP non-blocking initiator tests completed with 2 failures
- Tests performed = 4
- Tests successful = 2
- Serial numbers of tests that failed: 2, 4


***** IVP Responder Tests - Blocking Mode *****

Select OSAK call timed out

IVP blocking responder tests completed with 1 failures
- Tests performed = 3
- Tests successful = 2
- Serial numbers of tests that failed: 3


***** IVP Responder Tests - Non-blocking Mode *****

Select OSAK call timed out

IVP non-blocking responder tests completed with 1 failures
- Tests performed = 3
- Tests successful = 2
- Serial numbers of tests that failed: 3
$

[JohnDite]

Ruslan,

trust me. The only way to get to the source of this problem is to determine first of all whether you get out on the wire. You'll have to use either external or internal trace facilities.

What does your X.25 configuration look like?
XOT or GAP or synchronous devices ?
John

[Ruslan R. Laishev]

John,
problem begins at OSAK layer, not on wire...

[JohnDite]

Ruslan,

please carefully reconsider your statement - "problem begins in OSAK"

Ask yourself what happens when you initate the command

$ directory/appl=ftam/out=tempfile.tmp L5ESS""::*.*

If you are aware of your configuration the name L5ESS will be resolved via the file ISOAPPLICATIONS.DAT to a string which identifies the upper layer addressing (TSEL, SSEL, PSEL, AE Identifier etc.), an X.25 address or a name that is translated via the OSIT$NAMES name table and possibly an OSI Transport Template.

With this information, the FTAM application attempts to initate the lower layer connections. Remember the OSI seven layer model. Assuming there is a physical connection a layer 2, then layer 3 etc. will established.

All that you have shown is a "Port Terminated Event". This shows that yor DIR FTAM command resulted in an attempt to establish an X.25 connection. However this resulted in failure. If no X.25 Connection was been established hence no OSI Transport connection was established and therefore there was no upper layer activity.

Now you have to ask yourself the question, why was there an X.25 establishment failure?
BTW, you did not show us the complete "Port Terminated Event" - usually there is information pertaining to the Called and Calling X.25 address. In addition what looks suspicious is the value of your Protocol Identifier='00000000'H. Usually if you are running OSI Transport over CONS then this should be `03010100'H.

So if you want to get further with this problem gives us details of:

1) entry L5ESS in ISOAPPLICATIONS.DAT
2) your configuration:
NCL Definitions for
OSI Transport ...
X25 Access ...
X25 Protocol (if applicable)

3) a CTF Trace
this will at least show us the outgoing call and if you got some kind of response.

[Ruslan R. Laishev]

Hello, John!

Thanks for the cool exlplanation, but ... see again:


$ define OSAK_TRACE ON



$ directory/appl=ftam/out=tempfile.tmp L5ESS""::*.*
%FTAM-E-NOTDIR, *.* not found

%FTAM-E-TRC_INVFUNC, TRC -- Trace file in invalid state for requested operation

%FTAM-E-TRC_OPEN, Error opening trace file OSIF$RESPONDER.TRACE
%DIRECT-W-NOFILES, no files found
%RMS-E-FNF, file not found
$