Re: User Spaces

[Joel Cochran <jrc@xxxxxxxxxx>]

Barbara,

I like the static variable idea, and I love service programs, but will
the service program be tied to the particular job? If I have 20 users on
the system at once I have to be assured that the static variables they
are accessing are unique to them.  That's why I thought that maybe a
User Space would work: load the user space once in QTEMP and essentially
you have static data specific to that user.

Basically this is set up in a DB structure with the following columns:

userid   function   option   optDesc   authorized
JRC         MYSCREEN    2             change     N
JRC         MYSCREEN    3             copy         Y
JRC         MYSCREEN    4             delete     N
JRC         MYSCREEN    5             display   Y
JRC         MYSCREEN    F6           create     Y

So for MYSCREEN (which could be any program or screen name), this user
can copy, display, or Create new records.  The larger the application
the more of these entries to sift through, so maybe sticking with a
straight DB access method is best but I want to at least explore the
option.  


> Whether it
> would be better would depend on how nice you made the interface to the
> user space - a based data structure would work, but it would be
> difficult to maintain if you added new authorities or screens or
> whatever.  I also vaguely wonder if the user space would be as secure
> as the file.

I was going to put all the security procedures into one service program,
so maybe the DS maintenance wouldn't be too bad, but I do want to avoid
changing the Service Program every time we had a feature.  What would
the security risk of the User Space be?  If I put it in QTEMP wouldn't I
need to be signed on as that job in order to read/change it?

Thanks,

Joel
http://www.rpgnext.com