|
|
|
date: Thu, 17 Jul 2008 15:31:37 -0700 (PDT),
group: microsoft.public.hiserver.general
back
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
Thanks Steve for your reply..
I can find out if they have multiple NIC's. It is a physical server,
but we are connecting (on Windows side) from a Virtual PC environment.
How do I verify if the EE accepts connection? Like is there a tool to
use.
On Jul 18, 12:29 am, "Steve Melan" wrote:
> Hi,
>
> I'd once the same warning event and in my case it was related to a wrong
> network configuration on the server side.
> Do you have multiple network cards in your server ? Is it a physical or a
> virtual server ?
> Have you already verified if the Enterprise Extender is accepting
> connections ?
>
> Steve
>
> "EssKay" wrote in message
>
> news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com...
>
>
>
> > Community folks,
> > Need some help very badly... Have been working on this issue for a
> > week now.
>
> > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > using IP-DLC through SNA Manager. I have followed the document [http://
> >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-.> > and have been able to setup everything till I try to start the 3270
> > Client from SNA Service->Connections->Test (created by the 3270
> > wizard). The SNA Service has a status of Active, but the connection I
> > created using the SNA Service->All tasks->3270 Wizard has a status of
> > [Pending] and then [Failed@some time].
> > The error I get from the event log is:
> > -------------------------
> > Event Type: Warning
> > Event Source: SNA IP-DLC Link Service
> > Event Category: Base
> > Event ID: 121
> > Date: 7/15/2008
> > Time: 4:56:41 PM
> > User: TESTSYS\User1
> > Computer: DevBizTalk
> > Description:
> > The attempt to start the link to Network Node Server 10.5.20.94
> > failed.
> > NNS link station: @N000001
> > Secondary return code: 0x13400000
>
> > Cause:
> > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > Node Server may be inactive, or an invalid NNS address may have been
> > configured for the link service.
>
> > Effect:
> > The IP-DLC link service will continue to attempt to connect to the
> > Network Node Server. If this fails, and no alternative NNS has been
> > configured, no connections will be able to start successfully.
>
> > Action:
> > Check that the Network Node Server address has been configured
> > correctly, that the NNS is active, and that it is reachable across the
> > IP network.
> > ---------------------------
>
> > I have no clue what could be wrong. I have used almost all the
> > diagnostics tool under SNA Manager->Tools to help me in
> > troubleshooting the problem. We have gone through the Verification
> > steps of the document and nothing makes sense to me.. Is there
> > anything that could be missing? I can provide the ipdlc log file if
> > anyone wants to have a look at it.
> > Thanks in advance.. True "GodSend" if you could help me..........- Hide quoted text -
>
> - Show quoted text -
date: Fri, 18 Jul 2008 06:55:06 -0700 (PDT)
author: EssKay
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
EssKay
I noted that you said you had used the Microsoft HIS "white paper"
"Configuring IP-DLC Link Service for IBM Enterprise Extender". I noted
some time ago that the advice given about VTAM in previous editions of
this "white paper" was suspect. I have now reviewed the important
sections of the "updated" edition and found the advice concerning VTAM
absolutely dreadful.
I have just created a review so I am prepared to back up that comment
to anyone who cares to challenge it. I will need some time to make it
portable and neater.
For now I will say that your VTAM person should review the VTAM
material and wherever he or she suspects that the "white paper" is
wrong or confusing, he/she will almost certainly be right and he/she
should follow his/her existing knowledge of the subjects of APPN, HPR,
Enterprise Extender and DLUR in VTAM rather than the "white paper".
The referenced redbook, "IBM - Enterprise Extender Implementation"
should be the best source for more or less reliable advice and samples
- but I guess I should make time to review this manual one day!
If your VTAM person needs more help I will send him/her the review -
even in the current rough state if it's all urgent - and answer any
questions preferably, for the sake of the archives, through the list -
as time permits.
Incidentally I am not at all surprised that, going by the advice in
the "white paper", you can't get it working.
Chris Mason
On Jul 18, 3:55 pm, EssKay wrote:
> Thanks Steve for your reply..
> I can find out if they have multiple NIC's. It is a physical server,
> but we are connecting (on Windows side) from a Virtual PC environment.
> How do I verify if the EE accepts connection? Like is there a tool to
> use.
>
> On Jul 18, 12:29 am, "Steve Melan" wrote:
>
>
>
> > Hi,
>
> > I'd once the same warning event and in my case it was related to a wrong
> > network configuration on the server side.
> > Do you have multiple network cards in your server ? Is it a physical or a
> > virtual server ?
> > Have you already verified if the Enterprise Extender is accepting
> > connections ?
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com..> > > Community folks,
> > > Need some help very badly... Have been working on this issue for a
> > > week now.
>
> > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390> > > using IP-DLC through SNA Manager. I have followed the document [http:> > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36> > > and have been able to setup everything till I try to start the 3270
> > > Client from SNA Service->Connections->Test (created by the 3270
> > > wizard). The SNA Service has a status of Active, but the connection I
> > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > [Pending] and then [Failed@some time].
> > > The error I get from the event log is:
> > > -------------------------
> > > Event Type: Warning
> > > Event Source: SNA IP-DLC Link Service
> > > Event Category: Base
> > > Event ID: 121
> > > Date: 7/15/2008
> > > Time: 4:56:41 PM
> > > User: TESTSYS\User1
> > > Computer: DevBizTalk
> > > Description:
> > > The attempt to start the link to Network Node Server 10.5.20.94
> > > failed.
> > > NNS link station: @N000001
> > > Secondary return code: 0x13400000
>
> > > Cause:
> > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > Node Server may be inactive, or an invalid NNS address may have been
> > > configured for the link service.
>
> > > Effect:
> > > The IP-DLC link service will continue to attempt to connect to the
> > > Network Node Server. If this fails, and no alternative NNS has been
> > > configured, no connections will be able to start successfully.
>
> > > Action:
> > > Check that the Network Node Server address has been configured
> > > correctly, that the NNS is active, and that it is reachable across the
> > > IP network.
> > > ---------------------------
>
> > > I have no clue what could be wrong. I have used almost all the
> > > diagnostics tool under SNA Manager->Tools to help me in
> > > troubleshooting the problem. We have gone through the Verification
> > > steps of the document and nothing makes sense to me.. Is there
> > > anything that could be missing? I can provide the ipdlc log file if
> > > anyone wants to have a look at it.
> > > Thanks in advance.. True "GodSend" if you could help me..........- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
date: Sun, 20 Jul 2008 16:47:07 -0700 (PDT)
author: Chris Mason
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
If you are using multiple NIC's, verify if the VLAN is the same for the
incoming and the same for the outgoing connections.
Are you using a NLB (Network Load Balancing) to connect to the server ?
To verify the connections from the Mainframe Side :
1. Go to ISPF
2. ULOG
3. /D NET,EE --> Verify that the EE is enabled
4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
get an IP address of the EE)
5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
If you receive on each case a correct answer, than the Mainframe Side is ok
and we have to investigate on the Windows Side.
If it's possible, can you provide me the Mainframe Displays of the commands
written above ?
Thank you in advance
Steve
"EssKay" wrote in message
news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com...
Thanks Steve for your reply..
I can find out if they have multiple NIC's. It is a physical server,
but we are connecting (on Windows side) from a Virtual PC environment.
How do I verify if the EE accepts connection? Like is there a tool to
use.
On Jul 18, 12:29 am, "Steve Melan" wrote:
> Hi,
>
> I'd once the same warning event and in my case it was related to a wrong
> network configuration on the server side.
> Do you have multiple network cards in your server ? Is it a physical or a
> virtual server ?
> Have you already verified if the Enterprise Extender is accepting
> connections ?
>
> Steve
>
> "EssKay" wrote in message
>
> news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com...
>
>
>
> > Community folks,
> > Need some help very badly... Have been working on this issue for a
> > week now.
>
> > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > using IP-DLC through SNA Manager. I have followed the document [http://
> >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > and have been able to setup everything till I try to start the 3270
> > Client from SNA Service->Connections->Test (created by the 3270
> > wizard). The SNA Service has a status of Active, but the connection I
> > created using the SNA Service->All tasks->3270 Wizard has a status of
> > [Pending] and then [Failed@some time].
> > The error I get from the event log is:
> > -------------------------
> > Event Type: Warning
> > Event Source: SNA IP-DLC Link Service
> > Event Category: Base
> > Event ID: 121
> > Date: 7/15/2008
> > Time: 4:56:41 PM
> > User: TESTSYS\User1
> > Computer: DevBizTalk
> > Description:
> > The attempt to start the link to Network Node Server 10.5.20.94
> > failed.
> > NNS link station: @N000001
> > Secondary return code: 0x13400000
>
> > Cause:
> > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > Node Server may be inactive, or an invalid NNS address may have been
> > configured for the link service.
>
> > Effect:
> > The IP-DLC link service will continue to attempt to connect to the
> > Network Node Server. If this fails, and no alternative NNS has been
> > configured, no connections will be able to start successfully.
>
> > Action:
> > Check that the Network Node Server address has been configured
> > correctly, that the NNS is active, and that it is reachable across the
> > IP network.
> > ---------------------------
>
> > I have no clue what could be wrong. I have used almost all the
> > diagnostics tool under SNA Manager->Tools to help me in
> > troubleshooting the problem. We have gone through the Verification
> > steps of the document and nothing makes sense to me.. Is there
> > anything that could be missing? I can provide the ipdlc log file if
> > anyone wants to have a look at it.
> > Thanks in advance.. True "GodSend" if you could help me..........- Hide
> > quoted text -
>
> - Show quoted text -
date: Mon, 21 Jul 2008 07:33:43 +0200
author: Steve Melan
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
Hi Chris,
I really appreciate your reply and cautioning the steps in the
whitepaper. It would be great if you can send me any information that
would help the VTAM folks to setup the connection. As I had mentioned
earlier, this is my third week with this issue and any quick response
is highly appreciated..
Thanks
On Jul 20, 6:47 pm, Chris Mason wrote:
> EssKay
>
> I noted that you said you had used the Microsoft HIS "white paper"
> "Configuring IP-DLC Link Service for IBM Enterprise Extender". I noted
> some time ago that the advice given about VTAM in previous editions of
> this "white paper" was suspect. I have now reviewed the important
> sections of the "updated" edition and found the advice concerning VTAM
> absolutely dreadful.
>
> I have just created a review so I am prepared to back up that comment
> to anyone who cares to challenge it. I will need some time to make it
> portable and neater.
>
> For now I will say that your VTAM person should review the VTAM
> material and wherever he or she suspects that the "white paper" is
> wrong or confusing, he/she will almost certainly be right and he/she
> should follow his/her existing knowledge of the subjects of APPN, HPR,
> Enterprise Extender and DLUR in VTAM rather than the "white paper".
>
> The referenced redbook, "IBM - Enterprise Extender Implementation"
> should be the best source for more or less reliable advice and samples
> - but I guess I should make time to review this manual one day!
>
> If your VTAM person needs more help I will send him/her the review -
> even in the current rough state if it's all urgent - and answer any
> questions preferably, for the sake of the archives, through the list -
> as time permits.
>
> Incidentally I am not at all surprised that, going by the advice in
> the "white paper", you can't get it working.
>
> Chris Mason
>
> On Jul 18, 3:55 pm, EssKay wrote:
>
>
>
> > Thanks Steve for your reply..
> > I can find out if they have multiple NIC's. It is a physical server,
> > but we are connecting (on Windows side) from a Virtual PC environment.
> > How do I verify if the EE accepts connection? Like is there a tool to
> > use.
>
> > On Jul 18, 12:29 am, "Steve Melan" wrote:
>
> > > Hi,
>
> > > I'd once the same warning event and in my case it was related to a wrong
> > > network configuration on the server side.
> > > Do you have multiple network cards in your server ? Is it a physical or a
> > > virtual server ?
> > > Have you already verified if the Enterprise Extender is accepting
> > > connections ?
>
> > > Steve
>
> > > "EssKay" wrote in message
>
> > >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com> > > > Community folks,
> > > > Need some help very badly... Have been working on this issue for a
> > > > week now.
>
> > > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > > > using IP-DLC through SNA Manager. I have followed the document [http://
> > > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > > and have been able to setup everything till I try to start the 3270
> > > > Client from SNA Service->Connections->Test (created by the 3270
> > > > wizard). The SNA Service has a status of Active, but the connection I
> > > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > > [Pending] and then [Failed@some time].
> > > > The error I get from the event log is:
> > > > -------------------------
> > > > Event Type: Warning
> > > > Event Source: SNA IP-DLC Link Service
> > > > Event Category: Base
> > > > Event ID: 121
> > > > Date: 7/15/2008
> > > > Time: 4:56:41 PM
> > > > User: TESTSYS\User1
> > > > Computer: DevBizTalk
> > > > Description:
> > > > The attempt to start the link to Network Node Server 10.5.20.94
> > > > failed.
> > > > NNS link station: @N000001
> > > > Secondary return code: 0x13400000
>
> > > > Cause:
> > > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > > Node Server may be inactive, or an invalid NNS address may have been
> > > > configured for the link service.
>
> > > > Effect:
> > > > The IP-DLC link service will continue to attempt to connect to the
> > > > Network Node Server. If this fails, and no alternative NNS has been
> > > > configured, no connections will be able to start successfully.
>
> > > > Action:
> > > > Check that the Network Node Server address has been configured
> > > > correctly, that the NNS is active, and that it is reachable across the
> > > > IP network.
> > > > ---------------------------
>
> > > > I have no clue what could be wrong. I have used almost all the
> > > > diagnostics tool under SNA Manager->Tools to help me in
> > > > troubleshooting the problem. We have gone through the Verification
> > > > steps of the document and nothing makes sense to me.. Is there
> > > > anything that could be missing? I can provide the ipdlc log file if
> > > > anyone wants to have a look at it.
> > > > Thanks in advance.. True "GodSend" if you could help me..........- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
Hi Chris,
I really appreciate your reply and cautioning the steps in the
whitepaper. It would be great if you can send me any information that
would help the VTAM folks to setup the connection. As I had mentioned
earlier, this is my third week with this issue and any quick response
is highly appreciated..
Thanks
date: Mon, 21 Jul 2008 08:38:02 -0700 (PDT)
author: EssKay
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
Hi Steve,
Thanks for your reply. I have asked the MF team to provide me the
screenshot for the command execution.
I shall provide them when I have it with me..
Thanks again!
On Jul 21, 12:33 am, "Steve Melan" wrote:
> If you are using multiple NIC's, verify if the VLAN is the same for the
> incoming and the same for the outgoing connections.
> Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> To verify the connections from the Mainframe Side :
> 1. Go to ISPF
> 2. ULOG
> 3. /D NET,EE --> Verify that the EE is enabled
> 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> get an IP address of the EE)
> 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> If you receive on each case a correct answer, than the Mainframe Side is ok
> and we have to investigate on the Windows Side.
>
> If it's possible, can you provide me the Mainframe Displays of the commands
> written above ?
>
> Thank you in advance
>
> Steve
>
> "EssKay" wrote in message
>
> news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com...
> Thanks Steve for your reply..
> I can find out if they have multiple NIC's. It is a physical server,
> but we are connecting (on Windows side) from a Virtual PC environment.
> How do I verify if the EE accepts connection? Like is there a tool to
> use.
>
> On Jul 18, 12:29 am, "Steve Melan" wrote:
>
>
>
> > Hi,
>
> > I'd once the same warning event and in my case it was related to a wrong
> > network configuration on the server side.
> > Do you have multiple network cards in your server ? Is it a physical or a
> > virtual server ?
> > Have you already verified if the Enterprise Extender is accepting
> > connections ?
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com..> > > Community folks,
> > > Need some help very badly... Have been working on this issue for a
> > > week now.
>
> > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390> > > using IP-DLC through SNA Manager. I have followed the document [http:> > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36> > > and have been able to setup everything till I try to start the 3270
> > > Client from SNA Service->Connections->Test (created by the 3270
> > > wizard). The SNA Service has a status of Active, but the connection I
> > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > [Pending] and then [Failed@some time].
> > > The error I get from the event log is:
> > > -------------------------
> > > Event Type: Warning
> > > Event Source: SNA IP-DLC Link Service
> > > Event Category: Base
> > > Event ID: 121
> > > Date: 7/15/2008
> > > Time: 4:56:41 PM
> > > User: TESTSYS\User1
> > > Computer: DevBizTalk
> > > Description:
> > > The attempt to start the link to Network Node Server 10.5.20.94
> > > failed.
> > > NNS link station: @N000001
> > > Secondary return code: 0x13400000
>
> > > Cause:
> > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > Node Server may be inactive, or an invalid NNS address may have been
> > > configured for the link service.
>
> > > Effect:
> > > The IP-DLC link service will continue to attempt to connect to the
> > > Network Node Server. If this fails, and no alternative NNS has been
> > > configured, no connections will be able to start successfully.
>
> > > Action:
> > > Check that the Network Node Server address has been configured
> > > correctly, that the NNS is active, and that it is reachable across the
> > > IP network.
> > > ---------------------------
>
> > > I have no clue what could be wrong. I have used almost all the
> > > diagnostics tool under SNA Manager->Tools to help me in
> > > troubleshooting the problem. We have gone through the Verification
> > > steps of the document and nothing makes sense to me.. Is there
> > > anything that could be missing? I can provide the ipdlc log file if
> > > anyone wants to have a look at it.
> > > Thanks in advance.. True "GodSend" if you could help me..........- Hide
> > > quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
date: Mon, 21 Jul 2008 08:39:16 -0700 (PDT)
author: EssKay
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
On Jul 21, 12:33 am, "Steve Melan" wrote:
> If you are using multiple NIC's, verify if the VLAN is the same for the
> incoming and the same for the outgoing connections.
> Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> To verify the connections from the Mainframe Side :
> 1. Go to ISPF
> 2. ULOG
> 3. /D NET,EE --> Verify that the EE is enabled
> 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> get an IP address of the EE)
> 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> If you receive on each case a correct answer, than the Mainframe Side is ok
> and we have to investigate on the Windows Side.
>
> If it's possible, can you provide me the Mainframe Displays of the commands
> written above ?
>
> Thank you in advance
>
> Steve
>
> "EssKay" wrote in message
>
> news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com...
> Thanks Steve for your reply..
> I can find out if they have multiple NIC's. It is a physical server,
> but we are connecting (on Windows side) from a Virtual PC environment.
> How do I verify if the EE accepts connection? Like is there a tool to
> use.
>
> On Jul 18, 12:29 am, "Steve Melan" wrote:
>
>
>
> > Hi,
>
> > I'd once the same warning event and in my case it was related to a wrong
> > network configuration on the server side.
> > Do you have multiple network cards in your server ? Is it a physical or a
> > virtual server ?
> > Have you already verified if the Enterprise Extender is accepting
> > connections ?
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com..> > > Community folks,
> > > Need some help very badly... Have been working on this issue for a
> > > week now.
>
> > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390> > > using IP-DLC through SNA Manager. I have followed the document [http:> > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36> > > and have been able to setup everything till I try to start the 3270
> > > Client from SNA Service->Connections->Test (created by the 3270
> > > wizard). The SNA Service has a status of Active, but the connection I
> > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > [Pending] and then [Failed@some time].
> > > The error I get from the event log is:
> > > -------------------------
> > > Event Type: Warning
> > > Event Source: SNA IP-DLC Link Service
> > > Event Category: Base
> > > Event ID: 121
> > > Date: 7/15/2008
> > > Time: 4:56:41 PM
> > > User: TESTSYS\User1
> > > Computer: DevBizTalk
> > > Description:
> > > The attempt to start the link to Network Node Server 10.5.20.94
> > > failed.
> > > NNS link station: @N000001
> > > Secondary return code: 0x13400000
>
> > > Cause:
> > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > Node Server may be inactive, or an invalid NNS address may have been
> > > configured for the link service.
>
> > > Effect:
> > > The IP-DLC link service will continue to attempt to connect to the
> > > Network Node Server. If this fails, and no alternative NNS has been
> > > configured, no connections will be able to start successfully.
>
> > > Action:
> > > Check that the Network Node Server address has been configured
> > > correctly, that the NNS is active, and that it is reachable across the
> > > IP network.
> > > ---------------------------
>
> > > I have no clue what could be wrong. I have used almost all the
> > > diagnostics tool under SNA Manager->Tools to help me in
> > > troubleshooting the problem. We have gone through the Verification
> > > steps of the document and nothing makes sense to me.. Is there
> > > anything that could be missing? I can provide the ipdlc log file if
> > > anyone wants to have a look at it.
> > > Thanks in advance.. True "GodSend" if you could help me..........- Hide
> > > quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
Below is the output of the command execution:
1. /D NET,EE
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = EE
IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
IST1685I TCP/IP JOB NAME = TCPIP
IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = EEXCAB1
IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
IST2005I IPRESOLV = 0
IST2231I CURRENT HPR CLOCK RATE = STANDARD
IST924I -------------------------------------------------------------
IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
IST2008I IPTOS VALUE = C0 C0 80 40 20
IST924I -------------------------------------------------------------
IST2017I TOTAL RTP PIPES = 0 LU-LU SESSIONS = 0
IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 0
IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
IST2021I TOTAL ACTIVE EE CONNECTIONS = 0
IST314I END
2. /D NET, ID= EEXCAB1,E
N03906 START DE PROCESSING COMPLETE. NCLID 015951
IST097I DISPLAY ACCEPTED
IST075I NAME = EEXCAB1 , TYPE = XCA MAJOR NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1679I MEDIUM = HPRIP
IST1685I TCP/IP JOB NAME = TCPIP
IST924I -------------------------------------------------------------
IST089I EEGROUP TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST089I EEGRIN TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST089I EEGROUT TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
IST170I LINES:
IST1901I LINES UNDER GROUP: EEGROUP
IST232I EEL000 ACTIV
IST232I EEL001 ACTIV
IST232I EEL002 ACTIV
IST232I EEL003 ACTIV
IST232I EEL004 ACTIV
3. /D NET,ID= SWDEVBTB,E
N03906 START DE PROCESSING COMPLETE. NCLID 015956
IST097I DISPLAY ACCEPTED
IST075I NAME = SWDEVBTB , TYPE = SW SNA MAJ NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
IST084I NETWORK RESOURCES:
IST089I DEVIPDLC TYPE = PU_T2 , CONCT
IST089I V1TST002 TYPE = LOGICAL UNIT , CONCT
IST089I V1TST003 TYPE = LOGICAL UNIT , CONCT
IST314I END
4. This is the output when we try to activate the node:
XCAE40EE VBUILD
TYPE=XCA
*THIS IS FOR TEST
XPE40EE PORT MEDIUM=HPRIP,
X
VNNAME=EEJEB,
X
VNGROUP=EEGRPJ,
X
LIVTIME=15,
X
SRQTIME=15,
X
SRQRETRY=9,
X
SAPADDR=04
*/
*
EEGRPJ GROUP ANSWER=ON,
X
AUTOGEN=(64,L,P),
X
CALL=INOUT,
X
DIAL=YES,
X
DYNPU=YES,
X
DYNPUPFX=$E,
X
ISTATUS=ACTIVE
HERE IS THE ERROR
act
XCAE40EE
IST097I VARY
ACCEPTED
IST1249I SYNTAX ERROR AT RECORD 4 IN MEMBER
XCAE40EE
IST258I STMT IN ERROR =
VNNAME=EEJEB,
IST314I
END
IST072I VARY ACT FOR ID = XCAE40EE FAILED DURING NETWORK DEFINITION
Let me know if you need any more information!
Thanks in advance for looking into it..
date: Mon, 21 Jul 2008 14:10:47 -0700 (PDT)
author: EssKay
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
Hello,
Do you get only this :
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
OR is the XX represented by values that you don't want to show to the
newsgroup because of security ?
You should get here an IP address which should be pinged over the network
!!!
VTAM : member sys1.vtamlst(XCAE40EE)
XCAE40EE VBUILD
TYPE=XCA
*THIS IS FOR TEST
XPE40EE PORT MEDIUM=HPRIP, X
LIVTIME=15, X
SAPADDR=4
*
EEGRPJ GROUP DIAL=YES, X
AUTOGEN=(010,D,R), X <<== Check with you
mainframe operator for these values
CALL=INOUT, X
DYNPU=YES, X
ISTATUS=ACTIVE
Try with this member the VARY again !
I hope this member will work for you.
I will help you to get through this !!!
If you need more quick response, I will give you my mail address !
Steve
"EssKay" wrote in message
news:edda0a21-77b8-4fe2-be77-dc1fac976d64@j22g2000hsf.googlegroups.com...
On Jul 21, 12:33 am, "Steve Melan" wrote:
> If you are using multiple NIC's, verify if the VLAN is the same for the
> incoming and the same for the outgoing connections.
> Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> To verify the connections from the Mainframe Side :
> 1. Go to ISPF
> 2. ULOG
> 3. /D NET,EE --> Verify that the EE is enabled
> 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> get an IP address of the EE)
> 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> If you receive on each case a correct answer, than the Mainframe Side is
> ok
> and we have to investigate on the Windows Side.
>
> If it's possible, can you provide me the Mainframe Displays of the
> commands
> written above ?
>
> Thank you in advance
>
> Steve
>
> "EssKay" wrote in message
>
> news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com...
> Thanks Steve for your reply..
> I can find out if they have multiple NIC's. It is a physical server,
> but we are connecting (on Windows side) from a Virtual PC environment.
> How do I verify if the EE accepts connection? Like is there a tool to
> use.
>
> On Jul 18, 12:29 am, "Steve Melan" wrote:
>
>
>
> > Hi,
>
> > I'd once the same warning event and in my case it was related to a wrong
> > network configuration on the server side.
> > Do you have multiple network cards in your server ? Is it a physical or
> > a
> > virtual server ?
> > Have you already verified if the Enterprise Extender is accepting
> > connections ?
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com...
>
> > > Community folks,
> > > Need some help very badly... Have been working on this issue for a
> > > week now.
>
> > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > > using IP-DLC through SNA Manager. I have followed the document
> > > [http://
> > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > and have been able to setup everything till I try to start the 3270
> > > Client from SNA Service->Connections->Test (created by the 3270
> > > wizard). The SNA Service has a status of Active, but the connection I
> > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > [Pending] and then [Failed@some time].
> > > The error I get from the event log is:
> > > -------------------------
> > > Event Type: Warning
> > > Event Source: SNA IP-DLC Link Service
> > > Event Category: Base
> > > Event ID: 121
> > > Date: 7/15/2008
> > > Time: 4:56:41 PM
> > > User: TESTSYS\User1
> > > Computer: DevBizTalk
> > > Description:
> > > The attempt to start the link to Network Node Server 10.5.20.94
> > > failed.
> > > NNS link station: @N000001
> > > Secondary return code: 0x13400000
>
> > > Cause:
> > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > Node Server may be inactive, or an invalid NNS address may have been
> > > configured for the link service.
>
> > > Effect:
> > > The IP-DLC link service will continue to attempt to connect to the
> > > Network Node Server. If this fails, and no alternative NNS has been
> > > configured, no connections will be able to start successfully.
>
> > > Action:
> > > Check that the Network Node Server address has been configured
> > > correctly, that the NNS is active, and that it is reachable across the
> > > IP network.
> > > ---------------------------
>
> > > I have no clue what could be wrong. I have used almost all the
> > > diagnostics tool under SNA Manager->Tools to help me in
> > > troubleshooting the problem. We have gone through the Verification
> > > steps of the document and nothing makes sense to me.. Is there
> > > anything that could be missing? I can provide the ipdlc log file if
> > > anyone wants to have a look at it.
> > > Thanks in advance.. True "GodSend" if you could help me..........-
> > > Hide
> > > quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
Below is the output of the command execution:
1. /D NET,EE
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = EE
IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
IST1685I TCP/IP JOB NAME = TCPIP
IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = EEXCAB1
IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
IST2005I IPRESOLV = 0
IST2231I CURRENT HPR CLOCK RATE = STANDARD
IST924I -------------------------------------------------------------
IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
IST2008I IPTOS VALUE = C0 C0 80 40 20
IST924I -------------------------------------------------------------
IST2017I TOTAL RTP PIPES = 0 LU-LU SESSIONS = 0
IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 0
IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
IST2021I TOTAL ACTIVE EE CONNECTIONS = 0
IST314I END
2. /D NET, ID= EEXCAB1,E
N03906 START DE PROCESSING COMPLETE. NCLID 015951
IST097I DISPLAY ACCEPTED
IST075I NAME = EEXCAB1 , TYPE = XCA MAJOR NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1679I MEDIUM = HPRIP
IST1685I TCP/IP JOB NAME = TCPIP
IST924I -------------------------------------------------------------
IST089I EEGROUP TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST089I EEGRIN TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST089I EEGROUT TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
IST170I LINES:
IST1901I LINES UNDER GROUP: EEGROUP
IST232I EEL000 ACTIV
IST232I EEL001 ACTIV
IST232I EEL002 ACTIV
IST232I EEL003 ACTIV
IST232I EEL004 ACTIV
3. /D NET,ID= SWDEVBTB,E
N03906 START DE PROCESSING COMPLETE. NCLID 015956
IST097I DISPLAY ACCEPTED
IST075I NAME = SWDEVBTB , TYPE = SW SNA MAJ NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
IST084I NETWORK RESOURCES:
IST089I DEVIPDLC TYPE = PU_T2 , CONCT
IST089I V1TST002 TYPE = LOGICAL UNIT , CONCT
IST089I V1TST003 TYPE = LOGICAL UNIT , CONCT
IST314I END
4. This is the output when we try to activate the node:
XCAE40EE VBUILD
TYPE=XCA
*THIS IS FOR TEST
XPE40EE PORT MEDIUM=HPRIP,
X
VNNAME=EEJEB,
X
VNGROUP=EEGRPJ,
X
LIVTIME=15,
X
SRQTIME=15,
X
SRQRETRY=9,
X
SAPADDR=04
*/
*
EEGRPJ GROUP ANSWER=ON,
X
AUTOGEN=(64,L,P),
X
CALL=INOUT,
X
DIAL=YES,
X
DYNPU=YES,
X
DYNPUPFX=$E,
X
ISTATUS=ACTIVE
HERE IS THE ERROR
act
XCAE40EE
IST097I VARY
ACCEPTED
IST1249I SYNTAX ERROR AT RECORD 4 IN MEMBER
XCAE40EE
IST258I STMT IN ERROR =
VNNAME=EEJEB,
IST314I
END
IST072I VARY ACT FOR ID = XCAE40EE FAILED DURING NETWORK DEFINITION
Let me know if you need any more information!
Thanks in advance for looking into it..
date: Tue, 22 Jul 2008 07:52:07 +0200
author: Steve Melan
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
EssKay
A quick response.
Are you sure that at least one of your "VTAM folk" is paying attention
to your problem?
You cannot expect anything to work until you manage to have any system
accept your definitions. VTAM is rejecting your XCF definition so it
is as if it didn't exist!!!
Rather than use the "white paper" for the VTAM side of the definitions
and the concepts involved with EE, you should use the referenced IBM
redbook. Please be aware that IBM redbooks are written using "field"
people even if they are (supposed to be) reviewed by developers so
they also cannot be guaranteed to be 100% accurate. The regular
manuals are the most reliable source but generally suffer from being
difficult to follow.
I'm away from the system where I prepared the review right now. I'll
be able to send it - spellchecked at least - next weekend if current
plans hold out. In any case your current problem is not related to the
problems I found in the "white paper". You and your VTAM help need
actually to understand the definitions you are trying to use - and
also how definitions are fed into VTAM!
Chris Mason
On Jul 21, 10:10 pm, EssKay wrote:
> On Jul 21, 12:33 am, "Steve Melan" wrote:
>
>
>
>
>
> > If you are using multiple NIC's, verify if the VLAN is the same for the
> > incoming and the same for the outgoing connections.
> > Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> > To verify the connections from the Mainframe Side :
> > 1. Go to ISPF
> > 2. ULOG
> > 3. /D NET,EE --> Verify that the EE is enabled
> > 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> > get an IP address of the EE)
> > 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> > If you receive on each case a correct answer, than the Mainframe Side is ok
> > and we have to investigate on the Windows Side.
>
> > If it's possible, can you provide me the Mainframe Displays of the commands
> > written above ?
>
> > Thank you in advance
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com..> > Thanks Steve for your reply..
> > I can find out if they have multiple NIC's. It is a physical server,
> > but we are connecting (on Windows side) from a Virtual PC environment.
> > How do I verify if the EE accepts connection? Like is there a tool to
> > use.
>
> > On Jul 18, 12:29 am, "Steve Melan" wrote:
>
> > > Hi,
>
> > > I'd once the same warning event and in my case it was related to a wrong
> > > network configuration on the server side.
> > > Do you have multiple network cards in your server ? Is it a physical or a
> > > virtual server ?
> > > Have you already verified if the Enterprise Extender is accepting
> > > connections ?
>
> > > Steve
>
> > > "EssKay" wrote in message
>
> > >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com> > > > Community folks,
> > > > Need some help very badly... Have been working on this issue for a
> > > > week now.
>
> > > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > > > using IP-DLC through SNA Manager. I have followed the document [http://
> > > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > > and have been able to setup everything till I try to start the 3270
> > > > Client from SNA Service->Connections->Test (created by the 3270
> > > > wizard). The SNA Service has a status of Active, but the connection I
> > > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > > [Pending] and then [Failed@some time].
> > > > The error I get from the event log is:
> > > > -------------------------
> > > > Event Type: Warning
> > > > Event Source: SNA IP-DLC Link Service
> > > > Event Category: Base
> > > > Event ID: 121
> > > > Date: 7/15/2008
> > > > Time: 4:56:41 PM
> > > > User: TESTSYS\User1
> > > > Computer: DevBizTalk
> > > > Description:
> > > > The attempt to start the link to Network Node Server 10.5.20.94
> > > > failed.
> > > > NNS link station: @N000001
> > > > Secondary return code: 0x13400000
>
> > > > Cause:
> > > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > > Node Server may be inactive, or an invalid NNS address may have been
> > > > configured for the link service.
>
> > > > Effect:
> > > > The IP-DLC link service will continue to attempt to connect to the
> > > > Network Node Server. If this fails, and no alternative NNS has been
> > > > configured, no connections will be able to start successfully.
>
> > > > Action:
> > > > Check that the Network Node Server address has been configured
> > > > correctly, that the NNS is active, and that it is reachable across the
> > > > IP network.
> > > > ---------------------------
>
> > > > I have no clue what could be wrong. I have used almost all the
> > > > diagnostics tool under SNA Manager->Tools to help me in
> > > > troubleshooting the problem. We have gone through the Verification
> > > > steps of the document and nothing makes sense to me.. Is there
> > > > anything that could be missing? I can provide the ipdlc log file if
> > > > anyone wants to have a look at it.
> > > > Thanks in advance.. True "GodSend" if you could help me..........- Hide
> > > > quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
>
> Below is the output of the command execution:
>
> 1. /D NET,EE
> IST097I DISPLAY ACCEPTED
> IST350I DISPLAY TYPE = EE
> IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
> IST1685I TCP/IP JOB NAME = TCPIP
> IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = EEXCAB1
> IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
> IST2005I IPRESOLV = 0
> IST2231I CURRENT HPR CLOCK RATE = STANDARD
> IST924I -------------------------------------------------------------
> IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
> IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
> IST2008I IPTOS VALUE = C0 C0 80 40 20
> IST924I -------------------------------------------------------------
> IST2017I TOTAL RTP PIPES = 0 LU-LU SESSIONS = 0
> IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 0
> IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
> IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
> IST2021I TOTAL ACTIVE EE CONNECTIONS = 0
> IST314I END
>
> 2. /D NET, ID= EEXCAB1,E
> N03906 START DE PROCESSING COMPLETE. NCLID 015951
> IST097I DISPLAY ACCEPTED
> IST075I NAME = EEXCAB1 , TYPE = XCA MAJOR NODE
> IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> IST1679I MEDIUM = HPRIP
> IST1685I TCP/IP JOB NAME = TCPIP
> IST924I -------------------------------------------------------------
> IST089I EEGROUP TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST089I EEGRIN TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST089I EEGROUT TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> IST170I LINES:
> IST1901I LINES UNDER GROUP: EEGROUP
> IST232I EEL000 ACTIV
> IST232I EEL001 ACTIV
> IST232I EEL002 ACTIV
> IST232I EEL003 ACTIV
> IST232I EEL004 ACTIV
>
> 3. /D NET,ID= SWDEVBTB,E
> N03906 START DE PROCESSING COMPLETE. NCLID 015956
> IST097I DISPLAY ACCEPTED
> IST075I NAME = SWDEVBTB , TYPE = SW SNA MAJ NODE
> IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> IST084I NETWORK RESOURCES:
> IST089I DEVIPDLC TYPE = PU_T2 , CONCT
> IST089I V1TST002 TYPE = LOGICAL UNIT , CONCT
> IST089I V1TST003 TYPE = LOGICAL UNIT , CONCT
> IST314I END
>
> 4. This is the output when we try to activate the node:
> XCAE40EE VBUILD
> TYPE=XCA
> *THIS IS FOR TEST
> XPE40EE PORT MEDIUM=HPRIP,
> X
> VNNAME=EEJEB,
> X
> VNGROUP=EEGRPJ,
> X
> LIVTIME=15,
> X
> SRQTIME=15,
> X
> SRQRETRY=9,
> X
> SAPADDR=04
> */
> *
> EEGRPJ GROUP ANSWER=ON,
> X
> AUTOGEN=(64,L,P),
> X
> CALL=INOUT,
> X
> DIAL=YES,
> X
> DYNPU=YES,
> X
> DYNPUPFX=$E,
> X
> ISTATUS=ACTIVE
>
> HERE IS THE ERROR
> act
> XCAE40EE
> IST097I VARY
> ACCEPTED
> IST1249I SYNTAX ERROR AT RECORD 4 IN MEMBER
> XCAE40EE
> IST258I STMT IN ERROR =
> VNNAME=EEJEB,
> IST314I
> END
> IST072I VARY ACT FOR ID = XCAE40EE FAILED DURING NETWORK DEFINITION
>
> Let me know if you need any more information!
>
> Thanks in advance for looking into it..- Hide quoted text -
>
> - Show quoted text -
date: Tue, 22 Jul 2008 01:56:44 -0700 (PDT)
author: unknown
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
EssKay
I decided I should have a closer look at the actual error. Unfortunately it
is a historical feature of VTAM that it follows IBM Assembler formatting
conventions.[1] Unfortunately also the newsgroup copy of your post does not
indicate whether or not you have been strict in placing your "continuation
punch"[2] in column 72. Since I can see no other problem with the way you
have coded your statements, I will leave it to you to be sure your
statements are correctly formatted. Until you sort that problem out, all
other possible infelicities are moot.
Looking at the output of your display commands, I'm a bit confused not only
because you seem to have some XCA nodes active already. Please show all of
your VTAM definitions relevant to EE including any individual start options
you suppose to be related, provide a short rationale for why each exists and
what it is supposed to be doing.
[1] Don't ask - although I could hazard a guess as to why VTAM decided on
this limitation for its definition statements back in the early '70s.
[2] 80-column punched card thinking, I'm afraid. Bill was still wearing
short trousers I expect when this approach was universal!
Chris Mason
"EssKay" wrote in message
news:edda0a21-77b8-4fe2-be77-dc1fac976d64@j22g2000hsf.googlegroups.com...
On Jul 21, 12:33 am, "Steve Melan" wrote:
> If you are using multiple NIC's, verify if the VLAN is the same for the
> incoming and the same for the outgoing connections.
> Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> To verify the connections from the Mainframe Side :
> 1. Go to ISPF
> 2. ULOG
> 3. /D NET,EE --> Verify that the EE is enabled
> 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> get an IP address of the EE)
> 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> If you receive on each case a correct answer, than the Mainframe Side is
> ok
> and we have to investigate on the Windows Side.
>
> If it's possible, can you provide me the Mainframe Displays of the
> commands
> written above ?
>
> Thank you in advance
>
> Steve
>
> "EssKay" wrote in message
>
> news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com...
> Thanks Steve for your reply..
> I can find out if they have multiple NIC's. It is a physical server,
> but we are connecting (on Windows side) from a Virtual PC environment.
> How do I verify if the EE accepts connection? Like is there a tool to
> use.
>
> On Jul 18, 12:29 am, "Steve Melan" wrote:
>
>
>
> > Hi,
>
> > I'd once the same warning event and in my case it was related to a wrong
> > network configuration on the server side.
> > Do you have multiple network cards in your server ? Is it a physical or
> > a
> > virtual server ?
> > Have you already verified if the Enterprise Extender is accepting
> > connections ?
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com...
>
> > > Community folks,
> > > Need some help very badly... Have been working on this issue for a
> > > week now.
>
> > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > > using IP-DLC through SNA Manager. I have followed the document
> > > [http://
> > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > and have been able to setup everything till I try to start the 3270
> > > Client from SNA Service->Connections->Test (created by the 3270
> > > wizard). The SNA Service has a status of Active, but the connection I
> > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > [Pending] and then [Failed@some time].
> > > The error I get from the event log is:
> > > -------------------------
> > > Event Type: Warning
> > > Event Source: SNA IP-DLC Link Service
> > > Event Category: Base
> > > Event ID: 121
> > > Date: 7/15/2008
> > > Time: 4:56:41 PM
> > > User: TESTSYS\User1
> > > Computer: DevBizTalk
> > > Description:
> > > The attempt to start the link to Network Node Server 10.5.20.94
> > > failed.
> > > NNS link station: @N000001
> > > Secondary return code: 0x13400000
>
> > > Cause:
> > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > Node Server may be inactive, or an invalid NNS address may have been
> > > configured for the link service.
>
> > > Effect:
> > > The IP-DLC link service will continue to attempt to connect to the
> > > Network Node Server. If this fails, and no alternative NNS has been
> > > configured, no connections will be able to start successfully.
>
> > > Action:
> > > Check that the Network Node Server address has been configured
> > > correctly, that the NNS is active, and that it is reachable across the
> > > IP network.
> > > ---------------------------
>
> > > I have no clue what could be wrong. I have used almost all the
> > > diagnostics tool under SNA Manager->Tools to help me in
> > > troubleshooting the problem. We have gone through the Verification
> > > steps of the document and nothing makes sense to me.. Is there
> > > anything that could be missing? I can provide the ipdlc log file if
> > > anyone wants to have a look at it.
> > > Thanks in advance.. True "GodSend" if you could help me..........-
> > > Hide
> > > quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
Below is the output of the command execution:
1. /D NET,EE
IST097I DISPLAY ACCEPTED
IST350I DISPLAY TYPE = EE
IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
IST1685I TCP/IP JOB NAME = TCPIP
IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = EEXCAB1
IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
IST2005I IPRESOLV = 0
IST2231I CURRENT HPR CLOCK RATE = STANDARD
IST924I -------------------------------------------------------------
IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
IST2008I IPTOS VALUE = C0 C0 80 40 20
IST924I -------------------------------------------------------------
IST2017I TOTAL RTP PIPES = 0 LU-LU SESSIONS = 0
IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 0
IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
IST2021I TOTAL ACTIVE EE CONNECTIONS = 0
IST314I END
2. /D NET, ID= EEXCAB1,E
N03906 START DE PROCESSING COMPLETE. NCLID 015951
IST097I DISPLAY ACCEPTED
IST075I NAME = EEXCAB1 , TYPE = XCA MAJOR NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1679I MEDIUM = HPRIP
IST1685I TCP/IP JOB NAME = TCPIP
IST924I -------------------------------------------------------------
IST089I EEGROUP TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST089I EEGRIN TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST089I EEGROUT TYPE = LINE GROUP , ACTIV
IST1680I LOCAL IP ADDRESS
XX.XX.XX.XX
IST924I -------------------------------------------------------------
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
IST170I LINES:
IST1901I LINES UNDER GROUP: EEGROUP
IST232I EEL000 ACTIV
IST232I EEL001 ACTIV
IST232I EEL002 ACTIV
IST232I EEL003 ACTIV
IST232I EEL004 ACTIV
3. /D NET,ID= SWDEVBTB,E
N03906 START DE PROCESSING COMPLETE. NCLID 015956
IST097I DISPLAY ACCEPTED
IST075I NAME = SWDEVBTB , TYPE = SW SNA MAJ NODE
IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
IST084I NETWORK RESOURCES:
IST089I DEVIPDLC TYPE = PU_T2 , CONCT
IST089I V1TST002 TYPE = LOGICAL UNIT , CONCT
IST089I V1TST003 TYPE = LOGICAL UNIT , CONCT
IST314I END
4. This is the output when we try to activate the node:
XCAE40EE VBUILD
TYPE=XCA
*THIS IS FOR TEST
XPE40EE PORT MEDIUM=HPRIP,
X
VNNAME=EEJEB,
X
VNGROUP=EEGRPJ,
X
LIVTIME=15,
X
SRQTIME=15,
X
SRQRETRY=9,
X
SAPADDR=04
*/
*
EEGRPJ GROUP ANSWER=ON,
X
AUTOGEN=(64,L,P),
X
CALL=INOUT,
X
DIAL=YES,
X
DYNPU=YES,
X
DYNPUPFX=$E,
X
ISTATUS=ACTIVE
HERE IS THE ERROR
act
XCAE40EE
IST097I VARY
ACCEPTED
IST1249I SYNTAX ERROR AT RECORD 4 IN MEMBER
XCAE40EE
IST258I STMT IN ERROR =
VNNAME=EEJEB,
IST314I
END
IST072I VARY ACT FOR ID = XCAE40EE FAILED DURING NETWORK DEFINITION
Let me know if you need any more information!
Thanks in advance for looking into it..
date: Tue, 22 Jul 2008 16:19:07 +0100
author: Chris Mason
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
On Jul 22, 12:52 am, "Steve Melan" wrote:
> Hello,
>
> Do you get only this :
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
>
> OR is the XX represented by values that you don't want to show to the
> newsgroup because of security ?
> You should get here an IP address which should be pinged over the network
> !!!
>
> VTAM : member sys1.vtamlst(XCAE40EE)
> XCAE40EE VBUILD
> TYPE=XCA
> *THIS IS FOR TEST
> XPE40EE PORT MEDIUM=HPRIP, X
> LIVTIME=15, X
> SAPADDR=4
>
> *
> EEGRPJ GROUP DIAL=YES, X
> AUTOGEN=(010,D,R), X <<== Check with you
> mainframe operator for these values
> CALL=INOUT, X
> DYNPU=YES, X
> ISTATUS=ACTIVE
>
> Try with this member the VARY again !
>
> I hope this member will work for you.
>
> I will help you to get through this !!!
>
> If you need more quick response, I will give you my mail address !
>
> Steve
>
> "EssKay" wrote in message
>
> news:edda0a21-77b8-4fe2-be77-dc1fac976d64@j22g2000hsf.googlegroups.com...
> On Jul 21, 12:33 am, "Steve Melan" wrote:
>
>
>
>
>
> > If you are using multiple NIC's, verify if the VLAN is the same for the
> > incoming and the same for the outgoing connections.
> > Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> > To verify the connections from the Mainframe Side :
> > 1. Go to ISPF
> > 2. ULOG
> > 3. /D NET,EE --> Verify that the EE is enabled
> > 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> > get an IP address of the EE)
> > 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> > If you receive on each case a correct answer, than the Mainframe Side is
> > ok
> > and we have to investigate on the Windows Side.
>
> > If it's possible, can you provide me the Mainframe Displays of the
> > commands
> > written above ?
>
> > Thank you in advance
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com..> > Thanks Steve for your reply..
> > I can find out if they have multiple NIC's. It is a physical server,
> > but we are connecting (on Windows side) from a Virtual PC environment.
> > How do I verify if the EE accepts connection? Like is there a tool to
> > use.
>
> > On Jul 18, 12:29 am, "Steve Melan" wrote:
>
> > > Hi,
>
> > > I'd once the same warning event and in my case it was related to a wrong
> > > network configuration on the server side.
> > > Do you have multiple network cards in your server ? Is it a physical or
> > > a
> > > virtual server ?
> > > Have you already verified if the Enterprise Extender is accepting
> > > connections ?
>
> > > Steve
>
> > > "EssKay" wrote in message
>
> > >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com> > > > Community folks,
> > > > Need some help very badly... Have been working on this issue for a
> > > > week now.
>
> > > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > > > using IP-DLC through SNA Manager. I have followed the document
> > > > [http://
> > > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > > and have been able to setup everything till I try to start the 3270
> > > > Client from SNA Service->Connections->Test (created by the 3270
> > > > wizard). The SNA Service has a status of Active, but the connection I
> > > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > > [Pending] and then [Failed@some time].
> > > > The error I get from the event log is:
> > > > -------------------------
> > > > Event Type: Warning
> > > > Event Source: SNA IP-DLC Link Service
> > > > Event Category: Base
> > > > Event ID: 121
> > > > Date: 7/15/2008
> > > > Time: 4:56:41 PM
> > > > User: TESTSYS\User1
> > > > Computer: DevBizTalk
> > > > Description:
> > > > The attempt to start the link to Network Node Server 10.5.20.94
> > > > failed.
> > > > NNS link station: @N000001
> > > > Secondary return code: 0x13400000
>
> > > > Cause:
> > > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > > Node Server may be inactive, or an invalid NNS address may have been
> > > > configured for the link service.
>
> > > > Effect:
> > > > The IP-DLC link service will continue to attempt to connect to the
> > > > Network Node Server. If this fails, and no alternative NNS has been
> > > > configured, no connections will be able to start successfully.
>
> > > > Action:
> > > > Check that the Network Node Server address has been configured
> > > > correctly, that the NNS is active, and that it is reachable across the
> > > > IP network.
> > > > ---------------------------
>
> > > > I have no clue what could be wrong. I have used almost all the
> > > > diagnostics tool under SNA Manager->Tools to help me in
> > > > troubleshooting the problem. We have gone through the Verification
> > > > steps of the document and nothing makes sense to me.. Is there
> > > > anything that could be missing? I can provide the ipdlc log file if
> > > > anyone wants to have a look at it.
> > > > Thanks in advance.. True "GodSend" if you could help me..........-
> > > > Hide
> > > > quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
>
> Below is the output of the command execution:
>
> 1. /D NET,EE
> IST097I DISPLAY ACCEPTED
> IST350I DISPLAY TYPE = EE
> IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
> IST1685I TCP/IP JOB NAME = TCPIP
> IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = EEXCAB1
> IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
> IST2005I IPRESOLV = 0
> IST2231I CURRENT HPR CLOCK RATE = STANDARD
> IST924I -------------------------------------------------------------
> IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
> IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
> IST2008I IPTOS VALUE = C0 C0 80 40 20
> IST924I -------------------------------------------------------------
> IST2017I TOTAL RTP PIPES = 0 LU-LU SESSIONS = 0
> IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 0
> IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
> IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
> IST2021I TOTAL ACTIVE EE CONNECTIONS = 0
> IST314I END
>
> 2. /D NET, ID= EEXCAB1,E
> N03906 START DE PROCESSING COMPLETE. NCLID 015951
> IST097I DISPLAY ACCEPTED
> IST075I NAME = EEXCAB1 , TYPE = XCA MAJOR NODE
> IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> IST1679I MEDIUM = HPRIP
> IST1685I TCP/IP JOB NAME = TCPIP
> IST924I -------------------------------------------------------------
> IST089I EEGROUP TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST089I EEGRIN TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST089I EEGROUT TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> IST170I LINES:
> IST1901I LINES UNDER GROUP: EEGROUP
> IST232I EEL000 ACTIV
> IST232I EEL001 ACTIV
> IST232I EEL002 ACTIV
> IST232I EEL003 ACTIV
> IST232I EEL004 ACTIV
>
> 3. /D NET,ID= SWDEVBTB,E
> N03906 START DE PROCESSING COMPLETE. NCLID 015956
> IST097I DISPLAY ACCEPTED
> IST075I NAME = SWDEVBTB , TYPE = SW SNA MAJ NODE
> IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> IST084I NETWORK RESOURCES:
> IST089I DEVIPDLC TYPE = PU_T2 , CONCT
> IST089I V1TST002 TYPE = LOGICAL UNIT , CONCT
> IST089I V1TST003 TYPE = LOGICAL UNIT , CONCT
> IST314I END
>
> 4. This is the output when we try to activate the node:
> XCAE40EE VBUILD
> TYPE=XCA
> *THIS IS FOR TEST
> XPE40EE PORT MEDIUM=HPRIP,
> X
> VNNAME=EEJEB,
> X
> VNGROUP=EEGRPJ,
> X
> LIVTIME=15,
> X
> SRQTIME=15,
> X
> SRQRETRY=9,
> X
> SAPADDR=04
> */
> *
> EEGRPJ GROUP ANSWER=ON,
> X
> AUTOGEN=(64,L,P),
> X
> CALL=INOUT,
> X
> DIAL=YES,
> X
> DYNPU=YES,
> X
> DYNPUPFX=$E,
> X
> ISTATUS=ACTIVE
>
> HERE IS THE ERROR
> act
> XCAE40EE
> IST097I VARY
> ACCEPTED
> IST1249I SYNTAX ERROR AT RECORD 4 IN MEMBER
> XCAE40EE
> IST258I STMT IN ERROR =
> VNNAME=EEJEB,
> IST314I
> END
> IST072I VARY ACT FOR ID = XCAE40EE FAILED DURING NETWORK DEFINITION
>
> Let me know if you need any more information!
>
> Thanks in advance for looking into it..- Hide quoted text -
>
> - Show quoted text -
Hello Steve:
Sorry for the delay. I have asked the mainframe folks to look into as
I have dont have a deeper knowledge on the MF side.. I am reading the
redbook and trying to figure out as much as I can.. BTW, those ip
address have been masked for security purpose..
Do you have a sample VTAM definition to set this up that you could
send to me? I mean whatever basic/necessary information it takes to
setup the connectivity.
Thanks again!
date: Wed, 23 Jul 2008 14:57:47 -0700 (PDT)
author: EssKay
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
On Jul 22, 3:56 am, christopher.john.ma...@gmail.com wrote:
> EssKay
>
> A quick response.
>
> Are you sure that at least one of your "VTAM folk" is paying attention
> to your problem?
>
> You cannot expect anything to work until you manage to have any system
> accept your definitions. VTAM is rejecting your XCF definition so it
> is as if it didn't exist!!!
>
> Rather than use the "white paper" for the VTAM side of the definitions
> and the concepts involved with EE, you should use the referenced IBM
> redbook. Please be aware that IBM redbooks are written using "field"
> people even if they are (supposed to be) reviewed by developers so
> they also cannot be guaranteed to be 100% accurate. The regular
> manuals are the most reliable source but generally suffer from being
> difficult to follow.
>
> I'm away from the system where I prepared the review right now. I'll
> be able to send it - spellchecked at least - next weekend if current
> plans hold out. In any case your current problem is not related to the
> problems I found in the "white paper". You and your VTAM help need
> actually to understand the definitions you are trying to use - and
> also how definitions are fed into VTAM!
>
> Chris Mason
>
> On Jul 21, 10:10 pm, EssKay wrote:
>
>
>
> > On Jul 21, 12:33 am, "Steve Melan" wrote:
>
> > > If you are using multiple NIC's, verify if the VLAN is the same for the
> > > incoming and the same for the outgoing connections.
> > > Are you using a NLB (Network Load Balancing) to connect to the server> > > To verify the connections from the Mainframe Side :
> > > 1. Go to ISPF
> > > 2. ULOG
> > > 3. /D NET,EE --> Verify that the EE is enabled
> > > 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> > > get an IP address of the EE)
> > > 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> > > If you receive on each case a correct answer, than the Mainframe Side is ok
> > > and we have to investigate on the Windows Side.
>
> > > If it's possible, can you provide me the Mainframe Displays of the commands
> > > written above ?
>
> > > Thank you in advance
>
> > > Steve
>
> > > "EssKay" wrote in message
>
> > >news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com> > > Thanks Steve for your reply..
> > > I can find out if they have multiple NIC's. It is a physical server,
> > > but we are connecting (on Windows side) from a Virtual PC environment> > > How do I verify if the EE accepts connection? Like is there a tool to
> > > use.
>
> > > On Jul 18, 12:29 am, "Steve Melan" wrote:
>
> > > > Hi,
>
> > > > I'd once the same warning event and in my case it was related to a wrong
> > > > network configuration on the server side.
> > > > Do you have multiple network cards in your server ? Is it a physical or a
> > > > virtual server ?
> > > > Have you already verified if the Enterprise Extender is accepting
> > > > connections ?
>
> > > > Steve
>
> > > > "EssKay" wrote in message
>
> > > >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com...
>
> > > > > Community folks,
> > > > > Need some help very badly... Have been working on this issue for a
> > > > > week now.
>
> > > > > Trying to attain connectivity between HIS 2006 and IBM Mainframe (390)
> > > > > using IP-DLC through SNA Manager. I have followed the document [http://
> > > > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > > > and have been able to setup everything till I try to start the 3270
> > > > > Client from SNA Service->Connections->Test (created by the 3270
> > > > > wizard). The SNA Service has a status of Active, but the connection I
> > > > > created using the SNA Service->All tasks->3270 Wizard has a status of
> > > > > [Pending] and then [Failed@some time].
> > > > > The error I get from the event log is:
> > > > > -------------------------
> > > > > Event Type: Warning
> > > > > Event Source: SNA IP-DLC Link Service
> > > > > Event Category: Base
> > > > > Event ID: 121
> > > > > Date: 7/15/2008
> > > > > Time: 4:56:41 PM
> > > > > User: TESTSYS\User1
> > > > > Computer: DevBizTalk
> > > > > Description:
> > > > > The attempt to start the link to Network Node Server 10.5.20.94
> > > > > failed.
> > > > > NNS link station: @N000001
> > > > > Secondary return code: 0x13400000
>
> > > > > Cause:
> > > > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > > > Node Server may be inactive, or an invalid NNS address may have been
> > > > > configured for the link service.
>
> > > > > Effect:
> > > > > The IP-DLC link service will continue to attempt to connect to the
> > > > > Network Node Server. If this fails, and no alternative NNS has been
> > > > > configured, no connections will be able to start successfully.
>
> > > > > Action:
> > > > > Check that the Network Node Server address has been configured
> > > > > correctly, that the NNS is active, and that it is reachable across the
> > > > > IP network.
> > > > > ---------------------------
>
> > > > > I have no clue what could be wrong. I have used almost all the
> > > > > diagnostics tool under SNA Manager->Tools to help me in
> > > > > troubleshooting the problem. We have gone through the Verification
> > > > > steps of the document and nothing makes sense to me.. Is there
> > > > > anything that could be missing? I can provide the ipdlc log file if
> > > > > anyone wants to have a look at it.
> > > > > Thanks in advance.. True "GodSend" if you could help me..........- Hide
> > > > > quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -
>
> > Below is the output of the command execution:
>
> > 1. /D NET,EE
> > IST097I DISPLAY ACCEPTED
> > IST350I DISPLAY TYPE = EE
> > IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
> > IST1685I TCP/IP JOB NAME = TCPIP
> > IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = EEXCAB1
> > IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
> > IST2005I IPRESOLV = 0
> > IST2231I CURRENT HPR CLOCK RATE = STANDARD
> > IST924I ------------------------------------------------------------> > IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
> > IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
> > IST2008I IPTOS VALUE = C0 C0 80 40 20
> > IST924I ------------------------------------------------------------> > IST2017I TOTAL RTP PIPES = 0 LU-LU SESSIONS = 0
> > IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 0
> > IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
> > IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
> > IST2021I TOTAL ACTIVE EE CONNECTIONS = 0
> > IST314I END
>
> > 2. /D NET, ID= EEXCAB1,E
> > N03906 START DE PROCESSING COMPLETE. NCLID 015951
> > IST097I DISPLAY ACCEPTED
> > IST075I NAME = EEXCAB1 , TYPE = XCA MAJOR NODE
> > IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> > IST1679I MEDIUM = HPRIP
> > IST1685I TCP/IP JOB NAME = TCPIP
> > IST924I ------------------------------------------------------------> > IST089I EEGROUP TYPE = LINE GROUP , ACTIV
> > IST1680I LOCAL IP ADDRESS
> > XX.XX.XX.XX
> > IST924I ------------------------------------------------------------> > IST089I EEGRIN TYPE = LINE GROUP , ACTIV
> > IST1680I LOCAL IP ADDRESS
> > XX.XX.XX.XX
> > IST924I ------------------------------------------------------------> > IST089I EEGROUT TYPE = LINE GROUP , ACTIV
> > IST1680I LOCAL IP ADDRESS
> > XX.XX.XX.XX
> > IST924I ------------------------------------------------------------> > IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> > IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> > IST170I LINES:
> > IST1901I LINES UNDER GROUP: EEGROUP
> > IST232I EEL000 ACTIV
> > IST232I EEL001 ACTIV
> > IST232I EEL002 ACTIV
> > IST232I EEL003 ACTIV
> > IST232I EEL004 ACTIV
>
> > 3. /D NET,ID= SWDEVBTB,E
> > N03906 START DE PROCESSING COMPLETE. NCLID 015956
> > IST097I DISPLAY ACCEPTED
> > IST075I NAME = SWDEVBTB , TYPE = SW SNA MAJ NODE
> > IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> > IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> > IST084I NETWORK RESOURCES:
> > IST089I DEVIPDLC TYPE = PU_T2 , CONCT
> > IST089I V1TST002 TYPE = LOGICAL UNIT , CONCT
> > IST089I V1TST003 TYPE = LOGICAL UNIT , CONCT
> > IST314I END
>
> > 4. This is the output when we try to activate the node:
> > XCAE40EE VBUILD
> > TYPE=XCA
> > *THIS IS FOR TEST
> > XPE40EE PORT MEDIUM=HPRIP,
> > X
> > VNNAME=EEJEB,
> > X
> > VNGROUP=EEGRPJ,
> > X
> > LIVTIME=15,
> > X
> > SRQTIME=15,
> > X
> > SRQRETRY=9,
> > X
> > SAPADDR=04
> > */
> > *
> > EEGRPJ GROUP ANSWER=ON,
> > X
> > AUTOGEN=(64,L,P),
> > X
> > CALL=INOUT,
> > X
> > DIAL=YES,
> > X
> > DYNPU=YES,
> > X
> > DYNPUPFX=$E,
> > X
> > ISTATUS=ACTIVE
>
> > HERE IS THE ERROR
> > act
> > XCAE40EE
> > IST097I VARY
> > ACCEPTED
> > IST1249I SYNTAX ERROR AT RECORD 4 IN MEMBER
> > XCAE40EE
> > IST258I STMT IN ERROR =
> > VNNAME=EEJEB,
> > IST314I
> > END
> > IST072I VARY ACT FOR ID = XCAE40EE FAILED DURING NETWORK DEFINITION
>
> > Let me know if you need any more information!
>
> > Thanks in advance for looking into it..- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
Hi Chris:
Thanks for the reply.. Honestly, the VTAM folks are also new to setup
something like this in the EE.. So as you said, we are going through
the redbook implementation guide to get a better understanding..
Meanwhile, whenever you have the basic steps ready, please send it
over. (a non spellchecked version is also fine ;-)..
date: Wed, 23 Jul 2008 15:03:03 -0700 (PDT)
author: EssKay
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
Hi,
Please pay attention implementing a VTAM defintion, the position of the X
matters !!!!
Enterprise Extender Defintion
XCAEEb VBUILD TYPE=XCA
*
PORXCA0 PORT MEDIUM=HPRIP, PORT aa X
LIVTIME=10,
X
SAPADDR=4
*
GRPEEb GROUP DIAL=YES, X
AUTOGEN=(010,D,R), X
CALL=INPUT, X
DYNPU=YES, X
ISTATUS=ACTIVE
Replace:
aa = connection via CUADDR, access mode enterprise extender
b = logical line name prefix (mainframe partition)
Do you only want to use the HIS for Emulation3270 or something else ?
In that case, I can provide you with everything you need to setup your
mainframe!
Steve
"EssKay" wrote in message
news:2e05138d-ed85-40cd-977d-b12861ee4094@b1g2000hsg.googlegroups.com...
On Jul 22, 12:52 am, "Steve Melan" wrote:
> Hello,
>
> Do you get only this :
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
>
> OR is the XX represented by values that you don't want to show to the
> newsgroup because of security ?
> You should get here an IP address which should be pinged over the network
> !!!
>
> VTAM : member sys1.vtamlst(XCAE40EE)
> XCAE40EE VBUILD
> TYPE=XCA
> *THIS IS FOR TEST
> XPE40EE PORT MEDIUM=HPRIP, X
> LIVTIME=15, X
> SAPADDR=4
>
> *
> EEGRPJ GROUP DIAL=YES, X
> AUTOGEN=(010,D,R), X <<== Check with you
> mainframe operator for these values
> CALL=INOUT, X
> DYNPU=YES, X
> ISTATUS=ACTIVE
>
> Try with this member the VARY again !
>
> I hope this member will work for you.
>
> I will help you to get through this !!!
>
> If you need more quick response, I will give you my mail address !
>
> Steve
>
> "EssKay" wrote in message
>
> news:edda0a21-77b8-4fe2-be77-dc1fac976d64@j22g2000hsf.googlegroups.com...
> On Jul 21, 12:33 am, "Steve Melan" wrote:
>
>
>
>
>
> > If you are using multiple NIC's, verify if the VLAN is the same for the
> > incoming and the same for the outgoing connections.
> > Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> > To verify the connections from the Mainframe Side :
> > 1. Go to ISPF
> > 2. ULOG
> > 3. /D NET,EE --> Verify that the EE is enabled
> > 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> > get an IP address of the EE)
> > 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> > If you receive on each case a correct answer, than the Mainframe Side is
> > ok
> > and we have to investigate on the Windows Side.
>
> > If it's possible, can you provide me the Mainframe Displays of the
> > commands
> > written above ?
>
> > Thank you in advance
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com...
> > Thanks Steve for your reply..
> > I can find out if they have multiple NIC's. It is a physical server,
> > but we are connecting (on Windows side) from a Virtual PC environment.
> > How do I verify if the EE accepts connection? Like is there a tool to
> > use.
>
> > On Jul 18, 12:29 am, "Steve Melan" wrote:
>
> > > Hi,
>
> > > I'd once the same warning event and in my case it was related to a
> > > wrong
> > > network configuration on the server side.
> > > Do you have multiple network cards in your server ? Is it a physical
> > > or
> > > a
> > > virtual server ?
> > > Have you already verified if the Enterprise Extender is accepting
> > > connections ?
>
> > > Steve
>
> > > "EssKay" wrote in message
>
> > >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com...
>
> > > > Community folks,
> > > > Need some help very badly... Have been working on this issue for a
> > > > week now.
>
> > > > Trying to attain connectivity between HIS 2006 and IBM Mainframe
> > > > (390)
> > > > using IP-DLC through SNA Manager. I have followed the document
> > > > [http://
> > > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > > and have been able to setup everything till I try to start the 3270
> > > > Client from SNA Service->Connections->Test (created by the 3270
> > > > wizard). The SNA Service has a status of Active, but the connection
> > > > I
> > > > created using the SNA Service->All tasks->3270 Wizard has a status
> > > > of
> > > > [Pending] and then [Failed@some time].
> > > > The error I get from the event log is:
> > > > -------------------------
> > > > Event Type: Warning
> > > > Event Source: SNA IP-DLC Link Service
> > > > Event Category: Base
> > > > Event ID: 121
> > > > Date: 7/15/2008
> > > > Time: 4:56:41 PM
> > > > User: TESTSYS\User1
> > > > Computer: DevBizTalk
> > > > Description:
> > > > The attempt to start the link to Network Node Server 10.5.20.94
> > > > failed.
> > > > NNS link station: @N000001
> > > > Secondary return code: 0x13400000
>
> > > > Cause:
> > > > An LS_FAILURE was returned from a START_LS NOF verb. The Network
> > > > Node Server may be inactive, or an invalid NNS address may have been
> > > > configured for the link service.
>
> > > > Effect:
> > > > The IP-DLC link service will continue to attempt to connect to the
> > > > Network Node Server. If this fails, and no alternative NNS has been
> > > > configured, no connections will be able to start successfully.
>
> > > > Action:
> > > > Check that the Network Node Server address has been configured
> > > > correctly, that the NNS is active, and that it is reachable across
> > > > the
> > > > IP network.
> > > > ---------------------------
>
> > > > I have no clue what could be wrong. I have used almost all the
> > > > diagnostics tool under SNA Manager->Tools to help me in
> > > > troubleshooting the problem. We have gone through the Verification
> > > > steps of the document and nothing makes sense to me.. Is there
> > > > anything that could be missing? I can provide the ipdlc log file if
> > > > anyone wants to have a look at it.
> > > > Thanks in advance.. True "GodSend" if you could help me..........-
> > > > Hide
> > > > quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -
>
> Below is the output of the command execution:
>
> 1. /D NET,EE
> IST097I DISPLAY ACCEPTED
> IST350I DISPLAY TYPE = EE
> IST2000I ENTERPRISE EXTENDER GENERAL INFORMATION
> IST1685I TCP/IP JOB NAME = TCPIP
> IST2003I ENTERPRISE EXTENDER XCA MAJOR NODE NAME = EEXCAB1
> IST2004I LIVTIME = (10,0) SRQTIME = 15 SRQRETRY = 3
> IST2005I IPRESOLV = 0
> IST2231I CURRENT HPR CLOCK RATE = STANDARD
> IST924I -------------------------------------------------------------
> IST2006I PORT PRIORITY = SIGNAL NETWORK HIGH MEDIUM LOW
> IST2007I IPPORT NUMBER = 12000 12001 12002 12003 12004
> IST2008I IPTOS VALUE = C0 C0 80 40 20
> IST924I -------------------------------------------------------------
> IST2017I TOTAL RTP PIPES = 0 LU-LU SESSIONS = 0
> IST2018I TOTAL ACTIVE PREDEFINED EE CONNECTIONS = 0
> IST2019I TOTAL ACTIVE LOCAL VRN EE CONNECTIONS = 0
> IST2020I TOTAL ACTIVE GLOBAL VRN EE CONNECTIONS = 0
> IST2021I TOTAL ACTIVE EE CONNECTIONS = 0
> IST314I END
>
> 2. /D NET, ID= EEXCAB1,E
> N03906 START DE PROCESSING COMPLETE. NCLID 015951
> IST097I DISPLAY ACCEPTED
> IST075I NAME = EEXCAB1 , TYPE = XCA MAJOR NODE
> IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> IST1679I MEDIUM = HPRIP
> IST1685I TCP/IP JOB NAME = TCPIP
> IST924I -------------------------------------------------------------
> IST089I EEGROUP TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST089I EEGRIN TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST089I EEGROUT TYPE = LINE GROUP , ACTIV
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
> IST924I -------------------------------------------------------------
> IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> IST170I LINES:
> IST1901I LINES UNDER GROUP: EEGROUP
> IST232I EEL000 ACTIV
> IST232I EEL001 ACTIV
> IST232I EEL002 ACTIV
> IST232I EEL003 ACTIV
> IST232I EEL004 ACTIV
>
> 3. /D NET,ID= SWDEVBTB,E
> N03906 START DE PROCESSING COMPLETE. NCLID 015956
> IST097I DISPLAY ACCEPTED
> IST075I NAME = SWDEVBTB , TYPE = SW SNA MAJ NODE
> IST486I STATUS= ACTIV , DESIRED STATE= ACTIV
> IST1656I VTAMTOPO = REPORT , NODE REPORTED - YES
> IST084I NETWORK RESOURCES:
> IST089I DEVIPDLC TYPE = PU_T2 , CONCT
> IST089I V1TST002 TYPE = LOGICAL UNIT , CONCT
> IST089I V1TST003 TYPE = LOGICAL UNIT , CONCT
> IST314I END
>
> 4. This is the output when we try to activate the node:
> XCAE40EE VBUILD
> TYPE=XCA
> *THIS IS FOR TEST
> XPE40EE PORT MEDIUM=HPRIP,
> X
> VNNAME=EEJEB,
> X
> VNGROUP=EEGRPJ,
> X
> LIVTIME=15,
> X
> SRQTIME=15,
> X
> SRQRETRY=9,
> X
> SAPADDR=04
> */
> *
> EEGRPJ GROUP ANSWER=ON,
> X
> AUTOGEN=(64,L,P),
> X
> CALL=INOUT,
> X
> DIAL=YES,
> X
> DYNPU=YES,
> X
> DYNPUPFX=$E,
> X
> ISTATUS=ACTIVE
>
> HERE IS THE ERROR
> act
> XCAE40EE
> IST097I VARY
> ACCEPTED
> IST1249I SYNTAX ERROR AT RECORD 4 IN MEMBER
> XCAE40EE
> IST258I STMT IN ERROR =
> VNNAME=EEJEB,
> IST314I
> END
> IST072I VARY ACT FOR ID = XCAE40EE FAILED DURING NETWORK DEFINITION
>
> Let me know if you need any more information!
>
> Thanks in advance for looking into it..- Hide quoted text -
>
> - Show quoted text -
Hello Steve:
Sorry for the delay. I have asked the mainframe folks to look into as
I have dont have a deeper knowledge on the MF side.. I am reading the
redbook and trying to figure out as much as I can.. BTW, those ip
address have been masked for security purpose..
Do you have a sample VTAM definition to set this up that you could
send to me? I mean whatever basic/necessary information it takes to
setup the connectivity.
Thanks again!
date: Thu, 24 Jul 2008 08:01:17 +0200
author: Steve Melan
Re: HIS 2006 (SNA Manager) to Mainframe connectivity
Hi Suijit,
I think that you will use SNA/IP to connect to the mainframe or will you use
native TCPIP ?
In case of SNA/IP (LU6.2), you need to setup the following :
* Define a LOGMODE in VTAM
* Define a connection in your CICS
* Define sessions in your CICS
Could you get me the following information from your VTAM / CICS / Mainframe
/ Windows Administrator :
* HIS Server Name (we need that to define a control point name CNAME)
* Would you like to address the CICS via TOR or directly to the AOR ?
* If the Enterprise Extender is working, we need its IP address
First of all, we need to setup a few thinks to test the connectivity. It
could be possible that the first cics calls were really slow, but
there is a chance to get you CICS executions from HIS really fast.
Example : Workstation --> IIS --> HIS --> CICS --> HIS --> IIS -->
Workstation (7 ms) milliseconds :-) for a dummy cics transaction
Greetings,
Steve
"EssKay" wrote in message
news:2e05138d-ed85-40cd-977d-b12861ee4094@b1g2000hsg.googlegroups.com...
On Jul 22, 12:52 am, "Steve Melan" wrote:
> Hello,
>
> Do you get only this :
> IST1680I LOCAL IP ADDRESS
> XX.XX.XX.XX
>
> OR is the XX represented by values that you don't want to show to the
> newsgroup because of security ?
> You should get here an IP address which should be pinged over the network
> !!!
>
> VTAM : member sys1.vtamlst(XCAE40EE)
> XCAE40EE VBUILD
> TYPE=XCA
> *THIS IS FOR TEST
> XPE40EE PORT MEDIUM=HPRIP, X
> LIVTIME=15, X
> SAPADDR=4
>
> *
> EEGRPJ GROUP DIAL=YES, X
> AUTOGEN=(010,D,R), X <<== Check with you
> mainframe operator for these values
> CALL=INOUT, X
> DYNPU=YES, X
> ISTATUS=ACTIVE
>
> Try with this member the VARY again !
>
> I hope this member will work for you.
>
> I will help you to get through this !!!
>
> If you need more quick response, I will give you my mail address !
>
> Steve
>
> "EssKay" wrote in message
>
> news:edda0a21-77b8-4fe2-be77-dc1fac976d64@j22g2000hsf.googlegroups.com...
> On Jul 21, 12:33 am, "Steve Melan" wrote:
>
>
>
>
>
> > If you are using multiple NIC's, verify if the VLAN is the same for the
> > incoming and the same for the outgoing connections.
> > Are you using a NLB (Network Load Balancing) to connect to the server ?
>
> > To verify the connections from the Mainframe Side :
> > 1. Go to ISPF
> > 2. ULOG
> > 3. /D NET,EE --> Verify that the EE is enabled
> > 4. /D NET,ID=MajorNode,E --> Verify that the Node is activ (you should
> > get an IP address of the EE)
> > 5. /D NET,ID=IPDLCLNK,E --> Displays the PU (Physical Unit)
>
> > If you receive on each case a correct answer, than the Mainframe Side is
> > ok
> > and we have to investigate on the Windows Side.
>
> > If it's possible, can you provide me the Mainframe Displays of the
> > commands
> > written above ?
>
> > Thank you in advance
>
> > Steve
>
> > "EssKay" wrote in message
>
> >news:b8697d1a-b9e1-41d3-8cad-f39675b879cd@i20g2000prf.googlegroups.com...
> > Thanks Steve for your reply..
> > I can find out if they have multiple NIC's. It is a physical server,
> > but we are connecting (on Windows side) from a Virtual PC environment.
> > How do I verify if the EE accepts connection? Like is there a tool to
> > use.
>
> > On Jul 18, 12:29 am, "Steve Melan" wrote:
>
> > > Hi,
>
> > > I'd once the same warning event and in my case it was related to a
> > > wrong
> > > network configuration on the server side.
> > > Do you have multiple network cards in your server ? Is it a physical
> > > or
> > > a
> > > virtual server ?
> > > Have you already verified if the Enterprise Extender is accepting
> > > connections ?
>
> > > Steve
>
> > > "EssKay" wrote in message
>
> > >news:cc48b3ca-7c17-40cc-8aa7-5a9957c9e6a2@l64g2000hse.googlegroups.com...
>
> > > > Community folks,
> > > > Need some help very badly... Have been working on this issue for a
> > > > week now.
>
> > > > Trying to attain connectivity between HIS 2006 and IBM Mainframe
> > > > (390)
> > > > using IP-DLC through SNA Manager. I have followed the document
> > > > [http://
> > > >www.microsoft.com/Downloads/details.aspx?FamilyID=86d6011a-3396-4c36-...]
> > > > and have been able to setup everything till I try to start the 3270
> > > > Client from SNA Service->Connections->Test (created by the 3270
> > > > wizard). The SNA Service has a status of Active, but the connection
> > > > I
> > > > created using the SNA Service->All tasks->3270 Wizard has a status
> > > > of
> > > > [Pending] and then [Failed@some time].
> > > > The error I get from the event log is:
> > > > -------------------------
> > > > Event Type: Warning
> > > > Event Source: SNA IP-DLC Link Service
> > > > Event Category: Base
> > > > Event ID: 121
> > > > Date: 7/15/2008
> > > > Time: 4:56:41 PM
> > > > User: TESTSYS\User1 |
