TSO logon through 3270

[ER]

Please forgive me as I'm new to this whole thing.

I'm trying to establish an LU-LU session with TSO through MS SNA Server
(actually, HIS). TSO has MAXUSERS set to 10 and only 1 or 2 are in use at
any given time. My LUs appear as ACTIVE through HIS. But when I open a
3270 window and type LOGON (or any other command), I get either COMMAND NOT
RECOGNIZED or MISSING PARAMETER or INVALID SYNTAX. The DLOGMOD, MODETAB and
USSTAB parameter values (for the LUs) cause 'table not found' messages, but,
I'd think that even with the default tables and modes I'd be able to get
something other than the responses I've been getting.

I know that the major and minor nodes are active when I try this because I
use the

d net,id=snal3174

and

d net,id=snal02 (snal03, 04, etc.)

commands, and they show the nodes as active. The LU has its PLU capability
INHIBITED, but its SLU capability is ENABLED (once I open the 3270 window in
HIS).

I'm not completely sure of what command I'd need to type to logon, so I
tried LOGON USERID, LOGON TSO USERID, LOGON, etc., all to no avail.

If there's more information that you need, or if you can point me somewhere
helpful, please let me know.

Thanks,
Emilio

[John S. Giltner, Jr.]

Suggest that you talk to your VTAM network sysprog.

to logon from TSO from the welcome screen you would normally

LOGON APPLID(tsoappl) DLOGMOD(D4C32782)

Where "tsoappl" is your TSO's APPLID. The logmode table D4C32782
is for SNA 3270 terminals with Model 2 (24x80) screen.

The table not found messages mean that what ever you have coded
on the MODETAB and USSTAB parameter do not exist as members in your
VTAMLIB
concatination. DLOGMOD should specify a value of an entry that exists
in
the table you specify for the MODETAB.

[ER]

Thank you, John!

(Unfortunately, I'm as close as they get to a VTAM network sysprog here. We
have a test MP3000 that we recently acquired, but nobody here knows VTAM. I
really appreciate the help you've given me so far, and I'm not expecting you
to continue ... but definitely would be thankful.)

Although I didn't get to connect to TSO yet, at least I got a different
error message. I typed in

LOGON APPLID(A06TSO09)

and got the following response

SNAL02 UNABLE TO ESTABLISH SESSION - INIT SELF FAILED WITH SENSE 08570002

I've tried with the DLOGMOD parameter but it responds with

DLOGMOD PARAMETER EXTRANEOUS

The sense code tells me that the SSPC-PLU session is not active. I'm not
sure how to activate that session, but I think I'm getting closer.

Thanks again for your help,
Emilio

"John S. Giltner, Jr." <gil...@mnsinc.com> wrote in message
news:3A8CA845...@mnsinc.com...

[John S. Giltner, Jr.]

Try issuing LOGON APPLID(A06TSO) and see what happens

[ER]

Thanks again for your help John.
Turns out that I needed to type:

LOGON APPLID(a06tso) LOGMODE(sna3270)

Thank goodness it was so intuitive! (a little sarcastic)

ER

[John S. Giltner, Jr.]

What this means is that the default logmode table entry for the terminal
being used is not SNA3270. Which SNA3270 is not one of the default
entries supplied by IBM, so this entry is one that your sysprogs defined
themselves for some reason. Which there are many reasons to define your
own entries. Normally to get the command required you do need to go to
your sysprogs. If they do not know, they should be able to find it out,
but it is not always easy. Could have been something that was setup
years ago and and the people that setup are no longer there.

If your sysprogs setup your LU definition so that the default is SNA3270
and if they setup a USS command called TSO that automatically does the
LOGON APPLID(A06TSO), then all you would need to type in is TSO. This
is how it is normally done.