X-Envelope-to: ibmtcp-l@PUCC.BITNET
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.ibmtcp-l
Date:         Mon, 28 Sep 1992 15:37:44 +0200
From:         Hans de Klein <snhkl3@AMSI05.KSLA.NL>
Subject:      TCP/IP for MVS/ESA V2.2 Dataset allocations

We run two MVS/ESA systems with shared spool (one nodename), shared
dasd and a shared SMP/E target, running multiple TCP/IP STC's (at
least one per system).
We feel that the way datasets are allocated by the TCP/IP software
is very inconvinient, very impractical and time consuming to
maintain.
Does anyone have some suggestions for the issue's below.

SMP/E installation:
Is is possible to change the TCPIP high level qualifier without
running the ZAP ?
(one target for both systems + don't want to ZAP without SMP)

--------------------------------------------------------------------

Scenario:
A TCPIP or FTP parameter dataset is allocated to a TSO address space
with exclusive ownership following an edit.
TCPIP or FTP are then started,
An error message is issued by TCPIP or FTP stating that the dataset
cannot be opened but initialisation continues.
The result is an active TCPIP or FTP which is only partly configured.

Is it possible to suspend the initialisation if a dataset which exists
cannot be opened ?

--------------------------------------------------------------------

To keep parameter datasets unique for each TCPIP and FTP address space
the dataset must have an HLQ the same as the JOBNAME (our preference).
This results in a proliferation of USER CATALOG ALIAS definitions,
RACF groups and RACF profiles having to be defined.
For multiple TCPIP / FTP address spaces the parameters become spread
over numerous datasets rather than in one central place.
Administration tasks become complex.

Is is possible to define the parameters as members of a PDS
rather than as individual sequential datasets ?

--------------------------------------------------------------------

It is possible to direct a TELNET user to a specific TCPIP address space
by defining a 'userid.TCPIP.DATA' dataset pointing to the specific
TCPIP address space.
If for any reason that TCPIP address space is not available is it
possible to globally switch the users to a different TCPIP address space
without manually editing the 'userid.TCPIP.DATA' datasets?

--------------------------------------------------------------------

We have an environment consisting of two processors running MVS/ESA
in a shared JES spool environment with shared DASD.
Our requirement is to run multiple TCPIP address spaces on both
of the machines.
When a user on the SNA network selects TSO from his menu he may be
logged on to TSO running on either machine.
His TELNET request needs to be directed to a specific TCPIP address
space depending on which machine he has been logged onto.
Please could you suggest what parameters could be created to achieve
this flexibility ?

--------------------------------------------------------------------

Under TELNET the attention key may be used to invoke a TELNET command.
Is it possible to pass the attention to an application ?
Some applications, eg DFHSM, require use of the attention key.

--------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU