These files belong to the Blog article
https://www.shortcut-it.com/blog/index.php?speed-up-the-system-refresh
which describes how the runtime of a system refresh can be optimized. 
Feel free to use them, they can be easily adapted to your needs. 

You need to check / adjust some paths:
- the path to the command line tool of "Shortcut for SAP systems"
  (here: C:\Programs\Sc4SAP)
- the path where the XML files are stored
  (  here: E:\SAP\System refresh\QX1\1-Prework\
           E:\SAP\System refresh\QX1\2-Postwork - Cleanup\
		   E:\SAP\System refresh\QX1\3-Postwork - Import\   )

The single XML files for the parallel tasks should be generated on the
target system, as the size of the components is used for balancing the
XML files according to the estimated runtime. 		

For each step there is an additional XML file used.
- For the prework: locking users, kicking out users, suspending batch jobs
  -> file Prepare_Export.xml
- For the cleanup: locking users, kicking out users, suspending batch jobs
    (again, because as the system at that phase has data from the target system)
  -> file Prepare_Cleanup.xml
- For the import: resetting table buffer, BDLS run, unlocking users,
    releasing batch jobs.
  -> file Import_Finalize.xml

As it is here about runtime optimization it is likely that your system contains
lots of data - otherwise it would not make sense to do some optimization. 
For processing the data DIA work processes are used. For huge components / tables
it could be that the processing time needs more time than usually allowed to
DIA WP's. There are up to 4 profile parameters containing a lime limit:
    rdisp/max_wprun_time
    rdisp/scheduler/prio_high/max_runtime
    rdisp/scheduler/prio_low/max_runtime
    rdisp/scheduler/prio_normal/max_runtime
For avoiding timeouts here the maximum runtime of DIA WP's is temporarily increased.
In the export phase it is extended to 3 hours, in the import phase to unlimited. 
After the export and after the import phase it is set back to the default value. 
See files
    ExtendMaxWPRuntime.xml  -> in the prework folder (setting max. runtime to 3 hours)
                            -> in the postwork - import folder (setting to unlimited) 
    DefaultMaxWPRuntime.xml -> in both of these folders 
and their usage in the main.cmd files.

Change the connection in these files to the same that you use in the 
generated XML files for export / cleanup / import. 
Notice that in
- Prepare_Export.xml and Prepare_Cleanup.xml a variant for program RLFW_SD_LOGOFF_USERS
    is used ('Systemrefresh'), that has to exist in the system. 
	Recommendation: create this variant in the target systems as well as in 
	the source system (in the cleanup phase, the variants in the target system 
	were copied from the source system). 
- Import_Finalize.xml a variant for BDLS is used ('Postwork SR'), that has 
    to exist in the system. As the variants from the target system are restored 
	at the time of BDLS execution, the creation of this variant in the target system 
	in front of the system refresh is sufficient.  	
  