Rebecca: Thanks for the script suggestion. kmbodine: I used the example of TIME because I figured that everyone has that on their system (and the output from that is captured at both levels). I used the ENVINIT example (a Datatel specific example) because it is similar to a situation that I was experiencing (where output was not being captured at the unix level). In the acct that I am working with, ENVINIT is not part of the LOGIN so the ENVINIT is not redundant...if that is what you are eluding to by saying 'Why are you using ENVINIT...when you are using udt to get into UniData'. At the unix level you can type something like: udt RUN CUST.SOURCE PROGRAM...and it will process but not keep you logged in. (this is what I mean by udt at the unix level.)
Anyway, I did manage to get my original issue resolved. But I would still be interested in some insight as to what would cause the CAPTURING clause to not capture at the unix level (yet capture at the UniData level). Thanks, Stephan Date: Tue, 29 Jun 2004 20:10:10 -0700 From: "Rebecca Corson" <[EMAIL PROTECTED]> Subject: RE: [U2] Question about udt at the unix level At the Unix level we do it like this using a script. UDTBIN=/usr/ud60/bin UDTHOME=/usr/ud60 export UDTBIN UDTHOME cd /datatel/live/collive echo PARANAME | $UDTBIN/udt >./_PH_/OUTPUT.NAME 2>&1 Where PARANAME is any paragraph. The paragraph can call a UniBasic program. Rebecca Corson Another Datatel Client - -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of kmbodine Sent: Tuesday, June 29, 2004 8:40 AM To: [EMAIL PROTECTED] Subject: RE: [U2] Question about udt at the unix level 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. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
