RE: DSPJRN very, very slow

["Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>]

55,275,140K with 214,563,314 is huge.  Change to system managed and have
a couple a day created.  Another factor is where the journal receivers
are located.  Are they on their own ASP?  If so, do you have enough arms
for the traffic?

Chris Bipes 
Director of Information Services 
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles
Sent: Wednesday, August 15, 2007 8:15 AM
To: Midrange Systems Technical Discussion
Subject: RE: DSPJRN very, very slow

receiver:
Size (K) . . . . . . . :   55275140
Status  . . . . . . . . . . . . . . . . . . . . . . :   ATTACHED 
Number of entries . . . . . . . . . . . . . . . . . :   214563314 
Attach date  . . . . . :   03/20/07      Attach time  . . . . . :
10:35:45

This is on a QA system, so it's not surprising that the receiver has
been attached for a while.
I'll see if I can get operations to attached a new receiver.


But even on production, DSPJRN is slower than what I'm used too.  That
receiver gets changed every
day.

Thanks,
Charles