Simon, Thanks I will give it a try.
Rich
At 03:34 PM 9/3/2004 +0100, you wrote:
Tony
For non-Uniobjects sessions...
You need to
PCPERFORM 'newversion n'
where 'n' is the pid of the running process to get that pid to pick up any changed s/w. This works whether the s/w is locally or globally cataloged as far as I can see - so I don't know what the shared memory reference in the manual means.
The manual says a number of things about NEWPCODE and its effect - the true bit is where it says the NEWPCODE only effects the session that runs it.
ie both newversion and NEWPCODE are equivalent to dropping to ECL and re-starting a program - newversion for other sessions, and NEWPCODE for your own session.
I've just checked this with a uniobjects session for UD 6.0.12 on Windows and newversion doesn't seem to work. You might want to log this with IBM support to confirm that this is indeed the case. However, executing NEWPCODE from the uniobjects session does make it pick up new code. While developing can you put an EXECUTE 'NEWPCODE' in a uniobjects sub that will get called regularly (perhaps your session load/save; a logging sub etc)?
Note to Richard Sammartino: Putting EXECUTE 'NEWPCODE' in your menu program loop should solve your issue.
Simon
------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
Richard Sammartino
Systems Analyst
Information Technology
School District of Philadelphia
734 Schuylkill Avenue
Philadelphia, PA 19146-2397
Phone: (215) 875-4734
Fax: (215) 893-4243 -------
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
