[U2] [UD] Weird Logging Issue

2006-10-10 Thread Kevin King
I am supporting a phantom program that uses PRINTs to output information to _PH_ for a log. When this log starts getting near 3MB, the phantom begins performing very strange. For example, sometimes a READ in the phantom will be successful, but the variable that was read is null (even though the

Re: [U2] [UD] Weird Logging Issue

2006-10-10 Thread karlp
I suspect you are right, but consider that you are writing to a sequential file when you use the PH file as a 'log' file. Handling that much data in an ongoing process will fill up the memory space assigned to the phantom process. At least that's my story... I would recommend actually opening up

RE: [U2] [UD] Weird Logging Issue

2006-10-10 Thread Kevin King
I would recommend actually opening up an item in a file, counting the number of lines in the file (with a routine to delete the top of the file as it grows beyond a useful size) and then doing: I'd love to implement more elegant logging, but as this is a vendor-written process, my options are

[U2] Bad DICTionary Attributes

2006-10-10 Thread Brutzman, Bill
I would like to see what is in field 8 for several data dictionaries. I need a command like... LIST DICT INVOICE WITH FIELD 8 LIKE M but I need help with syntax on the Field 8 part. Now that I am writing this e-Mail, I suppose that I could write a little UniBasic program. We have a bug here

RE: [U2] Bad DICTionary Attributes

2006-10-10 Thread Allen E. Elwood
Not sure if this would work in UV or not, but in mvBase you can stick the dict into the MD and use it for any file. See entry *A1 below: *A1 001 A 002 1 003 Attr. 1 004 005 006 007 008 009 L 010 15 If that doesn't work, you could try the not very well known 'USING DICT' phrase, like: LIST

RE: [U2] Bad DICTionary Attributes

2006-10-10 Thread rbl000
--- On Tue 10/10, Brutzman, Bill [EMAIL PROTECTED] wrote: I would like to see what is in field 8 for several data dictionaries.I need a command like... LIST DICT INVOICE WITH FIELD 8 LIKE Mbut I need help with syntax on the Field 8 part. How about: LIST DICT INVOICE WITH F8 LIKE M

[U2] PCL-XL

2006-10-10 Thread George Gallen
OK. has anyone here had the pleasure of coding in PCL-XL for report control? I'm looking for some examples of output, how it's formatted and such. I'm not talking about PCL5{x} or lower, this is for those host-based printers. Right now, sometimes the PCL5 works great, other times it gives me the

Re: [U2] Bad DICTionary Attributes

2006-10-10 Thread Jeff Schasny
LIST DICT XXX WITH F8 LIKE ...M... should work in Universe. Attribute 8 of the dictionary is used for the SQL data type Brutzman, Bill wrote: I would like to see what is in field 8 for several data dictionaries. I need a command like... LIST DICT INVOICE WITH FIELD 8 LIKE M but I need

RE: [U2] Bad DICTionary Attributes

2006-10-10 Thread Ray Wurlod
That message comes because there is a value of INTEGER or INT in field #8 (SQL data type) but a conversion of MDn - where n 0 - in field #3 (conversion). You can probably safely remove the contents of field #8. UPDATE DICT INVOICE SET F8 = '' WHERE F8 ''; However, if INVOICE is a UniVerse/SQL

Re: [U2] Bad DICTionary Attributes

2006-10-10 Thread Ray Wurlod
UniVerse itself does not use fields #9 through #16 in dictionaries. One (or more) of your applications is responsible for this. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/

RE: [U2] [UD] Weird Logging Issue

2006-10-10 Thread Baker Hughes
I've seen similar erratic behavior when a phantom process set locks for a possible update, but then didn't clear the lock when no update occurred. I'm suggesting you have a locking issue but the out of memory behavior is identical - it waits for available memory before it can perform the next

RE: [U2] Bad DICTionary Attributes

2006-10-10 Thread Brutzman, Bill
Victory... Thanks to Richard, Jeff, and Allen. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of rbl000 Sent: Tuesday, October 10, 2006 2:45 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Bad DICTionary Attributes --- On Tue 10/10, Brutzman,

RE: [U2] [UD] Weird Logging Issue

2006-10-10 Thread Baker Hughes
Corrected posting - sorry... I've seen similar erratic behavior when a phantom process set locks for a possible update, but then didn't clear the lock when no update occurred. I am NOT suggesting you have a locking issue but the out of memory behavior is identical - it waits for available

[U2] unsubscribe u2-users@listserver.u2ug.org

2006-10-10 Thread John Casserly
unsubscribe u2-users@listserver.u2ug.org John Casserly Senior Applications Systems Administrator Information Technology Bata Library Suite 101.10 Trent University Peterborough, Ontario Canada K9J 7B8 Phone: 705 748-1011 Ext. 7579 Fax: 705 748-1122 E-Mail: [EMAIL PROTECTED] ---

[U2] Creating XML from Universe and using multi values in InfoPath 2003

2006-10-10 Thread Boyd, Diane
Good Afternoon: I was wondering if anyone has had experience creating a Universe element 'centric' XML file and using that XML file in InfoPath ? If so where you able to properly display multi value fields in a table or master/detail control? I am using InfoPath 2003 with a drop

Re: [U2] [UD] Weird Logging Issue

2006-10-10 Thread Thomas Derwin
Hi Kevin, What O/S? _PH_ is a DIR-type file, so your issue could be O/S-related. Also, could you confirm that your VOC _PH_ is in fact a DIR-type? If a record reaches 3MB in a hashed file, every multivalued database I've worked with gets cranky. Hope this helps, Tom [EMAIL PROTECTED]

RE: [U2] Bad DICTionary Attributes

2006-10-10 Thread Brutzman, Bill
Ray: Thanks. This helps a lot. DICT Field 8 (F8) has a single A, S, M, or blank... in a lot of the D- and I-Desriptors here. We are not using SQL for anything at all. While a lot of problems with Ms were fixed by purging the Ms, perhaps the As and Ss should also be removed. It bothers me

RE: [U2] [UD] Weird Logging Issue

2006-10-10 Thread Womack, Adrian
Karl, Is that a UniData thing? Because with UniVerse exactly the reverse would be true - writing to a sequential file (via CRT statements to a COMO or with WRITESEQ to a record in a directory) would be much more efficient and use less memory than performing a WRITEV (which has to read the entire

[U2] Trigger behavior

2006-10-10 Thread Debster
Here is the scenario Remote non-pick box runs an ODBC process coming through Tuxedo Unidata 6.0/IAIX 5.x is running on the Pick box A file that contains a trigger is updated -- the trigger updates not only hashed files but also attempts to update a DIR type file. The DIR file cannot be