1. Why is the sample Stock adapter not getting stock prices for me?

2. Why do my old conduct sets not load anymore?

3. Why do I get message "Problems getting Conduct Set" when trying to load my conduct set?

4. How do I know if I'm running level 5 or level 5a of ABE?

5. How do I get level 5a of ABE?

6. Where is iagentj.exe?

7. Where is iagent.cfg?

8. Does it cost anything to download ABE?

9. Why am I getting the message Exception in thread "main" java.lang.unsatisfiedLinkError: no iaglibrj in shared library path on my AIX system?

10. Why am I getting the message Couldn't connect to Java Listener, on port 1028 on my OS/2 system?

11. Why am I getting message "Error: Incompatible signatures between predicate predicate name and effector procedure effector name"?

12. Why do my old rule sets suddenly get parsing errors when I try to bring up the agent?

13. Why am I getting message "Error: Unregistered effector procedure effector name"?

14. Why am I no longer seeing any events from the Time Adapter?


1. Why is the sample Stock adapter not getting stock prices for me?

The stock adapter will appear to 'do nothing' if it is unable to obtain the stock prices from the web. Symptoms include the messages:
    QuoteYahooCom:startMonitor() connect
    StockAdapter:stockPriceCompare()

A few things that might cause this:
  • Your web access does not use a proxy, and you are running any version of ABE prior to level 5a. Prior to level 5a, the stock adapter would only work when a valid proxy was specified by the rules in the .rls file.
  • Your web access requires a proxy and you have not specified one. You need to update the sampstok.rls file and replace.


(StockAdapterProxy "myhttpproxy.mycompany.com" 80)

with the url and port of your proxy server.

[Goto Top]

2. Why do my old conduct sets not load anymore?

The format of conduct sets changed between the Alpha
4 release of ABE and the level 5 release. Conduct sets
that loaded successfully under earlier ABE releases will
fail to load under ABE level 5 with message:

   Parsing errors were detected in conduct set .



   Problems getting Conduct Set.



   Error loading and parsing conduct set

   IAG0326 

   Error loading conduct set with name = 

Run the ABE level 5 conduct set conversion utility (utils\cvtrules) against your old conduct sets to convert them to the new format. Then the old conduct sets should load successfully.

See the ABE READ.ME file for details on running the conversion utility.

[Goto Top]

3. Why do I get message "Problems getting Conduct Set" when trying to load my conduct set?

The agent may be unable to load your conduct set for a variety of reasons, all of which cause the (not-very-helpful) series of messages:

   Parsing errors were detected in conduct set .



   Problems getting Conduct Set.



   Error loading and parsing conduct set

   IAG0326 

   Error loading conduct set with name = 

Some of the causes for this error are as follows:

[Goto Top]

4. How do I know if I'm running level 5 or level 5a of ABE?

The READ.ME file indicates which version of level 5 you have.

[Goto Top]

5. How do I get level 5a of ABE?

As of April 10, 1997, when you download 'level 5' from the web you get level 5a. Level 5 was only available on the web between 3/28/97 and 4/10/97

[Goto Top]

6. Where is iagentj.exe?

In ABE releases Alpha 2 and Alpha 3, the iagentj.exe is located in the ABE bin\ directory.

In ABE release Alpha 4 and beyond, the iagentj.exe has been replaced by the iagent.exe, in the ABE bin\directory. ABE now uses the same agent for both C++ and java.

The Alpha 4 documentation for the sample stock adapter is incorrect, and should have been updated to specify iagent.exe instead of iagentj.exe.

[Goto Top]

7. Where is iagent.cfg?

iagent.cfg is not shipped as part of ABE. If you don't specifically state the name of a configuration file on invocation of the agent.exe program, the program defaults to looking for a configuration file called iagent.cfg. If agent.exe finds no such file, you will receive error message:

Unable to open configuration file iagent.cfg: One of the library files needed to run this application cannot be found. ABE does ship sample configuration files for an nntp news / email agent (nntpsmp1.cfg), and for a stock agent (sampstok.cfg). See the read.me files in the samples\ directories for more information.

[Goto Top]

8. Does it cost anything to download ABE?

Current ABE versions are free. You can download ABE from our IA home page or from IBM's alphaWorks site.

[Goto Top]

9. Why am I getting the message Exception in thread "main" java.lang.unsatisfiedLinkError: no iaglibrj in shared library path on my AIX system?

The ABE java adapter interface uses the javai.dll interface. The AIX LIBPATH and LD_LIBRARY_PATH environmental variables need to include the path to this dll.

If you are using the 1.0.2 version of the JDK, use:

export LIBPATH=/lib:/usr/lib:/usr/lpp/xlC/lib:IAGHOME/lib:JAVA_HOME/lib/aix_pt export LD_LIBRARY_PATH=YOURDIR:IAGHOME/lib:JAVA_HOME/lib/aix_pt

If you are using the 1.1 version of the JDK:

export LIBPATH=/lib:/usr/lib:/usr/lpp/xlC/lib:IAGHOME/lib:JAVA_HOME/lib/aix/native_threads export LD_LIBRARY_PATH=YOURDIR:IAGHOME/lib:JAVA_HOME/lib/aix/native_threads

In the above, JAVA_HOME is the top directory into which you installed Java, and YOURDIR is the directory in which your personal Java native method shared object files (.so) reside, if you are using native methods.

[Goto Top]

10. Why am I getting the message Couldn't connect to Java Listener, on port 1028 on my OS/2 system?

ABE communicates with java adapters across the local host/loopback ip address. If this ip address is not enabled in your TCP/IP configuration, you will receive this message when trying to start a java adapter.

Configuring loopback under OS/2:

  • Double-click on the TCP/IP icon. This can usually be found on the desktop or in the OS/2 System folder.
  • Double-click on the TCP/IP Configuration icon.
  • If the notebook page is titled Configure Network Interface Parameters then:
    • Select loopback interface under Interface to Configure
    • Check the Enable Interface checkbox
    • Verify that IP Address is 127.0.0.1
  • Otherwise, you have an older version of TCP/IP for OS/2. Refer to your documentation for enabling the loopback interface.

    If you are using a version of OS/2 where you connect via a dial-up connection and there is no TCP/IP Configuration icon, then you need to setup localhost maually. To do this, issue the OS/2 command:
    • ifconfig lo 127.0.0.1

    This will add the localhost configuration to TCP/IP for that logon session. Everytime you reboot you will need to reissue this command so we advise creating a .CMD file you can run everytime. Example of this (called ABELOCAL.CMD):
    • REM Command file to start LocalHost for the ABE agent
    • ifconfig lo 127.0.0.1

[Goto Top]

11. Why am I getting message "Error: Incompatible signatures between predicate predicate name and effector procedure effector name"?

The Time adapter was updated in ABE Level 6 to allow timers to be persistent across an agent shutdown. As a result, all of the Time adapter effectors have been changed. Some were eliminated (consolidated), others were updated to take additional terms. If you try to use a rule set containing old timer effectors with the level 6 timer adapter, you will get messages like:
 



       Parsing errors were detected in conduct set test.



       ==== EFFECTOR DECLARATION errors ====



       Effector: EFFECTOR setIntervalAlarm      Time:setIntervalAlarm

       Error: Incompatible signatures between predicate 'setIntervalAlarm'

              and effector procedure 'Time:setIntervalAlarm'



       Effector: EFFECTOR turnOffIntervalAlarm  Time:turnOffIntervalAlarm

       Error: Unregistered effector procedure 'Time:turnOffIntervalAlarm'

  

       Error loading and parsing conduct set

       IAG0326 No error message provided

       Error loading conduct set with name = test



To eliminate these messages and allow the agent to run, update the old rule sets to use the new Time effectors and to supply the additional terms that are now required by the changed effectors. See the ABE Components and Adapter Reference for details on the new effectors, and the CHANGES file in the ABE root directory for more information on the changes.

[Goto Top]

12. Why do my old rule sets suddenly get parsing errors when I try to bring up the agent?

see #11 above.

[Goto Top]

13. Why am I getting message "Error: Unregistered effector procedure effector name"?

see #11 above.

[Goto Top]

14. Why am I no longer seeing any events from the Time Adapter?

The Time adapter was updated in ABE Level 6 to allow timers to be persistent across an agent shutdown. As a result, all of the Time adapter event names have been consolidated into one new event name Time:Alarm. You need to update your rules to use the new event name in order to see and process the events. See the CHANGES file, or the ABE Components and Adapter Reference, for details.

[Goto Top]