User`s guide

PC*MILER-AS/400 MVS User’s Guide 98
Appendix L: New in Version 25 – Four Levels of Logging
Starting with V25: Logging has been added to the pcmmv.dll and to the pcmsockxx.exe
layers in addition to the existing logging at the AS400.exe (Bart) and
pcmsrv32.dll/pcmserve.ini levels.
AS400.exe connects to pcmmv.dll, which connects to the version-specific instances of
pcmsockXX.exe, which in turn connect to their version-specific instances of pcmsrv32.dll.
Logging should be used only during trouble shooting as the files can grow quite large.
AS400.exe Logging is turned on within the PC Distance Server (AS400.exe ((Bart)) by
clicking the File drop-down menu and choosing AS400 Control then Log to File and then a
choice of Overwrite, Append, or Verbose.
Overwrite will create a new file called “as400.log” in your ALKMVS or ALKToll folder.
Use Overwrite when troubleshooting data is being received on the AS400 side.
Append will create a new as400.log file or start logging on the bottom of an existing file.
Use Append for issues with AS400.exe crashes.
Verbose will create a new as400.log file or start logging on the bottom of the existing file
and will include PC to AS400 communication return codes and low level internal trip
information. Use the Verbose setting for troubleshooting PC to AS400 communication
failures.
Pcmmv.dll logging is turned on in your pcmmv.ini file. Add the following to your
pcmmv.ini in Notepad (Pcmmv.ini is typically found in C:\Alkmvs or C:\Alktoll):
[Logging]
Enable=0 off 1 on
File=C:\temp\Pcmmv.txt <=Folder must exist
Append=1 to append, 0 will overwrite
Use Append=1 for troubleshooting crashes.
Pcmmv.dll only reads pcmmv.ini at startup, you will have to restart your application after
making the INI file edits.
PcmsockXX.exe logging is turned on with command line parameters.
Make a copy of your StartMVS.bat file, then rename the file “StartLogging.bat”.
Edit StartLogging.bat in Notepad as follows:
Change V25’s line from:
Start Pcmsock25.exe PC_MILER 8250