View previous topic :: View next topic
|
Author |
Message |
jaimf
New User
Joined: 07 Dec 2009 Posts: 5 Location: Bangalore
|
|
|
|
Hi,
I have used the below time parameter override in jcl but not working fine,
start of jcl........
//XXXATPRD JOB (T00101,000),NOTIFY=&SYSUID
//XXXBT1 EXEC XXXCT1,
//*
// OCYCLE=J9L901
//***
//TIME.ACTDT100=0
//TIME.ACTDT110=1440
END of jcl...
I have tried to override the time parameter in the catalog procedure step XXXDT100 and XXXDT110
Please suggest me to override time parameter.
Thanks
Jai |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
What did you find when you looked in the manual (link at the top of the page)?
Also, when you say it didn't work, do you mean:
1) the job ran to normal completion but didn't produce the results you expected?
2) the job ran but gave a user abend (Uxxxx) code?
3) the job ran but gave a system abend (Sxxx) code?
4) the job failed converter / interpreter and never started at all?
These are all legitimate, valid, and possible interpretations of "didn't work". If you cannot be precise in your terminology, which is so central and important to IT, you really should reconsider your career choice. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
I have used the below time parameter override in jcl but not working fine.
.
.
//TIME.ACTDT110=1440 |
In addition to Robert's observations, you should never specify TIME=1440 for any of your jobs. |
|
Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008 Posts: 1249 Location: Richfield, MN, USA
|
|
|
|
Attempts to override TIME parameters can be overridden by the people who support z/OS (MVS) at your site. Have you checked with them to make sure what you want to do is allowed (acceptable)? Many shops frown on overriding TIME values. |
|
Back to top |
|
|
|