DB2 SPUFI error message

Hi,

Not sure, if this is the place to ask help for DB2 related stuff. Anw, here it goes…

Normally I use QMF for DB2 queries but now I needed a way to run multiple simple update queries on DB2. SPUFI turs out to be the right tool for it.

It sort of works when I put few lines (queries) in it. Then, when I placed more queries (say ~500 lines) into that file and execute it, I get an error message that I don’t fully understand.

Maybe someone from here can read some sense out of it?

IEC030I B37-04,IFG0554A,USRMS90,LGALL,SYS00012,D828,A9D828,USRMS90.MSRA
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=B37  REASON CODE=00000004
 TIME=13.15.43  SEQ=06829  CPU=0000  ASID=0084
 PSW AT TIME OF ERROR  075C1000   80E28CB6  ILC 2  INTC 0D
   NO ACTIVE MODULE FOUND
   NAME=UNKNOWN
   DATA AT PSW  00E28CB0 - 41003846  0A0DB20A  00509808
   GR 0: 00E28EC0   1: A4B37000
      2: 00064EFE   3: 00E2867A
      4: 009AB208   5: 00E3E000
      6: 009AB4AC   7: 009AB504
      8: 009AB4CC   9: 009AC568
      A: 00F908B0   B: 009ABFA8
      C: 009CB3AC   D: 00000008
      E: 00E28ADC   F: 00000004
 END OF SYMPTOM DUMP
Abend B37000 hex occurred processing command 'DSN     '.
***

Queries itself are as simple as they can be. For example:


UPDATE AS9.V9BM21 SET ARTGRUPP=13 WHERE ARTNR='10030039';
UPDATE AS9.V9BM21 SET ARTGRUPP=11 WHERE ARTNR='12133047';
UPDATE AS9.V9BM21 SET ARTGRUPP=11 WHERE ARTNR='12133054';
UPDATE AS9.V9BM21 SET ARTGRUPP=11 WHERE ARTNR='12133062';
UPDATE AS9.V9BM21 SET ARTGRUPP=11 WHERE ARTNR='12133070';
UPDATE AS9.V9BM21 SET ARTGRUPP=11 WHERE ARTNR='12133088';

Thanks,

boy, it’s been decades since i worked on a mainframe, but i seem to recall that B37 means you’ve run out of disk space

even if rudy hadn’t piped it, i probably would have guessed an out of memory condition. that error looks like a stack trace, meaning an error occurred in the SPUFI program that is either a bug or an error condition that the programmers didn’t anticipate.

instead of 500+ update queries, i suggest creating a temporary table, loading your change data in to that table, then run 1 update query with a join to the temp table.