Difference between revisions of "Version Decoder Ring"

From MicroFocusInternationalWiki
Jump to: navigation, search
m (more table, some tweaks)
m (tweaked 6.x text)
Line 13: Line 13:
 
In Netware 6.0, version numbers incremented more consistently, but the version major code  
 
In Netware 6.0, version numbers incremented more consistently, but the version major code  
 
was still "5." -- justified by noting the kernel hadn't changed as much as the application  
 
was still "5." -- justified by noting the kernel hadn't changed as much as the application  
products.
+
products.  The 2nd number should be a "60".
  
 
NW6.0 SP3 abend logs may not list module date info; this was added in later support packs.
 
NW6.0 SP3 abend logs may not list module date info; this was added in later support packs.
  
 
=== Netware 6.5 ===
 
=== Netware 6.5 ===
Finally, in NW6.5 at and after Support Pack 3, the abend log shows the major number was bumped and the increments were consistent,
+
Finally, in NW6.5 at and after Support Pack 3, the abend log shows the Product Version (PVER line)
but version shows a leading 5 with the 2nd number bumped.  
+
and the increments were consistent,
 +
but the version still shows a leading 5 with the 2nd number bumped ("70").  
 
Some required patches added the code "CPR" (for "Critical Product Release") after the version
 
Some required patches added the code "CPR" (for "Critical Product Release") after the version
 
to indicate an important update of the kernel or other core code between Support Packs.
 
to indicate an important update of the kernel or other core code between Support Packs.
 +
 +
=== The Story So Far ===
 
{|
 
{|
 
|+ Netware 5.x/6.0 Version Decoder Ring
 
|+ Netware 5.x/6.0 Version Decoder Ring

Revision as of 20:31, 18 April 2007

Draft Netware Version Wiki

Starting point for Netware Version (tracking) wiki -- for those who need to maintain older configurations.

Only NW6.5 is currently supported. For older versions, this page reflects community wisdom only.

Netware 5.x

Netware 5.0 and 5.1 use overlapping version strings. In reading abend logs, the version string (line 2 of the Abend entry, right after the abend number) may be ambiguous between several versions, and you will need the date of the server.nlm file or other additional information to decode the critter.

Netware 6.0

In Netware 6.0, version numbers incremented more consistently, but the version major code was still "5." -- justified by noting the kernel hadn't changed as much as the application products. The 2nd number should be a "60".

NW6.0 SP3 abend logs may not list module date info; this was added in later support packs.

Netware 6.5

Finally, in NW6.5 at and after Support Pack 3, the abend log shows the Product Version (PVER line) and the increments were consistent, but the version still shows a leading 5 with the 2nd number bumped ("70"). Some required patches added the code "CPR" (for "Critical Product Release") after the version to indicate an important update of the kernel or other core code between Support Packs.

The Story So Far

Netware 5.x/6.0 Version Decoder Ring
OS+Support Pack Version String "Decimal" Server.NLM Date
NW5.1SP2 5.00j __ September 21, 2000
NW5.1SP5 5.00_ 5.00.10 July 10, 2002
NW5.1SP7 5.00k 5.00.10 December 9, 2003
NW5.1SP8 5.00l 5.00.11 January 19, 2005
NW60SP3 __ 5.60.03 March 27, 2003
NW60SP5 __ 5.60.05 May 27, 2004
NW65SP1 __ 5.70 December 11, 2003
NW65SP2 6.50.02 5.70.02 June 11, 2004
NW65SP3 CPR PVER: 6.50.03 5.70.03 May 23, 2005
NW65SP4 PVER: 6.50.04 5.70.04 August 15, 2005
NW65SP5 __ 5.70.05 April 11, 2006
NW65SP6 6.50.06 5.70.06 October 26, 2006

Room for Corrections

Looking forward to the sysops' notes on this page.