The pcmserve.ini file resides on the mileage PC in the c:\windows or the c:\winnt folder. Values specified in pcmserve.ini will be used unless they are otherwise specified in the mileage request packet. PC*MILER|Streets uses pmwssrv.ini, and has a few additional key values included at the bottom of the chart below.
Valid values for default and option settings in the pcmserve.ini that can be changed by the user are described below.
Valid Values (Defaults)
Not supported by PC*MILER for the AS/400. If routing type is not specified, the default route type of Practical will be used.
Which unit of measure for distance.
When optimizing the route, should the trip’s destination be optimized also.
Should the engine try to keep routes within the United States (F), or can they cross and recross the borders at will (T)
Calculate the routes from the origin to each stop (T), not through each stop (F).
List the states in the State Report in alphabetical order, or in the order driven.
Use ferry distances in mileage and cost calculations (T), or don’t use (F).
Should Custom routing be used.
The default hazardous routing type: disabled, general material, explosive, inhalant, radioactive, corrosive, or flammable.
Set to TRUE (T) for light vehicle routing and restriction overrides; FALSE (F) = heavy vehicle routing and obey restrictions.
Require exact match on city name strings (T) or match on partial city names (F). Primarily used for long city names like “Naval Shipyard Portsmouth N0018, VA, Portsmouth”.
When set to TRUE, if a 5-digit postal code might be a U.S. or a Mexican code, the U.S. code will be used. Default = True
When set to TRUE, if a 5-digit postal code might be a U.S. or a Mexican code, the Mexican code will be used. Default = False
NOTE: If UseUSPostCodes and UseMexPostCodes are both FALSE, or are not in the .INI, the default U.S. code will be used.
Should street-level (T) or highway-only (F) routing be used when stops are city names or ZIP codes.
Set to (T) to match address on road name only.