Verifying ABAP SCS with enqueue replication

Edit online

When you complete the steps that are described in the previous sections, you must verify that your SAP central services installation runs without problems.

Starting and stopping the ASCS

Verify that you can start and stop the ASCS services manually:

Activate the VIPA under z/OS® UNIX System Services or the IP alias under Linux®. Under z/OS UNIX, use the moddvipa command as root user:
```
moddvipa -p tcpip -c 10.101.5.194 (if this is the IP address of ha1ascsv)
```
Manually start the ASCS00 instance as <sid>adm:
```
startsap r3 ASCS00 ha1ascsv
```

Verify that all processes are running correctly with sapcontrol:

sapcontrol -nr 00 -function GetProcessList

The output must show that all processes have a GREEN status as shown in this example output:


12.11.2013 07:50:22
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
msg_server, MessageServer, GREEN, Running, 2013 11 11 10:56:59, 20:53:23, 67175064
enserver, EnqueueServer, GREEN, Running, 2013 11 11 10:56:59, 20:53:23, 33620546

If you are not using EnqCF replication, manually start the enqueue replication server instance ERS10 as <sid>adm on a different LPAR after you activated the ERS VIPA there:
```
startsap r3 ERS10 ha1aersv
```
Verify that the replication process is running correctly with sapcontrol:
```
sapcontrol -nr 10 -function GetProcessList
```
The output must show that the process has a GREEN status as shown in this example output:
```
2.11.2013 07:55:02
GetProcessList
OK
name, description, dispstatus, textstatus, starttime, elapsedtime, pid
enrepserver, EnqueueReplicator, GREEN, Running, 2013 11 12 06:51:58, 1:03:04,
…
```

Verification of the replication mechanism

Start an SAP application server and use SAP transaction SM12 to generate test entries in the enqueue table to verify manually that the SAP system is running with replication enabled. See Preparing for the test for further information. It is only possible to generate entries and display them when the enqueue server of ASCS is running, and not when it is stopped.

To check whether replication is active (either via the replication server or by using EnqCF replication), use:
```
ensmon pf=<profile> -H <hostname>
```
For example, enter:
```
ensmon pf=/usr/sap/HA1/SYS/profile/HA1_ASCS00_ha1ascsv
```
From the main menu, select 1: Dummy request. The dummy request must run successfully.
Select 2: Get replication information. This returns:
```
Replication is enabled in server, repl. server is connected
Replication is active
```
and also displays statistics.
Note: The output shows repl. server is connected even when using EnqCF replication, where there is no separate replication server running.

To display the generated test entries, run:

enqt pf=/usr/sap/HA1/SYS/profile/HA1_ASCS00_ha1ascsv 20

Kill the enqueue server and message server manually.
Move the VIPA to the system where the replication server is started. Start the ASCS instance there. The replication server must stop itself after the enqueue table has been rebuilt.
Run again:
```
enqt pf=/usr/sap/HA1/SYS/profile/HA1_ASCS00_ha1ascsv 20 
```
If it displays the same output as before you killed the enqueue server, you have verified that replication works.