Restriction on deployment directory length

The deployment utility uses the APPLICID attribute of the runmqsc DEFINE PROCESS command to contain a command to start the listener. This will have the name of the deployment directory embedded in it. WebSphere MQ imposes a maximum length of 256 on the APPLICID field which in turn means there is a limit on the maximum length of the deployment directory.

For Java services, this limit is as follows:

For .NET services the limit is

where "service_name" is the name of the input service file without any extension. (For example, "StockQuoteDotNet.asmx" would have a service name of StockQuoteDotNet, which has a length of 16 characters, and so the corresponding maximum deployment directory length would be 193).

If you are using triggering, the deployment utility checks whether the limit for APPLICID is exceeded. If the limit is exceeded, the utility does not attempt to define the triggering process; it displays an error message and the deployment process fails with no deployment steps having been taken.

For more information on the DEFINE PROCESS command, see WebSphere MQ Script (MQSC) Command Reference.