Deploying an Enterprise Information System

Managing Your SAS/EIS Files

When you develop a SAS/EIS application, information about your application is stored and maintained for you in various files. These files are an essential component of your application. When you copy or move an application, you must also copy or move all files that are associated with the application. The following list briefly describes the files that SAS/EIS software maintains for you:

application databases

Each application database consists of an indexed SAS table of type SASAPPL and a catalog of the same name.

object group databases

Each object group database consists of an indexed SAS table of type SASOBJ.

attribute dictionaries

Each attribute dictionary consists of a SAS table.

columns databases

Each columns database consists of an indexed SAS table of type ASTCOL.

configuration catalogs

Each catalog consists of entries that contain information for one or more of the following:

client/server configurations
library configurations.

parameters catalogs

Each catalog consists of entries that contain information for one or more of the following:

user parameter information
file configurations.

repository managers

Each repository manager points to a physical path or folder. Only one repository manager can exist per path. Each repository manager contains the following SAS files:

assocmgr (Type=DATA)
cntainer (Type=DATA)
dictctrl (Type=DATA)
mrrgstry (Type=DATA)
rposctrl (Type=DATA)
verbmgr (Type=DATA).

repositories

Each repository points to a physical path or folder. Only one repository can exist per path. Each repository contains the following SAS files:

cntainer (Type=DATA)
column (Type=DATA)
dynattr (Type=DATA)
library (Type=DATA)
mdassoc (Type=DATA)
mrrgstry (Type=DATA)
slist (Type=CATALOG)
table (Type=DATA).

To facilitate moving non-repository SAS/EIS files to various host operating environments or to a different location on the same host, follow these guidelines:

Store all SAS/EIS files in a single library.
Copy or move the entire library to a new library or to a library that does not contain existing SAS/EIS files.
Do not copy or move individual SAS/EIS files to a library that contains existing SAS/EIS files, unless you use SAS/EIS software to perform the copy or move.
Do not delete SAS/EIS files unless you use SAS/EIS software to perform the deletions.

CAUTION:: Repository files must be moved using the SAS/EIS metabase facility or the REPOSMGR facility.
Using other methods to move the files will render the repositories unusable. Remember to make a backup copy of your files before you move them.

A Note on Repository Managers and Repositories

The SAS/EIS metabase facility stores registrations (for example, registered tables or MDDBs) in a repository. Repositories are managed by a repository manager. You can have one or more repository managers, each with one or more repositories defined.

Here are some important things to note when working with repositories:

You can copy repositories only through the SAS/EIS metabase facility or through the REPOSMGR facility. Do not use other utilities to copy repositories or repository managers because your files can become unusable.
To change to another repository manager or to create a new repository manager, enter the REPOSMGR command on any SAS command line. In the Repository Manager window, select Setup Repository Mgr. Specify the libref and path in the Repository Manager Setup window.
A repository manager or repository cannot span multiple directories. In other words, concatenated directories are not supported.
Be careful when you delete write-accessible repositories from a repository manager. If a repository is write accessible from many repository managers and you delete it from one of those repository managers, you will need to delete it from all repository managers. If you do not, then the repository will be corrupted when it is used by the other repository manager.

A Note on Configuration Files

Because configuration files contain host-specific path information, you might need to update this information after you copy or move files from one host to another or to a different location on the same host.

File configuration information is stored in the same location as the SAS/EIS parameter catalog. If you intend to reference a file configuration that has been copied, specify this location when you reference the catalog in the PARMS= option. See Using the EIS Command for details on specifying the PARMS= option.

A Note on Parameters Catalogs

If the copied SAS/EIS library contains a parameters catalog and you want to use this information in your SAS/EIS session, specify the parameters catalog with the PARMS= option when you invoke SAS/EIS software. If you do not want to use the parameter information from the copied SAS/EIS library, but you do intend to use the SAS/EIS files from the library, then include the necessary files in the appropriate search path. See Using the EIS Command for details on specifying the PARMS= options.

Copying SAS/EIS Files with PROC COPY

You can use PROC COPY to copy non-repository SAS/EIS files to another location on the same host.

CAUTION:: Repository files must be moved using the SAS/EIS metabase facility or the REPOSMGR facility.
Using other methods to move the files will render the repositories unusable. See A Note on Repository Managers and Repositories for additional information.

Here is an example:

libname source 'SAS-data-library';
libname target 'SAS-data-library';

proc copy in=source out=target;
run;

You can also use PROC COPY to move non-repository SAS/EIS files to another location that has a remote libref.

To copy SAS/EIS files from one host to another host, use PROC CPORT to create a transport file that you can then import to the second host with PROC CIMPORT. The following example code uses PROC CPORT to write a library that contains SAS/EIS files to a transport file:

libname source 'SAS-data-library';
filename tranfile 'transport-file-name'
                  <host-option-for-block-size>;

proc cport library=source file=tranfile;
run;

The following example code uses PROC CIMPORT to import a transport file that contains a library of SAS/EIS files:

libname target 'SAS-data-library';
filename tranfile 'transport-file-name'
                  <host-option-for-block-size>;

proc cimport library=target infile=tranfile;
run;

Note: If you are copying Version 6 files to a newer version of SAS/EIS, after running PROC COPY, you must assign the libref that you used in Version 6 to the new path. [cautionend]

Top of Page