If you experience issues with your SySAM license, read this section to find information that might help you troubleshoot licensing issues, or help you collect information that Technical Support can use to diagnose licensing issues. You can find more information about SySAM licensing on the SySAM Web site and in the SySAM Documentation.
You can enable logging by adding an entry to the IM.INI file with the following format, where N is 0, 1, or 2:
[pb] LogSySAM = N
The default value for LogSySAM is 0, which means no logging. Set the value to 1 for basic logging information or 2 for more detailed logging information. The log file is saved in the same directory as IM.INI and is named IM115_sysam.log. The file contains status information from the development environment, the details of the current license, and, if you set the SySAMTrace value in IM.INI, information from the SySAM API. Technical Support might ask you to set these values if you experience license problems.
IM.INI directory
Although IM.INI is
installed by the setup program to the main installation directory,
InfoMaker does not use or modify the IM.INI file
in this directory. Instead, InfoMaker creates a personal copy of
the IM.INI file the first time you or another
user starts InfoMaker, and this is the initialization file that InfoMaker
uses.
On Windows XP and Windows 2003, the directory containing the personal copy of the IM.INI file is C:\Documents and Settings \userName\Local Settings\Application Data\Sybase\InfoMaker 11.5, where userName is the name of the current InfoMaker user. A personal SySAM log file is saved to this directory, and local license files are kept in this directory for each InfoMaker user. The name of this directory on Windows Vista and Windows 2008 is C:\Users\userName\AppData\Local\Sybase\InfoMaker 11.5.
The im115_sysam.properties and PB115.lic (or IM115.lic) files are installed in the same directory as IM.INI. These files contain information that might be useful to Technical Support. Do not edit these files unless directed to do so by Technical Support.
If you enter an unqualified server name, such as “myserver” as the license server name, it might not be found. Try a fully-resolved name, such as “myserver.mydomain.com.”
