CRSP_CCM_LINK - Security Link History
Only one set of link information is presented for each calendar range in the Compustat GVKEY and IID history. Soft LX and LD links are included if there is a match that indicates an alternate record or a security on a non-US exchange. CRSP provides no automated methods to use these soft links to connect to CRSP data, but the information is available for the user.
Native Link usage provides access to all Compustat records, regardless of whether or not securities are in the CRSP universe.
|GVKEY*||integer, primary key (1)||Compustat GVKEY|
|LIID||char(3), primary key (2)||Compustat IID. Dummy IID assigned with an “X” suffix during a range when company data exists but no Compustat security is identified.|
|LINKDT||integer (date), primary key (3)||First effective calendar date of link record range|
|LINKENDDT||integer (date)||Last effective calendar date of link record range|
|LPERMNO||integer||Linked CRSP PERMNO, 0 if no CRSP security link exists|
|LPERMCO||integer||Linked CRSP PERMCO, 0 if no CRSP company link exists|
Primary issue marker for the link. Based on Compustat Primary/Joiner flag (PRIMISS), indicating whether this link is to Compustat’s marked primary security during this range.
Link type code. Each link is given a code describing the connection between the CRSP and Compustat data. Values are:
* - The GVKEY is the primary key of all Compustat company records when using the native link. In CRSPAccess programming this field is not present in the structure but inherited from the CCMID item in the master structure for the company. In standalone usage the GVKEY field is included.