Running Ironstream agent - ironstream_for_servicenow_discovery_1 - 7.5

Ironstream for ServiceNow® Discovery for IBM Z® Installation
Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for ServiceNow® Discovery
Version
7.5
Language
English
Product name
Ironstream for ServiceNow® Discovery for IBM Z®
Title
Ironstream for ServiceNow® Discovery for IBM Z® Installation
First publish date
2007
Last edition
2024-08-08
Last publish date
2024-08-08T06:53:53.282486

You can use the sample JCL "VP390" in the hlq.SAMP dataset to run the Ironstream agent.

The Ironstream job may be run as a started task or a batch job.

Note:
  • If you are monitoring multiple mainframe LPARs, the Ironstream job must be run with the same job name on all LPARs, or add an identifier name (which can access the jobs via the modiFy console command) to the job when starting that is the same on all LPARs.
  • If you want to capture Software Information from SMP/E, you may need to set MSGLEVEL=(1,0) as shown in the JCL sample to suppress dataset allocation messages.

To Start the VP390 Job as a Batch Job

To start the VP390 job as a batch job, follow these steps:
  1. Modify the hlq.SAMP(VP390) dataset names according to the instructions at the top of the job.
  2. Execute using the SUBMIT command.

To Start the VP390 Job as a Started Task

To start VP390 as a task, follow these steps:

  • Copy the hlq.SAMP(VP390) procedure into the started tasks library.
  • Modify the dataset names according to the instructions at the top of the job.
  • It is recommended that the REGION parameter be set with either REGION=0M or REGION=64M if REGION=0M is not possible.
  • Start the VP390 procedure from a z/OS console with this command:
    S VP390

To Stop the VP390 Task

To stop the VP390 task:

Enter the following command from a z/OS console:

P VP390