How does this work with V5R4?
Posted: Fri Apr 23, 2010 3:57 pm
Question:
How does this work with V5R4, which doesn't support the HANDLER keyword?
Answer:
Instead of coding the HANDLER keyword, you will have to use our RPG Preprocessor Module. As the name implies, this component works by preprocessing your code to add in direct calls to our Handler. We provide commands PUIRPGMOD, PUIBNDRPG, and PUIRPGSQLI that correspond to CRTRPGMOD, CRTBNDRPG, and CRTSQLRPI, respectively.
As an alternative to calling the PUIXXXXXX commands directly, we also provide optional CL command exit points that can invoke them automatically when you use CRTXXXXXX, if the source code contains Profound UI specific /DEFINE directive.
The preprocessor will create a temporary copy of your original source code, replace the display file operations in there with calls to the Handler, and then invoke the appropriate system RPG compile command on the source to finish the job.
How does this work with V5R4, which doesn't support the HANDLER keyword?
Answer:
Instead of coding the HANDLER keyword, you will have to use our RPG Preprocessor Module. As the name implies, this component works by preprocessing your code to add in direct calls to our Handler. We provide commands PUIRPGMOD, PUIBNDRPG, and PUIRPGSQLI that correspond to CRTRPGMOD, CRTBNDRPG, and CRTSQLRPI, respectively.
As an alternative to calling the PUIXXXXXX commands directly, we also provide optional CL command exit points that can invoke them automatically when you use CRTXXXXXX, if the source code contains Profound UI specific /DEFINE directive.
The preprocessor will create a temporary copy of your original source code, replace the display file operations in there with calls to the Handler, and then invoke the appropriate system RPG compile command on the source to finish the job.