| 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 |
I have a customer that has the following configuration :
Digital enviroment:
A) Vax 4100 OVMS 5.5-2H4, MEP-VT V2.3, MEPRTL V1.0B (local)
B) Vax 4100 Ovms 5.5-2 , MEP-VT V2.3, MEPRTL V1.0B (remote througth
routeabout 90)
C) Vax 3100 OVMS 5.5-2 , MEP-VT V3.0, MEPRTL V1.1 (remote througth
WANrouter 500)
D) Domain SNA Gateway sw V2.0
IBM enviroment:
E) IBM 3090 , VTAM v3.3/XA
F) IBM 3090 , VTAM v4.2/ESA
G) 3270 terminal's connected to E)
H) 3270 terminal's connected to F)
He try a connection from G) terminals to vaxes A),B),C) and all work fine.
When he connects from H) terminals to vaxses A) and B) he doesn't found
any problem , but he isn't able to connect to vax C).
The opcom message that appears in VAX C) console , comming from domain
gateway is that follows :
%%%%%%%%%% OPCOM 13-FEB-1997 11:09:40.07 %%%%%%%%%%%%%%%%%%%%
Message from user SYSTEM on VX1109
Event: Outbound Connection Rejected from :Node NISSAN:.GW1102 SNA Access
Server , at: 1858-11-17-01:25:35.670-01:00Iinf
Port=SNA Access Server Port 24,
Reason=652
eventUid 5AEAA560-886E-1135-8000-08002B36CE66
entityUid CE122800-886A-1135-8000-08002B36CE66
streamUid CDBE3BA0-886A-1135-8000-08002B36CE66
%%%%%%%%%% OPCOM 13-FEB-1997 11:09:40.07 %%%%%%%%%%%%%%%%%%%%
Message from user SYSTEM on VX1109
Event: Session Start Failure from: Node NISSAN:.GW1102 SNA LU Services,
at: 1858-11-17-01:25:35.670-01:00Iinf
SID='D95F6C2CFD86F60A'H,
LU=BERGE,
Remote LU=LDPMCS,
Initiating LU= LDPMCS,
Sense Data='08570002'h
eventUid 5AEAA560-886E-1135-8000-08002B36CE66
entityUid CE122800-886A-1135-8000-08002B36CE66
streamUid CDBE3BA0-886A-1135-8000-08002B36CE66
The sense data translation is "SSCPLU session is not active "
Customer says that LU in IBM is up and actived.
Is there any incompatibility between VTAM v4.2 and MEP-VT v3.0 ?
Any pointer to MEP-VT kit ( MEPVT030.B and MEPVT030.C )????
Any suggestions will be appreciate
Thank's in advance
Luis Miguel Sanchez
BARCELONA SUPPORT
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 7010.1 | FREE::CAMBRIA | We're just one PTF from never talking to VTAM again | Fri Feb 14 1997 11:23 | 48 | |
> <<< Note 7010.0 by BARNA::DSMAIL >>>
> -< SNA SENSE DATA 08570002 MEP-VT V3.0 VTAM 4.2/ESA >-
[snip]
> He try a connection from G) terminals to vaxes A),B),C) and all work fine.
> When he connects from H) terminals to vaxses A) and B) he doesn't found
> any problem , but he isn't able to connect to vax C).
[snip]
> %%%%%%%%%% OPCOM 13-FEB-1997 11:09:40.07 %%%%%%%%%%%%%%%%%%%%
> Message from user SYSTEM on VX1109
> Event: Session Start Failure from: Node NISSAN:.GW1102 SNA LU Services,
> at: 1858-11-17-01:25:35.670-01:00Iinf
> SID='D95F6C2CFD86F60A'H,
> LU=BERGE,
> Remote LU=LDPMCS,
> Initiating LU= LDPMCS,
> Sense Data='08570002'h
> eventUid 5AEAA560-886E-1135-8000-08002B36CE66
> entityUid CE122800-886A-1135-8000-08002B36CE66
> streamUid CDBE3BA0-886A-1135-8000-08002B36CE66
[snip]
> The sense data translation is "SSCPLU session is not active "
> Customer says that LU in IBM is up and actived.
The 08570002 sense code, when sent from the DG, indicates that the
gateway (usually) could not establish a network connection from the gateway
to the system where MEP (LU Berge) is _configured_ to be.
The text in the OPCOM message above: "Event: Session Start Failure" is
100% misleading(==wrong). In SNA, you can't have a Session Start Failure
until the CDINIT rq receives a +rsp.
There are many reasons why that sense code is used <vbg>, but they
all relate to the gateway not being able to get things going with the
application. For example,
o The object pointing to the application may not be configured right
o The application may not be running (or able to start automatically)
o The application may be running, but the connection request to it
times out
o There may not be a "network" route between the gateway and the VAX
at that moment
o etc.
You need to take a logmask trace and see how far you get from the gateway
to the vax.
MikeC
| |||||