Re: Error on OPnqryf CPI432C while invoking SP from .NET

There is a timeout for .NET connections. It is on the iDB2Command or
iDB2Connection, IIRC. It should be .TimeOut. Try adding that and it should
work for ya. I have had to change that in the past for some queries for
some reason. Even if the query took mere seconds on the green-screen.

On Wednesday, November 16, 2011, S.Kavitha wrote:

Walden,

Am able to execute the stored proc wherein, CLPGMNM has been embedded (in
SP). Even the same program am able to execute via Datagate(ASNA).
But this stuck up with .NET alone. Is there any other details that i should
consider like .NET connection string parms or something in iSeries.

- Kavitha.
On Thu, Nov 17, 2011 at 1:04 AM, Walden H. Leverich <
WaldenL@xxxxxxxxxxxxxxx

wrote:

Query exceeds specified time limit or storage limit.

Well, there's your problem right there. The query you're trying to run
exceeds the allowed runtime. IIRC, it's defined in QAQQINI. I don't think
the green screen call is constrained by the time limiter so you're
successful on the green screen, but die from .Net.

-Walden


--
Walden H Leverich III
Tech Software &
BEC - IRBManager
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com
http://www.IRBManager.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx [mailto:
systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of S.Kavitha
Sent: Wednesday, November 16, 2011 1:51 PM
To: systemidotnet@xxxxxxxxxxxx
Subject: [SystemiDotNet] Error on OPnqryf CPI432C while invoking SP from
.NET

Hi,

** **

I wrote a Stored procedure to execute a CLP CLPPGMNM in AS400 V6R1
Environment. This SP is being called in .NET environment to Execute
CLPPGMNM. ****

Am able to execute the SP in iSeries/directly as a program. But when
executed from .NET, the job abends in MSGW. Below is the Error Msg
provided. ****

** **

All access paths were considered for file JOINLF3. ****

Additional access path reason codes were used. ****

All access paths were considered for file JOINLF3. ****

Additional access path reason codes were used. ****

File JOINLF3 processed in join position 1. ****

File JOINLF3 processed in join position 2. ****

Temporary result file built for query.
****

Query exceeds specified time limit or storage limit.
****

Error occurred during processing of command.
****

Function check. CPF9899 unmonitored by CLPGMNM at statement 2200,

****

instruction X'0011'.

****

CPF9899 received by CLPGMNM at 2200. (C D I R)

****

** **

** **

Message ID . . . . . . : CPI432C Severity . . . . . . . :
00 ****

Message type . . . . . :
Information ****

Date sent . . . . . . : 11/14/11 Time sent . . . . . . :
02:17:50 ****


****

Message . . . . : All access paths were considered for file JOINLF3.
****

Cause . . . . . : The query optimizer considered all access paths

built

over ****

member JOINLF3 of file JOINLF3 in library < LibraryName>.
****

The list below shows the access paths considered. If file JOINLF3in
****

library LibraryName is a logical file then the access paths specified
are ****

actually built over member PF1 of physical file PF1 in library ****

LibraryName. Following each access path name in the l