Problem: 

The standard command DXESTART supplied with the product:

    -  does not support parameters passing connection information about the input and output data stores,

    -  does not give a specific number of steps to be processed when a method is exported via the Distributed Exporter and run via the DE Extension.  

This  creates  difficulties  for some customers with strong  security requirements  who use scripts for batch processing.   

 Resolution:

New parameters  are added to the command  DXESTART  to satisfy  the customers’  needs and specific steps can be exported via the Distributed Exporter.  These parameters are valid for Oracle and ODBC Extension.    

The new command syntax is:     

 dxestart   -d <path>   -i<input method.rc>  -o<output method.rc>  -f < nr. Step from>  -t < nr. Step to>  -l <path>        

  where:  

 -d <path>

-d means that the methdo.rc  file  is read from the directory specified in  the parameter  <path>.  If such an option is not specified  Data Express will use  the default configuration  directories.   

 Example 1:

 dxestart   -d “C:\\Testlib1”

The process will read  the connection information from the file method.rc  located  in the directory  C:\\Testlib1\\config  and  will create the produced log and statistic files   in the directory  C:\\Testlib1\\log.  

 -i<input method.rc>    

 -i  means that the  input  connection information is read  from a different  ''InputFileName.rc''  file,  similar to the method.rc file.  The name and the path to the new .RC file  can be specified in this parameter.   

 -o<output method.rc>  

 -o  means that the output  connection information is read  from a different  ''OutputFileName.rc''  file,  similar to the method.rc file.  The name and the path to the new .RC file  can be specified in this parameter.   

 Example 2: 

 dxestart   -d   “C:\\Testlib1” -i “C:\\Testlib2\\method1.rc” -o “C:\\Testlib3\\method2.rc”   

 The process will read  the input connection information from  the file  method1.rc  placed in the folder C:\\Testlib2,  the output connection information from  the file method2.rc  placed in the folder  C:\\Testlib3, the exported configuration information from the folder  C:\\Testlib1\\config  and will  create  the produced log and statistic  files in the folder  C:\\Testlib1\\log. 

  -f< nr. Step from>     

  -f  means that the step number to start the elaboration can be specified manually.       

  -t < nr. Step to> 

  -t  means that the step number to end the elaboration can be specified manually.

Example 3:

a)  dxestart   -f 20  -t 20  

The process will read  the connection information from the file method.rc  located  in the default Data Express directory and  will create the produced log and statistic files  in the default directory.  All tables included  into step 20 will be processed. 

 b)  dxestart   -d   C:\\Testlib1  -f 20  -t 30  

The process will read  the connection information from the file method.rc  located  in the directory  C:\\Testlib1\\config and  will create the produced log and statistic files into directory  C:\\Testlib1\\log.  All tables  from step 20 to step 30  will be processed. 

 c)  dxestart   -d   C:\\Testlib1 –i C:\\Testlib2\\method1.rc  -o  C:\\Testlib3\\method2.rc   -f 30   -t 60

The process will read  the input connection information from  the file  method1.rc  placed in the folder C:\\Testlib2,  the output connection information from  the file method2.rc  placed in the folder  C:\\Testlib3,  the exported configuration information from the folder  C:\\Testlib1\\config  and will  create  the produced log and statistic  files in the folder  C:\\Testlib1\\log.  All tables from step 20 to step 60 will be processed.

   -l <path>

   -l  specifies the path where the log file will be created.  If the specified folded does not exist the process will create it.  If the  parameter  -l  is not specified  the process will use  the default configuration log directories. 

  Example 4:

  dxestart   -l   " C:\\Test LogFolder"   

 The process will create the log file in the directory specified in  the path  "C:\\Test  LogFolder".

In order to create  the input  and the output  .RC files follow the steps below:        

 1.  Create .INI  flat files,  named  InputFileName.ini  for the input connection information and OutputFileName.ini  for the output connection information.        

2.  Specify the appropriate connection parameters  below and  comma  ","  as  a  delimiter.  Two formats are valid.   

     -  for the input file:  

     Connection Type (ODBC or ORACLE),Input Connection Alias,Input Schema,Input Userid,Input Password

     or

     Connection Type (ODBC or ORACLE),Input Connection Alias,Input Schema,Input Userid,Input Password,,,,

     -   for the output file:   

     Connection Type (ODBC or ORACLE),Output Connection Alias,Output Schema,Output Userid,Output Password

     or 

     Connection Type (ODBC or ORACLE),Output Connection Alias,Output Schema,Output Userid,Output Password,,,,

 3.  Encrypt  the .INI files  using the command:  dxeencrypt.exe  FileName