IBM Workload Automation & Workload Scheduler

IBM Workload Automation & Workload Scheduler

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  TWS historical data

    Posted Thu March 12, 2026 09:07 PM

    Dear Everyone,


    We having a doubt here.

    We currently in tech refresh to change the current TWS physical server to the new VM server. And we setup/install TWS everything new in the VM server.

    The question is how will we want to retrieve the historical data from current TWS physical server and then transfer into the new VM server?

    We have tried to copy the schedlog(/opt/ibm/TWA/wa/TWSDATA/schedlog) from current TWS physical server into the new VM TWS server but no luck.
    When we open the imported sched from current TWS physical server into the new VM TWS server at the DWC console, the error popup saying "AWSJSY514E The Symphony plan operation "queryJobStreams" cannot be performed because the Symphony file "M202508300459" cannot be opened." (as attached)

    Is there any other way that this historical data are able to load into the new VM TWS server?



    ------------------------------
    Mohd Shahreen Izwan Ridzuan
    ------------------------------


  • 2.  RE: TWS historical data

    Posted Tue March 24, 2026 12:32 AM

    Dear Everyone,

    Does anyone know on this and able to share how to achieve it?
    I'm still not find a way to solve it.

    thanks.



    ------------------------------
    Mohd Shahreen Izwan Ridzuan
    ------------------------------



  • 3.  RE: TWS historical data

    Posted Tue March 24, 2026 06:10 AM

    Hi!

    You can copy both the current and archived Symphony files to the new server. However, simply placing them in the directory is not enough, as these files are encrypted using the security keys from the original physical environment.
    To ensure the new VM can decrypt these files, follow this procedure:

    • Migrate security keys: copy the entire contents of the <TWSDATA>\ssl\aes directory from the old physical server to the corresponding directory on the new VM.
    • Migrate symphony files: copy the Symphony files to their designated directory on the new server.
    • Restart services: once the files and keys are in place, perform a full restart of the environment (shut down and restart all services) to initialize the configuration.

    Anyway we recommend that you are running at least V10.2.4 or 10.2.5.

    Please note that this procedure is intended for a clean installation on the new VM. If you have already archived plans on the new server, changing these keys will make those existing files unreadable.

    If the procedure does not resolve the issue, we request that you open a support case. This will allow us to gather all necessary environment details to track the problem through to a full resolution.

    Regards,

    Veronica Tesei



    ------------------------------
    Veronica Tesei
    ------------------------------