CA Ramis database files RAMDB2NAMES and RAMSQLID

book

Article ID: 50352

calendar_today

Updated On:

Products

CA Ramis Reporter

Issue/Introduction

My CA Ramis database has system files named RAMDB2NAMES and RAMSQLID. What are they and are they needed?

Environment

Release:
Component: RAMIS

Resolution

CA Ramis system files RAMDB2NAMES and RAMSQLID have been obsolete since CA Ramis Version 7.2.
Both files were part of the DB2 interface prior to the RDBMS Interface provided with CA Ramis Version 7.2, 7.3 and 7.4. 

As part of the upgrade/migrate procedures, RAMDB2NAMES and RAMSQLID data were migrated to system file RAMSQLMASTER.
The migration process did not erase file RAMDB2NAMES and RAMSQLID and left it to the user to do so after their upgrade was completed.

Each file, if exists, can be deleted/erased using Ramis commands. 

Note that password "DB2" is needed to erase these files:

PASS DB2   
ERASE*   
FILE RAMDB2NAMES   
END
ERASE* 
FILE RAMSQLID
END 

It is best practice to follow up with reorganization of system files RAMASTER and STORE after deleting file descriptions and files, with reports before and after to see the state of both system files.

Use the following Ramis commands:

RAMBLOCKS   
STATUS RAMASTER   
STATUS STORE   
RAMREORG RAMASTER   
RAMREORG RAMCLEAN   
RAMBLOCKS   
STATUS RAMASTER   
STATUS STORE 

Additional Information

The Ramis commands can be issued in a batch or online Ramis session.

Refer to the RDBMS Interface publication via the CA Ramis Version 7.4 set of documentation at CA Ramis Bookshelves and PDFs