Class structure

Edit online

This topic explains the purpose of classes and contains information about the class hierarchy for the SAP resources that are defined in the *SAPSRV add-on policy. Figure 1 shows the class hierarchy for the SAP resources.

A class in SA z/OS® can be used to define common characteristics, which are shared by many resources. The *SAPSRV add-on policy makes intensive use of the class concept in SA z/OS.

Like in the old *SAP add-on policy, C_SAP_USS is the top-level class for all SAP resources. Since this class was not changed between the *SAP add-on policy and the *SAPSRV add-on policy, you do not need to replace it, if your active production PDB already contains it. All SAP z/OS UNIX resources should refer to this class. It contains definitions, which are common to all SAP resources. It defines, for example, the RESTART OPTION as ALWAYS. This is because any abnormal end of a UNIX application appears to SA z/OS as a shutdown outside of the automation condition. The restart option ALWAYS enables SA z/OS to correctly recover from these situations.

Depending on your environment you might need to change definitions in this class. For example, on a slow system you might have to adjust the Start Delay and Start Cycles of your SAP z/OS UNIX resources.

The SA z/OS policy command line is restricted to 160 characters. Therefore, for example all ASCS or SCS resources, contain the tilde symbol (~) in the template of the command lines for starting and stopping the resources. The tilde saves a lot of space in that command lines compared to defining the home directory of the <sid>adm.

Below this top-level class the *SAPSRV add-on policy contains classes, which are usage-specific (C_SAP_<SID>_ABAP or C_SAP_<SID>_JAVA, C_SAP_<SID>_BASE and C_SAP_<SID>_WEBD) and which depend on the specific SID of the resources that reference it. Most of the SID-specific information is contained in the symbol definitions of these classes.

The resource names and the values for the symbols in the *SAPSRV add-on policy contain as SAP system ID (SID/SAPSID) a value of <SID> for the standard ABAP and Java™ central services components and <CON> for the optional SAP Web Dispatcher components.

These template classes from the *SAPSRV add-on policy need to be converted into SID-specific classes as shown in Table 1 for the sample SIDs HA1 and WD2 for the SAP system and an SAP Web Dispatcher respectively. The class names are shown with their SA z/OS entry names. Their corresponding subsystem names are the same, without the last three letters, for example, C_SAP_HA1_B, see also Table 1.

Table 1. SID-specific classes
Class name in *SAPSRV	Sample class name generated by wizard	Comment
C_SAP_<SID>_BASE	C_SAP_HA1_BASE	SAP Class for SAPSID-specific data, needed by ABAP or Java VIPA resources
C_SAP_<SID>_ABAP	C_SAP_HA1_ABAP	SAP Class for ABAP SAPSID-specific data, needed by ABAP resources
C_SAP_<SID>_JAVA	C_SAP_HA1_JAVA	SAP Class for Java SAPSID-specific data, needed by Java resources
C_SAP_<CON>_WEBD	C_SAP_WD2_WEBD	SAP Class for Web Dispatcher, needed by SAP Web Dispatcher resources
C_SAP_SM<n>_SMDA	C_SAP_DA<n>_SMDA	SAP Class for Diagnostics Agent <n> (n = 1,2,3), needed by SAP Solution Manager Diagnostics Agent resource

The following figures show the class structure before (Figure 1) and after (Figure 2) it was adapted to the specific SID HA1:

*SAPSRV add-on policy - class structure in SA 3.4 — Figure 1. *SAPSRV add-on policy - class structure for SAP Central Services resources

Figure 2. *SAPSRV add-on policy - class structure for HA1 sample system

For a complete list of symbols that are used in the *SAPSRV add-on policy, refer to the definition of this policy that is shipped with the SA z/OS product. Also, refer to the file SAPHAwizard.pdf, which is shipped inside the ING_sap.tar file in the SA z/OS z/OS UNIX directory /usr/lpp/ing/SAP.