Ansicht
Dokumentation

RSLVCSTOP - liveCache: Stop liveCache in Background

Addresses (Business Address Services)   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Purpose

This program is used to stop a liveCache in an SCM system.

Integration

Prerequisites

• The integration data for the liveCache must be correctly stored (transaction DB59 or LC10 -> Integration). It must also be possible to run DBMServer commands for the liveCache using the DBMRFC connection.

• The executing user must have authorization to stop a liveCache. This is contained in roles SAP_BC_LVC_OPERATOR, SAP_BC_LVC_ADMINISTRATOR, and SAP_BC_LVC_SUPERUSER.

• The SAP user stored in the User Profile Container of the DBMServer must match the entry for the standard liveCache user in the integration data.

Features

Selection

PCONNAME:

Name of the database connection

Standard Variants

Output

Activities

Special Features:

• The individual actions of the program and its result are stored in a table as an extended log. You can display this in transaction LC10 under "Properties" and "Operating".

• The program initially attempts to set a lock (LC_ADMIN_<IV_CON_NAME>). If someone else already holds this lock, the program terminates with an error message. The lock is released again when the program ends (with or without an error).

Process Steps:

The program

• Executes any preprocessing reports stored in the integration data

• Stops the Database Analyzer, if it is activated for the liveCache

• Informs all work processes that they need to use the secondary connection to check the validity of the next SQL statement before running it..

• Stops the liveCache by executing the script lcinit or lcinit.bat (Microsoft Windows). This is called with the option "shutdown".

• Executes any postprocessing reports stored in the integration data.
  

Special Features of the Preprocessing and Postprocessing Reports

• Up to ten reports can be specified in the integration data as preprocessing or postprocessing reports for an action.

• The reports in a report chain of this type (such as preprocessing reports for stopping) must all be different. Different chains (such as preprocessing reports and postprocessing reports for stopping) can, however, contain the same reports.

• The program proccesses the reports synchronously in another task.

• If you want asynchronous processing, the reports can execute the actions asynchronously or schedule them as a background job.

• If an error occurs or a termination of the program is desired, the reports can signal this by exporting a text to the main memory:
  

EXPORT report_return_text = <TEXT>
TO MEMORY ID 'LC_REPORT_RETURN_TEXT'

• <TEXT>: up to 255 characters in length

• <TEXT> that starts with "STOP ": Preprocessing report or postprocessing report is signalling that further processing of the start, stop, or initialization process by the program should be terminated - for example, because the report is starting the liveCache itself. The program ends itself (without an error message).

• <TEXT> that does not start with "STOP ": Preprocessing or postprocessing report is returning an error. For a more detailed error message, see the <TEXT>. The program terminates with an error message.

• <TEXT>: You can view this in the detailed log in transaction LC10 (under "Properties# and "Operating#)

Example

PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 4446 Date: 20240520 Time: 110246     sap01-206 ( 54 ms )