Hello Nithin, thanks! I have a few comments:
1) Jon ended up performing much of this work previously for ticket PP-483, see https://pbspro.atlassian.net/wiki/pages/viewpage.action?pageId=31621169. That should be either be used as the starting point or allowed to stan on its own, depending on what we decide in comment 2) below. I am sorry if I didn't mention the existence of this EDD previously.
2) I believe that filing PP-508 as a user story was unnecessary. I had previously filed these tickets surrounding the planned qstat changes:
As a user or admin, I would like qstat to return a full job attribute list with 1 line per job attribute, so that I can more easily use tools like grep to find the information I am looking for regarding my jobs
As an admin or user, I would like qstat to be able to output full job attribute information in JSON format, so that I can more easily write scripts consuming this information
As an admin or user, I would like qstat to be able to output full job attribute information in delimeter separated value format, so that I can more easily write scripts consuming this information
We can either change PP-508 to be an epic that encompasses those three tickets, or close it altogether. Before I take any action like that, was one of those options your original intention? And if so, was your plan to add the JSON and DSV interface options to this same EDD page?
3) About Interface 1 handling Resource_List.select: I think that breaking up the select statement like this distorts and misrepresents the resource value and we should just print it in normal select statement format like we do in the present behavior, we should just not break it up into multiple lines if it is longer than 78 characters if this new option is specified.
4) Same comment as 3) except pertaining to schedselect attribute.
5) Similarly, I believe that we should leave Variable_List as all one line as it is today, but simply not wrap it if it exceeds 78 characters.
6) The actual syntax used needs to be "qstat -f1" , rather than "qstat -f 1" (no space vs. space). The former can mean "full output with one line per attribute", but the later already means "full output with line breaks for job 1.servername".