Antwort: 00C9008E (timeout!) on 304(TS RID)

[login to unmask email]

Antwort: 00C9008E (timeout!) on 304(TS RID)
maybe the mainprogram calls an assembler subroutine, which generates two
threads?



Venkat (PCA) Pillay

Re: 00C9008E (timeout!) on 304(TS RID)
(in response to duerr_jacobsg@WESTLB.DE)
1. It is row level locking.
2. (Timing out with itself !!!), I have seen this earlier. We migrated from
V3 to V4 and this problem started appearing. If you see the lock detailes
thru traces then you will find that this just REPORTING BUG. The real agent
involved was something else.

Confirm this with traces - STATISTICAL CLASS(3) or PERFORMANCE CLASS(6) ,
IFCID is 196. This will give you exact detail of the VICTIM agent and LOCK
HOLDING agent.

I don't remember the PTF but you could check it in IBMLINK.

HTH
Pillay

> -----Original Message-----
> From: [login to unmask email] [SMTP:[login to unmask email]
> Sent: Tuesday, October 12, 1999 4:27 AM
> To: [login to unmask email]
> Subject: 00C9008E (timeout!) on 304(TS RID)
>
> A single batch is often involved in timeout on a Ts rid
> ,it seems with itself generating two thread........ lock escalation ?
> It's a cobol II ,not PLI !.
>
> any suggestion will be a nice gift !!.
>
>
> DSNT376I +DS1P PLAN=GSPL0001 WITH
> CORRELATION-ID=GGS00120
> CONNECTION-ID=BATCH
> LUW-ID=DB2P.LUDB2PR.B2FB63B87B86=12795
> THREAD-INFO=PROD:*:*:*
> IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN=GSPL0001
> WITH
> CORRELATION-ID=GGS00120
> CONNECTION-ID=BATCH
> LUW-ID=DB2P.LUDB2PR.B2FB63B87B86=12783
> THREAD-INFO=PROD:*:*:*
> ON MEMBER DS1P
>
> DSNT501I +DS1P DSNILMCL RESOURCE UNAVAILABLE
> CORRELATION-ID=GGS00120
> CONNECTION-ID=BATCH
> LUW-ID=*
> REASON 00C9008E
> TYPE 00000304
> NAME DBxxxxxx.TSAAAAAA.X'905D41' '.X'08' .
>
>
>
>
>