Re: Ok here is a challenge

Perhaps a late reaction (and the wrong list, as ohers have stated)

Creating a command is IMHO a sort of CL programming. No hardcoding? You
cannot do this in the Command Defintion Object (CDO), as you have to
hardcode allowed values, ranges, dependencies and prompt controls within
the CDO. Other options are Prompt Overwrite Ptogrammes (POP), Command
Choice Programme (CCP) and the Validation Command Programme (VCP). Those
are seperate object from, but linked to the CDO and called at any time
before the Command Processing Programme (CPP).

It is all explained in the CL manuals. 

If he refers to the CPP he is right, but it is not the CDO as he seems to
refer to. Completely misleading statement on his account, especially when
he will not reveal his answer/solution/method.

Regards,
Carel Teijgeler.  

*********** REPLY SEPARATOR  ***********

On 7-3-2007 at 8:48 Douglas Palme wrote:

I received this from one of our RPG gurus and I thought I would present it

to the midrange group and see what ya'll thought:

There is a way to completely control the input from a command and validate

it before the program is actually called. There is also a way to present

the actual valid parameters without hard-coding anything. As an example

you could have a command that takes a division number and if you do not
enter a

division that exists in the DIVISION file it will not accept the value.
This is true for anything you want to validate, a date, time, printer,

username, etc. Most programmer shy away from writing powerful commands as
they do not

understand them.

Anyone?