Trigger Check

Use the Trigger Check screen to compare the triggers IntelliDealer expects on key database files (physical files) in your session's files library with the triggers actually defined on those files at your dealership. The screen helps administrators confirm trigger health after maintenance, a PPU, or when logging, interfaces, or request-queue processing behaves unexpectedly.

A database trigger is a programmatic activation on a database file that IntelliDealer can attach so that insert, update, or delete activity on that file can drive logging, outbound interfaces, or request-queue jobs. Triggers use IBM i trigger support; the programs and SQL objects are defined and maintained by IntelliDealer, not by the dealer.

The Trigger Check screen is at Administration > Settings > Trigger Check.

Topics in this section are:

How Triggers are Added to Files

Triggers are not added from the Trigger Check screen. They are installed and removed by IntelliDealer maintenance.

The most common case is a Full Database Reorganization, which removes triggers early in the process and runs trigger maintenance at the end to attach the standard trigger set to your database files. The same trigger maintenance also runs during PPU processing, library creation, and some other jobs (for example, a customer merge). Behind the scenes, full-database maintenance typically uses programs CCP008 (remove) and CCP009 (add); you do not run those programs from this screen.

If maintenance cannot add triggers because a file is in use, some triggers can remain absent until maintenance runs again when the files are available.

What Determines Which Triggers Apply

The grid lists a fixed checklist of database files that IntelliDealer can place triggers on. Whether a given file or event should have triggers for your dealership depends mainly on configuration, not on the grid alone.

Triggers are added or left off based on three broad areas:

  • Logging — File Monitoring and related options (for example, on the COMPUTER maintenance table) and System Specific File Monitoring & Retention on System Settings. When logging for a master file is turned off, trigger maintenance typically does not add legacy logging triggers for that file. For example, if vendor master logging is off, VMASTR can show Missing for Insert, Update, and Delete even though the dealership is configured correctly.

  • System settings and configuration — Other dealership choices in system settings, maintenance tables, and configuration screens determine which files participate in logging, interfaces, and queue processing. Those choices drive which triggers maintenance adds.

  • Licensed features and interfaces — OEM and layered-app interfaces (and related request-queue SQL triggers) apply when the corresponding feature or interface is licensed and configured. That is often a smaller part of the overall trigger picture than logging and system settings. See Interface-related Database Files for files tied to specific integrations.

Note:  Results apply to the files library for your current session only. The checklist covers key files used for logging, interfaces, and request-queue processing; it is not every trigger on the IBM i system.

How to Read Trigger Status

The columns on this screen report the status of a database file. You cannot add or remove triggers from this screen.

Column Display Description
Insert No text The legacy trigger for that event is present, enabled, and operative on the database file.
Update
Delete
SQL Insert No text

Show the optional SQL Insert Program, SQL Update Program, and SQL Delete Program columns:

  • when a program name is listed for an event, no text in the matching status column means the trigger is present

  • when the program column is blank, no text in the status column means not applicable (legacy-only file for that event).
SQL Update
SQL Delete
Any of the above Missing For that file and event, the checklist expects a trigger, but the database file does not have a matching trigger that is enabled and operative. Missing is often normal when logging or a feature is off. It can also indicate a problem after maintenance or when an interface you use requires that trigger. See Interpreting Missing.

Interpreting Missing

Missing does not always mean something is wrong. For most dealerships, most Missing cells reflect configuration: logging turned off, a feature not licensed, or an interface not in use. In those cases, maintenance intentionally does not add triggers, and the grid still labels the cell Missing because the checklist row exists for that file.

Treat Missing as a problem only when:

  • You use logging, an interface, or request-queue processing that depends on that file and event, and behavior suggests updates are not flowing; or

  • Triggers were recently removed or not restored after maintenance (for example, a Full Database Reorganization or PPU) and files were in use when trigger maintenance ran.

When Missing is unexpected, review What Determines Which Triggers Apply (especially logging on System Settings and File Monitoring in maintenance tables). Work with your system administrator to correct configuration or rerun trigger maintenance when appropriate. For OEM and layered-app issues, use Interface-related Database Files to see which integrations are tied to each file name.

Screen Description

The grid shows one row per database file in the checklist. For each file, IntelliDealer reads trigger definitions on your dealership's copy of that file and reports status for legacy triggers (classic TRIG* trigger programs) and, where the checklist defines them, SQL triggers (request-queue programs such as *_INS_REQQ, *_UPD_REQQ, and *_DEL_REQQ).

The fields in the Trigger Check grid are:

Field Description
Database The physical file (table) name in the files library, for example BASE or WOH. The column label in the application is Database; the value is the file name.
Insert Legacy trigger status for insert, update, and delete events on the file. See How to Read Trigger Status.
Update
Delete
SQL Insert SQL (request-queue) trigger status for insert, update, and delete when the checklist includes SQL trigger programs for that file. If no SQL program is defined for an event, that column is not applicable for that row. See How to Read Trigger Status.
SQL Update
SQL Delete

When you need the exact program names while troubleshooting, show the optional columns in the grid for Legacy Trigger Program, SQL Insert Program, SQL Update Program, and SQL Delete Program.

Select Show only missing Triggers to limit the grid to rows where at least one legacy or SQL trigger column shows Missing. Many of those rows are expected when logging or features are turned off; see Interpreting Missing.

Interface-related Database Files

The following table is a reference for OEM and layered-app integrations that depend on triggers on specific database files. It does not list every reason a file has triggers; logging and system settings drive most of what maintenance adds. If an interface you use stops sending or receiving updates after maintenance, check trigger status on the listed files when that interface is licensed and configured. Feature numbers indicate the license required when applicable.

Database Interfaces
BASE John Deere SMO (6423)
CGIBASE Integrated Rental (6276), John Deere SMO (6423), John Deere ERS (6120), John Deere Equipment Upload (6258), John Deere Quote II (6163), Midnet Media Equipment Web Upload (6162), Product Support Rental (6512)
CGIGRP Integrated Rental (6276), John Deere SMO (6423)
CGIHIST Integrated Rental (6276), John Deere SMO (6423)
CGIOPT Integrated Rental (6276), John Deere SMO (6423)
CGIMC Integrated Rental (6276)
CGIINH CNH Data Exchange Platform (6429)
CMASAA Integrated Rental (6276)
CMASCON Integrated Rental (6276), John Deere SMO (6423)
CMASSH John Deere SMO (6423)
CMASTR Integrated Rental (6276), John Deere SMO (6423)
CMASTRE Integrated Rental (6276), John Deere SMO (6423)
COACMAST Integrated Rental (6276)
PARTMAST John Deere Parts Locator (1004), Komatsu ASL (6158), John Deere Prism (6193), AGCO API (6219), Vermeer Parts Inventory (6196), Volvo Marketplace (6522), Shopify (6422), Parts Price Update Extract (6257)
PFWTAB Integrated Rental (6276), John Deere SMO (6423), Komatsu ASL (6158)
MEMOS John Deere SMO (6423)
SALORD CNH Data Exchange Platform (6429)
WOH Integrated Rental (6276), CNH Data Exchange Platform (6429), Vermeer Work Order (6430)
WOLAB WOLAB Timecard Integration (6405)
WOR Integrated Rental (6276), CNH Data Exchange Platform (6429), Vermeer Work Order (6430)
VMASTR John Deere SMO (6423)

Note:  Other database files on the Trigger Check grid are part of the standard checklist but are not listed here. This table includes files with known interface dependencies only.

Security: 994 - WebAdmin, Access Utilities

Revision: 2026.10