Hi,
Some developpers in our companie have really problems to use NaturalONE because they don't like the implementation of filters for the Natural server view. For us, and I agree with them, it's more convenient, more quick, to edit a program with SPoD or with CICS editor. (they don't need to add a filter object, and then for this filter object, add a filter pattern, and finaly, apply this filter object ...).
We would like to use filters as it has been implemented in SPoD and in Mainframe Navigation included in the NaturalONE plugin.
With a right click on the Natural Server, we would like to have :
-
an "object type" presentation or have a "Flat view" presentation (idea 1059863)
-
additionnal option to filter (eg date saved) (idea 1046586)
-
possibility to use directly a filter pattern on the selected object (into the 1st "Set Filters" window, be able to enter directly the filter pattern)
The actual implementation of filters in NaturalONE in the Natural Server view is realy a reason, for many natural developpers, to reject this tool .
Thank you for your attention.
Best regards
Bernard
Just two remarks:
Normally, filters are used to pick out a few objects from a huge list. Sometimes filters are used to speed up the response time. In the later case, I would recommend to implement the new hyperdescriptor and ONE 914/NatMF912CF4+HF. This improves the performance essentially (e.g. list 10.000 programs from 36 sec down to 4 sec) so that filters are no longer needed for performance reasons.
The very fast read with the hyperdescriptor does no longer provide all properties of an object. It mainly reads the name, type (like "subprogram") and kind (like "cataloged") of the objects. As long as filters are restricted to this information, a fast descriptor read (HISTOGRAM) can be performed. If other filters (like "save date") are used, the data record must be read (with READ). Using such filters would therefore slow down the performance (not in general but in those cases where such a filter is used).