I have found that one process failed until I changed the from lower case to mixed case in a windows batch job (v6.3.01). Specifically, a file name was in mixed case on the system. My friend didn't believe case made a difference on a Windows server - however the process succeeded with the simple change of case to match in the batch job with the file on disk.
Is Control-M Case sensitive in some conditions on a MS Windows platform?
Case Sensitive
-
richardoku
- Nouveau
- Posts: 20
- Joined: 11 Mar 2008 12:00
Hello
Control-M is case-sensitive for Job/Memnames, Conditions and so on. However Filenames on Windows e.g. JoB_bATch.bat will be found by Control-M jobs trying to execute a Filename=Job_BatcH.bat!
If you would try to define both files JoB_bATch.bat & Job_BatcH.bat under windows explorer you would get an error 'file JoB_bATch.bat already exists'.
That leaves a curious situation, can you give some more details on what you had and what you had to change?
Thanks in advance!
Regards
Control-M is case-sensitive for Job/Memnames, Conditions and so on. However Filenames on Windows e.g. JoB_bATch.bat will be found by Control-M jobs trying to execute a Filename=Job_BatcH.bat!
If you would try to define both files JoB_bATch.bat & Job_BatcH.bat under windows explorer you would get an error 'file JoB_bATch.bat already exists'.
That leaves a curious situation, can you give some more details on what you had and what you had to change?
Thanks in advance!
Regards