While I seriously doubt your the only one
on the planet doing something like that, it
is a technique I'm not familiar with, but
it sounds useful - could you post (or point
out a link to) some sample code
demonstrating this?

>>> Bob Cozzi <BobCozzi@ibm.net> 09/11/97
10:07am >>>
You know, am I the only one that creates
messages with substitution 
parameters and then issue a RTVMSG command
to get the nicely formatted 
value back?  All that *TCAT stuff, while
perfectly okay for stuff, is a 
really pain in the as. to me. Why not just
create a message?

Bob Cozzi
Bob@RPGIV.COM
www.rpgiv.com
AS/400 Books: 
http://www.rpgiv.com/as400Books.html


On Wednesday, September 10, 1997 11:40 PM,
Neil Palmer 
[SMTP:neil@systemetrix.ca] wrote:
> No Charlie.  The OCL requires commas
between parameters.  You could *CAT 
','
> between them, as long as the parms don't
have blanks padded at the right.
> (Come to think of it, you would *TCAT ','
between them, which is what I
> should have used in my original answer
where I created the &PARMS 
variable
> by concatenating all 4 parms).
> ...Neil

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail
to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email
to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L'
in the body of your message.
| Questions should be directed to the list
owner/operator: david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].