Re: CRTDEVDSP Validity checker program

But a proxy command is not really a command, so it can not have its own\separate validity checker.? If I were to issue the request to CHGCMD MyProxyCmd VLDCHK(MyLib/MyVldChk), the original command would get the assigned validity checker, not the proxy command.?

The question marks, because I have limited experience with the proxy commands. Mostly only what I read in some design documents before the feature was to be activated for the WRKQRY command [via automated updates, if the command were not first explicitly removed from a list].

Regards, Chuck

Jack Kingsley wrote:

Chuck what if you went the route of creating a proxy command,
the proxy is still going to use the original commands validity checker correct.

On Wed, Apr 7, 2010 at 2:54 AM, CRPence wrote:

jmoreno@xxxxxxxxxxxxxxxx wrote:

Does anyone has a skeleton of a validity checker program for
the CRTDEVDSP command

Just the fact that the command has too many parameters makes
it long and tedious.

<<SNIP>>

Perhaps just having the effective output of a RTVCMDSRC-like feature is all that is required to progress? If so, search the
web for that token as command name or perhaps rtvcmd.zip as a
file name. There is also the XML output of commands via
QCDRCMDD API.

Note however that CRTDEVDSP already has a VLDCKR program named QDCCKDLD which is a system-state program and invoked by the
Command Analyzer\Prompter using a method available only to
system-state programs. AFaIK changing the command [rather than
changing only a copy of the command] to refer to a user-state
program will /break/ the command, such that the OS will invoke
the VLDCHK using a method that functions only with user-state
programs; i.e. even a future CHGCMD CRTDEVDSP
VLDCKR(QSYS/QDCCKDLD) to reset the command will not make the
command fully functional again after it was broken by CHGCMD
CRTDEVDSP VLDCKR(somelib/somepgm).

Regardless of any of the above, it may be worth describing what
is desired to be accomplished with use of a private validity checking program. That is, rather than asking about creating
the VLDCHK program, ask about how to effect what is intended to
be achieved by having activated a private validity checking for
that command. There may be more appropriate alternatives to
effect what is desired as the final goal, other than managing
to replace the VLDCKR() of an OS *CMD object.