Re: Using /home for application directories

It's picking nits but here is an example:


*-- Find subdirectories in /home where the user is gone.*
select AUTHORIZATION_NAME from qsys2.user_info
;
select *substr*(i.path_name, *LOCATE*('/', I.PATH_NAME, *2*) + *1*) as
user_id,
I.*
FROM TABLE (QSYS2.IFS_OBJECT_STATISTICS(START_PATH_NAME *=>* '/home',
OBJECT_TYPE_LIST *=>* '*ALLDIR',
SUBTREE_DIRECTORIES *=>* 'NO')) I
where path_name <> '/home'
and *upper*(*substr*(i.path_name, *LOCATE*('/', I.PATH_NAME, *2*) + *1*))
not in(select authorization_name from qsys2.user_info)
;

On Wed, Feb 19, 2025 at 8:22 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello,

Am 19.02.2025 um 02:05 schrieb smith5646midrange@xxxxxxxxx:

My client has been creating directories in the /home directory for

applications such as /home/finance. This seems wrong to me.

Expanding on the other replies: It's simply a matter of taste. There's
nothing wrong with this approach as long as it's used in a consistent
matter.

If it helps a bit… for me, a library in QSYS.LIB is a likewise grouping
facility. I see a library as a "project", where everything regarding this
project (source, data, applications) are tucked into one spot.

: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.