|
Scott: This may be a good idea for just a temporary fix. Someone did change one of the menus to native without looking into this issue & now the hot keys don't work. I think maybe I'll try this temporarily while we hammer out what to do for the future. Thank You, Lois > > Are you actually replacing the OCL with CL? Or are you just changing > the menus? > > Maybe a quick-fix would be to pass the menu name as a parameter? (You'll > have to excuse me, my OCL is a little rusty) > > On the menu, make the call look like: > > MYPROC MYMENU > > And in the proc do: > > // LOCAL OFFSET-167,DATA-'?1?' > > Or if you're using CL: > > CALL MYCLPGM PARM('MYMENU') > > And: > > PGM PARM(&MENU) > > DCL VAR(&MENU) TYPE(*CHAR) LEN(10) > > CHGDTAARA DTAARA(*LDA (167 10)) VALUE(&MENU) > > ... other stuff ... > > ENDPGM > > > In the long-term, I'd change this to not base things on the menu names, > but use something else, so you could put these programs on any menu > without having the menu name hardcoded into them.
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.