The FmtNum subprocedure has been very useful to me in dealing with oversized numbers. When I use FmtNum in a report program, it is obvious to anyone when a number has gotten too large for its allotted space. I suppose it was only a matter of time until I would need to show that a character value is too large for the space I had allowed for it. While chopping off the end of many character fields, such as customer names and inventory item descriptions, is no big deal, chopping of the end of others does present a problem.

I

For developers using Websphere Development Studio Client (WDSc), here is a tip that has been worth its weight in gold to me. The outline view is a very powerful tool. It can be enhanced even more than the default way it is loaded. For example, in the default mode the outline shows the files that are defined, the record format, and all the fields. Outline view can also show the source line numbers where the fields, indicators, subroutines, etc. are accessed. Clicking on a line number in the Outline view takes you to that line in the LPEX editor. This

I want to change all the objects in a library so that they all have the same *PUBLIC and user authorities. My third party software also requires us to change the owner for all these objects, so that each program object in the library can be run under the adoptive authority of the primary software user. Do you have any suggestions for how I can do this?

–Gerald

In this case, performing these two tasks is easy. It just involves executing a couple of CL commands–the Revoke Object Authority (RVKOBJAUT) command and the Grant Object Authority (GRTOBJAUT) command–and creating a