Hold parameter in batch job
why should we give the hold paramater (*yes) in a batch job? please let me the what is a a batch job?
Software/Hardware used:
v5r3db2,rpgle
Software/Hardware used:
v5r3db2,rpgle
ASKED:
August 29, 2011 4:32 AM
UPDATED:
March 31, 2012 5:27 PM
Answer Wiki:
On SBMJOB command, By default HOLD keyword holds system default value '*JOBD'
<pre>Inquiry message reply . . . . . *JOBD *JOBD, *RQD, *DFT, *SYSRPYL
Hold on job queue . . . . . . . *JOBD *JOBD, *NO, *YES
Schedule date . . . . . . . . . *CURRENT Date, *CURRENT, *MONTHSTR...</pre>
The parameter '*YES' refers to keep the Job in Hold status after submitting to batch.
The parameter '*NO' will not keep the Job in Hold status as soon as it enters to batch, it will be in Active mode.
Pradeep.
To see all answers submitted to the Answer Wiki: View Answer History.
Regarding the question “what is a batch job”?
In the simplest form, if you are keying in information, that is call interactive.
It you want something to run at a later time and without human intervention, you submit that job to a job queue and have it run in BATCH.
Many shops run reports and big update jobs in batch. This keeps the interactive subsystem available to quickly respond when users press the “Enter” key.
The operating system applies processing efficiencies to batch jobs which is another benefit of submitting to batch when no operator interventions is needed.
As to why you would hold a job,
well, duringthe day users press a command key that submits a job as held into a job Q
at night, when they all go home, the system releases the jobs and does the work.
Holding a batch job is necessary when you want to debug an ILE program in batch. When doing that you need to STRSRVJOB on the held batch job. Then after STRDBG on your program, you release the job.
Holding a batch job is necessary when you want to debug an ILE program in batch.
This hasn’t been true for quite some time. Setting a service entry point can eliminate a need to put batch jobs on hold for debugging.
Tom