RE: Why do software companies always want ALLOBJ

["Henrik Krebs" <hkrebs@xxxxxxxxx>]

Here is what I as an IT consultant need to work effectively. The same thing 
probably
apply to software companies I guess.

 o All-authority to objects in the application (Directly or via GRPPRF).
 o A good cooperation with a person at the 
   customer for (rather infrequent use of) *ALLOBJ and *SECADM - creating 
   userprofiles, fixing the "oops - Object changed owner when restored" (we
   all make mistakes sometime) etc.
 o An answer Yes/No to the question "Want a joblog for each job/session?"). 
   Personally I've only met 'No', even when the infrequent use of *ALLOBJ 
   was managed with the loan of QSECOFR.

The sentence "We refused to give them *ALLOBJ rights, period." or "after a 
specified
time, it cancels the dial in job," really sounds like a lack of 'good 
cooperation' and
more like "Do your bloody job and don't bother us". If I - in that situation - 
should do
the bloody job, I should also need *ALLOBJ!

Henrik
http://hkrebs.dk



- -----Original Message-----
From: Graziano, Marie [mailto:mgraziano@badgermeter.com]
Sent: Wednesday, September 13, 2000 8:37 AM
To: 'Midrange'
Subject: Why do software companies always want ALLOBJ


I am currently working with a software vendor that is asking for the userid
for the software to have ALLOBJ.  Now we all know that this is a very very
bad move.  However, in order to get the product up and running I had to do
it.  What are other companies doing?  And why do the software vendors not
understand what ALLOBJ is and does.  IF the user id was not used to sign in,
then I would not have a problem, but the software signs in with the userid
each day.

Marie Graziano

+---
| 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
+---