MC Systems Insight
MC Power Technology Manager
MC RPG Developer
MC Power Developer
MC TNT Tips 'n Techniques
MC AIX Expert
MC Linux Expert
MC Mobile on Power
This Week @ the MC Press Bookstore

March 4, 2009 | Vol 8 Issue 5


In This Issue:

Feature Article - Programming
Calling a PC Application from RPG, Part III

Allow commands to be executed on the remote computer.

tom_snyder.jpgBy Tom Snyder

To execute commands on your PC from RPG, you must first set up a server to listen for these requests and grant permission to the IBM i to execute those commands. In order for RPG to be able to call a PC application using REXEC, you will need three capabilities:


•·         Identifying the IP address of a PC from within an RPG program

•·         Calling the PC application from within an RPG program

•·         Allowing commands to be executed on the computer


In previous articles, I explained how to identify your PC on the network using the QDCRDEVD API and how to send commands to your PC using the Run Remote Command (RUNRMTCMD) command. In this article, we will install and configure a server to support RUNRMTCMD.


Feature Article - Programming
Practical RPG: Replace PSSR and INFSR with MONITOR

MONITOR takes RPG into the next level of error detection, and this article introduces one of the most useful aspects of this new opcode.

joe_pluta.jpgBy Joe Pluta

RPG has come a long way since the H1 halt indicator. Back in the day, you issued a halt when a program encountered a completely unexpected condition--usually application errors such as a master record not found or a divide by zero, although fatal errors could also include programs not found or files full. The current height of technology is to use the Program Error Subroutine (PSSR) to handle unexpected errors, but this article will show you an even cleaner and easier way to handle errors: the MONITOR opcode.


Support MC Press - Visit Our Sponsors


 Popular Forums



   Search Sponsor


 Popular Searches