One answer is simply not to use CL for things like CHKOBJ. If you want to check if an object exists, call the Retrieve Object Description (QUSROBJD) API instead of calling another API to execute a command. Or if you want to check authorities to an object, call the Check User Authority to an Object (QSYCUSRA) API.

Or don’t put CL into RPG — put it into a CL module and bind it for a procedure. Compile it rather than calling an API to interpret it. The CL compiler already does a lot of work for you. Why write RPG code to construct a command in a string out of multiple variables, pass it to an API and then handle whatever results it might log in the job? That’s all easier to do in a module that’s written in the appropriate language.

If there is some reason to interpret and run a CL command, you can call the Process Commands (QCAPCMD) API, the Execute Command (QCMDEXC) API, the system() Execute a Command C library function and one or two others.

Tom