At 02:35 07/20/98 -0700, Mohammad Kahn wrote:
>man, SDA is being a bitch to work w/for the first time.
>can someone explain why on earth when i design a menu and hit enter
>the computer tells me certain fields over lap and when i enter, half
>the stuff i entered by the menu option #'s end up disappearing into
>thin air?
>
>oh yeah, and when you work with commands on an SDA screen what do you
>write there? i mean i'm going to write cl programs so, do cl commands
>go there? what?

Display file menus use part of the screen (I think below line 19) for the 
command line, prompt and function keys. Create a new menu. It will have numbers 
down the side. Put your descriptions next to the numbers and you should be 
fine. You can also change the display title, but don't change anything else. 
Then press F13 to access the command area. You do type CL commands there. 
Usually they are either CALL PGM(xxx) or SBMJOB CMD(CALL PGM(X)) or a user 
written command that executes a program. Don't press F3 or you will lose 
everything. Press Enter first, then F12. When you exit, SDA will display a list 
of options, one of which lets you compile your menu.

Usually, I've found that if you understand what it's doing, it's a little 
easier to understand what's happening. When you create a menu with SDA, you are 
really creating three separate objects. The first is a display file, which 
contains the menu options display. You can see what's in there with DSPFFD 
menuname or DSPFD menuname. The second is a message file, which contains the 
commands. You can use WRKMSGD MSGF(menuname) to see what's in it. The third is 
a menu object. It is an object which contains a reference to the display file 
and message file, and several other values, like command line size, current 
library and product library. You can see what's in that one by running DSPMNU 
menuname. There is one gotcha with SDA menus. They always specify the library 
that the display file and message file were in when the menu object was 
created. If you move the menu, display file and message file from one library 
to another, the menu won't work anymore, because the menu object will t!
ell 
the system to look in the original library. You can change this with CHGMNU, 
and specify *LIBL for the display and message file locations.

Pete


Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

+---
| 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
+---


This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].