|
> >they do not want to READ the message, they do not > >want to READ Al's instructions, they just want the system to work without > >any further hassles > > and you have a problem with that? ;-) Al's boss has a problem with Al failure to solve some user problem. User's boss has a problem with Al giving instructions to user instead of solving problem. Al thinks they are all birds of a feather & needs to avoid further trouble with undiplomatic language. > Create a keyed file by program/field and write a help window that reads the > file and displays the help text. Add a function key that will check to see > if the user is authorized to update/add the help text. If they are > authorized they can write there own help text. (Train the > manager/supervisor and give them the ability to write THEIR help text for > THEIR people.) Thanks - this is a cool idea for my power users who help the folks who are incapable of remembering that Al said "The next time this happens, put the CURSOR on the message at the bottom of the screen & press F1 help for the whole story." Somewhere here someone suggested DSPMSGD & error message # except that we have several WRKMSGF in library list, so they have to know a bit more. I am now tempted to put DSPMSGD & WRKMSGF with the relevant parameters filled in, on one of the menus used by our power users ... menu options to read like Display Common IBM Messages e.g. Spool Control Display Common BPCS Scenarios e.g. Multi-User Record Lock Alister William Macintyre +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.