TheHeck   165 pts.  |   Aug 7 2009  2:56PM GMT

I would do the following:
DSPOBJD OBJ(QSYS/*ALL) OBJTYPE(*LIB) OUTPUT(*PRINT)

This will give a list of the libraries on your system along with their size. Review this list and determine which libraries need to be deleted. Once you have removed the libraries, I would probably IPL in order to gain the space back.

Aceofdelts   400 pts.  |   Aug 7 2009  7:35PM GMT

You can also delete objects from a library instead of the entire library.
Use the WRKLIB command and option 12.

Note that data files consume much more disk than programs.

Nice to have a backup of everything in case you delete too much (so can put it back).

Whatis23   4040 pts.  |   Aug 8 2009  6:48AM GMT

I would suggest scheduling a RTVDSKINF (during downtime) to get the most thorough info on your entire system. PRTDSKINF has many options for report output, select one which will also list the largest objects in each library in descending order. From there you can decide if you truly want to perform a DLTLIB or just delete the individual large objects. If you go the DLTLIB route, ensure that it is not in your USRLIBL or SYSLIBL or jobs will error looking for the now deleted libs. You should also check with your developers to verify the libraries are not hard coded or used in any production programs or check yourself using FNDSTRPDM(? i’m not logged in). Sometimes disk space is used up by old journal receivers that can be deleted or PFs with thousands of deleted records that should be REORG. As recommended, get a full save of the lib before any deletes.

Voodoovw   1720 pts.  |   Aug 10 2009  12:44PM GMT

Hi Shs,

I know times are tough for many out there right now but I have to throw this out there.

Most 170’s are 10+ years old now. At that age you can expect things to start failing at an increasing rate. The new models are insainly fast. 20+ times faster. Most 170’s were under 400CPW the new ones start at 4300CPW. In a small shop you can probably get 420GB disk, 4GB main storage (RAM), and an LTO4 tape drive and 30 or 40 users for about $18,000. Add $4,000 or $5,000 for services to move you over. Sometimes even the savings on the maintenance alone will pay for the new server in 3 years or less.

I have migrated a few 170’s to the new E4A models. One companies ERP run was an 1 hour and 45 minutes on the 170 and 3 minutes and 30 seconds on the new E4A. That’s 30 times faster. Now they are using lots of features they never even thought about before.

Voodoo

Lovemyi   1470 pts.  |   Aug 11 2009  3:16PM GMT

I would first check with your software vendor as most iSeries machines have license keys for the ERP application software. This could cost you a lot more $$$$$ to move this workload to another newer machine. Also check to see if you are on a support contract for all your software if not most companies will not give you a key for a new machine and depending on the level machine, it may cost you a lot more $$$ for that key if you can even get it.

Infor which owns BPCS, MAPICS, INFINIUM and PRISM is a real tough company to negotiate with if you do not have a maintenance contract and you want to move it to another machine. You are asked up front to pay all back support which can run into millions on even the smallest of machines.

Check out all 3rd party application software for licensing before ordering a new machine. I have run into this trap many many times and sometimes you can make it work with the new hardware and licensing fees to keep the costs down but a lot of the times it really has to be a major reason that the company has to make the switch.

Do your home work before deciding a course of action.

Lovemyi

TomLiotta   7990 pts.  |   Nov 26 2009  11:21AM GMT

Note that DSPOBJD OBJ(QSYS/*ALL) OBJTYPE(*LIB) OUTPUT(*PRINT) will not give you any useful size info. It will only give you the size of the *LIB objects themselves which won’t include the sizes of anything in the libraries (which is where 99+% of the size is going to be).

As for the question, consider first running CLRLIB rather than DLTLIB. There may be job descriptions that have libraries on their library lists or other library dependencies. A CLRLIB will delete objects from the library while leaving the library in place.

Also, consider RNMOBJ (renaming) against libraries instead of deleting anything. A rename means that the original name can be put back in seconds. If things continue to run well, the library can be deleted later.

Tom