S/MF
StackMF Knowledge Base • z/OS
DevOps & Automation 10 min read 2026-09-27

Fixing CA-7 Data Set Trigger (DSN) Failures: Resolving Missed SMF Type 15 Close Events

A
Reviewed by Anshu
Chief Technology Architect & Mainframe Systems SME
Enterprise Modernization Advisory
Google AI Overview & Featured Snippet Quick Answer

Executive Summary: Fixing CA-7 Data Set Trigger (DSN) Failures: Resolving Missed SMF Type 15 Close Events

CA-7 Data Set Triggers (DSN) automatically initiate downstream batch jobs when an input file is closed. Troubleshoot why jobs fail to trigger due to disposition issues (DISP=MOD vs NEW), SMF Type 15 intercept drops, or SASSSMI0 exits.

1 Problem Statement & Architecture Context: Fixing CA-7 Data Set Trigger (DSN) Failures: Resolving Missed SMF Type 15 Close Events

A critical overnight billing job fails to launch automatically in CA-7 after upstream step STEP040 finishes writing PROD.FEED.DAILY. Operations teams wait hours before discovering the schedule stalled.

2 Technical Root Cause & Architecture Mechanics

CA-7 monitors dataset creation using the SMF Type 14/15 close exit (SASSSMI0):

1. Disposition Filtering: CA-7 only triggers on datasets closed successfully with DISP=(NEW,CATLG) or DISP=(MOD,CATLG) if configured in the dataset definition.

2. Step Condition Code: If the creating step abended or completed with a condition code higher than the threshold, CA-7 suppresses the trigger.

3. Queue Full / Exit Deactivated: If the CA-7 SMF intercept queue fills up during peak traffic, SMF records drop.

3 Implementation Guide & Modernization Strategy

# 1. Inquire Dataset Definition in CA-7

From the CA-7 3270 terminal:

text
LDSN,DSN=PROD.FEED.DAILY

Verify attributes:

  • TRIG: Ensure dataset trigger is enabled (YES).
  • RO: Check reverse offset and creation criteria.

# 2. Check the Creating Step JCL Disposition

Ensure the dataset was created with a triggering disposition:

jcl
//SYSUT2   DD DSN=PROD.FEED.DAILY,
//            DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(50,10)),UNIT=SYSDA

If using DISP=SHR, CA-7 will NOT trigger unless TRIGGER=ALWAYS is explicitly configured.

# 3. Manually Demand the Successor Job

To restore production while diagnosing:

text
DEMAND,JOB=BILLNIGHT,SET=ND

Technical Specifications Matrix

Attribute Specification
Target Environment IBM z/OS • DevOps & Automation
Key Technologies CA-7, Workload Automation, Dataset Triggers
Delivery SLA Accelerated Sprint Delivery via StackMF Pods
Technical Reviewer Anshu, Chief Technology Architect • StackMF Architecture Pod

Production Readiness & Verification Checklist

? Frequently Asked Questions

What is the root cause of Fixing CA-7 Data Set Trigger (DSN) Failures: Resolving Missed SMF Type 15 Close Events? ↓
CA-7 monitors dataset creation using the SMF Type 14/15 close exit (SASSSMI0):.
How do you resolve Fixing CA-7 Data Set Trigger (DSN) Failures: Resolving Missed SMF Type 15 Close Events in production? ↓
CA-7 Data Set Triggers (DSN) automatically initiate downstream batch jobs when an input file is closed. Troubleshoot why jobs fail to trigger due to disposition issues (DISP=MOD vs NEW), SMF Type 15 intercept drops, or SASSSMI0 exits.
How can teams prevent Fixing CA-7 Data Set Trigger (DSN) Failures: Resolving Missed SMF Type 15 Close Events in enterprise pipelines? ↓
Verify SMF intercept exit `SASSSMI0` status during system IPLs.

Recommended Technical Runbooks

Authoritative Reference Documentation

Official IBM manuals, Redbooks, and vendor technical advisories:

Related Topics: CA-7Workload AutomationDataset TriggersSMFBroadcom Replacement
Diagnostic Runbook Notice & Nominative Fair Use Disclaimer

This diagnostic runbook is published by StackMF Technologies LLP for educational and architectural reference only. All code snippets, JCL, and procedures are provided "AS IS" without warranty of any kind. Always test changes thoroughly in non-production sysplex environments prior to production rollout.

IBM, z/OS, CICS, Db2, IMS, RACF, and IDz are registered trademarks of International Business Machines Corporation. Broadcom, CA-7, and Endevor are trademarks of Broadcom Inc. All other trademarks belong to their respective owners and are referenced under the Nominative Fair Use Doctrine (US Lanham Act 15 U.S.C. ยง 1125 / Section 30 of the Indian Trade Marks Act, 1999) solely for technology compatibility and diagnostic identification. StackMF Technologies LLP is an independent consulting entity not affiliated with or endorsed by these vendors. View Full Legal & IP Policy →

Enterprise Advisory

Struggling with Critical Mainframe Incidents or Vendor Renewal Pressure?

StackMF deploys certified Senior Mainframe Engineers fluent in both z/OS legacy internals (COBOL, DB2, CICS, VSAM, CA-7, Endevor) and modern cloud stacks (React, Kafka, AWS, Git). Onboard dedicated pods in 48 hours or cut Broadcom licensing by 60%.