Skip to content

v0.5.0

Choose a tag to compare

View all tags
@squid-protocol squid-protocol released this 06 Oct 19:27
· 32 commits to main since this release
v0.5.0
9ee42d1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Format unchanged: cics-crucible/1 (SPEC.md), with additive SPEC additions only, so every v0.4.0 file still validates. 18 cases (was 16) and 86 scenarios (was 76). No log was corrected: no file under an existing case changed.

Two cases cover interval control and ASSIGN, for gitgalaxy#4270 (slices 2 and 3, gitgalaxy PRs #4578 and #4582). The expected logs were written by hand from IBM's CICS Application Programming Reference before running against any implementation. The citations are in each case's NOTES.md. All 18 cases pass tools/validate.py.

Added, by trap

Both cases are in ghost-tasks.

  • gt-start-options (7 scenarios, #7). START options beyond INTERVAL / TIME:
    • the data options RTRANSID / RTERMID / QUEUE, and RETRIEVE's ENVDEFERR;
    • RETRIEVE with no INTO;
    • AFTER / AT, and INVREQ's RESP2;
    • a REQID reused with FROM (IOERR);
    • a RUN TRANSID child task.
  • gt-assign-startcode (3 scenarios, #9). ASSIGN STARTCODE, USERID, FACILITY, SCRNHT and SCRNWD:
    • how a task was started (terminal input, or START with or without FROM);
    • the default user;
    • the terminal facts a task with no terminal does not have (INVREQ).

SPEC additions (additive)

  • START / RETRIEVE events may carry rtransid / rtermid / queue.
  • AFTER / AT are recorded as the interval / time they amount to.
  • TIME / AT rules are filled in from IBM's expiration-time rules:
    • a time not later than now is tomorrow, unless it is within the last six hours (then it expires immediately);
    • an hours component above 23 means a following day.
  • New RUN event, and a {"kind": "run"} task trigger for a RUN TRANSID child.
  • The reference region's default user is CICSUSER.

Also on main since v0.4.0

  • RELEASING.md lists v0.4.0 (#8).

gitgalaxy moves its pin to v0.5.0 in a separate PR, which re-baselines the runner (30 added cells, no existing cell changed) and re-proves the committed ports.

Assets 2
Loading