Evidently I’m too stupid to set it up. Certainly a possibility. Let’s just go with that. However I was able to set it up 5 years ago, and complete the Master the Mainframe course. After contacting support with credential problems, and starting over. The PDF seems pretty clear. I once again get…
There is only one thing I’ not strictly doing. And that is using MS VScode. I’m using Codium… VScode with the MS telemetry stripped out. That’s what I used 5 years ago. I would think if that’s the problem, I would get a different error.
In the past I liked Zowe. But if anything it should be easier to set up 5 years later. I don’t know why so many manual steps are necessary, 5 years later. On the other hand the PDF steps are pretty clear, and not hard.
I’m not going to humiliate myself, by asking for help… again! I’m following the PDF to a T.
I thought it’d be nice to learn a few new z/OS topics. Specifically I was interested in DB2. I’m familiar with SQL, but never used DB2. We used Adabas, and I was the DBA. However my successful mainframe career is over, at this point.
If there was blame to place it would be with the Systems Programmers who no doubt designed these procedures. Can you imagine application programmers designing a interface that required in house staff to edit config files before signing on? They no doubt have no experience in designing user interfaces. I was an a application programmer before becoming a IBM VM/VSE system programmer. How about some meaningful error messages. How about “User id not found” or “Invalid Password” instead of “Invalid credentials”. But that would require more work on their part. And we wouldn’t want that now… would we? It’s so much easier just spitting out a generic error message. I mean later in the document they say “if at any time your team configuration becomes corrupted (“messed up”), you can restore a basic working copy from the sample team configuration”. Working copy? Why not start there? It’s still manual but most of the correct values they tell you to use are there.