jpomanevreset

Format

jpomanevreset
     [-h logical-host-name]
     [-F service-name]
     [-a execution-host-name|-all]
     [-s]
     [-e]
     [-dh manager-host-name -a execution-host- name]

To Page Top

Description

Deletes the information that is to be held by the event action control manager. The command also deletes information on the execution host after communicating with the execution host specified in the -a option.

When a large number of events related to start conditions occur, event action control is in a state of high load, with the result that a slowdown or similar problem may occur in the entire system. However, you can execute this command to return the system to normal operation from the next JP1/AJS3 startup. If the system has several agents, you should use the jpomanevshow command in advance to identify the agent that has caused a large number of events.

In addition, if you run the command with the -dh option specified in cases such as the following, the command communicates with the execution host specified in the -a option and deletes the information on the execution host side:

• In an environment where a hardware copying and mirroring function is used to enable disaster recovery, JP1/AJS3 at the remote site is started by disaster recovery start.

• In an environment that uses an external database, JP1/AJS3 is started by disaster recovery start after recovery.

• In an environment that uses the backup enhancement function, JP1/AJS3 is started by disaster recovery start after recovery.

In the standard configuration, this command can be executed only when the JP1/AJS3 host service is running and the target JP1/AJS3 scheduler service is not running. If you execute the command when the target JP1/AJS3 scheduler service is running or the overall JP1/AJS3 service has stopped, the command results in an error. However, if you specify the-dh option, provided that the JP1/AJS3 service is running, you can execute this command regardless of the status of the JP1/AJS3 scheduler service.

For details about how to stop the scheduler service, see jajs_spmd_stop in 3. Commands Used for Normal Operations.

To Page Top

Execution privileges

In Windows: Administrators privileges

In UNIX: Superuser privileges

To Page Top

Arguments

To Page Top

Notes

• Always separate an option and its value by at least one space character.

• You cannot execute several instances of this command at the same time. Wait for one command to be completed before you move on to another command.

• If the target host specified in the -a option has been defined as the target host for multiple execution agents, information about these execution agents is also deleted.

• The command does not check whether the target host specified in the -a option has been registered as the target host for the execution agent in agent management information. Therefore, if JP1/AJS3 has not been installed on the specified target host, it could take time before the command terminates.

• If you execute the command when the folder to be used for storing information about the event action control manager, which is used by the event action control manager, does not exist, the system operates as if there were no data. The command is terminated normally. For details about the folder for storing information about the event control action manager, see A.1 JP1/AJS3 - Manager files and directories in the manual JP1/Automatic Job Management System 3 Troubleshooting.

• Note that the command will terminate normally even if you fail to delete the file or send data to the execution host. If the KAVT8342-E A file access error occurred. (file-name) (maintenance-information) or KAVT8343-W An attempt to communicate with the agent has failed. (agent-host-name) (maintenance-information) message is output in the standard error output file, you must manually delete the file according to the specified procedure.

• If you fail to delete files, the KAVT8342-E A file access error occurred. (file-name) (maintenance-information) message for each of the unsuccessful files is output to the standard error output file. If you fail to delete a large number of files, a large number of error messages are output accordingly. This implies that you cannot view all the messages. For this reason, you should redirect the standard error output file when executing this command.

  Example:

  jpomanevreset 2> file-name

• If the KAVT8343-W An attempt to communicate with the agent has failed. (agent-host-name) (maintenance-information) message is output, the information about the agent involving the error is not deleted. As necessary, therefore, you should cold-start the JP1/AJS3 service on the execution host.

• If the -all option is specified, the command reports that the specified scheduler service has been cold-started to the target hosts on which the status of event jobs, custom event jobs and jobnets with start conditions is Now running. In addition, the command also performs the same report to the target hosts for which unreported information exists. If the -a option is specified, the command reports that the specified scheduler service has been cold-started to the specified target host even if the status of event jobs, custom event jobs and jobnets with start conditions is not Nor running.

• If an error such as a network error occurs while data is being sent to the target host, the behavior of the command is as follows:

  • When the agent host cannot be connected (a connection attempt times out)

    The command does not retry sending of data.

  • When another network error occurs

    The command retries to connect (up to two attempts) at 10-second intervals.

  For this reason, if the target host or the JP1/AJS3 service on the target host has stopped, it could take time before the command terminates. If the target host name cannot be resolved into the IP address, the command also retries acquisition of the IP address three times at one-second intervals.

• You execute this command in the same environment as that of JP1/AJS3 operation. For example, suppose that you changed DNSEstablish after a JP1/AJS3 stop. Executing this command changes the host name used when communicating with the execution host, so that you cannot identify which manager information needs to be deleted on the execution host. This may cause a problem; for example, the information on the execution host will not be deleted, as expected.

• If there are many files under the folder used for storing information about the event control action manager, it will take time before the command is completed because of the presence of many files that are to be searched for and deleted.

• If you specify the local host name in the -h option, the system will operate by assuming that a physical host is specified.

• If you execute the command after specifying the -e option, the system continues to monitor event jobs, custom event jobs and start conditions but deletes the event information and event start information generated before the event reset. For this reason, you may see Now running for the status of a job in which an event occurred before an event reset or Now queuing for the state of a job in which monitoring has already started. If this occurs, for Now running jobs, you must re-generate events meeting the conditions. For Now queuing jobs, meanwhile, you should either use them as they are or terminate them and then re-register them.

• On the target host side, only the information managed by the target host is deleted. Files remaining as trash are not deleted. If you want to delete files left on the target host as trash, cold-start the JP1/AJS3 service on the target host side.

• If you execute the command without specifying the -e option, monitoring of event jobs, custom event jobs and start conditions ends. If monitoring of these is necessary, perform registration again. You can ignore the KAVS1400-E and KAVS0265-E messages output to the integrated trace log because these messages pertain to termination of monitoring of event jobs, custom event jobs and start conditions.

• If you specify the -dh option, the command terminates all event jobs and custom event jobs that are running in the range from the manager host specified in the -dh option to the execution host specified in the -a option. Therefore, use the -dh option only when any of the cases shown in the description of the option applies.

  If you inadvertently specify the -dh option when none of those cases applies, perform the following procedure: First, from the manager host specified in the -dh option, forcibly terminate all event jobs and custom event jobs that are running on the execution hosts specified in the -a option. Then, register the event jobs and the custom event jobs for execution again.

• If the default scheduler service name assumed when the -F option is omitted is not registered, the command outputs message KAVT8351-E to standard error output and terminates abnormally. Make sure that the default scheduler service name is registered on the command execution host, and then execute the command again.

  You can reference the -h option in the command line to identify the host where the command will be executed.

To Page Top

Return values

To Page Top

Additional information

The status of JP1/AJS3 - View displayed when JP1/AJS3 is normally started is different from that displayed when JP1/AJS3 is started after you use the jpomanevreset command to recover the status of the event action control manager. The state of JP1/AJS3 - View is also different depending on whether you specify the -e option in the jpomanevreset command: that is, whether the event jobs, custom event jobs and start conditions are to be continued. These different statuses are compared and summarized below:

• When you hot-start JP1/AJS3 (-hot)

  Target	Status
  	Status before JP1/AJS3 is stopped	Normal state		After executing the jpomanevreset command
  		Being executed on the local host	Being executed on the remote host	Specifying -e		Not specifying -e
  				Being executed on the local host	Being executed on the remote host	Being executed on the local host	Being executed on the remote host
  Event job and custom event job (in jobnet)	Now running	Ended abnormally #1, #2	Now running #2	Ended abnormally/Unknown end status	Now running/Unknown end status	Unknown end status
  	Wait for prev. to end	Wait for prev. to end #3		Wait for prev. to end #3
  	Being held	Being held #3		Being held #3
  	Now queuing	Now running/Ended abnormally	Now running	Ended abnormally/Unknown end status	Now running/Unknown end status	Unknown end status
  	Other statuses	No change		No change
  Start condition	Now monitoring	Now monitoring		Now monitoring		Monitor terminated
  	Other statuses	No change		No change
  Event job and custom event job in start condition	Now running	Now running		Now running/Unknown end status		Unknown end status
  	Now queuing	Now queuing		Now queuing/Unknown end status
  	Other statuses	No change		No change

  #1

  The Now running status occurs when the system is restarted after a system down.

  #2

  The Unknown end status may occur depending on the timing of the termination processing.

  #3

  If the Not executed + Ended status occurs when the preceding unit is handled as an abnormal end.

• When you warm-start JP1/AJS3 (-warm)

  Target	Status
  	Status before JP1/AJS3 is stopped	Normal status		After executing the jpomanevreset command
  		Being executed on the local host	Being executed on the remote host	Specifying -e		Not specifying -e
  				Being executed on the local host	Being executed on the remote host	Being executed on the local host	Being executed on the remote host
  Event job and custom event job (in jobnet)	Now running	Unknown end status		Unknown end status
  	Wait for prev. to end	Not executed + Ended		Not executed + Ended
  	Being held	Not executed + Ended		Not executed + Ended
  	Now queuing	Unknown end status		Unknown end status
  	Other statuses	No change		No change
  Start condition	Now monitoring	Now monitoring		Now monitoring/Monitor terminated		Monitor terminated
  	Other statuses	No change		No change
  Event job and custom event job in start condition	Now running	Now running		Now running/Unknown end status		Unknown end status
  	Now queuing	Now queuing		Now queuing/Unknown end status
  	Other statuses	No change		No change

• When you cold-start JP1/AJS3 (-cold)

  Target	Status
  	Status before JP1/AJS3 is stopped	Normal state		After executing the jpomanevreset command
  		Being executed on the local host	Being executed on the remote host	Specifying -e		Not specifying -e
  				Being executed on the local host	Being executed on the remote host	Being executed on the local host	Being executed on the remote host
  Event job and custom event job (in jobnet)	Now running	Not registered		Not registered
  	Wait for prev. to end
  	Being held
  	Now queuing
  	Other statuses
  Start condition	Now monitoring
  	Other statuses
  Event job and custom event job in start condition	Now running
  	Now queuing
  	Other statuses

• If the startup mode is not specified when JP1/AJS3 is started

  The status of each item when the startup mode of the scheduler service is used is the same as that of the corresponding item shown above.

To Page Top

Example 1

For an example of deleting the information held by the event action control manager, see Example in jpomanevshow in 3. Commands Used for Normal Operations.

To Page Top

Example 2

The following command deletes information about the manager host MAINHOST held by execution agent AP1 in an environment where operation has been switched to a remote site using the disk copy and mirroring functionality of the hardware.

jpomanevreset -h LogicalHost -F AJSROOT2 -dh MAINHOST -a AP1

To Page Top