acpload.cmd fails with the following error The input line is too long Technote
(troubleshooting)Problem(Abstract) You run acpload.cmd on Windows . The command fails with the following error message:
The input line is too long.Cause The Windows operating system has restrictions on the number of characters in the command line call:
- Under Windows NT , the command line is limited to 256 characters.
- Under Windows 2000, the command line is limited to 2046 characters.
- Under Windows XP, the command line is limited to 8190 characters.
The acpload.cmd calls the WC/bin/setdbenv.db2.bat to set the Java™ class path prior to executing the Java class. This script sets the path (the %CP% environment variable) to almost 2000 characters by default, so once the Java call is made with this class path, the command line grows to longer than 2046 characters on Windows 2000.Resolving the problem There are two possible workarounds for this problem:
- Option 1
Comment out the last two lines that add to the CP variable in the current WC/bin/setdbenv.db2.bat when running any acp*.cmd:
set CP5=%WCS_HOME%\wc.ear\Enablement ....
set CP6=%WCS_HOME%\wc.ear.ext\ .....
These lines are not needed for the acpload tool or any other acp* tool. Comment those two out before running acpload, then place them back in case you run other WC/bin tools that need them.
- Option 2
- Create a copy of the setdbenv.db2.bat script (for example, call it setdbenv.db.acp.bat), and place it in the same directory.
- Remove the two aforementioned lines.
- Change the references in the WC/bin/acpload.cmd file to now refer to the new setdbenv copy, which does not have the last two lines of the class path (CP).
For example, replace these two lines in acpload.cmd:
:db2dbenv
call setdbenv.db2.bat
with:
:db2dbenv
call copied_setdbenv_script.bat
where the copied setdbenv script is one without CP5 or CP6 being set.
Scripts other than acpload.cmd may fail for the same reason. Any access control policy script (prefixed 'acp' in WC/bin) can use the same solution above. Other utilities besides the ACP ones may need the last two lines of the %CP% environment variable to function correctly. If another script fails for the same reason, contact IBM WebSphere Commerce Support.
Cross Reference information
Segment Product Component Platform Version Edition Commerce WebSphere Commerce - Express Utilities/Tools Windows 6.0 Commerce WebSphere Commerce Professional Edition Utilities/Tools Windows 6.0
Document Information Current web document: http://www.ibm.com/support/docview.wss?uid=swg21244103