MVSFORUMS.com

Phaninder · Beginner Joined: 06 Jul 2005 Posts: 27 Topics: 11

Hi All,
I have a query please help me if possible, I have job which takes more than 60 mins of CPU time, This goes down with S322 after running for 3 hrs, Now if TIME=1440 is coded the job goes perfectly fine,
I wanted to know is there any diadvantage in doing it, I mean if i code it permanently.
If possible please let me know the advantages and disadvantages of coding the time parameter.

Bill Dennis · Posted: Wed Dec 07, 2005 9:26 am Post subject:

We like to enforce time limits for programmer development work, just in case a program starts looping. Most of our production work runs with 1440 (set by JES2 job class definitions).
_________________
Regards,
Bill Dennis

Disclaimer: My comments on this foorum are my own and do not represent the opinions or suggestions of any other person or business entity.

Mervyn · Posted: Wed Dec 07, 2005 9:54 am Post subject:

A job taking more than 60 minutes of CPU time is a very long job. Just be sure it's working correctly. Bill's philosophy is perfectly reasonable.
_________________
The day you stop learning the dinosaur becomes extinct

SureshKumar · Intermediate Joined: 23 Jan 2003 Posts: 211 Topics: 21

Phaninder,
You may also check the CLASS, which generally has pre-defined time limits in a production system.

Phaninder · Beginner Joined: 06 Jul 2005 Posts: 27 Topics: 11

Bill/Mervyn/suresh
Thanks a lot for your response, I would be pleaseg if give me some links regarding the descripition of time parameter.

Hi kolusu,
Please throw some light on this if possible.

kolusu · Posted: Thu Dec 08, 2005 10:18 am Post subject:

saro · Posted: Sat Dec 31, 2005 4:25 am Post subject:

Kolusu,

I have a couple of questions..?

My requirement is to submit a job daily at a particular time.

1)is it possible to submit a job at a particular time without using rexx execs..?

My trials..

//LASTSTP EXEC PGM=IKJEFT01,COND=(0,NE)
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=D
//SYSTSIN DD *
SUB 'AFW34R.TSO.JCL(AUTOTE)'

i try to put a job into a loop by adding the above mentioned step at end of job, and a rexx exec inbetween to valuate the time and perform what i needed.
This above step will submit the same job again and again.
The rexx inbetween will have a "submit" command to TRIGGER my actual job.

Is this a good logic..? if not .... "is there a way to avoid repeated looping by giving a WAIT or HOLD like options ". is there any in JCL..?

2.can the same be done thro REXX alone without involving JCL..?(offcourse the rexx has to submit or trigger my job).Here too i have a question.i'll post it if your reply doesn't help me. Smile

Thank you
_________________
Saro

Nothing is great unless God.

Ravi · Beginner Joined: 27 Jun 2005 Posts: 88 Topics: 2

saro, What exactly are you trying to achive. Explain why you want to do and then probably we have an oppurtinity to look from a different perspective, so the objective is acheived.

saro · Posted: Mon Jan 02, 2006 9:30 pm Post subject:

Ravi,
i'll put it simple.

I want to trigger (or submit) a job at a particular time(say 5 AM in the morning).
Is it possible to do with JCL or REXX..?(it should be)

let me know the possibilities.
_________________
Saro

Nothing is great unless God.

semigeezer · Posted: Mon Jan 02, 2006 10:38 pm Post subject:

This is what job schedulers are for. Do not use a batch job that just runs all day. That uses an initiator which is a scarce resource. Ask your systems people how to do this in your shop. They will either have a job scheduler installed, or they will have job classes that start at particular times of day.

Ravi · Beginner Joined: 27 Jun 2005 Posts: 88 Topics: 2

As semigeezer mentioned, you must use Job Schedulers for all prod jobs. But Wink

if the job you are submitting is for your own personal use, and don't want to involve mainframe scheduler, then try this approach http://www.mvsforums.com/helpboards/viewtopic.php?p=24200#24200

saro · Posted: Tue Jan 03, 2006 10:15 pm Post subject: