+

Search Tips   |   Advanced Search

Start and stop the administrative agent

Start and stop administrative agents using startServer and stopServer commands.

startServer <administrative_agent>

From a command dialog at the bin directory of the administrative agent profile, run the serverStatus -all command. Suppose running the command shows that the administrative agent profile is named adminagent. To start the administrative agent, from a command dialog at the bin directory of the administrative agent profile:

startServer adminagent

For iSeries, use the Submit Job (SBMJOB) CL command.

SBMJOB CMD(CALL PGM( product_library/QWASSTRSVR) PARM('-profilePath' 'profile_root' '-server' 'administrative agent')) JOB(server) JOBD(QWAS85/QWASJOBD) JOBQ(QWAS85/QWASJOBQ) USER(QEJBSVR) LANGID(*USRPRF) CNTRYID(*USRPRF) CCSID(*USRPRF) OUTQ(QWAS85/QWASOUTQ) ALWMLTTHD(*YES)

Windows First steps dialog...

Stop administrative agent...

stopServer adminagent

For iSeries, use the end job (ENDJOB) CL command.

ENDJOB JOB(jobNumber/QEJBSVR/jobName) OPTION(*CNTRLD) DELAY(delayTime)

The jobNumber element is the job number, the jobName element is the name of administrative agent job, and the delayTime element is the amount of time to wait for the job to end in seconds. Use a value of 600 seconds initially. Read about the appropriate delay time in the topic on shutting down the product subsystem.


  • Start and stop a node
  • (iSeries) Shutting down the QWAS85 subsystem for WAS
  • Starting and logging off the administrative console
  • startServer command
  • stopServer command
  • Administer stand-alone nodes using the administrative agent