User`s guide

PC*MILER-AS/400 MVS User’s Guide 99
to:
Start Pcmsock25.exe PC_MILER 8250 LOG_BASIC .\V25log.txt
or
Start Pcmsock25.exe PC_MILER 8250 LOG_BASIC C:\PcmLogs\V25log.txt <=Folder must exist
Other options are:
 Add a fourth parameter of ‘Append’ to be used to troubleshoot crashes:
Start Pcmsock25.exe PC_MILER 8250 LOG_BASIC C:\PcmLogs\V25log.txt APPEND
 Include communications and not just routing and distance information, using
LOG_ADVANCED instead of LOG_BASIC:
Start Pcmsock25.exe PC_MILER 8250 LOG_ADVANCED C:\PcmLogs\V25log.txt
APPEND
To run on logging for older versions, you will need to copy …\pmw250\tcpip\pcmtcp.dll,
listex.dll, and pcmsock25.exe to the older PmwXXX\Tcpip folders. After copying
Pcmsock25.exe, rename the copy to PCMSockXX.exe to match the version you are
replacing. For example if you are copying pcmsock25.exe to …\pmw220\tcpip, rename this
copy of pcmsock25.exe to pcmsock22.exe.
You will need to close the existing instances of PcmsockXX.exe before starting them in
logging mode. Failure to close the existing instances will result in ‘bind failed’ errors.
Pcmsrv32.dll logging is turned on in your pcmserve.ini files.
[Logging]
Enable=0 off 1 on
File=C:\temp\V25log.txt <=Folder must exist
Append=1 to append, 0 will overwrite
Use Append=1 for troubleshooting crashes.
Pcmsrv32.dll only reads pcmserve.ini at startup, you will need to restart pcmsockXX.exe
after making the INI file edits.