Hi, All,
In preparation for z/OS 1.9 (currently on 1.7), we're fledging the
tn3270 server from the TCPIP nest to its own address space. TCPIP
currently runs in SYSSTC. Would that also be appropriate for the new
TN3270 address space? Any difference in importance or specific goals
for it?
We're
Chase, John wrote:
Hi, All,
In preparation for z/OS 1.9 (currently on 1.7), we're fledging the
tn3270 server from the TCPIP nest to its own address space. TCPIP
currently runs in SYSSTC. Would that also be appropriate for the new
TN3270 address space? Any difference in importance or
Yes, no difference in importance or goal since SYSSTC is *hardwired* at FE
which is where TCPIP lives.
Chase, John [EMAIL PROTECTED] wrote: Hi, All,
In preparation for z/OS 1.9 (currently on 1.7), we're fledging the
tn3270 server from the TCPIP nest to its own address space. TCPIP
currently
TCPIP currently runs in SYSSTC. Would that also be appropriate for the new
TN3270 address space?
I would recommend leaving it there.
Since it's a 'server' address space, it should be higher than every sub-system
that 'uses' it.
-
Too busy driving to stop for gas!
This is how our's is set up
TN3270 TN3270 TN3270 NSW SO A=00BA PER=NO SMC=000
PGN=N/A DMN=N/A AFF=NONE
CT=043.425S ET=80.07.21
WUID=STC00267 USERID=TCP
What Mark Jacobs and Mark Hamman said? Yeah, us too.
TN3270 TN3270 TN3270 NSW SO A=0063 PER=NO SMC=000
PGN=N/A DMN=N/A AFF=NONE
CT=077.101S ET=73.56.59
WUID=STC04097
6 matches
Mail list logo