RE: [U2] problem with SQL Users
Not seen it, but I'm not up to date with releases. Can you map the user IDs through UV.LOGINS ? - Original Message - From: David Jordan [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Subject: RE: [U2] problem with SQL Users Date: Thu, 3 Apr 2008 15:05:42 +1100 I just upgraded to Uv ReLease 10.2.8 PE on my laptop. It does not recognise me as a sql user, even though the the login name is in UV_USERS. The difference is the user name in UV_USERS has the domain name in lower case, but if I do who the domain name is uppercase. This is the username that loaded Universe, so it should be the uv user. I suspect it is a bug, related to casing, as I am sure this was not a problem in the previous release. Has anyone come across this problem in the latest release Regards David Jordan --- 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] COMMON
Hi I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Any advice? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] COMMON
Sure You can and You don't have to have the named common in any other routine. The only gotcha I'm aware of is that the file stays open until you exit universe or explicitely closes it i.e. even if you LOGTO another acoount. It's quite confusing and potentially dangerous that the open file still points to the old account. -- mats Dennis Bartlett skrev: Hi I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Any advice? --- 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] COMMON
quote who='Dennis Bartlett' date='Thursday 03 April 2008' Hi I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Yes - I use this approach and it works fine. In short, I build a COMMON array with file handles and a dynamic array with the names of the open files. At first invocation, you need to check to see if the COMMON vars are initialized or not - if not, you initialize them. Once this is done I merely look for a filename in the dynamic array, if found it returns the file handle for I/O. If it's not present it opens the file, adds the filename to the list and you go on. At the end of the process, it loops over all open file handles and closes them. Depending on your application, you can figure out optimal places to open/close the file handles. -- Jeff Butera, Ph.D. Administrative Systems Hampshire College [EMAIL PROTECTED] 413-559-5556 Where I'm from, we believe all sorts of things that aren't true. We call it history. The Wizard, Wicked --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
And - as a suggestion - as mentioned earlier - the array of file names should contain ACCOUNT-FileName to ensure MainAcct-CustFile # TestAcct-CustFile -- it's happened more than once the DIM'd array of file handles survived a LOGTO and suddenly that person is trashing the MAIN account data thinking they are in the TEST account. We have a DIM(50) of file handles we carry around - I'm sure we could do 200 -- you're limited by the OS open files, but at the point you approach that, U2 usually 'soft closes' the file (closes at OS level, but remembers your handle and reopens on demand). Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? All the code on this site opens the file in the calling routine and passes the handle to the subroutine. I want to rather make the subroutine a stand-alone, not requiring more than the subroutine call added to the calling programs. I have a suspicion I can use named common - if so, does this have to be declared in the calling routine (which would negate my purpose!). Yes - I use this approach and it works fine. In short, I build a COMMON array with file handles and a dynamic array with the names of the open files. At first invocation, you need to check to see if the COMMON vars are initialized or not - if not, you initialize them. Once this is done I merely look for a filename in the dynamic array, if found it returns the file handle for I/O. If it's not present it opens the file, adds the filename to the list and you go on. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] COMMON
Here is a simple but effect way to handle this scenario: COMMON /NAMED_COM/ NAMED_COM.REC(10) EQUATE NAMED_COM.FLAG TO NAMED_COM.REC(1) EQUATE F.OPEN.FILETO NAMED_COM.REC(2) Etc. IF NAMED_COM.FLAG NE @WHO:@DATE THEN ;* Open Files, Set Variables and NAMED_COM.FLAG if everything is OK. GOSUB INIT.NAMED.COM END --- If you are concerned about closing files or deleting a temp file or record then you can call your subroutine with a Final call via a Call Type argument. Normally this Call Type would be I for Initializing, N for Normal, F for Final. Thanks, David A. Green www.dagconsulting.com (480) 813-1725 -Original Message- I have a subroutine that WRITESEQ to a record in a type 1 file called INTEGRITY. Is there anyway I can open the file once (in the subroutine) and thereafter use the same file handle (to avoid opening the file each time the subroutine is called) ? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] UniData and Unicode
All, We're running Unidata version 7.1, and are trying to get a pc-based id card system (Idworks) to communicate via ODBC to our database; we are having limited success. The software vendor said they thought it was a Unicode compliance issue. I've found some marketing docs for U2 which indicates it is supported, but could find nothing in the Unidata docs which indicates if this compliance is the default, or if it is something to be enabled for either the database or the ODBC driver. Any provided information would be greatly appreciated. Drew msulogobw-smallDrew Henderson Director, Computer Center Operations 110 Ginger Hall Morehead State University 606/783-2445 [demime 1.01d removed an attachment of type image/gif which had a name of image001.gif] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniData and Unicode
Note, I've researched it in the past but not actually done it, so I may get something wrong here. This I do know, however: Unicode is not the default for Unidata. Note that some of the default MultiValue system delimiters conflict with Unicode characters. In addition to turning this on and converting all your existing files, you have to change any program that hard codes the system delimiters with an EQU to use the @AM, @VM and such instead. You might get more mileage (with less risk) out of calling a Java program and having it do a Unicode conversion for you. You are effectively converting from whatever your code-page is on your system that you do input on, to Unicode. Unidata, like most MultiValue systems, takes input from whatever your input program is, in whatever code page it is running, and writes it as a byte-stream, without regard for encoding. A user who enters data from their Chinese browser using a non-Unicode code-page will write out characters that look like something completely different to a user who then views the same data from their western code-page browser, unless you make your apps smart enough to handle the different code-pages, or handle Unicode properly. Most MultiValue apps are a LOOONG way from supporting Unicode, even if you turn it on at the database. What I'm saying is, even if you turn Unicode on at the Unidata level, you may still not get the right data written to the file. Good luck! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Drew Henderson Sent: Thursday, April 03, 2008 9:11 AM To: u2-users@listserver.u2ug.org Subject: [U2] UniData and Unicode All, We're running Unidata version 7.1, and are trying to get a pc-based id card system (Idworks) to communicate via ODBC to our database; we are having limited success. The software vendor said they thought it was a Unicode compliance issue. I've found some marketing docs for U2 which indicates it is supported, but could find nothing in the Unidata docs which indicates if this compliance is the default, or if it is something to be enabled for either the database or the ODBC driver. Any provided information would be greatly appreciated. Drew msulogobw-smallDrew Henderson Director, Computer Center Operations 110 Ginger Hall Morehead State University 606/783-2445 [demime 1.01d removed an attachment of type image/gif which had a name of image001.gif] --- 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] UniData and Unicode
I could be all wet here, but it is my recollection that while Universe uses Unicode, Unidata uses UTF-8 for I18N. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniData and Unicode
I'm responding to the other responses, to some degree... Most MultiValue systems are data transparent; what goes in comes out. Except for the special characters in MV, which I believe are decimal 252 and up. However, in contradiction to an earlier response, these characters are not used in UTF-8. UTF-8 is a way of storing Unicode in which a character requires one or more bytes for storage. It is quite well designed. Control characters and ASCII are the same. Characters above hex 7F are NOT the same as is any codepage-based system. I believe that you can store UTF-8 in MV. You just have to decide that that is the coding scheme which your bytes represent, and be consistent about it. Our terminal emulator, AnzioWin can send its characters to the server as UTF-8, understand characters coming from the server as UTF-8, switch fonts automatically to find a font that contains each character, and print data as UTF-8 (again with auto-font usage). There can still be issues. Most notably, you can no longer assume that a byte in the database requires one cell to display or print. We'd be happy to work with anyone in this regard. Regards, Bob Rasmussen, President, Rasmussen Software, Inc. personal e-mail: [EMAIL PROTECTED] company e-mail: [EMAIL PROTECTED] voice: (US) 503-624-0360 (9:00-6:00 Pacific Time) fax: (US) 503-624-0760 web: http://www.anzio.com street address: Rasmussen Software, Inc. 10240 SW Nimbus, Suite L9 Portland, OR 97223 USA --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniData and Unicode
All, Thanks for the information you've provided. We've received some additional comments from the Id Works vendor. They have indicated that the earlier versions of their software only required ODBC compliance (with various conformance levels: core, extended grammar, etc.), but that the current versions require ODBC Unicode compliance. If it is not - by default - ODBC Unicode compliant, can it be configured to be so? Thanks, Drew --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniData and Unicode
What ODBC driver are you using? Is this Id Works using Unidata ODBC to retrieve data from Unidata? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Drew Henderson Sent: Thursday, April 03, 2008 3:28 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UniData and Unicode All, Thanks for the information you've provided. We've received some additional comments from the Id Works vendor. They have indicated that the earlier versions of their software only required ODBC compliance (with various conformance levels: core, extended grammar, etc.), but that the current versions require ODBC Unicode compliance. If it is not - by default - ODBC Unicode compliant, can it be configured to be so? Thanks, Drew --- 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] error question
Hey all, I am pretty sure this is a out of memory/stack space type error but I was hoping someone could tell me where I can find the fault types and if there is a way to use the address that the error returned to get where the code was when it blew up? below is the error Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program FREE.LOC at address 4c4 Thanks all dougc --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] problem with UniVerse SQL Users on windows
Hi Ray Mapping in UV.LOGINS does not help. UV_USERS has domain\user, and if you type WHO, you get DOMAIN\user, the difference being casing. There is no way to force the login to be in lower case and no way to change UV_USERS as I am not a valid SQL User. UniVerse has made NT AUTHORITY\System the default DBA, but as this has no password as an internal user, I cannot login as NT AUTHORITY\system to create a new SQL User. When you hit this type of issue, there appears to be no tools for an administrator to get in to resolve problems, it becomes a lockout situation. Regards David Jordan Managing Consultant --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] error question
In the UniVerse Administration guide (admin.pdf). Did you have a look or you can't find them? The documentation isn't the best!! These errors are best reported to IBM U2 Support. Especially, if you can reproduce the problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Chanco Sent: Friday, April 04, 2008 12:35 PM To: u2-users@listserver.u2ug.org Subject: [U2] error question Hey all, I am pretty sure this is a out of memory/stack space type error but I was hoping someone could tell me where I can find the fault types and if there is a way to use the address that the error returned to get where the code was when it blew up? below is the error Abnormal termination of UniVerse. Fault type is 11. Layer type is BASIC run machine. Fault occurred in BASIC program FREE.LOC at address 4c4 Thanks all dougc --- 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/
