Re: %date() parameter confusion

Doug,

Thanks for the tip.  I would normally put this sort of thing in a service 
program.  As it stands, I'm doing this in a program generation tool, and 
in this case it is simpler to use their validation framework than to use a 
service program procedure.

You're right though - this sort of switching construct is less frustrating 
when it's done in such a way that it won't be repeated.

Thanks again,
Adam


rpg400-l-bounces@xxxxxxxxxxxx wrote on 02/08/2006 09:45:28 AM:

Adam,

.. figurative constants like *ISO are not the same as '*ISO', I guess

I was hoping there might be a way around the if ... elseif logic.

Create your own subprocedure which accepts a character variable for the
second argument, and put your if/else or select/when logic in it. 

Ideally,

you'd then place this in a service program with other date handling
routines, so you can re-use them easily in other projects.  But even
encapsulating it in a subprocedure within the same program gives the 

effect

you are seeking.

Subprocedures are terrific -- take advantage of them.

Doug

#####################################################################################
Attention:
The above message and/or attachment(s) is private and confidential and is 
intended 
only for the people for which it is addressed. If you are not named in the 
address 
fields, ignore the contents and delete all the material. Thank you. Have a nice 
day.

For more information on email virus scanning, security and content
management, please contact administrator@xxxxxxxxxxxx
#####################################################################################