You are currently viewing the legacy RunMyJobs documentation site. This site will be taken down later this month.
All current and future RunMyJobs documentation, including versions 2023.3 and later, can be found here.
Please update your bookmarks. Use the version dropdown menu to select the documentation you need.

← rs_all_registry_keysrs_applications →

on-site-related topic rs_all_triggers

The following table lists the columns for the rs_all_triggers view. The equivalent jcs_all_triggers view is available for backward compatibility reasons. The difference between the two is the data type of the date/time columns; the rs_* views use TIMESTAMP WITH TIME ZONE while the jcs_* views use DATE.

Column Datatype Description
TRIGGER_PARTITION VARCHAR2 The partition of the trigger
TRIGGER_NAME VARCHAR2 The name of the trigger
TRIGGER_TYPE NUMBER The type of trigger
TRIGGER_POINT
ENABLED VARCHAR2 Is the trigger enabled
STATUS VARCHAR2 The status of the trigger
SCOPE VARCHAR2 The scope of the trigger
note

TRIGGER_NAME: Trigger names in v7 start with the type of trigger. This is not true anymore in v8.

note

TRIGGER_TYPE: The ON_JOB_STATUS_CHANGE trigger is split into four different triggers in v8. Therefore the BeforeJobOnChange, BeforeJobOnChangeMaintenence, BeforeJobPreRunning and the BeforeJobPostRunning trigger types are all mapped to 5=ON_JOB_STATUS_CHANGE. You can use the new column trigger_point to make this distinction. The v7 trigger types ON_DDL, ON_EVENT_STATUS_CHANGE, ON_JOB_RECALCULATE, ON_QUEUE_STATUS_CHANGE, ON_STARTUP, ON_SHUTDOWN and ON_CONFIRM_MONITOR do not exist in v8 anymore.

note

TRIGGER_POINT: New in v8, gives the trigger point code as used in v8.

note

STATUS: This column will always return 'VALID', because triggers in v8 should always be valid.

note

SCOPE: This is column is not implemented yet.

plsqlTopic

onsiteTopic

← rs_all_registry_keysrs_applications →