Best Practices for Backup Procedures for XCOM for AS/500
search cancel

Best Practices for Backup Procedures for XCOM for AS/500

book

Article ID: 23684

calendar_today

Updated On:

Products

XCOM Data Transport

Issue/Introduction

What components should be backed up for XCOM™ Data Transport® for AS/400 i5/OS and when.

 

Environment

XCOM™ Data Transport® for AS/400 i5/OS

Resolution

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

Monthly
  • Take a full XCOM Data Transport backup at times when XCOM Data Transport is stopped. This should be at least monthly when the AS/400 is IPLed, or some other time when XCOM Data Transport is down.
Daily
  • As the 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 XCOM Data Transport with current queue, logs and transfer ID)

    To restore 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.
  • XCOMLOG (if still in use)

    Use the LOGSIZEUPD command.. 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.