windows script to Unix

ETC Microsoft Windows
1

Dear All,

I am looking to understand the feasabilities to migrate the following batches command line into Unix plateform. If yes anyone can do it ?

UDB_import_AAA.bat

del /Q %VMAPdir%\Excel_files\*.*
del /Q %VMAPdir%\Log\*.*
del /Q %VMAPdir%\Output\*.*
del /Q %VMAPdir%\Reports\Input\*.*
del /Q %VMAPdir%\Reports\OutputCSV\*.*
rmdir /Q /S %VMAPdir%\Reports\Output
mkdir %VMAPdir%\Reports\Output

IF "%2"=="BE" GOTO BE_FOLDERS

:BE_FOLDERS
mkdir %VMAPdir%\Reports\Output\Risk
copy %VMAPdir%\Params\Readme.txt %VMAPdir%\Reports\Output\Risk
mkdir %VMAPdir%\Reports\Output\Other
copy %VMAPdir%\Params\Readme.txt %VMAPdir%\Reports\Output\Other
GOTO Launch_IMPORT

:Launch_IMPORT
@call "%sasdir%\sas.exe" -noautoexec -nosplash -dmsbatch -icon -sysin %VMAPdir%\SASCODE\Batch\UDB_import_AAA.sas -sysparm "%1 %2"

@if %errorlevel%==0 echo RC=%errorlevel%

UDB_CREATOR.bat

@call "%sasdir%\sas.exe" -noautoexec -nosplash -dmsbatch -icon -sysin %VMAPdir%\SASCODE\Batch\UDB_CREATOR.sas -sysparm "%1 %2"

rem TO DELETE IN NEXT RELEASE !!!!!!!!
copy %VMAPdir%\Output\init\paramMarketData_multi.xml %VMAPdir%\Output\paramMarketData_multi.xml

@if %errorlevel%==0 echo RC=%errorlevel%

XML_EXTRACT.bat

@call "%sasdir%\sas.exe" -noautoexec -nosplash -dmsbatch -icon -sysin %VMAPdir%\SASCODE\Batch\XML_EXTRACT.sas -sysparm "%1 %2"

@call "%sasdir%\sas.exe" -noautoexec -nosplash -dmsbatch -icon -sysin %VMAPdir%\SASCODE\Batch\RPA_Report.sas -sysparm "%1 %2"

@if %errorlevel%==0 echo RC=%errorlevel%

ETL_import_FTB.bat

@call "%sasdir%\sas.exe" -noautoexec -nosplash -dmsbatch -icon -sysin %VMAPdir%\SASCODE\Batch\ETL_import_FTB.sas

@if %errorlevel%==0 echo RC=%errorlevel%

2

With the exception of the sas.exe lines, all the lines convert easily.
Do the following:
replace all \ with /
replace all %xxx% with $xxx
replace "del /q" with "rm"
make sure none of your file names have embedded spaces, or special characters.
mkdir is mkdir
rmdir is rmdir
replace the "if goto" construct with "if ....endif".

An alternative is to use a product like Samba on the unix system, export a share, and use your regular Windows script to manipulate the files.

3

even the sas bit can easily be converted to something that works under unix but for that you need to know which version and on what unix...