ACR X TCASII RA WITH VFR SMT Y NMAC EVASIVE ACTION TAKEN. SEE AND AVOID CONCEPT.

Narrative

THE PROB AROSE BECAUSE PAM RAPCON NEGLECTED TO APPLY MERGING TARGET PROCS AS REQUIRED IN FAA HANDBOOK 7110.65G; PARAGRAPH 5-8(A)(2); AND NEGLECTED TO ENSURE THE CONFLICT BTWN ACR X AND SMT Y WAS RESOLVED PRIOR TO COM TRANSFER. ACR X RPTED ON PFN TWR FREQ IN THE VICINITY OF THE OM ON RWY 14 ILS APCH. I OBSERVED TFC AT ACR X 1 O'CLOCK POS; 2 MI; CONVERGING AT 2000 FT. ACR X ALT WAS 2500 FT; DSNDING. I ISSUED TFC WHICH I BELIEVED TO BE A FLT CHK OPERATING IN VFR CONDITIONS E TO W ACROSS THE FINAL AT 2000 FT. ACR X RPTED TFC IN SIGHT XING HIS APCH PATH AND ALSO RPTED A TCASII ALERT. ACR X INITIALLY APPEARED TO BE SURPRISED WHEN TFC WAS ISSUED. HE WAS NOT AWARE OF THE TFC UNTIL I ISSUED THE TFC INFO. ANOTHER DISCRETE CODE WAS OBSERVED BEHIND ACR X AT 2300 FT. WHEN WE INQUIRED ABOUT THAT TARGET; WE WERE ADVISED THAT THE TARGET WAS FLT CHK. WE THEN ASKED ABOUT THE XXXX DISCRETE CODE AND TARGET THAT PASSED IN FRONT OF ACR X. WE WERE TOLD THAT THE XXXX CODE WAS SMT Y. SMT Y WAS NEVER POINTED OUT TO THE TWR NOR TO ACR X BY PAM RAPCON. CORRECTIVE ACTIONS: PAM RAPCON SHOULD BE REQUIRED TO CARRY DATA BLOCKS WITH THE ACFT CALL SIGN AT ALL TIMES. SOME CTLRS USE PARTIAL DATA BLOCKS WHICH ONLY SHOW THE DISCRETE CODES AND ALTS. BECAUSE OF THIS PRACTICE; WHEN I SAW THE XXXX CODE I BELIEVED IT TO BE THE FLT CHK ACFT WHICH HAD BEEN PREVIOUSLY COORDINATED WITH TWR.