All the time than not you can keep running into issues when running batch documents and frequently than not you would need to troubleshoot your bunch records somehow or the other to decide the issue with the clump document itself. Following are a portion of the procedures that can help in investigating Batch Script documents.
To discover the source of the message, follow these steps −
Step 1 − REM out the @ECHO OFF line, i.e. REM @ECHO OFF or :: @ECHO OFF.
Step 2 − Run the batch file with the required command line parameters, redirecting all output to a log file for later comparison.
Step 3 − Search the file batch.log for the error messages
Step 4 − Check the previous line for any unexpected or invalid command, command line switch(es) or value(s); pay special attention to the values of any environment variables used in the command.
Step 5 − Correct the error and repeat this process until all error messages have disappeared.
Another common source of errors are incorrectly redirected commands, like for example "nested" FIND or FINDSTR commands with incorrect search strings, sometimes within a FOR /F loop.
To check the validity of these complex commands, follow these steps −
Step 1 − Insert "command check lines" just before a line which uses the complex command set.
Following is an example wherein the ECHO command is inserted to mark where the output of the first TYPE command ends and the next one starts.
Step 2 − Follow the procedure to find error message sources described above.
Step 3 − Pay special attention to the output of the "simplified" command lines: Is the output of the expected format? Is the "token" value or position as expected?
Subroutines generating error messages pose an extra "challenge" in finding the cause of the error, as they may be called multiple times in the same batch file.
To help find out what causes the incorrect call to the subroutine, follow these steps −
Step 1 − Add and reset a counter variable at the beginning of the script –
Step 2 − Increment the counter each time the subroutine is called, by inserting the following line at the beginning of the subroutine
Step 3 − Insert another line right after the counter increment, containing only the SET command; this will list all environment variables and their values.
Step 4 − Follow the procedure to find error message sources described above.
If you mean to allocate your batch files to other computers that may or may not run the same Windows version, you will need to test your batch files in as many Windows versions as possible.
The resulting instance demonstrations how to check for various operating system versions to check the relevant windows versions.
ECHO Sorry, this batch file was written for Windows XP and later versions only
All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.