Re: [U2] update: PICK Systems Administrator position
Probably :^) The name I got was Address -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Mecki Foerthmann Sent: Thursday, April 07, 2011 7:08 AM To: U2 Users List Subject: Re: [U2] update: PICK Systems Administrator position Why? Are you one of the recruiters trying to poach Joe's client?:-) On 07/04/2011 12:32, Address wrote: Can someone close this thread ? --- On Thu, 4/7/11, Joseph Chelston j...@bsgstaffing.com wrote: From: Joseph Chelston j...@bsgstaffing.com Subject: [U2] update: PICK Systems Administrator position To: U2 Users List u2-users@listserver.u2ug.org Date: Thursday, April 7, 2011, 7:15 AM For the recruiter(s) that have been responding to me purporting to be candidates, please get a life. It's a real shame that you some would have to respond to a real job posting using the stolen identities of other professionals from this group just to try to steal my opening. Not only is it unethical, I believe it is illegal. I will do whatever is necessary to identify you and let the real person know how their name and identity is being used. I'm confident that there will be legal consequences for your actions. If anyone from this group can give me feedback, I'd appreciate it. This isn't funny. It's actually very sad. Regards, Joe ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
RE: [U2] Need help connecting to Universe and querying via SQL Server 2005 Management Studio
You can connect to most any database with adhoc views or a linked
server. You'll need the odbc drivers installed but once you have those
use openrowset or openquery to create views into the database.
Simple Examples:
CREATE VIEW [view name here]
SELECT Rowset_1.* FROM OPENROWSET('MSDASQL', '{servernamehere}'; '{logon
account}'; '{password}', '[sql command here]') as Rowset_1
Or Create a linked server and:
CREATE VIEW [view name here]
--SELECT Rowset_1.* FROM OPENquery([linked server name], '[sql command
here]') as Rowset_1
Steven R. Christensen
DBA, AMSOIL INC.
[EMAIL PROTECTED]
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
[U2] VSG view error
I was trying to add a column to the sql views that we have setup and received the following error: Died in UCI::SQLExecDirect() with SQLSTATE S1000, Native error:0 [IBM][SQL Client][UNIDATA]Dictionary location has conflicting SM specifications. Can anyone tell me what the error means and what I can do to correct? Thanks, 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 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] resolving udt error message
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/
[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. 925 Tower Ave. Superior, WI 54880-1527 [EMAIL PROTECTED] ph: 715-392-7101 ext. 6385 cell: 218-213-4161 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] udt problem
Thanks, Colin and to everyone who offered suggestions. Most of these I have been through including the IBM docs I have access to but Colin's suggestion about another service issue may be a clue to the problem. I am giving myself a crash course in unidata since I am only familiar with the more common relational database apps and I have a critical system that runs on unidata but support options for this are limited so I am not particularly familiar with the platform at this point. If the licensing does not have the Device License option would that disallow running the udt command line on the local machine? I have setup a script to run and extract the data to text files but without the ability to start the udt session locally I am not able to run the program. I was also looking at perhaps finding a way to run it as a phantom process but am not sure on the syntax on that and whether or not I can bypass the udt command in that fashion. Thanks for all the help. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, November 08, 2006 11:21 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] udt problem Seconded. If you're still having trouble - make sure UD is licensed. I think it shows up in the smm.log if it's not. UniAdmin or confprod will show if it is or not. If it is licensed; have you installed new software recently? 5.1.27 is rather old so I'm assuming you've had it running for a while. We've had problems with another service (windows management something or other) that would grab one of the memory handles. However, it would allow UD to start on a reboot - but wouldn't let you stop and start it (without rebooting). I used tools from www.sysinternals.com to find the offending service. hth Colin Alfke Calgary Canada From:Bill Haskett Steve: You might want to check out: http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0409ter hune / It's pretty good. :-) Bill -Original Message- From: Christensen, Steve Thanks for the suggestions. Unfortunately getting the following when forcing the shutdown: Attach shared memory fail. stopud failed. The Unidata service cannot be stopped. Reboot does not fix the problem either. [demime 1.01d removed an attachment of type application/ms-tnef which had a name of winmail.dat] --- 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/
RE: [U2] udt problem
I've burned up any urge to become frantic years ago :^) Licensing is fine on the machine. I've verified it as I accidentally invalidated it and had to obtain a new authorization code the other day. The smm is running, just getting a failure on the udt command line so I suspect some system issues that need to be addressed. The system has been running for several years with no maintenance. I believe it has been accumulating maintenance issues and data transfers via odbc have become rather slow and cause some cross-department locking issues which is what I am working on addressing. Did you shut down the instrumentation service and the driver extension service that goes along with it? I suspect I will need to review and shut down all unnecessary services to find the culprit on this problem. Thanks Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, November 09, 2006 9:14 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] udt problem No problem. The device licensing is for being able to connect to the server multiple times from the same machine but only use 1 license. It won't prevent you from connecting from the console. Does it actually say it's licensed? Did you perhaps load UD locally about a month ago? If smm is not running then no-one would be able to connect. If it's a critical system I would expect you to be a lot more frantic. The service I've had problems with is Windows Management Instrumentation Service; however, it let UniData start on the reboot. A phantom simply lets the udt process run in the background. You will still need smm running. It's pretty easy to use: from the command line you simply enter PHANTOM command Note that the process will go through the login voc item and the process will abort if it stops to ask for input. Hth Colin Alfke Calgary Canada -Original Message- From: Christensen, Steve Thanks, Colin and to everyone who offered suggestions. Most of these I have been through including the IBM docs I have access to but Colin's suggestion about another service issue may be a clue to the problem. I am giving myself a crash course in unidata since I am only familiar with the more common relational database apps and I have a critical system that runs on unidata but support options for this are limited so I am not particularly familiar with the platform at this point. If the licensing does not have the Device License option would that disallow running the udt command line on the local machine? I have setup a script to run and extract the data to text files but without the ability to start the udt session locally I am not able to run the program. I was also looking at perhaps finding a way to run it as a phantom process but am not sure on the syntax on that and whether or not I can bypass the udt command in that fashion. Thanks for all the help. Steve --- 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/
RE: [U2] udt problem
Excellent! Thanks for the details. This should help narrow my focus on the problem. I suspect your right about the service issue. It definitely make sense. Thanks for the tip on the sysinternal tools. Those have some fantastic view into the processes and I can see a lot of use for other purposes on that. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, November 09, 2006 12:29 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] udt problem Our problem with WMIS was that UniData would start on a reboot of the server, but if you stopped UD it wouldn't restart unless you rebooted. Until I found the conflict with the WMIS service. Then I stopped the WMIS service, stopped and restarted UD - which worked fine, and then restarted the WMIS service. I used the process explorer from www.sysinternals.com to find an smm handle being held by the WMIS service. If it's only udt on the console that is giving you the problem - are you sure you're in a valid account when you start udt, or maybe the pathing is messed up? Sorry, I'm not much more help here - I always use telnet (SBClient) to connect. Can you use telnet? Hth Colin Alfke Calgary Canada -Original Message- From: Christensen, Steve I've burned up any urge to become frantic years ago :^) Licensing is fine on the machine. I've verified it as I accidentally invalidated it and had to obtain a new authorization code the other day. The smm is running, just getting a failure on the udt command line so I suspect some system issues that need to be addressed. The system has been running for several years with no maintenance. I believe it has been accumulating maintenance issues and data transfers via odbc have become rather slow and cause some cross-department locking issues which is what I am working on addressing. Did you shut down the instrumentation service and the driver extension service that goes along with it? I suspect I will need to review and shut down all unnecessary services to find the culprit on this problem. Thanks Steve --- 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/
RE: [U2] udt problem
Not sure that this would apply since it's on a windows machine and the problem doesn't have anything to do with upgrading. I've run the command in several locations just to be sure that I tried every valid directory at both the account level and the system level but same results. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Angelo Collazo Sent: Thursday, November 09, 2006 1:37 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] udt problem Ron is correct, Do a cd $UDTBIN then do the tar -xvf and then updatesys. Cheers, Angelo Collazo System Administrator Long shot but this happened to me once. The tar file must be untar'd from the udt directory, not your upgrade directory. Its meant to over right some things. Ron Sharcott (3635) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christensen, Steve Sent: Wednesday, November 08, 2006 3:23 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] udt problem Thanks for the suggestions. Unfortunately getting the following when forcing the shutdown: Attach shared memory fail. stopud failed. The Unidata service cannot be stopped. Reboot does not fix the problem either. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Derwin Sent: Wednesday, November 08, 2006 4:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] udt problem Did you try stopud -f? That will force UD to stop even if it thinks users still have Unidata sessions running. If that doesn't work, sounds like you need to reboot the server. Note that these suggestions are only recommended as a last resort, as you run the risk of corrupting your data. Good luck, Tom [EMAIL PROTECTED] 11/08/06 4:13 PM Can anyone tell me what to do about this problem: Trying to start udt from command line generates the following error: Start SMM first! This is on Unidata 5.1.27 running locally. Tried startud but it is running and stopud refuses to stop it. Thanks, Steve --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ - This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the LabCorp Privacy Officer at [EMAIL PROTECTED] or call (877) 23-HIPAA / (877) 234-4722. --- 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/ --- 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/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] udt problem
Can anyone tell me what to do about this problem: Trying to start udt from command line generates the following error: Start SMM first! This is on Unidata 5.1.27 running locally. Tried startud but it is running and stopud refuses to stop it. Thanks, Steve --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] udt problem
Thanks for the suggestions. Unfortunately getting the following when forcing the shutdown: Attach shared memory fail. stopud failed. The Unidata service cannot be stopped. Reboot does not fix the problem either. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Derwin Sent: Wednesday, November 08, 2006 4:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] udt problem Did you try stopud -f? That will force UD to stop even if it thinks users still have Unidata sessions running. If that doesn't work, sounds like you need to reboot the server. Note that these suggestions are only recommended as a last resort, as you run the risk of corrupting your data. Good luck, Tom [EMAIL PROTECTED] 11/08/06 4:13 PM Can anyone tell me what to do about this problem: Trying to start udt from command line generates the following error: Start SMM first! This is on Unidata 5.1.27 running locally. Tried startud but it is running and stopud refuses to stop it. Thanks, Steve --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ - This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the LabCorp Privacy Officer at [EMAIL PROTECTED] or call (877) 23-HIPAA / (877) 234-4722. --- 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/
