Configuring sapcpe (SAP Library - System Services (BC))

Configuring sapcpe

Generally, you do not need to customize or configure sapcpe. Should you need to change the way the program works, you can do so with command line options, or by creating or editing control files. If you have called up sapcpe from sapstart, you cannot change the transfer parameters to sapcpe. In this case you can only modify the files used by sapcpe. If you call up sapcpe directly, you can control the program by entering transfer parameters. Calling up sapcpe help gives you a list of the parameters that you can set.

You can define which files should be copied, or should have links, from the central directory to the local directory by calling up sapcpe directly and setting two control parameters.
The first parameter, all, has the highest priority and ensures that all files in the central directory are processed.
The second parameter is list:<filename>. If this parameter has been set, only all files from the list file <filename> will be processed.
If neither of these parameters has been set, the program searches for list files in the central directory.

Known list files:

instance.lst

List of database-independent executables. These executables are valid for all database systems with which the SAP System runs.

instancedb.lst

List of database-dependent executables. These executables are valid only with a particular database system.

tools.lst

all files that do not belong in either instancedb.lst or instance.lst.

inhouse.lst

all local files which should not be replaced by sapcpe during a copy run.

frontend.lst

If there is at least one list file in the central directory, then the files entered in this (these) list file(s) are created. If there is no list file in the central directory, then the files that are defined in the configuration file sapcpeft are created in the local directory.

Either a soft link or a copy may be created, or a simple check of the availability of the file may be carried out. This depends on:

the sapcpeft file, or

the file transferred with the ftable control parameter.

The ftable control parameter has the highest priority, and the availability of the sapcpeft file has the second-highest priority. Files of the ftable type (including the sapcpeft file) have the following structure:

Example

Program names | attributes

disp+work | local_copy

Possible attributes: local copy, softlink, check_exist