Sometimes MF buffers’ structures change by the program scenario. With OpenLegacy, with OpenLegacy you can define the desired structure with a status code and handle the different structures.
...
| Info |
|---|
There are no success or error status code codes - the customer can choose what is select the expected status code. |
...
You can indicate the specific success structure by the following aplicationapplication.yml configurations.
ol.cics.project.[orhectratedorchestrated-key].status-code
Key | Type | Default Value | Description |
|---|---|---|---|
default-success-value | Int | 15 | The default value indicates success. Default value represents |
indicators[] | List<StatusCodeIndicator> | Empty list | List of status code indicators |
indicators[].offset | Int | 0 | Offset in the buffer to start read the status code |
indicators[].length | Int | 1 | Number of bytes to read from the offset |
...
How to handle a different structure?
Currently, we have 2 two cases:
The returned status code matched the
default-success-value- no exception is thrown.The return status code doesn't match the
default-success-value- anOperationNotMappedExceptionwill be thrown.
...