Very Computer

Hi,

The command has a parameter (SRCFILE) of type ELEM that consists of 3
fields (File name, Libary and Member) per element. The min and max values
of SRCFILE are MIN(1) and MAX(9). When the prompt override program
finishs, then the overriden values of SRCFILE are passed back to the
command but obviously they are not "recognized" by the command. Although I
can see the overriden values of SRCFILE on the screen the values are not
passed to the following validity checker. Is it a bug in the OS/400 or am
I missing something.

The first parameter of the command (OPTION) is the only parameter that has
KEYPARM(*YES).

Any help would be greatly appreciated.

Thomas Raddatz.

With or without keyparm the prompt override program will work, then the
values passed back by it should be passed to the validity checker. I
made a lot of command like that and I did never  had that problem. The
validity checker must declare the same parameters of the processig
program, that's all.
--
Dr. Ugo Gagliardelli, Modena, Italy
Spaccamaroni andate a cagare/Spammers not welcome
Spamers iros a la mierda/Spamers allez vous faire foutre
Spammers loop schijten/Spammers macht Euch vom Acker

Ugo,

The command works fine (prompt override and validity checker program) for all
other parameters. Only the SRCFILE parameter which is of type ELEM with 3 fields
per ELEM cause the problems. So I think it only has to do with the TYPE(ELEM1)
keyword.

Thomas Raddatz.

Ugo Gagliardelli schrieb:

--
*=====================================================*

   e-mail Adresse:

   Homepage:
        http://www.tools400.de

*=====================================================*

I should make some tests to be sure, up to now I cannot remember any
problem with validity checker and parms with elem keyword specified.
--
Dr. Ugo Gagliardelli, Modena, Italy
Spaccamaroni andate a cagare/Spammers not welcome
Spamers iros a la mierda/Spamers allez vous faire foutre
Spammers loop schijten/Spammers macht Euch vom Acker

Please let me know about the results of your tests. This is how the
"trouble maker" is defined:

PARM       KWD(SRCFILE) TYPE(ELEM1) MIN(1) MAX(9) +
             PROMPT('Source File(s)')

ELEM1:      ELEM       TYPE(*NAME) LEN(10) +
                         PROMPT('File Name')
            ELEM       TYPE(*NAME) LEN(10) PROMPT('  Library')
            ELEM       TYPE(*GENERIC) LEN(10) DFT(*ALL) SPCVAL((*ALL)) +
                         CHOICE('*ALL, name, generic*') +
                         PROMPT('    Member')

Thomas Raddatz

It works.
These are sources of my test case:

Prompt override (COMANDOO):
PGM (&CMD &STR)                                                    
DCL &CMD *CHAR 10                                                  
DCL &STR *CHAR 5700                                                
DCL &BIN *CHAR 2 X'0028'                                          
CHGVAR &STR (&BIN *TCAT 'SRCFILE((PROVALIB PROVAFILE PROVAMBR))')  
SNDPGMMSG  MSG('POP' *CAT &STR)                      
ENDPGM

Command processing (COMANDOP):
PGM &SRCF                                    
DCL &SRCF *CHAR 32                            
SNDPGMMSG  MSG('CPP' *CAT &SRCF)
ENDPGM

Validity checker (COMANDOV):
PGM &SRCF                                      
DCL &SRCF *CHAR 32                            
SNDPGMMSG  MSG('VPP' *CAT &SRCF)  
ENDPGM

Command (COMANDO):
compiled with:  
CRTCMD CMD(COMANDO) PGM(COMANDOP) SRCFILE(SRCF) VLDCKR(COMANDOV)
PMTOVRPGM(COMANDOO)                                                                      
CMD 'PROVA COMANDO'                                                      
PARM       KWD(SRCFILE) TYPE(ELEM1) MIN(1) MAX(9) +                      
             PROMPT('SOURCE FILE(S)')                                    
ELEM1:      ELEM       TYPE(*NAME) LEN(10) +                            
                         PROMPT('FILE NAME')                            
            ELEM       TYPE(*NAME) LEN(10) PROMPT('  LIBRARY')          
            ELEM       TYPE(*GENERIC) LEN(10) DFT(*ALL) SPCVAL((*ALL)) +
                         CHOICE('*ALL, NAME, GENERIC*') +                
                         PROMPT('    MEMBER')                            

Input line entered:
COMANDO + F4

Output from joblog:
COMANDO SRCFILE((PROVALIB PROVAFILE PROVAMBR))    
POP  SRCFILE((PROVALIB PROVAFILE PROVAMBR))      
VPP      PROVALIB  PROVAFILE PROVAM              
CPP      PROVALIB  PROVAFILE PROVAM              

Non displayable characters are:
POP + x'0028'
VPP + x'000100040003'
CPP + x'000100040003'
as expected. That's it.

--
Dr. Ugo Gagliardelli, Modena, Italy
Spaccamaroni andate a cagare/Spammers not welcome
Spamers iros a la mierda/Spamers allez vous faire foutre
Spammers loop schijten/Spammers macht Euch vom Acker

Thanks a lot for the valuable information you provided. I found the error
and here is what happend:

Since the "CL Programming" guide states "Precede each keyword with a
selective prompt character to define how to display the parameter and what
value to pass to the CPP." I added selective prompting characters to each
keyword in the command string by the prompt override program. But since I
did not notice that parameters with MIN(1) must be preceded with "??"
instead of "?<" I added the "?<" to the SRCFILE parameter. That was the
mistake I made. After having removed the selective prompting it works
fine, now. I also tried "??" and it works fine, too.

However I see no difference between "??" and no selective prompting
characters. Maybe that someone can enlighten me?

Thomas Raddatz.

The way I understand this figure is that each parameter a prompt overide
program specify, is like a ?? selective prompting were specified for
that parameter. In other words they do the same job and for that the
result must be the same.

--
Dr. Ugo Gagliardelli, Modena, Italy
Spaccamaroni andate a cagare/Spammers not welcome
Spamers iros a la mierda/Spamers allez vous faire foutre
Spammers loop schijten/Spammers macht Euch vom Acker