Sidebar

The API Corner: Handling System Changes Automatically

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

Write an exit program for the Watch for Event exit point.

 

This is the second in a series of articles related to watch support on the system. The previous column, "One Approach to System Automation," introduced the concept of watches and the Start Watch (STRWCH) command. Also provided in that article was the source for a watch exit program that would be called when the message CPD1689 (Local system time has been adjusted) was sent to the QHST history log. We did not, however, have time to discuss the mechanics of how the program worked. In this article, we will look at the actual program flow. The source for the exit program will not be repeated here. Refer to the previous article if you need to refresh your memory on how the program was written.

 

When the Watch for Event exit point calls a user exit program, four parameters are passed to the exit program. These parameters are documented here, with the bare essentials of the parameter list also shown below.

 

Required Parameter Group:

 

1

Watch option setting

Input

Char(10)

2

Session ID

Input

Char(10)

3

Error detected

Output

Char(10)

4

Event data

Input

Char(*)

 QSYSINC/H member name: ESCWCHT

The first parameter, Watch option setting, is a 10-byte input value that identifies why the exit program has been called. In the case of WCHCPD1689, the value passed will be *MSGID, indicating that a watched-for message ID was sent to a watched-for message queue.

 

The second parameter, Session ID, is a 10-byte input value identifying the name of the session calling the exit program. In our case, the value passed will be TIME_CHG as that is the value we specified for the SSNID keyword of the STRWCH command in the previous article.

 

The third parameter, Error detected, is a 10-byte output value that is returned by the exit program. The exit program must set this parameter to a value of all blanks upon return to the system exit point in order to indicate that the exit program detected no error. The special value *ERROR--or any non-blank value for that matter--indicates to the system that the exit program encountered an error and that the watch session identified by the second parameter is to be ended. Ending the session means that the user exit program will no longer be called when the watched-for message is sent.

 

The fourth parameter, Event data, is a variable-length input value that further identifies the reason the exit program was called. When the first parameter has a value of *MSGID, the format of the fourth parameter for V5R4 is this:

 

Fourth Parameter Format

Offset

Type

Field

Dec

Hex

0

0

BINARY(4)

Length of trace information

4

4

CHAR(7)

Message ID

11

B

CHAR(1)

Reserved

12

C

CHAR(10)

Message queue name

22

16

CHAR(10)

Message queue library

32

20

CHAR(10)

Job name

42

2A

CHAR(10)

Job user name

52

34

CHAR(6)

Job number

58

3A

CHAR(4)

Reserved

62

3E

CHAR(256)

Sending program name

318

13E

CHAR(10)

Sending module name

328

148

BINARY(4)

Offset to sending procedure name

332

14C

BINARY(4)

Length of sending procedure name

336

150

CHAR(10)

Receiving program name

346

15A

CHAR(10)

Receiving module name

356

164

BINARY(4)

Offset to receiving procedure name

360

168

BINARY(4)

Length of receiving procedure name

364

16C

BINARY(4)

Message severity

368

170

CHAR(10)

Message type

378

17A

CHAR(8)

Message timestamp

386

182

CHAR(4)

Message key

390

186

CHAR(10)

Message file name

400

190

CHAR(10)

Message file library

410

19A

CHAR(2)

Reserved

412

19C

BINARY(4)

Offset to comparison data

416

1A0

BINARY(4)

Length of comparison data

420

1A4

CHAR(10)

Compare against

430

1AE

CHAR(2)

Reserved

432

1B0

BINARY(4)

Comparison data CCSID

436

1B4

BINARY(4)

Offset where comparison data was found

440

1B8

BINARY(4)

Offset to replacement data

444

1BC

BINARY(4)

Length of replacement data

448

1C0

BINARY(4)

Replacement data CCSID

*

*

CHAR(*)

Sending procedure name

*

*

CHAR(*)

Receiving procedure name

*

*

CHAR(*)

Message comparison data

*

*

CHAR(*)

Message replacement data

 

In V6R1, IBM did introduce some additional fields to this parameter. But they are not needed for our example program.

Additional formats for the fourth parameter are defined.  If interested, you can refer to the exit point documentation in the Information Center  (here for V5R4 and here for V6R1) for other formats that might be returned. These other formats would provide similar information on events such as watched-for LIC log or PAL entries.

 

As you can see, a wealth of information is made available to the exit program in order to allow processing based on the sending of a message on the system. These are the key pieces of information used in the WCHCPD1689 exit program:

 

•·         Message ID is the message ID being sent that caused the exit program to be called. In the current scenario, this field should always be set to CPD1689, but recall that you can use the STRWCH command to specify more than one message ID. In the case of multiple watched-for messages, it would obviously be worth knowing which specific message has been sent! In addition, validating the message ID within the exit program can help you avoid unpleasant surprises if, for instance, a user mistakenly specified the WCHCPD1689 exit program with the wrong WCHMSG value on the STRWCH command.

•·         Offset to replacement data is the offset from the start of the fourth parameter to where the replacement data for the message identified by message ID is located.

•·         Length of replacement data is the length of the replacement data in bytes. This value is not actually used by the WCHCPD1689 exit program but is a critical piece of information all the same. Just as IBM strives for upward compatibility with APIs and outfiles by adding new fields to the end of a data structure or record format and not removing or changing the data type and/or size of previously existing fields, so too does IBM provide for upward compatibility with message description replacement data. Currently, message CPD1689 defines only two replacement variables (we will see how to determine this shortly), but in a future release, IBM may decide to add additional information. In this case, IBM would add these new or changed replacement variables to the end of the existing replacement variables. You could then use the Length of replacement data to determine what amount of replacement data is available to the exit program for processing. In the current case, this is not a concern; both V5R4 and V6R1 provide the same amount of replacement data.

•·         Message replacement data is the variable data inserted into the message. This information is accessed by taking the address of the Event data parameter (the fourth parameter) and adding to this address the Offset to replacement data.

 

We will be using the QSYSINC-provided definition for the Event data parameter as there is no good reason to define and test our own data structure. The RPG data structure, which is found in member ESCWCHT of QSYSINC/QRPGLESRC, is shown below. This member name is provided in the exit point documentation immediately following the parameter list.

 

D*****************************************************************    

D*Watch Exit Program called because a message id and any              

D*associated comparison data is matched.                            

D*This structure is for the user exit program called by               

D*STRWCH cmd or Start Watch (QSCSWCH) API                             

D*****************************************************************    

DESCQWFM          DS                                                  

D*                                             Qsc Watch For Msg      

D ESCLWI                  1      4B 0                                 

D*                                             Length Watch Information

D ESCMID00                5     11                                     

D*                                             Message ID             

D ESCERVED01             12     12                                    

D*                                             Reserved               

D ESCMQN                 13     22                                    

D*                                             Message Queue Name     

D ESCMQL                 23     32                                    

D*                                             Message Queue Lib      

D ESCJN                  33     42                                    

D*                                             Job Name               

D ESCUN                  43     52                                    

D*                                             User Name              

D ESCJNBR                53     58                                    

D*                                             Job Number             

D ESCRSV2                59     62                                     

D*                                             Reserved2              

D ESCSPGMN               63    318                                    

D*                                             Sending Program Name   

D ESCSPGMM              319    328                                    

D*                                             Sending Program Module 

D ESCOSP                329    332B 0                                 

D*                                             Offset Sending Procedure

D ESCLOSP               333    336B 0                                 

D*                                             Length Of Sending Procedure

D ESCRPGMN              337    346                                     

D*                                             Receiving Program Name   

D ESCRPGMM              347    356                                     

D*                                             Receiving Program Module

D ESCORP                357    360B 0                                   

D*                                             Offset Receiving Procedure

D ESCLORP               361    364B 0                                  

D*                                             Length Of Receiving Procedure

D ESCMS                 365    368B 0                                  

D*                                             Msg Severity            

D ESCMT                 369    378                                     

D*                                             Msg Type                 

D ESCMT00               379    386                                     

D*                                             Msg Timestamp           

D ESCMK                 387    390                                     

D*                                             Msg Key                 

D ESCMFILN              391    400                                     

D*                                             Msg File Name          

D ESCMFILL              401    410                                     

D*                                             Msg File Library       

D ESCRSV3               411    412                                    

D*                                             Reserved3              

D ESCOCD01              413    416B 0                                 

D*                                             Offset Comparison Data 

D ESCLOCD01             417    420B 0                                 

D*                                             Length Of Comparison Data

D ESCCA                 421    430                                    

D*                                             Compare Against        

D ESCRSV4               431    432                                    

D*                                             Reserved4              

D ESCCCSID              433    436B 0                                 

D*                                             Comparison Data CCSID  

D ESCOCDF               437    440B 0                                 

D*                                             Offset Comparison Data Found

D ESCORD                441    444B 0                                 

D*                                             Offset Replacement Data

D ESCLORD               445    448B 0                                  

D*                                             Length Of Replacement Data

D ESCCCSID00            449    452B 0                                 

D*                                             Replacement Data CCSID 

D*ESCSP                 453    453                                    

D*                                                                    

D*                                  variable length data @B2M         

D*ESCRP                 454    454                                     

D*                                                                    

D*                                  variable length data @B2M         

D*ESCCD01               455    455                                    

D*                                                                     

D*                                  variable length data @B2M         

D*ESCRD                 456    456                                    

D*                                                                     

D*                                  variable length data @B2M        

 

From the QSYSINC-provided data structure ESCQWFM, the subfields ESCMID00, ESCORD, ESCLORD, and ESCRD correspond to the previously described Message ID, Offset to replacement data, Length of replacement data, and Message replacement data fields, respectively. Within the WCHCPD1689 program, we will not actually use the commented field ESCRD. Instead, we will define a based data structure (CPD1689), which describes the replacement data variables associated with the message being processed.

 

Having now gotten the Information Center documentation and QSYSINC definitions behind us, program WCHCPD1689 first declares the prototype and program interface specifications that are appropriate for a watch exit program. The four parameters declared--Type, SsnID, Error, and MsgDta--correspond to the documented parameters Watch option setting, Session ID, Error detected, and Event data, respectively. In the case of the Event data parameter, the WCHCPD1689 program declares this parameter as being likeds(ESCQWFM). ESCQWFM is the RPG data structure shown previously and is copied into WCHCPD1689 with the statement /copy qsysinc/qrpglesrc,escwcht.

 

Following this, the data structure CPD1689 is defined. This data structure defines the replacement data associated with message CPD1689. In order to determine what replacement data variables are available, we use the Display Message Description (DSPMSGD) command for message CPD1689. Looking at the message text (option 1), we can see that replacement variable &1 is the number of minutes that the local system time is offset from Coordinated Universal Time (UTC) and that variable &2 is a reason code for why the UTC offset value has been changed. In addition, we see that a reason code value of 1 indicates that the system has experienced a Daylight Saving Time transition. A reason code value of 2 indicates that the QTIMZON system value has been changed. Examining the field data (option 2 of DSPMSGD), we can see that &1 is a 4-byte integer value and that &2 is a 2-byte integer value. These two replacement variables are reflected in the CPD1689 data structure as subfields MinutesAdj and ReasonCode, respectively. The data structure is defined as being based(RplDtaPtr) and qualified. Using a based data structure simplifies access to the message replacement data, while qualifying the data structure aids in reducing the possibility of name collisions across message descriptions (ReasonCode, for instance, is a rather generic name that might be found in many messages). In the case of exit program WCHCPD1689, there is little chance of name collisions because the program is so simple. But in a more-complex application name, collisions could start to occur. I suggest that you simply set a standard of qualified message description data structures and be done with it.

 

Following this, we define the pointer variable RplDtaPtr (Replacement data pointer). Strictly speaking, this definition isn't necessary as the RPG compiler will implicitly create a pointer definition for us due to the previous use of RplDtaPtr in basing the CPD1689 data structure. But as with using qualified data structure names to minimize name collisions, I prefer to "across the board" explicitly define my pointer variables in order to avoid possible problems in more-complex applications. The particular problem I'm attempting to avoid here is that pointers implicitly defined by the compiler are scoped as local procedure variables, not global program variables. I have been burned more than once in the past by "accidently" having two occurrences of a pointer variable due to implicit compiler declarations.

 

After declaring the pointer variable RplDtaPtr, WCHCPD1689 then defines five named constants. These are used to better document what is being done in subsequent processing. RqdNbrParms is the minimum number of parameters that WCHCPD1689 requires, SessionName is the name of the watch session that WCHCPD1689 is written for, and the remaining three named constants represent the three documented reason codes that might be returned as replacement data in message CPD1689.

 

Following these definitions, we get to the actual processing of WCHCPD1689, which is very straightforward.

 

After starting a global monitor group to catch unexpected errors, the program checks to ensure that it has been called properly--that is, that the environment the program is running in is the one expected when we initially wrote the program. In a perfect world, none of this checking would be necessary, but I find that most of my programs do not run in a perfect world.

 

The first check is to make sure that at least four parameters were passed. If, for some reason, fewer than four parameters were passed and we did not perform this check, then message MCH3601 (Pointer not set for location referenced) would be the result. I find that problem determination is easier if, rather than "Pointer not set for location referenced," the program displays the message "WCHCPD1689 received only X parms."

 

The other checks being done are simply to verify that the parameters WCHCPD1689 received appear to be of the format expected. That type is *MSGID, SsnID is TIME_CHG, and the message ID is CPD1689. If any of these checks fail, the program sends a message identifying the problem and then ends. Failing any of these checks suggests that "something" is very wrong and that WCHCPD1689 should not continue. Either the program is not being called by the Watch for Event exit point or the parameters used when starting the watch were not correct.

 

There is some redundancy in the provided source code. Rather than setting Error to the value *ERROR in each of the checks, I could have simply set the variable Error once prior to the parameter value checks and allowed the subsequent validation checks to pick up the value of *ERROR. I elected to code the setting of Error as I did so that any developer looking at this program a year from now could easily see my intent--my intent being to exit the program and to tell the system "Don't call me again until this is fixed."

 

Upon successfully passing the previous checks, WCHCPD1689 accesses the message replacement data by setting the basing pointer RplDtaPtr to the correct address and then performs various processing based on the ReasonCode found in the message replacement data. This processing is shown as comments as it will vary significantly for each system. After performing any necessary processing, WCHCPD1689 returns control to the operating system with the Error parameter set to success (all blanks). This tells the operating system to continue calling WCHCPD1689 if more CPD1689 messages are sent to the QHST history log.

 

You might notice that even in the case of an unexpected ReasonCode (the other operation of the select group), WCHCPD1689 indicates to the system that it's OK to continue calling the exit program in the future. To take this action (displaying a message to indicate an unexpected input was encountered and continuing to process subsequent message occurrences) is a judgment call that needs to be made on a case-by-case basis. In this particular situation, the exit program is not doing any processing of a permanent nature (data base updates, object changes, etc.) related to the "other" ReasonCode (it's just displaying a message) and, if the watch session wasn't active, the system would still have "done" whatever was causing the system to send the CPD1689 message in the first place. So I elected to essentially ignore the fact that the message was sent, other than displaying a message documenting that some investigation needs to be done.

 

Contrast this to the previous environment checks, where we ended the watch session in an Error = '*ERROR' situation. In the environment cases, there is a clear indication that we have a configuration problem and that the exit program is not able to watch for the message it was designed for. In the ReasonCode cases, the exit program is still capable of watching and processing the message it was designed for; it is simply detecting ReasonCodes above and beyond its design point. This is a subtle, but important, distinction that you should keep in mind when developing any exit program.

 

This concludes our discussion of the WCHCPD1689 watch exit program and hopefully gives you a feel for how easy it might be write a watch exit program. In the next article, you will see how to watch, and react to, message CPF1393 (Subsystem &1 disabled user profile &2 on device &3) in order to selectively re-enable user profiles without operator intervention. In doing so, you'll also discover a few other capabilities of the system watch support.

 

Meanwhile, if you have other 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

Support MC Press Online

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.

     

     

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

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

  • The Biggest Mistakes in IBM i Security

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

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

    SB CYBRA PPL 5382

    TRY the one package that solves all your document design and printing challenges on all your platforms.

    Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product.

    Request your trial now!

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

    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.