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

Conference smaug::snagwy

Title:SNA GATEWAY NOTEFILE
Notice:Note 1.* -> kits and doc, 288.* -> obtaining product support
Moderator:EDSCLU::GARROD
Created:Fri Feb 07 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:7116
Total number of notes:28576

7008.0. "lu62_server and hang" by LATINA::VENTURA (MCS Madrid) Tue Feb 11 1997 11:05

    
    
    
    
    Hi,
    
    We have the following configuration:
    Sna peer server 1.3 eco 2
    Sna APPC lu 6.2 3.0 (eco 5) for digital unix 
    Alpha server 1000A 4/233 with Digital Unix 3.2G
    
    There are two problems that the customer reports to   
    us:
    
    1. When the IBM machine makes IPL and restart,
       the communication with the peer server  
       doesn't restart automatically.
       The communication is by token ring.  The customer
       makes  t21_sna_server stop and start and all
       was ok.
    
      2. The lu 6.2 server and the software is on the
         same machine that is the peer. 
    
         A) The lu62 is
         configured by script lu62_script, sometimes
    	 when start gives the error resource failure
    	 on the line INT_SVC or INT_MODE.
    
         B) Sometimes the lu62_server daemon hangs
    	 the customer solve this with lu62_server stop
    	 and lu62_server start. We see on the daemon.log
         the following message : 
    
         lu62_srv [12147]>>>>>>>>>>>>>> <<<<<<<<<<<<<<<<<
                        >> link to TP failed
                        >> PS thread is ABENDing <<
                        >>>>>>>>>>>>>>>  <<<<<<<<<<<<<<<<<    
    
    
        We make on this moment log file for the lu62_Server
        with snalog_mask , but until will be reproduce we
        don't have it.
        When this situation occurs with the lu62_server there
        are through of the peer with another lu's with
        make transactions from VMS lu 6.2 that are depedent
        and goes against the same IBM and not have this problem.
    
        Any expert know the solution for the two points.
    
        Best Regards,
        Elsa Soengas
        MCS Spain
T.RTitleUserPersonal
Name		DateLines
7008.1abort error???LATINA::SOENGASMCS MadridThu Feb 13 1997 03:0334
    
    
    	Hi,
    
    	We put snalog_mask
    	       snalog_size
    	       snalog_file
    
        and obtain this errors on the log file that we don't understand
19:42:32.51  GAI__COMPLETE_GCI_RECEIVE_DATA called
19:42:32.51  GAI has received GAP msg (size = 9)
19:42:32.51  Formatted GAP message: ABORT
             Type:      17
             Abort Code: 0x95
             Sense Code: 0x00000000
             Reserved:  0x00
             Impl  Code: 0x0000
19:42:32.51  Abort msg received on the session
             Reason = 149, Sense Code = 0x00000000
19:42:32.51  Abnormal Session Termination
               Remapping from GAP Abort to SNA error 0x0203FA7A


	  We have this same error on different parts of the log file.
    
    	  What is the meaning of this error??
    	  It's our software problem??
    	  Thanks for your answers,
    
    	  Elsa Soengas
    	  MCS Spain
7008.2Some info, but not many answers, yet...EDSCLU::BELANGERDEBUGGING. The art of creating better bugs!Thu Feb 13 1997 08:1715
    
    The 0x0203FA7A value represents the SNA_S_PATHLOST error.  This means
    that the virtual route, route, transmission group, or circuit that
    carried the session between the gateway LU and the IBM LU has become
    unavailable.  The connection has been terminated by the gateway.
    
    The "link to TP failed" is just indicating that the transaction program
    executing on the UNIX system exited prior to all resources allocated to
    it in the LU6.2 Server were deallocated.  If the conversation was not
    in deallocate state, then a DEALLOCATE(ABEND) would be sent by the
    LU6.2 Server.  Otherwise, the resource clean-up continues normally.
    
    What version (ECO) of the LU6.2 product do you have?
    
    ~Jon.
7008.3eco 5 before, eco 6 todayLATINA::SOENGASMCS MadridThu Feb 13 1997 10:3212
    
    
    	Hi,
    
        We see the error " link to TP failed" with eco5 product. Yesterday
        we installed the eco6 product and we don't see another time
        this error.
    
        Thanks for your answers,
        Elsa Soengas
        MCS Spain
7008.4 Link to TP failed ,PS thread is ABENDingMDR01::SOENGASMCS MadridMon Feb 17 1997 10:1653
    
    
    	Hi,
    
    	We see another time the " link to TP failed" with eco 6 product
    	of LU62 SERVER AND PROGRAMMING for Digital UNIX
     
        # grep LU62 daemon.log
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]:
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:40 sunro002 LU62_SRV[560]:
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:14:43 sunro002 LU62_SRV[560]:
    Feb 17 13:20:13 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:20:13 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:20:13 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:20:13 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:20:13 sunro002 LU62_SRV[560]:
    Feb 17 13:32:53 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:32:53 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:32:53 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:32:53 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:32:53 sunro002 LU62_SRV[560]:
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]:
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>>   Link to TP failed   <<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>> PS thread is ABENDing <<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]: >>>>>>>>>>>>>>>|<<<<<<<<<<<<<<<
    Feb 17 13:46:53 sunro002 LU62_SRV[560]:
    
    May be our software problem ??
    How analyze this??
    Thanks for your feedback,
    Elsa Soengas