Re: Library hard-coded in menu objects

Dave Pate wrote on 07/25/2005 12:38:18 PM:

> I was surprised to learn that you cannot copy the 3 menu objects that
make
> up a menu from one library to another and get the same results that you
> would get if you compiled the source in the destination library.  You can
> copy COBOL or CL members and that works fine but when you copy menu
objects
> at least one of the menu objects is still pointing to the original
library
> to find the other menu objects.
>  (the original objects are used in the original library even though that
> library is not on the user's library list !)
>
>
> Why would a machine level object have a hard-coded reference to a library
> instead of the using the library list to find the object ?

You do not say the type of menu, but if it was created with the CRTMNU
command then whoever created the menu may have specified a library name on
the DSPF, MSGF, or PGM parameters. These parameters default to *LIBL. It is
probably more likely that the Current Library (CURLIB) or Product Library
(PRDLIB) parameters of the menu have been set to reference the original
library of the menu. The current and product libraries are added to the
library list when the menu is used. This could cause it to use objects in
the original library.

Ed Fishel,
edfishel@xxxxxxxxxx