I am not yet a COBOL person, but I would not rule it out.
Away from more metropolitan areas I occasionally but repeatedly bump into job reqs seeking COBOL in the mix with more modern languages & API's.
This seems like a long tail residual effect of the pervasiveness of the IBM mid-range systems (System/36/38, AS/400, eServer iSeries, System i, and then IBM Power Systems with a choice of either AIX, or the latest variant of OS/400 or i5/OS or whatever they are calling it today.)
I have seen System/36 & AS/400 systems deployed in facilities where there is no SysAdmin and no IT staff, and possibly not even a programmer. The machines just keep running til a mouse finds a way to burrow inside and make a nest near the warmth of the power supply. In those environments there might be only a single application but a critical one for the users at that firm, like their ERP system.
I've worked with ERP systems on other platforms, including Unix & Wintel, and the labor headcount to keep those systems running is often costly, especially with the never-ending stream of patches & forced upgrades to be applied. Then of course is the chronic cat & mouse game of security & anti-virus efforts. There is something to be said for platforms which do only one thing but do it adequately in a reliable bullet-proof non-labor-intensive manner.
Anyone who thinks COBOL has only 5-10 years left is simply missing the point. Anyone graduating from college today could build proficiency in COBOL and have that carry them their entire career, assuming that they remain an outlier amongst their cohorts.