"Darren Macdonald" <[EMAIL PROTECTED]> wrote on 12/22/2005 04:24:08 AM:
> We have been running (in the dark ages) on Unidata 3.3 and 5.2 (on SGI > Irix) for a number of years, and are considering moving up to Unidata 7 > - ideally on a Windows machine. You've gotten some good responses about O/S-level executables - I can't think of much to add to that. You also need to think about the following: 1) Do you have any device-specific settings in SETPTR commands? If so, they may need to be evaluated for the new platform 2) If you have any tape jobs, you may need to evaluate the device settings. 3) It may be necessary run convdata on the data files. 4) Because of skipping so many releases, you should rebuild all index files rather than run convidx. 5) You should recompile and - as necessary - recatalog all programs. Hopefully your source code is in good shape. 6) VOC pointers will have to be modified to accommodate the nomenclature for the new O/S. 7) If you're using CallC or CallBasic routines, they will have to be regenerated and relinked. It may be necessary to modify the source code, depending on what is being done. 8) In addition to hard-coded PCPERFORM and EXECUTE statements, you'll have to look at those that launch processes based on constructed strings. This applies not only to the commands themselves, but to parameters that may contain paths and other O/S-specific information. 9) Be on the lookout for variable names that have become reserved words. The compiler is generally smart enough to work things out based on context, but there is a possibility of confusion. 10) There could be problems with files that are being created on the fly, since they could be based on explicit paths. This includes CREATE.FILE, OPENSEQ, OSOPEN, etc. How many concurrent users are you planning on? Be wary of placing too many on Windows - if you hit the wall you quickly run out of scalability options. You're skipping many releases and implementing a new O/S and hardware at the same time. It goes without saying that you really need to test this thoroughly before going live. If something goes wrong it may be difficult to isolate causes. You may want to seek help from somebody who has gone through it before. (Hint, hint.) Tim Snyder Consulting I/T Specialist , U2 Professional Services North American Lab Services DB2 Information Management, IBM Software Group 717-545-6403 [EMAIL PROTECTED] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
