|
View previous topic :: View next topic
|
| Author |
Message |
NehaPathak
New User
Joined: 02 Aug 2007
Posts: 5
Location: Pune
|
|
|
|
Hi all
can any body tell me the use of
//*MAIN DEADLINE=
command and Its parameters.
thanks in advance. |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
The //*MAIN statement is used to define the processor requirements for the current job. This is a JES3 command. |
|
| Back to top |
|
|
NehaPathak
New User
Joined: 02 Aug 2007
Posts: 5
Location: Pune
|
|
|
|
@dick scherrer
Can you please elaborate more?
I mean how to use this command, what values we specify in this command.Mainly like if we want to execute a jcl on a partivular time in a particular date. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Hi,
QW gives this:
The //*MAIN statement is used to define the JES3 processor requirements for your job. JES3 abends your job and writes warning messages to the the JESMSG data set if an error is found in the //*MAIN statement. The //*MAIN statement consists of the characters //*MAIN in columns 1 through 7, a blank in column 8, and the necessary parameters anywhere in columns 9 through 72. You should insert the //*MAIN statement for your job after the JCl JOB statement and before the first EXEC statement in the job.
DEADLINE=(time,type{,date}) | (time,type{,rel,cycle})
This parameter tell JES3 when the job is required, by supplying a time and date before which the job must be scheduled. 'time' is the time of day by which the job must initiate, and Specifies the deadline time.
Hope this helps. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If you want a job to run at a particular time, your better choice is to use the scheduling system already in use. Most systems want scheduling centrally controlled and managed rather than just everyone "scheduling their own" and possibly interferring with the operation of the center. |
|
| Back to top |
|
|
NehaPathak
New User
Joined: 02 Aug 2007
Posts: 5
Location: Pune
|
|
|
|
I also got some points on this topic so sharing that. 
Deadline Scheduling
JES3 seems to have this as a scheduling facility. Sometimes, jobs are on hold for a long time, due to not being able to assign priorities. Deadline parameter is used to tell the system to execute this job by the time you need.
//*MAIN DEADLINE=(0700,B,020906)
to execute the job on 7'o clock morning 2nd sep 2006.
Deadline scheduling is a facility that allows users to schedule a job to
execute at (or by) a certain time (wall clock time or number of minutes or
hours relative to job submission time) on a specific date or periodically at
a given time every week, month, or year.
The installation defines up to 36 deadline-scheduling algorithms (A-Z and
0-9) and communicates the behavior of these algorithms to its users.
Deadline-scheduling algorithms specify such things as the initial priority
change, the lead-time for the job (i.e., the amount of time prior to the
specified deadline that the initial priority change will be made), and
parameters such as priority increment and frequency of incrementation.
The user’s JCL specifies the deadline time and date (or cycle relative to
week, month or year) and indicates which deadline-scheduling algorithm is to be used. |
|
| Back to top |
|
|
|
|
