OrCAD Symbol Libraries - Parts with /SM or /SO or /WHATEVER suffixes?

[mbendzick]

Has anyone learned deep enough info about OrCAD symbol libraries to know what is going on with symbols that have forward-slash endings, such as /SM or /SO or /WHATEVER?  These seem to be cousins of their non-slash parts, and copying one seems to copy them all.

How would one use those to an advantage?  How would one kill off unwanted connections in a library?

Process I just did that makes things awkward:
I have symbol "HEADER 20X2 WITH MTG PINS".  I copied and renamed a new version "HEADER 20X2 WITH AL PINS".  These seem to have their genesis with OrCAD's provided libraries, "HEADER 20X2" specifically.  But now all of the "HEADER 20X2", "HEADER 20X2 WITH MTG PINS", and "HEADER 20X2 WITH AL PINS" tie back to "HEADER 20X2/SM", so changes to any of those 3 symbols take precedence in changing the /SM part.

I'd like to just make "HEADER 20X2 WITH AL PINS" have no relatives.

Thanks in advance!

[nctnico]

It would help to tell us which version of Orcad and which program you are using.

[mbendzick]

Found out more about this - it applies to at least version 9 through 16.6.  They are "Package Aliases".  Where a normal symbol has just an icon next to it in the library list that looks like an AND gate, a part with aliases will also have a small hyphen in the AND gate body.  This means that it shares the graphical and pin design with other parts, but has unique properties.  The intent of this "Feature" was to allow you to make a 7400 in a DIP, a 7400 in an SOIC, and a 7400 in a TSSOP, all using the same symbol, but with different orderable part number and footprint name attributes pre-assigned in the symbol.