ZDV CTLR ALERTS ZLC CTLR OF UNCOORD COM HDOF XFER OF ENRTE GV.

Narrative

I WAS WORKING RADAR POS 15. MY ADJACENT SECTOR 6; CALLED TO INFORM ME OF TFC REQUESTING IFR. SECTOR 6 '/OKED' (LOGIC OVERRIDE FUNCTION). THE DEP MESSAGE AND INITIATED A DATA BLOCK ONLY HDOF. I ACCEPTED THE HDOF AND SUBSEQUENTLY ISSUED IFR CLRNC. THE 'DM' MESSAGE THAT SECTOR 6 INITIATED CAUSED AN 'UNSUCCESSFUL MESSAGE' TO DISPLAY ON MY VDM (VIDEO DISPLAY MONITOR) WHICH I DID NOT CATCH. THE ACFT TRAVERSED MY SECTOR NORMALLY; BUT WHEN A HDOF WAS INITIATED TO ZDV (DENVER); IT FAILED. I WAS VERY BUSY WITH OTHER DUTIES IN THE SECTOR AND DIDN'T NOTICE THE FAILED 'FLASH.' I REINITIATED THE HDOF; ONLY TO HAVE IT FAIL AGAIN. (THE SECOND TIME ALWAYS WORKS!) I NOTICED THE DATA BLOCK NOT FLASHING ANYMORE; SO I THOUGHT; AND ISSUED A FREQ CHANGE TO THE ACFT. A MINS OR SO LATER; I RECEIVED A CALL FROM ZDV; 'WHO IS THIS GUY?' NO FLT PLAN INFO HAD PASSED TO ZDV. FORTUNATELY; I WAS ABLE TO INITIATE A MANUAL HDOF AND PASS FLT PLAN INFO PRIOR TO THE ACFT EXITING MY AIRSPACE. NO FOUL! HOWEVER; I WAS REMOVED FROM DUTY BECAUSE OF A 'PERFORMANCE ISSUE.' FAILURE TO RECOGNIZE AN UNSUCCESSFUL FLT PLAN!? THE FAILURE WAS A RESULT OF ZDV COMPUTER NOT RECOGNIZING THE OBSCURE DEP ARPT IN ZLC AIRSPACE. THIS LACK OF COMPUTER INPUT/DATABASE COULD HAVE CAUSED A SERIOUS PROB. BUT FORTUNATELY; I WAS ABLE TO QUICKLY COVER STEPS AND AVOID THAT SIT. WITH DSR ON-LINE AND THE FACT THAT THE DENVER COMPUTERS HAVE AMPLE STORAGE CAPACITY; THERE SHOULD BE NO EXCUSES FOR ANY ARPT NOT BEING STORED IN ANY DATABASE! 3-LETTER IDENTIFIERS DO NOT CONSUME ANY; OR VERY LITTLE; COMPUTER MEMORY. THIS SHOULD HAVE NEVER HAPPENED!