Data Set Triggering

Products

• CA Workload Automation CA 7 Edition
• Automic Automation Intelligence
• CA Unicenter Job Management Option
• CA Workload Automation iDash

Issue/Introduction

I had an issue with a file triggering a job. The dataset definition is set up correctly and the LCTLG show that the DSN was created and recognized by CA 7.  The  triggered job entered the queue and there DSN was listed as being satisfied.  Yet, there was another input DSN that was not satisfied.  Why?

Environment

Release : 11.3

Component : CA-7

Resolution

You must load the job creating the DSN with a MAINT=N on the DB.1 panel.  This causes all DSNs to be tracked a NORM data sets, which are then requirements for the job to run.  The solution is the mark those datasets as PERM on the DB.6 panel so that those datasets are no longer a requirement.