|
Hello Chris, You wrote: >I get a CPF24B4 - Severe error while addressing parameter list. From the Error >Code of the API. Honestly, you would think people would have learnt by now. This topic keeps coming up and has been discussed on this list numerous times. The fundamental problem is a complete lack of understanding about basic data types. This is not rocket science -- understanding the basic data types of your programming language language is fundamental to programming and should have been learnt in Programming 101. The really annoying part is that this problem is simply an extension of a problem we've had in RPG for years when dealing with the INFDS and PSDS. They also use BIN(4) -- and BIN(2) -- fields. RPG 'B' fields are not the same as API binary fields. This is discussed quite clearly in the API reference manuals and even in the dis-Information Centre. Follow the links: Programming->CL and APIs->OS/400 APIs->Data Types and Parameter Coding->Binary Data. If you cannot understand that section then you have no business programming. Never use RPG 'B' fields unless you know what you are doing. Don't use them just because the dumb examples you are copying from use them. If you are stuck using RPG/400 or earlier then you have to use RPG 'B' and you should define them as 9B 0. In RPG IV you should always use 10I 0 unless the API parameter definition is explicitly marked as UNSIGNED in which case you should use 10U 0. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
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.