× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jerry -

On Thu, 26 Apr 2012 12:00:03 -0500, "Jerry C. Adams"
<midrange@xxxxxxxx> wrote:

I deal with a lot of old S/36 style menus and use UIM for new, native menus.
I was wondering if there was any way to display the name of the library, in
which the menu resides, on the menu? The reason I ask is because I create
test libraries every night from production. I have separate profiles for
production and test. Sometimes I forget which environment I'm in! Of
course, I can DSPLIBL or WRKUSRJOB. Thought there might be an easier way,
like a parameter on the menus that I missed or forgot about.

We use DSPF/MSGF-type menus. What I've done is displayed the text of
a specified msgid in a specified msgf.

1. Where the message file is specified to be in QTEMP and a setup
program creates the message file and creates the msgid with the
specific text.

2. Where the message file is found by the library list, so the message
file that actually gets found will determine the text which is
displayed. The message file and msgid are permanent.

Assuming that UIM menus can display text from a specified msgid, you
could do something like option 2, where you would have a message file
in every libary in which the menu resides.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.