While the question might not be formed as clearly as it could, I believe I may understand the sentiment and have the answer.
Much has been written to indicate a lot of new batch processing is being coded in Java. If this is true, in time, it is possible Java will take over the lion share of batch processing from COBOL. All the major big iron boxes that run COBOL will also run Java: IBM zSeries, HP NonStop, Unisys 2200, and Unisys MCP.
I am starting a new COBOL gig with the state of Washington on November 1. While I have not met my new coworkers, I suspect I will be the youngest COBOLogist in the office.
At age 44, I am probably in the bottom 10%, or less, of COBOL programmers sorted by age in ascending order across the industry. I would hazard a guess that 80% or more are at least 10 years my senior.
Something is going to happen, and there are at least a couple of possibilities.
Companies with an investment in COBOL will undertake the training of young Computer Science graduates in the wonders of COBOL. I have worked one place where this happened, but the market today is such that I doubt they would still need to do this.
A variant of #1 might be the sudden appearance of Quickie-Mart COBOL training schools will pop up to train the workforce.
More and more COBOLogists will remain in the workforce, either delaying retirement or returning to work after retirement.
Those of us COBOLogists left still working, as more and more of our more senior brothers and sisters retire, will perform conversion work. Java makes the most sense given that the box where COBOL lives also allows Java to move into the neighborhood.
If there is forethought and planning, the conversion and transition from COBOL to Java will be relatively smooth and painless. If not, then a lot of excitement could ensue that makes the whole Y2K era seem quiet and tame.