All Reports are generating Error 1324 on DG Alpha with 4GL 7.20 UD6 and ISDN 7.30FC8
Posted in 1999
Topics: Connectivity: ESQL/C, 4GL & Embedded SQL, Versions, Editions & End-of-Life
Hello, there is some strange problem with all our reports after recompiling our 4GL sources on DG Alpha platform with 4GL developement tools 7.20UD6 and IDS 7.30FC8 (coming from Siemens/RM series with 4.x tools and 5.x online). When writing to a report file, all reports will crash with error 1324 after having written part of the data. File sizes are completely different. There is enough space on the filesystem, ulimit for files is unlimited for the user. There are no operating system messages in the logs. I checked one report which generated customer lists. It´s about 80000 lines of output. This report works if i limit every output row to 110 or less chars. It crashes with more then 110 chars. This number depends on the number of output lines. Decreasing the number of output lines and you can print more then 110 chars. The file size when the problem happened is completely different. Some reports crash just at 800K, the above reports generates about 15M. Any idea? Greetings, Joerg
Joerg Spilker wrote: > > Hello, > > there is some strange problem with all our reports after recompiling our > 4GL sources on DG Alpha platform with 4GL developement tools 7.20UD6 and > IDS 7.30FC8 (coming from Siemens/RM series with 4.x tools and 5.x > online). When writing to a report file, all reports will crash with > error 1324 after having written part of the data. File sizes are > completely different. There is enough space on the filesystem, ulimit > for files is unlimited for the user. There are no operating system > messages in the logs. > > I checked one report which generated customer lists. It´s about 80000 > lines of output. This report works if i limit every output row to 110 or > less chars. It crashes with more then 110 chars. This number depends on > the number of output lines. Decreasing the number of output lines and > you can print more then 110 chars. The file size when the problem > happened is completely different. Some reports crash just at 800K, the > above reports generates about 15M. 4GL builds the reports in a temp table and then spools them from there to the printer or file. In IDS 7.xx temp tables are created, by default, in ROOTDBS unless they are created WITHOUT LOG and there are one or more temp dbspaces in which case they go there. It is possible that you are running out of space in ROOTDBS for the temp table. If you made the root dbspace the same size it was under 5.xx and it was smallish then the extra overhead of IDS 7 and the sysmaster and sysutils databases in rootdbs may be leaving less for temp tables than you had before. Art S. Kagel
"Art S. Kagel" wrote: Hello, > 4GL builds the reports in a temp table and then spools them from there to the > printer or file. In IDS 7.xx temp tables are created, by default, in ROOTDBS > unless they are created WITHOUT LOG and there are one or more temp dbspaces > in which case they go there. It is possible that you are running out of > space in ROOTDBS for the temp table. If you made the root dbspace the same > size it was under 5.xx and it was smallish then the extra overhead of IDS 7 > and the sysmaster and sysutils databases in rootdbs may be leaving less for > temp tables than you had before. the reason was more strange. It seems to be a problem with 8 Bit characters in the report. See me new message. Greetings, Joerg