At times, I wish embedded SQL would act more like RPG. A case in point is with exception/error handling.

Embedded SQL assumes you are using SQLCODE or SQLSTATE to check whether or not each statement worked. In RPG, the equivalent would be have an E extender on every file operation code and checking the %error() after the operation code.

Wouldn’t it be nice if you could get embedded SQL to cause the program to fail if it gets an unexpected error–just like RPG? Well, you can, just by adding one line of code after each SQL statement.

Figure 1 shows

I have used option 25 of the Work with Members Using PDM (WRKMBRPDM) for years to look for character strings in source physical file members. Is there a way to search for two or more strings at once?

–T.

It’s not possible with that option. You might want to use option -e of Qshell’s grep utility.

Let’s say you want to find all instances of invnbr and invoicenumber in source physical file SRC in library TST. Here’s the command you would need to use:

$
grep -in -e 'invnbr
>
invoicenumber
>
'  /qsys.lib/tst.lib/src.file/*

The first, third, and fifth lines

How do you react when there’s an issue with your IBM i partition? This isn’t an easy question as IBM i incidents can involve many different areas, including networking/infrastructure, applications, storage, performance, and third-party vendors. This issue and next, I’ll outline the critical elements of an IBM i incident management plan and how it helps you quickly determine what to do and who to call when problems come up.

The Elements Of IBM i Incident Management

Here are the critical elements I believe every IBM i incident management plan should include.

1. What type of monitoring are you doing: Manual, automatic,