Generally gathering requirements is a multi-step procedure.
First ensure that you understand the scope of the requirement. In your case aree you sure that you aren't going to need other mainframe tables to calrify any codes etc on the table you are intersted in. Additionally, is all the information on this table or are you going to need to parametise or have other input tables to meet the user needs?
Once the scope is defined and agreed upon, get the key users to submit their requirements to you in writing. Compile all these requirements and come up with a draft set of reuirements for distribution. Only once this draft set has been distributed get the users together and hold a workshop to discuss this document. Use the workshop to eliminate unnecessary requirements and to clarify any that are not clear. you may also find extra requirements being discussed at this point due to cross pollination between users during discussion.
Prepare a final requirements document and circulate for comment in preparation for signoff. Once the users are happy get them to signoff this document after necessary changes have been made. this is important as based on these requirements you will probably have to commit to time frames and resources. By having had the requirements signed off, any changes that come afterwards must affect the timing and resources as they were not planned for. Also, it prevents later issues of people saying something was specified and not done.
Cheers
Marc