Hi Benoit,
To add on to what Siddhesh is saying, I would ask why you ran BTCTRNS1 and BTCTRNS2 if you planned to take the step of setting rdisp/wp_no_btc to 0 before starting the system, then changing all Released jobs to Scheduled status? This latter, by the way, is what I do for QA refreshes via system copy, since I don't usually have the luxury in this case to stop things on the production source system, nor do I often get to pick the timestamp in advance for the copied snapshot (i.e., a certain moment during payroll exit, etc).
Anyway, if you are preventing all jobs from running at startup on the destination system, the BTCTRNS1/2 steps are just extra complications and not necessary.
To provide a clue to your question, however, my suspicion would be that you setting all 'Released' jobs to 'Scheduled' didn't really impact many of the jobs affected by BTCTRNS1 in the source system. This is because BTCTRNS1 doesn't set the status to 'Scheduled', nor leave it in 'Released', but puts it in a special status of 'Suspended due to upgrade' or something like that. BTCTRNS2 then is supposed to take only jobs in this special status of 'Suspended' and release them. When you clicked on Job... Released->Scheduled in SM37 in your destination system, it probably didn't impact those jobs in 'Suspended' status as they weren't in 'Released' status. Just a guess, but this seems a likely scenario to me.
Cheers,
Matt