My brain dump on this topic.
In the new world, we need to fully understand where the source code management is to be expected. The reason you lock down Geneva is to ensure the source is not changed accidentally.
For someone to go in and change an lr would be highly detrimental to the rest of the team. I think there are two mode review and develop – sometimes you need to see how it was coded without being and xml genius. Hence view only.
Is it possible to have view based on userid without password? Userid’s to certain environments? Is that overkill? The beauty of the wb is that you don’t have to know xml. It helps when debugging but is not mandatory.
I struggle with this one – a mainframe programmer uses the point and click because very likely they have no server skillset. Is the overall object to make the mainframe like a server in outward appearance or train a server person to be
Are we taking a step back by eliminating the gui front end?
I guess it is silly to restrict people if you don’t have a password to ensure they are the people meant to have that access. So if we remove the authentication – what is the point of having different access rights? Good question. Protection
for the individual that doesn’t want to harm something.
Maybe it is more like browse with view only and browse with edit in the mainframe.
Agreed if you are taking that all away and considering it is only an editor – you will leave the authentication of changes in the hand of other software such as github commit authority or acf2 / racf authorization on the mainframe.
I think the answer to this question is the source code management – what is the proposal for that? Will the build / compile of a view or views take the source out of github? Then we have an answer. Commit is the way not to shoot everyone
in the foot by mistake.
What I am unclear of is where are the lr’s stored once we leave the workbench – are they stored in something like a copybook and pulled into the view at compile time? Is that the plan with the new wb replacement.
reviewing an issue re management of passwords led me to think about the workbench in a more general sense.
We currently do not manage our passwords in a way that will comply with the CII best practices.
We keep that passwords locally in a less than acceptable encrypted form.
I partially understand how to fix the issue.
But let's stand back and think about what the workbench is and where we want to go with it.
It is a temporary beast. We want to move to a language based approach.
As a step towards that I propose we think of the workbench as an editor. Nothing more.
An editor that produces say WB XML files. That can then be processed on the mainframe to generate the run control files and run the performance engine.
As such I think we should remove any password storage from the workbench system.
The database behind the workbench should be thought of as nothing more than a clever scratch pad.
Similarly the business of logging into the workbench is not really needed. The whole user account and management of internal permissions is pretty pointless.
Simple connect to the database and a given environment. Do what you want and export the xml.
It can then be stored in source control and re imported at a later date.
Share an environment with others. But treat the workbench just as an editor.
Agree how you are going to work together. Do not rely on the tool to sort it for you.
Or maybe just use a local database.... that is then much more like an editor?
This will greatly simplify it and the need for management of accounts etc,
All we need is to provide a login screen that makes a connection to the database and takes you to the desired environment.
What about someone accidently deleting things? Yep, a valid concern. Open to suggestions on that one.
If whatever is stored in a source control system then it can be restored.
Reply to the group with comments etc. And we can maybe discuss in our coming meetings.
Though I think things like this should be sorted outside of a meeting and merely confirmed in the meeting.
Looking forward to hearing from you. We need to figure out what we are going to do pretty soon.