| Author | 
		  Message
		 | 
		
		  | aks | 
		  
		    
			  
				 Posted: Tue Jul 19, 2005 5:49 pm    Post subject: Trigger problem with MQ 5.3 CSD4 on Windows 2000 | 
				     | 
			   
			 
		   | 
		
		
		   Voyager
 
 Joined: 19 Jul 2002 Posts: 84
  
  | 
		  
		    
			  
				I hava a Windows bat file  that does not run when triggered. The bat file runs a Java program that has all correct paths and classpaths and executes OK from the command line. When I run the trigger monitor runmqtrm from the command line, when triggered, this error message occurs:
 
 
The input line is too long
 
The syntax of the cmmand is incorrect
 
Error starting triggered application
 
 
This same triggered process runs OK in our production environment. The path on the production server to the batch file is identical to the server with the problem.
 
 
Any suggestions?
 
Thanks
 
Alan | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | malammik | 
		  
		    
			  
				 Posted: Tue Jul 19, 2005 6:21 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Partisan
 
 Joined: 27 Jan 2005 Posts: 397 Location: Philadelphia, PA 
  | 
		  
		    
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RogerLacroix | 
		  
		    
			  
				 Posted: Tue Jul 19, 2005 6:44 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 15 May 2001 Posts: 3265 Location: London, ON  Canada 
  | 
		  
		    
			  
				All,
 
 
On Windows, a command must be less than 255 characters.  This includes:
 
- the path & executable name (i.e. java)
 
- JVM paramters
 
- and the MQTMC2 strcuture that is passed.
 
 
Did you Google those error messages?
 
 
Regards,
 
Roger Lacroix
 
Capitalware Inc. _________________ Capitalware: Transforming tomorrow into today.
 
Connected to MQ!
 
Twitter | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | aks | 
		  
		    
			  
				 Posted: Tue Jul 19, 2005 7:29 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Voyager
 
 Joined: 19 Jul 2002 Posts: 84
  
  | 
		  
		    
			  
				No, I didn't Google the error messages, as the same command is working OK in producton and our development environment. The problem is occurring in our test environment, which is running identical levels of software.  Moreover I counted the length of the command and it is less than 255 characters. Hence my post here.
 
 
I'm thinking some sort of corruption
 
Alan | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | RogerLacroix | 
		  
		    
			  
				 Posted: Tue Jul 19, 2005 7:53 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 15 May 2001 Posts: 3265 Location: London, ON  Canada 
  | 
		  
		    
			  
				aks,
 
 
I am willing to bet that some of your environment variables are different between your servers.  
 
 
Start  runmqtrm again and do your test again.  Then use the BBCodes of [code] and [/code]  and copy & paste the EXACT output, include EVERYTHING, from the command prompt.  Do not edit it.
 
 
Regards,
 
Roger Lacroix _________________ Capitalware: Transforming tomorrow into today.
 
Connected to MQ!
 
Twitter | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | aks | 
		  
		    
			  
				 Posted: Tue Jul 19, 2005 10:52 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Voyager
 
 Joined: 19 Jul 2002 Posts: 84
  
  | 
		  
		    
			  
				We had a deployment to our test environment today and all seems to work now with triggering!
 
 
I redeployed the following batch file which is run on the trigger (which is identical to the previous one), but also a new version of the MQSI bar file which writes the messages to the queue with the trigger on it. 
 
 
Figure that one out!
 
 
Thanks for the input
 
Regards
 
Alan
 
 
   
	| Code: | 
   
  
	@echo off
 
 
::----------------------------------------------------------------------
 
:: au.com.zurich.integration.zstreamxa.batch.Export Startup Script
 
::----------------------------------------------------------------------
 
 
SET HOME=D:/win32app/Zurich/Adapters/MessageDaemon
 
SET JAVA_EXE=D:/win32app/j2sdk1.4.2/jre/bin/java.exe
 
SET MQJAVA=D:/win32app/MQSeries/Java/lib
 
SET CTGJAVA=D:/win32app/Zurich/Adapters/MessageDaemon/lib
 
SET CTGBIN=D:/win32app/Zurich/Adapters/MessageDaemon/lib
 
SET DB2JAVA=D:/Win32app/IBM/SQLLIB/java
 
SET JAVA_LIB_PATH=%MQJAVA%;%CTGJAVA%;%CTGBIN%
 
 
SET CLASS_PATH=.
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/log4j.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/commons-lang.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/commons-codec.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/xml-apis.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/xercesImpl.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/xalan.jar
 
SET CLASS_PATH=%CLASS_PATH%;%MQJAVA%/jms.jar
 
SET CLASS_PATH=%CLASS_PATH%;%MQJAVA%/com.ibm.mq.jar
 
SET CLASS_PATH=%CLASS_PATH%;%MQJAVA%/com.ibm.mqjms.jar
 
SET CLASS_PATH=%CLASS_PATH%;%MQJAVA%/connector.jar
 
SET CLASS_PATH=%CLASS_PATH%;%MQJAVA%/jta.jar
 
SET CLASS_PATH=%CLASS_PATH%;%CTGJAVA%/ctgclient.jar
 
SET CLASS_PATH=%CLASS_PATH%;%CTGJAVA%/ctgserver.jar
 
SET CLASS_PATH=%CLASS_PATH%;%DB2JAVA%/db2jcc.jar
 
SET CLASS_PATH=%CLASS_PATH%;%DB2JAVA%/db2jcc_license_cu.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/au.com.zurich.util.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/lib/au.com.zurich.integration.jar
 
SET CLASS_PATH=%CLASS_PATH%;%HOME%/conf/zstreamxa
 
 
SET MAIN_CLASS=au.com.zurich.integration.zstreamxa.batch.Export
 
 
%JAVA_EXE% -Xms128m -Xmx512m -Dlog4j.configuration=log4j-export.properties -Djava.library.path=%JAVA_LIB_PATH% -cp %CLASS_PATH% %MAIN_CLASS% %1 | 
   
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |