DEFAULT JOB DEFINITION NOT VALID FOR JOB TYPE"
Article ID: 241105
Updated On:
Products
Issue/Introduction
Users are seeing below error when attempting to ADD jobs to CA 7 after upgrading to RELEASE 12.1
" DEFAULT JOB DEFINITION NOT VALID FOR JOB TYPE"
CA-7.023 - r12.1.01 OPERATOR IS LOGGED ON TO TERMINAL BTERM1 AT 09:27:53 ON
22119 092753 JOB
SM20-00 ENTER INPUT DATA
22119 092753 ADD,JOB1,SYSTEM=TEST,USERID=125,JCLID=125,MAINT=Y,MSGCLASS
SM20-25 DEFAULT JOB DEFINITION NOT VALID FOR JOB TYPE
Environment
Release : 12.1
Component : CA 7
Resolution
The job that is defined to the DB.1 as DEFAULTS must specify a UID value of 0, unless the user has a COID value that give access to job that match DEFAULTS.
The DEFAULTJOB value in the CA 7 INIT File specifies a job on the database to be used for default values for all job adds. If a job is defined on the database with this name, the values for fields of this job are used as default values for the new job, with the exception of the MEMBER and UID fields. The default job name is DEFAULTS. For the Personal Scheduling exceptions, see the DEFAULTPS keyword.
Additional Information
Feedback
