User v Concurrent Licences was (ADTS V6R1 - No SEU updates?)

Hi Joe,

I am not sure how this works.

For 'named user' licencing, when are the users named.
Is it at installation, or can I name and rename as needed,
how else can I handle the case of staff resignation.

Can I have 'User 1', 'User 2' etc. and have a pool
of shared PCs that the programers/contractors can log on with.
This however raises issues of tracking and tracing. (SOX)
But it can be manually controlled. Does this simulate
concurrent users.

With WDSC and RDi I can no longer go to 'any' PC and do
source maintenance. With Client Access the PC is just a
'terminal emulator' so I dont really need a PC to change code,
but I now longer have any terminals.
When we switched to TCP and threw out the twinax controllers
I predicted this would happen. (I think I can dig up something
in the archives.)

RDi/WDSC hac changed all that. Our PC team can no longer
deploy a 'common image' to all PCs. The developers now
need a special image, well for WDSC V6, thats the case, will
RDi V7.1 affect the 'common PC image' issue.

All our programmers are under a QPGMR group profile.
All our users are under a 'ERP USER' group profile.
All our programs are 'owned' by QPGMR in Development and
'ERP USER' in production.
Does this mean I only need 2 compiler licences.
We use MKS Implementer for source control and
deployment. I am not sure, but can we set up a single
compile licence 'QSECOFR' then adjust permissions and
ownerships as needed.

Or have I completely lost the plot and misunderstood the
gist of this topic.

Frank Kolmann
(Anyhow it wont be too long before all us old SEUers will
pop our clogs and Bill will take over the world, me, I'm
rooting for the Penguin.)

date: Thu, 14 Feb 2008 17:47:55 -0600
from: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] ADTS V6R1 - No SEU updates?
We're still not quite sure how the licensing works on the compilers.
As Jon Paris pointed out pretty damned eloquently, IBM is almost
daring people to use one user profile to compile all programs.

---text removed ---

I don't even disagree that it would be nice to have V6R1 support in WDSC,

I'm simply saying it's not the most important battle -
the definition of a user is probably the single most important issue
that will confront System i developers this decade, and
I don't think I'm being grandiose about it.

If I had to pick ONE battle, concurrent licensing is the one I'd pick,
with ADTS -> RDi entitlement being a very close second.