Conference ufhis::siemens_communication

8.0. "Large File Problems" by ECCGY4::STROHMAIER () Tue Aug 30 1988 17:58

          <<< PAULUS::SYS$SYSDEVICE:[NOTES$LIBRARY]VAXFTSIE.NOTE;1 >>>
                       -< VAX FTSIE Support Conference >-
================================================================================
Note 7.0                       Large file problems                     4 replies
MGOS01::JONES "$ HELP> I need somebody <RET>"        23 lines  29-JAN-1988 15:40
--------------------------------------------------------------------------------
    I installed FTSIE at Siemens (UB-B) in Munich at the end of last year
    and we are currently carrying out tests with large files (small
    ones work O.K.) of approx. 20 Megabytes.
    After transferring for a while we receive the status "W" instead
    of "A" and two things have happened:
    1. The process FTSIE$OPS_0000 has disappeared
    2. OPCOM sends the message:
       "FTSIE AUTTAB ERROR-STATE-EVENT-0000000B-00000005"
       which I can't find documented anywhere.
    Is this a logical link failure on the BS2000 side (the traces would
    suggest this)?
    I'd appreciate any answers or tips on the subject.
    Incidentally I've altered the command procedure FTSIE$MKSHRIMG.COM
    because the program FTSIE$MSG.EXE had the wrong protections ie.
    WORLD had no access, everytime the VAX was booted.
    What puzzles me is why this program is deleted in SYS$SPECIFIC:[SYSLIB]
    and then copied over from SYS$SPECIFIC:[SYSMSG] at every startup.
    
================================================================================
Note 7.1                       Large file problems                        1 of 4
PAULUS::LUKAS "Dieter Lukas, VAX FTSIE Technical Pr" 14 lines   1-FEB-1988 13:10
                     -< Perhaps a "MAX_FILE_SIZE"-problem >-
--------------------------------------------------------------------------------
	It seems to be a "MAX_FILE_SIZE"-problem, that means
	SIEMENS/FT-BS2000 can't perhaps handle such big files.
	To give you a more detailed answer I need the output of
	the FTSIE trace.
	Please try it again with FTSIE Trace switched on and copy the
	binary FTSIE traces (FTSIE$TRACE_nnnnnn.DAT) to
	PAULUS::FTSIE$PUBLIC.
	I will look at these traces and give you another reply.
	- Dieter
================================================================================
Note 7.2                       Large file problems                        2 of 4
MGOS01::JONES "$ HELP> I need somebody <RET>"         6 lines   5-FEB-1988 17:25
                               -< Reply to 7.1 >-
--------------------------------------------------------------------------------
    Dieter,
    Thanks for responding so swiftly. I carried out tests with TRACE
    enabled at Siemens yesterday and have sent you all relevant listings
    today, so you should have them by Monday. 
    Regards
    Mitchell 
================================================================================
Note 7.3                       Large file problems                        3 of 4
PAULUS::LUKAS "Dieter Lukas, FTSIE Project Leader"   19 lines  10-FEB-1988 09:22
                             -< Need VOTS Traces >-
--------------------------------------------------------------------------------

    Mitchell,
    I have analyzed the FTSIE trace listings you sent me.
    The "famost last words" in this listing are:
    TEVENT DISIN CID= 272
    TDISIN CID=  272 REASON=   7
    This messages tell us that the transport connection has gone down.
    But I don't know why.
    Could you please send me the VOTS Traces.
    I need them to solve this problem.
    Dieter
                         
================================================================================
Note 7.4                       Large file problems                        4 of 4
MGOS01::JONES "Quorum lost - cLuster's last stand"   11 lines  25-FEB-1988 10:20
                         -< Current state of affairs >-
--------------------------------------------------------------------------------

    Dieter,
    We carried out OSI traces as you suggested but they only produced
    "normal" results on the VMS side ie. "DR" (disconnect request) and
    "DC" (disconnect confirm). We then decided to test the systems on
    their own ie. on a seperate section of ethernet with the repeaters
    switched off. This worked O.K. and we transferred 25 MB files at
    a rate of 80 Kilobits/sec.
    Siemens then admitted that the firware in their adapter had problems
    when there was heavy traffic. We are now waiting for them to turn
    up with the latest revisions of their software.
    Mitch