DB2 Commands

db2 activate db <dbsid>                               #Activate Database
db2 backup database <sid>                          #Take an offline backup to specified location
"disk:\location"
db2 connect to <db2sid>                              #Establish connection to an instance
db2 deactivate <dbsid>                              #Deactivate an active database
db2 drop database <target db2sid>              #Delete and instance
db2 force application all                              #Close all applications that uses DB2 Database.
db2 get db cfg for <db2 sid>                       #Display configuration parameter of an instance
db2 get dbm cfg                                          #Display configuration parameter of database manager.
db2 list tablespaces show detail                  #Displays table space information
db2 list utilities show detail                        #Display Database backup status
db2 restore db <sid> from “disk:\path”      # Restore database from a backup image
replace history file
db2 rollforward db <db2sid> query status  #Display rollforward status
db2 rollforward db <SID> to end of logs  #Apply all pending logs
db2 terminate                                              #Close the database connection
db2 update db cfg for <db2 sid>                 #Change value of a instance configuration parameter.
using <parameter_name> <new value>
db2 update dbm cfg using <parameter_name>  #Change value of a database manager configuration parameter.
<new value>
db2_kill -all                                                        #Kill a hanged instance
db2cc                                                              #Open DB2 Control Centre
db2cmd                                                              #Open DB2 Command line Tool
db2level                                                             #Display DB2 version and fix pack level
db2licm -l                                                          #View license information
db2start                                                             #Start Database Normaly
db2stop                                                            #Stop Database Normaly
db2stop force                                                   #Stop Database forcely
db6level                                                            #Display DB2 Client Version


db2admin stop                                                 #stops the db2 administration server instance
db2admin starts                                               #starts the db2 administration server instance
db2 list applications                                       #shows the current connections (for more
                                                                           detail add the ‘show detail’ parameter)
db2 connect to <dbname>                             #connects to the database named in <dbname>
db2 connect reset                                           #closes the database connection held by that user

db2 update db cfg for                                     #To Update Db parametre with new value
<dbname> using <param> <new setting>
db2 backup db <dbname> to                           #very simplistic backup DB command
 <bk_dir> with 4 buffers
db2 backup db <dbname>                              #Simple offline backup, do stopsap and db2start
use TSM
db2 backup db <dbname>                              #Simple online backup using TSM
online use TSM
db2 backup db <dbname> tablespace <tablespace name> online use TSM
db2 list history backup all for <SID>| more                #lists history for the backups
 
db2 restore db <sid> from . taken at <timestamp>     #restore from disk

This will put the database in ROLLFORWARD
state
db2 restore db <sid> use TSM taken at <timestamp>

Rollforward

db2 rollforward db <sid> to <time to recover to>

To get the rollforward status

db2 rollforward db <sid> query status

Alter Tablespaces

db2 “alter tablespace <?> extend (all containers <no of pages>)”

To run stats for all tables


dmdb6srp –n <SID> -t ALL

Stop the Db2-License-Daemon-Process                          'db2licd end'                                                  
'ps-ef   grep db2licd' (for checking)                                

Install the DB2-License                                                   db2licm -a <RDBMS-CD-Path>\db2udbee.lic'
                                                                                           'db2licm -l' (for checking)
                                                                             
                                       
Query to check table size in Db2

db2 "select substr(a.tabname,1,30), (a.fpages*PAGESIZE/1024) as TAB_SIZE from
syscat.tables a, syscat.tablespaces b where a.TBSPACEID=b.TBSPACEID ORDER BY
TAB_SIZE desc"|more

The db2 diagnostic log for SAP instances is usually stored under <instance home>/db2dump/db2diag.log. This directory
will also house any dumps that may occur. If using the std SAP archive exit for DB2, the log and error files for the archives will resides here as well. Simply
view with ‘more’.


To Read db2diag


db2diag -g db:= -gi level=severe


db2diag -g db:= -gi level=error


db2diag -gi "level=error" -H 1d


db2 force application all                                                                  #Terminate all applications


db2stop force                                                                                  # Forcefully stopping database


db2level                                                                                       # Current version and fix pack details


db2 list db directories                                                                   #  Directories used by database


db2 list utilities show detail                                                            #Running utilities like backup/restore/runstat


db2 list history backup all for <DBsid>                                       # Backup history of database

db2 list history backup all for <DBSID> | more                            #Lists history for the backups

db2 restore db <dbname>                                                               # Database restore


db2 " select distinct tabschema from syscat.tables "                      #DB2 Schema name search

db2pd -logs -db <dbname>                                                              # Archive log details


db2 update db cfg for <SID> using LOGARCHMETH1 DISK:/db2/<SID>/log_archive


db2top                                                                                         #DB2 monitoring tool c

HANA High Availability

Availability the measure of a system's operational continuity, is expressed as a percentage of time,
inversely proportional to downtime. For example, if a given system is designed to be available for 99.9% of the time (sometimes called "three nines"), its downtime per year must be less than 0.1%, or 9 hours.

Downtime is the consequence of outages, which may be intentional (e.g. for system upgrades) or caused
by unplanned faults. A fault can be due to equipment malfunction, software or network failures, or due to a
major disaster such as a fire, a regional power loss or a construction accident, which may decommission
the entire data-center.

High Availability is a set of techniques, engineering practices and design principles for Business
Continuity. This is achieved by eliminating single points of failure (fault tolerance), and providing the ability
to rapidly resume operations after a system outage with minimal business loss (fault resilience).

Fault Recovery is the process of recovering and resuming operations after an outage due to a fault.
Disaster Recovery is the process of recovering operations after an outage due to a prolonged data center or site failure. Preparing for disasters may require backing up data across longer distances, and may thus be
more complex and costly.

HANA High Availability:

As an in-memory database, SAP HANA must not only concern itself with maintaining the reliability of its data in the event of failures, but also with resuming operations with most of that data loaded back in memory as quickly as possible.

The following figure shows the phases of High Availability. The first phase is readiness, being prepared for the inevitable fault. During this time, data is backed up and standby systems are ready to take over. A fault must be detected, either automatically or administratively (to avoid false positives), and a recovery process is put in action. Finally, the fault must be repaired, and the system may need to be reverted to the original configuration (failed back), to be ready again for the next fault.

Different RPO/RTO values can be associated with different kinds of faults. Business critical systems are expected to operate with an RPO of zero data loss in the case of local faults, and often even in the case of a disaster. But the challenges of disaster recovery are different from locally recoverable faults; to achieve zero RPO and low RTO, data must be replicated synchronously over longer distances, which impacts regular system performance and may require more expensive standby and failover solutions. All of this leads to tradeoff decisions around the attributes of fault recovery functionality, cost and complexity. SAP accordingly offers complementary design options, including three levels of Disaster Recovery support and two automatic Fault Recovery support features, summarized in the following table and further discussed in the sections below.

SAP HANA BACKUP:

Even though SAP HANA database is a IN-Memory database ,i.e data residing in memory ,it has got its own persistency .
Data is always saved from memory to disk at save points and data changes are written into redo log files.So that in case of failure they can be used for recovery.

                   

Data in SAP HANA is constantly written into disk from memory at savepoints. Databackup can be performed with database being online

To perform a databackup in SAP HANA, below prerequisites are essential
DATABASE USER: Backup in SAP HANA can only be performed with a database user, so it is necessary to create or use a existing user with the necessary privileges and authorizations
BACKUP_ADMIN: This is the system privilege that the Database user used for performing the backup should have .
CATALOG READ: System privilege that the Database user need to have for collecting the information required by the backup wizard

Data backup can be taken manually or can be scheduled

SAP HANA database backups up its services (nameserver,nameservertopology,indexserver,xsengine and statisticserver)
Which will be stored in a specific destination mentioned in configuration file  global.ini with the parameters
basepath_databackup and basepath_logbackup

The parameters pointing as below to the default valuesbasepath_databackup=$(DIR_INSTANCE)/backup/data used for databackup,
basepath_logbackup==$(DIR_INSTANCE)/backup/log respectively for logbackup

Backup can be performed with the below sql query

BACKUP DATA USING FILE  ('<path><prefix>')

The backup files generated by performing the databackup of SAP HANA database will be as below
COMPLETE_DATA_BACKUP_databackup_0
COMPLETE_DATA_BACKUP_databackup_1
COMPLETE_DATA_BACKUP_databackup_2
COMPLETE_DATA_BACKUP_databackup_3
COMPLETE_DATA_BACKUP_databackup_4

Where COMPLETE_DATA_BACKUP is the prefix(default) ,which can be changed to the required prefix while performing a data backup.



Log Modes in SAP HANA:

There are 3 types of log modes in SAP HANA which influence the log backup
•              Normal: In this mode ,log backup happens where the log segment is nearing full which will prevent the log segment full situation.Log backup is automatic by default which can be changed by editing the global.ini parameter enable_auto_log_backup .For point in time recovery this mode is recommended.
•              Overwrite:In this mode log segments are freed upon each savepoints and no log backup happens
So no point in time recovery can be done.
•              Legacy:in this mode log segments are freed,  once the full database backup is performed.Log backup is not performed.

Log backup generates a backup files of the log segments at the interval which is specified in the global.ini file parameter log_backup_timeout_s.if the log segment becomes full before the log backup timeout interval ,log backup will be performed .This log backup time interval can be set only if the database is running with automatic log backup enable
The path of the logbackup will be at the location $DIR_INSTANCE/backup/log

Configuration Files Backup:

Backup of the SAP Hana database configuration file
SAP Hana database configuration files are not backed up automatically as a part of database backup .So all the configuration files like global.ini,indexserver.ini,nameserver.ini,sapprofile.ini,daemon.ini and other customer-specific configuration files needs to be backed up manually



SAP HANA RECOVERY

Pre-steps:

<sid>adm:user password is required to shutdown the target system where the
backups have to be recovered upon

Configuration:between source and target system ,if backups are to be recovered on
different target system


Databackup and logbackups taken before the system failure or the time to which the system
needs to be recovered

Available Recovery types option with SAP HANA:

Recovering the database to the most recent state:used for recovering the database
to the time as close as possible to the current time . Databackup ,logbackup available
since last databbackup and log area are required to perform the above type recovery

Recovering the database to the point in time :used for recovering the database to the specific
point in time. . Databackup ,logbackup available since last databbackup and log area are
required to perform the above type recovery.

Recovering the database to specific database:Used for recovering the database
to a specified data backup.specificdatabackup is required for the above
type of recovery option.


we can perform Backup and recover using HANA studio.


Storage Replication:

One drawback of backups is the potential loss of data from the time of the last backup to the time of the
failure. A preferred solution therefore, is to provide continuous replication of all persisted data. Several SAP
HANA hardware partners offer a storage-level replication solution, which delivers a backup of the volumes or
file-system to a remote, networked storage system. In some of these vendor-specific solutions, which are
certified by SAP, the SAP HANA transaction only completes when the locally persisted transaction log has
been replicated remotely. This is called synchronous storage replication.

System Replication is an alternative HA solution for SAP HANA, System replication employs an "N+N" approach,
with a secondary standby SAP HANA system with the same number of nodes as the active, primary system.
Each service and instance of the primary SAP HANA system communicates pair-wise with a counterpart in
the secondary system.


The secondary system can be located near the primary system to serve as a rapid failover solution for
planned downtime, or to handle storage corruption or other local faults. Alternatively, or additionally,
a secondary system can be installed in a remote site for disaster recovery. Like Storage
Replication, this Disaster Recovery option requires a reliable link between the primary and secondary sites.

The instances in the secondary system operate in live replication mode. In this mode, all secondary system
services constantly communicate with their primary counterparts, replicate and persist data and logs, and
typically load data to memory. The secondary system does not accept requests or queries.

In an alternative configuration, called system replication without data-preload, the secondary system
does not pre-load data, and hence consumes very little memory. This allows the secondary system to serve
dual purposes, for instance as a development or test/QA system with separate storage. Before failover,
these activities must of course be turned off. The tradeoff is a longer RTO in case of failover.

Here is how system replication works. When the secondary system is brought up in live replication mode,
each service component establishes a connection with its primary system counterpart, and requests a
snapshot of the data. From then on, all logged changes in the primary system are replicated. Whenever logs
are persisted in the primary system, they are also sent to the secondary system.

A transaction in the primary system is not committed until the logs are replicated, as determined by a log replication option:

Synchronous: The primary system waits with committing the transaction until it receives a reply
that the log is persisted in the secondary system. This mode guarantees immediate consistency
between both systems, at a cost of delaying the transaction by the time for data transmission and
persisting in the secondary system.

Synchronous in-memory: The primary system commits the transaction after it receives a reply that
the log was received by the secondary system, but before it was persisted. The transaction delay in
the primary system is shorter, because it only includes the data transmission time.

Asynchronous (from SPS6): the primary system commits the transaction after sending the log
without waiting for a response. This eliminates the synchronization latency, at the risk of minor
theoretical data-loss during failure. This mode is most useful when the secondary site is hundreds
of kilometers away from the primary site, or when reducing latency is critical.

SAP HANA SPS 11 new features

SAP HANA SPS 11 is available and comes with new capabilities to innovate modern
applications, accelerate insights, and simplify IT. Customers continue to select SAP HANA
to run mission critical applications and create next-generation applications that converge transactional,
analytical, predictive and streaming data processing. Now, SAP HANA SPS 11 allows you to innovate even faster by leveraging micro services architectures through a broaden choice of programming languages. And you can also transparently accelerate insights on any kind of data – including geospatial and data streams – from any source. With SAP HANA SPS 11

SAP HANA SPS 11 also delivers several enhancements to development tools and data modeling,
to simplify application development and accelerate application performance.
These include a new “where-used list” functionality to find object dependencies,
enhancements to SQL scripts, and enhancements SAP HANA calculation views to SAP Power Designer.

Accelerate Insights:

SAP HANA SPS 11, can transparently mange large data volumes by moving data across memory, disk, and Hadoop/SAP IQ with the Data Lifecycle Manager (DLM) tool. This allows you to gain total visibility from data across your organization and optimize price-performance considerations

To speed-up Hadoop data analysis, SAP HANA SPS 11 includes a new SAP HANA Vora connector. SAP HANA Vora is the new in-memory query engine for Apache Spark and Hadoop that adds business context to analysis by combining enterprise and Hadoop data.

In the area of data integration, SAP HANA SPS 11 delivers new adapters to replicate or perform bulk data loads from SAP Business Suite DataSources (BW Extractors), SAP Business Suite on SAP ASE, Microsoft Excel, and SOAP Web Services. To facilitate data discovery, the new Enterprise Semantic Services available in SAP HANA SPS 11 helps developers, and business users search SAP HANA database tables and remote sources to identify relevant business content. These services use metadata, semantic information, and table contents to build knowledge graphs that answer users’ search requests.

In SAP HANA SPS 11, Smart Data quality adds survivorship rules for data cleansing and reverse geocoding capabilities for data enrichment. Survivorship rules use multiple data records to create a new one, based on predefined custom rules, such as creation date, completeness of the data and source of the data. Reverse geocoding helps to identify all addresses in given radius from the geolocation.

 Simplify IT:

SAP HANA is an ideal platform to run mission-critical applications and simplify IT landscape with its built-in application services, advanced data processing and data integration and quality services.

SAP HANA SPS 11 comes with several high availability and disaster recovery capabilities, to further strengthen the platform and deliver business continuity. The new Hot Standby functionality helps you regain faster access to data after a data center failure, by enabling applications to fail-over to a fully up-to-date standby database. The primary and the standby databases as kept synchronized by continuously replaying logs.

Additional capabilities in SAP HANA SPS 11 can help you shorten the database recovery time even further. For example, you can now analyze database logs and parameters while the database is down, restart the database recovery from the point of failure, rather than from the beginning, and perform parallel backup and recovery.

In the area of security, SAP HANA SPS 11 delivers built-in SQL injection prevention functions to prevent malicious SQL code execution, and a new security dashboard in SAP HANA Cockpit to give you complete visibility into security KPIs.

For your SAP landscapes, integration with SAP Solution Manager – Early Watch Alerts and SAP Security Baseline – simplifies the monitoring of security breaches and the implementation of default security policies across all SAP systems.

In SAP HANA SPS 11, SAP HANA database administration has been further simplified. For example, you can automatically partition rapidly growing tables using dynamic range partitioning and achieve optimal resource utilization for data loads and transformations, by allocating system resources (CPU threads and memory) to individual processes.

On the tools front, SAP HANA Cockpit, a modern web based administration tool, supports delta backup, database start, stop & restart, analysis of diagnostic files, log analysis when the system is down, and the troubleshooting during scheduled or unscheduled system maintenance.

SAP HANA Cockpit also includes enhanced administration capabilities for Dynamic Tiering, Smart Data Access, Remote Data Sync and the SAP ASE accelerator. SAP HANA Database Control Center, a tool designed to streamline management of multiple SAP HANA systems, comes with enhanced installation capabilities and centralized configuration management.

Openness is a key theme of SAP HANA. You can expand your hardware choices as IBM Power Systems include support for SAP Business Suite applications, SAP Business Warehouse scale-out features, and virtualization of SAP HANA production instances for more flexible deployment options.

Additionally, the SAP HANA certification program has been expanded to include synchronous storage mirroring tools, Smart Data Integration/Smart Data Access adapters and additional database backup and recovery tools.

1. Download SAP HANA SPS11 from SAP Service Marketplace : https://support.sap.com/swdc
2. SPS11 release notes are available at http://help.sap.com/hana/Whats_New_SAP_HANA_Platform_Release_Notes_en.pdf
3. The SPS11 release note (2227464) can be found at http://service.sap.com/sap/support/notes/2227464

Gateway

Gateway system communicates with other SAP and Non SAP system e.g. SAP:BW,CRM,SCM: Non SAP

Architecture of the SAP Gateway: 

Each instance of an SAP System has a gateway. The gateway enables communication between work processes and external programs, as well as communication between work processes from different instances or SAP Systems.

Gateway Processes:

The SAP Gateway is made up of various processes:

·        Gateway read process

·        Gateway monitor

These processes are described in the following topics.

Note :Earlier gateway releases that support DCAM and SNA have additional gateway work processes (gwwp, gwwp.exe).

Gateway Read Process:

Gateway read (gwrd, gwrd.exe) is the main process in the gateway system.

It is started by the application server (dispatcher) and checked by it periodically.

The gateway reader receives and processes all CPI-C requests.

Note:

If the executable gwrd program is called without parameters or with the switch -help, the program outputs a description of the possible command parameters, as well as all the patches

Gateway Monitor:

The gateway monitor (gwmon, gwmon.exe) is used to analyze and administer the SAP Gateway.

When you start it, you initially get a list of active CPI-C connections. You can call up all the other monitor functions via a menu.

You can monitor the gateway from the SAP System (transaction SMGW) or from the operating system. 

What would happen if your Gateway is not working?

1-     No RFC is working

2-     No connection with other sap system and non sap systems

3-     In dual stack case : No connection between ABAP instance and JAVA instance. Java instance will go down. But as per new scenarios Netweaver 7.10 Onwards JAVA instance and ABAP instance would be working independently and communicate through JCO rfc connection only. So there is no master slave concept between java instance and ABAP instance (My concept) .Why I have  called ABAP as master instance and Java as slave .Because ABAP start java instance and Java instance can be stopped independently. Without affect ABAP instance .But You can to run java instance without ABAP instance.

SMGW:

Displaying Clients Currently Logged On 

You can display a list of currently logged on systems via Goto ® Logged on systems .

The following values are displayed for each system that is logged on:

·        LU Name: With CPIC connections via TCP/IP, this field describes the host on which the partner program is running or supposed to run.

If we check in SM21 system log, we can find out that this particular connection was terminated by the administrator at that particular time stamp.

How to monitor SAP Gateway from the OS  level ?

Gateway can also be monitored at the os level (in particular if the gateway is running in a system without AS ABAP) using program gwmon (.exe) 

Note:

The term "logical unit" is a term borrowed from SNA and describes a logical node in an SNA network. The remote partner program is intended to run on this node.

·        TP Name: Name of the transaction program or the name of the program that was started by the gateway.

·        System Type The following values are possible:

·         ¡        NORMAL_CLIENT : Normal client (external program)

·         ¡        LOCAL_R3: Local SAP System

·         ¡        REMOTE_GATEWAY: connection to remote gateway

·         ¡        FROM_REMOTE_GATEWAY: connection from a remote gateway

·         ¡        REGISTER_TP: Registered transaction program

·        Host Name: Name of host client is running on

·        Host Address: All TCP/IP names on the host. If there are several network cards then there may be several entries here. Usually 5 alternative host names are supported.

·        Last Req: Time of last activity

·        Status: Connection status to a client or another gateway at TCP/IP level. The default value is CONNECTED.

In the following cases connections are highlighted in color in the gateway monitor.

·         ¡        Connections with status PENDING (handshake while opening the connection) are colored orange

·         ¡        If the data packets could not be fully written in the network connections, the connection is colored green. 

If this status lasts for a while, it indicates network problems, or the partner program cannot read any data from the network, because it is busy with other tasks that take time (for example, BRBACKUP).

Parameter	Description	Default Value
gw/accept_remote_trace_level	Specifies whether the trace level of a CPIC or RFC connection should be transferred. (configuration parameter)	1
gw/accept_timeout	Maximum allowed time period for the login process of a server program. (timeout parameter)	60 seconds
gw/acl_file	Specifies the name of an access control list (ACL) file. (security parameter)	No ACL file is used
gw/acl_mode	The parameter defines the behavior of the gateway, if no ACL file (gw/sec_info oder gw/reg_info) exists. (security parameter)	1
gw/alternative_hostnames	List of alternative host names for local host. Network Parameters	No alternative host names
gw/close_routes	Specifies the period (in seconds) after which a route to a remote gateway through which a CPIC connection is open is closed. (timeout parameter)	120 seconds
gw/conn_disconnect	Specifies the maximum number of seconds for which an active connection can remain in the status DISCONNECT or DISCONNECTED. (timeout parameter)	900 seconds
gw/conn_pending	Specifies the maximum number of seconds for which a connection can remain in the status CONN_PENDING. (timeout parameter)	60 seconds
gw/cpic_timeout	Specifies the maximum wait time for a connection setup. (timeout parameter)	20 seconds
gw/deallocate_timeout	Time period in which the network connection for a DEALLOCATE must be closed. (timeout parameter)	600 seconds
gw/frag_timeout	Determines the timeout for incomplete network write operations. (timeout parameter)	120 seconds
gw/gw_disconnect	Specifies the maximum number of seconds for which a GW-GW connection can remain inactive. (timeout parameter)	1800 seconds
gw/internal_timeout	Specifies the timeout value for NiReadand NiWrite calls. (timeout parameter)	0 milliseconds
gw/keepalive	Specifies the maximum time period (in seconds) before the system checks, using a ping, whether the partner is still alive when there is no data transfer across a CPIC connection. (timeout parameter)	300 seconds
gw/listen_queue_len	The operating system must keep requests in a queue while the connection is being set up. (parameter for resource management)	512
gw/local_addr	Network Parameters
gw/logging	With this parameter you can configure gateway logging. (configuration parameter)	see detailed parameter documentation.
gw/max_conn	Specifies the maximum number of connections that can be active at a time. (parameter for resource management)	500
gw/max_conn_per_dest	Configures how many TCP/IP connections to a remote gateway or ABAP Application Server can be opened in parallel. (parameter for resource management)	10
gw/max_overflow_size	This parameter specifies the size of the overflow area in bytes. (parameter for resource management)	10000000 Bytes (10 MB)
gw/max_overflow_usage	Specifies the usage of the overflow area as a percentage from which the gateway slows down its clients, that is it sends SYNC requests. (parameter for resource management)	20 %
gw/max_sleep	Specifies the maximum time in seconds for which the gateway read process sleeps on the select. (timeout parameter)	20 seconds
gw/max_sys	Specifies the maximum number of clients connected at a time. (parameter for resource management)	300
gw/monitor	This parameter determines whether the gateway should communicate with the monitor locally or remotely. (configuration parameter)	1
gw/netstat_once	There are high availability solutions in which the IP addresses can move from one host to another. This means that the entries read when the gateway was started up may no longer be valid. In such cases, the current configuration must always be read using the command when making the test for a local IP address. Network Parameters	1
gw/nibuf_max	Number of entries in the host name buffer. Network Parameters	Used by NI interface
gw/nibuf_retry	Time period after which the invalid entries are deleted in the host name buffer. (timeout parameter)	Used by NI interface.
gw/nifragtest	Tests fragmentation on the network layer. Network Parameters	0
gw/nitrace	Activates or deactivates the trace for NI connections. Network Parameters	0
gw/prxy_info	This parameter is used to specify the proxy settings of the gateway. (configuration parameter)	/usr/sap/<SID>/<instance>/data/prxyinfo
gw/reg_info	File with the security information for registered programs. (security parameter)	<Data directory>/reg info
gw/reg_keepalive	Specifies the maximum time period in seconds before the system checks, using a ping, whether the partners are still alive in a registered server program with the status WAITING. (timeout parameter)	300 seconds
gw/reg_lb_default	Default value for the load of a server if its IP address cannot be found in the list. (Load balancing parameter)	20
gw/reg_lb_ip	Specifies the load value for an IP address or for a range of IP addresses. (Load balancing parameter)	see detailed parameter documentation.
gw/reg_lb_level	Defines the type of load balancing for registered programs. (Load balancing parameter)	1
gw/reg_timeout	Specifies the maximum wait time for setting up the connection with a registered program. (timeout parameter)	60 seconds
gw/remsh	Specifies the call path of the remote shell to start programs on other hosts. (configuration parameter)	see detailed parameter documentation.
gw/rem_start	Determines how remote CPIC programs are to be started. (configuration parameter)	REMOTE_SHELL
gw/req_stack_size	Specifies the number of CICP requests that can be stacked for each CPIC connection. (parameter for resource management)	30
gw/resolve_phys_addr	This parameter specifies whether theGateway will resolve names of IP addresses.	Perform name resolution
gw/resolve_timeout	This parameter is used to activate a time measurement for the network lookup calls (host name - IP address, service name - port number). (timeout parameter)	0 milliseconds
gw/sec_info	File with the security information. (security parameter)	<Data Directory>/secinfo
gw/so_keepalive	Parameter to activate the socket option KEEPALIVE for the network connections. Network Parameters	0
gw/ssh	Specifies the call path of the secure shell to start programs on other hosts. (configuration parameter)	see detailed parameter documentation.
gw/start_in_homedir	Determines the directory in which the gateway starts programs. (configuration parameter)	1
gw/start_threshold	If programs are started using rexec, blockages may occur in the gateway. To make it easier to analyze any blockages, a warning is written to the trace file once the time has exceeded by the defined time. (configuration parameter)	5 seconds
gw/startup	File containing statements to start programs when the gateway starts. (configuration parameter)	-
gw/stat	Determines the status of the gateway statistics after starting the gateway. (configuration parameter)	0
gw/tcp_security	(security parameter)
gw/timeout	Specifies the timeout value for the establishing connections to other gateways. (timeout parameter)	0 milliseconds
snc/enable	Specifies whether the gateway accepts connections that protect the data via SNC. (security parameter)	0
snc/gssapi_lib	Path for the shared library of the security system in use. (security parameter)	-
snc/identity/as	Identity of the gateway application server (security parameter)	-
snc/permit_common_name	Specifies whether the gateway can use a default SNC name specified by the parameter snc/identity/as, if an SNC name for the connection cannot be read from the secinfo. (security parameter)	0
snc/permit_insecure_comm	Specifies whether the gateway accepts connections without SNC. (security parameter)	0
snc/permit_insecure_start	Specifies whether the gateway may establish connections with programs that communicate without SNC. (security parameter)	0