DOS Batch - Interfacing non DOS Software | Embed other languages into your batch, like: Perl, SQL, FTP, ... |
FTP - Automatic Login | Automatically login to your FTP session with a single click. |
FTP - Resolving Environment Variables | Creating FTP script on the fly at runtime and using variables within the FTP script. |
FTP - Simple Single Batch | FTP script and batch in a single file. |
FTP Scripts Sharing Login Info | Manage the FTP login separately from your FTP scripts. |
OSQL.EXE - Run SQL script from DOS Batch | SQL script and dos batch script in one file, the One-File Solution |
OSQL.EXE - Run SQL script from DOS Batch, passing parameters | Run SQL scripts with parameters passed in from the batch script. |
Perl - Perl Script within a DOS Batch | Perl script and batch in a single file. |
Perl Script within a DOS Batch with delayed exit | Perl script and batch in a single file. |
Description: | If you frequently find yourself calling FTP from the command line, each time having to login and change directory and change FTP modes, until you finally get where you want be in order to do some real work then you may wish to get there with a singe click. This little batch can connect to your FTP server and logs you in before it gives you the prompt. You can easily add more FTP commands to it, like changing directories or switching to binary mode or whatever you like to be done before taking over control on the FTP prompt. The FTP connection information is embedded within the batch itself. The batch connects to an FTP server by executing itself in FTP context using the FTP -s option. Once executing in FTP context it executes all FTP commands listed in the file. By omitting the final FTP "bye" command it will stop at the FTP prompt and wait for user input. Optionally a FTP script can be provided as input stream, that way multiple FTP scripts can share the same login information. Example: FtpLogin.bat <script1.ftp |
||
Script: | Download: FtpLogin.bat
|
||
Script Output: |
|
Description: | This batch executed the FTP script embedded within the batch. All variables in the FTP script will be resolved. The FOR loop extracts the FTP script into a temporary file. It the ECHO command is being CALLed for each line in order to resolve the variables. Variables can be used within the FTP script the same way as in a batch script, including any string manipulation and command line arguments like %1 %2 %~n0 %* and so on. All batch lines start with semicolon so that they will be ignored by the FOR loop. Semicolon is the default end-of-line (EOL) character used by the FOR command. |
||
Script: |
|
Description: | Embed FTP script into a batch script. Add this line at the beginning of the FTP script: @ftp -i -s:"%~f0"&GOTO:EOFThe "FTP -s:ftpscript.txt" option executes a FTP script wheres "%~f0" resolved to the name of the running batch file.
"GOTO:EOF" ends the batch script and makes sure the FTP script doesn`t run as part of the batch.
|
||
Script: |
|
||
Script Output: |
|
Description: | If you have multiple FTP scripts that all use the same login information to your FTP site then you may wish to manage the login information separately from your FTP scripts in a single place. That way if the username, password or hostname for the FTP connection changes you only need to edit a single place instead of having to edit all FTP scripts one by one. This automatic login script (also described in detail earlier) can be used to execute different FTP scripts that share the same login information stored within the batch file. Example: FtpLogin.bat script1.ftp Note: The FTP scripts passed into the batch must have the login sequence removed. Note: The FTP script executes even if the connection sequence fails potentially causing `Not connected` and other errors. This is no different from regularly executing FTP with -s option. |
||
Script: | Download: FtpLoginSharing.bat
|
Description: | Embedding SQL script within a batch script is just as easy. The following batch script executes itself in SQL context. The trick is the GOTO command in the first line of the script. When executing GOTO START in batch context than the command processor will jump to the label ":START" and execute the batch script. The batch script will then run the OSQL.EXE using the batch file itself as SQL file argument to be executed. When subsequently executing the GOTO START line in SQL context, the query language processor will jump to the label "START:" and execute the SQL queries. In fact the file can be opened and executed in Query Analyzer as is, since the batch script in the file looks like a comment to the query language processor. |
||
Script: | Download: Batch4SQL.bat
|
Description: | Now we can embed SQL queries into a batch file. But how can we pass arguments from the batch script into SQL? This can be done using a temporary table. Temporary tables live as long as the connection to the SQL Server. But how can we fill a temporary table with runtime data and execute the embedded SQL script without creating two separate SQL Server connections by calling OSQL.EXE twice? The trick is that OSQL allows to use the -i and -q option at the same time whereas:
|
||
Script: | Download: Batch4SQL2.bat
|
Description: | It`s nice not to have to type "perl -s Batch4Parl.pl" into the command line and rather being able to just double click a Perl script in Explorer. The trick of renaming the Perl .pl to a batch .bat file and wrapping a batch script around the Perl script is well known under Perl monks. However the solution I have seen so far needed batch code before and after the Perl script where as the solution presented below only needs some lines of DOS at the top. The added DOS script is generic and works independent from the name of the file. When running the batch the DOS command interpreter will read the first lines and execute the file itself in Perl context. |
||
Script: | Download: Batch4Perl.bat
|
Description: | This example works just as the previews one but will wait 4 seconds before the application finally closes. This is just enough time to inspect the screen output before the window vanishes. The delay can probably be done much easier in Perl, but somebody just starting on Perl might find this still useful. |
||
Script: | Download: Batch4Perl2.bat
|