Study: 7632 Name: Mortality Detail Files, 1968-1991 Dataset: 6 Name: 1972 File CARD CBLT 80 4908 cb72.s7632 CARD DATA 80 983001 da72.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb72.s7632 OSIR DATA 80 983001 odata72.s7632 OSIR DICT 80 36 odict72.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 6: 1, 53, 3, 70 Dataset: 7 Name: 1973 File CARD CBLT 80 4908 cb73.s7632 CARD DATA 80 1975126 da73.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb73.s7632 OSIR DATA 80 1975126 odata73.s7632 OSIR DICT 80 36 odict73.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 7: 1, 53, 3, 70 Dataset: 8 Name: 1974 File CARD CBLT 80 4908 cb74.s7632 CARD DATA 80 1936476 da74.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb74.s7632 OSIR DATA 80 1936476 odata74.s7632 OSIR DICT 80 36 odict74.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 8: 1, 53, 3, 70 Dataset: 9 Name: 1975 File CARD CBLT 80 4908 cb75.s7632 CARD DATA 80 1895135 da75.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb75.s7632 OSIR DATA 80 1895135 odata75.s7632 OSIR DICT 80 36 odict75.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 9: 1, 53, 3, 70 Dataset: 10 Name: 1976 File CARD CBLT 80 4908 cb76.s7632 CARD DATA 80 1911907 da76.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb76.s7632 OSIR DATA 80 1911907 odata76.s7632 OSIR DICT 80 36 odict76.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 10: 1, 53, 3, 70 Dataset: 11 Name: 1977 File CARD CBLT 80 4908 cb77.s7632 CARD DATA 80 1902106 da77.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb77.s7632 OSIR DATA 80 1902106 odata77.s7632 OSIR DICT 80 36 odict77.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 11: 1, 53, 3, 70 Dataset: 12 Name: 1978 File CARD CBLT 80 4908 cb78.s7632 CARD DATA 80 1930627 da78.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb78.s7632 OSIR DATA 80 1930627 odata78.s7632 OSIR DICT 80 36 odict78.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 12: 1, 53, 3, 70 Dataset: 13 Name: 1969 File CARD CBLT 80 4908 cb69.s7632 CARD DATA 80 1921990 da69.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb69.s7632 OSIR DATA 80 1921990 odata69.s7632 OSIR DICT 80 36 odict69.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 13: 1, 53, 3, 70 Dataset: 14 Name: 1970 File CARD CBLT 80 4908 cb70.s7632 CARD DATA 80 1922966 da70.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb70.s7632 OSIR DATA 80 1922966 odata70.s7632 OSIR DICT 80 36 odict70.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 14: 1, 53, 3, 70 Dataset: 15 Name: 1971 File CARD CBLT 80 4908 cb71.s7632 CARD DATA 80 1929476 da71.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb71.s7632 OSIR DATA 80 1929476 odata71.s7632 OSIR DICT 80 36 odict71.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 15: 1, 53, 3, 70 Dataset: 16 Name: 1968 File CARD CBLT 80 4908 cb68.s7632 CARD DATA 80 1930082 da68.s7632 CARD SJCC 80 240 sp7632cd.y6878 OSIR CBLT 80 4908 cb68.s7632 OSIR DATA 80 1930082 odata68.s7632 OSIR DICT 80 36 odict68.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 240 sp7632lr.y6878 Also see the following paragraph(s) for study 7632 dataset 16: 1, 53, 3, 70 Dataset: 17 Name: 1980 File OSIR CBLT 80 5648 cb80.s7632 OSIR DATA 86 1993137 data80.s7632 OSIR DICT 80 39 dict80.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 31484 sp7632lr.y7980 Also see the following paragraph(s) for study 7632 dataset 17: 1, 3, 53, 70 Dataset: 18 Name: 1979 File OSIR CBLT 80 5648 cb79.s7632 OSIR DATA 86 1916776 data79.s7632 OSIR DICT 80 39 dict79.s7632 This file is a Type 1 OSIRIS dictionary or codebook/dictionary. These files must be transferred in image (or binary) mode and may require reformatting to 80 character record length on the receiving computer. OSIR SJCC 80 287 sp7632lr.y7980 Also see the following paragraph(s) for study 7632 dataset 18: 70, 1, 3, 53 Dataset: 19 Name: 1981 File LREC DATA 159 1981309 da7632.yr81 Also see the following paragraph(s) for study 7632 dataset 19: 70, 21 Dataset: 20 Name: 1982 File LREC DATA 159 1977957 da7632.y82 Also see the following paragraph(s) for study 7632 dataset 20: 70, 21 Dataset: 21 Name: 1983 File LREC DATA 159 2022190 da7632.y83 Also see the following paragraph(s) for study 7632 dataset 21: 70, 21 Dataset: 22 Name: 1984 File LREC DATA 159 2042304 da7632.yr84 Also see the following paragraph(s) for study 7632 dataset 22: 70, 21 Dataset: 23 Name: 1985 File LREC DATA 159 2089378 da7632.y85 Also see the following paragraph(s) for study 7632 dataset 23: 70, 21 Dataset: 24 Name: 1986 File LREC DATA 159 2108384 da7632.y86 Also see the following paragraph(s) for study 7632 dataset 24: 70, 21 Dataset: 25 Name: 1987 File LREC DATA 159 2126342 da7632.y87 Also see the following paragraph(s) for study 7632 dataset 25: 70, 21 Dataset: 26 Name: 1988 File LREC CBPD 8816 87084 cb7632.y88.pdf LREC DATA 159 2171196 da7632.y88 Also see the following paragraph(s) for study 7632 dataset 26: 481, 70, 21 Dataset: 27 Name: 1989 File LREC CBPD 10024 112678 cb7632.yr89.pdf LREC DATA 159 2153859 da7632.yr89 Also see the following paragraph(s) for study 7632 dataset 27: 481, 70, 21 Dataset: 28 Name: 1990 File LREC CBPD 10953 108863 cb7632.yr90.pdf LREC DATA 159 2151890 da7632.yr90 Also see the following paragraph(s) for study 7632 dataset 28: 481, 70, 21 Dataset: 29 Name: 1991 File LREC CBPD 9789 103232 cb7632.yr91.pdf LREC DATA 159 2173060 da7632.yr91 Also see the following paragraph(s) for study 7632 dataset 29: 481, 70, 21 Dataset notes: Paragraph #1: Users are informed that OSIRIS dictionary/codebook files are stored in EBCDIC. When downloading these files via FTP, please make sure that the image or binary option is set even if you are downloading the files unzipped. The image or binary option must also be set when these files are moved from one system to another locally. Users are reminded that in order to use the OSIRIS dictionary/codebook and data files in an interface such as the one in the SAS program package, the data file must also be in EBCDIC. To allow users to use the OSIRIS data independently of the OSIRIS dictionary/codebook files, the data files have been stored in ASCII. Therefore, before running the dictionary/codebook and data files through this interface, the data file would need to be converted from ASCII to EBCDIC. Users are urged to consult with their local support staff to determine what procedures are to be used to do the necessary conversions locally. However, this should be a fairly straightforward process in most cases. As an example for a user in an UNIX environment, the following steps get the user an EBCDIC file that can then be used with the OSIRIS interface (the example is for study 8764.) tr -d \\n < da8764 > da8764b dd if=da8764b of=da8764dd conv=ebcdic Please note that this series of commands generates a stream file (in this case da8764dd) which is in EBCDIC. Therefore, whenever you again need an ASCII version of the OSIRIS data file, return to the original file that you downloaded from ICPSR. Do not attempt to convert this EBCDIC file back to ASCII. Such a conversion would not generate a file that would be identical to the OSIRIS data file originally downloaded from ICPSR. The OSIRIS dictionary/codebook file must never be converted to ASCII since dictionary/codebook files contain binary fields that would be corrupted by such a conversion. Paragraph #53: Some of the machine-readable codebook files are supplied with carriage control characters in column one of each record. Users should check the first few records in these files to determine whether the files they have received contain these characters. If the file does have carriage control characters in column one (usually a 1, -, +, or blank and with either a 1, -, or + appearing in the first column of the first record), the file should be listed with a print program that can interpret these characters. As an alternative, the first column of each record can be skipped and the remaining columns may be listed. When carriage control characters do not exist in a file, all columns in each record can be routinely printed. These listings document the appropriate data files. Paragraph #3: Users are informed that OSIRIS dictionary files are stored in EBCDIC. When downloading the dictionary files via FTP, please make sure that the image or binary option is set even if you are downloading the files unzipped. The image or binary option must also be set when these files are moved from one system to another locally. Users are reminded that in order to use the OSIRIS dictionary and data files in an interface such as the one in the SAS program package, the data file must also be in EBCDIC. To allow users to use the OSIRIS data independently of the OSIRIS dictionaries, the data files have been stored in ASCII. Therefore, before running the dictionary and data files through this interface, the data file would need to be converted from ASCII to EBCDIC. Users are urged to consult with their local support staff to determine what procedures are to be used to do the necessary conversions locally. However, this should be a fairly straightforward process in most cases. As an example for a user in an UNIX environment, the following steps get the user an EBCDIC file that can then be used with the OSIRIS interface (the example is for study 8764.) tr -d \\n < da8764 > da8764b dd if=da8764b of=da8764dd conv=ebcdic Please note that this series of commands generates a stream file (in this case da8764dd) which is in EBCDIC. Therefore, whenever you again need an ASCII version of the OSIRIS data file, return to the original file that you downloaded from ICPSR. Do not attempt to convert this EBCDIC file back to ASCII. Such a conversion would not generate a file that would be identical to the OSIRIS data file originally downloaded from ICPSR. The OSIRIS dictionary file must never be converted to ASCII since dictionaries contain binary fields that would be corrupted by such a conversion. Paragraph #70: The Mortality Detail Files, 1968-1991 (ICPSR 7632) is a large collection of data averaging approximately one million units of analysis for 1972 and over two million for each of the years from 1968-1971 and 1973-1991. Users should note that data for 1968 through 1980 have been processed by the Consortium; data for 1981 through 1991 are supplied as received by ICPSR. The data are organized by year so that one year's worth of information is in one file. For OSIRIS users, the dictionary file remains the same for the 1968 through 1978 period. There is a separate dictionary for the 1979-1980 period. The machine-readable codebook information and the SPSS control cards remain the same for each year from 1968-1978. There is a separate machine-readable codebook and SPSS control cards for the 1979-1980 period. Ten separate hard copy codebook volumes document the 1968-1978, 1979-1980, 1981-1982, 1983-1984, 1985, 1986-1987, 1988, 1989, 1990, and 1991 years respectively. Paragraph #21: Data from this collection are supplied in the same format as received by the Consortium and with their original documentation. Paragraph #481: In October 1998 ICPSR began releasing codebooks, previously available only in paper copy, in Portable Document Format (PDF). This was possible because of a commitment by ICPSR, supported in part by the National Science Foundation (SBR-9617813), to make documentation for all past ICPSR holdings available in machine-readable format. The documentation for this collection was converted to PDF format as part of that effort. Please note that the PDF files created in this process are not edited. The resulting PDF documents may not be fully searchable. Additionally, there are no other updates performed on these collections during the document conversion process. Files with .PDF extensions are provided as an electronic image file in Portable Document File (PDF) format. The PDF format was developed by Adobe Systems Incorporated and can be accessed using the Adobe Acrobat Reader. A copy of the current Acrobat Reader can be downloaded from the Adobe Systems Incorporated Website at: http://www.adobe.com Users are reminded to make sure that the image or binary option is set when downloading the electronic image files via FTP, even if the files are being downloaded unzipped. Additionally, the image or binary option will most likely also need to be set when PDF files are moved from one system to another locally.