"Wrong with code" is awful vague.
Are there errors in the log?: Post the code and log in a code box opened with the "</>" to maintain formatting of error messages.
No output? Post any log in a code box.
Unexpected output? In this case copy and paste a few lines of the text file to read into a text box opened with the </> icon.
Note that your codebook has this very important line:
Also enclosed is a complete description of the comma delimited file or CSV file which the
Assessor of Property has made available.
That means that the FIXED column approach, i.e. a "start and end point" to read you are attempting is just plain wrong. Commas separate the values unless you have modified the file and that is on you.
CSV files should have the delimiter option on the INFILE statement such as DLM=',' to use commas. If there is any text in long fields that may include commas then add the DSD option to the Infile as well.
Then you should provide descriptors for the variables such as an informat or length and not provide columns to read. If the value in the document says it is ALPHANUMERIC then provide a LENGTH statement with the length in the document as the length of the variable. That should be the maximum length needed but in a CSV file shorter values would not use all of the columns and so your fixed column approach would read part of the following value into the previous.
For values labeled as DECIMAL just leave them alone.
The values that say they are dates and appear a M/D/YYYY you want to use a MMDDYY10. informat and assign a SAS date format either MMDDYY10. to match the input, or YYMMDD10. or DATE9. so folks don't have to guess which is month and which is day with values like 03/05/2021. Specify the informat with the : modifier to avoid some of the issues with likely short values of 1 digit month or 1 digit day. Something like: Sale_date :mmddyy10. on the input.