|
View previous topic :: View next topic
|
| Author |
Message |
shobam
New User
.jpg)
Joined: 18 Jul 2005
Posts: 34
Location: CN
|
|
|
|
Hi,
I am creating a job using skeleton and submitting the created job.
The JOB card is as follows
| Code: |
//MUTHAS1@ JOB (F-ZZZZZ-NUSP-ZZZ),
// 'ENDV',
// CLASS=P,
// MSGCLASS=X,NOTIFY=&SYSUID,
// USER=MUTHAS1
|
as you can see there is no HOLD option. Yet on submission of the job, it goes on HOLD and only on releasing the job its running.
Am I missing something here. Any idea towards this will help. Thanks. |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Find out from your own technical support what CLASS=P means at your site. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
since today is Monday and psychic day is in Wednesday,
since we do not belong to Your organization
just looking at the JOB statement nobody will be able to diagnose what is going on
| Quote: |
| Am I missing something here. |
just the good judgement of asking somebody inside Your organization |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Sounds like it's "test-job", is it? Then there can be many reasons behind for your job to be on hold - such as you've kept some file open in view/edit using ISPF 3.4, did you check that?
Was somehting flagged in JESMSGLG? |
|
| Back to top |
|
|
bipinpeter
Active User
.jpg)
Joined: 18 Jun 2007
Posts: 213
Location: Cochin/Kerala/India
|
|
|
|
| May be the input files for your job is migrated or already in use,. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
when a file/resource has had an exclusive issued
thus preventing other jobs accessing that file/resource
don't the jobs normally going into a WAIT and not a HOLD.
jobs go into HOLD from JES. i would think the class parm is your problem.
JOBS in HOLD, have not started executing.
as a result, there is no jesmsg to interrogate. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
Thanks dbz...  |
|
| Back to top |
|
|
David Robinson
Active User
Joined: 21 Dec 2011
Posts: 199
Location: UK
|
|
|
|
| This will happen if you run TWS and have the EWTROPTS parm set to HOLDJOB(YES) |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
The TS is using a skeleton, and then im thinking about ISPF services, and submitting the job. As far as i can see thats outside TWS.
HOLDJOB(YES) is the least preferred of the three options. Consider HOLDJOB(YES) only if you have Tivoli Workload Scheduler for z/OS-planned jobs that both:
1.Cannot be submitted by Tivoli Workload Scheduler for z/OS
2.Do not have TYPRUN=HOLD specified on their job cards. |
|
| Back to top |
|
|
David Robinson
Active User
Joined: 21 Dec 2011
Posts: 199
Location: UK
|
|
|
|
With HOLDJOB(YES), all jobs get submitted on hold, not just TWS ones.
TWS will then release those that are non-TWS jobs, but it's possible that if his job name matched one in the current plan, it would remain held. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
as usual the TS has disappeared
without more details from the TS everything is just speculation and waste of forum resources |
|
| Back to top |
|
|
|
|
