Dave Snyder wrote:

> We have multiple data libraries that we need our users to access that we 
>usually define the user profile to start a tran that gets them directly to the 
>proper library and menu. Do we need to define a user profile on the AS400 for 
>each person to access each separate library via the library list?

Basic AS/400 101:  There are at "least" three/four different ways to do 
                   what you want. This drives newbies to 400 up the

You need to read up on:

1. Library Lists (All users have access to any library in list)
2. Job Descriptions (Any person using this JOBD will use these
3. Menus (Controls which job uses which library through CL cmds)
4. CL commands that work with library lists (Works with option 3)
5. Group Profiles

Everybody on this list will give you a "slightly" different way to do
it, so you need to understand how each method works before you decide
what is right for your shop. Security is also part of the puzzle and
will have to be part of the answer.

> I am coming from a VSE (mainframe) environment where we have a product which 
>allows us to switch from environment to environment as we need to. Anything 
>like it on the AS400 environment?

There are similar products on the 400 or you can roll your own.....

Library List control is one of the early steps on setting up the
400. You can make it as simple or complex as you wish.

After a year or so on the 400, you will wonder why MVS ever existed...
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].