Thanks again, but I am still considering PROC IMPORT rather than DATA notwithstanding the shortcomings due to another reason. Here I attach one example. This file was created by CMPT_ME_RETS using the 201911 CRSP database. It contains
value- and equal-weighted returns for size portfolios. Each record contains returns for:
Negative (not used) 30% 40% 30% 5 Quintiles 10 Deciles
The portfolios are constructed at the end of Jun. The annual returns are from January
to December.
Missing data are indicated by -99.99 or -999.
Value Weight Returns -- Monthly
,<= 0,Lo 30,Med 40,Hi 30,Lo 20,Qnt 2,Qnt 3,Qnt 4,Hi 20,Lo 10,Dec 2,Dec 3,Dec 4,Dec 5,Dec 6,Dec 7,Dec 8,Dec 9,Hi 10
192607, -99.99, 0.14, 1.59, 3.42, 0.37, 0.78, 1.68, 1.39, 3.67, -0.12, 0.52, -0.05, 1.31, 1.21, 2.04, 1.58, 1.29, 3.53, 3.71
192608, -99.99, 3.21, 2.77, 2.91, 2.26, 3.51, 3.75, 1.53, 3.07, 1.33, 2.55, 4.00, 3.20, 2.81, 4.45, 1.61, 1.49, 0.61, 3.79
192609, -99.99, -1.74, -0.88, 0.80, -1.39, -1.06, 0.05, -0.26, 0.81, 0.59, -2.00, -2.01, -0.46, -0.06, 0.14, -2.02, 0.74, -0.77, 1.25 Again the variable name row starts with a comma here too. However, the variable names are not appropriate enough for SAS to recognize since they contain not only math symbols such as <= 0 but also blanks such as Lo 30. Actually, PROC IMPORT does a great job in dealing with those situations.
... View more