Consider the following issues for automatic reloading:

• You cannot schedule 2 load modules for the same communication controller unit to be loaded within 5 minutes of each other.
• A 3745 Communication Controller can have two central controller units. You cannot load one central controller unit using a scheduled automatic reload while the other central controller unit is waiting to be loaded.
• If MOSS goes down after you have scheduled an automatic reload, one of the following occurs:
  • If MOSS returns online after the time for the scheduled reload, the scheduled reload is canceled. No alert is sent.
  • If MOSS returns online before the time for the scheduled reload and the time to send the alert has passed, MOSS performs the reload as scheduled and an alert is sent if possible.
  • If MOSS returns online before the time to send the alert, MOSS sends the alert and performs the reload as scheduled.
• If you schedule an automatic reload with a load module that contains errors, MOSS attempts to load the load module again before failing the load.
• If you have more than one VTAM® that owns a remote 3745 communication controller, consider the following situations:
  • It is possible for a person at each VTAM to set different scheduled automatic reloads for the same load module. If this happens, the scheduled automatic reload set by one VTAM can be written over by the other VTAM. MOSS performs the reload at the last time set for the load module.
  • If MOSS receives a command to purge a load module that has a scheduled automatic reload, MOSS cancels the scheduled reload and purges the load module. No message is sent to the VTAM that scheduled the reload.
  • If MOSS receives a command to replace a load module that has a scheduled automatic reload, MOSS replaces the load module and cancels the scheduled reload. No message is sent to the VTAM that scheduled the reload.
• AUTODMP and AUTOIPL operands on the PCCU definition statement are always set to YES after a scheduled automatic reload. For more information about these operands, see the z/OS Communications Server: SNA Resource Definition Reference.
• If the time you specify for the IPL time is the same as the current system time, MOSS does not IPL.
• If you set the IPL time for more than 15 days in advance, you might encounter minor MOSS clock deviations. However, if this is not a problem, then you can set the IPL time up to 90 days in advance.