Fast XML with RPG IV and SAX

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

In my article, "RPG IV and XML Together," in the November 2000 issue of Midrange Computing, I detailed the steps necessary to create an XML document for a security-policy compliance auditing application and build an XML Document Object Model (DOM) tree as the internal representation of the security policy in memory. I showed how to programmatically navigate that tree to extract recommended policy value settings for security-related system values for the purpose of evaluating those recommendations against values on a target AS/400 and adding that rating to an output XML policy evaluation document for later analysis.

In that article, I briefly touched upon the performance disadvantages of this method when an XML document could be of indeterminate (i.e., large) size. In that instance, DOM would be a poor choice for the application in providing timely reporting. Building the XML DOM tree would consume an extraordinary amount of memory, CPU time, and other system resources. To overcome this limitation to XML document usage, early users (David Megginson and the developers on the xml-dev list) of the XML API invented a method for handling real-world applications called Simple API for XML (SAX) that did not require building an internal tree representation of the document in memory. The primary difference between using DOM and SAX, from a performance standpoint, is that DOM is extremely memory-intensive, while SAX is not.

In this article, I will show you how to use SAX to manipulate documents that cannot be predetermined to be of a fixed size optimal for processing using the XML DOM API, do not require the navigational precision of DOM, or otherwise manifest properties where DOM would not be the appropriate choice to maintain the XML document. In the example provided, you will learn how to use the SAX API to do the following:

  • Parse an XML document containing system-values policy requirements regarding security-related system values.
  • Extract recommended values from the policy document.
  • Rate the current AS/400 system value against recommended system values by using compile-time lookup ratings and add the rating to the document for the appropriate system value.
  • Write the new document back out to a designated AS/400 Integrated File System (AS/400 IFS) directory stream file.

How SAX Does It for You!

The actual mechanics of the SAX API involves a bit of handshaking between a scanner (application code, not the hardware), a parser, and a document handler. The scanner is a core part of the SAX API supplied by the vendor (in this case, IBM alphaWorks). The parser can be supplied by anyone conforming to the SAX API interface requirements but is typically supplied by the vendor supplying the scanner. The document handler is where you come in. The SAX API defines an interface (a set of procedure and method signatures) that must be implemented by the user that wishes to interact with XML documents. IBM alphaWorks has already implemented this interface with its C++ classes and has given you a set of procedures to interact with those classes as defined by the "XML for Procedural Language Interface" for download at Although the Web site calls the interface "XML Interface for RPG," it can be used by ILE C and COBOL as well. You can refer to my article in MC's November issue for more information.

As the scanner passes through an XML document, the scanner uses established callback events (defined by the XMLDocumentHandler interface) to pass data to the parser. The SAX API gives you access to XML document information by allowing you to register your interest in a set type of events and establishing procedures in your application that the SAX API can call back when the registered event is encountered by the document-scanning process. Data for those events are passed to the user application procedure defined (and registered) to handle the event as the parser passes the related node type. In the next section, I will show you how easy it is to use SAX to read in a large XML document and to create a new and larger XML document as output.

SAX in 21 Minutes and 10 Easy Steps

Whether your appreciation of SAX takes 21 minutes or not, I believe you will enjoy learning that SAX is easier than DOM. However, before you get into the example application, you need to review and understand some requisite details about the example.

FIGURE 1: DTD for Security Auditing Policy Recommendations & sample document.

The document type definition (DTD) shown in Figure 1 shows the expected format of the incoming XML security-policy source document that I use in my demonstrative SAX parsing program (SEC0002RS) and a sample XML document using that format as presented in an XML-enabled browser. Note the document can have either a single value or a range of recommended values.

FIGURE 2: DTD for Security Auditing Policy Evaluation Rating.

The DTD shown in Figure 2 shows the expected format of the new XML document (and a sample) that will be created as output by using callback events from the SAX parser. You can refer to my November 2000 article if you require a refresher on DTDs. Next, I will lead you through a 10-step process to write your own SAX parsing program.

Step 1: Set a Pointer to DOM Exceptions Feedback Area

The first step in creating an XML document with SAX is to get the pointer (Figure 3, Section D) to the Qxml_DOMExcData data structure. This data structure is defined in QXML4PR310 headers provided in the alphaWorks download and contains feedback information about the success or failure of SAX API calls. You must pass the pointer along to the QxmlInit function as shown in Figure 3, Section E before any SAX functions are called. While you will be using the SAX API to parse the incoming XML document, some high-level parsing errors are reported in the DOM exception data structure. To get more granular in your error handling, you will want to use the SAX error-handler interface that I will present later.

FIGURE 3: Using SAX to parse a large XML document.

Proper error handling can only be ensured by checking the return code (Qxml_DOMRtnCod) after a SAX API method executes and by taking appropriate action when an error occurs. A list of what each return code means is contained in the QxmlPR4310 copy member defined as integer constants.

Step 2: Create a New Instance of a SAX Parser

Next, you need to create an instance of the underlying SAX parser with the statement:

Eval SAXParse@ = QxmlSAXParser_new

This procedure takes no arguments and returns a pointer to the SAX parser instance just created. The parser instance is used to register callback events, set the related callbacks to application document and error handler procedures, and send the source input XML file to the parser pointed to by SAXParse@. This instance creation is presented in Figure 3, Section F.

Step 3: Set the Parser Validation Mode

In this step, the parser validation mode is set. Validation is the process of ensuring the format defined by the XML document type (and specified in the "" tag) is observed by the accompanying XML document details. In the exercise presented in this article, I assume a non-validating parser will be used. However, if you wish to implement the validating version, the DTDs and sample validation code are included in the downloadable source for this article.

CallP QxmlSAXParser_setDoValidation( pointerToSAXParser: validationMode)

To set the validation mode, all that is required is to pass two arguments to the QxmlSAXParser_setDoValidation procedure. The first argument is the pointer to the SAX parser instance you created in Step 1. The second argument is an integer value of zero for non-validating and one for the validating parser. This is illustrated in Figure 3, Section G.

Step 4: Create a Document-Handler Instance for the Current Parser

Next, create an instance of an underlying document handler that will use the pointers to callback procedures (discussed shortly), shown in Figure 3, Section B in the example program, to respond to SAX events.

Eval DocHndlr@ = QxmlDocumentHandler_new

To accomplish this, call the QxmlDocumentHandler_new procedure that takes no arguments and returns a pointer (DocHndlr@) to the document handler, as shown in Figure 3, Section H. You will use this pointer to register callback events and related procedures.

Step 5: Create an Error-Handler Instance for the Current Parser

Next, you will create an instance of an underlying error handler that will use the pointers to callback procedures (discussed shortly), shown in Figure 3, Section B in the example program, to respond to SAX exception events.

Eval ErrHndlr@ = QxmlErrorHandler_new

To accomplish this, call the QxmlErrorHandler_new procedure that takes no arguments and returns a pointer (ErrHndlr@) to the error handler, as shown in Figure 3, Section I. You will use this pointer to register what procedure in your application handles each of the three types of SAX error events.

Step 6: Connect the Document Handler to the Current Parser

During this step, you will establish a connection between the parser instance created in Step 2 and the document-handler instance created in Step 4.

CallP QxmlSAXParser_setDocumentHandler

When the parser, pointed to by the first argument, gets a document event for which a procedure has been registered, the parser uses the pointer in argument 2 to find the document handler and get a pointer to the callback procedure in the application that handles that event. The code in the sample application to set the document handler is shown in Figure 3, Section H.

Step 7: Connect the Error Handler to Parser

This step is when you will establish a connection between the parser instance created in Step 2 and the instance of the error handler created in Step 5.

CallP QxmlSAXParser_setErrorHandler

When the parser, pointed to by argument 1, gets an error event for which a procedure has been registered, the parser uses the pointer in argument 2 to find the error handler and get a pointer to the callback procedure in the application that handles that error type event. The code in the sample application to set the error handler is shown in Figure 3, Section I.

Step 8: Set Callback Procedures Each of Three Error Events

The error handler, created in Step 5 and connected to the parser in Step 7, will deal with each of the following exception events:

  • Qxml_WARNINGHNDLR = warning
  • Qxml_ERRORHNDLR = error
  • Qxml_FATALERRORHNDLR = fatalError

To delegate handling for each error type event to user application procedures, the following procedure is called to establish the procedure to be called in the application in the event the related error occurs.

CallP QxmlErrorHandler_setCallback

The QxmlErrorHandler_setCallback procedure is called once for each of the three error types indicated above to establish a procedure in your application that will handle warnings, errors, and fatal-error conditions. You can supply three different procedures or use the same procedure to handle all three types. If you use a common procedure to handle all error events, you will have to interrogate the DOM and SAX exception data structures to determine the severity and nature of the exception. The error callback procedures must conform to the procedure interface defined by the prototypes shown in Figure 3, Section C and are passed only a pointer to the error string. The QxmlErrorHandler_setCallback procedure takes the following:

  • A pointer to the error handler in the first argument.
  • One of the three numeric literal names above (i.e., Qxml_WARNINGHNDLR, Qxml_ERRORHNDLR, or Qxml_FATALERRORHNDLR) representing the related numeric constants that indicate the error type for which the callback is being set as the second argument.
  • A pointer to the callback procedure in your application that will handle this error event type as the last argument.

    In the sample application, this step is done in Figure 3, Section O.

Step 9: Set the Callback Procedure for Each Required SAX Event

Next, you must set a callback to a procedure in your application for each SAX event you want to respond to.

CallP QxmlDocumentHandler_setCallback

FIGURE 4: Table associating call event numeric literals with constant values in QXML4PR310 source member.

The QxmlDocumentHandler_setCallback procedure is called once for each SAX event you wish to handle as identified in Figure 4 by the numeric literal that translates to the proper numeric constant identifier for the event type. This must be a different procedure for each event type you wish to monitor and must accommodate the procedure interface requirements for the event type, as shown in Figure 5 and illustrated in Figure 3, Section A. This procedure takes the following:

  • A pointer to the document handler in the first argument.
  • One of the nine numeric literal names above representing the related numeric constants that indicate the document event type for which the callback is being set as the second argument. A pointer to the callback procedure in your application that will
  • handle this document event type as the last argument.

In the sample application, this is done in Figure 3, Section J for the start- and end-document events, Section K for the start- and end-element events, Section L for the characters event, Section M for the processing instructions event, and Section N for the ignorable whitespace event.

FIGURE 5: Interface for callback procedures.

Step 10: Parse the XML Document Using a SAX Parser

Finally, to start the parsing process, your application must call the QxmlSAXParser_parse_SystemId procedure:

CallP QxmlSAXParser_parse_SystemId

This procedure initiates the parsing process, and control is turned over to the parser pointed to in the first argument (SAXParse@). The second argument identifies a pointer (XmlFile@) to the source input XML document to be parsed. The third argument identifies the character-encoding scheme (Qxml_CCSID37) for the document, and the last argument tells the parser that the pointer in argument 2 points to an XML file name that is a null-terminated string. This step is shown in the example in Figure 3, Section Q.

Putting Callbacks to the Test

One of the major differences of the DOM API application discussed in my November 2000 article versus the SAX application discussed in this article is that since you are not building the document in memory (using DOM), you must rebuild the input document from all SAX events, as you go, and write the document to your new output file. You can't simply insert the new element to add the rating. The XML tags act as triggers for the characters' extraction process that will be the source of your new document. To write this data out to a stream file, I will use the same stream file procedures that I used in the DOM API article to accomplish creating the new XML document with earned points.

Now, reviewing the source input XML document of Figure 1, I will walk through the SAX parsing process for the first branch (QPWDEXPITV). The root node, or what Figure 4 identifies as the StartDocument event, instigates the first callback event the parser encounters. This is the tag shown in Figure 1. This causes the startDocument procedure shown in Figure 3, Section S to be called where the tag is recreated for the output XML document. Next, upon encountering the top-level element , the scanner instigates the StartElement event. This causes the parser to issue a callback to the startElement procedure shown in Figure 3, Section X in the SEC0002RS application. As shown in the procedure interface for this function and the table in Figure 5, this function has two arguments passed to it:

  • A pointer to the element name (Name@).
  • A pointer to a list of any attributes for the element (Attr@).

In Figure 3, Section Y of this procedure, the Name@ pointer is passed to another procedure (not shown in Figure 3) called getName that returns a pointer (OutString@) to a character string encoded with CCSID 37 (USA English) converted from the DOMString representation (which is essentially Unicode) of the underlying object created by SAX parser. The OutString@ pointer is used to extract the element name with the %str function in that section for building the start element tag in the output document. Figure 3, Section Z introduces a new function to this application called QxmlAttributeList_getLength that retrieves the number of attributes, if any, associated with the current element under the scanner given a pointer (Attr@) to the attribute list. This is followed by an iteration or loop shown in Figure 3, Section AA that extracts the attribute name (with the QxmlAttributeList_getName_byIndex function) and the related attribute value (with the QxmlAttributeList_getValue_byIndex function) to construct the attribute phrase of the form attribute name="value" that becomes a part of the element tag of the form .

Next, the element is encountered and passed to the StartElement callback. Then the element is encountered and once again the StartElement callback is called. The scanner encounters a string of characters (QPWDEXPITV) which causes the parser to issue a callback the procedure identified to respond to the Characters event, as shown in Figure 3, Section V. Two arguments, a pointer to the character string and a pointer to an integer representing the length of the character string, are passed to the Characters procedure shown. With the pointer to the character string, the application calls the getName function again to convert the encoding scheme from a Unicode representation (DOMString) to a character string encoded as CCSID 37, shown in Figure 3, Section W. The QxmlTranscode function, discussed in my November 2000 article, is called to accomplish this encoding conversion. (For the discussion of the usage of this function, refer to that article.)

Navigating through the XML document shown in Figure 1, the scanner passes over its first end tag, the end element tag. Accordingly, the parser issues a callback to the applications endElement procedure shown in Figure 3, Section BB. There the procedure accepts only one argument that represents a pointer to the tag element name for which an end has been found. In Section CC of that procedure, a test is made to determine if a valid system value grouping has preceded this element and if the end tag is for the Points element. If so, the procedure takes the previously saved system value and does a lookup in the compile-time table to retrieve the number of earned points for this policy value. As I mentioned earlier in this article, to simplify the illustration, I have not complicated it with an involved algorithm for determining the rating--just a simple lookup. But, since you have not encountered the Points tag, the procedure simply creates an ending tag and writes the tag out to a stream file, as shown in Figure 3, Section BB, with the call to the QxmlWriteOutPutStream. This function takes the following argument:

  • A pointer (fd) to the output XML file identified opened with the call to QxmlOpenNewOutPutStream, shown in Figure 3, Section P.
  • A pointer (OutPutStr@) to the string representing the ending element tag.
  • An integer (InCodePage) containing the value for the character encoding scheme.
  • An integer representing the length of the character for the ending element.

The scanner next encounters the starting element tag for , which causes the parser to issue another call to the startElement callback procedure. After recreating this tag in the output XML document, the character string for Value is encountered, and the parser issues a call to the Characters procedure. To finish this element, the parser next encounters the ending element tag in the source input XML document for Value () that it writes to the output stream file. Then the starting element for Points is encountered. This causes the same sequence of steps to be executed as for previous elements and has the distinction of causing the EarnedPoints element to be written to the output XML document as detailed. Then the application returns control to the parser, and the scanner continues to the next SystemValue policy recommendation branch. Finally, the end of the document is reached, which causes the parser to issue a callback to the application procedure, endDocument, which as shown in Figure 3, Section U, does not take any arguments and does not do anything. However, you can implement any specific requirements your application may have upon encountering the end of the document. While neither processing instructions nor ignorable whitespace should be encountered in the source input XML document, I have provided an example of how those XML elements might be handled. The ignorableWhiteSpace procedure, shown in Figure 3, Section DD, takes two arguments:

  • A pointer (Char@) to the whitespace characters.
  • A pointer (Len@)to an integer holding the length of the whitespace character.

The processingInstructions procedure, shown in Figure 3, Section EE, takes two arguments:

  • A pointer (target@) to the character string representing the target for the processing instruction.
  • A pointer (data@) to the character string representing the data (parameters) to be passed to the target of the processing instruction.

Processing instructions force a call to be made to an external procedure for some arbitrary requirement. Processing instructions are somewhat frowned on by most XML developers because they do not have any relational significance to the structure of an XML document and can be placed anywhere in the document. Processing instructions are used more often by Extensible Stylesheet Language Transformations (XSLT) to use Extensible Stylesheet Language (XSL) to transform an XML document in one notation to an XML document in another lexical notation.

As with most every application of substance, there is usually a bit of housekeeping to be done before exiting. The example application accomplishes its cleanup work in Figure 3, Section R. There the application calls a series of XML API functions unique to IBM's implementation that are used to destroy underlying objects that have been used to support the XML DOM and SAX functions. The call to QxmlDocumentHandler_delete takes the pointer to the document handler, and

          CallP QxmlDocumentHandler_delete(DocHndlr@)

deletes the instance created in Step 4. The call to QxmlErrorHandler_delete takes the pointer to the error handler, and

          CallP QxmlErrorHandler_delete(ErrHndlr@)

deletes the instance created in Step 5. The call to QxmlSAXParser_delete takes the pointer to the SAX parser, and

          CallP QxmlSAXParser_delete(SAXParse@)

deletes the instance created in Step 2. The call to QxmlCloseOutPutStream takes the pointer to the stream file, and

          CallP QxmlCloseOutPutStream(fd)

closes the output stream file that was opened for the output XML document in Figure 3, Section P. With the call to QxmlTerm, the XML parsing environment is ended, and underlying support objects are destroyed and released from memory.

Running the SAX Parser Example

To run this application, issue the following command:

Call SEC0002RS Parm('/home/your_directory/sec0002n.xml' +

The first parameter to this command is the qualified file name for the input source document (sec0002n.xml) that you should get with the downloadable code. The second parameter is the qualified target file name for the output XML document (in this example, sec0002o.xml), which can be any name you choose.

This ends the tutorial. I hope you have enjoyed learning about SAX as much as I have enjoyed writing about it. Along with my November 2000 article, "RPGIV and XML Together," this article should give you yet another option in XML-enabling your RPG IV application and promote better integration with Web-based and multiplatform applications without requiring expensive middleware solutions.

Jim D. Barnes is an infrastructure architect at PentaSafe Security Technologies, Inc. in Houston, Texas. You may reach him at This email address is being protected from spambots. You need JavaScript enabled to view it..


  • Applied XML: A Toolkit for Programmers. Alex Ceponkus and Faraz Hoodbhoy. John Wiley & Sons, Inc., 1999
  • Professional Java XML Programming with Servlets and JSP. Alexander Nakhimovsky and Tom Meyers. Wrox Press Inc., 1999
  • XML and Java: Developing Web Applications. Hiroshi Maruyama, Kent Tamura, and Naohiko Uramoto. Addison-Wesley, 1999






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


    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


    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


    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


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