Comments on: how to code the parameters for API QUSRSPLA http://itknowledgeexchange.techtarget.com/itanswers/how-to-code-the-parameters-for-api-qusrspla/ Fri, 24 May 2013 00:46:57 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/how-to-code-the-parameters-for-api-qusrspla/#comment-73780 tomliotta Fri, 12 Feb 2010 20:46:55 +0000 #comment-73780 There are two parameters that might be most commonly declared incorrectly — Length of receiver variable and Spooled file number. The API documentation shows both as BINARY(4). That essentially means they are “4-byte binary numbers”. (Or 32-bit binary.)

In ILE CL at V5R3 and later, they could both be declared as *INT, which defaults to *INT (4). In RPG IV, they could be declared as 10I 0.

Note that because ‘Spooled file number’ can accept negative values, the declaration cannot be “10U 0″. A sign must be accommodated.

Also note that “BINARY(4)” is not precisely the same as RPG’s ‘B’ data type. While the parms can generally be declared as data type ‘B’, there are plenty of reasons not to do so.

Tom

]]> By: matis http://itknowledgeexchange.techtarget.com/itanswers/how-to-code-the-parameters-for-api-qusrspla/#comment-73771 matis Fri, 12 Feb 2010 16:39:13 +0000 #comment-73771 this is a batch job and i email the report. yes, the job was emailing some other report produced – perhaps in this job stream – perhaps somewhere else – with the same name. i began doing research and came up with this particular api. which special value -1? in the qusrspla api? my difficulty is in actually defining and coding the parameters so i get the expected results. so far i’ve been getting a CPF3C20 when I call the api

]]>