Sysplex considerations when using scheduled services

Assume you are logging space data on more than one system (SYSA and SYSB) and you want to create capacity planning records for each. If you share the SMSCHDxx member between these systems and leave the CAPPLAN DAILYSUM interval definition as it is defined ('*' for system affinity), the command will execute on both SYSA and SYSB, creating the capacity planning records on both systems. In this example, sharing the SMSCHDxx member and using the asterisk (or masking) in the interval definition is advantageous because you do not need two intervals defined in a member that executes the same command. The one interval that is defined is used on both systems.

In contrast, however, if you were issuing a command that refreshed one of the SVOS PARMLIB members or if you were issuing the VSCAN command, sharing the SMSCHDxx member and using asterisk or masking could cause an error or duplicate processing. The timing of a refresh command to a member across systems could be critical; running a VSCAN against the same volumes on multiple systems is more overhead than necessary (assuming the same SMVSCFxx member is also used).