Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New API - submit JCL and wait till completion #28

Open
Joe-Winchester opened this issue Jan 9, 2019 · 2 comments
Open

New API - submit JCL and wait till completion #28

Joe-Winchester opened this issue Jan 9, 2019 · 2 comments
Labels
backlog enhancement New feature or request

Comments

@Joe-Winchester
Copy link
Member

Requirement is to have the ability to submit a job and wait till its completion.
Issues to consider:
How long is the wait for - can a timeout value be passed in and what would the default be ?
What if the job goes onto the input queue ?
What is the response to the API ? Is a particular job file content to be returned and is this an input parm to specifiy which one, or should the list of all of the files be returned ?

@stevenhorsman stevenhorsman added the enhancement New feature or request label Jan 21, 2019
@JeffreyDouglas
Copy link

  1. default to 1 minute, with the ability for the user to define some setting to alter that
  2. if the timeout is exceeded, return from the API with a specific status code and a URL (like you suggested)
  3. we should have a setting in the API to tell it whether to concatenate all output spool files as one large file, or if the setting is activated, then return each spool subfile individually

@Destabilizator
Copy link

  1. By default bring back only RC, if it's not the desired one (setting?), user should ask for files... no need to waste bandwidth on RC=0, right?

What happens when I submit 1000 jobs (eg. regression suite) like this then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants