Logical System Conversion after system refresh failed

[Former Member]

Hello,

Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.

02/18/2009 16:09:33 Job started 00 516 S

02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD) 00 550 S

02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system PO 349 I

02/18/2009 16:10:19 Job finished 00 517 S

When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".

Any suggestions on this?

Thanks,

Mahesh

[former_member1351727 · Accepted solution]

Hi ,

Rerun the BDLS again as this took very little time.

When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.

May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.

Thanks.

[Former Member]

Thanks Vani, for your response. I had to do few more steps like unlocking a printer and etc but rerun the converstion, it worked. I rewarded the points to you.