Not a lot of folks know about REXX. REXX is a pretty important little tool in the OS/400 and i5/OS arsenal, because it's sort of like an interpreted CL with lots of extra goodies thrown in. While there are a few things you can't do (for example, you can't directly call a procedure in a service program), the things that you can do are simply amazing. For example, you can execute OS/400 and i5/OS commands using program variables. You simply substitute the REXX variable name in the command, much like you do with PDM options.
Another feature I find especially useful is the ability to embed SQL in my REXX procedures. This ability is more powerful than the RUNSQLSTM command, because you can use it in conjunction with program variables in your REXX program, much as you would in SQLRPG programs. This makes REXX very powerful for system management functions. I can use an OS/400 command to create an output file, then read that file using SQL statements. Based on the contents of each record, I can then execute additional commands.
In this tip, I'm including a simple mass compile program that will compile all RPG and RPGLE members in a source file. The parameters (source file name and library) are read in from the command line. The procedure uses an OS/400 command call to display all the members of the selected source file to a file called MBRS in QTEMP. It then uses SQL statements to read through the file. For each record in the file, it calls a subroutine that processes that member.
To execute this, create a source file and then type the code from listing 1 into a new source member. Let's say you created a member called COMPILEALL in a file called QREXSRC in MYLIB. This would be the syntax:
PARM('QRPGSRC MYLIB')
This will attempt to compile all RPG and RPGLE members in file MYLIB/QRPGSRC.
So how does REXX compare to CL? Let's review our source code, shall we? Roll tape!
Figure 1: This is the listing for the REXX procedure COMPILEALL. (Click image to enlarge.)
(A) First, you can pass as many parameters on the command line as you want; REXX has built-in opcodes to parse the input stream. C and Java programmers should recognize the term "input stream"; the REXX program reads STDIN to get its data (output goes to STDOUT).
(B) The next comparison has to do with calling OS/400 commands. The two are almost identical, except that you must put the command in quotes in REXX. This tells REXX to run the command through an external command processor. The default is to execute the command as an OS/400 command. But the next capability shows how powerful REXX is.
(C) The ADDRESS opcode tells REXX that you want to execute a command, but not an OS/400 command. Instead, you can tell it which environment to target. Environments include the standard OS/400 command processor, the SQL processor, or the CPI communications subsystem. You can even target your own program, which leads to a whole host of other possibilities.
(D) Here is where you can use SQL statement to populate local variables. One cool thing about REXX is that you don't have to define the variables ahead of time. Lazy programmers unite!
(E) This looks pretty simple: calling a subroutine, right? REXX is far more powerful than that, though. Not only can you pass parameters, but if the subroutine doesn't exist in your procedure, REXX will go look outside in the source file for a member with the appropriate name.
(F) Finally, this is the very impressive SELECT statement, which is much like the SELECT statement in RPG and far more impressive than the corresponding "switch" opcode in Java or C. This statement checks the source type and executes the appropriate compile command. Note that you can easily add more types right here or even add special processing for specific programs.
That's just a brief overview of REXX via a working example. You can do a lot more with the language. If you're interested in more REXX tips, please write in and let me know! You can either post in the forums or email me directly:
Joe Pluta is the founder and chief architect of Pluta Brothers Design, Inc. He has been working in the field since the late 1970s and has made a career of extending the IBM midrange, starting back in the days of the IBM System/3. Joe has used WebSphere extensively, especially as the base for PSC/400, the only product that can move your legacy systems to the Web using simple green-screen commands. Joe is also the author of E-Deployment: The Fastest Path to the Web, Eclipse: Step by Step, and WDSc: Step by Step. You can reach him at
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online