The IBM HTTP Server for i, powered by Apache, has three distinct ways to handle whether a particular request for a resource will result in that resource actually being returned. These three techniques are access control, authentication, and authorization, or AAA.

In this article, I’ll share how AAA works within IBM HTTP Server for i.

First A: Access Control

Access control refers to any means of controlling access to any resource. This A is distinct from authentication and authorization.

IBM HTTP Server for i uses Allow and Deny directives to implement the criteria of access control. The Order directive

Unless you say otherwise, numeric database fields have a value of zero and character fields are blank, right? Not necessarily. There’s more to default field values than some i Gurus realize.

A field’s default value is the value the system assigns to the field when an application does not specify a value. Default values come into play in several situations.

1. A record (row) is added to (inserted into) a physical file (table) by means of a logical file or SQL view that does not contain one or more fields.
2. RPG O specs list the fields of an externally described file,

Properly implemented, single sign-on (SSO) is a blessing for i/OS shops. With it, users log on to their desktops once and then access all their servers without entering several different passwords. But it’s always been problematic enabling SSO for Power i machines, causing some administrators to skip the process all together. This week, I’ll present a workaround for making PC5250 sessions act like single sign-on participants without configuring SSO.

Same as Single Sign-On, Only Different

In earlier articles, I outlined how to set up an i/OS system for single sign-on. (See Related Stories below.) A true SSO environment provides access