|
> To me the bigger sin(being a data base bigot) is > using a 15,5 parameter variable for (say) a customer number or invoice > number when my data dictionary defines it as 7,0. I want that attribute > of the DB customer entity to cascade everywhere I used customer number. The sin is in using the CALL CL command. If the format or length of the parameter is important (when isn't it?), use a CMD interface for any program that must be called from the command line or within a CL program (unless the CL program *always* passes variables) or submitted as a job. Barbara Morris +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.