7 replies to this topic

[Donald Rossoll]

I get error code 18 on an update using mode B. The first two records are added correctly to the file being updated, but the third record already exists and should be changed, but I get error code 18 which stops in gui mode. If I change the mode to C for the third record, I get no error. Red Hat 6.1 and ProIV 4.6. Any suggestions??

[Vlodik Zmyslony]

I suggest that you capture the keys in a scratch variable on ARNE and reset these in BW logic. I'm assuming your error is in the write cycle!

[Chris Pepper]

PRO-IV has never required the keys to be reset on Before Write so I doubt if this is the problem.
Which file system are you using?
Were other processes active and was the record added by one of those or do you know it was on file before running this function?

[Donald Rossoll]

I tried saving & restoring the keys and you are correct in that it didn't work. I am using the standard Pro-IV files and have five files defined. The first two are lookup mode and the keys are set in the update default logic. The next three files are mode B, (all the same file). In other words, I am reading one record, and writing three from that one. The third write has the same key as the first and gives me an error. In this instance, when I change the mode from B to C, I don't get the error. Thanks

[Steven Torrance]

Donald,
I think the key point here is that you are trying to add 3 records to the same file.
When ProIV reaches the read of file 3, file 1 has not yet been written (and committed) and so it assumes that the record is new. Unfortunately, the information is out of date by the time ProIV comes to write file 3.
There are three solutions
1. Change file 3 to mode C (probably not possible by the sounds of things)
2. Write 2 separate updates to write the records.
Best solution:
3. Integrate the update of file 1 and file 3 with some sort of condition statement in before write, where it only does the update from file 3 on file 1 if the condition is true (and a dself on file 3 ARNE if this same condition is true, hence preventing any duplicates).

example:
Before write of file 1:
if key_1 = key_3 then
update from file 3 done on file 1
endif

ARNE of file 3:
if key_1 = key_3 then dself endif


I have experienced similar problems in other programming languages, and so it is probably not a ProIV bug!

[Rob Donovan]

Another possible solution would be to put a control break in.

If you have a control break that is based on all the keys to the primary file (ie every record) and only write file 3 on this control break it will change the timing cycle to make sure that the first file is written before the third file is accessed.

Rob D

[Steven Torrance]

Woops - spot the deliberate error. The code done on ARNE of file 3 should also be done on After Read Error!

[Donald Rossoll]

I ended up redesigning the function with a temp file. Originally, I had one file with 12 fields, each with a gl number and amount. I was trying to write the twelve gl numbers and create a new record or update an existing record with the amounts. I set a temp file with 12 records and then updated the amounts and it works fine. Thanks for all your suggestions.