allow files on the Editor Configurations page in property groups to use variables when the remote preprocessor is selected

When trying to use the new preprocessor option in RDz, if you are using a remote preprocessor you must define the mainframe files on the Editor Configurations page of the Property Group. One if these fields is the Preprocessor Output Location. This is defined as the Fully qualified name of the output file that is downloaded from the host to the workstation after a remote preprocessor is invoked. It must be either a partition data set (PDS) member or sequential data set.

The way the Preprocessor Output Location must be set up is a file that uses no variables. In our shop we have a standard workspace that everyone copies in and uses as a basis for their own workspace. Since we have over 700 people that will be using RDz it would be impossible for everyone to use the same PDS member. To resolve this it would require that each person go in and change this property group setting. If you have mainframe defined property group this is impossible. We also have 25-30 property groups so a lot of modifications would be needed. The better option would be to allow the use of variables that are already allowed in RDz. The ability to use the $userid or $name would alleviate the need to make changes on to this once it has been set up.

It would be great if the High Level Qualifier for Preprocessor Data could also use these variables.