Managing multiple DPTRs as well as many other system resources, such as stack, register banks, code banks and data pages, etc., with strict policies and rules are monumentally important to any coding practice. However, I wasn't exactly looking for a philosophical solution other than --- some tricks maybe? For example, in my group, we define MPL macros like this one in one of the include files,

%DEFINE( SelRB0 )
(
	clr PSW.3
	clr PSW.4
)

to select the proper register bank. It doesn't save any code space or make the code run faster, but it does make the assembly code more readible and therefore less error prone. I was thinking that if I redefined "INC DPSEL" as macro "NextDPTR" and "DEC DPSEL" as macro "PriorDPTR", I would improve the readibility of the code, then I asked myself - how did other people handle multiple DPTRs? What were their common techniques and rituals? After all, I can be one hundred percent certain that I am not the only one who has eight DPTRs at his disposal. :)