Sidebar

The API Corner: Automating Recovery, Part II

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

Detect Errors when using the QCAPCMD API.

 

In last month's column, "Automating Recovery (or Keeping the Help Desk Out of the Loop)," you saw how to use the Execute Command (QCMDEXC) API to run a CL command and then recover from a variety of possible error situations related to the running of the CL command. Today, we'll look at how to provide similar, though to my thinking improved, recovery using the Process Commands (QCAPCMD) API documented here.

 

Unlike the QCMDEXC API, the QCAPCMD API supports an error code parameter. As you saw in the second article of this series, "Running CL Commands from RPG," the error code parameter enables you to control whether or not escape messages are returned to the RPG program in error situations. If you set the Bytes Provided field of the error code parameter to 0, then escape messages are sent by the API and you effectively have the same level of error-handling capability as you saw with the QCMDEXC API reviewed last month. If, however, you set the Bytes Provided field to a non-zero value, then you pick up some ease-of-use characteristics that I find attractive. Here is a sample program patterned after the QCMDEXC example used last month, but using a non-zero error code Bytes Provided value when calling the QCAPCMD API.

 

h dftactgrp(*no)                                                  

                                                                  

dRunCmd           pr                  extpgm('QCAPCMD')           

d SourceCmd                  65535    const options(*varsize)     

d LenSrcCmd                     10i 0 const                       

d CtlBlk                     65535    const options(*varsize)     

d LenCtlBlk                     10i 0 const                       

d CtlBlkFmt                      8    const                       

d ChgCmd                         1    options(*varsize)           

d LenAvlChgCmd                  10i 0 const                       

d LenRtnChgCmd                  10i 0                             

d QUSEC                               likeds(QUSEC)               

                                                                  

dSndMsg           pr                  extpgm('QSYS/QMHSNDPM')     

d MsgID                          7    const                       

d QualMsgF                      20    const                       

d MsgDta                     65535    const options(*varsize)     

d LenMsgDta                     10i 0 const                        

d MsgType                       10    const                       

d CSE                        65535    const options(*varsize)     

d CSECtr                        10i 0 const                       

d MsgKey                         4                                 

d QUSEC                               likeds(QUSEC)               

d LenCSE                        10i 0 const options(*nopass)      

d CSEQual                       20    const options(*nopass)      

d DSPWaitTime                   10i 0 const options(*nopass)      

d CSEType                       10    const options(*nopass)      

d CCSID                         10i 0 const options(*nopass)      

                                                                  

dMaxInt           pr            10i 0                             

d Input1                        10i 0 const                       

d Input2                        10i 0 const                       

                                                                   

 /copy qsysinc/qrpglesrc,qcapcmd                                  

 /copy qsysinc/qrpglesrc,qusec                                    

                                                                  

dPSDS            sds           429    qualified                   

d JobUsr                254    263                                  

                                                                    

dErrCde           ds                  qualified                     

d Common                              likeds(QUSEC)                 

d ErrMsgDta                    512                                  

                                                                    

dCmd              s            512                                   

dMsgKey           s              4                                  

dNotUsedChr       s              1                                  

dNotUsedInt       s             10i 0                               

                                                                     

 /free                                                              

                                                                    

  QUSBPRV = 0;                                                      

  ErrCde.Common.QUSBPRV = %size(ErrCde);                            

                                                                    

  QCAP0100 = *loval; // initialize input structure to nulls         

  QCACMDPT = 0;      // Run command                                   

  QCABCSDH = '0';    // Ignore DBCS                                  

  QCAPA = '0';       // Do not prompt command                        

  QCACMDSS = '0';    // User i5/OS syntax                            

                                                                      

  Cmd = 'CLRPFM FILE(SOMEFILE) MBR(' + PSDS.JobUsr + ')';            

  RunCmd(Cmd :%len(%trim(Cmd)) :QCAP0100 :%size(QCAP0100)            

         :'CPOP0100' :NotUsedChr :0 :NotUsedInt :ErrCde);             

  if ErrCde.Common.QUSBAVL > 0;                                      

     select;                                                         

        when ErrCde.Common.QUSEI = 'CPF3141';                        

             Cmd = 'ADDPFM FILE(SOMEFILE) MBR(' + PSDS.JobUsr + ')'; 

             RunCmd(Cmd :%len(%trim(Cmd)) :QCAP0100 :%size(QCAP0100) 

                    :'CPOP0100' :NotUsedChr :0 :NotUsedInt :ErrCde); 

             if ErrCde.Common.QUSBAVL > 0;                           

                SndMsg(ErrCde.Common.QUSEI :'QCPFMSG   *LIBL'        

                       :ErrCde.ErrMsgDta                             

                       :MaxInt(0 :ErrCde.Common.QUSBAVL - %size(QUSEC))

                       :'*DIAG' :'*PGMBDY' :1 :MsgKey :QUSEC);      

                SndMsg('ESC0001' :'OURMSGS   *LIBL' :' ' :0           

                       :'*ESCAPE' :'*PGMBDY' :1 :MsgKey :QUSEC);      

             endif;                                                   

                                                                      

        when ErrCde.Common.QUSEI = 'CPF3142';                         

             Cmd = 'CRTPF FILE(SOMEFILE) MBR(' + PSDS.JobUsr +        

                   ') MAXMBRS(*NOMAX) OPTION(*NOSRC *NOLIST)';        

             RunCmd(Cmd :%len(%trim(Cmd)) :QCAP0100 :%size(QCAP0100)  

                    :'CPOP0100' :NotUsedChr :0 :NotUsedInt :ErrCde);  

             if ErrCde.Common.QUSBAVL > 0;                            

                SndMsg(ErrCde.Common.QUSEI :'QCPFMSG   *LIBL'         

                       :ErrCde.ErrMsgDta                              

                       :MaxInt(0 :ErrCde.Common.QUSBAVL - %size(QUSEC))

                       :'*DIAG' :'*PGMBDY' :1 :MsgKey :QUSEC);      

                SndMsg('ESC0001' :'OURMSGS   *LIBL' :' ' :0           

                       :'*ESCAPE' :'*PGMBDY' :1 :MsgKey :QUSEC);      

             endif;                                                    

                                                                      

        other;                                                        

             SndMsg(ErrCde.Common.QUSEI :'QCPFMSG   *LIBL'            

                    :ErrCde.ErrMsgDta                                 

                    :MaxInt(0 :ErrCde.Common.QUSBAVL - %size(QUSEC))  

                    :'*DIAG' :'*PGMBDY' :1 :MsgKey :QUSEC);         

             SndMsg('ESC0001' :'OURMSGS   *LIBL' :' ' :0               

                    :'*ESCAPE' :'*PGMBDY' :1 :MsgKey :QUSEC);         

     endsl;                                                           

  endif;                                                              

                                                                       

  // Do further processing                                            

                                                                      

  *inlr = *on;                                                         

  return;                                                             

                                                            

 /end-free                                                  

                                                             

pMaxInt           b                                         

                                                            

dMaxInt           pi            10i 0                       

d Input1                        10i 0 const                 

d Input2                        10i 0 const                 

                                                            

 /free                                                      

                                                            

  if Input1 > Input2;                                       

     return Input1;                                         

  else;                                                     

     return Input2;                                         

  endif;                                                     

                                                            

 /end-free             

                       

pMaxInt           e    

 

Similar to last month's QCMDEXC example program, this program starts by prototyping the QCAPCMD and QMHSNDPM APIs. The current program, however, does not prototype the QMHRMVPM API (used in last month's example program in order to leave a "clean" job log when recovering from an error situation). There will not be any error messages to remove from the job log when this month's program encounters an error that it can recover from as the QCAPCMD API would not have sent the message in the first place (due to a non-zero Bytes Provided value in the error code structure).

 

Following the prototype for QMHSNDPM, there is, however, a new prototype for an internal function named MaxInt. This function is not actually required in the current program, but I find it handy for a reason that we'll get into later in this article.

 

The program then includes (or copies) the QSYSINC-provided header files QCAPCMD and QUSEC. These header files provide the IBM-supplied definitions for the structures associated with the QCAPCMD API and the API error code parameter, respectively. As with the QCMDEXC example program, the current program defines the Program Status Data Structure in order to access the current user's name. Unlike with the QCMDEXC example, though, the PSDS subfield MsgID is not defined. The message ID of any error detected by the QCAPCMD API will instead be accessed using the error code Exception ID (QUSEI) subfield of the error code parameter (which is defined within the QUSEC header file). Using the QUSEC error code structure defined by the QUSEC header file, the program then defines the data structure ErrCde using the base IBM-provided definition of the error code parameter with an additional 512 bytes allocated for error message replacement data (ErrMsgDta). It is this ErrCde data structure that the program will use as an error code parameter when calling the QCAPCMD API and not wanting escape messages to be sent in the case of error situations.

 

As with the previous QCMDEXC example, the program also defines the two standalone fields Cmd and MsgKey. The program also defines two new standalone fields, NotUsedChr and NotUsedInt. These fields are used to represent QCAPCMD API character and integer parameters, respectively. These fields are used as placeholders for parameters that, while not being utilizing per se, are defined as outputs of the API and therefore cannot be specified as constants on the API call.

 

With the data definitions out of the way, the program initializes the Bytes Provided field of the QUSEC and ErrCde error code data structures to 0 and 528, respectively. The QUSEC error code data structure will be used when calling system APIs and where any failure encountered by the API would generally indicate a situation outside the control of the program. For instance, a failure when calling the QMHSNDPM API to send an error message (assuming appropriate testing of the call parameters during development) would generally indicate a failure beyond the application program's control. Also initialized are various control fields of the QCAPCMD QCAP0100 data structure used with format CPOP0100. The initializations essentially indicate that we want to run a CL command.

 

As with the previous QCMDEXC example program, the current program now formats and attempts to run a CLRPFM command. In this example, though, the QCAPCMD API is used to run the command, and the error code parameter passed to the API is the ErrCde data structure. With the preceding explanations out of the way, we have now set the environment for the meat of this article: namely, recovering for errors when running a CL command.

 

If an error is encountered in running the CLRPFM command, then the Bytes Available field (QUSBAVL) of the ErrCde data structure will be returned with a positive value, and the program will enter a Select group to determine which error occurred. In the previous program using QCMDEXC, the logic related to handling errors such as CPF3141 and CPF3142 included removing the message from the job log. With QCAPCMD and an error code with a non-zero Bytes Provided field, there is no need to remove the message as it was never sent by the API (see above). Using QCAPCMD and the ErrCde error code data structure, the recovery for these error situations is to simply select and run the appropriate CL command given the error message ID returned in ErrCde.Common.QUSEI. If this attempt to recover from the error succeeds—for instance, ErrCde.Common.QUSBAVL is 0 following the ADDPFM recovery action when CPF3141 is returned from the CLRPFM command—then the program simply continues on to its "further processing." No additional work, such as removing the CPF3141, is needed.

 

There is, of course, a downside to the QCAPCMD API not sending error messages—namely, that the message is not in the job log if our recovery action is unsuccessful (for instance, the ADDPFM fails when attempting to recover from CPF3141) or if the error encountered is one that the program is unprepared to handle (for instance, the CLRPFM command fails with a CPF3134 – Referential constraint error). In this case, the program needs to send the CPF message as a diagnostic, followed by the escape message ESC0001. Fortunately, this is very easy as we know the error message ID from the ErrCde subfield QUSEI and we have the message replacement data readily available in the ErrCde subfield ErrMsgDta. To send the necessary messages to the job log, we can use the QMHSNDPM API as shown in the sample program.

 

It's in the sending of the CPF error messages that the program uses the MaxInt function mentioned previously. Strictly speaking, MaxInt is not needed for the example program. In an error situation when running the CLRPFM, ADDPFM, or CRTPF commands, the program could simply use the following QMHSNDM API call to send the appropriate CPF error message.

 

      SndMsg(ErrCde.Common.QUSEI :'QCPFMSG   *LIBL'          

             :ErrCde.ErrMsgDta                              

             :ErrCde.Common.QUSBAVL - %size(QUSEC)

             :'*DIAG' :'*PGMBDY' :1 :MsgKey :QUSEC);      

 

In the preceding call, the value of the fourth parameter when using the QMHSNDM API, Length of message data, can be determined by taking the number of bytes available in the ErrCde data structure (ErrCde.Common.QUSBAVL) and then subtracting the size of the QUSEC Common subfield of ErrCde. This will leave us with the size of the message data associated with the error message being sent. The size of the QUSEC data structure is 16, so we effectively have (ErrCde.Common.QUSBAVL – 16). This, however, only works because all of the error messages returned by CLRPFM, ADDPFM, and CRTPF return message replacement data.

 

There are some CL commands (and some APIs, ignoring QCAPCMD for the moment) that can return error message information in the ErrCde parameter and the message does not utilize message replacement data. In the situation of no message replacement data, the value of ErrCde.Common.QUSBAVL is 15 (due to the 16th byte of QUSEC being reserved and not representing any meaningful error-related data being returned). If we then use the preceding QMHSNDM API call, we'll end up with the fourth parameter being set to the value -1 as we will be subtracting 16 (the size of QUSEC) from 15 (the number of bytes available in the ErrCde data structure). This negative value will result in a runtime error when calling the QMHSNDM API. As I prefer to write generic code that can be widely utilized (as opposed to using one way of calculating the Length of message data for some API calls and other ways for other API calls), I use the MaxInt function to set the fourth parameter to the value of 0 when the calculation (ErrCde.Common.QUSBAVL - %size(QUSEC)) returns a negative value. Then, I can simply copy this QMHSNDM API call logic to any program I'm writing.

 

At this point, I should also mention that even the QMHSNDM call shown in the example program is not what I actually use in my application development environment. Though it's not directly relevant to this article, I have written a set of functions that are used by my applications and are what I really code to in my application programs. One function, for instance, will simply send whatever system message is currently found in the ErrCde data structure as a diagnostic message to the current program boundary. So, in my program, I can simply code SendDiag(). It's then the SendDiag function that utilizes the MaxInt function to set the value of the fourth parameter when calling the QMHSNDM API, sets the fifth parameter (Message type) to *DIAG, determines what message file really stores the message ID value found in ErrCde.Common.QUSEI (you may notice that the example program has hardcoded QCPFMSG, which may not be the case for all commands and API calls), etc. For my application-oriented diagnostic messages, I have another function where I can pass parameters defining what error message ID I want sent, the data structure containing the replacement data I want sent with the message, and the length of the data within the data structure. In this way, I generalize the sending of diagnostic messages within my application programs.

 

Returning to the main topic of this article, error recovery, the ErrMsgDta subfield of the ErrCde data structure also provides some additional "free" information when compared to recovering from an error using the QCMDEXC API. When running the CLRPFM command, you may have noticed that the file SOMEFILE is not library-qualified, so the CLRPFM command is, by default, using the jobs library list to locate SOMEFILE. What if you wanted to know the library SOMEFILE was located in when error message CPF3141 is encountered?

 

Using QCMDEXC, you do have access to the first-level text of the message in the PSDS, but unfortunately the library name is in the second-level text, not the first-level text. And even if the library name was in the first-level text, the PSDS returns the message with the message replacement data merged into the text of the message, making access to the replacement data extremely error-prone. To access the library name, you will need to call another API in order to receive the error message.

 

With QCAPCMD, the message replacement data is readily available to you. To be able to access error message replacement data in a generic fashion, you can use an approach such as shown below.

 

dErrMsgDtaPtr     s               *   inz(%addr(ErrCde.ErrMsgDta))

                                                                  

dCPF3141          ds                  qualified                   

d                                     based(ErrMsgDtaPtr)         

d File                          10                                

d Member                        10                                

d Library                       10                                

                                                                  

If you know you may need additional information related to an error situation, you can define a based data structure, such as CPF3141 shown above, where the basing pointer is initialized to the address of the ErrMsgDta subfield of the ErrCde data structure. In this case, when error situation CPF3141 is returned and you're using the ErrCde data structure, you can directly access the library name using the variable CPF3141.Library. There is no need for additional API calls, for parsing of the message replacement text, etc. Just directly use the data within your error recovery logic. Admittedly, this example of determining the library used is trivial, but there are many error situations where you need access to additional information that can be found only in the error message replacement data (for instance, reason codes). With the error code parameter provided with QCAPCMD, access to this additional information is a snap.

 

Both the QCMDEXC and the QCAPCMD APIs can be successfully used to run CL commands from an RPG application program. Both of the APIs also provide for recovery from errors encountered when attempting to run CL commands. The choice is yours as to which API you may prefer to use. My preference is QCAPCMD as I find it easier to work with in terms of no "cleanup" in my error recovery when I want to leave a clean job log and much easier access to error-related information. QCAPCMD does, however, when using a non-zero error code Bytes Provided value, mean that the application program needs to send error messages when all attempts to recover from the error fail. To me, calling additional system APIs (sending diagnostic and escape information) in the "hard failure" case is preferable to calling additional APIs (remove messages, receive messages, etc.) in the scenarios where the application program is able to continue functioning.

 

Next month, we will look at error recovery using the API system, a third API that can be used to run CL commands from an RPG application program.

Questions?

In the meantime, if you have any API questions, send them to me at This email address is being protected from spambots. You need JavaScript enabled to view it.. I'll see what I can do about answering your burning questions in future columns.

 

Bruce Vining

Bruce Vining is president and co-founder of Bruce Vining Services, LLC, a firm providing contract programming and consulting services to the System i community. He began his career in 1979 as an IBM Systems Engineer in St. Louis, Missouri, and then transferred to Rochester, Minnesota, in 1985, where he continues to reside. From 1992 until leaving IBM in 2007, Bruce was a member of the System Design Control Group responsible for OS/400 and i5/OS areas such as System APIs, Globalization, and Software Serviceability. He is also the designer of Control Language for Files (CLF).A frequent speaker and writer, Bruce can be reached at bvining@brucevining.com. 


MC Press books written by Bruce Vining available now on the MC Press Bookstore.

IBM System i APIs at Work IBM System i APIs at Work
Leverage the power of APIs with this definitive resource.
List Price $89.95

Now On Sale

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.