The kinds of abends will totally depend upon the site and how good its programmers are. A site with poor programmers will see many S0C7 abends -- one with good programmers will never see a S0C7 abend. There may be some S0C1 and S0C4 abends along with SB37, SD37, SE37 abends. If you want to know more, read the MVS System Codes manual for a list of all the possible abend codes. Beside the possible abends, sites doing a lot of FTP jobs can have non-zero return codes such as 0166 due to problems with the FTP process -- these are not abends but they indicate the job did not completely do what it should have done.
And, more to the point, WHY do you want to know this? The usual procedure is for the programmer to submit a job stream to the site CA-7 person, who sets it up in CA-7 and includes prose to indicate what to do in the event the job does not run "normally' (whatever "normally" means in that context -- some jobs have to have a zero return code, some can have a non-zero return code but still have done what they were supposed to). The operations staff monitors the CA-7 queue and calls the appropriate on-call person based on the prose whenever a job does not complete normally. There's not any reason for the operational staff to be concerned about what possible abends could occur.
What do you mean by "console monitoring" -- are you talking about monitoring of the CA-7 job statuses or actually monitoring the messages that appear on the system console -- a totally different procedure?