|
Donald: Thanks for the response. I still want to know how to re-create that message file on the target system instead of transferring it. We are sometimes on a higher OS level on our development box than our production box. Instead of creating the object to a lower level, we are just recreating objects on our target system. This works great with everything except menus. When the systems are at the same level, we just transfer the objects over directly and do not have this issue. David J. Smith IS Contractor Advanced Information Solutions, Inc. (517) 548-7170 dsmith@ais400.com This is why people use or develop file based systems for creating and displaying menus. Creating IBM menus is painful. I have to look at my notes just about every time I do it. You'll have to send the message file along with the MNUDDS source member to your target system. This is used by the created menu to associated option numbers with commands to execute. Want to save some time? If you want to change what a menu option does, just change the appropriate message in the message file. To create the menu, CRTDSPF using the MNUDDS source member and then CRTMNU specifying the menu name only. The parameters default to *MENU. It will use your created display file and and message file to create the menu object. Hope that helps. Donald R. Fisher, III Project Manager The Roomstore Furniture Company (804) 784-7600 ext. 2124 DFisher@roomstoreeast.com <clip> Can anyone explain the menu creation process for me for the following reason: I have my two source members MENU (Type MNUDDS) and MENU01QQ (Type MNUCMD). Upon exit of SDA when maintaining MENU01, it asks if I want to "Create menu objects?. With a 'Y', three objects are created: MENU01 (Type *MSGF), MENU01 (Type *FILE DSPF), and MENU01 (Type *MENU DSPF). <clip>
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.