This section explains the range of network jobs that can be executed when the schedule server (where the network jobs are submitted) uses a version that is different from the version used by the execution server (where the network jobs are executed).
Basically, network jobs can be submitted to servers running any version.
However, this does not apply if the multi-subsystem operations provided by the Enterprise Edition of Systemwalker Operation Manager are used. The tables below show the combinations where network jobs can be executed.
| Destination of request | |||||
|---|---|---|---|---|---|---|
V10.0L10/5.2 to V13.2.0 | V13.3.0 and later | |||||
No multi-sub system operation/Subsystem 0 | Sub | No multi- | Sub | |||
Source of request | V10.0L10/ | No multi-subsystem operation/Sub | A | C | A | C |
Subsystems 1 to 9 | C(*1) | A | C(*1) | A | ||
V13.3.0 | No multi-subsystem operation/Sub | A | C | B | ||
Subsystems 1 to 9 | C(*1) | A | ||||
A: Can send an execution request to the same subsystem number
("No multi-subsystem operation" is handled in the same way as when "Subsystem 0" is specified)
B: Can send an execution request to any subsystem
C: Cannot send an execution request
Can send an execution request when no port number is specified by the requesting source (the schedule server)
This does not apply to AIX versions of Systemwalker Operation Manager 11.0 and earlier.
Note
When submitting network jobs from the schedule server in a new version to the execution server in an old version, the character limit for setting items must follow the one used in the old version.
Refer to "Upgrading Notes and Incompatible Items" in the Systemwalker Operation Manager Upgrade Guide for compatibilities for the character limit of setting items.
