> From: Richard Sammartino [mailto:[EMAIL PROTECTED] > Tony, I have experienced the same issues and I don't think there is a > solution. Our menu is a cataloged program which chains or > executes other cataloged programs.
I don't know about the performance impact, but a TCL stacker program has the same problem. I do an EXECUTE 'NEWPCODE' after compiling a program to get the 'refreshed' version available immedidately. As others have noted, this works only for the process executing the command. As for the wisdom of the Unidata developers, I have to say it's better than working on old PICK systems where compiling a new version of a program or subroutine would cause anyone running that routine to bomb out to the debugger. I have vivid memories of an error routine that used TIME() as part of the key, and therefore had to loop doing READU's to make sure the key was not in use. I.e it could only write one error log per second. One inventory weekend, at 10pm on Saturday, calculating how long it was going to take to finish returned 5 days! Changing the routine to use a sequential key was quick, but recompiling it live, knowing that if the timing was wrong we'd have to restore to Friday's backup and start over was nerve wracking to say the least :-) This was Ultimate on an IBM 3090. Is today old fart's memorial day or something? ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
