Convert S/36 menu to native menu

[T.Holt]

What's the easiest way to convert a S/36 menu to a native menu without a conversion package? The text for the options needs to stay as it is, but the procedure command names behind the options will be replaced with CALL commands to native CL and RPG programs.

[David Abramowitz]

The S/36 display file source will be available in QS36SRC, but outside of that, I don't think there is any easy way. Dave

[Guest.Visitor]

Ted, If you are using a PC, you can capture the screen image and then paste it to the /400 menu. Then just add the calls as required. I don't know of any freebie conversion from /36 to /400 menus. -bret

[Guest.Visitor]

With my Client Access session I copied (mouse pointer at top left part of screen, press and hold left mouse button, drag right and down to what you want to copy) an entire S/36 menu. Next start SDA (strsda) - use option 2 to create new menu. Paste the contents of what you just copied on your screen. Clean up any areas on your new menu. Press 10 and add the program calls or commands. If you don't have to do too many menus this should work. Hope this helps.... Scott

[T.Holt]

Thanks, guys. I hadn't thought of cutting & pasting the menu text, but that's a good idea. They can put a single command, like WRKJOB, behind each menu option, then use F15 in SEU to copy from the old msg member to the new command text source. Then recreate the menu. They just have one menu for now. This is an experiment of sorts. They're going native with this system to see what's involved and what benefits come of it. If this proves beneficial, they might get a conversion package and do everything. Thanks again for the ideas.

[J.Panzenhagen]

Forgive me if I am missing something, but here is my two cents. 1. Create a PDM option to compile the menu source and convert it to native. The command would be CRTS36DSPF DSPFILE(QTEMP/&N) SRCMBR(&N) SRCFILE(& L/&F) TOFILE(MENULIB/MENUSRC) TOMBR(&N) 2. WRKMBRPDM lib/source MBRTYPE(MNU36) 3. Convert all of the members that do not end with ## 4. Change the type of the converted files to MNUDDS 5. Copy all of the members that do end with ## to your menu source file but replace the ## with QQ. 6. Change the type of the QQ members to MNUCMD 7. Edit the QQ members to insert calls, change MENU to GO, etc. 8. Compile the menus using 17 from PDM on the non QQ members. It worked when I tested it. It should work for you. Additionally, you may want to think about creating commands with the same name as the OCL in the menus. In this case you would not have to change the menu commands and you would have prompting capability. Good Luck! John

[durusky@gowaninc.com]

I just completed a System/36 SSP conversion to native using NCS Professional by Applied Logic Corp. (www.alcsoftware.com). This software did a very good job coverting menus, screen formats, OCL to CL, RPGII to RPGIII and built DDS and converted data files. There where some bugs in the software, but nothing I could not overcome!!! The package comes with a 30 day trial period with limited functionality.

[David Abramowitz]

I don't think that what you are describing is a "conversion". A conversion would wrap the STRS36PRC command around the procedure name and parameters. Using CALL may not work in many cases. This is because it was allowable under S/36 rules to have a procedure name the same as a program name. Since the CL and the HLL are both programs, this became disallowed in native mode. IMO you have a bit of programming cut out for you. Dave