Sidebar

Unlocking the KLIST

RPG
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

Composite Keys and Key Lists

So how do you deal with composite keys? Do you use a work field, and move all the pieces in? Or are you somewhat more advanced, using a data structure? Whatever technique you used in the past, you have to learn a new method to work with composite keys in externally described files.

Judging by the queries on the Midrange Computing BBS, and in discussions with newly minted AS/400 programmers, it seems that the area of composite keys, key lists, and the rules for using key lists with RPG operations is confusing. The rules are really very simple, and the flexibility gained by converting to external files and using the new features is well worth the problems you may initially have.

Just What Is a Composite Key?

If you are coming from the System/34 to the AS/400, you may be baffled at the idea of composite, noncontiguous key fields. Even System/36 programmers may not feel that they are on solid ground, since the "alternate index" features arrived relatively late in the game. Also, many System/36 uses of alternate indexes are rather simple. An example is defining an alternate index on the Customer Master over the customer name, rather than the customer number.

The S/36 implementation also imposes some limits on how you define an alternate index, in that you are limited to three noncontiguous fields. That means you have to be careful when designing record formats, so that you can create alternate indexes over all of the fields that you need.

The AS/400, as did the System/38 before it, changed all of the rules, and also made programming quite a bit easier. On those machines, an external file can have any number of fields defined as index fields, as long as they stay within the limit of 120 bytes total. I have never come close to the limit, but I suppose there are some who wish the limit was bigger.

Also, with external files on the database machines, you have many more options for defining each key field. For example, you can define a key field to be in descending, rather than ascending, sequence. This could be useful if you are printing a listing of balances due, or inventory for an 80/20 report. The list of options that you can specify for key fields is quite extensive, and well worth reviewing if you are new to the machine. You may find that programming jobs that used to require tricks or many steps can now be handled as a matter of "definition."

The point is, on the AS/400, you can define different conditions for each field that is part of the key. And that is what a composite key is: two or more fields, from anywhere in the record format, that you want to use to access the file. Please remember that you define keys for external files in the DDS for the file, not on the F-spec in your RPG program. Although the system internally references the key fields in terms of from-to positions, you only have to think of the key fields in terms of the name of the field. Stop worrying about "from" and "to" positions! It's time to let the machine take care of the details that it is concerned with, so that you can deal with things on a higher level.

How Do I Define a Composite Key?

Although defining a composite key is not really within the scope of this article, we will touch upon it briefly. Refer to 1. This depicts the definition of a physical file, with a "primary" key defined within it. Also, a logical file is defined over the physical file, defining an "alternate index," composed of multiple, noncontiguous fields.

Although defining a composite key is not really within the scope of this article, we will touch upon it briefly. Refer to Figure 1. This depicts the definition of a physical file, with a "primary" key defined within it. Also, a logical file is defined over the physical file, defining an "alternate index," composed of multiple, noncontiguous fields.

There is some debate among AS/400 programmers as to the preferred method of defining keys over files. Some say that all keys should be in logical files, and that the physical file should never be keyed. Others maintain that the primary key should be included in the physical file. I have used both methods, and there are reasons to use them both. At this point, I tend to favor the approach of not including keys in the physical file.

Regardless of where you define keys, they are all treated the same within an RPG program. The program must be able to tell the operating system the record that is needed, in terms that the system understands. This means that you must make requests for records accessed by key within the terms that the record was defined. Please read that sentence again, since it summarizes the problems that you will have as you learn how to use keyed external files in your programs.

I Already Know How To Do This!

You may be thinking that you already know how to get at any record you want in a composite key file. If you are a sharp S/36 programmer, you probably create a data structure defining your multiple keys. If you are not quite as experienced, you may use the more laborious MOVEL/MOVE method, of building up little "work fields" until you finally arrive at the key. In either case, these methods won't work with externally-described composite keys, although the data structure people are closer to the new way of doing things.

And just what is this new way? In keeping with the new way of doing things, native RPG includes two new op-codes, KLIST (Key List) and KFLD (Key Fields). Let's look at these op-codes, review how they are used, and figure out why they cause so many problems.

For No Other Purpose

A KLIST is somewhat peculiar. It is used only for accessing a file by key. You use it only on file operations: CHAIN, DELET, READE, REDPE (new), SETGT and SETLL. You can't compare, move, or otherwise use a KLIST. These restrictions underscore the fact that a KLIST is a unique construct within RPG. After all, if you could access a composite key file with the old method of a data structure or a built-up field, then the language would simply let you do that and not need this strange new op-code.

To further add to the strangeness of the KLIST, it can only be coded if it is immediately followed by one or more KFLD statements. And to top it off, the KLIST isn't even executed! I mention this because many programmers innocently include multiple KLISTs in a separate subroutine, and execute that as part of their program initialization. Although this does no harm, it is unnecessary. A KLIST is a "declarative" statement, and is not "executed" in the sense that other RPG op-codes like MOVE and Z-ADD, are executed. Simply including a KLIST anywhere in the source is sufficient; it is "executed," so to speak, when the program is compiled.

Where to place KLISTs is another matter. Some programmers place all KLISTs at the beginning of the program, or within their initialization subroutine. Others place a KLIST immediately before the file access statement that uses the KLIST. I tend to favor the first method, and put all the KLISTs up front. The second method is OK, but breaks down when you use the same KLIST more than once in the program.

A KLIST is named following the rules for field names, even though it can't be used as a field. I start my KLIST names with "@", to distinguish them from other types of fields. You will find it useful to adopt a similar convention for your KLISTs, so that when you see them used, you will know they are KLISTs and not "simple" fields.

What About KFLD?

The other side of the KLIST coin is the KFLD (Key Field), which is really where the misunderstandings creep in. The whole point of a KLIST/KFLD construct is to define a key that you use to retrieve records from a file defined with a composite key access path. The KFLD is the means you use to tell your program to tell the operating system the record that you want.

The rule for defining KFLDs is simple: a KFLD in the same relational position as the composite key field must have the same attributes (character/numeric, length, decimal positions). Please reread that until you understand it. I am astonished at the problems people have with this, since it is a very simple concept. It is practically no work to define a KLIST and the KFLDs that are included with it, since you can work with the listing of the file and copy the definitions right from the listing. For example, refer to 2, which illustrates KLIST/KFLD for the definitions in 1.

The rule for defining KFLDs is simple: a KFLD in the same relational position as the composite key field must have the same attributes (character/numeric, length, decimal positions). Please reread that until you understand it. I am astonished at the problems people have with this, since it is a very simple concept. It is practically no work to define a KLIST and the KFLDs that are included with it, since you can work with the listing of the file and copy the definitions right from the listing. For example, refer to Figure 2, which illustrates KLIST/KFLD for the definitions in Figure 1.

Now, unlike a KLIST name, you can and must move values into the KFLDs before using the KLIST to retrieve records. Apart from the simple restriction of a KFLD not being an array or table name, you can use any field for the KFLD, as long as the attributes are the same as the corresponding field in the file. In practice, I tend to define separate KFLD fields. You can code the length and decimal positions entries on the KFLD statement, so you don't need separate statements to define the KFLDs.

Why define separate fields? Well, I like to have very explicit control over the values in my KLISTs, so I define the fields and move values into them immediately prior to using the KLIST for a file operation. You don't have to use this technique, but be aware that the value used in the KFLD is the "current" value of the field. If you aren't using a field that you explicitly control, the value may not be what you expect.

So Why Can't I Use the Old Way?

At this point, you might wonder why you can't just use the old technique of a data structure or a long field. After all, if a composite key field is 30 bytes long, why not just use a 30 byte field, and move values into the right places?

The problem with that technique is that the operating system demands exact correspondence with key fields, in the order of their appearance. For example, if your 30 byte composite key field comprises fields of length 7, 10, 8, and 5, your first key field must also be length 7. Succeeding key fields must be length 10, 8 and 5. If you try to apply a 30 byte key field to this composite key, you will get horrible compile errors. Your only alternative, of course, is to use the expected technique, which is to define a KLIST made up of KFLDs of the correct attributes.

Now, there's nothing to say that you can't use a data structure to define one of the KFLDs. For example, you might want to break up your 10 byte key field into two or three pieces. There's no problem with that, as long as you use the complete 10 byte key field in the key list. The system doesn't care how you arrive at a value for the key field, it only wants you to use the same attributes as those defined for the corresponding key in the file.

This Seems Like a Lot of Work...

And it is. If there were no greater value than getting at a record, the whole KLIST/KFLD technique would create a massive outcry of dissatisfaction. But in fact, you can use some really neat programming tricks with the KLIST/KFLD structure. The tricks involve using partial keys, which is another ramification of composite keys. Now understand, a "partial key" in this context is not the same as using "part of a key." For example, most of us have had the pleasure of explaining to a user that with our nifty name-search program, they don't have to key in the whole last name, but only the first few characters, and the program will display last names that are in the vicinity of their search request. The programming that you used in that technique is the "part of a key" technique, where you take however much was entered, SETLL with it, and read forward from there.

The partial key technique goes quite a bit further than that, and is extremely useful for a very common data processing task: you can use partial keys to retrieve "sets" of data, with much less programming than might otherwise be necessary.

For example, assume you have an order file; a key might be customer number, order number, and line item number. Using partial keys, you can retrieve all orders for a customer, or all line items for a particular order for a customer. Furthermore, you can define KLIST/KFLD constructs within your program to accommodate these partial keys as shown in 3.

For example, assume you have an order file; a key might be customer number, order number, and line item number. Using partial keys, you can retrieve all orders for a customer, or all line items for a particular order for a customer. Furthermore, you can define KLIST/KFLD constructs within your program to accommodate these partial keys as shown in Figure 3.

A particularly useful op-code for this situation is READE (Read Equal). I was used to the S/38 implementation of this long before the S/36 version became available. I have always felt that the S/36 version was practically useless, because it didn't allow usage of the partial key technique. For example, if the order file is defined with keys of customer, order and order line number, you can use the loop construct shown in 4 to read through all orders for a customer. The indicator on the READE operation is set on when a record is retrieved that is not for the same customer (or at end of file). Compare this with the old RPG II technique of using the simple READ operation and comparing the fields to see if you still are within the same customer.

A particularly useful op-code for this situation is READE (Read Equal). I was used to the S/38 implementation of this long before the S/36 version became available. I have always felt that the S/36 version was practically useless, because it didn't allow usage of the partial key technique. For example, if the order file is defined with keys of customer, order and order line number, you can use the loop construct shown in Figure 4 to read through all orders for a customer. The indicator on the READE operation is set on when a record is retrieved that is not for the same customer (or at end of file). Compare this with the old RPG II technique of using the simple READ operation and comparing the fields to see if you still are within the same customer.

You can extend the technique "from left to right" for as many key fields as you like. For example, 5 shows how you would define and use a construct to retrieve all line items for a particular customer order.

You can extend the technique "from left to right" for as many key fields as you like. For example, Figure 5 shows how you would define and use a construct to retrieve all line items for a particular customer order.

You should review all of the file op-codes that use a key field (KLIST) in factor 1 (CHAIN, DELETE, READE, SETGT, and SETLL). In situations where you use a partial key field, the first record meeting the conditions of that partial key is used. You should pay particular attention to the SETLL and SETGT operations, and also be aware of the special values *LOVAL and *HIVAL.

Watch Out For These

There are some other things you should know about defining KLIST/KFLDs and using composite keys. First, when you use an externally defined file in your program, the compiler prints the key fields immediately after the end of the source. So if you are getting compile errors about key field disagreements, go directly to that part of the listing and compare what you see with what you coded. If the key fields are not at all what you think they should be, then you should go back to the F-spec, and see from what library the compiler pulled in the file definition. If you have files named the same in different libraries, and the key fields are defined differently, then you might be creating problems for yourself when you compile or run the program. You have to be careful, even if the program compiled successfully. When you run the program, the file that is opened must have key fields that agree with what you compiled. Don't try to pull any tricks here, since you won't get very far: you'll get a rather exotic message, about key fields not having the same attributes as expected.

Another area where you'll have to be careful doesn't concern key fields per se, but has to do with the files you use. You have to be aware of the access path rules that are in effect for the file. For example, if the access path excludes certain records, then no amount of fiddling with key fields in your program will retrieve those records. You will simply get "record not found" indications. I mention this because many newcomers spend fruitless hours looking for problems in their programs, and blaming faulty KLISTs, when in fact the problem is completely independent of the program. This is a new concept to S/36 programmers, since alternate index files did not have any select/omit criteria associated with the alternate index. If you get really stuck and think there is a bug with an executing program, use the WRKJOB (Work with Job) command and display the open files and file overrides. You can then refer to the definitions of the open files and determine if the records that you want are in the access path. Remember, if the records aren't in the access path, they aren't in the file, as far as your program is concerned.

A final consideration is what do you do if the access path is made up of only one key field? Should you define a KLIST of a single KFLD, or just use an otherwise available field to access the file? For example, see 6. There is really no great debate favoring either technique, and it will depend upon your programming style. Like a cat at the doorstep, I can't decide either, and have used each technique about half the time. At this point I tend to favor the single KFLD construct, because that way, I am treating all file accesses consistently.

A final consideration is what do you do if the access path is made up of only one key field? Should you define a KLIST of a single KFLD, or just use an otherwise available field to access the file? For example, see Figure 6. There is really no great debate favoring either technique, and it will depend upon your programming style. Like a cat at the doorstep, I can't decide either, and have used each technique about half the time. At this point I tend to favor the single KFLD construct, because that way, I am treating all file accesses consistently.

What You Should Do

If you are just getting started with external files, you should sit down with some listings of your files and make up sample key fields. Pick some of your files that have composite key fields, and sketch out the KLIST/KFLD constructs that you might use. Remember that each KFLD must exactly match the corresponding key field in the file.

If you will study the requirements before getting into coding, you will see that using composite key fields is really a simple concept. But with the simplicity comes programming power that used to involve tedious moves, compares, and other non-intuitive operations. The whole point of RPG/400 is to make your programming life simpler, more powerful, and to the point, and you will find the KLIST/KFLD construct as the most appropriate method of


Unlocking the KLIST

Figure 1 Physical file and logical with composite key

 Physical: A R PFFILE A FIELD1 5 0 A FIELD2 10 A FIELD3 8 A FIELD4 8 A K FIELD1 Logical: A R PFFILE PFILE(PHYFILE) A K FIELD2 A K FIELD4 A K FIELD1 
Unlocking the KLIST

Figure 2 KLISTs for Figure 1

 KLISTs for Figure 1 C @KEY KLIST C KFLD @KF1 50 C* C @KEY2 KLIST C KFLD @KF2 10 C KFLD @KF4 8 C KFLD @KF1 
Unlocking the KLIST

Figure 3 Defining partial KLISTs

 Defining Partial KLISTs C @ORDKY KLIST C KFLD @CUSNO C KFLD @ORDNO C KFLD @ORDSQ C* C @ORDK1 KLIST C KFLD @CUSNO C KFLD @ORDNO C* C @ORDK2 KLIST C KFLD @CUSNO 
Unlocking the KLIST

Figure 4 Get all orders for a customer

 Get All Orders for a Customer C @ORDK2 SETLLORDERS C* C *IN99 DOUEQ'1' C @ORDK2 READEORDERS 99 ----EQ (NE to Key) C *IN99 IFEQ '0' C ... (various statements) 
Unlocking the KLIST

Figure 5 Get all line items for an order

 Get All Line Items for an Order C @ORDK1 SETLLORDERS C* C *IN99 DOUEQ'1' C @ORDK1 READEORDERS 99 ----EQ (NE to Key) C *IN99 IFEQ '0' C* ... (various statements) 
Unlocking the KLIST

Figure 6 Only one key field

 Only One Key Field C @ORDK2 KLIST C KFLD @CUSNO C* C @ORDK2 CHAINCUSMAS 99 HI---- C* C CUSNO CHAINCUSMAS 99 HI---- 
BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

RESOURCE CENTER

  • WHITE PAPERS

  • WEBCAST

  • TRIAL SOFTWARE

  • Mobile Computing and the IBM i

    SB ASNA PPL 5450Mobile computing is rapidly maturing into a solid platform for delivering enterprise applications. Many IBM i shops today are realizing that integrating their IBM i with mobile applications is the fast path to improved business workflows, better customer relations, and more responsive business reporting.

    This ASNA whitepaper takes a look at mobile computing for the IBM i. It discusses the different ways mobile applications may be used within the enterprise and how ASNA products solve the challenges mobile presents. It also presents the case that you already have the mobile programming team your projects need: that team is your existing RPG development team!

    Get your copy today!

  • Automate IBM i Operations using Wireless Devices

    DDL SystemsDownload the technical whitepaper on MANAGING YOUR IBM i WIRELESSLY and (optionally) register to download an absolutely FREE software trail. This whitepaper provides an in-depth review of the native IBM i technology and ACO MONITOR's advanced two-way messaging features to remotely manage your IBM i while in or away from the office. Notify on-duty personnel of system events and remotely respond to complex problems (via your Smartphone) before they become critical-24/7. Problem solved!

    Order your copy here.

  • DR Strategy Guide from Maxava: Brand New Edition - now fully updated to include Cloud!

    SB Maxava PPL 5476PRACTICAL TOOLS TO IMPLEMENT DISASTER RECOVERY IN YOUR IBM i ENVIRONMENT

    CLOUD VS. ON-PREMISE?
    - COMPREHENSIVE CHECKLISTS
    - RISK COST CALCULATIONS
    - BUSINESS CASE FRAMEWORK
    - DR SOLUTIONS OVERVIEW
    - RFP BUILDER
    Download your free copy of DR Strategy Guide for IBM i from Maxava today.

     

  • 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!

     

  • 2020 IBM i Marketplace Survey Results

    HelpSystems

    This year marks the sixth edition of the popular IBM i Marketplace Survey Results. Each year, HelpSystems sets out to gather data about how businesses use the IBM i platform and the IT initiatives it supports. Year over year, the survey has begun to reveal long-term trends that give insight into the future of this trusted technology.

    More than 500 IBM i users from around the globe participated in this year’s survey, and we’re so happy to share the results with you. We hope you’ll find the information interesting and useful as you evaluate your own IT projects.

  • AIX Security Basics eCourse

    Core Security

    With so many organizations depending on AIX day to day, ensuring proper security and configuration is critical to ensure the safety of your environment. Don’t let common threats put your critical AIX servers at risk. Avoid simple mistakes and start to build a long-term plan with this AIX Security eCourse. Enroll today to get easy to follow instructions on topics like:

    • Removing extraneous files
    • Patching systems efficiently
    • Setting and validating permissions
    • Managing service considerations
    • Getting overall visibility into your networks

     

  • 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

    HelpSystemsIT 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

     

  • IBM i Resources Retiring?

    SB HelpSystems WC GenericLet’s face it: IBM i experts and RPG programmers are retiring from the workforce. Are you prepared to handle their departure?
    Our panel of IBM i experts—Chuck Losinski, Robin Tatam, Richard Schoen, and Tom Huntington—will outline strategies that allow your company to cope with IBM i skills depletion by adopting these strategies that allow you to get the job done without deep expertise on the OS:
    - Automate IBM i processes
    - Use managed services to help fill the gaps
    - Secure the system against data loss and viruses
    The strategies you discover in this webinar will help you ensure that your system of record—your IBM i—continues to deliver a powerful business advantage, even as staff retires.

     

  • Backup and Recovery Considerations for Security Data and Encrypted Backups

    SB PowerTech WC GenericSecurity expert Carol Woodbury is joined by Debbie Saugen. Debbie is an expert on IBM i backup and recovery, disaster recovery, and high availability, helping IBM i shops build and implement effective business continuity plans.
    In today’s business climate, business continuity is more important than ever. But 83 percent of organizations are not totally confident in their backup strategy.
    During this webinar, Carol and Debbie discuss the importance of a good backup plan, how to ensure you’re backing up your security information, and your options for encrypted back-ups.

  • Profound.js: The Agile Approach to Legacy Modernization

    SB Profound WC GenericIn this presentation, Alex Roytman and Liam Allan will unveil a completely new and unique way to modernize your legacy applications. Learn how Agile Modernization:
    - Uses the power of Node.js in place of costly system re-writes and migrations
    - Enables you to modernize legacy systems in an iterative, low-risk manner
    - Makes it easier to hire developers for your modernization efforts
    - Integrates with Profound UI (GUI modernization) for a seamless, end-to-end legacy modernization solution

     

  • Data Breaches: Is IBM i Really at Risk?

    SB PowerTech WC GenericIBM i is known for its security, but this OS could be more vulnerable than you think.
    Although Power Servers often live inside the safety of the perimeter firewall, the risk of suffering a data leak or data corruption remains high.
    Watch noted IBM i security expert Robin Tatam as he discusses common ways that this supposedly “secure” operating system may actually be vulnerable and who the culprits might be.

    Watch the webinar today!

     

  • Easy Mobile Development

    SB Profound WC GenericWatch this on-demand webinar and learn how to rapidly and easily deploy mobile apps to your organization – even when working with legacy RPG code! IBM Champion Scott Klement will demonstrate how to:
    - Develop RPG applications without mobile development experience
    - Deploy secure applications for any mobile device
    - Build one application for all platforms, including Apple and Android
    - Extend the life and reach of your IBM i (aka iSeries, AS400) platform
    You’ll see examples from customers who have used our products and services to deliver the mobile applications of their dreams, faster and easier than they ever thought possible!

     

  • Profound UI: Unlock True Modernization from your IBM i Enterprise

    SB Profound PPL 5491Modern, web-based applications can make your Enterprise more efficient, connected and engaged. This session will demonstrate how the Profound UI framework is the best and most native way to convert your existing RPG applications and develop new modern applications for your business. Additionally, you will learn how you can address modernization across your Enterprise, including databases and legacy source code, with Profound Logic.

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

    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.

    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).

  • 5 New and Unique Ways to Use the IBM i Audit Journal

    SB HelpSystems ROBOT GenericYou must be asking yourself: am I doing everything I can to protect my organization’s data? Tune in as our panel of IBM i high availability experts discuss:


    - Why companies don’t test role swaps when they know they should
    - Whether high availability in the cloud makes sense for IBM i users
    - Why some organizations don’t have high availability yet
    - How to get high availability up and running at your organization
    - High availability considerations for today’s security concerns

  • Profound.js 2.0: Extend the Power of Node to your IBM i Applications

    SB Profound WC 5541In this Webinar, we'll demonstrate how Profound.js 2.0 enables you to easily adopt Node.js in your business, and to take advantage of the many benefits of Node, including access to a much larger pool of developers for IBM i and access to countless reusable open source code packages on npm (Node Package Manager).
    You will see how Profound.js 2.0 allows you to:

    • Provide RPG-like capabilities for server-side JavaScript.
    • Easily create web and mobile application interfaces for Node on IBM i.
    • Let existing RPG programs call Node.js modules directly, and vice versa.
    • Automatically generate code for Node.js.
    • Automatically converts existing RPGLE code into clean, simplified Node.js code.

    Download and watch today!

     

  • Make Modern Apps You'll Love with Profound UI & Profound.js

    SB Profound WC 5541Whether you have green screens or a drab GUI, your outdated apps can benefit from modern source code, modern GUIs, and modern tools.
    Profound Logic's Alex Roytman and Liam Allan are here to show you how Free-format RPG and Node.js make it possible to deliver applications your whole business will love:

    • Transform legacy RPG code to modern free-format RPG and Node.js
    • Deliver truly modern application interfaces with Profound UI
    • Extend your RPG applications to include Web Services and NPM packages with Node.js

     

  • Accelerating Programmer Productivity with Sequel

    SB_HelpSystems_WC_Generic

    Most business intelligence tools are just that: tools, a means to an end but not an accelerator. Yours could even be slowing you down. But what if your BI tool didn't just give you a platform for query-writing but also improved programmer productivity?
    Watch the recorded webinar to see how Sequel:

    • Makes creating complex results simple
    • Eliminates barriers to data sources
    • Increases flexibility with data usage and distribution

    Accelerated productivity makes everyone happy, from programmer to business user.

  • Business Intelligence is Changing: Make Your Game Plan

    SB_HelpSystems_WC_GenericIt’s time to develop a strategy that will help you meet your informational challenges head-on. Watch the webinar to learn how to set your IT department up for business intelligence success. You’ll learn how the right data access tool will help you:

    • Access IBM i data faster
    • Deliver useful information to executives and business users
    • Empower users with secure data access

    Ready to make your game plan and finally keep up with your data access requests?

     

  • Controlling Insider Threats on IBM i

    SB_HelpSystems_WC_GenericLet’s face facts: servers don’t hack other servers. Despite the avalanche of regulations, news headlines remain chock full of stories about data breaches, all initiated by insiders or intruders masquerading as insiders.
    User profiles are often duplicated or restored and are rarely reviewed for the appropriateness of their current configuration. This increases the risk of the profile being able to access data without the intended authority or having privileges that should be reserved for administrators.
    Watch security expert Robin Tatam as he discusses a new approach for onboarding new users on IBM i and best-practices techniques for managing and monitoring activities after they sign on.

  • Don't Just Settle for Query/400...

    SB_HelpSystems_WC_GenericWhile introducing Sequel Data Access, we’ll address common frustrations with Query/400, discuss major data access, distribution trends, and more advanced query tools. Plus, you’ll learn how a tool like Sequel lightens IT’s load by:

    - Accessing real-time data, so you can make real-time decisions
    - Providing run-time prompts, so users can help themselves
    - Delivering instant results in Microsoft Excel and PDF, without the wait
    - Automating the query process with on-demand data, dashboards, and scheduled jobs

  • How to Manage Documents the Easy Way

    SB_HelpSystems_WC_GenericWhat happens when your company depends on an outdated document management strategy?
    Everything is harder.
    You don’t need to stick with status quo anymore.
    Watch the webinar to learn how to put effective document management into practice and:

    • Capture documents faster, instead of wasting everyone’s time
    • Manage documents easily, so you can always find them
    • Distribute documents automatically, and move on to the next task

     

  • Lessons Learned from the AS/400 Breach

    SB_PowerTech_WC_GenericGet actionable info to avoid becoming the next cyberattack victim.
    In “Data breach digest—Scenarios from the field,” Verizon documented an AS/400 security breach. Whether you call it AS/400, iSeries, or IBM i, you now have proof that the system has been breached.
    Watch IBM i security expert Robin Tatam give an insightful discussion of the issues surrounding this specific scenario.
    Robin will also draw on his extensive cybersecurity experience to discuss policies, processes, and configuration details that you can implement to help reduce the risk of your system being the next victim of an attack.

  • Overwhelmed by Operating Systems?

    SB_HelpSystems_WC_GenericIn this 30-minute recorded webinar, our experts demonstrate how you can:

    • Manage multiple platforms from a central location
    • View monitoring results in a single pane of glass on your desktop or mobile device
    • Take advantage of best practice, plug-and-play monitoring templates
    • Create rules to automate daily checks across your entire infrastructure
    • Receive notification if something is wrong or about to go wrong

    This presentation includes a live demo of Network Server Suite.

     

  • Real-Time Disk Monitoring with Robot Monitor

    SB_HelpSystems_WC_GenericYou need to know when IBM i disk space starts to disappear and where it has gone before system performance and productivity start to suffer. Our experts will show you how Robot Monitor can help you pinpoint exactly when your auxiliary storage starts to disappear and why, so you can start taking a proactive approach to disk monitoring and analysis. You’ll also get insight into:

    • The main sources of disk consumption
    • How to monitor temporary storage and QTEMP objects in real time
    • How to monitor objects and libraries in real time and near-real time
    • How to track long-term disk trends

     

     

  • Stop Re-keying Data Between IBM I and Other Applications

    SB_HelpSystems_WC_GenericMany business still depend on RPG for their daily business processes and report generation.Wouldn’t it be nice if you could stop re-keying data between IBM i and other applications? Or if you could stop replicating data and start processing orders faster? Or what if you could automatically extract data from existing reports instead of re-keying? It’s all possible. Watch this webinar to learn about:

    • The data dilemma
    • 3 ways to stop re-keying data
    • Data automation in practice

    Plus, see how HelpSystems data automation software will help you stop re-keying data.

     

  • The Top Five RPG Open Access Myths....BUSTED!

    SB_Profound_WC_GenericWhen it comes to IBM Rational Open Access: RPG Edition, there are still many misconceptions - especially where application modernization is concerned!

    In this Webinar, we'll address some of the biggest myths about RPG Open Access, including:

    • Modernizing with RPG OA requires significant changes to the source code
    • The RPG language is outdated and impractical for modernizing applications
    • Modernizing with RPG OA is the equivalent to "screen scraping"

     

  • Time to Remove the Paper from Your Desk and Become More Efficient

    SB_HelpSystems_WC_GenericToo much paper is wasted. Attempts to locate documents in endless filing cabinets.And distributing documents is expensive and takes up far too much time.
    These are just three common reasons why it might be time for your company to implement a paperless document management system.
    Watch the webinar to learn more and discover how easy it can be to:

    • Capture
    • Manage
    • And distribute documents digitally

     

  • IBM i: It’s Not Just AS/400

    SB_HelpSystems_WC_Generic

    IBM’s Steve Will talks AS/400, POWER9, cognitive systems, and everything in between

    Are there still companies that use AS400? Of course!

    IBM i was built on the same foundation.
    Watch this recorded webinar with IBM i Chief Architect Steve Will and IBM Power Champion Tom Huntington to gain a unique perspective on the direction of this platform, including:

    • IBM i development strategies in progress at IBM
    • Ways that Watson will shake hands with IBM i
    • Key takeaways from the AS/400 days

     

  • Ask the RDi Experts

    SB_HelpSystems_WC_GenericWatch this recording where Jim Buck, Susan Gantner, and Charlie Guarino answered your questions, including:

    • What are the “hidden gems” in RDi that can make me more productive?
    • What makes RDi Debug better than the STRDBG green screen debugger?
    • How can RDi help me find out if I’ve tested all lines of a program?
    • What’s the best way to transition from PDM to RDi?
    • How do I convince my long-term developers to use RDi?

    This is a unique, online opportunity to hear how you can get more out of RDi.

     

  • 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

     

     

  • Inside the Integrated File System (IFS)

    SB_HelpSystems_WC_GenericDuring this webinar, you’ll learn basic tips, helpful tools, and integrated file system commands—including WRKLNK—for managing your IFS directories and Access Client Solutions (ACS). We’ll answer your most pressing IFS questions, including:

    • What is stored inside my IFS directories?
    • How do I monitor the IFS?
    • How do I replicate the IFS or back it up?
    • How do I secure the IFS?

    Understanding what the integrated file system is and how to work with it must be a critical part of your systems management plans for IBM i.

     

  • 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.

  • How to Meet the Newest Encryption Requirements on IBM i

    SB PowerTech WC GenericA growing number of compliance mandates require sensitive data to be encrypted. But what kind of encryption solution will satisfy an auditor and how can you implement encryption on IBM i? Watch this on-demand webinar to find out how to meet today’s most common encryption requirements on IBM i. You’ll also learn:

    • Why disk encryption isn’t enough
    • What sets strong encryption apart from other solutions
    • Important considerations before implementing encryption

     

     

  • 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.

     

     

  • Fight Cyber Threats with IBM i Encryption

    SB PowerTech WC GenericCyber attacks often target mission-critical servers, and those attack strategies are constantly changing. To stay on top of these threats, your cybersecurity strategies must evolve, too. In 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

     

     

     

  • 10 Practical IBM i Security Tips for Surviving Covid-19 and Working From Home

    SB PowerTech WC GenericNow that many organizations have moved to a work from home model, security concerns have risen.

    During this session Carol Woodbury will discuss the issues that the world is currently seeing such as increased malware attacks and then provide practical actions you can take to both monitor and protect your IBM i during this challenging time.

     

  • How to Transfer IBM i Data to Microsoft Excel

    SB_HelpSystems_WC_Generic3 easy ways to get IBM i data into Excel every time
    There’s an easy, more reliable way to import your IBM i data to Excel? It’s called Sequel. During this webinar, our data access experts demonstrate how you can simplify the process of getting data from multiple sources—including Db2 for i—into Excel. Watch to learn how to:

    • Download your IBM i data to Excel in a single step
    • Deliver data to business users in Excel via email or a scheduled job
    • Access IBM i data directly using the Excel add-in in Sequel

    Make 2020 the year you finally see your data clearly, quickly, and securely. Start by giving business users the ability to access crucial business data from IBM i the way they want it—in Microsoft Excel.

     

     

  • HA Alternatives: MIMIX Is Not Your Only Option on IBM i

    SB_HelpSystems_WC_GenericIn this recorded webinar, our experts introduce you to the new HA transition technology available with our Robot HA software. You’ll learn how to:

    • Transition your rules from MIMIX (if you’re happy with them)
    • Simplify your day-to-day activities around high availability
    • Gain back time in your work week
    • Make your CEO happy about reducing IT costs

    Don’t stick with a legacy high availability solution that makes you uncomfortable when transitioning to something better can be simple, safe, and cost-effective.

     

     

  • 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

    SB HelpSystems SC 5413Robot 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

    SB HelpSystems SC 5413Robot 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.

  • ACO MONITOR Manages your IBM i 24/7 and Notifies You When Your IBM i Needs Assistance!

    SB DDL Systems 5429More than a paging system - ACO MONITOR is a complete systems management solution for your Power Systems running IBM i. ACO MONITOR manages your Power System 24/7, uses advanced technology (like two-way messaging) to notify on-duty support personnel, and responds to complex problems before they reach critical status.

    ACO MONITOR is proven technology and is capable of processing thousands of mission-critical events daily. The software is pre-configured, easy to install, scalable, and greatly improves data center efficiency.