Windows Server

Edgar Polanco · Guest

Hi,

Is there any way to change the node type for the HIS2004 connecting through
IP-DLC?

I only see that the local node is LEN type and I want to change it to NN
(network node). My main issue is that I can't get CP-CP sessions to the
mainframe. I think that the reason is my node type, doesn't it?

Thanks in advance!!

Edgar Polanco · Guest

Charles,

Thanks for the info, unfortanetly I couldn't find any information about
changing the node type on that doc.

The only way I can check the local node type on HIS2004 is with the
Diagnostic Tool.

Do you know another doc reference? or how can I change that?

Thanks in advance!!

"Charles Ezzell (MSFT)" <charliee@online.microsoft.com> wrote in message
news:%23uZXAo3vFHA.1132@TK2MSFTNGP10.phx.gbl...

Charles Ezzell (MSFT) · Guest

Edgar,

Please take a look at this document and see if it helps in configuring this
correctly:
http://download.microsoft.com/download/a/f/f/affdc2aa-63ca-48c7-9431-c50736f24236/configuring%20ip-dlc%20link%20service%20for%20ibm%20enterprise%20extender.doc

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Edgar Polanco" <poledg@hotmail.com> wrote in message
news:EACFE0D3-715C-42EF-A21B-76E67F682503@microsoft.com...

Edgar Polanco · Guest

Guys,

I found this information,

IP-DLC Link Service Concepts and Terminology........

LEN Node
A LEN Node is a type 2.1 node that uses independent LU 6.2 protocols, but
does not support CP-CP sessions. It can be connected to a Network Node or
End Node but does not support APPN functions. The existing SNA node of Host
Integration Server is a LEN node.
http://msdn.microsoft.com/library/en-us/his_2004Main/htm/his_ip_dlc_introduction_to_the_ip_dlc_link_service_afxq.asp

Does it really means that HIS' node type is gonna be always LEN Node?

Regards,

"Charles Ezzell (MSFT)" <charliee@online.microsoft.com> wrote in message
news:%23uZXAo3vFHA.1132@TK2MSFTNGP10.phx.gbl...

Charles Ezzell (MSFT) · Guest

Yes. That was documented in the doc link I sent to you. We have always been
LEN node, since LanManager days.

LEN Node
A LEN Node is a type 2.1 node that uses independent LU 6.2 protocols, but
does not support CP-CP sessions. It can be connected to a Network Node or
End Node but does not support APPN functions. Host Integration Server's
existing SNA node is a LEN node.

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Edgar Polanco" <poledg@hotmail.com> wrote in message
news:OgDICI%23vFHA.3000@TK2MSFTNGP12.phx.gbl...

Neil Pike · Guest

Edgar,

What are you actually trying to do that you think requires this? HIS's SNA
node-type isn't going to change in the short-term, but if you can make a case
for needing extra functionality then you need to explain why.

All the functionality HIS offers in terms of LU2/3270, Printing, APPC (client
and server), WIP, HIP, OLEDB/ODBC to DB/2 etc. etc. all works over the existing
node, so what are you trying to do with a CP-CP connection?

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Stephen Jackson [MSFT] · Guest

The SNA Server service (snaservr.exe) node is a LEN node as has been
discussed here. The IP-DLC link service is actually another node that
operates as a Branch Network Node (BrNN). A BrNN acts as a Network Node (NN)
to downsteam nodes and as an End Node (EN) to upstream nodes.

As mentioned by Neil, what type of functionality are you trying to achieve?

--
Stephen Jackson
Microsoft® SNA/HIS Support

Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS"
with no warranties, and confers no rights.

"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.00006323.0a0791e0@compuserve.com...

Edgar Polanco · Guest

Hi guys,

I already configured LUs (local and remote) manually. I'm trying the basic
APPC connectivity using APING from HIS, but I'm still getting an error,

Unexpected CPI-C return code encountered...
CPI-C verb name: CMINIT, Initialize_Conversation
CPI-C return code: 20, CM_PRODUCT_SPECIFIC_ERROR
return code class: UNRECOVERABLE

I found this on a CPI-C programming reference,
Initialize_Conversation (CMINIT)
The conversation enters Reset state when CM_PRODUCT_SPECIFIC_ERROR is
returned in a return_code for the following reasons:
* CPI Communications was unable to obtain enough system storage to support
the conversation.
* An unexpected internal error occurred.

What do you think it is the problem?

Regards and thanks for your responses!

"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.00006323.0a0791e0@compuserve.com...

Neil Pike · Guest

Edgar,

Unfortunately that's not a very helpful message! A CPIC & APPC & Link Service
trace would help pinpoint where the problem lies. Could be an LU name/alias
issue, could be a bind issue, could be something else completely.

Also check out KB132720, as that's a common reason for this CPIC error message.

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Edgar Polanco · Guest

Neil,

I tried with the solution on KB132720 but it keeps failing.

I also try to get a CPIC trace, but whenever I use the <sna
folder>/sdk/bin/aping it doesn't trace anything. Should I do something else
to trace it?

The only trace I could get was the APPC, but again it doesn't work with the
APING. It was only tracing the Diagnostic Tool > APPC test and it got these
results:

APPC TP_STARTED request
APPC Type:Sync VerbID:00018000
APPC TP_STARTED response, result = OK
APPC Type:Sync VerbID:00018000
APPC ALLOCATE request
APPC Type:Sync VerbID:00014000
APPC ---- Verb Parameter Block at address 0006A248 ----
APPC 01000000 00000000 00000000 00000000 <................>
APPC F8722300 F0732300 00010000 00000000 <8r#.0s#.........>
APPC 00000000 00000000 XXXXXXXXXXXX <........XXXXXXXXXX> XX<--- deleted
on purpose
APPC 7BC9D5E3 C5D94040 C4C9E2D7 D3C1E840 <{INTER@@DISPLAY@>
APPC 40404040 40404040 40404040 40404040 <@@@@@@@@@@@@@@@@>
APPC 40404040 40404040 40404040 40404040 <@@@@@@@@@@@@@@@@>
APPC 40404040 40404040 40404040 40404040 <@@@@@@@@@@@@@@@@>
APPC 40404040 40404040 00000000 00000000 <@@@@@@@@........>
APPC 00000000 00000000 00000000 00000000 <................>
APPC 00000000 00000000 00000000 00000000 <................>
APPC 00000000 00000000 00000000 00000000 <................>
APPC 00000000 00000000 00000000 <............ >

(And it seems to get a timeout after 25 seconds ..)
APPC WinAPPCCancelAsyncRequest request
APPC Verb ID = 00014000
APPC ----------------------------------------------------------------------
----------
APPC ALLOCATE response, result = ALLOCATION_ERROR
APPC Type:Sync VerbID:00014000
APPC ---- Verb Parameter Block at address 0006A248 ----
APPC 01000000 00030000 00000004 00000000 <................>
APPC F8722300 F0732300 00010000 00000000 <8r#.0s#.........>
APPC 00000000 00000000 XXXXXXXXXXXXX <........XXXXXXXX> <--- deleted on
purpose
APPC 7BC9D5E3 C5D94040 C4C9E2D7 D3C1E840 <{INTER@@DISPLAY@>
APPC 40404040 40404040 40404040 40404040 <@@@@@@@@@@@@@@@@>
APPC 40404040 40404040 40404040 40404040 <@@@@@@@@@@@@@@@@>
APPC 40404040 40404040 40404040 40404040 <@@@@@@@@@@@@@@@@>
APPC 40404040 40404040 00000000 00000000 <@@@@@@@@........>
APPC 00000000 00000000 00000000 00000000 <................>
APPC 00000000 00000000 00000000 00000000 <................>
APPC 00000000 00000000 00000000 00000000 <................>
APPC 00000000 00000000 00000000 <............ >
APPC ----------------------------------------------------------------------
----------

APPC WinAPPCCancelAsyncRequest response, result = OK
APPC ----------------------------------------------------------------------
----------
APPC WinAPPCCleanup request
APPC ----------------------------------------------------------------------
----------
APPC WinAPPCUnhookBlockingHook request
APPC Current blocking function = 00000000
APPC ----------------------------------------------------------------------
----------
APPC WinAPPCUnhookBlockingHook response, result = TRUE

What do you think??

Thanks and regards!!

"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.00006324.1d926a4e@compuserve.com...

Neil Pike · Guest

Edgar,

Unfortunately that doesn't help. In Traces, choose SNA Application, messages
and then LU6.2 messages. Hopefully something a but more meaningful will appear
in that trace.

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Charles Ezzell (MSFT) · Guest

If the diagnostic tool times out after 25 seconds (which is what it is
designed to do for problems, see further down), then there is more than
likely a problem with the LU-LU-Mode triplet you have setup. That is, if the
link (connection) is active <vbg>. In other words, the remote and local LUs
defined in HIServer are not correct for what is defined on the host for this
PU connection, so the allocate fails.

The diagnostic tool issues the allocate across the triplet you specified,
and sits and waits for a response from the host. If it gets back a +RSP to
the allocate, it immediately issues a deallocate. In your case, it is not
getting a response, so it cancels the allocate call. Basically a simple appc
ping program to verify the LUs and modes are configured correctly.

Oh, and you really don't have to delete the LU names <vbg>.

SNA APPLICATION Internal traces (custom only), along with the traces Neil
mentioned would be helpful. The diag tool logs a lot of good information for
us here if you turn on custom tracing. Also, you may want to run the
Queryipdlc tool (this can be run from within the diag tool).

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Edgar Polanco" <poledg@hotmail.com> wrote in message
news:eqJUWM5wFHA.900@TK2MSFTNGP11.phx.gbl...

Edgar Polanco · Guest

Hi guys,

Firstable, Thanks for the great help!!

Well, i'm getting more information,
From the appc trace,
APPC Type:Sync VerbID:00014000
APPC ---- Verb Parameter Block at address 0006A248 ----
APPC 01000000 00030000 00000004 00000000 <................>

AP_M_ALLOCATE APPC_FLIPI(0x0100) /* X'0100'
APPC Primary return code = 0x003(AP_ALLOCATION_ERROR)
APPC Secondary Return Code: 0x00000004 (AP_ALLOCATION_FAILURE_NO_RETRY)

I also got different traces,

Calling routing proc 0 at address 67435A78, status 1
rc after call to routproc 0
Calling routing proc 1 at address 6101BF64, status 1
srci:0x0000 desti:0x0001. msgtype=1, opentype=36, openqual=3
destl+i: 13,1 srcl+i 5,0
Lcrcb TPCB:002372F8 RCB:002373F0
ENTER: tpcb 0x2372F8, rcb 0x2373F0 Message received: srcp 0x02, srci 0x0000,
destp 0x00, desti 0x0001
LU62CONN: set rcb destp and desti
rcb: destl = 0x05, destp = 0x02, desti = 0x0000
tpcb: destl = 0x00, destp = 0x11 desti = 0x0000
Found Original Message: previous best destl = 0x05
LU62 CONNECTION: Error Rsp
retcode,operr2,retqual: Current 0x0000000F, 0x0003, 0x00. Previous
0x00000000, 0xFFFFF004, 0x00
This error is the 'least worst' error so far
Free header at 0x0162492c
Releasing buffer 0162492C
ENTER: TPCB 002372F8 RCB 002373F0 (tp scrl = 0x00)
call sbpdfind for tpcb 0x2372F8 rcb 0x2373F0
Resloc type 0, Flags 0h, UpperLimit 4094

PVI 00000001->05110000 OPEN LU62 REQUEST
PVI
PVI ---- Header at address 0162492C, 2 elements ----
PVI 0124B006 00000000 00001800 0100C009 <.$..............>
PVI
PVI ---- Element at address 020170F4, start 1, end 81 ----
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 01000000 00000102 504F4C45 <............POLE>
PVI 44472020 XXXXXXXXXXXX 7BC9D5E3 <DG XXXXXX{INT>
PVI C5D94040 00000000 00000000 00000000 <ER@@............>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 01 <. >
PVI
PVI ---- Element at address 0201733C, start 1, end 127 ----
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 000000 <............... >
PVI ----------------------------------------------------------------------
----------
PVI 05020000->0D000001 OPEN LU62 RSP ERROR
PVI Err1:0000 Err2:0003
PVI
PVI ---- Header at address 0162492C, 2 elements ----
PVI 0324B006 00000000 00031800 01006C0A <.$............l.>
PVI
PVI ---- Element at address 020170F4, start 1, end 81 ----
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 010F0000 00000102 504F4C45 <............POLE>
PVI 44472020 XXXXXXXXXXXX 23494E54 <DG XXXXXX#INT>
PVI 45522020 00000000 00000000 00000000 <ER ............>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 01 <. >
PVI
PVI ---- Element at address 0201733C, start 1, end 89 ----
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00000000 <................>
PVI 00000000 00000000 00000000 00140BC1 <...............A>
PVI D7D7D54B D7D6D3C5 C4C707D5 8D7FA3C9 <PPNKPOLEDG.N.tI>
PVI 00010000 00000000 00000000 00000000 <................>
PVI 00000000 00050800 00 <......... >

Inbound complete, MsgFound = 1, status = 1, DestL = 13, SrcL = 5, msg =
014D492C
Call AsyncSepdveluSID with no SIDs
APPC LU access validation
Security is OFF - don't make RPC
MangleLPIs in from an App

Im also getting several Events,

Event ID: 545
ISR session failure because of link outage or error
Sense code = 0x80020000
FQPCID = APPN.POLEDG :ff3f0a0b e36924f6
Failing LS name = @R000707
Data:
0000: 53 4e 41 49 50 31 2c 20 SNAIP1,
0008: 31 1

Event ID: 18
Description:
APPC session activation failure: BIND negative response or UNBIND request
received
Sense data = 80020000 (NOTE: 0032xxxx indicates UNBIND received)
Connection = EE22
LU alias = POLEDG
PLU alias = REMOTELU
Mode name = SNASVCMG
Sense data:
8002
Link Failure: Data link failure.

And finally, lots of this event id,

Event ID: 664
Description:
RTP connection has timed-out
Connection name = @R000621
COS = CPSVCMG
Remote node name = REMOTELU
Local TCID = 00000002 6d000000
Remote TCID = 80000000 00000000
Data:
0000: 53 4e 41 49 50 31 2c 20 SNAIP1,
0008: 30 0

Regards and thanks again!!

Neil Pike · Guest

Hi Edgar. Unfortunately I've never needed to setup an IPDLC connection to a
real mainframe yet! So I've not seen the errors you're seeing. (Hoping to do
one next week at a client...)

But from the errors you're seeing it looks to me like there's a serious
connectivity/config issue at the basic link-service level. The ISR and RTP
time-outs would seem to show that.

At the network level do you have any firewalls between your HIS Server(s) and
the mainframe(s)? Are the HIS servers and mainframe(s) both ethernet attached?
What network devices are in between?

Charles will hopefully know how to debug IPDLC better than me, but I'd be doing
an IPDLC link service trace as well to see what that shows. Does Enterprise
Extender/VTAM on the mainframe show anything in it's logs?

Also, do you have any working services across the IPDLC link service? e.g. do
you have any basic LU2 3270 sessions working? I always like to define a couple
of 3270 sessions for basic comms checking even if there's no business use for
them (i.e. a connection is going to be CPI-C or DB/2 or VSAM only or
something).

Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP

Charles Ezzell (MSFT) · Guest

Edgar,

You are going to need to open a case with Microsoft's Product Support team.
I suspect this is nothing but a configuration problem. The guide I mentioned
earlier is what is needed to be setup on both our end and the host end, and
any changes could break things. That said, we are going to need to see the
following from you:

1) Change the default audit log level (subdomain properties) from
"significant" to "general information messages". This will log more
information from the link service. Then repro the problems with the new
settings.
2) Application Internal message, API, LU6.2 traces. We will need to see the
actual ATF files.
3) from the Diagnostic tool, click the IP-DLC tab and click status. It will
automatically save a file in your traces directory (this fires off the tool
to dump information about your ip-dlc link(s) installed on the box). No need
to enter a server name on this tab, it defaults to the local server.
4) Event logs (application and system) saved in EVT format. These are very
important, especially after doing #1 above. Word of warning: If you don't do
#1, then the event logs are useless and you will be asked to get them again
<vbg>.
5) Com.cfg file

If the above doesn't give us enough to go on, we would need additional
tracing on the link service. However, for IP-DLC this is in a different
format than other traces, so let's not worry about that for now. Event logs
and the output from qryipdlc.exe (using the diag tool as a front end in step
#3 above) should give us a good idea on what is wrong.

--
HTH,
Charles Ezzell
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Edgar Polanco" <poledg@hotmail.com> wrote in message
news:uqz6yx9wFHA.2792@tk2msftngp13.phx.gbl...

	Windows Server Forum Index -> Host Integration Server	All times are GMT Goto page 1, 2 Next
Page 1 of 2