Author Topic: Inaccurate Time() parameter in Msg Num 87?  (Read 2693 times)

frasert

  • Guest
Inaccurate Time() parameter in Msg Num 87?
« on: July 10, 2011, 07:11:38 PM »
Version 8.4.1.0 on AIX -

The Time() parameter for our Msg #87's does not make sense to me.  This is one of the system log query messages:

Application Group Load: Name(xxxxx) LoadId(57713-7-0-132361FAA-15164-15164) File(/mvsdnld1d/PRDA.DISPPRDA.DISPPRDA.xxxxx.2011189.23540352364.ARD) InputSize(1893) OutputSize(315) Rows(1) Time(67.0260) Appl(xxxxx)

So Time() is equal to 67 secs for this query message.

But when you retrieve this system log message, the total time (indexing + load) is only equal to 4 secs (23:59:34 - 23:59:30):

arsload: Processing file >/mvsdnld1d/PRDA.DISPPRDA.DISPPRDA.xxxxx.2011189.23540352364.ARD<

arsload: 07/08/11 23:59:30 -- Indexing started, 1893 bytes to process
0425-415 CC=YES
0425-415 CCTYPE=M
0425-415 CONVERT=NO
0425-415 CPGID=500
0425-415 MCF2REF=CPCS
0425-415 TRC=NO
0425-415 FILEFORMAT=RECORD
0425-415 TRIGGER1=*,124,X'D7C1C7C540404040F1',(TYPE=GROUP)
0425-415 FIELD1=2,14,10,(TRIGGER=1,BASE=0)
0425-415 FIELD2=0,10,3,(TRIGGER=1,BASE=0)
0425-415 FIELD3=2,69,4,(TRIGGER=1,BASE=0)
0425-415 INDEX1=X'998481A385',FIELD1,(TYPE=GROUP,BREAK=YES)
0425-415 INDEX2=X'828195929596',FIELD2,(TYPE=GROUP,BREAK=YES)
0425-415 INDEX3=X'8595A399A8',FIELD3,(TYPE=GROUP,BREAK=YES)
0425-415 DCFPAGENAMES=NO
0425-415 UNIQUEBNGS=YES
0425-415 IMAGEOUT=ASIS
0425-415 INDEXOBJ=ALL
0425-415 INDEXSTARTBY=2
0425-415 INSERTIMM=NO
0425-415 RESTYPE=NONE
0425-415 inputdd=/mvsdnld1d/PRDA.DISPPRDA.DISPPRDA.xxxxx.2011189.23540352364.ARD
0425-415 outputdd=/dev/null
0425-415 indexdd=/indextmp/PRDA.DISPPRDA.DISPPRDA.xxxxx.2011189.23540352364.ARD.ind
0425-415 resobjdd=/dev/null
0425-440 ACIF AT PK72203 HAS COMPLETED NORMALLY WITH RETURN CODE 0.
arsload: 07/08/11 23:59:30 Indexing completed
arsload: 07/08/11 23:59:30 -- Loading started, 1893 bytes to process
OnDemand Load Id = >57713-7-0-132361FAA-15164-15164<
Loaded 1 rows into the database
Document compression type used - OD77.  Bytes Stored = >315< Rows = >1<
arsload: 07/08/11 23:59:34 Loading completed
arsload: Processing successful for file >/mvsdnld1d/PRDA.DISPPRDA.DISPPRDA.xxxxx.2011189.23540352364.ARD<



Am I missing something??


Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2230
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Inaccurate Time() parameter in Msg Num 87?
« Reply #1 on: July 11, 2011, 07:57:00 AM »
There doesn't appear to be any mention of this being fixed in any of the patches to 8.4.1.0, and there's no mention of the issue being fixed up to 8.5.0.2 -- so it's likely a bug. 
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

frasert

  • Guest
Re: Inaccurate Time() parameter in Msg Num 87?
« Reply #2 on: July 12, 2011, 06:24:17 AM »
Thanks Justin.  I've opened a PMR about this ... I'll provide an update once I get one.