|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] This list has convinced me to create an externally described physical file with all the common PARM fields in it's description. Pass just this one parm. It assures consistency. A simple CLEAR will rid you of data decimal errors. ------------------------------------------ Booth Martin Booth@MartinVT.com http://www.MartinVT.com ------------------------------------------ "Hopkins, Bill" <BHopkins@saurerinc.com> Sent by: rpg400-l-admin@midrange.com 10/25/2002 11:14 AM Please respond to rpg400-l@midrange.com To "'rpg400-l@midrange.com'" <rpg400-l@midrange.com> cc Subject Best way for numeric parms I have a client who just with through alot of code and change Plist to use 15 5 values in his calls to RPG IV programs. stop data decimals on calls but now of course getting target to smal when trying to move back to correct size. ruff example RPGII call to RPG IV he has done RPGII code z-add 1 company 2 0 z-add company passcompany call 'pgm2' parm passcompany 15 5 RPG IV code *Entry plist parm passcompany 15 5 z-add passcompany keycompany 2 0 <<< error of course Can fix but was wanting to get suggestions for replacement code for all of these type calls. Thanks Bill H
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.