Note: The code accompanying this article is available for download here.

In qsort: A Better SORTA, I described the use of the qsort API. This time, we’ll be looking at its companion API–bsearch–which, as its name suggests, is used to perform searches.

Recent changes in array support in RPG, including V6.1’s abilities to define large arrays, means that I use bsearch less frequently than I used to. Nevertheless, the fact that I write the code that controls the matching still makes it useful. For example, I can code bsearch to search for a partial string, which is something

Note: The code accompanying this article is available for download here.

In my last article, Meet JSON, I introduced you to the concept of JavaScript Object Notation and how it’s changing the way Web applications are being built. Let’s explore JSON syntax a little further by building a really simple customer inquiry Web application. The code can be downloaded here.

This application consists of three simple parts:

• CustInq.html–Simple HTML page to ask for customer number and present customer information
• CUSTINQ.rpgle–RPG/CGI program to output customer information in JSON format
• CustInq.js–JavaScript code to facilitate the communication between the RPG

Handling the QSECOFR user profile is always problematic. On one hand, it’s essential for the smooth operation of your system. Conversely, it can be a major issue if someone discovers its password. This week, I’ll review some real-life QSECOFR security breaches I’ve encountered and what can be done if you encounter these situations in your shop.

Real-Life QSECOFR Security Situations

A lot of strange things can occur with QSECOFR usage. Here are some common situations I’ve run into over the years and what can be done, if you encounter them.

1. Situation: Your IBM i administrator doesn’t change the QSECOFR