New Assembler Macro feature implemented in RDz V8.0.3 does not work well in large shops

Description:
The new real-time syntax check feature for assembler macros implemented in RDz 8.0.3 is unworkable in large shops. On just one plex (we have 9) we have 7 different applications that use different PDS libraries. Each application has from three to six levels of libraries going from test to production. We have set up workspaces for each plex and have property groups defined in the workspace to identify each application and test level. We have 700+ people who work on these systems. Here are the issues with the way this assembler process is structured:

1. If we don't want to use this feature then there should be a way to use a more basic version. There is a place to define the macro files in the Property group. If the user file is not set up then the process should look at that library list to see if the macro exists in any of those files and only flag it as an error if it is not found. This is what is done for COBOL copybooks and it should work the same here.

2. The user XML macro file is defined at the Workspace Level, not at the property group level. Our macros are not named the same between the applications. Using this process we would need to define a workspace for each application and each test level. If you are going to use this process then the file definition should be at the property group level, not the workspace level.

3. There is no supplied process to read the macro library to build the XML file. This means that the entire process is manual. There should be a supplied routine that will read the mainframe macro PDS and build the initial XML file. It could then be updated manually to add any comments and descriptions.

4. With a large shop and without some automated process and a large number of programmers it will be very difficult to monitor and update the XML file when new macros are created.