Differences between STATIC and DYNAMIC triggers

Products

• CA CIS
• CA Common Services for z/OS
• CA 90s Services
• CA Database Management Solutions for DB2 for z/OS
• CA Common Product Services Component
• CA Common Services
• CA Datacom/AD
• CA ecoMeter Server Component FOC
• CA Easytrieve Report Generator for Common Services
• CA Infocai Maintenance
• CA IPC
• Unicenter CA-JCLCheck Common Component
• CA Mainframe VM Product Manager
• CA Chorus Software Manager
• CA On Demand Portal
• CA Service Desk Manager - Unified Self Service
• CA PAM Client for Linux for zSeries
• CA Mainframe Connector for Linux on System z
• CA Graphical Management Interface
• CA Web Administrator for Top Secret
• CA CA- Xpertware
• CA Compress Data Compression for MVS
• CA Compress Data Compression for Fujitsu
• CA Unicenter Job Management Option

Issue/Introduction

• Static trigger
  
  
  • Has no calendar defined to it
    
    
  • Brings in by autoscan
    
    
  • Fire multiple times.
    
    
  • It can never be used as a predecessor as it will never be marked complete.
    
    
• Scheduled trigger
  
  
  • Has a calendar defined to it
    
    
  • Brings in by autoscan
    
    
  • Fire only once.
    
    
  • This trigger can be used as a predecessor.

Note:

• Static Triggers do not get purged from the tracking file with new day autoscan whereas Scheduled Triggers (with backlog=no) get purged with new day autoscan.

Environment

Release:
Component: CA90S