z/OS S-TAP fails to show active the Guardium system

If z/OS S-TAP fails to show active on the Guardium system, restart the inspection-core.

Symptoms

z/OS S-TAP fails to show active on the Guardium system after you start it for the first time. The policy is correctly configured with a DB2 or IMS Collection Profile and installed. The z/OS S-TAP is properly configured to use port 16022. All messages on the mainframe indicate connectivity.

Causes

If the collector has not been actively used as a collector since being built and configured, the sniffer appears to time out port 16022.

Environment

z/OS is affected.

Resolving the problem

Restart the inspection-core by using the CLI command restart inspection-core.