Anyone got an opinion on converting the z/VM group into one for all operating systems available on mainframe, and if so, what will we call it, and what would be a good description.....anyone!
Frans BeylTo much detailed groups will generate a long groups list in the featured groups widget.
- Now there is a cobol group but what about c, assembler, pli, fortran, java, rexx, python, php, ...
- Now there is databases group but what about qsam, vsam, zfs, ...
- One might consider an Omegamon group but what about other monitors like Mainview, Sysview, ...
- We could create a CA Ops group but what about TSA, ControlR, Mainview, ...
- We could consider a CA7 group but then an other one for ControlM, T... moreTo much detailed groups will generate a long groups list in the featured groups widget.
- Now there is a cobol group but what about c, assembler, pli, fortran, java, rexx, python, php, ...
- Now there is databases group but what about qsam, vsam, zfs, ...
- One might consider an Omegamon group but what about other monitors like Mainview, Sysview, ...
- We could create a CA Ops group but what about TSA, ControlR, Mainview, ...
- We could consider a CA7 group but then an other one for ControlM, Tivoli Workload Scheduler, ...
.....
This list is far from complete and already you can see the danger to end up with a too long list. I fear the more users register the longer the list will become. Group dropdowns with subgroups hierarchie can avoid this.
