When you first posted some of your actual data ("here is a right copy of my original line", that limited sample showed that the comments were delineated with a traditional syntax for embedded comments: /*..comments...../. Now that you have posted more of your data, I can see that I cannot rely on the / to start your comments.
Without that, it is quite a bit more inconvenient. Start of comments must now be identified as the second word following the word "Line". This involves a little scanning of the line and some checking to ensure that I do not go into an infinite loop. The following code should do it. The only requirements for a data line are:
must contain =>
must contain Line to the right of =>
must have at least two words following Line
must have space-delimited words (not tab-delimited)
There is one rare situation that could cause this to loop, and that is if a data line violated BOTH of the last two rules. I could protect against that with gsub("\t"," ") but your awk does not want to modify $0.
I have the LINE REQUIREMENTS NOT MET just for testing. After testing, you will want to remove that, but you must leave the simple "print" just below it, which is the command that will print the unchanged line.
#!/bin/sh
awk '{
aloc=index($0,"=>")
cloc=index($0,"Line")+4
for (w=1;w<=NF;w++)
if ($w=="Line") break
if (aloc==0 || cloc==4 || cloc<aloc || (w+2)>NF)
{print "LINE REQUIREMENTS NOT MET - FOLLOWING LINE IS UNCHANGED:"
print}
else
{while (substr($0,cloc,1)==" ") cloc++
while (substr($0,cloc,1)!=" ") cloc++
pad1=substr("....................",1,35-aloc)
pad1len=length(pad1)
pad2=substr("....................",1,57-cloc-pad1len)
print substr($0,1,aloc-1) pad1 \
substr($0,aloc,cloc-aloc) pad2 \
substr($0,cloc)}
}' myfile > myNEWfile
exit 0