I use WebSphere Development Studio client (WDSc) often for editing RPG, CL, command, and DDS source code. I was happy to learn recently that WDSc also works well for the development of XSL transformations. I don’t consider myself a pro at it, but I’m finding WDSc so helpful with my XML projects that I wanted to go ahead and share something of what I’ve learned so far.

First, I need to mention that I am currently using WDSc 6.0.1. I have tried XSL transformations under the full product and WDSc Lite, and both have worked well for me so far.

Recently one of my superiors walked into my cubicle and asked for some information. I was in the middle of another task and didn’t want to be side-tracked, so I hurriedly ripped out an SQL query to satisfy his request. A little while later he was back in my office asking me to run a fresh copy of the query, and while I was at it, to total some of the columns. This last request threw me for a loop, so I used Query/400. Could I have satisfied his request with SQL?

–D

I thought I had covered this situation

In the last issue, I discussed how System i default passwords are created, their consequences, and how they can be detected and neutralized. Today, I’m going to shift the focus over to some simple command configurations for limiting or eliminating the proliferation of default password user profiles in your partition.

What Are Default Passwords and When Are They a Problem?

Default i5/OS and OS/400 passwords occur when a user profile’s password value is the same as its corresponding user profile name (i.e. a user profile called JOE has a password of ‘JOE’). Active default passwords are a security risk because