My 32-bit DB2 v9.7.5 *client* on Windows crashes when I compile a specific long
SQL-PL stored procedure (at the command line db2 -tvf proc.sql).
The database is remote.

Windows shows a message popup "IBM(R) DB2(R) has stopped working..." as soon as clp runs the line 'create procedure .....'

The same stored-procedure file compiles successfully on a Linux v9.7.5 client (using the same remote database as the Windows client).

But other smaller stored procedures compile fine on this client box, so it might be a size-related problem.

The file size of the stored-procedure file is around 137KB.

The db2-client db2diag.log shows two relevant messages:

FUNCTION: DB2 UDB, command line process, clp_savecmd, probe:12
MESSAGE : Command is too long to be saved in cmdhistory
DATA #1 : Command text truncated (max 20 chars), PD_CLP_TYPE_CMD, 20 bytes
create procedure xxx

then lots of these:
FUNCTION: DB2 UDB, command line process, clp_bp_con, probe:33
MESSAGE : I22 Read Queue Timeout Loop


Anyone got any suggestions for what *db2-client* settings can be tweaked to workaround this?

I don't know the answer to your question, but does db2 generate any trap files when it crashes?

It is the DB2 CLP that crashes (db2.exe , while running a function inside DB2CLPFP.dll).

The remote database remains unaffected.

Yes the db2 CLP creates trap file each time it crashes (nnnn.nnnn.trap.bin) ,and I can see the details from db2xprt, but those details are useless unless you have source code.

The main thing I'm seeking is workarounds.

Yes, it's useless without source code, but it may help find a known bug. Can you post db2xprt output here?

Resolved by applying fixpack-7 of the client package for v9.7.