Retrieve job output from jobs that route to other LPARs for execution

[MikeBauerCA]

I would like to retrieve job output via the CLI from jobs that route to other LPARs for execution.

Notes from original thread:

• The output from the job should come back to the submitting LPAR but may be assigned a different jobid. Zowe jobs commands are currently based on the jobid.
• When you receive a Job ID back from Zowe CLI, that job ID does not work when you try to follow up for output/status if it has been routed to another LPAR.
• z/OSMF jobs REST APIs return a "job correlator". Currently, the submit and "view all spool content" commands do use the JOBID to "follow up" for spool output. We should probably experiment with the correlator to address the changing JOBID. Some commands already provide the job correlator in the response if you ask for that field, but no commands as of today allow it as input (to view spool, etc.)

[dkelosky]

Notes from working with @ChrisBoehmCA

If you submit this from some system and XEQ to another via JCL:

//RUNMAIN  JOB ACCT#                               
/*ROUTE XEQ xxxxxxxx                                                  
//EXEC     EXEC PGM=IEFBR14

It seems like you get a command response like:

$ zowe jobs submit ds "user.work.jcl(iefbr14)" --vasc
Command Error:
Error obtaining status for jobname "RUNMAIN" jobid "JOB00790".
z/OSMF REST API Error:
Rest API failure with HTTP(S) status 400
rc:       4
reason:   10
category: 6
message:  No job found for reference: 'RUNMAIN(JOB00790)'

Error Details:
HTTP(S) error status "400" received.
Review request details (resource, base path, credentials, payload) and ensure correctness.

Host:      xxxx
Port:      443
Base Path:
Resource:  /zosmf/restjobs/jobs/RUNMAIN/JOB00790
Request:   GET
Headers:   [{"X-CSRF-ZOSMF-HEADER":true}]
Payload:   undefined

[ChrisBoehmCA]

Usage of the job correlator rather than job name and job ID does not seem to resolve this issue : (

Command Error:
Error obtaining status for jobname "xxxI" jobid "JOB01681".
z/OSMF REST API Error:
Rest API failure with HTTP(S) status 400
rc:       4
reason:   10
category: 6
message:  No job found for reference: 'J0001681xxx.......:'

Error Details:
HTTP(S) error status "400" received.
Review request details (resource, base path, credentials, payload) and ensure correctness.

Host:      xxxx
Port:      443
Base Path:
Resource:  /zosmf/restjobs/jobs/J0001681xxx.......:
Request:   GET
Headers:   [{"X-CSRF-ZOSMF-HEADER":true}]
Payload:   undefined

[JTonda]

Research needed.

[github-actions[bot]]

Thank you for raising this enhancement request. The community has 90 days to vote on it. If the enhancement receives at least 5 upvotes, it is added to our development backlog. If it receives fewer votes, the issue is closed.