Have you checked out NEWPCODE instead of NEWVERSION? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Gravagno Sent: Wednesday, September 01, 2004 9:10 PM To: [EMAIL PROTECTED] Subject: [U2] Unidata shared memory and catalogs
Platform is Unidata 6.0 PE over WinXP. I've been having a hard time doing development on subroutines when the main calling programs are running on active processes. This isn't live code, it's all development, but I'm trying to avoid stop/restarting the main code every time I change a subroutine. For some reason the main code is always executing the shared/cached object. I've tried cataloging globally and locally, using various combinations of DIRECT, LOCAL, FORCE, and NEWVERSION. I've made sure to DELETE.CATALOG/DECATALOG twice to clear the CTLG and I've watched the catalog files disappear through the Windows Explorer, so I know the object is going away, and that points to shared memory. I've tried the !NEWPCODE and !NEWVERSION commands to force a refresh with no joy. I've made sure that the NEWVERSION_USERS=ALL (or whatever that param is) was filed in the config record, because even my Administrator user was flagged as lacking the privs to use !NEWVERSION. The main routine is a client running through UniObjects. If that process itself does a recompile and recatalog, everything works. The problem is getting another process to refresh shared memory for the running (main) process. Can I just turn off smm while I'm in development? How? Thanks!! Tony ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
