If your development environment consists primarily of CL and RPG, you may want to look at how you prototype the RPG subprocedures in your service programs. Why, you may wonder? The short answer is so that you don't have problems with data integrity when you use CallPrc (Call procedure) in CL to invoke subprocedures. The data integrity problem occurs when you use return values or parameters passed by value for data types that CL handles differently than RPG (for example, ...

REGISTER NOW TO ACCESS THIS ARTICLE

All registered users get access to premium content on iPro Developer for free.

Already registered? here.