Role sap_opsyscheck 

The role sap_opsyscheck is checking some basic operating system settings that are required to run SAP applications on the operating system IBM i smoothly. It can be executed prior to the first SAP installation on a new system or partition with the operating system IBM i or as a “health check” on systems or partitions where SAP is already installed. The following checks will be performed:

Check if the user profile used to execute the Ansible role has at least the special authorities *ALLOBJ, *SECADM and *JOBCTL.
Check if the SAP Host Agent is installed. If it is installed, show release level and patch information.
Show the release level of the installed operating system.
Check the usage (in percent) of the system auxiliary storage pool (ASP) and compare it with the threshold that can be configured in the IBM i system service tools (STRSST).
Check the status of the database cross reference (XREF) files on the host.
Show the group ID (GID) of user profile R3GROUP and check if it is the same on all specified hosts.
Check the fill level of the job tables and issue a warning if they are more filled than specified (default: 10%).

During the execution of the role sap_opsyscheck, the directory specified in sapopsyschk_dir_temp_managednode will be created if it does not exist. At the end of the execution, the directory and its contents will be deleted.

Table of contents

Role sap_opsyscheck

Requirements 

This role is intended for the operating system IBM i. The target system must be enabled to execute Ansible playbooks. For details, see the prerequisites section in Ansible Content for IBM Power Systems - IBM i with SAP Software.

The role sap_opsyscheck must be executed as user profile QSECOFR or a user profile with similar authorities, user class *SECOFR or at least special authorities *ALLOBJ, *SECADM and *JOBCTL. If the user profile does not have these special authorities, the results of the role are unpredictable.

The check for the job tables filling requires IBM i 7.3 with SF99703 Level 22, IBM i 7.4 with SF99704 Level 10, or a higher IBM i release. On releases prior to IBM i 7.3, the check is skipped. On IBM i 7.3 or IBM i 7.4 without the required PTF level, the check will result in an error because column IN_USE_JOB_TABLE_ENTRIES cannot be found in catalog view QSYS2.SYSTEM_STATUS_INFO.

Tags 

Specify one or multiple of the following tags (separated by comma) to specify what checks you want to perform. If you do not specify a tag or the tag -t all, all checks will be performed.

Tag	Usage
`user_check`	Check if the current user has at least the special authorities ALLOBJ, SECADM and *JOBCTL.
`sap_host_agent_check`	Check if the SAP Host Agent is installed and display release and patch level if found.
`os_version`	Display the release level of the operating system.
`asp_check`	Display the total capacity, capacity used and percentage used of the system ASP and issue a warning if the defined threshold is exceeded.
`r3group_id`	Show the group ID (GID) of user profile R3GROUP and compare id with the group ID on all specified systems.
`xref_status`	Check the status of the database cross reference (XREF) files on the host.
`job_tables`	Check the status of the job tables and issue a warning if they are more used than specified in variable `sapopsyschk_asp_threshold` (default: 10%).

Variables 

Variable	Usage	Required
`sapopsyschk_dir_temp_managednode`	Directory path on the target host for creation of a temporary soft link	Yes 1
`sapopsyschk_asp_threshold`	Threshold for ASP usage, when to issue a warning	Yes 2

Remarks:

1: Default provided.
2: The default is being retrieved from the ASP threshold that has been configured in the system service tools (STRSST). The default setting is 90%.

Defaults 

Suggested default values are provided in defaults/main.yml:

Variable	Default
`sapopsyschk_dir_temp_managednode`	`"/tmp/ansible"`
`sapopsyschk_job_tables_percent_input`	`10_`

Dependencies 

None.

Example Playbook 

The example playbook is used to check operating system related settings on all configured hosts with the operating system IBM i. It is based on the assumption that a configuration file and an inventory file with contents similar to the configuration documentation exist in the current directory. The example playbook in the current directory is named sap_opsyscheck.yml and has the following contents:

- hosts: ibmi_servers
  roles:
  - role: <ansible_dir>/roles/sap_opsyscheck

To execute this playbook, enter the command:

ansible-playbook sap_opsyscheck.yml