What is the large(96 meg) file in the AREV directory.

It has a date and timestamp that seems to stay current with

the system date and time. Is it something that can be purged?

Thanks for any help.(REV75145.)

Frank Smith

Frank,

Do the following from TCL:

LISTMEDIA REVBOOT

and see what information it displays about rev75145.

It sounds like a file that is being written to by the system daily so I would have to say you should not delete it.

John Revelation

TURNED OUT TO BE THE LISTS FILE. THERE ARE LISTS FROM AS FAR BACK AS

1994. SINCE THE SYSTEM SEEMS TO USE THIS FILE TO STORE DATA(COMMAND.STACK FOR USERS AND I DON'T KNOW WHAT ELSE) IT WOULD

NOT SEEM A GOOD IDEA TO JUST CLEAR FTHE FILE. IS THERE ANY

SET OF RULES I COULD USE TO DELETE FROM THIS FILE? NOTICE THAT MANY

OF THE RECORDS START WITH AN "I" OR A "T" ALSO WITH TIME AND DATES.

THANKS

FRANK SMITH

Frank,

There is no feature in Arev (that i am aware of) that would allow you to do this. If you store the date you could select the file by date and delete all the records that are older than a certain date.

If all else fails you can clear the file (back it up first) and you shouldn't have any problems

John Revelation

Those records that start with an I* or a T* are temporary records used in selects. (Starting with version 3, I think, these items are stored in the SYSTEMP file instead) What you should do in a purge process is to wait until no user is logged on (if you don't, and they are doing a select, you will screw up their select process). At that point there should be NONE of these records, so you can delete them all. Be aware, though, that if you use a select statement in your process to delete them, you could be creating a new set of these records. You may also see many records of the form QUERY.TABLE*network_card_id or timestamp.network_card_id*seq_no

where timestamp is a time stamp created by Arev

network_card_id is the network card address (see WHO screen)

seq_no is a sequential number

These items maintain the stack of queries accessible by pressing CTRL-F10. Most users I've encountered are unaware of this feature, so having it there just clutters things up and increases network traffic. If you don't need this feature, you can disable it in your environment settings by changing the number of saved queries to 0.

The COMMAND.STACK items just maintain a list of commands that user entered prior to logging off. It allows them to press F2 to view a list of previous commands. If you delete these items, this list of commands will be cleared, but the user will be otherwise unaffected.

All remaining items are likely saved lists. If your users don't need saved lists, you can delete these items, too.

In short, the system does not by itself need anything in the LISTS file, but there is information there that your users may need.

Some time ago I wrote an MFS that, if placed on the LISTS file, kept track of the lists, allowing you to selectively delete items by selecting them from a popup. Please lights@onr.com if you'd like a copy of it. It most likely will require some modification to fit your particular situation.

Victor

If you would like I can send you a program that I wrote a couple years ago for our AREV 3.12 application that purges the LISTS table. It looks at the systems date/time stamp for the row and deletes any row that has yesterdays date or older. This leaves any currently active lists alone plus it doesn't touch any lists that have been saved by the SAVELISTcommand.

As mentioned by one of the other persons responding to you message, we have set our enviormental settings to 0 saved lists. For the most part the above program I mentioned isn't used any more.

The cleanup of the LISTS table is still needed from time to time. When I've done it, I've put out a message to the users telling them what I'm goin to do and when and for them to tell me which of the SAVELIST lists I'm not to delete. Then I create two temporary tables. One is a full copy of the LISTS table right before I clear it and the other is a copy of the particular rows that people have said that they still need. Once I clear the table (when no one is on the system), I put the selected rows back and delete that temporary table. Then if after a week or so on one comes back and says that they need a list that has been deleted, I delete the second temporary table that was holding a full copy of the original LISTS table.

If you would like a copy of the program I talked about, please write me.

Michael Slack

E-mail: slackmi.asa@asa.org

View this thread on the forum...