5 ms·
I'm not sure what you mean by "decent technical documentation describing things". IBM is very open about publishing their documentation. For instance "Introdu
by jdboyd 14y ago
I'm not sure what you mean by "decent technical documentation describing things". IBM is very open about publishing their documentation. For instance "Introduction to the New Mainframe: z/OS Basics" is available here:
http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246366.html?OpenDocument http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg...
I'm not saying that this makes it easy to get access to, which is still a real problem.
- sophacles 14y agoThis is a good point - I should clarify: what I mean is that there aren't a lot of tutorials, step-by-steps, etc by people using the systems... the type of thing I think of as "screwing around guides". The IBM documentation always feels more like deep manual. I'm pretty sure that even if I had access, I couldn't be up and running on a mainframe in an hour, like I could with some web stack and a simple app tutorial, there don't seem to be good blogs on "how I managed to do $HOT_TOPIC_OF_THE_WEEK on my mainframe". I find these really important for understanding various other technologies... not as an end to my understanding, but as an entry point. Conversely, If I finally get some time to look at Clojure seriously, I know how to find resources in a simple way. I could very well be wrong about this though. Maybe they exist and I just don't know the ecosystem terminology, but that itself is a problem, I can't even figure out how to get into the ecosystem if it exists.
- VLM 14y agoIs there an equivalent to http://www.debian-administration.org/ http://www.debian-administration.org/ for MVS, z/OS, pretty much any mainframe system (other than S390 linux, which is kinda cheating)