Managing Serviceguard Extension for SAP Version B.05.10, December 2012

START_WITH_PKG, STOP_WITH_PKG, RESTART_DURING_FAILOVER,
STOP_IF_LOCAL_AFTER_FAILOVER, STOP_DEPENDENT_INSTANCES.
◦ ASTREAT[*]=0 means that the Application Server is not affected by any changes that
happens to the package status. This value makes sense to (temporarily) unconfigure the
instance.
◦ ${START_WITH_PKG}: Add 1 to ASTREAT[*] if the Application Server should
automatically be started during startup of the package.
◦ ${STOP_WITH_PKG}: Add 2 to ASTREAT[*] if the Application Server should
automatically be stopped during halt of the package.
◦ ${RESTART_DURING_FAILOVER}: Add 4 to ASTREAT[*] if the Application Server
should automatically be restarted if a failover of the package occurs. If the restart option
is not used the SAP ABAP Engine has to be configure to use DB-RECONNECT.
◦ ${STOP_IF_LOCAL_AFTER_FAILOVER}: Add 8 to ASTREAT[*] if the Application
Server should automatically be shut down if the package fails over to its node. This
treatment policy will overrule the ${RESTART_DURING_FAILOVER} value if applicable.
◦ ${STOP_DEPENDENT_INSTANCES}: Add 16 to ASTREAT[*] if the instance is a Central
Instance and all specified Dialog Instances with the same ASSID[] should be stopped
prior to it. This treatment policy overrules the treatment policies specified for Dialog
Instances.
• For the ASPLATFORM[*]-array the platform for an Application Server that is controlled by
the package is specified. Supported values include the following:
◦ "HP-UX": standard Application server running on HP-UX
◦ "LINUX": standard Application server running on LINUX
◦ "WINDOWS": Application Server handling is not standardized as there is no standard
way to open a remote DOS/Windows shell that starts SAP Application Servers on the
Windows platform. sap.functions provides demo functions using the ATAMAN (TM)
TCP Remote Logon syntax. They should be replaced by implementations in
customer.functions.
◦ "SG-PACKAGE": The Application Server runs as Serviceguard package within the same
cluster. In this case ASHOST might have different values on the different package nodes.
If this value is used, you also have to specify the Dialog Instance package name in
ASPKGNAME[*]. The common naming conventions for Dialog Instance packages include
the following:
– d<ASNR><SID> (new)
– app<SID><ASNR> (deprecated)
${START_WITH_PACKAGE}, ${STOP_WITH_PACKAGE}, and {RESTART_DURING_FAILOVER}
only make sense if ASSID[]=${SAPSYSTEMNAME}, i.e. these instances need to belong to the
clustered SAP component. ${STOP_IF_LOCAL_AFTER_FAILOVER} and
{STOP_DEPENDENT_INSTANCES}can also be configured for different SAP components.
The following table gives an overview of ASTREAT[*] values and their combination. The
${START_WITH_PKG}, ${STOP_WITH_PKG}, ${RESTART_DURING_FAILOVER},
${STOP_IF_LOCAL_AFTER_FAILOVER}, ${STOP_DEPENDENT_INSTANCES} columns
represent binary values and decimal values in parenthesis that are accumulated in the ASTREAT
column.
Legacy Package Configuration 97