Thanks to everyone for the instructions. This is what I suspected would need to be done but the syntax was eluding me on the editor and the help files did not have enough detail.
It looks like I may have an issue with the original home account for the system. The current home path "e:\unidata\ud51" seems to be missing files that appear under most of the other accounts. Can you tell me where the default home location is created normally for the system (5.27 is the version we are using)? I am getting a failure from the UDT (eg - can't get to msgq in U_tosbcs) in accounts that are located outside the directory that the home account is set for in the environment variable which is causing me a problem getting to the editor. If I can find the global catalog files then I think I can get all of this fixed and working properly. Thanks for your help. Steven R. Christensen DBA, AMSOIL INC. 925 Tower Ave. Superior, WI 54880-1527 [EMAIL PROTECTED] ph: 715-392-7101 ext. 6385 cell: 218-213-4161 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Susan Lynch Sent: Tuesday, September 18, 2007 5:06 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] resolving udt error message From: "Christensen, Steve" <[EMAIL PROTECTED]> Subject: [U2] resolving udt error message > Can anyone clue me in on how to resolve this error (step-by-step)? > > When going to the command prompt and starting udt I receive the > following error: > > UniData Release 5.1 Build: (2189) > Copyright (C) Ardent Software, Inc. (USA) 1998 > All rights reserved. > > Current UniData home is e:\unidata\ud51\. > Current working directory is E:\JENKON\SV\AMI_SQL. > Warning: global CTLGTB file path(VOC pointer file) is different than > current > Unidata home path, cannot global CATALOG/MAP in this udt session. > : > > This is an install of an existing system onto new servers and I am > trying to clear up the command line issues. > > Thanks for any insight you may have on this. > > > Steven R. Christensen > DBA, AMSOIL INC. Steven, At ECL (the colon prompt you show above) after you get that error message, type CT VOC CTLGTB, and compare the path in the line after the line with a single F (which will be something like \unidata\ud51\sys\CTLGTB - you want to look at everything up to the \sys\CTLGTB) to the path in the message above (e:\unidata\ud51\). I have found that omitting the drive letter, even if it technically points to the same place, will result in that error message. Example: CT VOC CTLGTB CTLGTB: F \unidata\ud51\sys\CTLGTB \unidata\ud51\sys\D_CTLGTB The system will pull \unidata\ud51, which, when compared to the UDTHOME e:\unidata\ud51, will result in that error message. To change the VOC pointer for CTLGTB, you can AE VOC CTLGTB, hit enter twice to get to line 2, then R2/whatever-the-wrong-path-is/@UDTHOME (eg R2/unidata\ud51/@UDTHOME) After that, you should see something on line 2 like @UDTHOME\sys\CTLGTB and line 3 should be @UDTHOME\sys\D_CTLGTB - type FI to save it, and then type LOGIN to go through the login procedure again and verify that you do not get the error. The advantage of using @UDTHOME in the path is that you will never have to fix the path in the file pointer again if you move machines - it will use the @UDTHOME to pull in the matching path. Susan Lynch F.W. Davison & Company, Inc. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
