Resources

Article

How Legacy Processing in IT Leads to Downtime on IBM i

Why haven’t IT processes kept pace with business changes? Why are you still suffering from downtime as the result of human error? Read this article to see how legacy processing methods are still leading to downtime today—and what you can do to stop it.
Article

Be in Control of Your ERP

Many ERP packages have built-in schedulers. However, these schedulers are typically not flexible or robust enough to meet the needs of even the smallest data center.
Article

Lessons Learned from IBM's Native Scheduler

Your shop runs more than 30 jobs each day. Your jobs must communicate across IBM i and another OS. You need to monitor them and generate reports for audits or SLAs. Do your existing job schedulers really meet your needs?
Case Study

Hershey Entertainment Quickly Encrypts Credit Card Data with Powertech Encryption for IBM i

Hershey Entertainment & Resorts is a privately held company located in the tourist center of Hershey, Pennsylvania, and has entertainment, resort and commercial divisions. Earlier this year, Hershey learned that because the entertainment and resort operations accept credit cards for payment, they needed the information stored by their box office ticketing and reservations applications to be...
Case Study

Field-level Encryption Helps Retail Chain Achieve PCI Compliance

Love’s Travel Stops and Country Stores, a retail travel stop chain with over 210 locations in 34 U.S. states, processes approximately 200,000 credit card transactions on a daily basis. Needing to meet PCI standards, Love’s found in Powertech Encryption for IBM i a product to encrypt credit card numbers in a way that would satisfy PCI compliance auditors. “We need to be able to access credit card...
Article

Secret Capabilities of Robot Schedule Revealed

We recently surveyed our Robot Schedule technical support group for “ah ha!” moments that they’ve helped customers realize over the past few years. These tips from our tech gurus have helped customers automate jobs that needed to check a data area before running, track non-Robot jobs for reporting purposes, and check the status of a file before running a job.