Xpediter/DB2

Kathy Czepiel

Xpediter/DB2
Does anyone have any opinions, pro or con, as to letting the programming
staff use Xpediter/DB2 in a production environment? We have had someone
ask for it, and as we have had unpleasant experiences with Xpediter/CICS
clobbering a CICS region when misused, I am hesitant to allow access with
Xpediter/DB2.

Kathy Czepiel



Kathleen S. Jones

Re: Xpediter/DB2
(in response to Kathy Czepiel)
We allow it only on a case by case basis - the programs are not compiled
allowing it until they can't resolve a production problem in other way -
then the programmers ask the sr database analyst (she is responsible for
moving db2 programs to production) to compile with expeditor so they can
use. This was in place when I started here and it seems to work okay.



Gary Fahrlander

Re: Xpediter/DB2
(in response to Kathleen S. Jones)
All I can say is "DON'T DO IT... YOU'LL BE SORRY!!!" There should be no
reason the data can't be copied down the test environment and Expediter run
there.

Gary

Tell Ted Flowers I said hi!

"For every problem there is always a solution that is simple, obvious,
and wrong."





Kathy Czepiel
<[login to unmask email] To: [login to unmask email]
ERYBIZ.COM> cc:
Sent by: DB2 Data Subject: Xpediter/DB2
Base Discussion List
<[login to unmask email]
OC.COM>


12/18/2002 03:35 PM
Please respond to DB2
Data Base Discussion
List






Does anyone have any opinions, pro or con, as to letting the programming
staff use Xpediter/DB2 in a production environment? We have had someone
ask for it, and as we have had unpleasant experiences with Xpediter/CICS
clobbering a CICS region when misused, I am hesitant to allow access with
Xpediter/DB2.

Kathy Czepiel



the DB2-L webpage at http://listserv.ylassoc.com. The owners of the list
can



Cindy Andersen

Re: Xpediter/DB2
(in response to Gary Fahrlander)
One situation we have had with Xpediter (in a development environment) is a
user leaving their PC in the middle of a session and going home for the day.
Since this is a conversational mode product, the DB2 thread stays out there
until someone cancels the thread or the TSO Xpediter session is closed. We
had a contractor that did this a few times and caused some of our nightly
jobs to fail, plus binds, because of the exclusive locks still held on the
application DB2 tables. See interoffice emails below for one example.
-----------------------------------------------
Sent: Tuesday, July 16, 2002 9:30 AM
Subject: RE: Another Hung Thread

I talked with xxxx on this. It was like we assumed. He had
it in Xpediter stepping through and stopped at the insert and left the
screen up without closing it out like he should have. So the locks were not
released on the tables...........

-----Original Message-----
Sent: Monday, July 15, 2002 6:37 PM
Subject: Another Hung Thread

I was doing some bind plans tonight and my XX plans
were hanging on DBD1 and eventually got a lockout error.
I checked the locks on XX tablespaces and once again
there were IX, IS, and other locks on several XX objects.
I went into xxxxx and found that the CICS thread for
xxxx had been hung for over two hours (16:22 - 18:27). It was the xxxx
package again doing an INSERT into the xxxxxxxx table which is one of the
xxxxx xxxxx Alert tables. Since I knew this would cause a page on the DBD1
Archive Log job Tuesday morning, I canceled the thread.

I'll talk to you Tuesday. Just trying to prevent a
page.
====
> -----Original Message-----
> From: Kathy Czepiel [SMTP:[login to unmask email]
> Sent: Wednesday, December 18, 2002 3:36 PM
> To: [login to unmask email]
> Subject: Xpediter/DB2
>
> Does anyone have any opinions, pro or con, as to letting the programming
> staff use Xpediter/DB2 in a production environment? We have had someone
> ask for it, and as we have had unpleasant experiences with Xpediter/CICS
> clobbering a CICS region when misused, I am hesitant to allow access with
> Xpediter/DB2.
>
> Kathy Czepiel
>
>