|
We have a file/program based menuing system. When the user signs on they have that menu. Each menu option / particular application / has an "initial program". It is the responsibility of the initial program to handle things like library lists. Nothing submits a job depending on the job description associated with the user profile. It uses job descriptions associated with the particular application. Common techniques for initial programs include: - Using RTVJOBA to find out things like what is their current library list, etc. Store these into variables. - CHGJOB, etc to customize it for the application - Get into the meat of the application. - CHGJOB back to the stored values - return to the menu. We have a couple of canned software packages in use and it's working fine. No end user setup of initial program is required. We've added some obscure menu options to do things like "clone all menu options from one user to another", stuff like that. User id is part of the key to the menu file options. Sample I have several menu options (in addition to the menu maintenance options). I am able to get into BPCS for several divisions (each of which have their own library list, etc). I am also able to get into accounting for several divisions (each of which also have their own library list, etc). (The accounting vendor changes their name a lot - this week I think it is called Unicorn.) Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.