Scripts can be parsed on the Windows platforms at the command line or using a .bat file which inherits the working directory and other previously established environmental settings.
Example 1
Parse an engine script named DB2TOSQL that will perform near real-time replication of "Sales" application data from a DB2 database captured on a z/OS system named "MVS21" to SQL Server tables running on a Windows system. The source "Host" system and DB2 System ID will be passed as parameters because the engine script has been written so that it can be reparsed to process data coming from other systems as well.
sqdparse c:/sqdata/test/sales/ENGINE/DB2TOSQL.sqd c:/sqdata/test/sales/ENGINE/DB2TOSQL.prc list=all ENGINE=DB2TOSQL HOST=MVS21 SSID=DB2T >DB2TOSQL.rptExample 2
Batch files can be used to invoke the Parser in the Windows environment. Batch files are useful for automating the Parser processing and/or for parsing several scripts within the same command.
The following shell script parses the same script file from the previous example.
cd c:/sqdata/test/sales/ENGINE
sqdparse DB2TOSQL.sqd DB2TOSQL.prc ENGINE=DB2TOSQL HOST=MVS21 SSID=DB2T > ../DB2TOSQL.prt
cd ..Note: Since the working directory is changed to /home/test/sales/ENGINE before parsing, references in the script to the location of DB2 and SQL Server DDL table descriptions will need to be sensitive to their location in the directory hierarchy, ie: ./<directory_name>/<file_name>. In this case probably ../DB2DDL and ../SQLDDL (note the double dots).