Thierry,

Here I try giving you answer with my test example...

1) I ran a test job (as below)



                      J E S 2  J O B  L O G  --  S Y S T E M  1 X 0 1  --  
N O D
                                                                            
    
05.25.48 JOB00596 ---- THURSDAY,  17 JUN 2010 ----
                              
05.25.48 JOB00596  IRR010I  USERID NBKEODV  IS ASSIGNED TO THIS 
JOB.            
05.25.48 JOB00596  ICH70001I NBKEODV  LAST ACCESS AT 04:01:17 ON THURSDAY, 
JUNE 
05.25.48 JOB00596  $HASP373 NBKEODVA STARTED - WLM INIT  - SRVCLASS 
WLMDEVMD - S
05.25.48 JOB00596  NBUSI05I - REGION SET:  6,144KB BELOW;     32MB ABOVE; 
MEMLIM
05.25.48 JOB00596  IEF403I NBKEODVA - STARTED - 
TIME=05.25.48                   
05.25.52 JOB00596  *IEFACTRT* J=NBKEODVA,S=
(001,        .DUMPSTP ),RCODE=0000   
05.25.52 JOB00596  IEF196I *IEFACTRT* J=NBKEODVA,S=
(001,        .DUMPSTP ),RCODE
05.25.52 JOB00596  IEF404I NBKEODVA - ENDED - 
TIME=05.25.52                     
05.25.52 JOB00596  $HASP395 NBKEODVA 
ENDED                                      
------ JES2 JOB STATISTICS ------
                                               
  17 JUN 2010 JOB EXECUTION DATE         


Job came in input queue(conversion/reader time) at 05:25:28 & started 
executing at 05:25:52 (executiong queue) 

now since I had above example as my good friend SMF ..processed it with 
SAS/MXG and found 05:25:48 is a Job initiation time.

I selected TYPE30_1 which is for job initiation time and it surely had 
05:25:48 ..

this is a description for the JINITTIME

JINTTIME  NUM    8 DATETIME21.2 JOB*INITIATE*TIME                       
  Job initiate time stamp.  There can be multiple initiations of a job, 
  and this may be the first, last, or an in-between initiation event.   

What I also found the gap between the Job initiation time and the Readtime 
is shown in the variable RDRTM(Reader time) which is a gap between the 
Initiation and real execution...

Here's the output I had :

 OBS    SYSTEM        ZDATE                 JINTTIME      JOB              
RDRTM                 READTIME

  1      1X01     17JUN2010    17JUN2010:05:25:48.82    NBKEODVA      
0:00:01.94    17JUN2010:05:25:46.84

Now back to the solution :-

If you see substantial gap between the values of job initiation and 
execution..Bet look at the $D PERFDATA which has various parameter it can 
tell you where we are having delay..certainly IBM can also help you in 
tuning your JES configuration...MAS configuration has good impact on 
performance if not good tuning.

----------------------------------------------------------------------
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

Reply via email to