← Monitoring and Managing ProcessesFiltering Processes →

Advanced Process Search

To allow you to search overviews quickly, a process search box, named IntelliSearch, has been implemented. This search is able to use the following phrases as criteria:

  • numbers - ids
  • times - of requested start, run start, and run end time.
  • remote - remote information
  • names - names of queues, process servers, applications, descriptions (process names) or process definition names
  • parameters/parameter values - search processes based on parameter names and optionally their values
  • status - the status of the job

Prefixes allow you to search a specific property, all name searches (for example queues or parameter names) are case-insensitive, value searches (for example parameter values) are case-sensitive.

note

You cannot search for a step, only the main chain process as well as Chain processes.

note

Some fields can contain spaces, like Process descriptions and parameter values for example; to specify a value with spaces, use double quotes (").

note

If a specific search returns no results, the overview will be empty.

Operands

Specifying more than one prefix will be evaluated as <prefix:term1> OR <prefix:term2> when the process can only have one property searched by the prefix. Queries with multiple different prefixes are evaluated as <prefix1:term1> AND <prefix2:term2>. Multiple parameter prefixes are always evaluated with AND as a process can have multiple parameters.

Example

  1. Finding all processes that belong to SAP system PR1 or PR2:
queue:PR1_Queue queue:PR2_Queue

or

qId: PR1,PR2

or

sapq:PR1 sapq:PR2

or

sapq:PR1,PR2

All evaluated with a logical OR as a process can only have one queue.

  1. Finding all processes that ran on queue PR1 and that reside in the EXAMPLE application:
queue:PR1 application:EXAMPLE

This is evaluated with a logical AND as there are two different search prefixes in the query.

  1. Finding all processes with parameter combinations

parameter:Param2==Two parameter:Param1

Returns all processes that have parameter Param2 set to value Two (case-sensitive) and another parameter named Param1, of which the value is not a criteria.

parameter:SAP_SYSTEMS==PR1 parameter:CLIENT==800 parameter:SAP_USER_NAME==JDOE

Returns all processes that use client 800 of SAP system PR1 that run as SAP user JDOE.

Multiple parameter terms are evaluated with a logical AND since processes can have multiple parameters.

Search Order

When you do not specify a prefix, then the following search order is used:

  1. Process ID.
  2. Process Definition.
  3. Application.
  4. Process Name.
  5. Process Description.
  6. Process Parameter.
  7. SAP Queue.
  8. SAP Process Server.
  9. Remote ID.
  10. Remote System.
  11. Remote Status.
  12. Requested Start Time.
  13. Run start.
  14. Run end.
  15. A combination Requested start/Run start/Run end (it will search in any of these).
  16. Process Status.

Using Numbers

Any number is assumed to be a process ID.

For example, 111 would display the job with ID 111. If this process is part of a chain, the process will be shown expanded in the containing chain. When searching on ID, the process will also always be selected.

Dates & Times

Searches for all processes between a specified date/time. The search-criteria has to be specified in 24h times. The search is done on any of three date/times:

  • requested start time
  • run start
  • run end

There are different syntaxes for searching by date/time:

The date/time is specified using the following codes: seconds (s), minutes (m), hours (h), weeks (w), months (M), and years (y).

  • yyyy/MM/dd - the specified date.
  • yy/MM/dd - the century is assumed to be the current century.
  • MM/dd - the year is assumed to be the current year.
  • yyyy/MM/dd_hh:mm:ss - the specified time for the specified date, default range is +/- 1 minute.
  • yyyy/MM/dd_hh:mm - the specified time for the specified date, default range is +/- 15 minutes.
  • yy/MM/dd_hh:mm:ss - the specified time for the specified date, the century is assumed to be the current century, default range is +/- 1 minute.
  • yy/MM/dd_hh:mm - the specified time for the specified date, the century is assumed to be the current century, default range is +/- 15 minutes.
  • MM/dd_hh:mm:ss - the specified time for the specified date, the year is assumed to be the current year, default range is +/- 1 minute.
  • MM/dd_hh:mm - the specified time for the specified date, the year is assumed to be the current year, default range is +/- 15 minutes.
  • hh:mm:ss - the specified time today, default range is +/- 1 minute.
  • hh:mm - the specified time today, default range is +/- 15 minutes.
  • now - the current date and time, default range is +/- 1 minute.
  • hh:mm~nn{s,m,h,d,w,M,y} - the number indicated by nn defines a range.
  • yyyy/MM/dd_hh:mm:ss-yyyy/MM/dd_hh:mm:ss - the specified range of dates/times. Any date/time syntax above is supported in the range.
  • yyyy/MM/dd_hh:mm-now or yyyy/MM/dd_hh:mm- - if you use now in the range, or leave one blank, the current time is used.

For example, 22:00-23:00 would show all processes that have one of the three times in the range of 22:00-23:00 and 22:00~90m would result in all processes that have one of the three times in the range of 20:30-23:30 to get listed.

When you want to specify a specific date/time, use a prefix.

Prefixes

  • req, requested - Requested start time
  • rs, runstart - Run Start time
  • re, runend - Run End time
  • statuschangedbefore, scb - (internal) search for processes that changed status before a certain ISO-8601 period

For example, runend:22:00-23:00 would restrict the above example to show only processes which have a Run End Time in the specified range and req:22:00~90m would restrict the above example to display processes which have a Requested Start Time in the specified range.

Remote

Allows you to query for processes that run on remote systems with information of the remote system.

The following prefixes are available:

  • rid, remoteid - the remote ID.
  • rsys, remotesystem - the remote system
  • rstat, remotestatus - the remote status of the job

For example, rid:A12S34H3 would display the process which has the remote ID A12S34H3 and remotestatus:error would display all processes that have the remote status error.

Status

Allows you to display processes with a specific status.

The following prefix is available:

  • s, status - the status of the job

The status allows you to use the following comma separated list of values:

  • case sensitive status names
  • status codes
  • problem which maps to E,K,U or Error, Killed, and Unknown.

Example

Several ways to display processes which have reached a final state and have not reached status Completed.

status:Error status:Killed status:Unknown
status:Error,Killed,Unknown
status:E,K,U
status:EKU
status:problem

Two ways to display processes that have reached status Completed.

status:Completed
status:C

Background and Top-Level Processes

  • tl, toplevel - only display top-level processes, not child processes
  • bg, background - display background processes as well

Note that when you specify background: or bg:, then matching background processes are included in the search results alongside other matching processes.

note

A search on jobid, jobdefinition or jobname does not need a bg:true, because these automatically include all processes that match the search criteria.

Names

When a string is entered without a prefix, the search is done in the search order above.

Prefixes

If you want to search for a specific name, you can use one of the following prefixes.

  • a, application - find processes from an application, wildcard search
  • ae - find processes from an application, exact match
  • c, comm, comment - find processes with a comment, wildcard search
  • d, desc, description - find processes with a process name, wildcard search
  • jde - find processes from a process definition, exact match
  • jd, jobdefinition - find processes from a process definition, wildcard search
  • j, jobname - find processes with specific description, wildcard search
  • p, param, parameter - searches for processes with the parameter and optionally its default value, wildcard search
  • pse - find processes that run on a process server, exact match
  • ps, processserver, psId - find processes that run on a process server, wildcard search
  • qe - find processes from a queue, exact match
  • q, queue, qId - find processes from a queue, wildcard search
  • qId - find processes using the UniqueId of the process's queue
  • sappse - find processes that run on an SAP System process server, exact match
  • sapps, sapprocessserver - find processes that run on an SAP System process server, wildcard search
  • sapqe - find processes that run in an SAP System queue, exact match
  • sapq - find processes that run in an SAP System queue, wildcard search

For example, qe:System would display all processes that are in the queue named System, q:Sys would display all processes that ran in a queue containing the string sys in its name. The search expression jde:System_Sleep would display all processes of the process definition System_Sleep.

You can also specify multiple combinations of the above, when you specify more than one queue, for example, processes of all specified queues will be displayed. For example, PR1_Queue PR2_Queue PR3_Queue q:QA4_Queue would display all processes from the four queues PR1_Queue, PR2_Queue, PR3_Queue, and QA4_Queue. q:PR1_Queue PR2_Queue PR3_Queue ps:PR1_ProcSerVer would for example display all processes that are on the specified process server as well as in the specified queues.

A number of prefixes have wildcard and exact match variants. Searches using the wildcard variant of these prefixes are performed with leading and trailing wildcards ( * ).

Process Parameters

Process parameter IntelliSearch allows you to search for process parameters and parameter/'default value' combinations as follows:

  • p:<name> - search for processes with a parameter named <name>
  • p:<name>=<value> - search for a process with a parameter named <name> which has a value containing <value> ("=" means contains)
  • p:<name>==<value> - search for a process with a parameter named <name> which has a value set to <value> ("==" means equals)

You can filter on name alone, but you cannot filter on value alone.

Both the invalues and outvalues of JobParameters are searched.

There are four types of values which can be searched:

  • Strings
  • Dates
  • Times
  • Numbers

If a value can be converted to a number, then the string and number values are searched. The same goes for dates and times. If a value cannot be converted into a date, time or number, only the string values are searched.

The format for dates is restricted to yyyy-MM-dd (for example 2023-11-16), the format for time is restricted to HH:mm (for example 13:31). The format for numbers is restricted to dot notation for decimals (for example, 3.1415) and integer values.

  • = - means like or between in SQL.
    • string value is LIKE '%value%'.
    • For date "2023-11-16" => BETWEEN 2023-11-16 0:00:00 AND 2023-11-16 23:59:59.
    • For time "13:36" => BETWEEN 13:36:00 AND 13:36:59.
    • For number "3.14" => BETWEEN 3.14 AND 3.14099 (so adding 099 at the end of the string representation of the number).
  • == - means = in SQL, exact match.
  • For string "value" => IN (value).
  • For date "2023-11-16" => BETWEEN 2023-11-16 0:00:00 AND 2023-11-16 0:00:00.
  • For time "13:36" => BETWEEN 13:36:00 AND 13:36:00.
  • For number "3.14" => = 3.14.

See Also

job &fcaJobDefinitionJobl; search

← Monitoring and Managing ProcessesFiltering Processes →