IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

What will happen if we put EXEC = N for a job in CA7?


IBM Mainframe Forums -> CA Products
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Padmaja Chennupati

New User


Joined: 26 Feb 2010
Posts: 1
Location: HYD

PostPosted: Fri Feb 26, 2010 12:27 pm
Reply with quote

Hi,

I faced one issue in which one job say JOBA is set as EXEC=N, Its triggered jobs got executed.

Let us say JOBA triggers JOB B and JOB C. I am in an assumption that if JOBA is turned off(EXEC=N), then JOB B and JOB C should not get triggered, which didn't happen in my issue. Even JOB A didn't get executed, JOB B and JOBC got executed.

Can anybody please explain what exactly happens when we put EXEC=N and how the jobs got triggered?
[/Search]
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Feb 26, 2010 12:39 pm
Reply with quote

The information that you request is readily available in the product documentation which should have been the very first place that you looked.

EXEC=N sets a job when scheduled to be deemed as processed without physically processing the job.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CA Products

 


Similar Topics
Topic Forum Replies
No new posts JCL EXEC PARM data in C Java & MQSeries 2
No new posts Issue with EXEC CICS QUERY SECURITY c... CICS 6
No new posts Determine Library REXX exec was execu... CLIST & REXX 7
No new posts parmeter existence bit for URIMAP in ... CICS 1
No new posts Execute Partially Edited Rexx Exec fr... CLIST & REXX 14
Search our Forums:

Back to Top