Reactivating the Old Service Data Control Center

When you activate the new Service Data Control Center (transaction SDCCN), the old Service Data Control Center (transaction SDCC) will be automatically locked and the AUTO_SESSION_MANAGER job will be automatically descheduled. It will then no longer be possible to work with the old Service Data Control Center (transaction SDCC).

We do not recommend that you go back to working with the old Service Data Control Center after you have activated the new Service Data Control Center.

However, if you have activated the new Service Data Control Center, but then need to continue working with the old Service Data Control Center, perform the steps below to reactivate the old Service Data Control Center.

 

Procedure

...

       1.      Call transaction SE38.

       2.      Execute the following report:

In releases 4.0B to 46D, report /BDL/SETUP.

In release 6.x, report BDLSETUP.

       3.      Use the following parameters for the report:

KEY  = 'LOCKED'

VALUE  = space

delete = unchecked

       4.      Call transaction SDCC.

You are prompted to schedule the AUTO_SESSION_MANAGER job.

                            a.      Do not schedule the AUTO_SESSION_MANAGER job if you only need to check the old Service Data Control Center (transaction SDCC).

If jobs for both transaction SDCC and SDCCN are running in parallel, session data will be collected twice, which will cause unnecessary system load. The two transactions work independently of each other.

                            b.      If you need to continue working with the old Service Data Control Center (transaction SDCC), deschedule the new /BDL/TASK_PROCESSOR job first.

Do this in transaction SDCCN. Choose Goto ® Settings ® Task Processor. When you call transaction SDCC, schedule the old AUTO_SESSION_MANAGER job.