Home	RDP Sales	Contact Us	Training
RDP Support		Open a Web Support Ticket
RDPWin Knowledge Base	RDP-DOS Knowledge Base	IRM and IRM.Net Knowledge Base	Crystal Knowledge Base

System Utilities, Hardware, and Pervasive Database

See RDP Hardware Requirements

• Designed to correct and avoid availability problems such as double-bookings, overbooked group allocations or corrupt reservations.
• Should be run nightly.
• Reasons to run 995 during the day:  
  • Availability is incorrect on the yield management screen
  • "P"s are missing on the tape chart
  • You've added a new room or changed the room type of an existing room on the room master
  • Reservations appear to be missing.

• Mini 995
• Resets the availability for 1 particular room number.
• Reasons to run 209:  
  • "P"s are missing on the tape chart.
• Users do not have to exit from RDP

• Active vs Non Active History
• Should be run nightly. 
• Reasons to run 910:
  • Will shorten time it takes to run 995 
  • Makes searching for the guest  name "Smith" easier
  • Will speed up the sorting of various reports.
• Cancellation switches
• Default transfer days stored in C1 table, sub-record 910.  If you have owners or use travel agents do not set days to less than 45.
• F9 to view the 910 log

• Recent improvements to the log file make it easier to read.
• Utilities log a start and end time.
• Not all entries in log file are errors.
• Most errors do get recorded to the log file.
• Call support when you do get an error. 

• Lists the current users logged into RDP.
• Helpful when trying to run utilities that require all users exit out of RDP. 
• The * indicates the current user

• Allows you to reopen a statement after closing it.
• Will delete the B7D@ and B7D7 transaction codes (statement markers and voucher transactions).
• Does not undo the revenue that has already been processed.

• Rebuilds a data file based on the current records. 
• Reasons to run 994:
  • After a Pervasive upgrade
  • Data corruption
  • After running the 990 utility.
• If a record is corrupt, damaged or cannot be read, 994 deletes that record.
• It is impossible to identify the corrupt records - by definition they cannot be read.

• Option 1 - Delete invalid numbers & "Delete" in last name
  • Legacy software.  No longer in use.

• Option 2 - Guest History: Delete guests with no address info.
  • Removes all reservations, transactions, comments, notes and guest history.  
  • Will not delete guests with active reservations. 

• Option 3 - Guest History:  Delete guests with no active reservations.
  • Removes all reservations, transactions, comments, notes and guest history.

• Option 3a - Guest History:  Delete guests who have not stayed since a specified date.
  • Removes all reservations, transactions, comments, notes and guest history.

• Option 4 - NonActive History:  Delete reservations based on departure date.
  • Removes all reservations, transactions, comments, notes and guest history.

Run 994 on all critical files after running any of the above options.  This will decrease the file sizes.

None of the options above can be undone.  When the utilities are run the information is completely removed from  your RDP system.  The only way to retrieve the deleted information would be to restore from backup. 

If there are certain guest history records you want to keep, add the guest type called SAVE to the CA table and then change the guest type to SAVE on the individual guest history records you want to keep.

• Option 5 - Freeze Room Rates on All Reservations by Rate Plan

• Rebuilds the statistical totals files
• Reasons to run 902:  statistical totals are 0 but the statistical detail is present.  

• Rebuilds the totals files
• Reasons to run 998:  
  • Totals do not match the transactions, i.e. the 370 B1 does not match the 766
  • You've changed a GL account and want prior revenue to appear in the new account.  
• Caution:  do not run the 998 without first calling RDP Support for assistance.

• Worst case scenario during a hardware failure and/or data corruption WITH a tape backup:  
  • Load backup from the previous night and recreate the day's work.
    
• Worst case scenario during a hardware failure and/or data corruption WITHOUT a tape backup:  
  • START OVER
       

• Restore the backup to a RDP99 folder
• Do NOT test the backup by restoring over the RDP01 folder

• Perform a tape backup EVERY night
• Install the backup software on the fileserver
• The size of the backup media should be at least as large as the hard drive
• Periodically store the backups off-site
• Use a different tape nightly to prevent against overuse
• Tape backup software must be able to backup "open" files.
  • "Open" files are files that are in use.  
  • An example, would be the GM leaves his computer on overnight and is logged into RDP.  The RDP files are "open".