On Pre-defined Job and Adhoc Job submission, change automated creation of JOBS default job stream on Plan to be by folder to enable better folder separation

Today, there's a little secret when submitting a Pre-defined Job onto the plan when you don't have an existing job stream on the plan to put it in: just put into the "Into Job Stream" field in DWC the following magic text: "/JOBS".  On submission, whether or not there is a JOBS job stream already on the plan, one will get created, linked to the chosen "Into" workstation, and the job requested added to it.  Otherwise you have to find a job stream already on the plan on the workstation you're trying to target, which sometimes there isn't.

The issue is that this default job stream, "JOBS", always shows up under the root folder as "/JOBS".  Where RBAC security may be separated by lists of Workstations, this isn't an issue, because the /JOBS job stream comes in associated with the target workstation.  But where RBAC security is based on folders, separating teams into them and putting their owned workstations under those folders, there is an issue.  If a user only has operator-type privileges on their own folder, and submits a pre-defined job using the "/JOBS" trick, their job submission goes in, but then they can no longer manage the job, because they don't have privileges on root.  We are finding that our team users can submit a singleton job, but if they put it on Hold for release later, or attach a time and want to change it later, or it ABENDs and they want to re-run it, they can't do anything to the job-- they get an access error instead.  

The idea here would be to allow the person to choose the folder for the default job stream to go under: to choose the whole Job stream path.  If they put in /MYTEAM/JOBS, if it does not exist on the plan yet, it gets put on the plan immediately as the job goes in (assuming no name clashes).  This then puts the new job stream under their folder and allows for regular job actions per their folder RBAC privileges.

We have a workaround where we created a folder all teams have job/jobstream management privileges on, called "/ADHOC".  We have a job stream, "STREAM" defined on a Workstation Group containing all our workstations.  The job stream has no jobs and is loaded daily.  That produces a "/ADHOC/STREAM" job stream for every workstation every day.  If no jobs get put in it, it's empty at end of day and rolls out, and a new one comes in.  This allows everyone to choose "/ADHOC/STREAM" as their default job stream with a guarantee it is on the plan for any workstation they might be working with.  And everyone can manage jobs put into one of these.  So it's working.  The issue is, everyone can then manage such jobs once they're there, including jobs that aren't theirs; we can't control it by folder because it's all in one folder.  Putting one of these under every folder is our next attempt, but then we need to create a Workstation Group and this STREAM job stream definition under each folder.  And someone has to maintain each team's Workstation Group of just their workstations.  Ugh.  Everyone just wants "JOBS" to come in when they ask, but under their folder.