Progull doesn't bolt onto ITSM — it works inside it. Every action against the mainframe is mirrored as a structured ServiceNow update, so your audit, reporting and on-call surfaces don't change.
Progull's detection agent observes the JES spool and SYSLOG, classifies the abend code and opens INC0098231 in ServiceNow with severity, CI, assignment group and first-line context already populated.
The reasoning agent attaches SYSOUT, SYSUDUMP, JCL, DB2 SQLCODE and the last 24h of related change events. A worknote summarizes the explainable diagnosis in plain English for the on-call.
A policy-approved remediation playbook is proposed: resubmit STEP0040 with PARM='CLEAN' after holding the downstream GL feed. The on-call can approve, edit or override.
The remediation agent submits the modified JCL via the approved control path, watches return codes and rolls back automatically if any check fails. Every action is logged as a worknote with timestamp and signature.
The closure agent validates recovery, attaches the full reasoning trace and evidence pack, sets resolution code and closes INC0098231. The case becomes a reusable knowledge article for future S0C7 patterns.
Incidents continue to flow through your existing categories, assignment groups and SLAs.
Every agent action becomes a structured worknote — searchable, reportable, exportable.
Closed cases auto-generate KB candidates that your SMEs curate, not author from scratch.
Progull writes against standard ServiceNow tables and APIs — no custom UI shoved into your operator's face, no parallel ticketing system.
incidentCreate, enrich, update, close — with full worknote stream and resolution codes.
change_requestCorrelate abends to recent CHG records; raise emergency CR when a rollback is needed.
kb_knowledgeAuto-draft KB articles from resolved incidents, queued for SME publishing.
cmdb_ciMaintain CI relationships for LPARs, JES subsystems, CICS regions and DB2 subsystems.
sn_si.alertOpen Security Incident Response alerts when telemetry indicates a data-exposure pattern.
sys_journal_fieldEvery agent input and decision lands as a signed worknote with timestamp and operator ID.
task_slaHonor your SLA definitions, pause/resume rules and breach notifications natively.
flow_designerTrigger or be triggered by your existing Flow Designer flows — no fork in the road.
Progull supports four operating modes per job class, environment and time window. You promote autonomy where it earns its keep.
| Mode | Detection | Diagnosis | Remediation | Closure |
|---|---|---|---|---|
| Shadow | Agent | Agent (silent) | Suggest only | Human |
| Recommend | Agent | Agent | Suggest in worknote | Human |
| Approve | Agent | Agent | Execute on approval | Agent on RC verify |
| Autonomous | Agent | Agent | Execute under policy | Agent |