Why are you using ENVINIT in the second one when you are using the udt to get into UniData? Change ENVINIT to TIME on the second one and see what happens.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kim, Stephan Sent: Thursday, June 24, 2004 3:27 PM To: '[EMAIL PROTECTED]' Subject: [U2] Question about udt at the unix level Hi, I was wondering if anybody ever came across this situation... I have a UniBasic program that has lines like this... TIME.OUT = 'UNMODIFIED' EXECUTE 'TIME' CAPTURING TIME.OUT CRT 'TIME.OUT : ' : TIME.OUT This will return the time...this is not the problem. The problem is that when I do this with something else (Datatel code) I run into a bit of a problem under certain scenario...(and I am hoping to get some insight or a pointer in the right direction) E.OUT = 'UNMODIFIED' EXECUTE 'ENVINIT' CAPTURING E.OUT CRT 'E.OUT : ' : E.OUT At the UniData level, I get the correct output "Envision Initialized...blah blah" At the unix level (udt RUN CUST.SOURCE TEST.PROGRAM), I get a null...(meaning E.OUT is getting overwritten with the EXECUTE statement) Anybody ever run into this or might know why I get different results from the 2 environments? Thanks, Stephan [EMAIL PROTECTED] ------- 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/
