Does anyone know if code has tightened or changed for MODIFY FILE....FIXFORM in 8.2.01?
I was using this code recently in 8.0.09
APP ENABLE
APP HOLDMETA DB2TABLES
SET TRACEOFF = ALL
SQL DB2
END
-*
MODIFY FILE RGVITAL_ERA4135FF
FIXFORM FROM RGVITAL_ERA4135FINB
DATA ON RGVITAL_ERA4135FINB
END
-*
SQL
COMMIT;
END
APP HOLDMETA

and it has always worked. Now in 8201 I get a Reporting Server error and says "Too Many Messages" But I don't know what that means.

thanks

This message has been edited. Last edited by: BobV,

Something to try for diagnostic purposes...

Can you add a START/STOP to your MODIFY, so that only the first few input records are dealt with?

Then, hopefully, you won't get the server crash, and will be able to see the real error messages in your SYSOUT/View Source.

Something like...

MODIFY FILE n
START 1
STOP  3
FIXFORM..  

(Guessing you are getting an error for every input record, and your input file is big.)

I did the START/STOP at 3 and ran fine. Then tried 1000. Did not work.
DB2 table started with about 5,000 records. Each of the past two months added 4,000 more. This month has ~3,900 to append. When using 8.0.09, I've surpassed these volumes on other projects.

Is there a set command to see a SYS output?

thanks for the help.

My guess is that there is now a difference in the format of some fields, but that will be shown in the messages.

You should also check the format of the fields in the two files, RGVITAL_ERA4135FF and RGVITAL_ERA4135FINB.

Can you run a TABLE request against RGVITAL_ERA4135FINB?

I'm pretty sure most of the HOLD FORMAT blahblah is still using MODIFY and FIXFORM FROM DATA ON syntax.

Anything in the edaprint?

quote:

I did the START/STOP at 3 and ran fine. Then tried 1000. Did not work.

OK, that is useful information, that the first few records work, and at some point, in reading the input file, something goes awry.

There a several things to check, regarding the input/HOLD file. (Guessing you created the input file via a previous ON TABLE HOLD command given your MODIFY FILE code.)

For example, are any of the formats/lengths changed from the scenario that works, to the scenario that does not.

Are there more or less fields in either HOLD file?

When you TABLE the HOLD file, does the report look OK?

Are the MASTERs for the DB2 table you are modifying the same in terms of structure?

For sure, now that you aren't getting the server crash, you should try to find the messages from the run of the MODIFY.

If it is WebFOCUS, you should see the messages on the web page that pops up, or do a view source, to see them.

On z/OS batch (sadly it has been a while so just guessing :-)) you should see a JCL card something like-ish '//SYSPRINT DD SYSOUT=A' that points to where the messages are going.

This message has been edited. Last edited by: David Briars,

Thanks to all who responded. I just could not get anything to work, so did something different since this was the last month I needed to update my table.
I'm going to see if I continue to have this problem with other projects.
1) this project was started using Dev Studio 8.0.09 and finished running in App studio 8.2.01 Not sure if that has any effect.
2) I have added a "key" field to my process in which I will use ON NOMATCH INCLUDE syntax. Again, not sure if that has any effect.