SMLG - delayed availability

[Former Member]

Hi

I noticed that when an ABAP instance starts, the logon group is not available for a period of time. Even though I can connect to CI or DI, but I cannot connect via logon group. What are the parameters that controls it availability?

Edited by: Nader Soliman on Mar 14, 2011 1:42 PM

[Former Member]

Sometimes I am able to connect to the instance via logon group immediately after the bounce. Other day, it takes longer to access the instance (almost the full 300 sec delay for the parameter).

[mercedes_fernandez]

hello,

you could check when the RSRZLLG run via:

- SMLG -> Goto -> System diagnoses -> Cyclic system prog.

Example: Status table

Program name Status Dur. Start time Status text

SAPMSSY6_RSRZLST0 0 0 19941222 184840

and see if it corresponds when you were able to login.

kind regards,

Mercedes

[Former Member]

This is great info; thanks a lot.

Is there a way that I can see the historical values?

[mercedes_fernandez]

Hi,

No, you see the last time the program was executed.

kind regards,

Mercedes

[Former Member]

Thank you so much for the reply.

How can I explain the fact that there are days where the logon group faster, while rdisp/autoabaptime is not changed?

[mercedes_fernandez]

hello,

what do yo meand? could you please provide more details?

thanks & regards,

Mercedes

[mercedes_fernandez]

Hello,

it will take the time defined by parameter rdisp/autoabaptime: "This parameter controls the interval at which SAPMSSY6

is executed.". An then it will trigger program RSRZLLG0 that is the logon distribution program.

kind regards,

Mercedes