|
Why not just try doing a CpyFrmQryF to a temp file in Qtemp after the OpnQryF then doing the OvrDbf to the temp file? Bob Cagle -----Original Message----- From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On Behalf Of Frank Kolmann Sent: Sunday, March 19, 2000 5:10 PM To: RPG400-L@midrange.com Subject: Re: FW: Quest for you/midrange-l I have a program/s that does what Henrik is trying to do. I also had the problem. I needed to put in a tricky/nasty kludge. It involves a LOT of indicators. Use the Field/Record Relation Ind column. Split up the I/specs into arbitrary fields. Following is a small sample of the code. Get the actual record length (incoming parm?) Set on enough indicators to cope with the record. Even so I did not have enough indicators. So I needed 3 programs pgma covered 1-3000, b) 3000-6000 c) 6000 - 9000 IINPUTK NS 01 I 1 16 DA I 17 32 DB 55 <pos 63/64 I 33 64 DC 56 I 65 96 DD 57 I 97 128 DE 58 I 129 160 DF 59 I 161 192 DG 60 I 193 224 DH 61 I 225 256 DI 62 I 257 288 DJ 63 I 289 320 DK 64 I 321 352 DL 65 I 353 384 DM 66 I 385 416 DN 67 I 417 448 DZ 79 I 449 480 DO 68 I 481 512 DP 69 I 513 544 DQ 70 I 545 576 DR 71 I 577 608 DS 72 I 609 640 DT 73 I 641 672 DU 74 Frank Kolmann "Shaw, David" wrote: > Does anyone have an answer for Henrik? I've long known there were > limitations> on this kind of thing, but I've never analyzed it the > way he has, nor have I ever found documentation on it. Thanks! > > Dave Shaw > > "I have an RPG that should read or update 'any file', so the file is > defined: > > 'FUPDAT UF F 9999 DISK' > > It works fine with an other CL program: > OVRDBF UPDAT THISLIB/THISFILE SHARE(*YES) > CALL RPGPGM > > But as soon as I change the CL-program to > OPNQRYF THISLIB/THISFILE ... > OVRDBF UPDAT THISLIB/THISFILE SHARE(*YES) > CALL RPGPGM > > then the RPGPGM gives MCH0601 (Space offset X'00001460' is outside > current limit for object &1) when moving from buffer into the 9999 > bytes input field (DS). > > The actual file used for testing has a record length of 141 bytes. > It worked fine when defining the file as 150 bytes, so I did a > 'binary change-record-length-recompile-retest' to find, that it > worked for a record length of 3248 bytes but not 3249 bytes. > > What happends? Where is this limit documented?" > > Regards > > Henrik Krebs IMA/D23 +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.