Thanks, Chris. I'm stuck here on a z/800 box, running z/OS 1.4 and
wishing that an upgrade was probably, or at least possible.
Unfortunately, it looks like the only upgrade on the horizon is to shift
to Sun platforms, as soon as the COBOL legacy code is adjusted and
verified. Sort of a "caretaker" position, but it provides beer money
(and damn little else!)
Rick
-----------------------------------------------------------------------------------------
Chris Mason wrote:
Rick
Let's see if this can orient you better to what is going on here.
Here are the opening paragraphs of the "System z9 and Eserver zSeries z890
and z990Open Systems Adapter-Express Integrated Console Controller User's
Guide" manual:
<quote>
Chapter 1. Open Systems Adaper (sic) -Express Integrated Console Controller
Overview
The IBM® Open Systems Adapter-Express Integrated Console Controller (OSA-
ICC) is the replacement for 2074 Console Support Controller and local, non-
SNA DFT 3174 Control Units. Its primary application is to provide 3270
sessions so you can IPL your logical partitions within any channel subsystem
(CSS) and to provide System Operator/Master consoles for z/OS®, z/OS.e,
z/VM®, TPF, and VSE. These sessions can also be used by TSO, VM, or VSE
system programmers.
The OSA-ICC is one port on an Open Systems Adapter-Express (OSA-Express)
1000Base-T Ethernet feature. An OSA-Express 1000Base-T feature has 2
ports and either or both can be configured as an OSA-ICC. OSA-ICC function
is included with your OSA-Express 1000Base-T feature as Licensed Internal
Code and you can enable it by defining the channel path type as OSC.
Throughout this document OSA-Express may be referred to as OSA.
Each OSA-ICC is capable of handling 120 sessions. The OSA-ICC uses TCP/IP
connections over Ethernet LAN to attach to personal computers (PCs) which
are running an RFC 2355 compliant TN3270E emulator.
IBM has tested the Host Access Client Package which includes the eNetwork
Personal Communications V5.6 emulator (PCOMM) in CSD3 running under
Microsoft Windows XP + for compatibility, however there is no reason to
believe that other RFC 2355 compatible emulators may not work. Please
contact the emulator product vendor directly for terms, conditions, prices and
other product details related to such vendor's emulator.
</quote>
I'm giving you this because I know where to find the OSA-ICC manuals and I
don't know where to find the 2074 manuals. In any case, the relevance is
explained in the first sentence.
I would argue with this text only in the persistent use of the word "session".
Since you suspect SNA may be involved, this careless use of the
word "session" could be confusing since you would rightly suspect a "session"
involved SNA.
What the poor deluded lambs of manual authors mean, of course, is both a
TELNET or a TCP *connection*.
So, taking your post in detail:
Doesn't PCOM communicate via TCP/IP?
Not necessarily. Using the TN3270 client function is just one way PCOMM can
use for communication.
If that's the case, then it's not going to make an IPL console, since TCP/IP
hasn't started yet.
You are assuming that the only IP implementation with TCP and TN3270E
capability is dependent on the operating system being IPLed. Actually, we
don't know which operating system Glen may be using here since he didn't
say - and, having had my knuckles firmly rapped in the past for assuming that
anything in IBM-MAIN must be talking about z/OS, I never make the
assumption that the operating system has to be z/OS - although it usually is -
quickly sitting on my hands!
On review I realised the "Communications Server" does tend to imply z/OS
rather than another of the potential operating systems.
The point is that it must be that the 2074 and certainly the OSA-ICC provide
sufficient of their own logic implementation to support a TN3270E server. They
then turn around and appear as a pre/non-SNA 3270 controller to the channel
environment of the "hardware", ideal for behaving as an "IPL console".
If you want to know more, you can scan over/read the rest of the manual I
referenced above. It is a relatively short 65 pages, which means that, since it
has all the usual standard pages, means it is relatively easy reading. Note that
all OSA manuals are tucked away in a bookshelf in the z/OS library, release by
release, under OSA/SF even though the OSA-ICC has absolutely nothing
whatsoever in the world to do with OSA/SF.
There is also a redbook which manages to be more than twice a long as the
regular manual:
http://www.redbooks.ibm.com/abstracts/sg246364.html
It seems to me that the same would be true of a straight SNA (VTAM)
environment.
Prior assumptions being incorrect, this, while true, becomes irrelevant.
Incidentally, I think Glen Gasior's observation that the PCOMM TN3270
emulator worked when Communications Server (CS) started may have been
coincidence since the configuration about which we should be talking here has
no dependency on CS whatsoever.
Of course, we need to hear back from Glen Gasior but it's possible that there
was some confusion over the IP address in setting up for the "D/R exercise"
and the CS TN3270 server address was used rather than the 2074 address.
Chris Mason
P.S. Having done a "spellcheck" as I usually try to remember to do, I
discovered that those poor lambs of manual authors don't seem to bother
performing a "spellcheck" with the manual text!
On Thu, 24 Sep 2009 17:49:50 -0500, Rick Fochtman <[email protected]>
wrote:
-------------------------------<snip>-----------------------------
*
Has anyone experienced no NIP console and no MASTER console with an IBM
2074 ?
*
During a D/R exercise the NIP console failed to appear on the PCOM
emulator.
It was available at the HMC software console. The IPL proceeded using the
HMC console and after the Communication Server was started, the Master
Console appeared on the PCOM emulator and is working fine.
*
I have not found any reason why this would occur. Configuration displays
and
HCD definitions seem normal and unchanged from previous successful IPLs. I
hope someone has had the same experience and can point me to a possible
answer.
*
This is a two lpar system. The other lpar, on the same 2074, has not
experienced this failure.
*
------------------------------------<unsnip>-----------------------------
------------
This is a new area for me, so forgive me if I seem to ask a stupid question.
Doesn't PCOM communicate via TCP/IP? If that's the case, then it's not
going to make a IPL console, since TCP/IP hasn't started yet. It seems
to me that the same would be true of a straight SNA (VTAM) environment.
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
