How To Start/Stop The Managed Agent On AS400

You can start/stop the managed agent from the command line (green screen) by following the steps below:

  1. Start the by typing STRQSH at the command prompt.
  2. Change to the JDE_HOME/bin directory by typing <install_dir>/JDE_HOME/bin.
    *** The <install_dir> refers to the installation directory in the IFS
  3. To start the agent enter: startAgent &
    *** The & allows the agent to start as a background job so that it will not stop when you leave the
  4. To stop the agent enter: stopAgent
  5. To restart or bounce the agent enter: restartAgent

You will want to run this in your startup script with a user that has a job queue that is not able to be interrupted.  Because of this, QINTER is not a very good choice.  The user will also need the following permissions: *ALLOBJ, *SAVSYS, *JOBCTL & *SECADM.

Also covered on Oracle’s My Support page ID 659949.1

Tags: , , , , , , , , , , , , ,

Stubborn iSeries Jobs

July 10, 2007 by Stewart Schatz · Leave a Comment
Filed under: IBM i/System i/iSeries/AS400 

I am not an expert…

However, since we use the for our 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 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.

Related Posts with Thumbnails Tags: , , , , , , , ,