Define a task to monitor objects in the plan
by specifying a query in a query line. The objects for which you can
create a monitoring task query are: jobs, critical jobs, job streams,
workstations, files, resources, domains, and
prompts.
To monitor objects in the plan, perform the following steps.Note: For all the
details about options and fields displayed in the panels, see the online help by clicking the
question mark located at the top-right corner of each panel.
-
In the navigation toolbar, click
.
-
From the Engine drop-down list, select the check box related to the
engine where the task must run.
You can specify more than one engine only if the type of object you want to monitor is
job or job stream.
- From the Object Type drop-down
list, select the type of object you want to monitor. The available
object types correspond to the type of engine and number of engines
you selected.
For a distributed engine, you can create
a monitoring task query for: Job, Critical Job, Job Stream, Workstation, File, Resource,Domain, and Prompt.
For a z/OS engine, you can create a monitoring task query only for:
Job, Critical Job, Job Stream,
Workstation, and Resource.
- From the List Plans drop-down
list, you can select the current plan or an archived plan related
to the selected engine. Plans are only stored for the distributed
engines, you cannot select the field for critical jobs.
- In the Query text box,
type the query that specifies the filter criteria to apply to the
object type you selected. If you are familiar with the conman syntax,
the query syntax is quite similar; for example, the syntax for filtering
jobs is similar to conman showjobs. If you are
not familiar with conman, click Edit to
create your query by selecting the options from the filter criteria
that are displayed (for details, see step 7).
In general,
the following rules apply to the query syntax:
- The plus symbol (+) is used to separate filter parameters.
- The hash key symbol (#) is used to separate the workstation name
from the job stream name, for a distributed engine.
- The exclamation mark (!) is used to separate
the workstation from the job stream name, for a z/OS engine.
- The ampersand symbol (@) replaces one or more alphanumeric characters
(wild card).
- The period (.) separates the workstation name, job stream name
from the job name.
- The slash (/) separates the folders.
For example, to display the status of all jobs in the
acctg
job stream on
workstation
site3
for a distributed engine, type the following string in the
Query text box:
site3#/foo/acctg.@
or:
site3#/foo/acctg
For more example about queries and syntax, see
Example.
- Click Run to run the task immediately.
The results are displayed in table format in a new page. From this page you can continue
to edit the query in the query line or click
Edit to make changes to the user
interface selections. The list of results are updated with the changes you make.
Note: After running, the query is automatically saved in the
Query drop-down list, enabling you to reuse it for future monitoring. You can
manage the list either by removing a single query by selecting the minus (-) next to the query to be
removed, or clearing all saved queries by selecting Clear Query
History.
- Alternatively, click Edit to
select the filter criteria from a list of options rather than specifying
them in the Query text box.
The
Query text field is automatically populated with the
appropriate syntax.
For details about the filter criteria that apply
to the object type you selected, refer to the following sections:
- Type a name for the monitoring task in the Task
Name text box.
-
Click Save to save the task.
Each task you create and save is included in the Query drop-down
list. You can reuse or modify each saved task, as required.
- Select a task from the Query drop-down
list and click Edit. Duplicate to
create a new task exactly like the one you selected. This is useful
if you want to work with a task that is not your own, but is shared
with you.
- Select one or more tasks from the Query drop-down
list and click Edit. Click Delete to
delete them. You cannot delete tasks that are not your own.
- Click Run to run the task.
A list of results is displayed in table format in a new
page. Alternatively you can view the output of the selected task in
a report format in a separate HTML file. Click View as
Report to view the output.
You have created your task that, when run, creates a list
of results satisfying your filtering criteria and showing, for each
object in the list, the information contained in the columns you selected
to view.
The following examples
show the syntax used to create some specific queries:
- Job query in a distributed environment
- To query for all jobs, in all job streams and on all workstations on a specific distributed
engine, with the following characteristics:
- Having a dependency on a workstation with a name beginning with
FTA_1
- Beginning with Job_A in a job stream beginning with
JS_A
in FOLDERA folder
- Scheduled to run at 10 a.m. on October 31, 2015
- Currently in Waiting state with a priority in the range of 1 -
50
specify the following query in the query
line:/@/@#/@/@.@+follows=/@/FTA_1#/FOLDERA/JS_A@(1000 10/31/2015).JOB_A@+state=#Waiting,#Ready+priority=1,50
- Job query in a z/OS environment
- To query for all jobs in a job stream ending in 001,
on all workstations beginning with HR in a
z/OS environment, with the following characteristics:
- Having an internal status of Interrupted and Error
- Having a priority of 1
specify the following query in the query line:HR@!@001.@+jsfrom=1000 10/10/2015+state=E,I+priority=1