Norbert

Note that from the time of support for MPC CTC in devices such as the 2216, 
the term AHHC was formally changed to ANNC, that is, "host to host" 
became "node to node" for obvious reasons.

Have you defined both your APPN nodes as Network Nodes? The simplest 
configuration is to have one Network Node and one End Node.[1]

You had better define "hung". As far as I can see everything "works". It is 
just 
that when using LSA (3172 SNA channel protocol) Ethernet adapters using 
OSA features, which I know about, or these 7060 "internal cards" which I do 
not, and a type 2.1 connection as opposed to a subarea connection, you 
have a performance problem or some sort shortly after the SNA session is 
established, specifically a TSO session.

As - I think - you have managed to work out, the MAXDATA operand of the 
PU statement representing the adjacent link stations is irrelevant with type 
2.1 node connection definitions. This is because a type 2.1 node obtains the 
value of the size of the maximum "basic transmission unit" (BTU) which can be 
*sent* - which is what MAXDATA, in the absence of other information, 
defines - from the adjacent node which supplies the size of the 
maximum "basic transmission unit" (BTU) which can be *received* using 
the "exchange identification" (XID) message.

Note that there never has been nor never will be an entity which can logically 
be described as a "PU 2.1", there is a node type 2.1, a node type 2(.0) and a 
PU type 2. A node type 2(.0) *will* contain a PU type 2 and a node type 2.1 
*can* contain a PU type 2 - but it may not.[2]

I think you may have misreported the 1498 number. 1500 is the maximum size 
of a frame on an old-fashioned Ethernet LAN. You now need to introduce the 
802.2 connection-oriented headers. These take up 4 bytes, two for SAP and 2 
for control. I think your number should be 1496.

Incidentally, I am always for keeping discussions "on the list". That way 
someone with a similar problem searching the archives can find his/her solution 
without having to rely on responses from active subscribers on the list - who 
may be taking a well-earned rest over a weekend!

The two sets of XCA definitions shouldn't be too large. We need only one LU 
statement and associated operands in case you have coded many. If anyone 
following this can think of other needed definitions, he/she can request them. 
After all, time is not critical since what you want does work - eventually, as 
far as I can tell.

You had also better describe more precisely the sequence of the appearance 
of messages and an estimate of the delays.

In case this is problem with VTAM buffers, you can post the D NET,BFRUSE 
output before and after your TSO logon attempt on both systems. Note that 
only type 2.1 connections using switched procedures - which uniquely 
distinguishes your problem case(s) from the others - use the XDBUF buffer 
pool.

Chris Mason

[1] In a sense, simpler still would have been to define two Low Entry 
Networking (LEN) nodes which wouldn't require you to have enabled APPN in 
your VTAM definitions at all. However you would then need to create hand-
coded directory entries in the shape of LEN-style CDRSCs - and - forcing me 
to convert this comment to a footnote when I remembered! - you couldn't 
start a session which required to be initiated by the secondary logical unit 
(LU), which would include a TSO logon!

[2] Since you are a German-speaker I assume I could state these rules as "A 
node type 2(.0) *muss* contain a PU type 2 and a node type 2.1 *muss 
nicht* contain a PU type 2." but then I'd confuse all the non-German 
speakers! Some years ago I took over as an instructor in an education centre 
from a colleague who had German as his mother-tongue. Listening to one of 
his lectures I caught him saying "must not" when he meant "need not" in 
connection with some VTAM statement coding. Who knows what confusion he 
must have sowed in his previous three years of lecturing?

On Sat, 25 Apr 2009 01:58:34 +0200, Norbert Alfred Müller 
<[email protected]> wrote:

>Hi all!
>I hope this is a trivial question for the SNA gurus :-)
>I have two nodes with z/OS ( 1.5, ADCD) , NN, linked with MPC CTC, TRL, 
and so on. Very Easy, I access from the system B to TSO in system A, 
everything is Ok.
>When I make the same with XCA ( Ethernet )  and Sw Major Node, The 
Logon form TSO "hung" after 2 o 3 RACF and TSO Messages, before the whole 
screen comes... I have a deja vu with this MAXDATA and buffers problems... 
This ocurrs always , no matter that I use a 7060 with internal cards or a z/9 
with OSA. So,APPN with CTC ok, with LLC not ok. But, in the SAME system, I 
activate Subarea connection, ( so, interchange node ) with XCA, LLC but 
FID4, no MPC CTC, and it works !.
>Resumee: the sames MVS, the same applications, but: AHHC Conection OK, 
XCA APPN not OK, XCA with Subarea OK. What's happen ? I revised the PU'S 
many times.
>MAxdata can be coded in the Pu 2.1 but is ignored. It shows 1498.
>I will not disturb the list with the configurations, but perhaps a guru have a 
Idea or can contact me out the list ?
>Thank you very much !
>Norbert.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to