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.

iSeries Audit Journal

Use the following command to display the contents of the audit journal on the iSeries:


This is very useful when researching security issues.

Technorati Tags: e1,enterpriseone,erp,peoplesoft,oracle,jde,jd edwards

iSeries JDBC jt400.jar – {note to self}

Excerpt from a post on JDEList.com by Colin Dawes:

You CAN NOT use the jt400 from the client access folder.

You need to use the jt400 that is on your iSeries. The 2 versions are not the same and you’ll get some hanging if you use the iSeries Access version.

The jt400 on the iSeries is located at:

Usually you need to copy this to the following location on Windows:

I say usually because sometimes during the installation prople point the installed to the iSeries Access Path. In this case the WAS variable will be incorrect and you either need to (1) Change the variable in WAS or copy the jt400.jar from the iSeries on top of the jt400.jar that came with iSeries Access.

Technorati Tags: e1,enterpriseone,erp,peoplesoft,oracle,jde,jd edwards

FTP & iSeries

Ok, we have some UBEs that run and they produce a text file in the IFS System on our i550. In the processing options of these UBEs, the user can specify the name that they would like the file to have. Since their UI to the system is through the web, when they put in things like “c:401k.txt” or “c:insmembers.txt” the file gets placed into the root of the IFS system as a file with the name “c:401k.txt” or “c:insmembers.txt”. They look very strange in iSeries Navigator. And, oh by the way, you can’t delete them. The only way that I have found to delete them is by using the windows command line FTP. Here is what I do to get rid of them:

  1. Once logged in through FTP, type quote site namefmt 1 to change to the IFS naming format. You’ll notice that, if you do a pwd, the working directory is “/QSYS.LIB/QGPL.LIB”.
  2. You need to get to the root so, type cd .. [ENTER] cd .. [ENTER]. You should get a response that says your current directory is “/”.
  3. Then either use del or mdel and delete the files.

More on switching between the library file system and the directory file system when FTPing an AS400:

quote site namefmt [0|1]

  • Summary:
    • 0 – specifies the library file system
    • 1 – specifies the directory file system
  • Detail:
    • NAMEFMT 0 | 1 : Specifies the naming
      format that identifies file locations inside your FTP session.
      • NAMEFMT 0 assumes that you?re only copying
        files into and out of the QSYS.LIB file system using the DB2 UDB naming format of
      • NAMEFMT 1 is used for identifying files
        in all IFS file locations, and all files or locations must be listed in IFS notation
        (like /home/dir, /QOpenSys/dir, /QDLS/dir, /QSYS.LIB/dir.lib/file.file). To view the
        current NAMEFMT values for your FTP session, type NAMEFMT or QUOTE SITE NAMEFMT without
        any parameters.

Technorati Tags: e1,enterpriseone,erp,peoplesoft,oracle,jde,jd edwards

Stubborn iSeries Jobs

I am not an iSeries expert…

However, since we use the iSeries for our E1 Enterprise Server I am required to use it more than I ever wanted to. Anyway, I have been doing some experimenting with the XML Kernel jobs that get started up, when one of the kernel jobs did not end when I issued the endnet command. So, I used wrkactjob and issued an endjob command with *IMMED. Well, after waiting a while it didn’t end. After about 30 minutes of trying other things and talking to our resident iSeries guru, I gave up and left for the day.

I got in this morning to find the jobs still “ending”. So, I did some looking through Google and found another command that I could try ENDJOBABN (End Job Abnormal).

Info from an article on ITJungle.com:


ENDJOBABN has been known to take down jobs that are too stubborn for ENDJOB. But it has a few limitations that you need to be aware of. Specifically, the following things affect ENDJOBABN use:

  • ENDJOBABN cannot be run against a job before you’ve attempted to end the job through the ENDJOB command, with *IMMED specified in the “how to end” parameter. OS/400 is also hard-coded to ignore an ENDJOBABN statement until 10 minutes have passed since you ran an ENDJOB *IMMED command on the same job. So not only do you have to run ENDJOB for a problem job before using ENDJOBABN, you also have to give ENDJOB time to work.
  • ENDJOBABN is shipped with *PUBLIC *EXCLUDE authority. And to run ENDJOBABN, you need job control (*JOBCTL) authority in your user profile.
  • ENDJOBABN can be run against a job only once. Additional ENDJOBABN commands can’t be run.

QACX Files In The iSeries IFS

We had almost 8000 QACXxxxxxx files in our tmp directory in the IFS on our System i Enterprise server. They didn’t seem to be causing any harm, but they were definitely taking up space.

According to Oracle (WARNING: you will need access to Oracle’s customer support site), these files are temporary and should be cleaned by the system when a UBE completes processing. So far, since I have been monitoring, the UBEs are completing successfully, but the QACX files are remaining in IFS.

According to the Oracle doc, these files can be deleted…preferably when E1 services are down to ensure that you do not delete something the system is using.

Technorati Tags: e1,enterpriseone,erp,peoplesoft,oracle,jde,jd edwards