RE: LODRUN

[Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>]

I prefer the vender to offer a choice.  When you order the software, specify
whether you want QSECOFR or Vender specific profile to own the application.
I prefer the Vender specific profile myself.  The vender should specify what
authorities are required in the Vender specific profile and that the
installer must first create the profile, then logon using that profile to
perform the install.  Once installed, the profile should be giving the
password of *NONE and initial menu of *SIGNOFF.

If the purchaser says to use QSECOFR because they do not want to create the
prerequisite profiles, then the LODRUN should create the profiles using the
QSECOFR profile then switch to the prerequisite profile to install the rest
of the software.

Of course if you need full access to the system for some utility that adds
exit points and create profiles, well the buyer should be well informed.

Just my preference,

Chris Bipes

-----Original Message-----
From: Vern Hamberg

There are things in many products, including some of ours, that require 
full access to a system. Various system utilities fall into this area. The 
API used by our CD-ROM product got more restrictive in V5R1, e.g. Install 
programs may need *IOCONFIG, etc. Now most of our stuff IS owned by QSECOFR 
but does NOT adopt that authority, unless it's needed.

And there is always the ability to swap profiles, of course.

What would you need from a vendor in this situation? Is a section in the 
documentation sufficient? We certainly don't have anything to hide and do 
not want to cause any concerns to anyone. What helps a trustful (made up 
word) relationship with a vendor?

Anyone can reply to this - I'm interested in various points of view.