CA 7 - Why Jobs are in Skeleton Status.

book

Article ID: 194613

calendar_today

Updated On:

Products

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

Issue/Introduction

How can I check the reason why some of the jobs are found in skeleton status of CA 7 ?

What is the reason why the job cannot attached JCL in CA 7? Even all skeleton jobs have the correct JCL

 

Environment

Release : 11.3

Component : CA-7

Resolution

When a CA 7 job remains in SKELETON status in the queue, it means that for some reason,

CA 7 could not 'attach' the JCL for that job.  The JCL is written to the trailer queue when a job record comes into the request queue. 

There can be many different reasons for the failure to attach JCL. 

When this occurs, a message is written to the browse dataset (DD name BROWSE usually in CA 7's proc) that will help determine why the JCL could not be attached.

The job needs to be canceled with a FORCE=YES and DEMANDed.