@Saranya_Sub: this thread is almost two years old. It would be better if you start your own with your particular requirements and conditions. My take is (in priority order): 1) Check if can make use any of the ootb functionality in Environment Manager 2) Use the collect runtime statistics option I DI Studio 3) Create tour own macros that either make use of the standard set of macro variables in DI Studio, or if you don't have that, get the log info from other information available to you in the job session. ... View more

Ton, The life cycle of jobs in LSF is having a different concept as running SAS scripts. Sometimes using different words same meaning sometimes same words different meaning. The pend is no real event status. Your job remains pending until all conditions for its execution are met. Each queue has execution conditions that apply to all jobs in the queue, and you can specify additional conditions when you submit the job" page 24 users guide. A message for the users is most easy by giving a email - pag 20 users guide.   The reasons for missing triggers (pend) is a specialized task for some support guy   ... View more

Its really dependant on your setup.  If you have SAS locally installed then sysuserid will return the username it gets, probably Windows user login (I can't test this).  If you have it on a virtual system then it may be the login information for the virtual system.  We have ours on Citrix and that return the user information which is setup in the initiation files. Depending on your setup and what you want to do, you would need to talk to your IT Helpdesk.  Principally, you need to be careful what you are doing with the information, but also your IT will be the ones who deal with login information. If its just a matter of you want in your program and audit of who ran a program, then just setup a small dataset somewhere with user list and take it from there based on the sysuserid. ... View more