Rodney: Thanks. I was thinking this was true. U2 does allow direct reference to an O/S path from within BASIC, e.g:
OPEN 'DOS:E:\IBM\ud71\sys\BP' TO BP.FV ... (in D3) OSOPEN 'E:\IBM\ud71\sys\BP' TO BP.FV... (in UD) OPENPATH 'E:\IBM\ud71\sys\BP' TO BP.FV... (in UV) I can do this (assuming I have permissions) in DOS or Linux by: >dir e:\IBM\ud71\sys\BP or #ls -al /ourdir/ourbankdata D3 allows such direct O/S reference from TCL, like: :LIST DOS:E:\IBM\ud71\sys\BP or :LIST UNIX:/ourdir/ourbankdata Or to a file within a different D3 account by: :LIST PAYROLL,EMPLOYEE,2004, or :LIST DM,BP, This would one less layer of "stuff" we'd have to go through when installing and configuring our application and I'm thinking: less is more (or where is the MV2006 standard). :-) Thanks again. Maybe this would be a good enhancement request. :-) Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Baakkonen, Rodney A (Rod) 46K > Sent: Thursday, January 19, 2006 1:15 AM > To: 'u2-users@listserver.u2ug.org' > Subject: RE: [U2] [UD] Referencing remote file directly > > Sorry late night. I did not see you want to do a LIST using > the full path. > You do need a VOC pointer in Unidata. Even ecltype u says a > direct reference is not a file name > > list /mccdata/mcc13/CLM.DETAIL > Not a filename : > /mccdata/mcc13/CLM.DETAIL > > Sure, you can use full paths in attribute 2 or 3 of Unidata > VOCS. We make extensive use of @UDTHOME on our dev box. We > have a development env, Systems and Acceptance, End To End > and a training environment on the same server. We have a UNIX > shell script that prompts a logged in user which environment > they want to go to. From a maintenance stand point, the VOC's > for all these environments are the same, using @UDTHOME. But > the shell script sets a different $UDTHOME, so each > environment has its own unique sets of the files. To see what > your UDTHOME home is set to, do a !echo $UDTHOME at ECL. > > Hardcoded paths would make the maintenance of these > environments a major headache. So I see @UDTHOME as a major > blessing. - Rod > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Mike Preece > Sent: Thursday, January 19, 2006 2:15 AM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] [UD] Referencing remote file directly > > > I think not. This is often mentioned as one of the > differences. I assume you'ved used indexinfocus to search? > > > > >From: "Bill Haskett" <[EMAIL PROTECTED]> > >Reply-To: u2-users@listserver.u2ug.org > >To: <u2-users@listserver.u2ug.org> > >Subject: [U2] [UD] Referencing remote file directly > >Date: Wed, 18 Jan 2006 20:57:32 -0800 > > > >I can't find the old discussions of this but can one > reference a remote > >file > >directly in UniData. For instance, can I: > > > >:LIST D:\IBM\ud71\sys\VOC > > > >instead of needing a link like: > > > >001 F > >002 @UDTHOME\sys\VOC > >002 @UDTHOME\sys\D_VOC > > > >? > > > >Any help would be appreciated. :-) > > > >Bill Haskett ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/