Defining user profiles to control what can be measured

To implement the Strobe access filter, you establish a set of generic rules that Strobe uses to validate requests. Valid syntax for the rules includes:

• A high-level qualifier that identifies the rule as belonging to Strobe. The default is $STROBE, but you can supply another value in the PARMLIB using the PROFILE parameter. (See SECURITY_PROFILE= for information about the PROFILE parameter.)
• A system identifier equal to the one-to eight-character MVS system name of the target system for the request.
• An identifier that defines the target address space type for the request. The values are:
  • ’job’ for batch jobs
  • ’stc’ for started tasks
  • ’tsu’ for TSO users
  • ’appc’ for advanced program-to-program communication
  • ’omvs’ for OpenEdition.

• A one- to eight-byte job name mask or an asterisk (*) that restricts access to a job name or set of job names. The value depends on the security system at your site.