1. GemStone/S 64 Bit 3.3 Release Notes

New keyfiles required

New keyfiles are required for version 3.3. To obtain a new keyfile for GemStone/S v3.3, write to keyfiles@gemtalksystems.com. In your request, include your license information, platform and any updates to contact information. It may be helpful to include your current keyfile with the request.

Contact GemTalk Technical Support if you have issues or questions.

Application code recompile required

The upgrade process from 3.2.x or earlier to 3.3 requires all method source code be recompiled.

Platforms for Version 3.3

GemStone/S 64 Bit version 3.3 is supported on the following platforms:

• Solaris 10 and 11 on SPARC
• Solaris 10 on x86
• AIX 6.1 on POWER6 and POWER7 and
  AIX 7.1 on POWER7 and POWER8
• Red Hat Enterprise Linux Server 6.4, 6.5, 6.7, and 7.1;
  Ubuntu 12.04; and SUSE Linux Enterprise 12, all on x86
• OS X 10.9.5 (Mavericks), with Darwin 13.4.0 kernel, on x86

For more information and detailed requirements for each supported platforms, please refer to the GemStone/S 64 Bit v3.3 Installation Guide for that platform.

GemBuilder for Smalltalk (GBS) Versions

GemStone/S 64 Bit version 3.3 requires a new version of GBS, version 8.1. Older versions of GBS cannot login to v3.3. For details on the changes in GBS v8.1, see the GemBuilder for Smalltalk Release Notes for v8.1

The following versions of GBS are supported with GemStone/S 64 Bit version 3.3.

VSD Versions

The GemStone/S 64 Bit v3.3 distribution includes VSD version 5.1.1. The previous version of GemStone/S 64 Bit, v3.2.12, included VSD v5.1.

Changes between VSD v5.1 and v5.1.1 include :

• changes in the statistic type for a number of statistics, affecting combined graphs.

For more details, see the Release Notes for VSD v5.1.1.

GemBuilder for Java (GBJ) Versions

GBJ users must upgrade to GBJ 3.1.2 along with the upgrade to GemStone/S 64 Bit v3.3. Earlier versions of GBJ are not compatible with v3.3.

The GemStone/S 64 Bit v3.3 distribution includes the shared libraries for GBJ v3.1.2.

Note that GBJ 3.1.2 now requires Java 1.8.0.

For more information on changes in GBJ v3.1.2, see the Release Notes for GBJ v3.1.2

GemConnect Versions

The current version of GemConnect, v.2.3, is compatible with GemStone/S 64 Bit v3.3, so upgrade is not needed if you are running GemConnect 2.3.

The exception is the Macintosh; recent versions of Darwin have introduced incompatibilities with GemConnect. Contact GemTalk Technical Support if you need to use GemConnect with v3.3 on the Mac.

Documentation Changes

All Documentation has been revised for this release, with modifications to incorporate new and changed features, as well as corrections and improvements.

• The Topaz User’s Guide has been extensively updated, with Chapter 1 reorganized and largely rewritten. The Topaz User’s Guide is now available in .html as well as .pdf
• The graphics for the System Administration Guide and the Programmer’s Guide have been updated to be more informative and easier to read, as well as more attractive.
• The System Administration Guide has extensive updates to Chapter 3 on distributed configurations, and reorganized material on GemStone processes and log file management in Chapter 5.
• The GBS and GBJ Release Notes and Installation Guide are now available as .html as well as .pdf.

Updated libraries

Several open-source libraries included with GemStone/S 64 Bit have been updated:

• OpenSSL continues to release security advisories. The version of OpenSSL used by GemStone/S 64 Bit v3.3 has accordingly been updated to 1.0.2f.
• OpenLDAP has been updated to 2.4.40.
• ICU has been updated to version 54.1.

Multithreaded page servers and pageaudit

The pgsvr page server processes, including AIO and Free Frame page servers, and page servers for remote gems, are now multithreaded. When multiple page servers were previously used, these are now threads within a single pgsvr process, rather than multiple pgsvr processes, and write to a single log file.

The configuration parameters SHR_NUM_FREE_FRAME_SERVERS and STN_NUM_LOCAL_AIO_SERVERS configure the number of threads, not the number of processes.

All Gems on a remote cache will share a single pgsvr process on the stone’s machine.

The pageaudit utility has also been multithreaded, and will complete much more quickly. This is described under pageaudit.

Compression using LZ4

Internal compress and uncompress, particularly compression of pages transmitted to remote processes are now compressed using LZ4 instead of Zlib (gzip).

LZ4 provides much faster performance for these operations. Configurations in which interprocess compression did not provide performance improvements should reevaluate under version 3.3.

Externally visible compression continues to use Zlib; the changes to LZ4 should not impact normal operations, such as statmonitor/VSD, GsFile, compression of backups and transaction logs, and GciCompress/GciUncompress.

The GemStone distribution now includes LZ4 v1.3.1, and associated open-source license file.

New cache statistics have been added to track the performance of compression and decompression; see under Added statistics

Extent sizes multiple of 16MB

The minimum extent size is now 16MB, and extent now grow by units of 16MB. This is much more efficient for modern disk sizes. For details, see Extent sizes always multiple of 16MB.

Class name and instance variable limitations raised

Class names may now be up to 1024 characters in length, and may have up to 2030 instance variables.

Zoneinfo library updated

GemStone includes a distribution of the tz or zoneinfo Time Zone database, under $GEMSTONE/pub/timezone. The version distributed has been updated to version 2015d.

For the latest versions, see http://www.iana.org/time-zones.

Note that Linux and Solaris systems normally have this Time Zone Database installed as part of the operating system, and many methods in GemStone TimeZone classes will use the OS version by default on these platforms.

Improvements in support for debugging/single stepping

The code in GsProcess and other methods that supports stepping through and into code, which is used in GBS and topaz debugging, has been updated and refactored, and the API has been changed. A number of private methods have been removed from GsProcess, and other methods added.

Related to this, several GCI stepping functions have been deprecated.

Block execution

Version 3.3 includes new bytecodes and code changes to fix issues with Block execution.

Note that to:do: and similar loops may not be optimized; moving temps inside the loop may help restore the optimization.

With tranlogs set to /dev/null, no records sent

Setting the tranlog directories (STN_TRAN_LOG_DIRECTORIES) to /dev/null avoids the overhead of writing tranlog records to disk, at the risk of being unable to recover from unexpected shutdown.

Previously, while the disk write itself was not done, the tranlog records were still created and sent. Now, the gems themselves do not send tranlog records in the case where the tranlogs are set to /dev/null.

There are additional restrictions on tranlog directories set to /dev/null; either all items in the tranlog directories must be null, or none. A mix is disallowed and will raise an error.

Support for 1GB huge pages on Linux

The shared page cache can now be configured to use 1GB memory pages on Linux. This is configured in the same way as 2MB pages are configured. See the Installation Guide for more information.

Slow and no-op libraries and executables

When diagnosing problems, it can be useful to run slow or no-op Gems, which are not optimized and provide more internal state information and, in the case of slow executable, assertion checks. This can now be done more easily by using new components in the product distribution.

Slow and not-optimized (no-op or noop) libraries are now provided as libgcilnk_slow-NN-64.so and libgcilnk_noop-NN-64.so, in the $GEMSTONE/lib directory. The directory $GEMSTONE/libslow/ is no longer included.

The $GEMSTONE/sys directory includes the executables for gem, pgsvrmain and stone. In v3.3, both .slow and .noop executable variants of each of these are also included.

The following gemnetobject variants will cause a no-op or slow gem to be run:

$GEMSTONE/sys/gemnetobject_noop

$GEMSTONE/sys/gemnetobject_slow

To run a slow or noop gem, you can invoke the new variant in place of gemnetobject in your GemStone login parameters.

Process log files and deletion policy

Handling of log files on clean exit has been reviewed and made consistent. These are the updated rules:

• Stone, NetLDI, logsender and logreceiver logs are never automatically deleted.
• When a process terminates abnormally, from an error or kill -TERM, its log is not deleted, regardless of any environment settings. The SymbolGem is also preserved from deletion if an error occurred at any point in the process’s lifetime.
• If the environment variable GS_KEEP_ALL_LOGS is set, no log files are deleted.
• If the environment variable GS_FORCE_CLEAN_LOG_FILE_DELETE is set, then all log files for processes that exit cleanly are deleted.
• The environment variable GEMSTONE_KEEP_LOG controls whether a particular process log file is deleted on clean shutdown. These are set in the process startup script $GEMSTONE/sys/run*. This can be modified this for individual process scripts for finer control.
• SPC Monitor, PageManager, AdminGem and ReclaimGem logs are not deleted by default.
• The logs for an RPC Gem, Symbol Gem, AIO Page Server, Free Frame Page Server, and most other processes are deleted by default.
• Logs for remote processes are generally not deleted.

As a convenience to allow the RPC Gem log to be retained on clean exit, the following has been added:

$GEMSTONE/sys/gemnetobject_keeplog

Using this in place of gemnetobject in the gem login parameters allows the gem log to be retained on clean exit.

The names of log files for processes associated with remote processes has also been cleaned up to be easily identifiable and consistent with the naming for local process logs.

More specific run* scripts

Changes have been made to the set of $GEMSTONE/sys/run* scripts that are used to startup GemStone processes. New scripts have been added that are more specific to particular processes. This allows per-process type customization as needed, such as control over log file deletion.

The following scripts have been added:

runaiopgsvrrunffpgsvr

runcachepgsvr

rungempgsvr

runpageauditgem

runstatmonitor

32-bit GCI now available on AIX

In previous v3.1.x and 3.2.x releases, the 32-bit applications and libraries in $GEMSTONE/bin32 and $GEMSTONE/lib32 were not available on AIX. These have been restored.

Name change for Windows Client Distribution

The Windows client was previous provided with the name

GemBuilderCN.N.N-x86.Windows_NT.zip

This was not very descriptive; this has been renamed, and is now:

GemStone64BitClientN.N.N-x86.Windows_NT.zip

The Installation Guide to use with the Windows Client is GS64-WindowsClient-3.3.pdf; this new name was introduced in v3.2.6.

Encryption between remote gem and page server

To create an SSL connection between a remote Gem and its page server on the stone’s host and the mid level cache, if used, a new configuration option has been added; GEM_PGSVR_USE_SSL. See GEM_PGSVR_USE_SSL. This option enables SSL between both the gem and the page server on the stone host and the page server mid cache, if any. The SSL tunnel is established in anonymous mode, meaning communications are encrypted but the sender and receiver are not authenticated.

Updated SSL protocol

The SSL protocol has been updated from TLS 1.1 to 1.2.

Querying for connection encryption status

The following methods have been added:

System class >> gciClientConnectionIsEncrypted
Answer a Boolean indicating whether the network connection to the gem's GCI client is encrypted (using TLS). Always answers false for linked gems and for gems running on the same host as the GCI client.

System class >> pageServerConnectionIsEncrypted
Answer a Boolean indicating whether the network connection to the gem's page server is encrypted (using TLS). Always answers false for gems without a page server, i.e., gems that run on the same host as the stone process.

SmallFraction special added

SmallFraction is a new class in this release. SmallFraction is a special, an object for which the value is encoded in the OOP. Specials do not require a individual object in the repository, and so do not need to be loaded into the repository or into memory, making them much more efficient.

SmallFractions can hold fractional values with numerators between -536870912 and 536870911, and denominators greater than 0 and less or equal to 134217727 .

SmallFraction is related to Fraction similarly to how SmallDouble and Float or SmallInteger and Integer relate; Fraction creation or operations on Fractions that produce results within the SmallFraction range will return an instance of SmallFraction, and SmallFraction operations with results outside of the range will return an instance of Fraction.

The hierarchy for Fraction is changed in this release; the class AbstractFraction has been added as the superclass for Fraction as well as SmallFraction.

Change in printing

Float >> asStringLegacy

SmallFloat >> asStringLegacy

Float >> asStringLocaleCLegacy

Float >> asStringUsingFormatLegacy:

Parsing custom numeric literals

The GemStone compiler recognizes a number of numeric literals in addition to integers and floats; for example, ScaledDecimals can be specified using the literal syntax 1.23s2. If your application has defined a new numeric type, is it now possible to define a new literal syntax, and have the compiler handle this correctly to create instances of your numeric class. The new literal syntax can be of the form Nc or NcM, where N and M are numbers and c is an alphabetic character.

The following message provides a way to instruct the compiler to recognize a new literal format for a numeric class:

NumberSubclass parseLiterals: aCharacter exponentRequired: aBoolean

NumberSubclass must be a subclass of Number. Once this is sent, when the compiler encounters a numeric value using aCharacter, it will invoke NumberSubclass >> fromString: to create an instance of NumberSubclass.

The subclass of Number must implement fromString: in such a way as to be able to read the literal format and create the new instance.

aCharacter must an alphabetic Character with codePoint <= 127, and may not be an existing numeric literal character. The following are not allowed: $e $E $d $D $f $F $p $s $q $r.

aBoolean indicates if digits following aCharacter are required or not. If aBoolean is nil, it uninstalls a previously-installed literal class.

Once invoked, the new literal format will be recognized until the session logs out.

Note that for subsequent logins, compiled references to that literal will continue to be valid, but unless the method is invoked again, methods with that literal cannot be recompiled. Including the invocation in session initialization code (such as using loginHook:) is recommended.

to:do: and to:by:do: handling

The optimized selectors to:by: and to:by:do: are only applicable to classes that have a sequencable control value. Previously, these methods were provided in Number; however, this created issues for application classes that implemented sequenceable kinds of objects not under the Number hierarchy. These methods have been moved to Object; although, note that they will fail if the subclass does not implement minimal arithmetic protocol.

Runtime configuration of ReclaimGem and AdminGem

Previously, the only way to update Reclaim and Admin Gem’s configuration was to modify values for the appropriate keys in the GcUser’s UserGlobals, and, provided #autoRefreshGcGemConfig was set to true, waiting for the GcGem to notice and update.

These can now be set at runtime without commit, and take effect immediately. A particular value of this feature is to configure reclaim in warm and hot standby systems, which previously were limited to the identical ReclaimGem configuration as required by their primary production system.

Runtime configuration changes made using these new methods are not persistent; to make a change that will persist after the Reclaim or Admin restart, you must also edit the value in GcUser’s UserGlobals.

When you make persistent changes in GcUser’s UserGlobals, these changes take effect some time subsequent to the commit, when the Reclaim or Admin Gem commits or aborts. On idle systems, there may be a delay before these changes take effect; the frequency of checking has changed in this release. Note that #autoRefreshGcGemConfig is no longer used, so changes to GcUser’s UserGlobal settings will always take effect.

System class >> getReclaimConfig: configSymbol

System class >> setReclaimConfig: configSymbol toValue: aVal

#deadObjsReclaimedCommitThreshold

#deferReclaimCacheDirtyThreshold

#maxTransactionDuration

#objectTableCleanupIdleTime

#objsMovedPerCommitThreshold

#reclaimDeadEnabled

#reclaimMinFreeSpaceMb

#reclaimMinPages

#reclaimVerboseLogging

#sleepTimeBetweenReclaimMs

#sleepTimeWithCrBacklogMs

System class >> getAdminConfig: configSymbol

System class >> setAdminConfig: configSymbol toValue: aVal

#adminVerboseLogging

#epochGcMaxThreads

#epochGcPageBufferSize

#epochGcPercentCpuActiveLimit

#epochGcTimeLimit

#epochGcTransLimit

#saveWriteSetUnionToFile

#sweepWsUnionMaxThreads

#sweepWsUnionPageBufferSize

#sweepWsUnionPercentCpuActiveLimit

removed configuration options

The following parameters are obsolete in v3.3, and have been removed:

#autoRefreshGcGemConfig 

#enableDebugging

verboseLogging replaced

In order to complete the separation of the set of parameters that apply to the ReclaimGem vs. to the AdminGem, #verboseLogging has been removed, and replaced by #adminVerboseLogging and #reclaimVerboseLogging. Both of these default to false.

New Reclaim Parameters

The following have been added:

Mark/sweep by FDC/MGC no longer available

In previous releases, an alternative to markForCollection has been a findDisconnectedObjects/markGcCandidates set, generally used with FDC occurring on an offline copy of the repository. With the introduction of multi-threaded markForCollection, the offline FDC/MGC combination is no longer necessary for performance.

Changes in the multithreading scan may have introduced instability into the MGC, so this feature has been removed. The following methods are removed:

basicMarkGcCandidatesFromFile:forceOnError:readOnly:

cleanupBigArray:forMgc:

cleanupMgcResultsForMgc:

markGcCandidatesFromFile:

markGcCandidatesFromFile:forceOnError:

markGcCandidatesReadOnlyFromFile:

FDC remains available as an analysis tool.

The method Repository >> cleanupFdcResults has been added to replace the deprecated method Repository >> cleanupFdcResultsForMgc:.

Symbol Garbage Collection restored

Symbol garbage collection was disabled in the previous version, due to bug 45403. It is re- enabled in v3.3; you may now choose to set STN_SYMBOL_GC_ENABLED to TRUE.

stopGcSession: deprecated

Stopping garbage collection session by session number is deprecated; use stopReclaimGem or stopAdminGem instead.

Multi-threaded backup and restore now transparently adjust sessions

Multi-threaded backup and multi-threaded restore compute the number of sessions based on CPUs and extents. If this number of sessions is not available (e.g., when many other sessions are logged in), backup and restore now use fewer sessions, as available, and write a message to stone log.

Optimization in restoring backups

The code that performs the restore operation has been refactored to change the way the new object table is managed. This improves performance; testing indicates a 30% improvement in CPU time. Note that the actual performance improvement may also be limited by I/O. The changes are in the backup file; backups from earlier versions cannot be restored into 3.3, which is not a supported operation in any case.

Writing to logs now writes as UTF8 as needed

Messages that are written to the stone log using System class >> addAllToStoneLog:, or to the GCI client or server logs using gciLogClient: and gciLogServer:, are now encoded as UTF8.

This allows all kind of String containing any characters to be written to the logs.

performOnServer: now accept input beyond ASCII range

System >> performOnServer: accepts a string argument; this argument can now be a traditional or Unicode string or a Utf8, and may include Characters outside the ASCII range.

Note that the results are always returned as a String containing byte characters, in the range up to code point 254. The application must determine if the result is 8-bit or UTF8, and send decodeFromUTF8 to the result as needed.

Converting between Strings, UnicodeStrings, and Utf8s

Changing Unicode Comparison Mode

Unicode Comparison Mode makes it easier to work when there are combinations of Legacy and Unicode String data. In Unicode Comparison Mode, all legacy string as well as Unicode string comparisons use the ICU libraries. This avoids inconsistencies and disallowed operations in comparison rules between Legacy and Unicode strings.

Note that applications with existing Legacy String data in dictionaries and indexes should not change the Unicode Comparison Mode without performing manual resorts/rebuilds , since it is possible, although rare, for ordering to change and lookups to fail.

The following methods provide an interface for changing the setting and testing for Unicode Comparison Mode.

CharacterCollection class >> disableUnicodeComparisonMode
Disable Unicode Comparison Mode; restore legacy handling for Legacy String classes. This method may only be executed by SystemUser. This method performs a commit; the change takes effect on subsequent logins. This method returns the previous value of isInUnicodeComparisonMode.

CharacterCollection class >> enableUnicodeComparisonMode
Enable Unicode Comparison Mode, so all String comparison use ICU library comparison functions. This method may only be executed by SystemUser. This method performs a commit; the change takes effect on subsequent logins. This method returns the previous value of isInUnicodeComparisonMode.

CharacterCollection class >> isInUnicodeComparisonMode
Return if the current session operates in Unicode Comparison Mode. This does not reflect changes to the Unicode Comparison Mode status that were made subsequent to this session’s login.

These methods are implemented in CharacterCollection, so can be sent to any String class. It is recommended that you send these messages to the class returned by the Global reference #StringConfiguration. For example:

StringConfiguration isInUnicodeComparisonMode

StringConfiguration is a key in Globals that currently may refer to String or to Unicode16, but may in the future provide more ability to manage strings. Using StringConfiguration will accommodate future changes to this reference.

ReversedReadStream

Rather than returning indexing results as a collection, they can be returned a s a kind of Stream, which avoids the need to create a large result set in memory. This is done via GsQuery >> readStream, which streams over the query results in sorted order.

Now, you can also stream over the results in reverse order using the new method GsQuery >> reversedReadStream, or by sending reversed to the result of GsQuery >> readStream.

A new class, ReversedRangeIndexReadStream, has been added to implement this feature.

OptionalPathTerm indexes specification moved

OptionalPathTerms allow indexes to be built and queries run that ignore the presence of objects that do not implement an instance variable that is specified on a path. For building indexes, this feature is specified using protocol in GsIndexOptions.

To set optionalPathTerms on a query, previously GsQuery methods were used; now, methods on GsQueryOptions have been added, and the GsQuery methods are legacy.

The following methods have been added:

GsQueryOptions >> optionalPathTerms

GsQueryOptions >> optionalPathTerms:

GsQueryOptions >> setOptionalPathTerms

GsQueryOptions >> clearOptionalPathTerms

GsQueryOptions class >> optionalPathTerms

Introductory support for automatic management of selector path indexes

Selector path indexes are indexes on a computed value returned by a unary method selector, rather than the usual index that is directly on an instance variable value. These were introduced in v3.2 with the new indexing API, and have been usable for static data. However, you must manually manage any changes to the values that would affect the indexes.

This has been made somewhat easier in this release. Modification tracking support has been improved, and an example is now included with the distribution. This can be found under $GEMSTONE/examples/smalltalk/SelectorPathTermExample.gs.

The following method has been added:

Object >> aboutToModifyObject:atOffset:to:

Note that this example of automatic modification tracking is not fully tested or supported in this release, but is provided as an example for your own development.

Error handling

The updates to the PetitParser have improved query parsing error handling. Invalid formatting in a GsQuery string now provides useful messages for many kinds of errors.

The following classes have been added:

GsQueryParseError

GsQueryErrorHandlingParser

Indexing Stream Classes modified

To fix bug #44079, the class definition for BtreeReadStream has been modified. After upgrade, any persistent instances of this class, and its subclass RangeIndexReadStream, will be invalid.

It is not expected that customer applications create persistent instances of streams on index results. If any exist, they should be recreated after upgrade.

Set valued paths may not begin with asterisk

When creating an query or index, it has been disallowed for the first term on the path to be a set-valued collection. This disallows index paths starting with '*' and 'each.*', depending on the index and query API being used.

Cached instances require recompile

The upgrade to 3.3 will create new versions of a number of PetitParser classes. The older classes will remain, but will not have methods. Any existing instance of PetitParser classes are not automatically upgraded by the GemStone upgrade process.

PetitParser classes are used by the indexing system, but such instances are not persisted.

If you have created persistent instances of any of these classes, they should be rebuilt after upgrade.

Affected classes are:

Add continuousRestoreFromArchiveLogs: variant with delay

The following method has been added:

Repository >> continuousRestoreFromArchiveLogs:withDelay: 

This method is similar to continuousRestoreFromArchiveLogs:, with the additional option to specify a delay before the restore. Records are transferred immediately to the standby system but the processing of commits and checkpoints are delayed by the specified number of seconds to allow the system to be stopped to avoid restoring an operation on the database that is not desired.

Methods to get information about Hot Standby sessions

The following methods have been added, to determine if a hot standby logsender or logreceiver are running. Note that since a logsender or logreceiver may be started without passing in the associated master or slave stone, a zero does not prove that the given process is not present.

System class >> logreceiverSessionId
Return the session ID of the logreceiver process, or zero if no logreceiver is connected to the stone process.

System class >> logsenderSessionId
Return the session ID of the logsender process, or zero if no logsender is connected to the stone process.

Smalltalk reporting on logsender and logreceiver

A logsender or logreceiver uses a session slot. The return value from invoking System >> currentSessionNames now includes these by name. In addition, the results from System >> descriptionOfSession: now provides information on a logsender or logreceiver session; the session’s UserProfile slot is nil.

Other changes

The logsender will now detect and shut down if the master stone is in partial logging mode.

Improved performance for server files

Additional primitives and C level code changes improve performance when working with files on the server.

Improvements in handling extended characters

GsFile managing file locks

GsFile now has an interface to allow read or write locking a portion of a file. File locking services are provided by the operating system, so behavior is highly dependent on the operating system performing the lock operation. Consult the documentation for your host system to learn about the behavior of file locking for your system.

For processes running on UNIX based systems, file locks are advisory, which means locks are not enforced by the operating system and applications may freely ignore them.

For processes running on Microsoft Windows-based systems, file locks are mandatory, which means locks are enforced by the operating system and applications cannot ignore them. Also note that getStatusForLockKind:* is not valid on Windows, as an underlying system function is not available.

On UNIX-based systems, closing any handle referencing a given physical file forces all locks on that file held by the process to be released. For this reason, locks should not be used on any file which the process opens more than once.

Some systems do not support read locks if the file is opened in write-only mode or write locks if the file is open in read-only mode. Attempting to lock files opened in these manners may raise an error indicating a bad file descriptor.

The following methods have been added:

getStatusForLockKind: kind atOffset: offset forBytes: bytes
Tests if the receiver could be locked with the given arguments but without actually acquiring the lock. Returns information about a conflicting lock, if any. The kind argument must be a symbol that indicates the lock kind requested, and must be either #readLock or #writeLock. offset indicates the position within the receiver in bytes. bytes indicates the number of bytes starting at offset (0 means to the end of the file).

Returns an Array of 5 elements as described below. If the first element is false, then elements 2 through 5 contain information about a conflicting lock (there may be more than one) which prevented the lock from being available. If the first element is true, then element 2 will be nil and elements 3 through 5 will be -1.

1 - a Boolean: true if the lock would have been granted, otherwise false.

2 - a Symbol (#readLock or #writeLock): conflicting lock kind.

3 - a SmallInteger: start position of the conflicting lock.

4 - a SmallInteger: number of bytes held by the conflicting lock.

5 - a SmallInteger: process ID of the owner of the conflicting lock.

This method cannot be used for client files on Windows.

readLockAtOffset: offset forBytes: bytes
Requests a read lock on a portion of the receiver without blocking.

readLockAtOffset: offset forBytes: bytes waitTime: milliseconds
Requests a read lock on a portion of the receiver and blocks for up to milliseconds to acquire the lock.

readLockContents
Requests a read lock on the entire contents the receiver without blocking.

unlockAtOffset: offset forBytes: bytes
Releases a previously acquired lock on a portion the file referenced by the receiver. offset indicates the position within the receiver in bytes and bytes indicates the number of bytes to unlock (0 means unlock the file from offset to the end of the file).

unlockContents
Releases a previously acquired lock on contents of the receiver .

writeLockAtOffset: offset forBytes: bytes
Requests a write lock on a portion of the receiver without blocking.

writeLockAtOffset: offset forBytes: bytes waitTime: milliseconds
Requests a write lock on a portion of the receiver and blocks for up to milliseconds to acquire the lock.

writeLockContents
Requests a write lock on the entire contents the receiver without blocking.

nextPutAsUtf8 extended

nextPutAsUtf8: now accepts a Character as well as a String.

GsFile atEnd now returns true for empty file

When GsFile opened an empty file, previously the atEnd message returned false. Now, it will return true.

Other added method

serverCurrentDirectory
Returns a String, the current directory of this topaz -l or gem process.

New profiling options

ProfMonitor can now profile some memory-related activities, including:

• Object faults
• Page faults
• Time spent in in-memory garbage collection
• Use of temporary memory eden space

This allows you to correlate memory impact with specific method execution.

To specify these kinds of profiling, use the ProfMonitor >> setOptions: method, or a class method with the options: keyword, specifying an array with the type of profiling. The options are listed in Table 1.1. The options for type of profiling are mutually exclusive.

For example,

ProfMonitorTree 

	monitorBlock: [ code to profile ] 

	intervalNs: 100000

	options: { #objFaults }

When these memory monitoring options are used, in the resulting report, the sampling sections provide the per-method totals (leftmost columns) in units of the tallying option.

ProfMonitorTree 

	monitorBlock: [ code to profile ] 

	intervalNs: 100000

	options: { #objFaults . #cpu }

Profiling reports down to a percentage

Profiling methods with the downTo: argument allow you to limit the amount of result lines, making the results more readable. This keyword accepted an integer, the lower limit of the number of samples to report. However, if it was not clear before execution how many total samples would be taken, then this was of limited value.

Now, the downTo: keyword may be specified as a percentage, by using a SmallDouble between 0.01 and 0.99, as an alternative to an absolute number specified by an integer.

For example, to generate a profile report that includes samples for methods taking 10% or more of the total time:

ProfMonitorTree 

	monitorBlock: [ code to profile ] 

	downTo: 0.1

C function that accepts an array of callback function addresses

You may now pass callback functions to a C callout as an Array, rather than individually. The following methods have been added to support this:

CCallin >> copyBindTo: aBlock
Return a copy of the receiver which is bound to the specified block. The result would typically be used as second argument to CByteArray >> ccallinAt:put: when building an Array of function pointers.

CCallout >> bind
Attempt to resolve the C function described by the receiver, using dlopen() if needed, and dlsym() .

CByteArray >> ccallinAt: zeroBasedOffset put: aCCallin
Store the C address for a bound CCallin. Returns receiver.

CByteArray >>ccalloutAt: zeroBasedOffset put: aCCallout
Store the C address for a CCallout. Returns receiver.

Removed methods

The following methods, which were internal to the respective classes, have been removed during code refactoring:

CDeclaration >> readAlignedAttribute

CDeclaration >> readDeprecatedAttribute

CDeclaration >> readFormatAttribute

CDeclaration >> readNonnullAttribute

CHeader >> add:for:to:

CHeader >> createFunctionsInClass:library:select:

CHeader >> createInitializerInClass:forFunctions:library:

CHeader >> initializeFunctionsCodeForFunctions:library:

GemStone version no longer hardcoded in image

Previously, the GemStone shared library name in image methods including the specific version number. Now, this is computed from the current environment.

System Class

Collection classes

Class information and Fileout changes

No class-specific documentation for <myClass>, hierarchy is: 

Object

   <myClass>( ivar1 ivar2 ...

Socket classes

GsSocket class >> fromFileHandle: aSmallInteger
Create a non-blocking instance of the receiver which will use the specified file handle. The fileHandle must be the file descriptor of an open socket that was inherited from the parent when the gem or topaz -l process was forked, or a socket created by non-Gemstone C code. in this gem or topaz -l process. The non-Gemstone C code may be C application code that calls the GCI or C code called from a user action or through FFI.

The address family of the socket is determined by the process doing the fork when it accepts a connection, or by the non-Gemstone C code. The socket will be set to non-blocking and close-on-exec by this method.

GsSecureSocket class >> sslLibraryVersionString
Answer an instance of String which describes the version of OpenSSL library loaded by this session.

The following methods were added to GsSecureSocket, overriding the inherited version from GsSocket which was not correct for GsSecureSocket.

GsSecureSocket >> lastErrorString 

GsSecureSocket class >> lastErrorString 

GsSecureSocket >> acceptTimeoutMs:

Date and DateTime changes

ClassOrganizer changes

Repository

findReferencePath excludes internal implementation instances

The results of methods such findReferencePathToObject: produces a list of object representing the objects chain of references. Previously, this included objects such as LargeObjectNodes that are internal implementation details that cannot be accessed normally. Now, these are excluded from the result set, though they are still visible in the scan details.

GsExternalSession API for host login

Methods have been added to GsExternalSession to allow the host login information to be set in the parameters. The following instance methods have been added:

hostUsername:

hostPassword:

An instance creation method that includes host login information has been added:

GsExternalSession >> gemNRS:stoneNRS:username:password:
hostUsername:hostPassword:

An instance method to return the username has also been added, GsExteranalSession>>username

GsProcess stack report that includes method source code

A method has been added so programmatically generated stack reports can include the source code of the method:

GsProcess >> stackReportToLevel:withArgsAndTemps:	andMethods:includeSource:

Millisecond monitoring

Previously, statmonitor recorded the time as an Integer value, and if sampling rates smaller than 1 second were requested, these were recorded in incremented units rather than real time to accommodate VSD.

In VSD v4.0, the ability to read millisecond timestamps was added. The format is s.ms where s is seconds from January 1, 1970 and ms is the milliseconds within that second.

With v3.3, when statmonitor is specified with samples intervals of less than 1 second, timestamps are recorded using millisecond timestamps. VSD v4.0 and later will correctly graph and label these timestamps.

When sub-second time stamps are requested, statmonitor will initiate collecting stats on an rounded interval, to allow easier statistics reading. So for example, if 10 ms statistics are requested ( -I10) and the actual system time milliseconds is .734, statmonitor will delay the collecting the first statistic until the system time milliseconds is .740.

With recording real times for millisecond timestamps, there are some cases where samples may be skipped. The actual sample time is deemed "close enough" to the scheduled sample time if the actual sample time is within +- 10% of the scheduled sample time. Samples are skipped only if this difference exceeds 10% of the sample interval. To allow tracking, statmonitor has two additional statistics:

SamplesSkipped (Statmonitor)
Number of times statmonitor did not record statistics as a scheduled point in time.

SystemClockStuckCount (Statmonitor)
Number of time the system returned the same timestamp consecutively.

64-bit statistics

Previously, some statistics values could roll past the 32-bit unsigned integer range, which caused them to roll over to invalid values.

For statistics in which this occurred, in GemStone and for host statistics, the code now records 64-bit values. In VSD v4.0.2 and later, recorded statistics values that are outside the 32-bit range are automatically promoted to 64-bit, and will be displayed correctly.

Statmonitor automatic startup for Stones and remote caches

Configuration options have been added to allow you to specify that statmonitor should always be run when the stone is running. Configuration options allow monitoring Stone, remote shared page cache, and mid level shared page cache. These configuration options are:

STN_STATMONITOR_ARGS

GEM_STATMONITOR_ARGS

GEM_STATMONITOR_MID_CACHE_ARGS

These options are enabled by setting the configuration parameter to a valid set of statmonitor arguments, not including the name of the stone or cache. For example,

STN_STATMONITOR_ARGS = "-i5 -r -h24";

To allow the statmonitor output file location and names to be more easily managed for these automatically generated statmonitor data files, new options have been added to statmonitor, allowing much more control over output file names. The new options are described in the following sections.

If statmonitor fails to start, is does not prevent the stone or remote session from starting up.

statmonitor -F '%%S_%%H_%d-%m-%y_%H:%M:%S' gs64stone

Added statistics

The following new statistics are collected in v3.3:

CompressionCount (Pgsvr)
Number of times the compression library was called to compress data.

CompressionKbIn (Pgsvr)
Total size of data compressed before compression, expressed in kilobytes.

CompressionKbOut (Pgsvr)
Total size of data compressed after compression, expressed in kilobytes.

CompressionTimeCpu (Pgsvr)
CPU time in milliseconds spent performing data compression.

CompressionTimeReal (Pgsvr)
The real time in milliseconds spent performing data compression.

DecompressionCount (Pgsvr)
Number of times the compression library was called to decompress data.

DecompressionKbIn (Pgsvr)
Total size of data decompressed before decompression, expressed in kilobytes.

DecompressionKbOut (Pgsvr)
Total size of data decompressed after decompression, expressed in kilobytes.

DecompressionTimeCpu (Pgsvr)
CPU time in milliseconds spent performing data decompression.

DecompressionTimeReal (Pgsvr)
The real time in milliseconds spent performing data decompression.

ExtentGrowTimeMs (Stone)
Total amount of real time in milliseconds the stone has spent increasing the size of the repository by growing the extent (s).

ExtentGrowTimePerGrow (Stone)
Average amount of real time in microseconds it takes the stone to perform a single grow operation on an extent.

ExtentGrowTotal (Stone)
Number of times the stone has increased the size of the repository by growing the extent(s).

FreePagesPoolSize (Stone)
The number of pages in the freePool that the Stone maintains for its own use.

LogSenderBlockId (Stone)
The record ID of the last transaction log record read by the log sender process.

LogSenderFileId (Stone)
The file ID of the last transaction log read by the log sender process.

RecoverTimeLag (Stone)
The difference in commit time (restoreLogCommitTime - originalCommitTime), gives a relative idea of how hot a hot standby is.

SamplesSkipped (Statmon)
Number of times statmonitor did not record statistics as a scheduled point in time.

SystemClockStuckCount (Stone)
Number of time the system returned the same timestamp consecutively.

TotalObjectsCommitted (Stone)
Total number of new objects committed by all gems.

UserSessionsCount (Stone)
The total number of user sessions currently logged in to the system.

Renamed Statistics

The Gem statistic WorkingSetInvalidateAllCount has been renamed to WorkingSetClearedCount.

The Linux-only statistic CommittedAsKB has been renamed to CommittedASKB, to avoid the misleading name; this is the Linux system stat Committed_AS.

The Solaris-only statistic Recoverable has been renamed to RecoverableErrors for clarity.

the 32-bit statistic TotalNewObjsCommitted is replaced by a 64-bit statistic TotalNewObjectsCommitted.

Removed statistics

The following statistics have been obsolete, but were still recorded. They have been removed in this release:

AsyncWritesInProgress

BackupRecordPagesWrittenByGem

BackupRecordPagesWrittenByStone

CompressedLogPagesWrittenByGem

CompressedLogPagesWrittenByStone

CountMapLeafPagesWrittenByGem

CountMapLeafPagesWrittenByStone

DeadDataPagesWrittenByGem

DeadDataPagesWrittenByStone

EmptyBmLeafPagesWrittenByGem

EmptyBmLeafPagesWrittenByStone

LogRecordPagesWrittenByGem

LogRecordPagesWrittenByStone

LostOtPagesWrittenByGem

LostOtPagesWrittenByStone

MultObjPagesWrittenByGem

MultObjPagesWrittenByStone

RepBkupRestPagesWrittenByGem

RepBkupRestPagesWrittenByStone

Extent sizes always multiple of 16MB

The minimum extent size is now 16MB, and the size must be a multiple of 16MB.

This affects DBF_EXTENT_SIZES and DBF_PRE_GROW. Entries must be at least 16MB, and should be a multiple of 16MB. If your configuration file specifies a value that is not a multiple of 16MB, the next lowest multiple will be used.

For raw partitions, the DBF_EXTENT_SIZES entry should now be 16MB less than the size of the partition for optimal performance.

Additional option to manage commit record backlog

When a commit record backlog occurs, the oldest session is sent a sigAbort; after this sessions updates, then the next-oldest session becomes the oldest and will in turn get a sigAbort. When many sessions may be holding onto old commit records, and if the sessions timeout rather than respond immediately to the sigAbort, this can make resolving commit record backlogs difficult.

A configuration parameter has been added, STN_SIGNAL_ABORT_AGGRESSIVE, that instructs the system to send a sigAbort to a configurable number of sessions that would be eligible for sigAbort; that is, the sessions reference the oldest commit records that are older than STN_SIGNAL_ABORT_CR_BACKLOG. This allows a number of sessions to be sent sigAbort at once. This setting is off by default.

See STN_SIGNAL_ABORT_AGGRESSIVE.

Additional options for handing configuration parameters

In v3.3, there are additional features that provide flexibility in managing configuration options.

• The INCLUDE directive parameter has been added. This allows configuration files to be nested. It can be used multiple times to include multiple configuration files, and these can in turn nest further files. Headers in the log files include information on the order in which included configuration files are read. See INCLUDE.
• Topaz has a new -C option that allows you to pass in the actual configuration parameters settings on the command line, overriding settings in the configuration files specified by -e or -z options. This applies to linked sessions only. For more details, see Add -C option to pass in arbitrary configuration parameter values.
• The Gem process now accepts additional parameters, -e execonf and -C confParamsText, which may be provided via the NRS used when invoking the gemnetobject or other scripts.

For example, with topaz:

set gemnetid '!@santiam.gemtalksystems.com!gemnetobject -e $GEMSTONE/my.conf'

set gemnetid '!@santiam.gemtalksystems.com!gemnetobject -C GEM_TEMPOBJ_OOMSTATS_CSV=TRUE'

Runtime changes no longer write to system configuration file

Updates to the runtime configuration parameters #StnEpochGcEnabled or #StnSymbolGcEnabled previous added settings for STN_EPOCH_GC_ENABLED and STN_SYMBOL_GC_ENABLED to the system configuration. This was inconsistent with other runtime configuration parameters, which apply only for the running system. Changes are no longer appended to the system configuration file; to make persistent changes, you must manually edit the configuration file.

Use of units in configuration values

In v3.2, for configuration parameters that controls file and memory sizes, a feature was added to allow you to specify units of KB, MB, and GB, as well as omitting units to use the default size.

To avoid confusion and ambiguity, the default, maximum, and minimum values described in the configuration file now always include units, and the values printed in the Stone, Gem, and other logs now include the units.

Configuration values without units are still understood, as the default units of that parameter; it is not required that you update your configuration files.

Added configuration parameter features

The following configuration parameters have been added:

INCLUDE=config2.conf;   # will look in current directory

INCLUDE="$GEMSTONE/data/config3.conf";

scaledTimeout := cacheSize <= 32GB 

	ifTrue:[ (cacheSize / 32GB) * 120]

	ifFalse:[ 120 + ((cacheSize - 32GB / 268GB) * 300) ]

RT_ERR_UPGRADE_WARNING

Number 2486

This error is triggered when an attempt is made to login to a repository that has not been upgraded to 3.3.

STDB_ERR_BAD_NUMERIC_LIT

Number 1080

This error relates to a new feature, see Parsing custom numeric literals.

copydbf

File type: backup  fileId: 0 in a backup set with 2 files

gslist

pageaudit

pageaudit[info]: pageaudit gs64stone-pageAudit has been started, process 8500

Page Audit of Repository completed successfully - no issues found

pstack

pstack now supports the -h usage query.

removedbf

removedbf is no longer supported for remote use over a network connection. The -n and -p options, which did not function correctly in past releases, have been removed.

The -h option to return help text has been added.

startcachewarmer

startcachewarmer now reports a message in the stone log when the warming completes successfully.

Cache warming also now transparently handles the case where not enough user sessions are available for the specified or default number of cache warmer threads. Provided at least two sessions are available, the cachewarmer will reduce the requested number of sessions to match what is available.

It is now not an error to specify the stone name using NRS (see bug 45604 here)

startnetldi

waitstone

Waitstone now supports -h usage query.

Waitstone also now will wait for the SymbolGem to be ready; this is to support upgrade in which the SymbolGem requires extra time to convert Symbols.

GS_DEBUG_SSL_LOG_DIR disallowed in a fast build for security reasons

This environment variable causes diagnostic output to be sent to a file. To avoid a potential security risk, this has been disallowed; the environment variable is available in slow and no-op executables only.

Additional variables to manage log deletion

As described under Process log files and deletion policy, the variables GS_KEEP_ALL_LOGS and GS_FORCE_CLEAN_LOG_FILE_DELETE have been added.

Single-line command serializing

A number of changes in this release are designed to improve readability of topaz code.

It is now possible to enter topaz commands on a single line, by separating with a semicolon (;) character. For example:

topaz 1> time ; send SystemRepository fileSizeReport ; time 

These behave as if they were each entered on a separate topaz line, with the following exceptions:

• SPAWN and SHELL pass the remainder of the line to the OS shell.
• IFERR, IFERROR are disallowed with semicolon
• REMARK, RUN, PRINTIT, and DOIT ignore the rest of the line.
• EXEC will treat as Smalltalk source code anything up to the % character.

UTF-8 related changes

Topaz executable argument changes

topaz -l -C 'GEM_TEMPOBJ_CACHE_SIZE = 1GB; GEM_TEMPOBJ_OOMSTATS_CSV = TRUE;'

Warning on configuration file not found

When topaz starts up, it searches for a configuration file based on the command line arguments -z and -e, otherwise for the environment variables GEMSTONE_SYS_CONF and GEMSTONE_EXE_CONF, and finally on the default name for topaz, gem.conf.

Previously, the name of the configuration files and any errors in finding these files was reported in the first part of the topaz header. Now, an additional warning is printed at the end of the headers section, if either of these cannot be resolved to a valid file. This is particularly intended to catch errors in -z and -e arguments.

Line limit increased

The maximum command line is now 64K characters

New commands

topaz 1> exec SystemRepository markForCollection %

ClassOrganizer new literalsReport: anObject

Changes in the ordering of lines within status output

The status command outputs information on the current state of topaz variables. There are changes in the ordering of lines and what information is included.

The sourcestringclass and fileformat information is now under the current settings section.

Lines have also been added for interactive pause on warnings and transaction mode.

topaz fileout uses protocol in Behavior

The FILEOUT command in topaz now uses the Behavior protocol to generate fileout text.

Added functions

(BoolType) GciAll7Bit(

    const char* str,

    size_t *len

    );

(int64) GciExecuteStrFetchBytes(

    const char* source,

    int64 sourceSize,

    OopType sourceClass,

    OopType contextObject,

    OopType symbolList,

    ByteType *result,

    int64 maxResultSize

    );

(void) GciNbExecuteStrFetchBytes(

    const char* source,

    int64 sourceSize,

    OopType sourceClass,

    OopType contextObject,

    OopType symbolList,

    ByteType *result,

    int64 maxResultSize,

    );

Changed functions

(int64) GciFetchUtf8Bytes_(

   OopType aString, int64 startIndex, ByteType *buf, 

   int64 bufSize, OopType *utf8String, int flags);

In the flags argument, you may now pass 2, indicating to put a generated description in *buf instead of signalling an error.

Deprecated functions

The following functions have been deprecated in v3.3:

GciClampedTraverseObjs
use GciClampedTrav

GciFetchObjInfo
use GciFetchObjectInfo

GciNbClampedTraverseObjs
use GciNbClampedTrav

GciNbPerformTraverse,GciNbPerformTraverse_
use GciNbPerformTrav

GciStep, GciStep_, GciNbStep, GcNbStep_
Debuggers should use instance methods in GsProcess.

GciPathToStr

GciStrToPath

Removed Functions

The following obsolete functions have been removed:

GciInitNoSharedCache

GciUseSharedCache

The following GSCI functions have been removed; they are no longer valid with 64-bit stats:

GcsiShrPcMonStatAtOffset

GcsiStnStatAtOffset

Other Changes affecting the GCI interface

Linux Compile and Link Information

g++ -fmessage-length=0 -fcheck-new -O3 -ggdb -m64 -pipe 

-D_REENTRANT -D_GNU_SOURCE-pthread -fPIC -fno-strict-aliasing

-fno-exceptions -I$GEMSTONE/include -x c++ -c userCode.c 

-o userCode.o 

-Wformat -Wtrigraphs -Wcomment -Wsystem-headers -Wtrigraphs 

-Wno-aggregate-return -Wswitch -Wshadow -Wunused-value 

-Wunused-variable -Wunused-label -Wno-unused-function 

-Wchar-subscripts -Wmissing-braces -Wmultichar -Wparentheses 

-Wsign-compare -Wsign-promo -Wwrite-strings -Wreturn-type 

-Wuninitialized

g++ -shared -Wl,-Bdynamic,-hlibuserAct.so userCode.o 

$GEMSTONE/lib/gciualib.o -o libuserAct.so -m64 -lpthread -lcrypt -ldl -lc -lm -lrt -lpam -lpam_misc -Wl,-z,muldefs 

-Wl,--warn-unresolved-symbols

g++ userCode.o $GEMSTONE/lib/gcirtlobj.o -Wl,-traditional

-Wl,--warn-unresolved-symbols -m64 -lpthread -lcrypt -ldl -lc 

-lm -lrt -lpam -lpam_misc -Wl,-z,muldefs -o userAppl

Solaris on SPARC Compile and Link Information

There are corrections in the compile line, but otherwise there is no change from v3.2; for completeness, all information is included here.

CC -xO4 -xcode=pic32 -xarch=v9 -mt -xchip=ultra2 

-I$GEMSTONE/include -features=no%except -D_REENTRANT 

-D_POSIX_PTHREAD_SEMANTICS -features=no%anachronisms 

-c userCode.c -o userCode.o

CC -xarch=v9 -G -Bsymbolic -h libuserAct.so -i userCode.o 

$GEMSTONE/lib/gciualib.o -o libuserAct.so -Bdynamic -lc 

-lpthread -ldl -lrt -lsocket -lnsl -lm -lpam -lCrun -znodefs

CC -xildoff -xarch=v9 -i userCode.o $GEMSTONE/lib/gcirtlobj.o 

-z nodefs -Bdynamic -lc -lpthread -ldl -lrt -lsocket -lnsl 

-lm -lpam -lCrun -o userAppl

Solaris on x86 Compile and Link Information

There are corrections in the compile line, but otherwise there is no change from v3.2; for completeness, all information is included here.

CC -xO4 -m64 -xarch=generic -Kpic -mt -D_REENTRANT 

-D_POSIX_PTHREAD_SEMANTICS -I$GEMSTONE/include 

-features=no%except -c userCode.c -o userCode.o

CC -m64 -xarch=generic -G -Bsymbolic -h libuserAct.so -i userCode.o

$GEMSTONE/lib/gciualib.o -o libuserAct.so -Bdynamic -lc 

-lpthread -ldl -lrt -lsocket -lnsl -lm -lpam -lCrun -z nodefs

CC -xildoff -m64 -xarch=generic -i userCode.o 

$GEMSTONE/lib/gcirtlobj.o -z nodefs -Bdynamic -lc -lpthread 

-ldl -lrt -lsocket -lnsl -lm -lpam -lCrun -o userAppl

AIX Compile and Link Information

xlC_r -O3 -qstrict -qalias=noansi -q64 -+ -qpic 

-qthreaded -qarch=pwr6 -qtune=balanced -D_LARGEFILE64_SOURCE 

-DFLG_AIX_VERSION=version -D_REENTRANT -D_THREAD_SAFE 

-qminimaltoc -qlist=offset -qmaxmem=-1 -qsuppress=1500-010:1500

-029:1540-1103:1540-2907:1540-0804:1540-1281:1540-1090 -qnoeh 

-I$GEMSTONE/include -c userCode.c -o userCode.o

xlC_r -G -Wl,-bdatapsize:64K -Wl,-btextpsize:64K 

-Wl,-bstackpsize:64K -q64 userCode.o $GEMSTONE/lib/gciualib.o 

-o libuserAct.so -e GciUserActionLibraryMain -L/usr/vacpp/lib 

-lpthreads -lc_r -lC_r -lm -ldl -lbsd -lpam -Wl,-berok

xlC_r -Wl,-bdatapsize:64K -Wl,-btextpsize:64K 

-Wl,-bstackpsize:64K -q64 userCode.o $GEMSTONE/lib/gcirtlobj.o 

-Wl,-berok -L/usr/vacpp/lib -lpthreads -lc_r -lC_r -lm -ldl 

-lbsd -lpam -Wl,-brtllib -o userAppl

DARWIN Compile and Link Information

g++ -fmessage-length=0 -O3 -ggdb -m64 -pipe -fPIC 

-fno-strict-aliasing  -D_LARGEFILE64_SOURCE -D_XOPEN_SOURCE 

-D_REENTRANT -D_GNU_SOURCE -I$GEMSTONE/include -x c++ 

-c userCode.c -o userCode.o 

-Wformat -Wtrigraphs -Wcomment -Wsystem-headers -Wtrigraphs 

-Wno-aggregate-return -Wswitch -Wshadow -Wunused-value 

-Wunused-variable -Wunused-label -Wno-unused-function 

-Wchar-subscripts -Wconversion -Wmissing-braces -Wmultichar 

-Wparentheses -Wsign-compare -Wsign-promo -Wwrite-strings 

-Wreturn-type 

g++ -dynamiclib userCode.o $GEMSTONE/lib/gciualib.o 

-o libuserAct.dylib -m64 -lpthread -ldl -lc -lm -lpam -undefined

dynamic_lookup 

g++ userCode.o $GEMSTONE/lib/gcirtlobj.o -undefined dynamic_lookup 

-m64 -lpthread -ldl -lc -lm -lpam -o userAppl

Windows Compile and Link Information

This information is unchanged from v3.2

cl /W3 /Zi /MD /O2 /Oy- -DNDEBUG /TP /nologo /D_LP64 /D_AMD64_

/D_CONSOLE /D_DLL /DWIN32_LEAN_AND_MEAN /D_CRT_SECURE_NO_WARNINGS 

/DNATIVE /I 'VisualStudioInstallPath\atlmfc\include' 

/I 'VisualStudioInstallPath\VC\include' 

/I 'C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Include'

/I '%GEMSTONE%\include' -c userCode.c -FouserCode.obj

link /LIBPATH:"VisualStudioInstallPath\VC\lib\amd64" 

/LIBPATH:"C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\x64"

/OPT:REF /INCREMENTAL:NO /MAP /nologo /MANIFEST 

/MANIFESTFILE:userAppl.exe.manifest 

/MANIFESTUAC:"level='asInvoker'" userCode.obj 

%GEMSTONE%\lib\gcirpc.lib ws2_32.lib netapi32.lib advapi32.lib 

comdlg32.lib user32.lib gdi32.lib kernel32.lib winspool.lib 

/out:userAppl.exe