SQL: SQLWSC001 -> MCH5804 -> SQL0913

[Rolf Mittag]

Hello *all

I've got a program (RPGIV) which does

- EXEC SQL declare c cursor for stm END-EXEC
- eval s = '<Sql select statement>'
- EXEC SQL prepare stm form :s END-EXEC
- EXEC SQL open c1 END-EXEC

this worked fine for quite while. Since last week I get
a message (MCH5804) stating a timeout for
lib : QSYS object : SQLWSC001 type : *PGM

followed by message SQL0913 from SQL.

Since there is no program with that name in QSYS I
guess from the name that it could be a temporary SQL object.

The last change to the OS (V4R4) was installing the latest cum ptf
( C0252440 ).

Searching the ptf cover letters showed no documents for
"SQLWSC001 OR MCH5804 OR SQL0913".

Has anybody any idea ?

TIA Rolf

--

Dipl.Inf.(FH) Rolf P Mittag
IBM Partner In Development
Leipziger Str. 50
D-69214 Eppelheim
eMl: r...@r-m-e-d-v.de
Fon: +49 (6221) 76 78 60
Fax: +49 (6221) 76 80 26

[Karl Hanson]

Rolf Mittag wrote:
>
> I've got a program (RPGIV) which does
>
> - EXEC SQL declare c cursor for stm END-EXEC
> - eval s = '<Sql select statement>'
> - EXEC SQL prepare stm form :s END-EXEC
> - EXEC SQL open c1 END-EXEC
>
> this worked fine for quite while. Since last week I get
> a message (MCH5804) stating a timeout for
> lib : QSYS object : SQLWSC001 type : *PGM
>
> followed by message SQL0913 from SQL.
>
> Since there is no program with that name in QSYS I
> guess from the name that it could be a temporary SQL object.
>
> The last change to the OS (V4R4) was installing the latest cum ptf
> ( C0252440 ).
>
> Searching the ptf cover letters showed no documents for
> "SQLWSC001 OR MCH5804 OR SQL0913".
>

One thing to check - do you have the latest DB2 group PTF (aka fixpack)
installed for V4R4? To find the latest info, go here:
http://www.as400.ibm.com/db2/db2tch_m.htm
... and take the "DB2 UDB for AS/400 Fixpack Information" link. See
SF99104.

--

Karl Hanson

[Charles R. Pence]

Rolf Mittag wrote:
> I've got a program (RPGIV) which does
>
> - EXEC SQL declare c cursor for stm END-EXEC
> - eval s = '<Sql select statement>'
> - EXEC SQL prepare stm form :s END-EXEC
> - EXEC SQL open c1 END-EXEC
>
> this worked fine for quite while. Since last week I get
> a message (MCH5804) stating a timeout for
> lib : QSYS object : SQLWSC001 type : *PGM
>
> followed by message SQL0913 from SQL.
>
> Since there is no program with that name in QSYS I
> guess from the name that it could be a temporary SQL object.
>
> The last change to the OS (V4R4) was installing the latest cum ptf
> ( C0252440 ).
>
> Searching the ptf cover letters showed no documents for
> "SQLWSC001 OR MCH5804 OR SQL0913".
>

> Has anybody any idea ?

My guess <likely MSGMCH5804 was not noted; though if the correct
PTF, it should have been> for preventive:
V4R4M0 SF64382 00/11/16 Cnone440
V4R5M0 SF63111 00/08/28 C0231450

Regards, Chuck
All comments provided "as is" with no warranties of any kind whatsoever.

[Rolf Mittag]

I finally managed to order and apply the latest DB2/400
Fix Pack which fixed the problems with "prepare statement".

I'm still stuck with some ODBC problems which prevent
"Crystal Reports" and "OpNav" from working

comm rc 8405 : CWB0986
program ended unexpectedly (translation from german)

When I won't fin anything I will post again.

Thanx Rolf

[Jon Wold]

Not good -- 8405 means that the CAE comm code was blocked on a winsock
recv() and got zero bytes back, which is an indication that the other
end of the pipe (the DB server job) abruptly closed the socket. This
can happen if the server job function checks due to their own private
defect, or if the datastream as received by the server is mangled
enough, they may also bail out (in which case either the client code or
the network is at fault).

Perhaps there's an applicable PTF for the host ?

Jon

[Charles R. Pence]

Rolf Mittag wrote:
> I finally managed to order and apply the latest DB2/400
> Fix Pack which fixed the problems with "prepare statement".
>

> I'm still stuck with some ODBC problems which prevent
> "Crystal Reports" and "OpNav" from working
>
> comm rc 8405 : CWB0986
> program ended unexpectedly (translation from german)
>

> When I won't fin anything I will post again.

WRKSPLF (QUSER *N *N QZDASOINIT) /* Or similar; per ODBC comm */
Review the spooled joblog for the failure conditions. Per search:
Probably one of: II11953, SA91151, or special instructions for
immediate vs delayed apply of OPTION(12) PTF were not followed;
for example: SF63901

[Rolf Mittag]

the example of sf63901 was _the_ hint.
DLTSQLPKG QIWS/QZDAPKG resolved the problem