Well. That's an interesting API set. My current procedure is to create a file for each program that has to store defaults, then I have to make sure I clean this up periodically, and I have to explain to auditors why my profile is updating files on the production system every time I run one of these programs that stores my inquiry defaults. Attaching the defaults to the profile in a system level storage area eliminates all these annoyances. It doesn't look like there is a nice way to list current stored data though, so, as applications are discontinued, I suppose the profile storage area could become more bloated, but, perhaps that's not a concern in our large storage era.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joep Beckeringh via MIDRANGE-L
Sent: Tuesday, March 23, 2021 7:16 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Joep Beckeringh <joep.beckeringh@xxxxxxxxxx>
Subject: Re: Application Specific User Settings: How to?
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hello Patrik,
You can store user settings in the user profile with API QsyUpdateUserApplicationInfo and retrieve them with QsyRetrieveUserApplicationInfo.
If you'd like to, I can supply prototypes and code that I use myself.
Joep Beckeringh
Op 23-3-2021 om 11:48 schreef Patrik Schindler:
Hello,
sometimes, it's desirable that users on an IBM i system can modify and persistently save individual settings of applications. Example: A default sorting order for some table view. But not necessarily limited to that.
Not every user necessarily has a personal library to create a PF for saving things there. And, this approach unnecessarily clutters libraries.
Not every user necessarily has a home folder to create a file for saving things there.
What's more, depending on how a user accesses the data, these approaches might lack authority to access or update the files. AFAIK, the web server runs with a separate user profile. This is less of an issue with "local" (5250) users.
A central, application specific file would accumulate old entries (when user profiles are deleted from the system, for example).
What is the best way to save local user preferences (mainly for 5250 users of applications)? Any thoughts from the group on this topic?
Thanks!
:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
