|
Bob Cozzi wrote: > > You can't pass a date data-type from the command line via the CALL opcode. > You would need to write a command definition object and point it at your > program. Then the parms would go over just fine. > Sure you can. As long as you put it in the same format that the program is expecting, it should work. Within a program, date values look the same as character data. I think that if you coded a command definition to have a parm with type(*date), you'd have to receive it as a 7A or 7S and do a *CYMD conversion. As far as I know, the only type of parameter you can't pass from the command line is a pointer. (Not that it's always easy to do - some numeric types require specifying hexadecimal data.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
