Download record range flag

[jace-roell]

What It Does
Added --recordRange to zowe jobs download output command

How to Test
Run command 'zowe jobs download o "" --rr "0-100"` against a valid job
Where 0 is the start of the spool and 100 is the end (zero-indexed)

Review Checklist
I certify that I have:

• tested my changes
• added/updated automated tests
• updated the changelog
• followed the contribution guidelines

[github-actions]

📅 Suggested merge-by date: 1/29/2025

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.36%. Comparing base (af0c3ba) to head (fec6759).
Report is 24 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2411   +/-   ##
=======================================
  Coverage   91.35%   91.36%           
=======================================
  Files         639      639           
  Lines       18269    18283   +14     
  Branches     3844     3850    +6     
=======================================
+ Hits        16690    16704   +14     
  Misses       1577     1577           
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gejohnston]

I suggested an extra confirmation for some of your tests.
Give some consideration to whether it would be helpful.
Either way I approve this PR.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Reminder: This pull request has a merge-by date coming up within the next 24 hours. Please review this PR as soon as possible.

@t1m0thyj @zFernand0 @pujal0909 @traeok @ATorrise

[traeok]

Tested and functionality LGTM, thanks Jace!

I'm wondering if we should support for this argument to the zowe jobs view spool-file-by-id command as well? CLI users will likely want the record range for a specific job spool rather than for all spool files. For example, let's say you want to get the record range "50-75" for the 3rd spool file in the job - when running the download command w/ record range, that range doesn't exist for the 2nd spool file, so it returns an error:

Since we use GetJobs.getSpoolContentById instead of DownloadJobs.downloadSpoolContentCommon for that command though, it may involve some refactoring, and I don't want to add scope creep. Curious to get your thoughts on this @adam-wolfe, this could be addressed separately if we want to avoid increasing scope - I will approve the PR for now as this behavior is valid when expecting a record range that doesn't exist for all spool files.

[zFernand0]

Functionality LGTM! 😋

Can we add an example of this new option?

---

Also...
Not sure if this is fixed on another PR already, but...
I'm getting these file changes (mostly license headers being updated being)

On branch download-record-range
Your branch is up to date with 'origin/download-record-range'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   packages/imperative/src/utilities/__tests__/DeferredPromise.unit.test.ts
        modified:   packages/imperative/src/utilities/src/DeferredPromise.ts

revised

[zFernand0]

LGTM! 😋

Thanks for addressing the feedback so quickly 🙏

Just waiting for CI to finish.
Then lets have a merge-party and combine a few PRs 🥳

---

Be on the lookout for unit and integration test snapshots 😋

[zFernand0]

LGTM! 😋