All

I have got an error initially and we trapped it as

************************************************
WFREPORT ID=EANXPOHR 0 NUMBER OF RECORDS IN TABLE= 1 LINES= 1 0 NUMBER OF RECORDS IN TABLE= 1
LINES= 1 19-JUN-07 1 0 NUMBER OF RECORDS IN TABLE= 29684 LINES= 29684 0 (FOC441) WARNING. THE FILE EXISTS AL
READY. CREATE WILL WRITE OVER IT (FOC437) THE FORMAT USED WITH FIXFORM IS INCOMPATIBLE WITH THE DATA FORMAT E06 /CP08 BY
PASSING TO END OF COMMANDWebFOCUS Version 7.1.4 compiled and linked on Wed Sep 13 14:59:05 EDT 2006 (Gen branch714_hotfi
x:12)
************************************************

But when we tried to recreate the same, we cant recreate the same error . . The reports came good . Further we have no idea about this error . . .
So If any one of you have any idea of this error please post your assumptions so that it will help for my further investigations .

The basic translation is that the procedure EANXPOHR has an ON TABLE HOLD FORMAT FOCUS (as ffName?) in it. A FOCUS file of the same name, HOLD or ffName, was found and was overwritten, the CREATE message.

During the load of the data into the FOCUS file, which is a MODIFY procedure, the 6th column of your TABLE request, E06, a packed field, had a piece of data that was not considered to be packed, the FORMAT error message that caused the process to fail.

Some things to consider. Was the 6th column a packed field? Was there another hold master being referenced in the path? Was there a data problem?

So Alan is that like , before creating a hold file ABC in a particular location , if a hold file in the same name exists , the creation will try to modify the existing hold file ?

Or it will delete the existing hold file and try to create the new one ?

It should use the HOLD mas and ftm it created of course, but if it finds anything prior to that in the path, it would use that.

This is, of course, speculation.

I experience that more in our mainframe days of FOCUS. Normally the message is given and the master recreated. Problems do come up though if you use the same hold file names and have not cleared your browser temporary files in a while. It's as if the WebFOCUS engine is saying 'oh you already have a file of that name, I think I'll just use it.'

If you've issued an APP HOLD along the way your master file description could be sitting out there in the path causing you problems. Another master file that could be on the path causing problems is FOC$HOLD.

Loading a FOCUS hold file is a two step process... create a flat hold file called FOC$HOLD and then the MODIFY into the final FOCUS hold table.