🚀 go-pugleaf

Hello everybody,

During a session initialisation between an application using DECnet/SNA
APPC/LU6.2 on a VAX/VMS and a VTAM application on an IBM VSE/SP running VTAM
V3.2 (!!) the initialisation process hangs. The scenario is as following:

        The VTAM application is running and waiting for its LOGON exit
        being activated (necessary because the CINIT contains user data).
        Now the VAX application is started. It sends an INIT SELF packet to
        the IBM with a 60 bytes long user data. The SNA trace on the VAX side
        shows that the packet is sent to the IBM. A positiv response is even
        sent from VTAM. Then nothing comes anymore! The VTAM buffer trace on
        the IBM shows

                SSCP (VTAM)             LU (application)
                ----------------------------------------
                ACTLU   ---------->                
                        <----------     +RSP
                        <----------     NOTIFY
                +RSP    ---------->
                CINIT   ---------->

        then nothing. The CINIT packet is correct and the right logmode is
        taken. A VTAM display command on the application (P)LU shows a 
        session with the (VAX) SLU in PCINIT-S status.

The VTAM application can on the other hand estabish sessions with terminals.
Here the same princip is applied: INIT SELF from the terminal which triggers
the LOGON exit of the application (by the way the *s a m e* exit routine!).
And it works! Ofcourse one of the first things the exit routine does is to
output a message on the console. For a terminal session the message is written
to the console, for the "LU 6.2 session" nothing is written. That's why I
assume that the CINIT message does'nt "reach" the application.

The same application runs under VM/GCS/VTAM and under VM/VSE/ESA/VTAM V3.3 
without problem! Another version of the application, where the session is
initiated from the VTAM application (without CINIT request) comes up on the
VSE/SP machine without problems either!!

Can the reason of the problem be the resources of the VTAM (buffers, memory,
...)? Does somebody have an idea?

Thanks in advance

Tamim

--
Tamim Ziai                              internet: tamim@integrata.de
INTEGRATA AG, Tuebingen, Germany        Phone: +49 7071 409 191
-- 

--
Tamim Ziai                              internet: tamim@integrata.de
INTEGRATA AG, Tuebingen, Germany        Phone: +49 7071 409 191