Sidebar

The Linux Letter: Revving Up the RPMs

Linux / Open Source
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

One of the criticisms frequently launched at the *nix platforms is the procedure used to install new software. Although I don't think that the command string "./configure;make;make install" is beyond the capabilities of the average 12-year-old, many decry it as being too archaic, pointing to the installation wizard available on Windows as the way it should be done. This month, I'll investigate various "wizards" available to Linux users that duplicate, indeed exceed, the functionality of the Windows counterpart.

Back to the Source

Before we delve into our other options, let's start with basic *nix software installation. Once you've read this section, you'll understand why the *nix pundits criticize the process.

Although open-source software is almost always available as a precompiled binary, you'll occasionally find a program that is available in source form only. Should you uncover one of these, or if you wish to use the bleeding-edge version of a program, you'll need to roll your own binary. Typically, you obtain the source code from either an FTP server or the project's Concurrent Versions System (CVS) server (CVS was discussed in this column in November 2002). Once the source files are downloaded and installed on your system (the procedures for which vary and are normally described on the project Web site), the commands I mentioned earlier ("./configure;make;make install") are what would typically be used to install that program. The command "./configure" runs a script that verifies the existence and location of any compilers or libraries that will be needed to compile the program.

Assuming that you have all of the requirements (compilers, libraries, tools) loaded on your system, "make" is the GNU tool that, when called without parameters, performs the magic of compiling and linking the program into binary form. If no errors occur during the compilation process, "make install" will transfer the binaries and associated man (manual) pages to their final place on your *nix system.

So what's the problem with this scenario? Nothing, really--except that, as the system administrator, you'll have quite a bit of manual bookkeeping to perform. You'll need to keep an inventory of the software you install so that you can keep your system up-to-date when enhancements become available. The inventory will be useful when you want to create similar systems with identical software suites. The inventory will be invaluable when you wish to clean up a system, removing unused packages and reclaiming space.

Thus, you can build and maintain a system using virtually nothing but source code. Obviously, the fact that something can be done isn't usually reason enough to actually do it. There has to be a better way--and there is.

The Better Way

Most modern Linux distributions (and commercial unices) have some automated means of managing installed software. For the Red Hat, Mandrake, and SuSE distributions, it is called the Red Hat Package Manager (RPM), which is the main thrust of this article.

Software that has been bundled into an RPM "package" can easily be installed or removed with RPM in a manner similar to the Windows Add/Remove utility. But RPM has functionality beyond the Windows counterpart. RPM can also...

  • Tell you the packages that you have installed on your system, as well as their versions.
  • Provide the list of files that comprise a package.
  • Given a specific file's name, tell you which package "owns" it.
  • Prevent you from deleting a package upon which one or more other packages depend and tell you the names of the dependent package(s).
  • Prevent you from installing a package for which dependent packages are required but are not currently installed.
  • Update an existing package to a newer version or "downgrade" a package to a previous version.
  • List any files that have changed since they were installed, whether it be a change in permissions, ownership, or content.
  • Validate the package's source so you can be sure that the contents contain what the originator intended and that no nefarious schemes are being perpetrated.
  • Show you the scripts that will be run during the installation of a package, allowing you to determine what the package will be doing both pre- and post-installation.

 

As you can see, RPM is an extremely powerful package that has many advantages over its Windows cousin, not the least of which is the fact that it is open source. This means that you can use it yourself to package your own software without having to purchase an installation builder (which you must do if you want to use the Windows installer).

Most open-source software is available in binary form already bundled into an RPM file, so typically you only need to download the appropriate package and then issue the command rpm -ivh the_complete_package_name.rpm to have the software installed on your system. We'll look at an example shortly.

What if your desired software isn't available as an RPM, but is, instead, only available in source form? You might consult the manual for RPM and learn how to code RPM specifications. An easier solution is to use a program called checkinstall, which is used in lieu of the "make install" step mentioned earlier. This program creates an RPM package "on the fly," based on the actions performed by make. The result is that the software will be compiled, bundled into an RPM file, and installed on your system.

Now, let's turn our attention to a real-life example of using RPM to install software. I'll be using the command line to accomplish this, but for you visual types, there are GUIs to accomplish the same tasks. These include kpackage (for KDE desktop environment users), gnorpm (for Red Hat 7.3 and earlier), and redhat-config-packages (for Red Hat 8 and newer).

The software we'll be installing (and removing) during this demonstration is the Linux driver for IBM's 2085 printer/copier. Let's start by looking over the package to see what might be interesting (the output has been reformatted to fit the available space):

 

[root@zeus2 demo]# rpm -qpil PrintTool_enu.i386.rpm
Name        : IBMPrintTool                 
 Relocations: (not relocateable)
Version     : 2_enu                             
      Vendor: IBM Corporation
Release     : 02                            
  Build Date: Fri 10 May 2002 07:08:00 AM EDT
Install date: (not installed)               
  Build Host: cosminb.saguaro.ro
Group       : Utilities/System              
  Source RPM: IBMPrintTool-2_enu-02.src.rpm
Size        : 1984709                          
     License: GPL
Packager    : Cosmin Bonea <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Summary     : IBM Departmental Printer Tools
Description :
This packages contains tools for IBM Departmental Printers, for
managing queues and printing.
This IBM Departmental Printer Tools package requires the following,
in the specified order:
  1) The LPRng package version 3.6.4 , available from
     http://www.lprng.com (normally installed at system installation)
  2) GTK, available from http://www.gtk.org (normally installed at 
 system installation)
/etc/ibmlp2
/etc/ibmlp2/data
/etc/ibmlp2/data/pafs
/etc/ibmlp2/data/pafs/ibm27051.paf
/etc/ibmlp2/data/pafs/ibm27851.paf
/etc/ibmlp2/data/pafs/messages.paf
/etc/ibmlp2/data/pafs/messagesPPDParser.paf
/etc/ibmlp2/data/ppds
/etc/ibmlp2/data/ppds/ibm27051.ppd
/etc/ibmlp2/data/ppds/ibm27851.ppd
/etc/ibmlp2/docs
...

 

I have truncated the file listing, but, as you can see, there is a ton of information stored within the RPM file. It is curious to note here that IBM deviated from the standard naming convention for RPM files. The supplied RPM file is called "PrintTool_enu.i386.rpm," yet the package is called "IBMPrintTool." What's worse, the original source RPM had a name that followed convention, so, obviously, someone renamed the thing prior to burning the driver CD from which this file was obtained. Thank you very much for the confusion.

Want to see what scripts will be run when RPM starts installing this package?

 

[root@zeus2 demo]# rpm -qp PrintTool_enu.i386.rpm --scripts
postinstall scriptlet (through /bin/sh):
# display the LOGO pixmap
#-----------------------------------------------------------
/usr/bin/IBMlogo2 & 2>/dev/null
#-----------------------------------------------------------
preuninstall scriptlet (through /bin/sh):
# remove the runtime created files, if exist
#-----------------------------------------------------------
if [ -a "/etc/ibmlp2/data/pafs/queues.paf" ]; then
    rm /etc/ibmlp2/data/pafs/queues.paf
fi
rm -f `find /etc/ibmlp2/data -name "*.def"`
#-----------------------------------------------------------
[root@zeus2 demo]#

 

There are two scripts here. The first, called the "postinstall" script, is called once the software has been extracted to the appropriate directories. In this case, all the script does is display an IBM splash screen. The second, called "preuninstall," is called prior to the removal of the software (if that is ever done).

Now that our curiosity is satisfied, let's install the software. The command to do that is short and sweet:

 

[root@zeus2 demo]# rpm -ivh PrintTool_enu.i386.rpm
Preparing...                
########################################### [100%]
   1:IBMPrintTool           
########################################### [100%]
[root@zeus2 demo]#

 

We can easily check to verify that the package is a part of our system:

[root@zeus2 demo]# rpm -qi IBMPrintTool
Name        : IBMPrintTool                 
 Relocations: (not relocateable)
Version     : 2_enu                             
      Vendor: IBM Corporation
Release     : 02                            
  Build Date: Fri 10 May 2002 07:08:00 AM EDT
Install date: Thu 19 Jun 2003 05:26:43 PM EDT      
  Build Host: cosminb.saguaro.ro
Group       : Utilities/System              
  Source RPM: IBMPrintTool-2_enu-02.src.rpm
Size        : 1984709                          
     License: GPL
Packager    : Cosmin Bonea <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Summary     : IBM Departmental Printer Tools
Description :
This packages contains tools for IBM Departmental Printers, 
for managing queues and printing.
This IBM Departmental Printer Tools package requires the following,
 in the specified order:
  1) The LPRng package version 3.6.4 , available from
     http://www.lprng.com (normally it is installed at 
     the system installation)
  2) GTK, available from http://www.gtk.org (normally it 
     is      installed at the system installation)
[root@zeus2 demo]#

 

Finally, let's remove the package from our system and then verify that it is gone:

[root@zeus2 demo]# rpm -ev IBMPrintTool
[root@zeus2 demo]# rpm -qi IBMPrintTool
package IBMPrintTool is not installed
[root@zeus2 demo]#

 

That's the quick tour of RPM. I know what you're thinking: Where are the warts? There is one big one that I find annoying. As I mentioned earlier, RPM will preclude the installation of software for which at least one of its dependencies is not loaded. It will tell you the name of the missing file(s) but will not tell you which software package provides the file(s). It's not that the information isn't available--at least one web site offers a reverse "which package has this file?" inquiry. But once you know the names of the missing packages, you still need to download them manually and then install them either in order of dependency (one by one) or by typing them on the command line together: rpm -i package1 package2 ... package n.

And the torture never stops. If any of the packages that you try to install have missing parts, you'll need to repeat the game of hide-and-seek you've just played, locating the missing packages until you have all dependencies satisfied.

I can't speak about SuSE or Mandrake, but Red Hat does have another facility that takes care of all of this for you. It's called up2date, and it uses the Red Hat Network Server and the Internet to allow you to keep your system up-to-date (and to install new software). For example, if I want to install a particular package, say PackageA, all I need to do is type up2date -i PackageA, and it will do all of that work for me. The Red Hat Network is a subscription service that has a per-machine fee. Red Hat will give you one machine free (with access on a "resources-as-available" basis); you can get additional entitlements as needed. For those who have wondered how anyone can make money giving away software, this is one example of how to do it. I have a number of entitlements and am more than happy to throw some money Red Hat's way just for this service.

Now, That's YUMmy!

What if you don't want to spend the money for an entitlement for each of your machines? You have another option: more open-source software. I have a location that has for its Internet access a pathetically slow dial-up modem connection. So, even though the pocketbook is willing, the body can't make use of the up2date function. In this case, I have created a local version of an up2date server using a package called the Yellow dog Updater, Modified, or Yum. By copying all of the RPM files from the distribution CDs and then adding the update RPM files available from Red Hat (which I bring in on my laptop from home), I can create a Yum server with ease using only a standard FTP or HTTP server (conveniently available in all Linux distributions). Yum uses RPM "under the covers," but it does all of the nasty dependency checking for you. I encourage you to visit the Yum Web site for a complete overview of this wonderful product.

Something More Apt?

Aficionados of the Debian Linux distribution are out of luck when it comes to RPM. They do have their own equivalent, though. It's called "apt," and it has many of the same facilities as RPM (some say more). Commands such as apt-install or apt-update help keep the software inventory on your Debian system under control. Should you, too, become enamored of apt (RPM versus apt is another one of those geek holy wars), you can get a port (called apt-rpm) to manage your RPM-based system. I do not currently have any Debian-based systems to manage, so I admit to only a passing familiarity with it.

You aren't giving up the ability to manage your source-based software by using Debian. The checkinstall utility I mentioned earlier is capable of generating DEBs (the apt package file), so you'll have the same convenience in either RPM- or DEB-based systems.

Making It Easier

I'm always looking for ways to minimize the amount of time I need to manage a system. My motivation for this article came from an individual who was having issues with writing a script to start and stop a daemon. Upon investigation, I found that he had downloaded and installed the tar ball version of the product in question instead of the RPM version, which was available from the same place. The result was an installation that required a lot of manual tweaking to get it running properly. Once that oversight was corrected and he had installed the RPM for the software, he had an installation that meshed perfectly with his Red Hat Linux system.

Take some time to get familiar with RPM (or apt). The power of these tools will make your administrative job much easier, allowing you get on to more interesting things than software inventory management.
That's it for this month. If you have some vexing problem that you'd like me to address in future columns, please drop me a line.

Barry L. Kline is a consultant and has been developing software on various DEC and IBM midrange platforms for over 20 years. Barry discovered Linux back in the days when it was necessary to download diskette images and source code from the Internet. Since then, he has installed Linux on hundreds of machines, where it functions as servers and workstations in iSeries and Windows networks. He recently co-authored the book Understanding Linux Web Hosting with Don Denoncourt. Barry can be reached at This email address is being protected from spambots. You need JavaScript enabled to view it..

 

Barry Kline

Barry L. Kline is a consultant and has been developing software on various DEC and IBM midrange platforms since the early 1980s. Barry discovered Linux back in the days when it was necessary to download diskette images and source code from the Internet. Since then, he has installed Linux on hundreds of machines, where it functions as servers and workstations in iSeries and Windows networks. He co-authored the book Understanding Web Hosting on Linux with Don Denoncourt. Barry can be reached at barry@blkline.com.

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • White Paper: Node.js for Enterprise IBM i Modernization

    SB Profound WP 5539

    If your business is thinking about modernizing your legacy IBM i (also known as AS/400 or iSeries) applications, you will want to read this white paper first!

    Download this paper and learn how Node.js can ensure that you:
    - Modernize on-time and budget - no more lengthy, costly, disruptive app rewrites!
    - Retain your IBM i systems of record
    - Find and hire new development talent
    - Integrate new Node.js applications with your existing RPG, Java, .Net, and PHP apps
    - Extend your IBM i capabilties to include Watson API, Cloud, and Internet of Things


    Read Node.js for Enterprise IBM i Modernization Now!

     

  • Profound Logic Solution Guide

    SB Profound WP 5539More 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 companyare not aligned with the current IT environment.

    Get your copy of this important guide today!

     

  • 2022 IBM i Marketplace Survey Results

    Fortra2022 marks the eighth edition of the IBM i Marketplace Survey Results. Each year, Fortra captures data on how businesses use the IBM i platform and the IT and cybersecurity initiatives it supports.

    Over the years, this survey has become a true industry benchmark, revealing to readers the trends that are shaping and driving the market and providing insight into what the future may bring for this technology.

  • Brunswick bowls a perfect 300 with LANSA!

    FortraBrunswick is the leader in bowling products, services, and industry expertise for the development and renovation of new and existing bowling centers and mixed-use recreation facilities across the entertainment industry. However, the lifeblood of Brunswick’s capital equipment business was running on a 15-year-old software application written in Visual Basic 6 (VB6) with a SQL Server back-end. The application was at the end of its life and needed to be replaced.
    With the help of Visual LANSA, they found an easy-to-use, long-term platform that enabled their team to collaborate, innovate, and integrate with existing systems and databases within a single platform.
    Read the case study to learn how they achieved success and increased the speed of development by 30% with Visual LANSA.

     

  • Progressive Web Apps: Create a Universal Experience Across All Devices

    LANSAProgressive Web Apps allow you to reach anyone, anywhere, and on any device with a single unified codebase. This means that your applications—regardless of browser, device, or platform—instantly become more reliable and consistent. They are the present and future of application development, and more and more businesses are catching on.
    Download this whitepaper and learn:

    • How PWAs support fast application development and streamline DevOps
    • How to give your business a competitive edge using PWAs
    • What makes progressive web apps so versatile, both online and offline

     

     

  • The Power of Coding in a Low-Code Solution

    LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Why Migrate When You Can Modernize?

    LANSABusiness 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.
    In this white paper, you’ll learn how to think of these issues as opportunities rather than problems. We’ll explore motivations to migrate or modernize, their risks and considerations you should be aware of before embarking on a (migration or modernization) project.
    Lastly, we’ll discuss how modernizing IBM i applications with optimized business workflows, integration with other technologies and new mobile and web user interfaces will enable IT – and the business – to experience time-added value and much more.

     

  • UPDATED: Developer Kit: Making a Business Case for Modernization and Beyond

    Profound Logic Software, Inc.Having trouble getting management approval for modernization projects? The problem may be you're not speaking enough "business" to them.

    This Developer Kit provides you study-backed data and a ready-to-use business case template to help get your very next development project approved!

  • What to Do When Your AS/400 Talent Retires

    FortraIT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators is small.

    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:

    • Why IBM i skills depletion is a top concern
    • How leading organizations are coping
    • Where automation will make the biggest impact

     

  • Node.js on IBM i Webinar Series Pt. 2: Setting Up Your Development Tools

    Profound Logic Software, Inc.Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. In Part 2, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Attend this webinar to learn:

    • Different tools to develop Node.js applications on IBM i
    • Debugging Node.js
    • The basics of Git and tools to help those new to it
    • Using NodeRun.com as a pre-built development environment

     

     

  • Expert Tips for IBM i Security: Beyond the Basics

    SB PowerTech WC GenericIn this session, IBM i security expert Robin Tatam provides a quick recap of IBM i security basics and guides you through some advanced cybersecurity techniques that can help you take data protection to the next level. Robin will cover:

    • Reducing the risk posed by special authorities
    • Establishing object-level security
    • Overseeing user actions and data access

    Don't miss this chance to take your knowledge of IBM i security beyond the basics.

     

     

  • 5 IBM i Security Quick Wins

    SB PowerTech WC GenericIn today’s threat landscape, upper management is laser-focused on cybersecurity. You need to make progress in securing your systems—and make it fast.
    There’s no shortage of actions you could take, but what tactics will actually deliver the results you need? And how can you find a security strategy that fits your budget and time constraints?
    Join top IBM i security expert Robin Tatam as he outlines the five fastest and most impactful changes you can make to strengthen IBM i security this year.
    Your system didn’t become unsecure overnight and you won’t be able to turn it around overnight either. But quick wins are possible with IBM i security, and Robin Tatam will show you how to achieve them.

  • Security Bulletin: Malware Infection Discovered on IBM i Server!

    SB PowerTech WC GenericMalicious programs can bring entire businesses to their knees—and IBM i shops are not immune. It’s critical to grasp the true impact malware can have on IBM i and the network that connects to it. Attend this webinar to gain a thorough understanding of the relationships between:

    • Viruses, native objects, and the integrated file system (IFS)
    • Power Systems and Windows-based viruses and malware
    • PC-based anti-virus scanning versus native IBM i scanning

    There are a number of ways you can minimize your exposure to viruses. IBM i security expert Sandi Moore explains the facts, including how to ensure you're fully protected and compliant with regulations such as PCI.

     

     

  • Encryption on IBM i Simplified

    SB PowerTech WC GenericDB2 Field Procedures (FieldProcs) were introduced in IBM i 7.1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i including PII, PCI, PHI data in your physical files and tables.
    Watch this webinar to learn how you can quickly implement encryption on the IBM i. During the webinar, security expert Robin Tatam will show you how to:

    • Use Field Procedures to automate encryption and decryption
    • Restrict and mask field level access by user or group
    • Meet compliance requirements with effective key management and audit trails

     

  • Lessons Learned from IBM i Cyber Attacks

    SB PowerTech WC GenericDespite the many options IBM has provided to protect your systems and data, many organizations still struggle to apply appropriate security controls.
    In this webinar, you'll get insight into how the criminals accessed these systems, the fallout from these attacks, and how the incidents could have been avoided by following security best practices.

    • Learn which security gaps cyber criminals love most
    • Find out how other IBM i organizations have fallen victim
    • Get the details on policies and processes you can implement to protect your organization, even when staff works from home

    You will learn the steps you can take to avoid the mistakes made in these examples, as well as other inadequate and misconfigured settings that put businesses at risk.

     

     

  • The Power of Coding in a Low-Code Solution

    SB PowerTech WC GenericWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed.
    Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

    • Discover the benefits of Low-code's quick application creation
    • Understand the differences in model-based and language-based Low-Code platforms
    • Explore the strengths of LANSA's Low-Code Solution to Low-Code’s biggest drawbacks

     

     

  • Node Webinar Series Pt. 1: The World of Node.js on IBM i

    SB Profound WC GenericHave you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.
    Part 1 will teach you what Node.js is, why it's a great option for IBM i shops, and how to take advantage of the ecosystem surrounding Node.
    In addition to background information, our Director of Product Development Scott Klement will demonstrate applications that take advantage of the Node Package Manager (npm).
    Watch Now.

  • The Biggest Mistakes in IBM i Security

    SB Profound WC Generic The Biggest Mistakes in IBM i Security
    Here’s the harsh reality: cybersecurity pros have to get their jobs right every single day, while an attacker only has to succeed once to do incredible damage.
    Whether that’s thousands of exposed records, millions of dollars in fines and legal fees, or diminished share value, it’s easy to judge organizations that fall victim. IBM i enjoys an enviable reputation for security, but no system is impervious to mistakes.
    Join this webinar to learn about the biggest errors made when securing a Power Systems server.
    This knowledge is critical for ensuring integrity of your application data and preventing you from becoming the next Equifax. It’s also essential for complying with all formal regulations, including SOX, PCI, GDPR, and HIPAA
    Watch Now.

  • Comply in 5! Well, actually UNDER 5 minutes!!

    SB CYBRA PPL 5382

    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.

    Request your trial now!

  • Backup and Recovery on IBM i: Your Strategy for the Unexpected

    FortraRobot automates the routine 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:
    - Simplified backup procedures
    - Easy data encryption
    - Save media management
    - Guided restoration
    - Seamless product integration
    Make sure your data survives when catastrophe hits. Try the Robot Backup and Recovery Solution FREE for 30 days.

  • Manage IBM i Messages by Exception with Robot

    SB HelpSystems SC 5413Managing messages on your IBM i can be more than a full-time job if you have to do it manually. How can you be sure you won’t miss important system events?
    Automate your message center with the Robot Message Management Solution. Key features include:
    - Automated message management
    - Tailored notifications and automatic escalation
    - System-wide control of your IBM i partitions
    - Two-way system notifications from your mobile device
    - Seamless product integration
    Try the Robot Message Management Solution FREE for 30 days.

  • Easiest Way to Save Money? Stop Printing IBM i Reports

    FortraRobot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing.
    Manage your reports with the Robot Report Management Solution. Key features include:

    - Automated report distribution
    - View online without delay
    - Browser interface to make notes
    - Custom retention capabilities
    - Seamless product integration
    Rerun another report? Never again. Try the Robot Report Management Solution FREE for 30 days.

  • Hassle-Free IBM i Operations around the Clock

    SB HelpSystems SC 5413For over 30 years, Robot has been a leader in systems management for IBM i.
    Manage your job schedule with the Robot Job Scheduling Solution. Key features include:
    - Automated batch, interactive, and cross-platform scheduling
    - Event-driven dependency processing
    - Centralized monitoring and reporting
    - Audit log and ready-to-use reports
    - Seamless product integration
    Scale your software, not your staff. Try the Robot Job Scheduling Solution FREE for 30 days.