On 9/16/2020 10:21 PM, Barbara Nitz wrote:
Thanks, Brian,
This is almost always a problem with the VTAM definition of the NJE applid that
you are using. Possibly you didn't start it or it was started before VTAM or
JES was ready for it to be started.
The NJE/TCP connection method should work out much better than the SNA method,
but there is no reason why it should not have worked.
We defined and activated the VTAM NJE major node way after IPL, right around
the time we tried to set up NJE/SNA. It was showing a status of connectable,
and JES2 had no problem starting LOGON1 to that VTAM definition. In fact, we
used the same commands/definitions and order of things after we had IPL'd
without the NJE/TCP keywords in the JES2 deck.
I take it that we ran into a bug, then, if nobody is aware of it being
documented that it shouldn't/couldn't work.
We ran a mixture of TCP and SNA NJE for a long, long time and then
eventually (by accident in fact) ended up with an OSA hardware
configuration that could no longer support SNA. We couldn't use EE
because both ends of the connection were not MVS. So we capitulated and
changed everything over to TCP. It's a bit less predictable than SNA
was, but gets the job done. I see no reason to believe that falling
back to SNA would not work if we chose to do so (and had the necessary
OSA hardware).
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
