Glossary
The language of mainframe agentic ops.
A working reference for the abend codes, mainframe systems and agentic-AI terminology used across the Progull platform. Built for operators and the executives who fund them.
A3 terms
- Abend Mainframe
- Abnormal end. A z/OS job or step terminates before completion due to a system or user error (e.g. S0C7, U4038).
- Agentic AI Agentic AI
- An AI system that operates in a perceive–reason–act loop, executing tasks under explicit policy and authority instead of returning only suggestions.
- Autonomous mode Operations
- Operating mode in which Progull executes remediations without per-incident human approval, within a pre-approved policy scope.
B2 terms
- BYOCBring Your Own Cloud Operations
- Deployment topology in which Progull runs inside the customer's cloud tenant. Customer owns the network, IAM and key material.
- BYOKBring Your Own Key Security
- Customer-supplied encryption keys (via AWS KMS, Azure Key Vault, HashiCorp Vault). Progull never sees the master key material.
C3 terms
- CICSCustomer Information Control System Mainframe
- IBM transaction processing system on z/OS. Hosts the OLTP workloads that batch jobs typically depend on.
- CMDBConfiguration Management Database Operations
- System of record for IT assets and their relationships. Progull writes per-incident CI updates and reads dependency graphs.
- Control-M Mainframe
- BMC's workload scheduler. Progull reads the dependency graph and proposes scheduler adjustments via the CTM API.
D2 terms
- DB2 for z/OS Mainframe
- IBM relational database on the mainframe. Progull ingests catalog metadata and IFCID lock traces (196, 313) natively.
- Deadlock Mainframe
- Two or more units of work each hold a lock the other needs. DB2 nominates a victim; SQLCODE -911 reason 00000068.
G1 terms
- GDGGeneration Data Group Mainframe
- Versioned dataset family on z/OS. Common source of SB37 abends when generations grow unbounded.
H1 terms
- Hallucination gating Agentic AI
- Policy that rejects hypotheses below a confidence floor, requires corroborating telemetry, or requires citation of a known signature before acting.
I1 terms
- IFCID Mainframe
- Instrumentation Facility Component ID. DB2 telemetry events; IFCID 196 / 313 surface lock and deadlock detail.
J2 terms
- JCLJob Control Language Mainframe
- The declarative language that defines z/OS batch jobs: steps, datasets, dependencies and resource requirements.
- JES2 Mainframe
- Job Entry Subsystem 2 — z/OS spool, scheduler and output manager. Progull integrates natively, no 3270 scraping.
L1 terms
- LPARLogical Partition Mainframe
- Isolated execution environment on a mainframe. Acts as an independent operating system instance.
M2 terms
- MTTDMean Time To Detect Operations
- Average elapsed time from fault occurrence to incident creation.
- MTTRMean Time To Recovery Operations
- Average elapsed time from incident detection to service restoration. The headline Progull metric.
P4 terms
- Playbook Agentic AI
- Versioned, typed sequence of remediation actions Progull may execute for a class of abend, under explicit policy gates.
- Playbook v4 DSL Agentic AI
- Progull's authoring language for playbooks: typed actions, parameterized approvals, signed publication.
- Policy-as-code Agentic AI
- Authority, scope and approval rules expressed as version-controlled code, reviewed alongside playbooks in your change pipeline.
- PROCProcedure Mainframe
- Parameterized JCL template included by jobs at submission time. Often the source of inherited misconfiguration.
R5 terms
- RACF Security
- IBM's mainframe security manager. Source of authorization for every action Progull performs on z/OS.
- Reasoning trace Agentic AI
- Signed, machine-readable record of how Progull arrived at a decision: signals consumed, hypotheses considered, playbook chosen, actions executed.
- Recommend mode Operations
- Operating mode in which Progull proposes remediations to a named human for approval, then executes.
- RPORecovery Point Objective Security
- Maximum acceptable data loss measured in time. Progull's stated RPO is ≤ 5 minutes.
- RTORecovery Time Objective Security
- Maximum acceptable downtime. Progull's stated RTO is ≤ 30 minutes.
S7 terms
- S0C7 Mainframe
- Data exception abend. Typically a non-numeric value in a numeric field during COBOL arithmetic.
- S322 Mainframe
- CPU time-limit abend. A job step exceeded its declared TIME= allowance.
- SB37 Mainframe
- Out-of-space abend on dataset extend. Primary and secondary allocations exhausted.
- SDSFSystem Display and Search Facility Mainframe
- Native z/OS interface for spool, active job and operator command inspection. Progull integrates via the SDSF callable services.
- Shadow mode Operations
- Operating mode in which Progull observes and proposes, but does not act. The first mode of every rollout.
- SQLCODE -911 Mainframe
- DB2 'deadlock or timeout — rollback performed'. Reason code 00000068 = deadlock; 00000080 = lock timeout.
- SYSLOG Mainframe
- z/OS system log. Captures operator messages, system events and console traffic.
U1 terms
- U4038 Mainframe
- Language Environment user abend. Often surfaces failed CEE3204/CEE3207 conditions raised in COBOL or PL/I runtime.
Z1 terms
- Zero-touch operations Operations
- Operating posture in which a defined class of incidents is detected, diagnosed, remediated and closed without human intervention, under audit.
Missing a term you'd expect to see here? Email sai.rohit@progull.com and we'll add it.