I have heard much about the code tightening for 7.6+, we are upgrading from 5.3 to 7.6.6 (or maybe 7.67). What problems should I plan for? Does anyone have specific examples of code that worked before that did not work after?

One I know for sure is the AYM and AYMD legacy date subroutines. A lot of my developers got nailed on this one.

In the past, contrary to the documentation, you could get away with specifying the 'outfield' in a smartdate format, e.g. YYMD.

The doc clearly states that 'outfield' can be either I6, I6YMD, I8, I8YYMD.

There should be other posts on the forum that list upgrade problems with your jump. We did it last October after months of user testing but we went with 7.6.2 after problems with ..0 and ..1. We are now at 7.6.5.

Also be prepared with some issues regarding html pages though alot of those were resolved by the time we got to 7.6.2 because of the multitude of cases I opened.

Have fun. It'll be a heck of a ride.

PB,
We are getting ready for a similar ride. We are in testing stage right now.. Let me know, as will I for you, re: any surprises or known issues.

Ginny - Thanks for the input, and as always, sooooo appreciated.

Ira
AIX 533 ProdClient 533, Server 538, Test 7.6.1 (CLIENT), 538 SERVER,

We moved from 5.3.3 to 7.6.4 early last spring. I don't have my notes handy but I remember getting hit with these.

SQL pass thought there can be no code between the semi-colon ";" and the "TABLE FILE SQLOUT". We had some DM code to get timings.

ON TABLE . . . FORMAT HTMLTABLE instead of HTMTABLE (the htmLtable is incorrect syntax)

Check out 762 snags on this forum.

Thanks for your replies. From what I have seen in previous posts it appears we may not come out too bad.