A vendor whose software we use separates objects into two main libraries–a data library and an object library. I had to restore all the data, so I deleted the data library and restored it. After that, the application stopped working. The problem turned out to be that some stored procedures that they created in their data library got wiped out, and the Restore Library (RSTLIB) command didn’t put them back. The story ends happily because the vendor had a program in place for just such emergencies, but (and I’m sure IBM disagrees), I consider this a big old bug in

Yes, you, the person who knows so much about making machinery serve your organization. You, the person who knows so many little, seemingly trivial and insignificant bits and pieces of information. Here’s a bit of info that maybe no one in your shop knows, and it can come in handy. It comes from the IT Jungle Web forums.

Here’s the original question, after a bit of editing.

During a payroll run, I need to create multiple directories (which will be subdirectories) that will contain various reports, for specific companies, for specific pay dates. The company directories already exist. For

Every once in a while, I’ll run into a situation where for no apparent reason, a user can no longer run a process that either updates user-created System i data or creates an output file. The process will run fine one day and stop working the next day. After investigation, the problem usually has something to do with the user’s Maximum Storage Allowed (MAXSTG) parameter.

The MAXSTG parameter is assigned to a user profile when that profile is created. Its mission is to tell the operating system how much auxiliary storage (in kilobytes) can be assigned to store permanent system