SQData instance reference - connect_cdc_sqdata - aws_mainframe_modernization_service - Latest

AWS Mainframe Modernization Data Replication for IBM z/OS

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
AWS Mainframe Modernization > AWS Mainframe Modernization Service
Version
Latest
ft:locale
en-US
Product name
AWS Mainframe Modernization
ft:title
AWS Mainframe Modernization Data Replication for IBM z/OS
Copyright
2025
First publish date
2000
ft:lastEdition
2025-02-10
ft:lastPublication
2025-02-10T15:55:15.122000

Data and log directories

The data directory ( /var/precisely/di/sqdata) will be used to hold SQData configuration information and any intermediate information required. As such, it should be backed up to prevent loss. All engines should be defined in /var/precisely/di/sqdata/apply/<engine_name> and that directory should be specified as the working_directory in the sqdagents.cfg stanza. Use the following subdirectories for the engine:
  • scripts – To hold the SQData job script
    • /var/precisely/di/sqdata/apply/DB2ZTOORACLE/scripts/db2ztooracle.sqd
  • ddl– To hold required schema information
    • /var/precisely/di/sqdata/apply/DB2ZTOORACLE/ddl/dept_db2z.ddl
    • /var/precisely/di/sqdata/apply/DB2ZTOORACLE/ddl/dept_oracle.ddl

The log directory (/var/precisely/di/sqdata_logs) will be used to hold SQData log files from daemon controller, and any engine defined. The log directory need not be backed up as its loss will not impact processing. All engines should be defined to use /var/precisely/di/sqdata_logs/apply/<engine_name> directory for logging in the sqdagents.cfg stanza.

For example,
  • stdout_file=/var/precisely/di/sqdata_logs/apply/DB2ZTOORACLE/stdout.txt
    • This file is empty and will keep a note any user inputs before the task is started.
  • stderr_file=/var/precisely/di/sqdata_logs/apply/DB2ZTOORACLE/stderr.txt
    • This file, initially empty, serves as a repository to log any errors that might occur, causing the task to halt or fail. Furthermore, it will document the final output upon task completion (user interrupt/stop).