scsi inquiry command

Sidanat,

Just curious, what prompted you to look into this tool?  It is an informational tool, and is also one of several tools bundled and run as part of the host grab utilities (EMC Grab and EMCReports).  To answer your question as to whether or not you need it, what were you looking to accomplish?   Possibly help mapping the OS device reference/name back to the array component (not limited to Symmetrix)?  As noted from within PowerLink:

Home > Support > Product and Diagnostic Tools > INQ Utility

The Inquiry utility (INQ) is a command-line troubleshooting utility that displays information on storage devices, typically Symmetrix. By default, INQ returns the device name, Symmetrix ID, Symmetrix LUN, and capacity. This utility will operate independently of any other EMC software. Use the INQ Utility to collect system information to provide to EMC Global Services for problem troubleshooting. The latest versions for supported operating systems can be found on EMC's ftp server at ftp://ftp.emc.com/pub/symm3000/inquiry/.

is that true the emcreports run "chkdsk /F"  by default? I dont want to run a chkdsk on a mounted partition unless i do purpose, but not while i run emcreports

No, the EMCReport grab utility does not (at least currently) run chkdsk, nor imo ever expect it to, at least by default, as it would be too intrusive as you also are suggesting with your question.  The closest it does is look for existing (Cluster) CHKDSK logs and will include them in the final bundle.

There is full-disclosure to what is run/gathered as a result of running the utility and you have several options:

1) Review the README.TXT file which is alongside the executable in either of the following locations:

b) or the ftp repository

ftp://ftp.emc.com/pub/emcgrab/Windows

echo [%TIME%].......Checking for Cluster CHKDSK logs
CD /d "%systemroot%\Cluster"
FOR %%i IN (ChkDsk*.* ) DO type %%i >> %EMCReports%\CLUSTER\%COMPUTERNAME%_%%i_CLUSTER_CHKDSK.LOG

As you've probably already figured out from reviewing the snippet of code, this script is only looking for existing (cluster) chkdsk logs and if found, writes (type) the contents to its own log for inclusion in the final bundle.

As for extracting the emcrpt.cmd script, you have several options, and since you'll want to review it before you run it...

1) Use an extract utility that can rip open .EXE's such as 7-Zip

2) Use the switch "/c" which generally works for most Windows executables (prompts you for a directory to extract it to)

%SYSTEMROOT%\Emcreports\bin\