Hi,
Check whether Dispatcher and Workprocess started 
successfully.If not then restart the application server and 
goto the following path c:/sap/sid/ and type dpmon and 
check for the performance or goto c:/sap/sid/sys/exe/run 
and type NIPING and selftest the application server and if 
returns the selftest status as OK then the application 
Server is running successfully and now remains login into 
application server through local Lan or WAN so check for 
the RFC connection (BD54 or SALE) between different systems 
to communicate properly and then goto SM30 T code and 
maintain table Users_SSM and make changes to User passwords 
and check login into client with user account or Admin 
account.

yes it is mandatory to log off user while applying support 
pack.

Yes It is mandatory to log off all use while app;ying Add-Ons.

it is a mandatory pre-requsite to be followed that 
NO USER ACTIVITY takes place when applying SUPPORT PACKS
SPAM/SAINT UPDATE.

no we cant adjust tablespace using tcode DB02, brtools can 
adjust it.

we can not transport any requests from production to
development, transporting of request can only be done from
develpment to quality, as we cant create any transport
request in production environment we there fore cannot
transport any request from production to development.

Yes, you can transport the request from production to
development server.

DDIC is the Copy of SAPUser and is know as copy of 
Superadmin and it has a unique password 19920706.One can 
see whatever is seen in SAPUSER.

DDIC is the owner of Data Dictionary Elements.
This is SAP predefined user which consists of all 
authorizations.
SAP recommends to do some main activities like Post 
installation activities, Applying Support Packages etc....
with the user DDIC only.

yes, once application server(central instance) can have any
number of instances depending on business requirement, for
ex, dialog instance, background instance etc,. one
dispatcher per instance is sufficient. To find out which is
central instance and which is dialog instance, check the
enqueue work process, instances that has enqueue is the
central instance and the remaining are dialog instances.

the statement is 100% correct. we cant have more then one
dispatcher per application server.

RSBTCDEL-
It deletes finished or cancelled jobs

RSBTCDEL is the program which deletes Background job logs.

RSBTCDEL

RSBTCDEL is the program or report is used to delete 
cancelled jobs

RSBTCDEL IS THE REPORT WHICH DELETES THE OLD BACKGROUND JOBS

It wont goto PRIV mode. since only DIA is supposed to 
multiplex between user requests.
while other work processes are meant to be blocked until 
they finish the activity

Logon load distribution allows you to dynamically 
distribute the SAP users to application server instances. 
You can increase the efficiency of individual workgroups by 
setting up multiple logon groups that consists of one or 
more application instances.

RFC groups, you can control which servers can be used for 
parallel-processed jobs. An RFC group specifies the set of 
allowed servers for a particular parallel-processed job.

thank you

T-code for RFC groups is RZ12 not SM59

SMLG transaction code is for Logon Groups.
It is used to identify the leastly loaded application 
server.

Sm59 is for RFC connections with in a system.

-->(SMLG)Logon groups are used to identify the leastly 
loaded application servers.
-->(SM59)Rfc conection is used for the connectivity between 
the systems.