Error message
MJS881S jobname(<job number>) COMMUNICATION ERROR OCCURRED FOR <host name>,CODE(3,0000) |
Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action
Points to check
Does the continuous execution mode match on the schedule server and the execution server?
Cause
If the continuous execution mode does not match on the schedule server and the execution server, the network job starts in duplicate, and seems to be executing even though the job has actually ended, or outputs error message MJS881S and then ends abnormally.
Action method
Use the following procedure to check the current status of the continuous execution mode on each server, and if they do not match, unify them to a mode that is appropriate for the operation.
On each of the schedule server and the execution server, check if the continuous execution mode is enabled or disabled:
jmmode check [-sys { all|<subsystem number>} ]If the characters displayed to the right of JOB are on, the mode is enabled. If the characters displayed to the right of JOB are off, the mode is disabled.
If the continuous execution modes do not match, stop the Systemwalker Operation Manager daemon/service on one of the servers, and then enable or disable the continuous execution mode:
To enable
jmmode continue -func JOB [-sys { all|<subsystem number>} ]To disable
jmmode cancel -func JOB [-sys { all|<subsystem number>} ]Then, start the Systemwalker Centric Manager service/daemon that was stopped.