Repository navigation
CICS: EXTRACT WEB and EXTRACT TCPIP from the stated request (Part of #4767, sibling of #4940) #4972
Description
Sibling gap from #4940 (PR #4971), class: CICS web support, the server reading its request (register X38).
| Member | State |
|---|---|
| WEB EXTRACT (server form) | modelled (#4938) |
| WEB READ HTTPHEADER / FORMFIELD / QUERYPARM + browse forms | modelled (#4938, #4940) |
| WEB RETRIEVE | queued #4941 |
| WEB RECEIVE SET | pointer lane, #4771 |
| EXTRACT WEB (the older form of WEB EXTRACT) | name-only in standards/cics/commands/api.py |
| EXTRACT TCPIP (client/server address, port, SSL type) | name-only in standards/cics/commands/api.py |
Task: model EXTRACT WEB and EXTRACT TCPIP from the stated http_request as X38 does (IBM docs as the reference, ASSUMED / REFUSED by name where IBM is silent), on both runtimes (CicsTask + stub C) and both translators, with step-table tests over the whole option class. No burned estate is known to use them; check det_survey first and note it.
Activity
squid-protocol commentedon Oct 12, 2026
Class sweep update from #4941 (PR #4989):
standards/cics/commands/web.py(WEB SEND). Different mechanism from EXTRACT WEB / EXTRACT TCPIP: a design question under det/CICS: EXEC CICS WEB family (SEND, RECEIVE, EXTRACT, READ/WRITE HTTPHEADER, PARSE URL, OPEN, CONVERSE, CLOSE) -- zECS needs HTTP (design first) #4767.Siblings: #4941.
WIP: EXTRACT TCPIP tests, register X38 entry, formatting (Part of #4972)
det/CICS: EXTRACT WEB and EXTRACT TCPIP from the stated request (Closes