|
|
It would be nice to have an API method of retrieving the information provided by the DUMP ZAPS command. When working with the application and testing of zaps applied to the various core and sub-product components of Natural, having a programmatic method of determining the zaps applied for the current runtime environment would be very helpful.
Presently, the only way to extract this information is by issuing the DUMP ZAPS command and either manually reviewing the output or capturing the output and writing local utility logic to parse the results. This not only adds complexity but also suffers from maintenance
Adding an API (i.e. SYSEXT routine) to retrieve the applied zaps seem like a fairly simple and straight forward solution.
| Use Case | Pulling applied zaps information from an RPC call |
Eli,
When a customer is applying zaps to the environment, DUMP ZAPs is used to verify the zap is applied in the environment in which you're accessing Natural. This only works for an "interactive" environment (i.e. TSO/CICS/etc.), so this requested API would allow for a method of verifying zaps applied in the RPC runtime environment that is only accessible via RPC/subprogram calls.
If this requested API were available, we would code a simple RPC function to pull the zap related information which would allow us to verify the applied zaps in the called RPC environment. In addition to the RPC scenario, having an API to retrieve applied zaps would also enable automated test/verification procedures in general across all environments.
I hope that helps provide more context.
David
Hello David, thank you for posting this Idea.
We can think of making the ZAPS DUMP as an API (Input "product code/*", output a list of applied ZAPS)
Regarding the use case: what would you like to perform with the retrieved information from the API?