Johnny
Well done!
In defence of the manual - for once! - this is what it says about
DEFAULTAPPL:
<quote>
Note: The DEFAULTAPPL statement is not required. However, if a default host
application is not specified, the A3270 client must always supply an
application name when connecting to the server.
</quote>
It appears when they use the word "must", they mean it.
You may like to look into how to specify an application from within the
APPC3270 client logic in PCOMM.
Note that the APPC3270 programs and protocol are modeled after the TCP/IP
for MVS TELNET 3270 server of 1994. I worked out the date not only from
memory - upon which no reliance can be placed - but from the Copyright text
on the cover page of the manuals and a belief that APPC3270 has not been
enhanced since it was first provided in 1994.
Making the CP name the same as the PU name is to violate an SNA rule that
network addressable/accessible units (NAUs) must be unique. NAUs are SSCPs,
PUs and LUs. With the introduction of LEN and APPN, a special LU, the CP,
was created which, within VTAM, can share the name of the SSCP.
In fact, the name of the PU statement when there is no SSCP-dependent PU
entity present is only the name of the adjacent link station. You might
think you are entitled to use the same name as the CP LU in this case. Well,
many have tried it and failed! One reason it won't work is that it violates
a VTAM rule. VTAM places both names in its "name space" so that the VARY
ACT/INACT commands, for example, can find the resource based purely on its
name. The name of the CP is relevant even with a LEN connection, since the
CP acts as an LU and can show up in VTAM as a CDRSC.
Chris Mason
----- Original Message -----
From: "Johnny Luo" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <[email protected]>
Sent: Monday, February 26, 2007 3:27 AM
Subject: Re: Do I need to setup APPC/MVS?
Oops...it now works!!!!!!
John,
If you specify the workstation CP name the same as the PU name, the
connection will fail. I have tried with that. Of course, just as Chris
said,
the local LU 6.2 name can be the same as the CP name.
Yes. The DEFAULTAPPL statement is the cause of all these problems - When I
added it to the initialization file, both EEDLC and Anynet works!!!
I must say here that the APP3270 manuals are really not so friendly. They
told me that APP3270 is modelled after TN3270 server and they didn't told
me
that unlike TN3270 server APP3270 server must have a default application
choosed. (And that's why I commented that statement out in the ini file.)
Thanks, Chris and John. I'm now feeling very good and without your help,
it's impossible.
On 2/26/07, Johnny Luo <[EMAIL PROTECTED]> wrote:
On 2/25/07, John S. Giltner, Jr. <[EMAIL PROTECTED]> wrote:
In the "IST663I INIT OTHER REQUEST FAILED, SENSE=10010008 256" message,
what are the LU names invloved?
Ya..here is the problem. I don't know how to find out and the only thing
I
can do is to look up the sense code but sadly it's of little help.
As I said in the previous mail, when connecting through Anynet, the
problem is the same..
--
Best Regards,
Johnny Luo
--
Best Regards,
Johnny Luo
----------------------------------------------------------------------
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
