How does TEM identify individual patches for SUSE Linux Enterprise?

Technote (troubleshooting)


Problem(Abstract)

This article dicsusses the two ID schemes used in the "Patches for SUSE Linux Enterprise" site: "Patch-xxxxx" and "Patch-Bymmddnn".

Resolving the problem

TEM uses two ID schemes for the "Patches for SUSE Linux Enterprise" site: "Patch-xxxxx" and "Patch-Bymmddnn".

"Patch-xxxxx"

ID's that start with "Patch-xxxxx", where "xxxxx" is a 4 or 5 digit number are based on the patch-ID assigned by Novell. The majority of security patches in the SUSE Patch Support Database (PSDB) contains a patch-ID. The patch-ID can be located under the "Applies to" section of each patch page.

Example: PATCH-11377 for Security update for Mozilla..

"Patch-Bymmddnn"

ID's that start with "Patch-Bymmddnn", where "ymmddnn" is a 7 digit number are TEM/BigFix assigned IDs to identify patches that do not have a patch-ID assigned by Novell.

To accommodate the absence of the patch-ID, TEM assigns an ID derived from the source release date and number of patches released on that day. PATCH-Bymmddnn (B:BigFix Inc.; y:Year; mm:Month; dd:Day; nn:Iterator for multiple patches without patch-ID released on the same day).

Example: PATCH-B6092201 for Security update for Mono and PATCH-B6092202 for Security update for mysql..

Historical Number

391

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Endpoint Manager

Software version:

Version Independent

Operating system(s):

Platform Independent

Reference #:

1506038

Modified date:

2013-11-11

Translate my page

Machine Translation

Content navigation