Simple check for IFS objects existence:

Another simple way to check for the existence of an IFS object --without having to dig into IFS APIs -- is to use the DSPLNK command with the printer output option. The command will generate CPFA0A9 if the object(s) do not exist.
The only drawback to this method is that it will create a spool file listing the object(s) -- if they actually exist. But you could encapsulate it in a CL where you could override and hold the spool file before issuing the DSPLNK command, then delete it when done.
OVRPRTF FILE(QSYSPRT) HOLD(*YES)
DSPLNK OBJ('/path/objectname') OUTPUT(*PRINT) OBJTYPE(*ALL)
DETAIL(*BASIC)
DSPOPT(*USER)
DLTSPLF FILE(QSYSPRT) SPLNBR(*LAST)

Cost of Non-Conformance:

(CONC.) The element of the *Cost Of Quality* representing the total cost to the organization of failure to achieve a good *Quality* product.
CONC includes both in-process costs generated by quality failures, particularly the cost of *Rework*; and post-delivery costs including further *Rework*, re-performance of lost work (for products used internally), possible loss of business, possible legal redress, and other potential costs.

Embedded SQL in free format RPG:

At last free-form coders no longer have to relegate SQL calls to traditional C-spec subroutines or subprocedures at the bottom of the program (or worse, break out of /Free in the middle of the program). Now, an SQL statement can be placed directly in a /Free block. This is the new features in SQL with i5/OS V5R4.. The only rules are:
• The SQL Statement must begin with EXEC SQL (on one line)
• The statement itself can span multiple lines (without a special line extender)
• The statement, like normal free format, must be terminated with a semicolon
A sample statement with host variables looks like the following in free form RPG:

EXEC SQL Select EmpName
Into :EmpName
Where EmpNo=:EmpNo;

Quickly find SQL Error message Description:

These two methods are easy to use and are sure to help eliminate a lot of frustration when it comes to searching for SQL error message descriptions.
1. Use the following Display Message Description command, replacing the RANGE value with the SQL error code that you are investigating: DSPMSGD RANGE(SQL7007) MSGF(QSQLMSG)
2. Go to the DB2 Universal Database for iSeries page of the IBM Information Center web site, scroll down and then click on "SQL Message Finder". Key in your error number and you will quickly find yourself back on the road to productivity again.

Chaku Chaku:

The term "chaku chaku" may sound funny to most of us, but it's serious business in Boeing's Portland, Ore., bevel gear-making organization.
Japanese for "load load," chaku chaku is an efficient style of production in which all the machines needed to make a part are situated in the correct sequence very close together. The operator simply loads a part and moves on to the next operation. Each machine performs a different stage of production, such as turning, drilling, cleaning, testing or sandblasting.
In the past, using the "job shop" method, these machines were located in separate areas of the factory, and each required a separate machinist to operate it. They turned out hundreds of parts in batches that were then loaded into baskets for transporting to another area or simply sat there in stacks waiting until they were needed or the whole batch was completed.
The machines in the new chaku chaku line are located in a U-shaped flow line. The machines eject the parts automatically and everything is timed just right, so the operators don't spend time unloading or waiting.

This flow line is assigned only those resources (equipment and labor) that are required for the specific activities to be performed. Included in the line are appropriate inspection tools to ensure no quality problems are passed on to the next operation.
Because each flow line is responsible for turning out a completed product, it is easier to keep track of how many parts are being produced and to stay on schedule.

iSeries Pager Messages:

If your pager or cell phone has an e-mail address for text messages, and your iSeries is configured for SMTP, a simpler method is to send the messages using the SNDDST command.
SNDDST TYPE(*LMSG) TOINTNET(&ADDR) DSTD(&SUBJ) LONGMSG(&MSG)
Where:
&ADDR is the email address of your pager or cell phone (such as 7145551234@mobile.com )
&SUBJ is any subject text
&MSG is the message text

Monitor the number of Active Users in the System:

The DSPSYSSTS command with the assistance level as *BASIC provides the number of users active in the system. It also gives the total number of batch jobs in the system and the disk usage of the system.
DSPSYSSTS OUTPUT(*) ASTLVL(*BASIC)