Dave and Mike
In an attempt to leave the topic in a "clean" state, I need to try again!
In narrative terms, the choices are the following regarding the NODETYPE,
HOSTSA and SACONNS start options:
- subarea node with subarea=1, specify none of the above start options[a]
- subarea node with suba
> If you omit HOSTSA you'll get SACONNS=NO.
This point doesn't jump out at me from Table 70, "Node type functional summary"
and yet I believe you must be right - and I'll have to revise my just created
diagrams. In principle the default value for the SACONNS start option is YES -
just take a lo
mit HOSTSA you'll get SACONNS=NO.
>
>Regards,
>Mike Wawiorko
>-Original Message-
>From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
>Hansen, Dave L - Eagan, MN
>Sent: 07 October 2011 15:01
>To: IBM-MAIN@bama.ua.edu
>Subject: Using uni
PPN only.
If you omit HOSTSA you'll get SACONNS=NO.
Regards,
Mike Wawiorko
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Hansen, Dave L - Eagan, MN
Sent: 07 October 2011 15:01
To: IBM-MAIN@bama.ua.edu
Subject: Using unique HOSTSA (runnin
Dave
> Q). What "better manageability" would the authors be talking about?
Traces and dumps - principally when jumping between two or more in the pursuit
of a problem which has manifestations in multiple VTAM nodes. It may actually
assist IBM trying to work with one of your problems rather tha
Group,
I have been reviewing the Enterprise Extender Implementation guide
(SG24-7359) in Chapter 3 it talks about HOSTSA and SACONNS. It says "For
better manageability we recommend defining or keeping a unique subarea number
using HOSTSA, and running VTAM as a pure EN/NN by coding SACONNS=N
6 matches
Mail list logo
