i/System i/iSeries/AS400

The EnterpriseOne i/System i/iSeries/AS400 category will include all posts and pages pertaining to the IBM i/System i/iSeries/AS400 when administering EnterpriseOne.

How To Get A Disk Usage Report From IBM iSeries

Below are the steps that I used to get a disk usage report from our IBM iSeries which we used to find and track the large files in our JDE EnterpriseOne data library:

  1. Type: GO DISKTASKS and press [Enter]. Then choose option 1 in the screen below:
  2. Choose option 1 for when to collect the information:
  3. On the next screen type in *CURRENT in both the Date and Time fields and press [Enter].
  4. Press [F12] twice to get out of the Collect Disk Space Information screen.
  5. Do a WRKACTJOB and find a job similar to the one highlighted below:
  6. The job may run for several hours depending on the configuration of your system.
  7. When the job above has finished, go to the Disk Space Tasks menu again by typing GO DISKTASKS. This time, choose option 2: Print disk space information.
  8. On the next screen choose “Library” by putting a 1 in the field as in the image below:
  9. Enter a “Y” in the next field to indicate that you want to include info about objects in libraries. Then press [Enter].
  10. Fill in the library name that you would like to get information about as in the image below:
  11. Finally, find the report using System i Navigator and drag it to your desktop:
     IBM System i Navigator

I hope that helps you find the large objects in a library on an IBM iSeries.

Reference: IBM GO DISKTASKS Overview

Reduce Disk Space On IBM iSeries Using RGZPFM

This isn’t news to many iSeries Admins or CNC Admins but it really hit home for me a couple weeks ago. We had a file that was really increasing to an unmanageable size (500+GB) and didn’t know why. It was the F00165 (Media Objects). There were only 500,000+ records and only a few thousand deleted records. We really couldn’t understand the massive amount of growth. Well, it turns out that one of our developers has a job running on the scheduler every 3 minutes which rights text log entries to the F00165. It doesn’t create a bunch of new records, it just appends entries to existing records. Not knowing if Reorganizing the file would help, we waited until after hours and ran the following:


The results were amazing! It dropped the file size to 770+MB! Yeah, that’s right MB!!!

That’s nuts, I agree. However, it made our infrastructure manager very happy and now we run that job nightly just to make sure we don’t need to deal with it again.

IBM iSeries RGZPFM Command

IBM iSeries RGZPFM Command: FAQs

IBM iSeries RGZPFM Command: Ending a RGZPFM

Automatically Convert EBCDIC To ASCII When Accessing A File From An iSeries Mapped Drive

When accessing log files located on an iSeries using a mapped drive the text remains in EBCDIC format. However, by using iSeries Navigator and following the steps below, the file will be automatically converted to ASCII:

  1. Expand My Connections.
  2. Expand your connection name.
  3. Expand File Systems.
  4. Select File Shares.
  5. On the right side of the screen, right-click on the file share that will be converted.
  6. Select Properties.
  7. Select the Text Conversion tab.
  8. Select the option Allow file text conversion.
  9. Type .* (a period followed by asterisk) in the File extensions for automatic EBCDIC/ASCII text conversion: input area and click on the Add button.
  10. Click on the OK button to save the changes.

These steps can be found on IBM Document N1015165

Unable to Delete iSeries Physical File

This morning, I was unable to delete an unused physical file because of the following error:

Message ID . . . . . . : CPF3219 Severity . . . . . . . : 40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 08/20/13 Time sent . . . . . . : 08:30:16
Message . . . . : Cannot delete file or member of file F083510001 in
Cause . . . . . : If a member was referred to, the member name is *N. If
this is a delete operation, file F083510001 in library PRODDTA or a
member of file F083510001 was not deleted because dependent files or members
are based on either the file or the member. If this is a restore operation,
a problem occurred preventing a successful restore of file F083510001 in
library PRODDTA. This problem occurred after the restore operation had
already created the file in preparation for the load of the file’s data from
media. The restore operation was not able to delete this unsuccessfully
restored file because dependent files or members are based on either the
file or the member.

I used the following SQL command to delete the file:


Great iSeries SQL Reference When Working With Dates & Times

I really used this page a lot when working with SQL and dates & times.

DB2 Basics: Fun With Dates and Times