How To Start/Stop The Managed Agent On AS400
Filed under: *ALLOBJ, *JOBCTL, *SAVSYS, *SECADM, EnterpriseOne - Security, Java, QSHELL, STRSQH
You can start/stop the managed agent from the command line (green screen) by following the steps below:
- Start the QSHELL by typing STRQSH at the command prompt.
- 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 - 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 QSHELL - To stop the agent enter: stopAgent
- 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: *ALLOBJ, *JOBCTL, *JOBCTL, *SAVSYS, *SAVSYS, *SECADM, as/400, EnterpriseOne - Security, Java, jde, oracle, QSHELL, QSHELL, STRSQHStubborn 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:
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
ENDJOBABNstatement until 10 minutes have passed since you ran an
ENDJOB *IMMEDcommand on the same job. So not only do you have to run
ENDJOBfor a problem job before using
ENDJOBABN, you also have to give
ENDJOBtime 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
ENDJOBABNcommands can’t be run.


