[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference help::osi_appl_support

Title:Please read note 1.0ELP::OSI_APPL_SUPPORT
Notice:Please read note 1.0
Moderator:DRAGNS::MILLERCOM::S_WATTUM
Created:Mon Aug 30 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:516
Total number of notes:2729

508.0. "FTAM Kit pointer" by KERNEL::KHANR (UK_CSC Networks Support DTN 833-3831) Wed Apr 02 1997 06:00

    
    Hello ,
                                     
    Is there a 'later' version of FTAM other then 3.2F for DECnet/OSI
    for Open-VMS 6.3 systems ?   
    
    Thanks,
    
    ~Riaz
T.RTitleUserPersonal
Name
DateLines
508.1RMULAC.DVO.DEC.COM::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringWed Apr 02 1997 08:547
Yes, we're all the way up to -M or something.  We haven't put out an ECO kit
in a long time, so the later versions are only typically available with the
later DECnet/OSI or DECnet-Plus releases.

Are you encountering a problem you think may be resolved by a later kit?

--Scott
508.2KERNEL::KHANRUK_CSC Networks Support DTN 833-3831Wed Apr 02 1997 12:4916
    
    Scott,
    
    My customers reports a problem on copy from ICL to VAX, no traces are 
    available to us,however he requested to have all the fixes for FTAM
    prior to investigating further hence the base note.
    Anyway a text transfer from an ICL VME system succeeds but the file
    is de-structured in that the entire file appears as one record there
    is no CR/LF encoding.
    
    So at the momment not very much to go on, I have requested he pull the
    file back from VAX to ICL to see the result of that, so yes sorry
    not much to go on right now.
                                                                   
    
 Thanks,Riaz
508.3IP$16.65.80.19::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringThu Apr 03 1997 09:0216
>is no CR/LF encoding

Depending on the file type, this might be normal.  Remember that many file types
on OpenVMS don't have explicit CR/LF's either - they are either implied by the
presence of just the CR or the LF or implied by the record itself (FTAM-2). 
FTAM-1 files have some interesting rules associated with them, that if ICL has
not implemented correctly, could cause something like this to happen.

This sounds like a problem on the ICL system that they should probably take up
with ICL.

In any event - if you apply the FTAM kit included with DECnet-Plus 7.1, you'll
have most of the fixes.  I will say that it's unlikely that the latest kit will
solve this problem.

--Scott
508.4KERNEL::KHANRUK_CSC Networks Support DTN 833-3831Thu Apr 03 1997 10:544
    
    Scott, Thanks , I will speak to the customer.
    
    ~Riaz
508.5IP$16.65.80.19::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringFri Apr 04 1997 10:578
I should have mentioned that if you do get traces, we can take a quick look at
them to make sure there isn't an error in our implementation.

Most likely, ICL isn't sending the file correctly or has simplified the document
which will result in a loss of structure information (FTAM-2 to FTAM-1 for
example), but a trace will confirm that.

--Scott