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
        library/file.member.
      • 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

Where am I? – Distinguish EnterpriseOne (E1) Environments

Well, if you’ve found out anything while being an EnterpriseOne CNC person, it’s that E1 is confusing. Oh, maybe if you have a really simplified install, it might not be too bad. But, overall it is confusing.

The problem is it isn’t just confusing for us tech-types but also for the end users and implementation teams. In order to relieve the confusion of not knowing which environment you are in I did a little bit of image editing:

The image is located at ..webclient.warshareimagesjdelogo-onwhite.gif

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 JOB(999999/USER/JOBNAME)
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.

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

Nice Cut! – EnterpriseOne (E1) Fine Cut Task Views

Well, maybe not nice…but “Fine”.

In working with our users we have found that they take advantage of the menu filtering, which is referred to as “Fine Cut”. Moving these from one environment to the next can be done through OMW or by copying some files. For us, it has been easier just to copy the files.

Here they are:

F9000-Task Manager
F9001-Task Relationships
F9002-Task Alternate Descriptions
F9005-Variant Description
F9006-Variant Detail

Have Fun!

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

Ausy E1 Tools

Now these are AWESOME!

We have been using just 2 of the tools that Alexander Pastuhov has available.

What are those 2 products?

  • Boomerang
    • We have 2 separate instances for 2 different business units so we use Boomerang to quickly and easily transfer objects from one to the other. It’s a VERY slick product. In a previous installation of OneWorld Xe we created data sources and transfer activity rules to accommodate this need, but with Boomerang we were able to keep our installation as vanilla as possible.
  • Update Queue Names In Versions
    • Yeah, it’s a long name, but man is it a time saver. When you consider the time that it would take you to change the job queue in the hundreds of versions that we had to split up our batch processing, it probably saved a good week of tech time.

Thanks Alex for providing such easy to use specialized products!

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