|
> I want to add functionality from an MI program call to > automatically call "Work with PDM options" (F16). Do > anyone know what parameter(s) are required? Thanks in > advance for your help. For what it's worth, instead of messing with possibly voodoo PDM structures, we maintain a user-defined options file by way of command prompting with pseudo-CL variable names (like "&N" meaing "Item Name"), using Process Commands QCAPCMD API. The key trick is to specify type of command processing value "8" in the options control block parameter. >From the reference manual: "8. User-defined option. This option allows a user to create user-defined option command strings similar to those used by the programming development manager (PDM). It allows checking and creating a command string for future use with types 0 through 3 execpt that variables are allowed. The command string produced may not be directly operable. That is, if CL variables were specified in the command string, the user must perform a substitution prior to using the API with types of 0 or 2."
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.