Customizing with the sample job EQARMTSU

You need to create directories in z/OS® UNIX and copy sample configuration files from the installation directory to these directories for customization. The sample job EQAW.SEQASAMP(EQARMTSU) is provided to help you complete these tasks.

Follow the instructions within the EQARMTSU member and submit the job to customize your installation. The job performs the following tasks:
  • Create /etc/debug/* and populate it with sample configuration files.
  • Create /var/debug/* as work directories required to run the service.
  • Set the proper z/OS® UNIX file permissions on the files and directories.
The following sample files are copied to /etc/debug by the sample job:
eqarmtd.env
Environment variables that control, for example:
  • Which internal and external ports to use for the service.
  • Where to locate the security keystore file for SSL encryption. You can use the sample keystore file from Debug Profile Service located in the /etc/debug directory.
  • Whether to allow headless code coverage collection.
eqahcc.env
Properties that control headless code coverage collection, for example:
  • Where code coverage results are stored. By default, the results are output to $HOME/CC/user_ID, where $HOME is the home directory of the user running Remote Debug Service. You can specify a different root location than $HOME/CC/. Ensure that the code coverage users know the path to this directory to access results and have the following authority:
    • A minimum of read access to the parent directory to read their user ID subdirectory root_location/user_ID, where root_location is one of the following:
      • The value for the output property specified in eqahcc.env
      • $HOME/CC, where $HOME is the home directory of the user that is running Remote Debug Service
      The subdirectory and the results within inherit the permissions of the parent directory. You can add user access through group or public permissions.
    • Enough authority to change the ownership of z/OS UNIX files. Remote Debug Service changes the owner of both the subdirectory and code coverage results to the user ID. When users do not have authority, results can still be created, but users can only manage any results based on file permissions.
  • Whether to support only connections from the local host.
For more details on headless code coverage options, see Starting and stopping the headless code coverage daemon.Not all options for headless code coverage are supported in Remote Debug Service. The eqahcc.env file provides all the supported options.

Edit the files /etc/debug/eqarmtd.env and /etc/debug/eqahcc.env, and customize them to match your system environment.

You can run the sample job EQARMTSU more than once. If a file exists in the configuration directory, a backup is created for the existing file before a new one is copied over.