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

Conference ufhis::siemens_communication

Title:Siemens Connectivity
Notice:FTSIE Contact is Michael Eisenhut @MUC 865-1487
Moderator:UFHIS::MEISENHU
Created:Tue Aug 30 1988
Last Modified:Mon Feb 19 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:195
Total number of notes:512

166.0. "%FTSIE-E-FRLIE, internal error 131" by VNABRW::MISAK_G (Styria the green heart ...) Tue Aug 17 1993 10:11

    Hello,
    
    What's the meaning of the following OPCOM Message :
    
    %FTSIE-E-FRLIE, internal error 131
    
    That's the error message a customer gets intermittent, when he starts
    a File Transfer from the SIEMENS side to a specific VAX in a cluster
    environment (It's no problem to use another VAX in that cluster...).
    The other way around the File transfer is always working correctly 
    (specific VAX to SIEMENS).
    
    So could it be a lack of System or Process Resources...
    
    Thanks for any hint or information about that 131 error,
    
    regards,
    
    Goran    TSC Austria
T.RTitleUserPersonal
Name		DateLines
166.1Same event,when we receive a x25restartBACHUS::GOOVAERTSFri Aug 27 1993 11:4211
    Hi,
    	we have the same problem,when a filetransfer is started from vax to 
    	siemens,and for a reason the link between both system
    	goes down for a few moments (a restart on x25 level).
    
    Did you get any info?
    
    Rgds
    
    Danny Goovaerts
166.2It's a black hole ...BIKINI::DITEDECnet/OSI makes ~~~~ OK!Thu Sep 02 1993 18:3133
Hi,

	this error message has haunted me since I had anything to do with this
product. Let me explain why:

FTSIE consists of two parts (simplistically seen), one part is the Siemens
part which is basically the Siemens Protocol State M/c which DEC purchased from
Siemens. This was then ported onto a VMS platform. This black box has/is
never touched by our FTSIE engineering.
The other main part is DEC's which basically provides the environment so that
the above state M/c can run in the VMS envrionment. 

This now infamous error code 131 comes from the very dark depths of the Siemens
protocol M/c and seems to be a catch-all error message as the Siemens
developers have not been able to give us a explaination of when ie. in which 
states this error will occur. 
We have always observed the error message in cases such as below when an
association (name for an application to application connection) has been reset
or cleared by one of the partners. It usually means that operation is only 
temporarily impaired. 

If you have time we would be interested in receiving more information regarding
the situations in which you see this error occurr. 

Sorry if I can't be of more help at the moment.


John

>        we have the same problem,when a filetransfer is started from vax to 
>        siemens,and for a reason the link between both system
>        goes down for a few moments (a restart on x25 level).
>