Behavior of routines

While it is recommended that all new routines be defined as poorly behaved, for the purposes of this tutorial, you must check well behaved in the New Routine wizard.

Well behaved

A routine is well-behaved if it:
  • Yields the CPU on a regular basis to other threads.
  • Does not use blocking operating-system calls.
  • Does not allocate local resources.
  • Does not modify the global virtual processor state.

Poorly behaved

If you have a poorly behaved routine, check poorly behaved and type the name of a user-defined virtual processor in the user-defined virtual processor class box. If you let a poorly behaved routine run in the CPU virtual processor, you could experience potentially severe performance problems. You must create the user-defined virtual processor before you register the DataBlade® module containing routines that run in it.

See the Informix® DataBlade API Programmer's Guide for more information about coding practices and creating and configuring a user-defined virtual processor.