http://www.bidn.com/blogs/kylewalker/ssis/1915/how-to-match-your-subcription-names-with-its-job-id

Some things I've learned researching this topic in sql 2008 r2.

1) ssrs scheduled tasks create a corresponding sqlagent job with a nasty guid name that is meaningless

2) the bidn link above by Mr. Kyle Walker shows the query to retrieve and map the sqlagent guid name to your scheduled ssrs report.

3) putting all this information together with the msdb.dbo.sp_start_job, you can manage your scheduled reports within sql agent jobs with much flexibility.

I'm not sure I'm going to like managing this set up though during deployment of a new ssrs report? We'll see.