What have you tried? People are mush more willing to assist when some initiative is shown on the part of the person inquiring.
Keep in mind, you are entering a field governed by the practical application of the scientific method.
<ul type="square">[*]What is your Hypothesis on how this might work in WinRunner?[*] What test steps have you walked in an attempt to prove or disprove your hypothesis?[*] How have your actual observed results differed or confirmed your expected results? Have you modified your Hypothesis as a result?[*] What resources have you already consulted in an attempt to resolve this issue? It probably doesn't make sense to head down a blind alley if you have already been there and done that[/list]
One might argue that a QA practicioner requires a certain degree of self-reliance and stubbornness to get to the root of an issue and the rigor to withstand repeated assaults from developers who do not believe the results. If you demonstrate some of these attributes and also that you have done your homework, then you will likely receive more in depth replies.
My reply isn't ever going to be as eloquent as James', but I will add this to the conversation:
Vijay - this is a simple task that can be learned by taking the required time and effort to go through the tutorials that are supplied with WinRunner when your company received it (you did get this copy from your company, correct?).
The volunteers on this site allocate their time to help those that try for themselves more than those that don't. Please take a step back and perform the tasks laid out in the WinRunner tutorial as they will step you through the portions of the tool you need to get started. No one will be an expert at the end of the tutorial, but it will start you down the right path.