Good morning Wendi.
I've had these same issues the last 2 releases (R6 and 7) where I get one or two reports in jobs whose id's have changed and need to be remapped. It was actually harder to fix in 11.1.6.
To edit the job and correct the issue with the report, you must first enable the Cognos Connection portal by using the advanced parameter portal.disablecc and set the value to "false" -- that's case sensitive I'm told, so be sure its all lower case. This article gives the details:
https://www.ibm.com/support/pages/how-display-version-10-cognos-connection-home-page-cognos-analytics-11Then log into Cognos via one of your dispatchers using a URL of this format:
http://dispather-server-name:port/bi/v1/disp. After you've logged in you'll see the old Cognos Connection portal.
Navigate to your job, edit it, and fix the step(s) that are coming up with errors. Save it, and you'll be able to edit the job going forward using the normal 'glass' cognos 11 interface... until such time as another report in a step "goes rogue".
I once saw a posting (can't remember where) indicating that IBM was aware of the issue and was working on a fix so the job can be fixed without having to use cognos connection... perhaps one of the IBMers who participate in this forum can comment on the status of that fix or provide the APAR for us to monitor.
Until then, I've used this work around multiple times, and it works well.
I hope that helps!
Rich
------------------------------
Richard Chester
Director of Business Intelligence
LPA Software Solutions
------------------------------