Thanks to all of you. In our route i.e, between Visakhapatnam and Secunderabad Vijayawada is popular junction and usually due to the multi berthing reason, we normally get the confirmation. Example: WL 20 can not get but WL 220 can get the confirmation. 80 percent of the journeys of me are like this. Recently my niece travelled from Mangalore to Visakhapatnam. I booked her 3 tkts splitting MANGALORE to tirupathi and tirupathi to Vijayawada and from Vijayawada to Visakhapatnam. She is alone and could not get tatkaal as in Mangalore maual ticket providing agents are very less.
Luckily my idea won. She got confirmation for two tkts ie., from Mgl to Tpty and Vja to Vskp. For Tpty to Vja a...
more...

family offered her a seat instead of their daughter who has not travelled.
So in the critical situation, this idea will work.Hope all of you will appreciate. I know that surprise will come, as all of you have voted for WL when i posted the pnr. I only told it will get confirmation.

You are pretty much correct Sir.The right terminology for this is #berthmultiplexing.
Kindly go to the availability page for VSKP-BZA/BZA-HYB/VSKP-HYB
Note the similarity. All of them are under a same quota with a slight difference in status here and there. Now that is due to #berthmultiplexing
For example, if I assume 100 berths allocated under General Quota, I would never know if...
more...

a booking has been made under VSKP-BZA leg or BZA-HYB leg or VSKP-HYB leg.
Assuming only 1 berth is left out, I would still have no clue where the previous 99 berths have gone. Now it may all happen that all of them have been booked from start-end, while all of them may also have been booked for VSKP-BZA Leg or somewhere enroute or it may also happen that it may have been booked for BZA-HYB leg or enroute.
In both the above cases (Apart from start-end), if the tickets are booked for VSKP-BZA leg or enroute, it shall clear the way for the subsequent passengers. Same is with BZA-HYB Leg. It shall clear way for passengers boarding and deboarding prior to BZA.
This train being mostly popular to passengers traveling to the intermediate station/s, confirmation chances are higher for the same. However, it is purely a risk game.
Kindly note, this has got nothing to do with #shortdistancereservation. It is simply how berth/s are manipulated and forwarded. A classic example of #berthmultiplexing

Recently we travelled at Kumbhmela time from Bhubaneswar to Mughalsarai by BBS Rajadhani. I observed plenty of tkts available from BBS to Gaya but between Gaya to Kanpur or from BBS to Kanpur no berths available. So we took the risk to get the extension in train taken tckts and started travelling. TTE advised us this is the regular problem for the Varanasi piligrims and do not bother and travel between Gaya to Mughalsarai.
Return also the same problem but TTE allowed.
Otherwise, the road journey between Gaya and Varanasi shall take...
more...

approx. 8 hours but by Rajadhani it took only 2 hours.
RK