Best Practices for Backup Procedures of CA XCOM Data Transport for I5/OS (AS400).

Document ID : KB000023684
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction: 

What components should be backed up for CA XCOM Data Transport and when.

Instructions: 

    Minimal Backup Requirements (Minimum needed to bring up CA XCOM Data Transport from Backup)

Monthly
  • Take a full CA XCOM Data Transport backup at times when CA XCOM Data Transport is stopped. This should be at least monthly when the AS/400 is IPLed, or some other time when CA XCOM Data Transport is down.
Daily
  • As the CA XCOM Data Transport configuration could change daily, there is a need to backup XCOMCNFG daily. That will be enough to save the configuration changes.

     Together with a monthly backup this is enough to restore a working system.

    Full Backup Requirements (To restore CA XCOM Data Transport with current queue, logs and transfer ID)

    To restore CA XCOM Data Transport to its present state including transfer request number and queue, the following additional files must be backed up.

Daily or Automatic
  • XCOMRQNO and XCOMXMTQ
  • Detail Log

    The detail log is already on automatic backup if you have specified *CNTRLD and FILE *AUTO on the CHGDLOG command, (see Chapter 6 of the CA XCOM Data Transport for AS/400 User Guide release 11.0 You will need to search for it.).
  • XCOMLOG (if still in use)

    Use the LOGSIZEUPD command (see Chapter 2 in the CA XCOM Data Transport for AS/400 User Guide 11.0 You will need to search for it.). Then change the XCOMLOG to reuse deleted records with:

    CHGPF FILE(XCOM2/XCOMLOG) REUSEDLT(*YES)

    If REUSEDLT records are set, the records will automatically overwrite the oldest one, so no maintenance is required.