| Author |
Message |
Krijn Michiels
Guest
|
 Posted:
Thu Mar 31, 2005 2:48 pm Post subject:
Executing stored procedures |
|
|
Hi,
The msdb2command does not return result sets when using stored procedures.
The procedures work fine when using OleDbCommand with the client access
driver.
There are no errors thrown, the result set is empty. |
|
| Back to top |
|
 |
Krijn Michiels
Guest
|
| Posted:
Sat Apr 09, 2005 1:46 pm Post subject:
RE: Executing stored procedures |
|
|
The result sets are returned when executing the command through the oleDB
client access 5.2 driver and other managed providers (hitsw - ritmo).
I noticed that they connect through port 8471 instead of 446.
Is it possible to create a msdb2Connection to port 8471 instead of 446 ?
Is there another solution ? |
|
| Back to top |
|
|
Aaron Grady [MSFT]
Guest
|
| Posted:
Thu Apr 14, 2005 8:47 pm Post subject:
Re: Executing stored procedures |
|
|
The client access DB2 provider uses a different tcp/ip listener on the
AS/400. The Microsoft HIS DB2 providers talk to the DRDA TCP/IP listener on
the host which runs on port 446 by default. No, we cannot talk to the other
listener, but that should not be related to your problem of calling a stored
procedure.
For some reason I cannot see the earlier posts on this thread, can you
relate the details of your stored procedure problem again?
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:9A7DE52D-A15C-41D6-B1FE-92176B8A695B@microsoft.com...
| Quote: | The result sets are returned when executing the command through the oleDB
client access 5.2 driver and other managed providers (hitsw - ritmo).
I noticed that they connect through port 8471 instead of 446.
Is it possible to create a msdb2Connection to port 8471 instead of 446 ?
Is there another solution ?
|
|
|
| Back to top |
|
|
Krijn Michiels
Guest
|
| Posted:
Fri Apr 15, 2005 1:46 pm Post subject:
Re: Executing stored procedures |
|
|
Aaron,
Everything works fine on our AS400 system V4R4 except returning result sets
from stored procedures.
Trace file displays warning :
DRDA AR message: Name: ENDUOWRM, Severity: Warning, Diagnostic: , Database:
RDBREM
SetSqlState: 2 --> 4
SetSqlState: 4 --> 3
Dropping SqlStatement: 137003168
SetSqlState: 3 --> 3
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
It would be great if this could work.
"Aaron Grady [MSFT]" wrote:
| Quote: | The client access DB2 provider uses a different tcp/ip listener on the
AS/400. The Microsoft HIS DB2 providers talk to the DRDA TCP/IP listener on
the host which runs on port 446 by default. No, we cannot talk to the other
listener, but that should not be related to your problem of calling a stored
procedure.
For some reason I cannot see the earlier posts on this thread, can you
relate the details of your stored procedure problem again?
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:9A7DE52D-A15C-41D6-B1FE-92176B8A695B@microsoft.com...
The result sets are returned when executing the command through the oleDB
client access 5.2 driver and other managed providers (hitsw - ritmo).
I noticed that they connect through port 8471 instead of 446.
Is it possible to create a msdb2Connection to port 8471 instead of 446 ?
Is there another solution ?
|
|
|
| Back to top |
|
|
Aaron Grady [MSFT]
Guest
|
| Posted:
Fri Apr 15, 2005 9:47 pm Post subject:
Re: Executing stored procedures |
|
|
Krijn,
ENDUOWRM (end unit of work reply message) is not necessarily a problem.
Warnings do not generally cause errors. My guess is that there is some other
problem, but it is hard to tell from just this small trace snippet.
Can you tell me the exact error you receive from the DB2 provider?
Can you post the entire trace? I will give it a glance over to see if the
problem is easily spotted. If this appears to be a complex problem which
requires more investigation I may have to recommend you to start a call with
our support team. But... post it first and let's see...
Thanks,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:41AC8CAE-FC20-4292-B1E1-C19B2CD775E9@microsoft.com...
| Quote: | Aaron,
Everything works fine on our AS400 system V4R4 except returning result
sets
from stored procedures.
Trace file displays warning :
DRDA AR message: Name: ENDUOWRM, Severity: Warning, Diagnostic: ,
Database:
RDBREM
SetSqlState: 2 --> 4
SetSqlState: 4 --> 3
Dropping SqlStatement: 137003168
SetSqlState: 3 --> 3
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
It would be great if this could work.
"Aaron Grady [MSFT]" wrote:
The client access DB2 provider uses a different tcp/ip listener on the
AS/400. The Microsoft HIS DB2 providers talk to the DRDA TCP/IP listener
on
the host which runs on port 446 by default. No, we cannot talk to the
other
listener, but that should not be related to your problem of calling a
stored
procedure.
For some reason I cannot see the earlier posts on this thread, can you
relate the details of your stored procedure problem again?
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in
message
news:9A7DE52D-A15C-41D6-B1FE-92176B8A695B@microsoft.com...
The result sets are returned when executing the command through the
oleDB
client access 5.2 driver and other managed providers (hitsw - ritmo).
I noticed that they connect through port 8471 instead of 446.
Is it possible to create a msdb2Connection to port 8471 instead of 446
?
Is there another solution ?
|
|
|
| Back to top |
|
|
Krijn Michiels
Guest
|
| Posted:
Mon Apr 18, 2005 12:29 pm Post subject:
Re: Executing stored procedures |
|
|
Aaron,
There are no errors thrown by the DB2 provider (in .NET).
Executed code works with managed provider from client access 5.2 and other
managed provider from HitSW (named ritmo). The code executes a stored
procedure with 2 parameters, one in and one out. The out parameter is
returned successfully. The result set is not returned.
The WSAStartup error below only happens on one machine and only the first
execution. I don't think it has anything to do with it because the sql
statement is already dropped.
Thanks
The full trace :
DDM 00472201 00061149 0000000C 112ED8E2 D8F0F4F0 F4F0000D 002FD8E3 C4E2D8D3
DDM F4F0F000 0A003500 06119C01 F4000B21 354B4040 40404040 00062125 24340009
DDM 11A0D2D9 C9D1D5
Setting IsolationLevel from 9285 to 9282
Setting AutoCommit 1
Allocating SqlStatement: 137003168
SetSqlState: 1 --> 2
Preparing Stored Procedure in SP section: FREDDY.DOTNETR1
Executing Stored Procedure: FREDDY.DOTNETR1
DDM -----------------------------------------------------------------------
DDM Send: Length = 120
DDM 0078200B 00442113 D9C4C2D9 C5D44040 40404040 40404040 4040C6D9 C5C4C4E8
DDM 40404040 40404040 40404040 D4E2D5C3 F0F0F140 40404040 40404040 4040F5F0
DDM F0F0F0F0 F0F10081 00052111 F1000521 05F00013 2138C6D9 C5C4C4E8 4BC4D6E3
DDM D5C5E3D9 F1000821 1400007F FF000621 40FFFF00 052142C0
DDM -----------------------------------------------------------------------
DDM Send: Length = 30
DDM 001E2412 00130010 0976D031 000A0F05 040671E4 D0000100 07147A00 FFFF
DDM -----------------------------------------------------------------------
DDM Receive: Length = 43
DDM 002B2413 001C0010 0976D031 00080F05 000971E0 540001D0 00010671 F0E00000
DDM 000B147A FF008000 01834F
Local Transaction Commit
DDM -----------------------------------------------------------------------
DDM Send: Length = 4
DDM 0004200E
DDM -----------------------------------------------------------------------
DDM Receive: Length = 37
DDM 0025220C 00061149 00040016 2110D9C4 C2D9C5D4 40404040 40404040 40404040
DDM 00052115 01
DDM -----------------------------------------------------------------------
DDM Receive: Length = 5
DDM 00052408 FF
DRDA AR message: Name: ENDUOWRM, Severity: Warning, Diagnostic: , Database:
RDBREM
SetSqlState: 2 --> 4
SetSqlState: 4 --> 3
Dropping SqlStatement: 137003168
SetSqlState: 3 --> 3
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
A TCPIP socket error has occured (10093): De toepassing heeft WSAStartup
niet aangeroepen, of WSAStartup is mislukt.
DRDA AR message: Error Code: 10093, Severity: Error, SQLSTATE: 08S01,
SQLCODE: 10093
A TCPIP socket error has occured (10093): De toepassing heeft WSAStartup
niet aangeroepen, of WSAStartup is mislukt.
DRDA AR message: Error Code: 10093, Severity: Error, SQLSTATE: 08S01,
SQLCODE: 10093
"Aaron Grady [MSFT]" wrote:
| Quote: | Krijn,
ENDUOWRM (end unit of work reply message) is not necessarily a problem.
Warnings do not generally cause errors. My guess is that there is some other
problem, but it is hard to tell from just this small trace snippet.
Can you tell me the exact error you receive from the DB2 provider?
Can you post the entire trace? I will give it a glance over to see if the
problem is easily spotted. If this appears to be a complex problem which
requires more investigation I may have to recommend you to start a call with
our support team. But... post it first and let's see...
Thanks,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:41AC8CAE-FC20-4292-B1E1-C19B2CD775E9@microsoft.com...
Aaron,
Everything works fine on our AS400 system V4R4 except returning result
sets
from stored procedures.
Trace file displays warning :
DRDA AR message: Name: ENDUOWRM, Severity: Warning, Diagnostic: ,
Database:
RDBREM
SetSqlState: 2 --> 4
SetSqlState: 4 --> 3
Dropping SqlStatement: 137003168
SetSqlState: 3 --> 3
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
It would be great if this could work.
"Aaron Grady [MSFT]" wrote:
The client access DB2 provider uses a different tcp/ip listener on the
AS/400. The Microsoft HIS DB2 providers talk to the DRDA TCP/IP listener
on
the host which runs on port 446 by default. No, we cannot talk to the
other
listener, but that should not be related to your problem of calling a
stored
procedure.
For some reason I cannot see the earlier posts on this thread, can you
relate the details of your stored procedure problem again?
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in
message
news:9A7DE52D-A15C-41D6-B1FE-92176B8A695B@microsoft.com...
The result sets are returned when executing the command through the
oleDB
client access 5.2 driver and other managed providers (hitsw - ritmo).
I noticed that they connect through port 8471 instead of 446.
Is it possible to create a msdb2Connection to port 8471 instead of 446
?
Is there another solution ?
|
|
|
| Back to top |
|
|
Aaron Grady [MSFT]
Guest
|
| Posted:
Wed Apr 20, 2005 9:29 pm Post subject:
Re: Executing stored procedures |
|
|
Krijn-
How big is the result set you are expecting back? The SQLDTARD in the trace
below only seems to return 43 bytes:
DDM Receive: Length = 43
DDM 002B2413 001C0010 0976D031 00080F05 000971E0 540001D0 00010671
F0E00000
DDM 000B147A FF008000 01834F
And that 43 bytes includes the DDM command headers and data description. I'm
guessing this is your output parameter(s). What about the case where the
socket error does not occur, does the trace look different then?
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:CDD5D75B-172D-4551-A2AB-FAA58504328B@microsoft.com...
| Quote: | Aaron,
There are no errors thrown by the DB2 provider (in .NET).
Executed code works with managed provider from client access 5.2 and other
managed provider from HitSW (named ritmo). The code executes a stored
procedure with 2 parameters, one in and one out. The out parameter is
returned successfully. The result set is not returned.
The WSAStartup error below only happens on one machine and only the first
execution. I don't think it has anything to do with it because the sql
statement is already dropped.
Thanks
The full trace :
DDM 00472201 00061149 0000000C 112ED8E2 D8F0F4F0 F4F0000D 002FD8E3
C4E2D8D3
DDM F4F0F000 0A003500 06119C01 F4000B21 354B4040 40404040 00062125
24340009
DDM 11A0D2D9 C9D1D5
Setting IsolationLevel from 9285 to 9282
Setting AutoCommit 1
Allocating SqlStatement: 137003168
SetSqlState: 1 --> 2
Preparing Stored Procedure in SP section: FREDDY.DOTNETR1
Executing Stored Procedure: FREDDY.DOTNETR1
M -----------------------------------------------------------------------
DDM Send: Length = 120
DDM 0078200B 00442113 D9C4C2D9 C5D44040 40404040 40404040 4040C6D9
C5C4C4E8
DDM 40404040 40404040 40404040 D4E2D5C3 F0F0F140 40404040 40404040
4040F5F0
DDM F0F0F0F0 F0F10081 00052111 F1000521 05F00013 2138C6D9 C5C4C4E8
4BC4D6E3
DDM D5C5E3D9 F1000821 1400007F FF000621 40FFFF00 052142C0
M -----------------------------------------------------------------------
DDM Send: Length = 30
DDM 001E2412 00130010 0976D031 000A0F05 040671E4 D0000100 07147A00 FFFF
M -----------------------------------------------------------------------
DDM Receive: Length = 43
DDM 002B2413 001C0010 0976D031 00080F05 000971E0 540001D0 00010671
F0E00000
DDM 000B147A FF008000 01834F
Local Transaction Commit
M -----------------------------------------------------------------------
DDM Send: Length = 4
DDM 0004200E
M -----------------------------------------------------------------------
DDM Receive: Length = 37
DDM 0025220C 00061149 00040016 2110D9C4 C2D9C5D4 40404040 40404040
40404040
DDM 00052115 01
M -----------------------------------------------------------------------
DDM Receive: Length = 5
DDM 00052408 FF
DRDA AR message: Name: ENDUOWRM, Severity: Warning, Diagnostic: ,
Database:
RDBREM
SetSqlState: 2 --> 4
SetSqlState: 4 --> 3
Dropping SqlStatement: 137003168
SetSqlState: 3 --> 3
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
A TCPIP socket error has occured (10093): De toepassing heeft WSAStartup
niet aangeroepen, of WSAStartup is mislukt.
DRDA AR message: Error Code: 10093, Severity: Error, SQLSTATE: 08S01,
SQLCODE: 10093
A TCPIP socket error has occured (10093): De toepassing heeft WSAStartup
niet aangeroepen, of WSAStartup is mislukt.
DRDA AR message: Error Code: 10093, Severity: Error, SQLSTATE: 08S01,
SQLCODE: 10093
"Aaron Grady [MSFT]" wrote:
Krijn,
ENDUOWRM (end unit of work reply message) is not necessarily a problem.
Warnings do not generally cause errors. My guess is that there is some
other
problem, but it is hard to tell from just this small trace snippet.
Can you tell me the exact error you receive from the DB2 provider?
Can you post the entire trace? I will give it a glance over to see if
the
problem is easily spotted. If this appears to be a complex problem which
requires more investigation I may have to recommend you to start a call
with
our support team. But... post it first and let's see...
Thanks,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in
message
news:41AC8CAE-FC20-4292-B1E1-C19B2CD775E9@microsoft.com...
Aaron,
Everything works fine on our AS400 system V4R4 except returning result
sets
from stored procedures.
Trace file displays warning :
DRDA AR message: Name: ENDUOWRM, Severity: Warning, Diagnostic: ,
Database:
RDBREM
SetSqlState: 2 --> 4
SetSqlState: 4 --> 3
Dropping SqlStatement: 137003168
SetSqlState: 3 --> 3
Setting IsolationLevel from 9285 to 9285
Setting AutoCommit 1
It would be great if this could work.
"Aaron Grady [MSFT]" wrote:
The client access DB2 provider uses a different tcp/ip listener on
the
AS/400. The Microsoft HIS DB2 providers talk to the DRDA TCP/IP
listener
on
the host which runs on port 446 by default. No, we cannot talk to
the
other
listener, but that should not be related to your problem of calling
a
stored
procedure.
For some reason I cannot see the earlier posts on this thread, can
you
relate the details of your stored procedure problem again?
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server
Microsoft
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in
message
news:9A7DE52D-A15C-41D6-B1FE-92176B8A695B@microsoft.com...
The result sets are returned when executing the command through
the
oleDB
client access 5.2 driver and other managed providers (hitsw -
ritmo).
I noticed that they connect through port 8471 instead of 446.
Is it possible to create a msdb2Connection to port 8471 instead of
446
?
Is there another solution ?
|
|
|
| Back to top |
|
|
Krijn Michiels
Guest
|
| Posted:
Thu Apr 21, 2005 5:18 pm Post subject:
Re: Executing stored procedures |
|
|
The result set is between 100 to 1000 records with 7 fields.
The following error is returned when executing the same procedure on a V5R3
machine :
Index (zero based) must be greater than or equal to zero and less than the
size of the argument list. (DataAdapter.Fill or ExecuteReader)
Execute on V4R4 does not give errors.
Both the trace files look normal (too long for post). |
|
| Back to top |
|
|
Aaron Grady [MSFT]
Guest
|
| Posted:
Thu Apr 21, 2005 10:01 pm Post subject:
Re: Executing stored procedures |
|
|
So are you saying this works on V4R4 and you get a result set back? This
only fails on V5R3?
If so, we have an outstanding issue with V5R3 that we are trying to resolve
right now and I would ask that you get a support case started with Microsoft
support so that we can get those traces and try and get a fix for the
problem.
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:79D99A9F-D41C-49E4-AE77-5E1421968A65@microsoft.com...
| Quote: | The result set is between 100 to 1000 records with 7 fields.
The following error is returned when executing the same procedure on a
V5R3
machine :
Index (zero based) must be greater than or equal to zero and less than the
size of the argument list. (DataAdapter.Fill or ExecuteReader)
Execute on V4R4 does not give errors.
Both the trace files look normal (too long for post). |
|
|
| Back to top |
|
|
Charles Ezzell (MSFT)
Guest
|
| Posted:
Fri Apr 22, 2005 12:44 am Post subject:
Re: Executing stored procedures |
|
|
Please open a case with both Microsoft PSS and IBM. We are working with IBM
on this, and believe we have identified the problem. Also, upgrade to the
latest PTF from IBM and see if this helps. Mention in your case this is an
upgrade issue where everything was working fine (to both IBM and us). I can
give you more after you have a case, but the one thing I want to know now is
what PTF Group levels you are at (GO PTF, option 12 I believe).
Thanks,
Charles
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:79D99A9F-D41C-49E4-AE77-5E1421968A65@microsoft.com...
| Quote: | The result set is between 100 to 1000 records with 7 fields.
The following error is returned when executing the same procedure on a
V5R3
machine :
Index (zero based) must be greater than or equal to zero and less than the
size of the argument list. (DataAdapter.Fill or ExecuteReader)
Execute on V4R4 does not give errors.
Both the trace files look normal (too long for post). |
|
|
| Back to top |
|
|
Krijn Michiels
Guest
|
| Posted:
Mon Apr 25, 2005 9:03 pm Post subject:
Re: Executing stored procedures |
|
|
Sorry,
My previous post wasn't very clear. What I ment was that V4R4 does not give
any errors in .NET BUT also doesn't return any records !
Nothing too see in the trace files.
Thanks,
Krijn
"Charles Ezzell (MSFT)" wrote:
| Quote: | Please open a case with both Microsoft PSS and IBM. We are working with IBM
on this, and believe we have identified the problem. Also, upgrade to the
latest PTF from IBM and see if this helps. Mention in your case this is an
upgrade issue where everything was working fine (to both IBM and us). I can
give you more after you have a case, but the one thing I want to know now is
what PTF Group levels you are at (GO PTF, option 12 I believe).
Thanks,
Charles
"Krijn Michiels" <KrijnMichiels@discussions.microsoft.com> wrote in message
news:79D99A9F-D41C-49E4-AE77-5E1421968A65@microsoft.com...
The result set is between 100 to 1000 records with 7 fields.
The following error is returned when executing the same procedure on a
V5R3
machine :
Index (zero based) must be greater than or equal to zero and less than the
size of the argument list. (DataAdapter.Fill or ExecuteReader)
Execute on V4R4 does not give errors.
Both the trace files look normal (too long for post).
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in