A trap we fell into when converting from UniData to UniVerse was to run that excellent utility PORT.STATUS. This is extremely debilitating to UniVerse and should be restricted to only essential operations. Currently we are looking at converting UniVerse from AIX to W2K3. This is making us look at how things are done in our applications. We have noticed a number of situations where we are making UNIX calls where there are built in UniVerse methods. This is a hangover from previous lives which I think started at Reality to UniData to UniVerse. There was also "ALL" as part of the mix. A recent small change to a program extended the running time greatly. Turned out a call to SP-ASSIGN (our modified version) was being made every time a record was read instead of only if it were to be printed. This is very slow and I believe involves OS system calls. We have also noticed a very high level of system calls, but that was also on our previous Sequent hardware - so maybe it is our app not UniVerse or AIX. What I am trying to say is that by converting from D3 you may have extensive performance hits in your application code, which is not obvious. We are intending doing a lot more research into what our application is doing, especially as it interacts with the OS. This may be our greatest benefit from investigating the W2K3 route. Sara Burns (SEB) Development Team Leader
Public Trust Phone: +64 (04) 474-3841 (DDI) Mobile: 027 457 5974 < <mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED]> Information contained in this communication is confidential. If you are not the intended recipient the information should not be used, disclosed, copied or commercialised. The information is not necessarily the views nor the official communication of Public Trust. No guarantee or representation is made that the communication is free of errors, virus or interference. -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
