It is truly amazing how many IBM i administrators and programmers do not understand how to debug authority failures.

When a user they support encounters an authority failure, many typically do one of two things:

1. Give the user *ALLOBJ authority
2. Or, if they can identify the object on which the authority failure occurred, they make sure *PUBLIC has *ALL authority to it

Attacking authority failures in this way results in huge security holes. And this practice is almost certainly non-compliant with the organization’s written or unwritten security policy. Further, when the change happens to fix the authority failure, they

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

During execution, programs rely strictly on their compiled objects. The source used to create the object is not used in any way for execution. There are, however, some instances where source is of value during processing.

In a source member, one could store FTP commands to be used with the FTP (Start TCP/IP File Transfer) command, SQL statements to be used with the RUNSQLSTM (Run SQL Statements) command, or REXX statements to be used with the STRREXPRC (Start REXX Procedure) command. Knowing where the proper source exists is

Power i Capacity BackUp (CBU) systems are complicated critters. Aside from the basic tasks of configuring, testing, and enabling a CBU for taking over processing from a production box, there are a lot of different problems that can occur with CBU configuration, and even when the CBU is running in replication mode. This week, let’s look at a few not-so-obvious CBU configuration issues that can hurt your CBU or production system setup.

Issue #1: Problems with libraries that start with “Q”

By default, many Power i replication packages do not replicate objects in libraries whose names start with “Q”, such