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, unless you use the profile to change the parameters. 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

·        dbclient.lst

·        igsexe.lst

By default sapcpe does the copying. The linking (UNIX only) of executables is controlled by a parameter in file sapcpeft.


Program names  |  attributes

program name | softlink
program name | CP_LOC_IF_EXIST

Possible attributes: local_copy (default), softlink (nur UNIX), check_exist, CP_LOC_IF_EXIST