Business Continuity for SAP on IBM Z

https://www.ibm.com/docs/en/bcfsoz
Admin
This documentation provides information and guidance on ensuring high availability and automation...
Tokens:153,693
Snippets:997
Trust Score:10
Update:10 months ago
Show doc for...
Tokens:
Raw
### Example `start_sapsrv` Script Invocation

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=scripts-start-sapsrv

An example demonstrating the correct syntax for invoking the `start_sapsrv` script. This example shows how to provide the SAP system ID, instance name, hostname, job name, and maximum retries to start the service.

```shell
./start_sapsrv HA2 ASCS20 ha2ascsv SHA2ASR 9
```

--------------------------------

### Start SAP Instance Script Syntax and Example (Shell)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=scripts-start-cs

This snippet shows the command-line syntax for invoking the `start_cs` script, which starts SAP instances on z/OS. It also includes a practical example demonstrating how to use the script with specific parameters. The script requires several arguments: SAP system identifier, instance name, virtual hostname, job name, and maximum retries for starting the instance.

```shell
Usage:
./start_cs <sid> <SCS/ERS/WD/SMDA_instance> <hostname> <jobname> <maxretries>

Example:
start_cs HA2 ASCS20 ha2ascsv SHA2AST 9
```

--------------------------------

### SAP Web Dispatcher ZSCSinst Parameter File Example

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=dispatcher-installing-sap-web

This is an example parameter file used with the ZSCSinst tool for installing the SAP Web Dispatcher on z/OS. It includes essential parameters such as system type, virtual host name, SAP system ID, mount directory, kernel path, instance number, and ports. Ensure the HOSTNAME parameter is set to your virtual host name for high availability.

```shell
SYSTYPE=WD
HOSTNAME=sapwd1wdv
SAPSID=WD1
MOUNTDIR=/sapmnt
KERNELCD=/common/sapdvds/SAP_NW740/51046681_2/SAP_Kernel_7.40_z_OS_64bit_j
         /DATA_UNITS/K_740_U_OS390_64
INSTANCENUMBER=77
WMSHOST=ha3scsv
WMSPORT=8130
WDHTTP=8177

```

--------------------------------

### SAP Web Dispatcher ZSCSinst Tool Invocation Example

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=dispatcher-installing-sap-web

This code snippet shows how to invoke the ZSCSinst tool for installing an SAP 740 SR2 Web Dispatcher on z/OS. It specifies the SAP version, the z/OS instance name, and the path to the ZSCSinst configuration file. This command is used to initiate the installation process based on the provided parameters.

```shell
./zscsinst 740SR2 WD /u/wd1adm/SWPM/WD.WD1

```

--------------------------------

### Start autofs Service Manually (Linux)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=samples-linux-sample-nfsv3-mounts

Demonstrates how to manually start the autofs service on Linux using the `service` command. This service is crucial for managing NFS automounts.

```bash
service autofs start
```

--------------------------------

### Start Db2 Group Member with Light Mode (START DB2 Command)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=recovery-data-sharing-considerations-disaster

This command starts a Db2 group member. The 'LIGHT' parameter can be used to initiate the member in a light mode, which affects the startup process. Members in LIGHT(NO) mode should be started before those in LIGHT(YES) mode to ensure proper initialization order within the data sharing group.

```Db2 Console
START DB2 LIGHT(YES)
```

```Db2 Console
START DB2 LIGHT(NO)
```

--------------------------------

### Configure autofs Service to Start at Boot (Linux)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=samples-linux-sample-nfsv3-mounts

This snippet shows how to configure the autofs service on Linux to start automatically at boot time. It utilizes the `chkconfig` command. The autofs service manages NFS mounts.

```bash
chkconfig -a autofs
```

--------------------------------

### SMDA Instance Installation Parameters for z/OS

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=installation-smda-zos-setup

This is a sample input parameter file for the ZSCSinst tool used in SMDA installation on z/OS. It defines various settings like system type, hostname, SID, kernel location, instance number, and connection details for Solution Manager.

```shell
SYSTYPE=SMDA
HOSTNAME=coh2vipa
SAPSID=DA2
KERNELCD=/common/pewa/SMDA/Kernel_742_OS390
INSTANCENUMBER=92
SLDYESNO=NO
SLDHTTPHOST=
SLDHTTPPORT=
SMDSLCONYESNO=YES
SMDP4TYPE=1
SMDP4HOST=solman.boeblingen.de.ibm.com
SMDP4PORT=8101
JAVADIR=/usr/lpp/java/J7.0_64
```

--------------------------------

### Update SAP Central Services Instance Start Mechanisms

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=instances-installing-central-services-activate-coupling-facility-replication

This section demonstrates how to modify the SAP profile entries to change the start mechanism for the enqueue server, message server, and gateway server (for Java SCS) from 'Start_Program' to 'Restart_Program'. This ensures that these services are configured to restart automatically.

```INI
Start_Program_01 = local $(_EN) pf=$(_PF)
-->
Restart_Program_01 = local $(_EN) pf=$(_PF)
```

```INI
Start_Program_00 = local $(_MS) pf=$(_PF)
-->
Restart_Program_00 = local $(_MS) pf=$(_PF)
```

```INI
Start_Program_02 = local $(_GW) -a pf=$(_PF)
-->
Restart_Program_02 = local $(_GW) -a pf=$(_PF)
```

--------------------------------

### SAPMVCF Utility Execution Example

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=problems-sapmvcf-utility

Demonstrates how to call the SAPMVCF utility with SAP System ID (SAPSID) and instance number. It outlines the construction of the replication data note pad name and the configuration file path based on the provided parameters. The move flag parameter controls automatic co-location handling.

```shell
# Example call with SAP System ID 'HA1' and instance number '10'
# sapmvcfs <SAPSID> <InstanceNumber> [MoveFlag]
sapmvcfs HA1 10
```

--------------------------------

### Check Enqueue Replication Server Status with ensmon (SAP Utility)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=scenarios-unplanned-outage-test

The 'ensmon' utility is used to check the status of the enqueue replication server. This example calls 'ensmon' with a specific profile path and option 2 to get replication information, demonstrating connectivity and replication status.

```shell
ha2adm> ensmon pf=/usr/sap/HA2/SYS/profile/HA2_ASCS20_ha2ascsv 2
```

--------------------------------

### Example OSA Interface Configuration with setvipa for SUSE

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=setup-static-vipa-definitions-suse

An example `ifcfg` file for an OSA interface (`eth1`) on SLES 12, demonstrating the inclusion of `POST_UP_SCRIPT="compat:suse:setvipa"` to manage VIPA configurations.

```shell
BOOTPROTO="static"
UNIQUE=""
STARTMODE="onboot"
MTU="8992"
IPADDR="10.101.4.137"
NETMASK="255.255.255.192"
NETWORK="10.101.4.128"
BROADCAST="10.101.4.191"
_nm_name='eth1'
POST_UP_SCRIPT="compat:suse:setvipa"
```

--------------------------------

### Create RPCBIND PROCLIB Member (JCL)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=migrations-from-portmap-rpcbind

This JCL defines the RPCBIND server as a started task. It specifies the program to execute (RPCBIND) and allocates necessary output streams. This is a fundamental step for running RPCBIND on z/OS.

```JCL
//**************************************************************
//RPCBIND  PROC
//*
//*   TCP/IP FOR MVS
//*   SMP/E DISTRIBUTION NAME: EZARBBND
//*   FUNCTION: UNIX SYSTEM SERVICES RPCBIND SERVER MAIN PROCESS
//*
//RPCBIND  EXEC PGM=RPCBIND,REGION=4096K,TIME=1440
//*
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//         PEND                                                 

```

--------------------------------

### Stop and Disable iptables Service

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=lht-ospf-routing-in-red-hat-enterprise-linux-power-systems

These commands are used to stop the running iptables service and prevent it from starting on boot. This is often necessary during network testing if iptables interferes with connectivity, especially on internal networks. It requires systemd or a similar init system to be present.

```bash
systemctl stop iptables.service
systemctl disable iptables.service

```

--------------------------------

### Configure Zebra Daemon (zebra.conf)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=lht-ospf-routing-in-red-hat-enterprise-linux-power-systems

This snippet details the configuration for the Zebra daemon in Quagga, which handles routing table management. It includes hostname, password, log file settings, and interface configurations with IP addresses. It requires Quagga to be installed and Zebra enabled.

```quagga
hostname <hostname of system>\npassword <your PW>\nenable password <your PW>\nlog file /var/log/quagga/zebra.log\n!\ninterface nm-bond\nip address 10.101.4.147/26 \nmulticast\n!\ninterface eth0\n!\ninterface eth1\n!\ninterface lo

```

--------------------------------

### z/OS INGLIST Command Dialog Example

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=scenarios-test-methodology

This snippet displays a sample output from the z/OS INGLIST command dialog, used for monitoring and managing system resources. It shows the status of various automation components and their observed states.

```text
INGKYST0                  SA z/OS  - Command Dialogs     Line  1     of 28
Domain ID   = IPXFO      -------- INGLIST   ---------    Date = 03/29/10
Operator ID = HEIKES          Sysplex = COHPLEX          Time = 16:52:40
 A Update   B Start    C Stop     D INGRELS  E INGVOTE  F INGINFO  G Members
 H DISPTRG  I INGSCHED J INGGROUP K INGCICS  L INGIMS   M DISPMTR  T INGTWS
 U User     X INGLKUP  / scroll
CMD Name         Type System    Compound      Desired      Observed    Nature
--- ------------ --- --------  ------------  -----------  ----------  -------
    HA2_X        APG            SATISFACTORY  AVAILABLE    AVAILABLE   SERVER
    HA21         APG  COH1      SATISFACTORY  AVAILABLE    AVAILABLE   BASIC
    HA21_LITE_X  APG            SATISFACTORY  UNAVAILABLE  SOFTDOWN    MOVE
    HA21_X       APG            SATISFACTORY  AVAILABLE    AVAILABLE   MOVE
    HA21DBM1     APL  COH1      SATISFACTORY  AVAILABLE    AVAILABLE
    HA21DIST     APL  COH1      SATISFACTORY  AVAILABLE    AVAILABLE
    HA21IRLM     APL  COH1      SATISFACTORY  AVAILABLE    AVAILABLE
    HA21LITE     APL  COH2      SATISFACTORY  UNAVAILABLE  SOFTDOWN
    HA21LITE     APL  COH3      SATISFACTORY  UNAVAILABLE  SOFTDOWN
    HA21MSTR     APL  COH1      SATISFACTORY  AVAILABLE    AVAILABLE
    HA22         APG  COH2      SATISFACTORY  AVAILABLE    AVAILABLE   BASIC
    HA22_LITE_X  APG            SATISFACTORY  UNAVAILABLE  SOFTDOWN    MOVE
    HA22_X       APG            SATISFACTORY  AVAILABLE    AVAILABLE   MOVE
    HA22DBM1     APL  COH2      SATISFACTORY  AVAILABLE    AVAILABLE
    HA22DIST     APL  COH2      SATISFACTORY  AVAILABLE    AVAILABLE
    HA22IRLM     APL  COH2      SATISFACTORY  AVAILABLE    AVAILABLE
    HA22LITE     APL  COH1      SATISFACTORY  UNAVAILABLE  SOFTDOWN
    HA22LITE     APL  COH3      SATISFACTORY  UNAVAILABLE  SOFTDOWN
    HA22MSTR     APL  COH2      SATISFACTORY  AVAILABLE    AVAILABLE
    HA23         APG  COH3      SATISFACTORY  AVAILABLE    AVAILABLE   BASIC
    …
```

--------------------------------

### Configure OSPF Routing (RHEL - Deprecated Quagga)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=lht-ospf-routing-in-red-hat-enterprise-linux-power-systems

Provides example configurations for setting up OSPF routing using Quagga on Red Hat Enterprise Linux. Note that Quagga is deprecated in RHEL 8.x and replaced by FRR. This snippet illustrates the configuration file structure for OSPF.

```bash
# Define OSPF routing in /etc/quagga
# Note: Starting with RHEL 8.x quagga is deprecated. It has been replaced by "Free Range Routing (FRR)". So replace 'quagga' with 'frr' in the samples below.
```

--------------------------------

### Configure OSPF Daemon (ospfd.conf)

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=lht-ospf-routing-in-red-hat-enterprise-linux-power-systems

This snippet shows the configuration for the OSPF daemon in Quagga. It includes hostname, password settings, log file configuration, and OSPF specific settings like router ID and network configuration for area 0. It requires Quagga to be installed and configured with OSPF enabled.

```quagga
!\nhostname <hostname of system>\npassword <your PW>\nenable password <your PW>\nlog file /var/log/quagga/ospfd.log\nline vty\ninterface nm-bond\nip ospf cost 1\nip ospf priority 0\n!\nrouter ospf\nospf router-id <define a router ID>\nnetwork 10.101.4.128/26 area 0 \n
```

--------------------------------

### Execute `start_sapsrv` Script with Parameters

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=scripts-start-sapsrv

This shell script is designed to start a `sapstartsrv` service on z/OS UNIX using the `sapcontrol` utility. It requires specific parameters including SAP system ID, instance name, hostname, job name, and maximum retry attempts for service verification. The script utilizes the `sap_xplatform` library.

```shell
#!/bin/sh
# Version 3.1
# Starts a SAP instance service 'sapstartsrv' via 'sapcontrol' under z/OS® UNIX.
# Uses the 'sap_xplatform' library.

sapcontrol -nr $instance_number -function StartService
```

--------------------------------

### SA z/OS Policy Generation for CF Replication

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=instances-installing-central-services-activate-coupling-facility-replication

This snippet illustrates the output from the SA z/OS HA Wizard when it does not find an ERS profile. It indicates that the system will adapt the SAP policy for local replication, enabling in-place enqueue server restarts and generating an SAP ASCS/SCS policy for CF replication. This output guides users on which manual modification steps can be skipped.

```Text
...
Specify a SAPSID or X to exit:
HA1
SAP configuration file(s) for SAP system HA1 in /sapmnt/HA1/global/HAzOS/ :
--> ASCS10.conf
Info: no ERS configuration file was found for ABAP SCS.
Info: SAP policy will be adapted for local replication which allows an 
      Enqueue server restart in-place.
A System Automation policy for SAP System 'HA1' will be generated.
...
```

--------------------------------

### Start Remote Application Server Instance

Source: https://www.ibm.com/docs/en/bcfsoz/index_topic=scripts-start-as

This script initiates a remote application server instance. It requires the hostname, instance directory, instance type (0 for ABAP, 2 for Java), a unique job name, and the maximum number of retries. An optional 'via' parameter can specify the remote execution method, defaulting to SSH for AIX, Linux, or Windows.

```shell
start_as <hostname> <InstDir> <InstType> <jobname> <maxretries> [<via>]
```
Tokens:
Raw