String threadsafe, in Class DB2Routine

Documentation
From the v8.1 UDB documentation for external UDFs and stored procedures:

Specifies whether the procedure is considered safe to run in the same
process as other routines (THREADSAFE), or not (NOT THREADSAFE).

If the procedure is defined with LANGUAGE other than OLE:
- If the procedure is defined as THREADSAFE, the database manager can
invoke the procedure in the same process as other routines. In general,
to be threadsafe, a procedure should not use any global or static data
areas. Most programming references include a discussion of writing
threadsafe routines. Both FENCED and NOT FENCED procedures can
be THREADSAFE.
- If the procedure is defined as NOT THREADSAFE, the database
manager will never invoke the procedure in the same process as
another routine.

For FENCED procedures, THREADSAFE is the default if the LANGUAGE
is JAVA. For all other languages, NOT THREADSAFE is the default. If the
procedure is defined with LANGUAGE OLE, THREADSAFE may not be
specified (SQLSTATE 42613).

For NOT FENCED procedures, THREADSAFE is the default. NOT
THREADSAFE cannot be specified (SQLSTATE 42613).

As of Sept 2003, only for LUW


Export ControlPublicAccessContainmentUnspecified
StaticNoDerivedNo


Property Settings

Data Modeler
dmItemFalseDMName 
Ordinal0IsIdentityFalse
IsUniqueFalseNullsAllowedFalse
Length0Scale0
ColumnTypeNativeForBitDataFalse
DefaultValueType DefaultValue 
SourceId SourceType 
OIDFalse