| Author |
Message |
Scott
Guest
|
Posted:
Thu Nov 11, 2004 2:54 am Post subject:
Pending PU problem |
|
|
I have an application that uses an LU6.2 connection defined over a dedicated
PU on an HIS server with SP1. At times, when the application is brought down,
it seems to cause the connection to fail. When I look at the connection in
SNA Manager, it shows pending. However, from VTAM's perspective the node goes
between CONCT status and PCTD2. PCTD2 in VTAM means that the device hasn't
responded to the ACTPU command. If the HIS Server is rebooted, the connection
comes back just fine. The problem is that there are several more PUs on this
server, so I'm only able to boot the server on Sunday nights. |
|
| Back to top |
|
 |
Jeremy Remlinger [MSFT]
Guest
|
Posted:
Fri Nov 12, 2004 2:01 am Post subject:
RE: Pending PU problem |
|
|
Scott,
You should be getting an event logged in the Application Event log. Most
likely an Event ID 230. It will either be failing on the TEST command, or
the XID request. The Details for the event should show you what you are
getting.
If we are failing on the TEST command, then we are actually losing physical
connectivity. That is, we are never getting a response to the TEST frame
that is sent.
If it is failing on the XID, then we are maintaining our Physical
connectivity insomuch that we are getting a responst to the TEST frame.
However, that means that on the host end, there is nothing there at that
address that is able to respond to the XID request. this could be that the
PU on the host side is in an error state, or is stopped.
It is also possible that the host side is activly rejecting the XID request
for some reason. In that instance, you will need to again take a look at
the Applicaiton Event Log to see if there is an error being logged (IIRC it
is Event ID 56, but don't hold me to it! ^_^) You will most likely need to
trace the communication between the HIS Server and the host system to see
what is being sent, and why it is being rejected.
#############################
#Jeremy "Rem" Remlinger, MSCE
#SNA/HIS Engineer
#Microsoft
#
#This posting is provided
#'AS IS' with no warranties,
#and confers no rights.
#© 2004 Microsoft Corporation
#All rights reserved.
#############################
--------------------
Thread-Topic: Pending PU problem
thread-index: AcTHZ2mvsKoJfWj3T7yOL0C1V4PPVg==
X-WBNR-Posting-Host: 192.152.100.150
From: "=?Utf-8?B?U2NvdHQ=?=" <Scott@discussions.microsoft.com>
Subject: Pending PU problem
Date: Wed, 10 Nov 2004 12:54:04 -0800
Lines: 8
Message-ID: <68D1C4E2-B640-4A46-BE52-9FEA3EE97CCF@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.hiserver.general:4412
X-Tomcat-NG: microsoft.public.hiserver.general
I have an application that uses an LU6.2 connection defined over a
dedicated
PU on an HIS server with SP1. At times, when the application is brought
down,
it seems to cause the connection to fail. When I look at the connection in
SNA Manager, it shows pending. However, from VTAM's perspective the node
goes
between CONCT status and PCTD2. PCTD2 in VTAM means that the device hasn't
responded to the ACTPU command. If the HIS Server is rebooted, the
connection
comes back just fine. The problem is that there are several more PUs on
this
server, so I'm only able to boot the server on Sunday nights. |
|
| Back to top |
|
 |
Scott
Guest
|
Posted:
Sat Nov 13, 2004 12:49 am Post subject:
RE: Pending PU problem |
|
|
Nothing shows up in the Application log. I did capture a DLC trace, but since
I can't specify a specific PU to trace, it's 700kb. I have inactivated the
major node on VTAM and reactivated it, which rebuilds the control blocks in
VTAM for the device. I know a reboot of the HIS server will correct the
issue. I'm almost willing to bet that stopping and starting the SNA Service
would also correct the issue. However, I can't do that since this is a
production server.
"Jeremy Remlinger [MSFT]" wrote:
| Quote: | Scott,
You should be getting an event logged in the Application Event log. Most
likely an Event ID 230. It will either be failing on the TEST command, or
the XID request. The Details for the event should show you what you are
getting.
If we are failing on the TEST command, then we are actually losing physical
connectivity. That is, we are never getting a response to the TEST frame
that is sent.
If it is failing on the XID, then we are maintaining our Physical
connectivity insomuch that we are getting a responst to the TEST frame.
However, that means that on the host end, there is nothing there at that
address that is able to respond to the XID request. this could be that the
PU on the host side is in an error state, or is stopped.
It is also possible that the host side is activly rejecting the XID request
for some reason. In that instance, you will need to again take a look at
the Applicaiton Event Log to see if there is an error being logged (IIRC it
is Event ID 56, but don't hold me to it! ^_^) You will most likely need to
trace the communication between the HIS Server and the host system to see
what is being sent, and why it is being rejected.
#############################
#Jeremy "Rem" Remlinger, MSCE
#SNA/HIS Engineer
#Microsoft
#
#This posting is provided
#'AS IS' with no warranties,
#and confers no rights.
#© 2004 Microsoft Corporation
#All rights reserved.
#############################
--------------------
Thread-Topic: Pending PU problem
thread-index: AcTHZ2mvsKoJfWj3T7yOL0C1V4PPVg==
X-WBNR-Posting-Host: 192.152.100.150
From: "=?Utf-8?B?U2NvdHQ=?=" <Scott@discussions.microsoft.com
Subject: Pending PU problem
Date: Wed, 10 Nov 2004 12:54:04 -0800
Lines: 8
Message-ID: <68D1C4E2-B640-4A46-BE52-9FEA3EE97CCF@microsoft.com
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.hiserver.general:4412
X-Tomcat-NG: microsoft.public.hiserver.general
I have an application that uses an LU6.2 connection defined over a
dedicated
PU on an HIS server with SP1. At times, when the application is brought
down,
it seems to cause the connection to fail. When I look at the connection in
SNA Manager, it shows pending. However, from VTAM's perspective the node
goes
between CONCT status and PCTD2. PCTD2 in VTAM means that the device hasn't
responded to the ACTPU command. If the HIS Server is rebooted, the
connection
comes back just fine. The problem is that there are several more PUs on
this
server, so I'm only able to boot the server on Sunday nights |
|
|
| Back to top |
|
 |
Jeremy Remlinger [MSFT]
Guest
|
Posted:
Tue Nov 23, 2004 2:05 am Post subject:
RE: Pending PU problem |
|
|
Scott,
I am suprised that there is nothing in the Application Event Log. There
should at least be an Event ID 23 if the connection fails. Under the
Subdomain properties, is the Default Audit Log Level set to at least
Significant System Events?
The only way to troubleshoot this furhter is going to be by analyizing the
traces. Does this conenction use it's own Link Service? If so, you could
turn on tracing for just this Link Service and get a better idea what is
happening.
At this point I would strongly suggest opening a support issue with
Microsoft Support for assistance is configuring and reading the nessacary
traces.
#############################
#Jeremy "Rem" Remlinger, MSCE
#SNA/HIS Engineer
#Microsoft
#
#This posting is provided
#'AS IS' with no warranties,
#and confers no rights.
#© 2004 Microsoft Corporation
#All rights reserved.
#############################
--------------------
Thread-Topic: Pending PU problem
thread-index: AcTI6EhbslhJ/bjHSsCJk7mg9TTsCg==
X-WBNR-Posting-Host: 192.152.100.150
From: "=?Utf-8?B?U2NvdHQ=?=" <Scott@discussions.microsoft.com>
References: <68D1C4E2-B640-4A46-BE52-9FEA3EE97CCF@microsoft.com>
<pHqXKlCyEHA.1184@cpmsftngxa10.phx.gbl>
Subject: RE: Pending PU problem
Date: Fri, 12 Nov 2004 10:49:04 -0800
Lines: 86
Message-ID: <E85B1E11-E03E-43B4-8EBA-5E63B6767CB9@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.hiserver.general:4426
X-Tomcat-NG: microsoft.public.hiserver.general
Nothing shows up in the Application log. I did capture a DLC trace, but
since
I can't specify a specific PU to trace, it's 700kb. I have inactivated the
major node on VTAM and reactivated it, which rebuilds the control blocks in
VTAM for the device. I know a reboot of the HIS server will correct the
issue. I'm almost willing to bet that stopping and starting the SNA Service
would also correct the issue. However, I can't do that since this is a
production server.
"Jeremy Remlinger [MSFT]" wrote:
| Quote: | Scott,
You should be getting an event logged in the Application Event log. Most
likely an Event ID 230. It will either be failing on the TEST command,
or
the XID request. The Details for the event should show you what you are
getting.
If we are failing on the TEST command, then we are actually losing
physical
connectivity. That is, we are never getting a response to the TEST frame
that is sent.
If it is failing on the XID, then we are maintaining our Physical
connectivity insomuch that we are getting a responst to the TEST frame.
However, that means that on the host end, there is nothing there at that
address that is able to respond to the XID request. this could be that
the
PU on the host side is in an error state, or is stopped.
It is also possible that the host side is activly rejecting the XID
request
for some reason. In that instance, you will need to again take a look at
the Applicaiton Event Log to see if there is an error being logged (IIRC
it
is Event ID 56, but don't hold me to it! ^_^) You will most likely need
to
trace the communication between the HIS Server and the host system to see
what is being sent, and why it is being rejected.
#############################
#Jeremy "Rem" Remlinger, MSCE
#SNA/HIS Engineer
#Microsoft
#
#This posting is provided
#'AS IS' with no warranties,
#and confers no rights.
#© 2004 Microsoft Corporation
#All rights reserved.
#############################
--------------------
Thread-Topic: Pending PU problem
thread-index: AcTHZ2mvsKoJfWj3T7yOL0C1V4PPVg==
X-WBNR-Posting-Host: 192.152.100.150
From: "=?Utf-8?B?U2NvdHQ=?=" <Scott@discussions.microsoft.com
Subject: Pending PU problem
Date: Wed, 10 Nov 2004 12:54:04 -0800
Lines: 8
Message-ID: <68D1C4E2-B640-4A46-BE52-9FEA3EE97CCF@microsoft.com
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.hiserver.general:4412
X-Tomcat-NG: microsoft.public.hiserver.general
I have an application that uses an LU6.2 connection defined over a
dedicated
PU on an HIS server with SP1. At times, when the application is brought
down,
it seems to cause the connection to fail. When I look at the connection
in
SNA Manager, it shows pending. However, from VTAM's perspective the node
goes
between CONCT status and PCTD2. PCTD2 in VTAM means that the device
hasn't
responded to the ACTPU command. If the HIS Server is rebooted, the
connection
comes back just fine. The problem is that there are several more PUs on
this
server, so I'm only able to boot the server on Sunday nights |
|
|
| Back to top |
|
 |
|
|
|
|