Re: CMD Validity Program Oddity -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Thanks Chuck.

I looked for some documentation on this but my google skills failed me. I
guess I was right in thinking I was lucky that it worked some of the time.

I'll have to go the path of a traditional prompt program so that it works
all the time.

Brian

date: Mon, 11 Jun 2018 19:12:25 -0500
from: CRPence <crpbottle@xxxxxxxxx>
subject: Re: CMD Validity Program Oddity

Take note of the 2nd "consideration"; found in the docs since, before
v5r4:

[IBM i 7.3->Defining CL commands->Validity checking program for a CL
command](

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/rbam6/wvchk.htm)

"To detect syntax errors and send diagnostic messages for your command,
write a validity checking program.

The following are two considerations for validity checking programs:

The validity checking program is called only if the command syntax is
correct. All parameters are passed to the program the same as they are
passed to a command processing program.

You should *not use* the validity checking program to change parameter
values because the changed values are not always passed to the command
processing program.
--
Regards, Chuck

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.