Field Order in Version String

The order in which the fields appear in the dataserver version string depends on the version of the server you are running.

The fields in version 12.5.0.1, in order, are:

  1. Product.

  2. Version number and SWR.

  3. Release type: production (P), beta, or SWR version.

  4. Platform identifier.

  5. Operating system release under which the binary was compiled. This number is hard coded; it is not determined from your operating system.

  6. Server

  7. “Build number” – this is a Sybase internal reference.

  8. Mode: optimized (dataserver) or debug (diagserver).

  9. Compilation date and time.

In Version 11.9.2, the version string appears as follows (this example is from Sun Solaris):

Adaptive Server Enterprise/11.9.2/1031/P/Sun_svr4/OS 5.5.1/FBO
/Fri Aug 14 06:26:45 1998

The fields, in order, are:

  1. Product.

  2. Version number.

  3. “Build number” - this is a Sybase internal reference.

  4. Release type: production (P), beta (B) or SWR version.

  5. Platform identifier.

  6. Operating system release under which the binary was compiled. This number is hard coded; it is not determined from your operating system.

  7. Codeline used for this release - a Sybase internal reference.

  8. “Build number” - a Sybase internal reference.

  9. 32-bit or 64-bit system indicator.

  10. Type of post-build optimization server.

  11. Compilation date and time.

An example of the 12.5.0.1 version string from Sun Solaris follows (FBO stands for Feedback Optimized):

Adaptive Server Enterprise/12.5.0.1/SWR 9981 IR/P/Sun_svr4/OS 5.8/rel12501/1776/32-bit/FBO/Mon Feb 25 23:35:46 2002