User`s guide

PC*MILER-AS/400 MVS User’s Guide 28
5.0 Troubleshooting
After you have started your various instances of pcmsock.exe you can test them
by running the following command in DOS:
C:\alkmvs\mvtest<space>all
For any failures you will have to run a second tester. In each of the
...\Pmw1xx\Tcpip subfolders created by the self-extracting Zip files in Step 2.2
of the installation, you will find a pcmstest.exe file. Pcmstest.exe tests the layer
below pcmsock.exe. Failures here are typically a problem with the DllPath key
value in the ...\Tcpip\pcmserve.ini file. If the pcmserve.ini file is correct you
need to run ...\Pmw1xx\App\pcmwin32.exe to test for a working copy of the base
PC*MILER program.
NOTE: During troubleshooting it is common to get “Bind Failed” errors. These
can be cleared up by running your KillMVS batch file or by going to the
Windows Task Manager > Processes (right-click on your PC’s Windows tool bar
at the bottom of the screen and select Task Manager > Processes tab) and killing
any instances of Pcmsock.exe that have not closed properly.
If your server is on the Internet, ALK maintains the Logmein123.com service that
allows support staff to connect to your server to troubleshoot.
Delay Between Launching Pcmsock.exes
On some servers it is necessary to add a delay between the startup of the instances
of pcmsock.exe. Included in the \Alkmvs or Alktoll directory is delay.exe, which
can be used to add a delay between starting the instances of pcmsock.exe. Edit
Startmvs.bat as follows:
cd \pmw190\tcpip
start pcmsock19 PC_MILER 8190
c:\alkmvs\delay 2
cd \pmw200\tcpip
start pcmsock20 PC_MILER 8200
c:\alkmvs\delay 2
cd \”Program Files”\”Alk Technologies”\pmw210\tcpip
start pcmsock21 PC_MILER 8210
c:\alkmvs\delay 2
et cetera