#Ibm iconsole output queue inavigator code#

So based on that we built the first security system written by ourselves-of course in Assembler language-so that was pretty good. So what we did was that we basically wrote our mini standard into that with our own SFCs, etc., etc. Reg: SAF is pretty solid and everybody uses it.

We came up with the idea, 'why don't we write our own using the SAF interface that everybody uses?' We didn't buy RACF and we didn't buy Top Secret or ACF2. An interesting point was that we were SOUS bureau, so we didn't have a lot of money. Then I went off to an assignment in Nigeria to do something completely different and then coming back again, we heavily modified the operating system, and then at that time JES-2 too, to actually fit into our schedule. Then of course the CBT-A, that was absolutely fabulous, so that's what we did. So these guys had developed once a procedure where they modified things and that inspired me a lot. Karl-Erik: In fact almost 95% of the time was spent on allocation, the allocation and changing SEPS. University people run very short ops, you know, compile LINGO. Karl-Erik: So that was one of the things that got me and still thinking about guys at university, you know. So we had all the OS/360 also in source code. So what you could do but of course with you know, microfiche, where you had a film.

#Ibm iconsole output queue inavigator code#

HASP was source code you know and it was so easy to do, because they gave you the source code and you basically just fixed it up. In my first job, it was mostly around just HASP. Reg: Now a couple of things you've said so far make me think that maybe you got to make some changes to the operating system, because this is back when the source code was still available. So the three senior people ahead of me just left, almost from one day to the other, so I was thrown out on the deep water as a very, very young and very junior systems programmer. Then you know at the time you could basically write your own paycheck if you were a good systems programmer. Karl-Erik: It was absolutely gorgeous and we were running OS/360 MFT and HASP, so that's how it all started. We had a fabulous 360 Model 40 that had 128K of memory. So when I got back from education, I specifically asked in the company if I could join what they called the system programming department as a junior assistant programmer and got that. to the 360 guys at the university, I'd like to do that. One of the things we did was that we were taught Assembler language and that just got me, you know. So I went to this educational testing that they called IT programmer or IT assistant or whatever you want, but it was basically a programming class. They were seeking some hopeful that would be given a course-a one-year course with salary paid, of course-because there was no formal education for information technology at the moment. So when I finally got myself together and quit the mechanical engineering, I got employed by a relatively big Danish company who was running in about 45 countries across the world. I said this sounds like something I'd like to do. So the idea of IT had come to me but then when I saw this thing and started talking to the people operating it, they were modifying the operating system and doing things.

During my first starters, we used some advanced HP-you would call them advanced calculators. At my university they had this big thing sitting there called the System/360 Model 75. I tried very hard to become a mechanical engineer by the end of the 60s-you know, cars and gearboxes and so on-and then it just happened. Karl-Erik Stenfors: Well, a bit of a point. Well Karl-Erik, let's start by telling us about how did you end up on the mainframe? Reg Harbeck: Hi, I'm Reg Harbeck, and today I'm here with my colleague and co-author Karl-Erik Stenfors, who has been in the mainframe space for a very good long time.