This is kind of a poor boy solution but start two sessions, go to that menu on one of them then take each option and display the job on the other session and look at the call stack. As for parms, you’ll probably have to look at the pgm source for those pgms. If that doesn’t exist you can run debug for each of the pgms while you take the menu option.
In addition to working backwards from called options, you can also gain most of the information through a review of the DMPOBJ output for the *MENU object. One section that can be useful can be found by searching for “–WUIK–” in the spooled output. There are a lot of possible variations, but just about everything can be dug out of that output.
If you have source for similar menus, you might compare the dump output from those against the one without source. The patterns can become apparent for common elements.