|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Omitted parms in the middle. In OPM this was done by checking, not PARMS, but the address of each field. For example, if I called a program using parm1 and parm4 but not parm2 nor parm3. The called program would check the address of parm2 by using if %addr(parm2)=*null. If it was null do not do anything with it. Do not even try to clear it, move blanks or zeros to it, not anything. Otherwise you get the MCH error. When would this ever happen in real life? When using a command to drive your program. For example I made a command called RTVJOBD. This command calls a rpg program. Now, the program using this command may not care about some obscure job description property, thus it won't put a variable name in that parameter. If the parameter is not null then I assign the value of that variable from a result field from the api to retrieve a job descriptions attributes. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
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.