RE: Change Management Software -- MIDRANGE-L

Ron,

I'd have to agree with David, and I can sympathize with you, but any job can
be a resource hog if not properly administered.  You may want to check into
the Turnover setup as well as your system setup, e.g. subsystems, job
queues, job descriptions, priorities, etc.   As for Wisedesk, I haven't had
the pleasure yet....

Regards,
Jon A. Erickson
Sr. Programmer Analyst
800.COM Inc.
1516 NW Thurman St
Portland, OR  97209-2517

Direct: 503.944.3613
Fax: 503.944.3690
Web: http://800.com


-----Original Message-----
From: Shaw, David [mailto:dshaw@spartan.com]
Sent: Friday, February 25, 2000 8:29 AM
To: 'MIDRANGE-L@MIDRANGE.COM'
Subject: RE: Change Management Software


Ron,

If your promotions are taking that much, it's likely because TurnOver is set
up
to compile the objects into production.  That's a choice your TurnOver
administrator controls - there are several alternatives, including just
moving
the tested objects from test into production.  Whoever your administrator is
should know this, it's in the training material.  Perhaps you've had some
personnel changes and you don't currently have a trained administrator?
That
could have a bearing on why your perception of support is poor - it's
difficult
to train someone in using the product over the phone, a little bit at a
time.

TurnOver CAN be a resource hog, depending both on how it is set up and how
your
work management is set up on your machine, but it doesn't have to be.  Even
if
it's set up inappropriately, it usually doesn't take much more resource than
the
same process done manually would - the TurnOver software itself is pretty
efficient, oddities in WiseDesk notwithstanding.

I don't have any association with Softlanding Systems, but I was a TurnOver
administrator for about a year and a half in a previous position.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

> -----Original Message-----
> From: Ron Hawkins [mailto:RON@CPUMMS.COM]
> 
> Well, everytime I get a question about response, I do a work 
> active job. Guess what tops the list of cpu percentage? And 
> if I have two programmers promoting source at the same time, 
> each gets around 20% of cpu. That's 40% for two, 60% for 
> three... You get the idea (we have over 30 programmers.) When 
> I have my programming manager call for support on the issue, 
> he gets nowhere. They finally helped some (after three weeks) 
> on a wise desk resource problem that was taking over 80% of 
> cpu any time a user filtered their call list. I would 
> definitely call this a resource pig.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---