Hello Kevin:
About this...
"I would expect to see the job number closer together were they both
submitted at the same time. These jobs are more than 20000+ JOE apart. Are
they from different systems via NJE ?"
Yes, these jobs was submitted in different days.
I will try to explain the test in more detail:
Date: 1th March
1) To send some jobs (about 10 jobs)
2) To hold the jobs by hand
3) To free the jobs by hand
4) Quickly, to ask for job info
Date: 21th March
1) To send some jobs (about 10 jobs)
2) To hold the jobs by hand
3) To free the jobs by hand
4) Quickly, to ask for job info
At 1st test (1th March) we have obtained wrong time in queue (>23h!!) due to
these jobs were free (by hand) in few minutes from hold status. Therefore,
the correct time in queue should be few minutes. For example, we have post
the statistics of JOB01138
Then, at 2nd test (21th March) we have repeated the test following the same
steps. At this time, we have obtained correct time in queue (<2min). For
example, we have post the statistics of JOB24485.
So, with same test, we have obtained different results.
We think that it's no policy goal problem but it's a problem with SDSF job
information report.
We opened a PMR and following lab. steps we have try to reproduce it. Then
we have obtained 21th March report. We suspect some new PTF applied but we
haven't found anything.
You can try to test it:
1) To send some jobs (about 10 jobs)
2) To hold the jobs by hand
3) To free the jobs by hand
4) Quickly, to ask for job info
Jobs used:
/T751622E JOB CLASS=S,MSGCLASS=V,NOTIFY=&SYSUID
//P010 EXEC PGM=IKJEFT01,PARM='%LOOPSHRT'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSEXEC DD DISP=SHR,DSN=libname
//T751622E JOB CLASS=S,MSGCLASS=V,NOTIFY=&SYSUID
//P010 EXEC PGM=IKJEFT01,PARM='%LOOPSHRT'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSEXEC DD DISP=SHR,DSN=libname
//T751622E JOB CLASS=S,MSGCLASS=V,NOTIFY=&SYSUID
//P010 EXEC PGM=IKJEFT01,PARM='%LOOPSHRT'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSEXEC DD DISP=SHR,DSN=libname
...
--> libname(LOOPSHRT) <--
/* REXX */
/* "ALLOC DA('libname(LOOP1)') SHR F(I001)" */
/*DO I=1 TO 50000
TEXT.I=SUBSTR('A',1,4000,'Z')
END*/
DO I=1 TO 500
TEXT.I=SUBSTR('A',1,4000,'Z')
END
A=1
B=2
T=0
DO 15000000
/* T=T+1 */
C=A
A=B
B=C /*
IF T=500 THEN DO
T=0
"EXECIO 1 DISKR I001 1 (STEM A."
END */
END
...
--> libname(LOOP1) <--
/* REXX */
/* "ALLOC DA('libname(LOOP1)') SHR F(I001)" */
/*DO I=1 TO 50000
TEXT.I=SUBSTR('A',1,4000,'Z')
END*/
A=1
B=2
T=0
DO WHILE 1=1
/* T=T+1 */
C=A
A=B
B=C /*
IF T=500 THEN DO
T=0
"EXECIO 1 DISKR I001 1 (STEM A."
END */
END
On 3/22/06, Clark, Kevin D, HRC-Alexandria/EDS <
[EMAIL PROTECTED]> wrote:
>
> With that being the case.
>
> Now is the policy goal high enough to cause WLM to start another INIT. On
> the report there is always 1 job active.
>
> Go for 00:00:30 goal at 90%
>
> -----Original Message-----
> From: Clark, Kevin D, HRC-Alexandria/EDS
> Sent: Wednesday, March 22, 2006 2:06 PM
> To: 'Christian Blesa'
> Subject: RE: Job info: Wrong time in queue
>
>
> Christian,
>
> I would expect to see the job number closer together were they both
> submitted at the same time.
> These jobs are more than 20000+ JOE apart. Are they from different systems
> via NJE ?
>
> -----Original Message-----
> From: Christian Blesa [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 22, 2006 1:52 PM
> To: [email protected]; Kevin Clark
> Subject: Re: Job info: Wrong time in queue
>
>
> Yes, of course, these are 2 diff. jobs but both has been waiting for a
> init
> for 2min!! Therefore time in queue of 1138 was incorrect.
>
> Anyone could test it?
>
>
> On Wed, 22 Mar 2006 12:04:49 -0500, Clark, Kevin D, HRC-Alexandria/EDS
> <[EMAIL PROTECTED]> wrote:
>
> >What is the problem ?. These are two different jobs (1138 & 4485).
> >
> >1138 has been waiting for a initiator for 23 1/2 hours, is that the
> >issue ?
> >
> >Kevin
> >
> >-----Original Message-----
> >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
> >Behalf Of Christian Blesa
> >Sent: Wednesday, March 22, 2006 11:34 AM
> >To: [email protected]
> >Subject: Job info: Wrong time in queue
> >
> >
> >Hello
> >
> >We have had a "ghost" and we're finding it...
> >
> >
> >We're migrating from JES2 inits to WLM inits and in our test
> >environment we have done following test:
> >
> >1) To send some jobs
> >2) To hold the jobs by hand
> >3) To free the jobs by hand.
> >4) To ask for job info.
> >
> >1th March - Report
> >
> > Job Information
> > Job name T751622E Job class limit exceeded? NO
> > Job ID JOB01138 Duplicate job name wait? NO
> > Job schedulable? YES Time in queue 23:32:29 !!!!!!!
> > Job class mode WLM Average time in queue 00:00:00
> > Job class held? NO Position in queue 3 of 9
> > Active jobs in queue 1
> >
> >
> >21th March - Report
> >
> > Job Information
> > Job name T751622E Job class limit exceeded? NO
> > Job ID JOB24485 Duplicate job name wait? NO
> > Job schedulable? YES Time in queue 00:00:59
> > Job class mode WLM Average time in queue 00:00:01
> > Job class held? NO Position in queue 3 of 7
> > Active jobs in queue 1
> >
> >
> >
> >We have revised last sysres but we haven't found any PTF about it.
> >
> >
> >Could you test it? It's very easy!
> >
> >
> >Thanks
> >
> >----------------------------------------------------------------------
> >For IBM-MAIN subscribe / signoff / archive access instructions, send
> >email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
> >Search the archives at http://bama.ua.edu/archives/ibm-main.html
> >
> >----------------------------------------------------------------------
> >For IBM-MAIN subscribe / signoff / archive access instructions, send
> >email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
> >Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
