7.10.3 Changing an execution agent profile

Using the ajsprofalter command, you can change the settings in an execution agent profile while JP1/AJS3 services are active.

Changes executed by the ajsprofalter command take effect immediately, but do not affect jobs in Now queuing or Now running status. Also, depending on when you execute the command, profile changes might not be applied to standard jobs (including queueless jobs) and HTTP connection jobs in Waiting to execute status or to event jobs in Waiting for prev. to end status. For this reason, we recommend that you make changes to an execution agent profile when no jobs are running.

If you change the execution agent profile while a monitoring generation is in Now monitoring or Interrupted monitoring status, the changes are not applied immediately to the event job defined as the start condition.

The relationship between when profile changes are executed and when they are applied is described next.

Organization of this subsection

(1) Profile changes during monitoring for a start condition
(2) Profile changes during, before, or after start condition monitoring is interrupted

(1) Profile changes during monitoring for a start condition

If you change an execution agent profile by the ajsprofalter command while a start condition is being monitored, the new settings will not affect the event job defined as the start condition. To apply the new settings to the event job, you must perform either of the following:

Terminate start condition monitoring, and then re-register the jobnet for execution.
Perform a restricted termination of the JP1/AJS3 service or scheduler service, and then restart the service and resume monitoring.

The following figure shows an example of the system behavior when changes are made to the settings in an execution agent profile while start conditions are being monitored.

Figure 7‒25: Changing profile settings while a start condition is being monitored

As this figure illustrates, if you change the settings in an execution agent profile while a start condition is being monitored, the new settings do not affect the event job defined in the start condition. They apply only to event jobs in the root jobnet triggered by the start condition after the profile settings are changed.

To Page Top

(2) Profile changes during, before, or after start condition monitoring is interrupted

Start condition monitoring is interrupted when you perform a restricted termination of the JP1/AJS3 service or schedule service. If you then change the settings in the execution agent profile by the ajsprofalter command, the changes do not take effect until you restart the service. Monitoring resumes with new settings.

You can perform a restricted termination of the JP1/AJS3 service or scheduler service in the following ways:

Execute the ajsstop command with the -s, -n, -j, or -k option specified.
Execute the jajs_spmd_stop command with the -job option specified.
Perform a planned shutdown by linking with JP1/Power Monitor.

The following figure shows an example of the system behavior when changes are made to the settings in an execution agent profile while monitoring is interrupted.

Figure 7‒26: Changing profile settings while monitoring is interrupted

If you change the settings in an execution agent profile while start condition monitoring is interrupted, the new profile settings do not affect the monitoring process. They apply only after you restart the service and monitoring resumes.

Figure 7‒27: Changing profile settings before monitoring is interrupted

If you change the settings in an execution agent profile before start condition monitoring is interrupted, the new profile settings do not affect the monitoring process. They apply only after you restart the service and monitoring resumes.

Figure 7‒28: Changing profile settings after monitoring is interrupted

If you change the settings in an execution agent profile after start condition monitoring resumes following an interruption, the new profile settings do not affect the monitoring process.

To Page Top