PC*MILER|TCP/IP can be started from a command line or from a batch file. Within the Multi-Version Switch installation, each copy of PC*MILER|TCP/IP (pcmsock.exe) has been renamed to reflect the PC*MILER version it is returning mileage and routing information for. The format is pcmsockxx.exe where xx is the PC*MILER version. This enables identification of a particular version within the Windows Task Manager.
Pcmsock.exe takes two parameters, the PC*MILER package and the port number.
The PC*MILER package is PC_MILER. The convention for Port Number Assignment is for PC*MILER and PC*MILER|Streets versions to use the 8000 range with the last two digits being the version number. For example: For V20.x the default port is 8020. With both V20.0 and V20.1 installed, the default Ports would be 8020 for V20.0 and 8120 for V20.1.
Tolls versions use the 9000 range. V20.x Tolls would use 9020. If both V20.0 and V20.1 Tolls are installed V20.0 would use 9020 and V20.1 would use 9120.
Use of easy to remember conventions make troubleshooting and maintaining installations easier.
There are no hard rules for port assignments. You do need strict agreement between the port number in Pcmmv.ini and the port number that the particular version of pcmsock.exe was started with.
Pcmsock20.exe PC_MILER 8020 would be the command to start Version 20 PC*MILER|TCP/IP.
It is best to use a batch file to start the various services. Within the batch file you must change directories to the installation directory of PC*MILER|TCP/IP before launching the start command.
NOTE: If you are using a multiple PC setup, you will need to have a batch file on each PC.
Pcmsock.exe can be exited in a number of ways:
File => Exit when maximized.
Right Click => Close or Alt + F4 if minimized.
Or [right-click the Windows tool bar] Task Manager => Processes => [right-click on pcmsock.exe] => End Process.
Included in the Alkmvs.exe (or similar) is Killmvs.bat and Process.exe. Process.exe is a command line process utility that can close programs.
After copying Process.exe to C:\Windows the following sample section of Killmvs.bat would end all of the pcmsock.exe processes:
process -k pcmsock19.exe
process -k pcmsock19t.exe
process -k pcmsock20.exe
process -k pcmsock20t.exe
The syntax is process -k [Executable Name].
NOTE: Creating a shortcut to killmvs.bat on your desktop can be useful.
After starting the various instances of pcmsock.exe, you can test them.
If a particular version is failing, each PC*MILER version Tcpip subdirectory contains pcmstest.exe, which will test the PC*MILER|Connect (pcmsrv32.dll) level of the installation.
If you get an error running pcmstest.exe, it is commonly a configuration issue with the DLLPath value in that version’s pcmserve.ini file.
If the DLLPath value is valid you should then run the desktop program (pcmwin32.exe) for that version to rule out a problem with the PC*MILER Highway/Street Level databases. If pcmwin32.exe errors occur, you will have to uninstall and reinstall that version of PC*MILER.
You can also use Telnet or putty.exe to test an instance of pcmsock.exe to rule out a problem at the pcmmv.dll level:
O loopback port#
You should get ‘ALK Server Ready’ back.
You should get roughly 2800 miles back.
There is no kill command, you must exit the Telnet session.
If mvtest.exe is failing and the Telnet test is working, it could be that you need a delay in the Startmvs.bat file between the launching of the various pcmsock.exe’s.
After copying the delay.exe (included in the ALKMVS.exe) to C:\Windows:
start pcmsock19 PC_MILER 8019
start pcmsock20 PC_MILER 8020
cd \ “Program Files”\ “Alk Technologies”\pmw210\tcpip
start pcmsock210 PC_MILER 8021
‘Bind Failed’ errors are indicative of port conflicts. If you get a Bind Fail error on initial launch, you will need to change the port number for that version in pcmmv.ini and startmvs.bat.
If you are getting a Bind Failed error on a subsequent launching of a version of pcmsock.exe, it is caused by the previous instance not closing properly and it will need to be killed in Task Manager (right-click on the Windows tool bar and select Task Manager > Processes tab > [right-click on pcmsock.exe] > End Process) or by running killmvs.bat.
This installation is intended for adding PC*MILER V24 to an existing MVS AS400 Server.
On your existing MVS Server you will be installing the desktop PC*MILER program via an Install Shield setup.exe. This installation serves as the Highway Network "Database" for the MVS Server. The MVS Server portion is installed by unzipping a self extracting zip file into this installation of PC*MILER. The final part of this installation involves adding the new version to your existing pcmmv.ini, srv32.ini, killmvs.bat and startmvs.bat files.
Part One: Installing New Version of PC*MILER Software
1. Run dvd_rom\Vxxx\setup.exe
2. Your will be required to provide your 25-character product key code if installing PC*MILER 17 and up
(If you do not have the product key code, contact PC*MILER Support. It can also be located on in the Directions.txt file of your MVS disk) 3. It is strongly recommended that you install to the default location of:
PC*MILER 22 and back
C:\Program Files\Alk Technologies\PMWxxx
C:\Program Files\Alk Technologies\PMWxxx or
C:\Program Files (x86)\Alk Technologies\PMWxxx for 64-Bit PCs
PC*MILER 25 and up
C:\ Alk Technologies\PMWxxx
4. You can skip the License Activation Process at the end of the install.
5. Run DVD_ROM \MVSInstall\VxxMVS.exe. The extraction is set for the default location* (See previous step to determine default directory) *For non-default location installs redirect to the top level of your Vxx installation which will be marked by the presence of an 'App' subfolder. You will have to edit the DllPath key value in...\PMWxxx\Tcpip\pcmserve.ini. You will want the path to point to the ‘App’ subfolder.
For PC*MILER 23-24 64-Bit PCs
For 64 Bit PCs run DVD_ROM \MVSInstall\VxxMVSx86.exe the extraction is set for C:\Program Files (x86)\Alk Technologies\PMWxxx**
**For non-default location installs redirect to the top level of your Vxx installation which will be marked by the presence of an 'App' subfolder. You will have to edit the DllPath key value in...\PMWxxx\Tcpip\pcmserve.ini. You will want the path to point to the ‘App’ subfolder.
Part Two: Trouble Shooting Steps
1. Does the new desktop of the PC*MILER Program work? (pcmwin32.exe)
Try to run the interactive V24 program from the desktop icon and test that you can get a distance between two stops in a route entry window. A failure here is best remedied by uninstalling PC*MILER V24, then deleting the left over PMWxxx folder. A common cause of failure is not being logged in as an Administrator for the install.
2. Does Tcpip\pcmstest.exe work?
Via Windows Explorer browse to the ‘tcpip’ subfolder, run pcmstest.exe, and look for invalid results. Failure here is typically a pcmserve.ini/DLLPath= mis-mapping that results from not installing PC*MILER to its default location. Double click pcmserve.ini (open with notepad if prompted) and check that your DLLPath= value points to your PMWxxx\app folder.
3. Does running \alkmvs\mvtest all return a distance for the new version?
This test must be launched from a dos prompt. Click Start=>Run (Windows Logo Key + R on Vista and Windows 7) type in CMD and hit enter. Type in the following commands for a default location installation; adjust your commands for a non-default location installation.
C: Hit Enter
cd \"Program Files"\"Alk Technologies"\Alkmvs Hit Enter
mvtest all Hit Enter
Failure here is typically a port mismatch between pcmmv.ini and startmvs.bat.
Please note the version of your product in any correspondence so that we can answer your question more quickly.
For PC*MILER Support:
(PC*MILER and PC*MILER|Rail)
Phone: 1-800-377-6453 (ext. 2)
Phone: 1-609-683-0220 (ext. 2)
NOTE: Support for PC*MILER|FuelTax was discontinued February 2015.
If you have a question about your order, please contact your sales representative or email firstname.lastname@example.org.