General File Maintenance

This document covers basic file maintenance that should addressed from within DAD and within the network as a whole.  As always, please use caution when deleting files. Verify that the file you wish to remove is not needed elsewhere.

Scan files:

After generating a log, many times personal will "scan" that log for errors. This generates a scan file. This file is found in the C:\DAD directory of the computer. They have extensions of *.SCN. These files should be cleaned of on a regular basis.

Ie: C:\dad\MONDAY.SCN

Playlists:

Playlist can build up over time. You should remove unused playlist from your system. Please use caution as you might be deleting a playlist that is being used. Always double check before deleting any files.

These can be removed in two ways.

1. You can delete these files from within DAD by going to the Main Playlist Modifier, selecting the desired playlist and hitting DELETE.

2. If you have several playlist you wish to delete at once. You can use navigate your way to \DAD\FILES\PLAYLIST directory and select all the desired files and deleting them. If you chose this method you should run the DCL RE-PLIST from the Library Command window to re-index the playlist database.

These files can be found on the server's drive: F:\dad\files\playlists

Imported Logs:

Imported Logs also can build up over time. You should remove unused imports from your system. Please use caution as you might be deleting an import that is being used. Always double check before deleting any files.

If you have several imported logs you wish to delete at once. You can use navigate your way to \DAD\IMPORT\ directory and select all the desired files and deleting them.

Other logs:

DAD can be configured to keep several other types of logs. These can be Record Logs, Branch Logs and GPI/GPO Logs. These files are found on the local drive under the directory \DAD\LOGS.

Record Logs are noted by the Rlyymmdd.log

Branch Logs are noted by the Blyymmdd.log

GPI/GPO Logs are noted by the Glyymmdd.log

(yymmdd = year, month, day)

These logs can removed if they are not needed.

Asplays:

Asplay logs can grow to unmanageable size if they are not purged from time to time. To clean these files out, go to asplay report window and select the desired log and hit PURGE.

If you have several files to remove, you can find these logs on the server drive F:\DAD\ASPLAY. If you are going to delete the logs from this directory, be sure to also delete the associated index file. 

Ie: ONAIR.MON and ONAIR.MOX or ONAIR02172004.DBF

Netware Purge:

Netware keeps track of all deleted files. After a period of time, Netware will use a fair amount of resources keeping track of all these files. The files can be useful if you need to recover a corrupted or deleted file, however your server can become full of these files if a purge is not done on a regular basis.

To do a PURGE, you should go to a DOS prompt and change to the network drives. (ie: F: or G). Then enter     Purge /all     This will permanently remove all deleted files from the Netware drives. 

You will probable see several screens worth of files scrolling by. You might also notice a bit of sluggishness while performing a purge.

NOTE: This is ONLY for users with a Novell NetWare server.

Various other files:

There are several other files that can be generated from within DAD. These are not normally saved unless the user chooses to do so.

If these files are saved, they can commonly be found on the local drive in the \DAD\FILES directory.

IN USE reports.

A user selecting a library cut and pressing IN USE creates these reports. These files will have the filename of the selected cut and an extension of .CHK. (ie: 00007.CHK)

LIBRARY reports.

A user creates these files when generating a report from the library. These could be for the entire library, selected cuts or expired cuts. These files are listed as LIB.REP.

PLAYLIST reports.

A user creates this file when generating a text file of a spefic playlist within the system. These files are listed as PLIST.REP.

GROUP reports.

A user creates this file when generating a Group listing from the library reports window. These files are listed as GROUP.REP.

EXCEPTION reports.

These files are created by a user when generating a list of all cuts that might either be in the library without an associated audio cut, improper drive location or an audio cut that exists in the \CUTS directory but does not exist in the library database. These files are listed as EXCEPT.REP.

DEBUG Files.

If you are running a debug file, you should copy the file to someplace else for safe keeping then delete the original file. This will keep the file down to a usable size. If left alone this file can become quite large.  This file is normally found in the C:\DAD directory. It’s name is dependent on the value you gave when setting the debug variable. This file will not be present unless it is specifically set.