dc
6bb0316f2d
`public/getddl` for a dataset that is not there and `public/getcolvals` for a table that is not there - the two aborts the mock used to answer with a body. Both carry one accepted difference, `SYSCC`, for the reason the existing abort scenarios already record: the estate's wrapper adds it to an aborted response, and a JS program's envelope is finalised at CLOSE. The README gains the refresh runbook the status section kept promising: deploy first, how to find the estate's control library, what each gate line means, and how to read the two refusals. It also names what cannot be recorded yet and why. The "not authorised" abort needs a non-admin login, because %mpe_accesscheck lets the admin group through and the synthetic estate's user is in it. The getddl body needs index metadata the mock's table files do not carry. And getcols' libref tolerance is a behaviour change that needs a survey of its callers first.
25 lines
447 B
JSON
25 lines
447 B
JSON
{
|
|
"_meta": {
|
|
"scenario": "missing_table",
|
|
"service": "public/getcolvals",
|
|
"estate": "synthetic",
|
|
"targetType": "SASJS",
|
|
"sas": "9.4M9",
|
|
"dc": "7.22.0",
|
|
"captured": "2026-11-07",
|
|
"tls": "verified",
|
|
"members": [
|
|
"sasjsAbort"
|
|
]
|
|
},
|
|
"body": {
|
|
"sasjsAbort": [
|
|
{
|
|
"MSG": "Target table not found: <LIBREF>.NO_SUCH_TABLE",
|
|
"MAC": "MP_ABORT"
|
|
}
|
|
],
|
|
"SYSCC": "0"
|
|
}
|
|
}
|