Our shop runs a System/36 emulation environment on an RS/6000 AIX machine. We want to move this environment to an i5. In our current situation, we issue a ton of Unix calls within our OCL procedures. We have over 5,500 of these calls. We’re trying to wrap our arms around understanding the impact/feasibility of the move to the i5. If we can’t continue the Unix calls “as is,” going to the i5 probably will not happen.

We plan to keep the RS/6000 along with the i5. So, in a nutshell, is there a way to issue the Unix calls from

i5/OS subsystems are segmented system environments where work (jobs) is submitted and executed. Subsystems can be customized for the type of work being done (batch, interactive, server), how much work is simultaneously executed, and what resources are used for job execution. This week, I’ll look at how you can use shared pools to assign dedicated i5/OS main storage and active threads for subsystem job execution, without having to share these resources with another subsystem.

How Subsystem Shared Pools are Created and Assigned

For newer i5 administrators, this first section discusses how system shared pools are put together and provides some

Who would’ve guessed, but we’re almost done with the long list of SQL enhancements introduced in release V5R4 of i5/OS. Sorrow not, though, because this tip will bring abundant joy as a major limitation of SQL has just been lifted–the ability to run a query recursively.

Recursive queries are queries that need to do multiple self joins an unknown number of times. Take, for example, an employee master table that contains an employee’s employee number and the manager’s employee number. Say we need a list of all employees along with a listing of all manager’s above the employee. To do