RE: [U2] [UD] Cleaning out _PH_
On windows I would use scripting and wmi to 'select' files created before a certain date - google on winmgmts, cimv2 and CIM_DataFile - on *nux it is much easier using the find command. Symeon. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Wolverton Sent: 09 January 2008 04:29 To: u2-users@listserver.u2ug.org Subject: [U2] [UD] Cleaning out _PH_ Have a _PH_ that is just full of crud and I cannot think of a convenient way to automate the 'cleanup' from within UniData since there is nothing the key to the _PH_ record that shows a 'date' -- the design cleverly stores the User ID and ProcessID - both terribly non-useful for cleanup logic!! How do others deal with this maintenance short of telling users to 'periodically zap the records' -- I could clear data over 120 days old and never lose a moment of sleep, but can't find a way to do this without resulting to 'directory dump parsing', which just seems wrong. This is a 'Windows' box, and it appears to have _PH_ entries back to 2006! Yikes! Thanks for thoughts on this maintenance task... David W --- 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] Last chance to nominate
Calling all U2UG members on thist list - This is a final reminder that nominations for the U2UG board close on 10th February. To ensure your nomination gets processed in time, please email me directly on [EMAIL PROTECTED] We are looking for committed and enthusiastic candidates who want to move on the work of the U2UG on behalf of this community. Nominations can be for any U2UG member, and self-nominations are welcomed. Thank you Brian --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Cleaning out _PH_
David: Try CLEAR.ACCOUNT. This should clear both _PH_ and _HOLD_ entries. I run this every day. Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Wolverton Sent: Tuesday, January 08, 2008 8:29 PM To: u2-users@listserver.u2ug.org Subject: [U2] [UD] Cleaning out _PH_ Have a _PH_ that is just full of crud and I cannot think of a convenient way to automate the 'cleanup' from within UniData since there is nothing the key to the _PH_ record that shows a 'date' -- the design cleverly stores the User ID and ProcessID - both terribly non-useful for cleanup logic!! How do others deal with this maintenance short of telling users to 'periodically zap the records' -- I could clear data over 120 days old and never lose a moment of sleep, but can't find a way to do this without resulting to 'directory dump parsing', which just seems wrong. This is a 'Windows' box, and it appears to have _PH_ entries back to 2006! Yikes! Thanks for thoughts on this maintenance task... David W --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Universe 10.1 Itype possible parsing problem
This interesting feature is reproduced also at release 9.5.1 of UniVerse (and likely from the beginning), but this one was not yet referenced at IBM nor its predecessors. Note that compiling the DICTionary displays something abnormal that could alert on the problem : CD VOCLIB Compiling CRAMMED. IF @RECORD 3 = @RECORD 6 THEN 3 = @RECORD 6 THEN 1 ELSE -1 Compiling NICELY.SPACED. IF @RECORD 3 = @RECORD 6 THEN 1 ELSE -1 If you have a Maintenance Contract available, do not hesitate to raise a Technical Support call for an official request for a fix (But, however, I'm afraid it will be treated with a low priority). Hervi BALESTRIERI --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Universe 10.1 Itype possible parsing problem
I appreciate the feedback. Thanks all. john On 1/9/08, Herve Balestrieri [EMAIL PROTECTED] wrote: This interesting feature is reproduced also at release 9.5.1 of UniVerse (and likely from the beginning), but this one was not yet referenced at IBM nor its predecessors. Note that compiling the DICTionary displays something abnormal that could alert on the problem : CD VOCLIB Compiling CRAMMED. IF @RECORD 3 = @RECORD 6 THEN 3 = @RECORD 6 THEN 1 ELSE -1 Compiling NICELY.SPACED. IF @RECORD 3 = @RECORD 6 THEN 1 ELSE -1 If you have a Maintenance Contract available, do not hesitate to raise a Technical Support call for an official request for a fix (But, however, I'm afraid it will be treated with a low priority). Hervi BALESTRIERI --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- john --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UniSQL - virtual fields problem
We have tried from the sql , and the ODBC. They all failed. No problems with joins using ODBC. By that I mean, we can perform joins without any problems. However, we still are not getting any results from the the virtual fields taht participating in the joins. Dave Davis [EMAIL PROTECTED] wrote: Are you using sql just from the sql prompt, or from ODBC? Any problems with joins using ODBC? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Chiang Sent: Tuesday, January 08, 2008 1:55 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UniSQL - virtual fields problem Yes. We started out by selecting a mixed of data and virtual fields. Once it became apparent that no values returned from any of the virtual fileds, we tried by selecting either just multiple or single virtual fields to no avail. I'm not familiar with @SELECT dictionary item, but, they are definitely are in the LISTDICT. Dave Davis wrote: Are you explicitly including the virtual fields in your select statement? Are they in the @SELECT dictionary item? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Chiang Sent: Tuesday, January 08, 2008 10:59 AM To: u2-users@listserver.u2ug.org Subject: [U2] UniSQL - virtual fields problem Running UniData 7.1 and having difficulties of accessing virtual fields within UniSQL. We SQLized the UniData files using VSG. We then SELECT the table within UniSQL. There are good results returned from all the data fields, but, nothing returned from any of the virtual fields. Are there known issues with virtual fields within UniData 7.1? Thanks for your help. Larry - Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. --- 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/ - Never miss a thing. Make Yahoo your homepage. --- 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/ - Never miss a thing. Make Yahoo your homepage. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Cleaning out _PH_
Thanks for the responses -- but the _PH_ file may contain diagnostic info we'd want - so we want it around at least 30 days -- but all the responses yield the same answer -- there is no way to know the date of the item from within UniData -- Incredible! A log file that does not have a date associated with it (except at the OS level, anyway!) -- I wonder why they didn't include [EMAIL PROTECTED]@TIME in the key? Falls into the 'wow, I can't believe that one' category! Again, Thanks for the replies! DW --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] Cleaning out _PH_
Have a _PH_ that is just full of crud and I cannot think of a convenient way to automate the 'cleanup' from within UniData I usually do this with scripting at the O/S level, but you could do it with UniBasic. It would go something like this: 1) Open _PH_ with a normal OPEN statement 2) Use FILEINFO(filename, 2) to determine the path to _PH_ 3) Loop through with READNEXT 4) Construct the full path using the path to _PH_ and the ID returned by READNEXT 5) Use the DIR function to determine the date (and optionally, time) the file was updated 6) Delete, archive or whatever, based on the date Tim Snyder Consulting I/T Specialist U2 Lab Services Information Management, IBM Software Group [EMAIL PROTECTED] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Cleaning out _PH_
David Since you're on Windows you can run a simple VBScript to check the dates on the entries. If you haven't used VBScript on Windows, just create the script in notepad with a vbs extension and run from a command shell using CSCRIPT scriptname.vbs or WSCRIPT scriptname.vbs - they are the same, just WSCRIPT pops up message boxes. Here is an example - this is pretty much off the top of my head so you may need to fiddle around with it i.e. it's not warranted in any way and the actual deletion line is commented out! Should be run from the account directory. ' script to clear down old entries from a directory Const DIRNAME = PH ' change to _PH_ on UniData Const INTERVAL = 30' days Dim fso Main Sub Main If CreateFSO = False Then Exit Sub If CheckDirectory = False Then Exit Sub CheckFiles End Sub Function CheckDirectory If fso.FolderExists(DIRNAME) = False Then WScript.Echo Missing Directory DirName CheckDirectory = False Else CheckDirectory = True End if End Function Sub CheckFiles Dim Folder Dim Files Dim File Set Folder = fso.GetFolder(DIRNAME) Set Files = Folder.Files If Files.Count 0 Then For Each File In Files CheckFile(File) Next End If End Sub Sub CheckFile(File) If Left(File.Name,1) = . Then Exit Sub End If Today = Date If DateDiff(d, File.DateCreated, Today) = INTERVAL Then WScript.Echo Delete File.Name File.DateCreated ' UNCOMMENT THIS LINE TO DO THE DELETION File.Delete End If End Sub Function CreateFSO Set fso = CreateObject(Scripting.FileSystemObject) If (fso Is Nothing) Or (Err False) Then WScript.Echo Cannot initialize file system object CreateFSO = False Else CreateFSO = True End If End Function Regards Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Wolverton Sent: 09 January 2008 04:29 To: u2-users@listserver.u2ug.org Subject: [U2] [UD] Cleaning out _PH_ Have a _PH_ that is just full of crud and I cannot think of a convenient way to automate the 'cleanup' from within UniData since there is nothing the key to the _PH_ record that shows a 'date' -- the design cleverly stores the User ID and ProcessID - both terribly non-useful for cleanup logic!! How do others deal with this maintenance short of telling users to 'periodically zap the records' -- I could clear data over 120 days old and never lose a moment of sleep, but can't find a way to do this without resulting to 'directory dump parsing', which just seems wrong. This is a 'Windows' box, and it appears to have _PH_ entries back to 2006! Yikes! Thanks for thoughts on this maintenance task... David W --- 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] [UD] Cleaning out _PH_
David; I posted a program to pickwiki that helps do this. You can setup dict items in your VOC so you can list/select in UD based on the OS size, date, etc. It should work on any DIR type file. http://www.pickwiki.com/cgi-bin/wiki.pl?GetOsInfo Colin Alfke Calgary, Canada -Original Message- From: David Wolverton Have a _PH_ that is just full of crud and I cannot think of a convenient way to automate the 'cleanup' from within UniData since there is nothing the key to the _PH_ record that shows a 'date' -- the design cleverly stores the User ID and ProcessID - both terribly non-useful for cleanup logic!! How do others deal with this maintenance short of telling users to 'periodically zap the records' -- I could clear data over 120 days old and never lose a moment of sleep, but can't find a way to do this without resulting to 'directory dump parsing', which just seems wrong. This is a 'Windows' box, and it appears to have _PH_ entries back to 2006! Yikes! Thanks for thoughts on this maintenance task... David W --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Cleaning out _PH_
Very cool - Thanks Colin -- I don't go review the source code on the Wiki like I probably should! This problem has already been solved - and your code does it quite nicely -- I have never used the DIR function -- hadn't even thought of it -- and that's why I was dreading the exercise since I would have to write it 'platform independent' and was cursing the UniData gods for having condemned me to that fate of having to parse DIR or ls - but the DIR function solves that issue!! I wonder why I've never had cause to need it before?? But I've already got some ideas on other things I can start cleaning up, like log files in the /UniData directories at the bin level! Thanks again -- a perfect solution that seems it should be a weekly phantom at our sites... (Although the UniData documentation on DIR is incorrect at level 7.1 - shows Time and Date are BOTH in Attb 2 of the returned data.) David W. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 09, 2008 8:17 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] Cleaning out _PH_ David; I posted a program to pickwiki that helps do this. You can setup dict items in your VOC so you can list/select in UD based on the OS size, date, etc. It should work on any DIR type file. http://www.pickwiki.com/cgi-bin/wiki.pl?GetOsInfo Colin Alfke Calgary, Canada --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Universe 10.1 Itype possible parsing problem
Chuck, Thanks for verifying it. Also thanks for letting me know about the DLIST command I was wondering if there was a way to look at an I-descriptor. Jerry Banker Sr Programmer Analyst IBM Certified Solutions Expert Affiliated Acceptance Corp Sunrise Beach, MO 1-800-233-8483 www.affiliated.org -Original Message- From: Geoffrey Mitchell [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 6:14 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Universe 10.1 Itype possible parsing problem I would think that honoring a reasonable order of operations when parsing would resolve this. The extraction operator should certainly be higher priority than comparison. In fact, it works correctly in a BASIC program (UV 10.1.8). I compiled and ran the following: 0001: XX= 0002: XX1=5 0003: XX2=X 0004: IF XX1=5 THEN CRT YES ELSE CRT NO It returned YES as expected. If it suffered from the same affliction, it should have returned NO as (XX1) is not = 5. Therefore, it would seem that the parser for the I-Types is, as originally suggested, broken, or, more specifically, is not consistent with the BASIC compiler. I confess, however, that I have not verified the alleged I-type behavior on my system. Jerry Banker wrote: I have to add that this is just the reason why I stress using spaces between signs, variables, Boolean operators, and a liberal use of parentheses. -Original Message- From: Jerry Banker [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 4:46 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Universe 10.1 Itype possible parsing problem What it is doing is evaluating as: If @record is less than 3 is greater-than or equal to @record6 then 1 else -1 Or In other words: If 0 is greater-than or equal to 20071217:224240 then 1 else -1 -Original Message- From: john reid [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 3:57 PM To: list Subject: [U2] Universe 10.1 Itype possible parsing problem In the following query, a file is listed with two identical itypes, save for field 2 spacing, as shown below. Fields 3 and 6 are all equal in the query shown. The difference is that there is no space between the and = . This appears to yield wrong results, the bad one being shown as field 2 (all minus ones) in the query. Anyone seen this? john field 3 field 6 1-1 20071217:224240 20071217:224240 1-1 20071218:165115 20071218:165115 1-1 20071217:211056 20071217:211056 1-1 20071218:105346 20071218:105346 -- IF @RECORD3 = @RECORD6 THEN 1 ELSE -1 IF @RECORD3= @RECORD6 THEN 1 ELSE -1 john --- 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/ -- Geoffrey Mitchell Programmer/Analyst Home Decorator's Collection 314-684-1062 --- 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] [UD] Cleaning out _PH_
Actually - I saw two. Both mine and Tim's used the DIR() function to grab the date from the OS item. Tim had it in a program and I had it buried in a program called from a dictionary. Perhaps neither of these made it to you??? Colin Alfke Calgary, Canada -Original Message- From: David Wolverton Thanks for the responses -- but the _PH_ file may contain diagnostic info we'd want - so we want it around at least 30 days -- but all the responses yield the same answer -- there is no way to know the date of the item from within UniData -- Incredible! A log file that does not have a date associated with it (except at the OS level, anyway!) -- I wonder why they didn't include [EMAIL PROTECTED]@TIME in the key? Falls into the 'wow, I can't believe that one' category! Again, Thanks for the replies! DW --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Cleaning out _PH_
The wonderful speed of the internet! I sent that response BEFORE you two sent yours! Overnight, when people suggested external scripts to use - Not that there's anything wrong with that... But I prefer something that is all trackable within PRC and with UniData control... Thanks -- the DIR() idea is a GREAT fix... And I didn't even know of DIR's functionality... Thanks again! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 09, 2008 9:58 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] Cleaning out _PH_ Actually - I saw two. Both mine and Tim's used the DIR() function to grab the date from the OS item. Tim had it in a program and I had it buried in a program called from a dictionary. Perhaps neither of these made it to you??? Colin Alfke Calgary, Canada --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UD] Cleaning out _PH_
David, Windows command for finding and deleting files created 120 days ago: cd _PH_ forfiles /d -120 /c cmd /c del @file 21 NUL rex --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] [Ad] XLr8 Editor and Web Developer Updates
U2logic announces that our Free eclipse based plugin for Universe and Unidata has been updated. Instructions for downloading this tool is available at www.u2logic.com. Cumulative release notes: 1.3.5 - U2Plugin - The editor manages connections above the high water mark significantly better now. - U2Plugin - Fixed a problem with the Open Declaration feature when it was used on a file that was opened for the first time. - Installer - Close connections above the high water mark. - Form Developer - Add Id Field to ReadField validation dialog. - Form Developer - Change D01 category name and 4 property names. 1.3.4 - U2Plugin - Add the ability to open a INCLUDE file using the Open Declaration menu option. 1.3.3 - U2Plugin - Improved session handling when sessions are unavailable. - Installer - Improved the installer to handle session availability better. - Installer - Add a preferences page for the installer. 1.3.2 - U2Plugin - Fixed a problem when closing the editor and the file list was still loading. - U2Plugin - Fixed a problem when re-opening the editor after leaving a js file open when it was closed. 1.3.1 - U2Plugin - When indexing the connections the account path is always used if present. This reduces the number of connection when opening a form in the developer. Regards, U2logic Team --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Cleaning out _PH_
David, This will take time to settle to a time where it will function correctly. But here is my suggestion - Day 1 - save a SELECT list of _PH_ using the date of day 1 as part of the key. Day 2-30 - do the same, but remove from list the contents of the previous day's list Day 31 - delete everything in Day 1 saved list, make a new list as per Day 2. Day 32 onwards - delete what is in the list for 30 days ago. Make a new list as per Day 2. I haven't actually tried it but it seems logical. Jeffrey Lee Senior Analyst/Programmer IT Vision Australia Pty Ltd (ABN: 34 309 336 904) PO Box 881, Canning Bridge WA 6153 Level 3, Kirin Centre, 15 Ogilvie Road, Applecross, WA, 6153 P: (08) 9315 7000F: (08) 9315 7088 W: http://www.itvision.com.au ___ NOTICE : This e-mail and any attachments are intended for the addressee(s) only and may contain confidential or privileged material. Any unauthorised review, use, alteration, disclosure or distribution of this e-mail (including any attachments) by an unintended recipient is prohibited. If you are not the intended recipient please contact the sender as soon as possible by return e-mail and then delete both messages. ___ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UD] Cleaning out _PH_
Colin: This is pretty cool. Thanks. :-) Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, January 09, 2008 6:17 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UD] Cleaning out _PH_ David; I posted a program to pickwiki that helps do this. You can setup dict items in your VOC so you can list/select in UD based on the OS size, date, etc. It should work on any DIR type file. http://www.pickwiki.com/cgi-bin/wiki.pl?GetOsInfo Colin Alfke Calgary, Canada -Original Message- From: David Wolverton Have a _PH_ that is just full of crud and I cannot think of a convenient way to automate the 'cleanup' from within UniData since there is nothing the key to the _PH_ record that shows a 'date' -- the design cleverly stores the User ID and ProcessID - both terribly non-useful for cleanup logic!! How do others deal with this maintenance short of telling users to 'periodically zap the records' -- I could clear data over 120 days old and never lose a moment of sleep, but can't find a way to do this without resulting to 'directory dump parsing', which just seems wrong. This is a 'Windows' box, and it appears to have _PH_ entries back to 2006! Yikes! Thanks for thoughts on this maintenance task... David W --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
