Re: JES2 conversion delay

2013-06-05 Thread Baby Eklavya
Hello Robert , Changing the wait interval from 500 Milliseconds to 3 secs on Jobtrac might introduce a small delay on all other auto-sched jobs that goes through normal conversion phase which we dont want .Instead ,I would go with your first solution to flag the JCLLIB datasets as non-migrate

JES2 conversion delay

2013-06-04 Thread baby eklavya
Hello , We are running Z/OS 1.11 in our environment and recently had a problem with Auto-sched jobs in Jobtrac . There were a set of auto-sched jobs which comes to JES2 and jobtrac puts a HOLD on it by design (for Auto-sched processing) . Later ,Jobtrac issues a release command to free them for

Re: JES2 conversion delay

2013-06-04 Thread Doug Henry
How many convertor tasks are you running? You can find out by command $DPCE(CNVT). What is the jobdef option cnvt_enq set to ? You can find out by command $JOBDEF,CNVT_ENQ ? Doug On Tue, 4 Jun 2013 17:03:39 +0530, baby eklavya baby.ekla...@gmail.com wrote: It was found that JES2 conversion

Re: JES2 conversion delay

2013-06-04 Thread baby eklavya
@LISTSERV.UA.EDU Subject: JES2 conversion delay Hello , We are running Z/OS 1.11 in our environment and recently had a problem with Auto-sched jobs in Jobtrac . There were a set of auto-sched jobs which comes to JES2 and jobtrac puts a HOLD on it by design (for Auto-sched processing) . Later

Re: JES2 conversion delay

2013-06-04 Thread Doug Henry
I would wonder if you had 4 jobs that were using jcllib and were waiting on an HSM recall. Check out this Share presentation for a very good explanation of possible converter perfomance issues. ftp://ftp.software.ibm.com/s390/jes2/Share104/s2663lp1.pdf Doug On Tue, 4 Jun 2013 22:14:38 +0530,

Re: JES2 conversion delay

2013-06-04 Thread baby eklavya
AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: JES2 conversion delay Hello , We are running Z/OS 1.11 in our environment and recently had a problem with Auto-sched jobs in Jobtrac . There were a set of auto-sched jobs which comes to JES2 and jobtrac puts a HOLD on it by design (for Auto-sched

Re: JES2 conversion delay

2013-06-04 Thread Doug Henry
@LISTSERV.UA.EDU] On Behalf Of baby eklavya Sent: Tuesday, June 04, 2013 4:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: JES2 conversion delay Hello , We are running Z/OS 1.11 in our environment and recently had a problem with Auto-sched jobs in Jobtrac . There were a set of auto-sched jobs

Re: JES2 conversion delay

2013-06-04 Thread Baby Eklavya
We dont have any other datasets on the checkpoint volume . I would also plan to increase the no of converter tasks . Regards, Baby(Sachin) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: JES2 conversion delay

2013-06-04 Thread baby eklavya
Hello Doug , We had this problem 2 or 3 times in past few months . But each time , 4 jobs were affected (coincidence or not ) .Jobtrac by design issues the $AJ command after 500 Milliseconds once it puts the HOLD . In that case , the JCL conversion should have crossed more than 500 Milliseconds

Re: JES2 conversion delay

2013-06-04 Thread Robert A. Rosenberg
At 03:46 +0530 on 06/05/2013, baby eklavya wrote about Re: JES2 conversion delay: Hello Doug , We had this problem 2 or 3 times in past few months . But each time , 4 jobs were affected (coincidence or not ) .Jobtrac by design issues the $AJ command after 500 Milliseconds once it puts