"Gordon Wolfe, Ph.D." <[EMAIL PROTECTED]> writes: > For those who are interested, my position will be opening up. > Boeing will actually have 2 positions in VM Systems opening, as soon > as we fill the position of Delivery Systems Manager. My last two > managers quit within three months of each other. Maybe it's my > deodorant? I don't know when the position(s) will open up. I doubt > that hiring will be an immediate priority for the new manager. But > go to http://www.boeing.com, at the top select 'employment', and at > the right select 'Job Search'. This is 'Information Technology' or > possibly 'Computing Delivery Systems', 'Salaried Non-Management', > state of Washington, 'Experienced'. The job title is 'System Design > Integration Specialist', which might be abbreviated 'Syst Desn Intgr > Spec'. Search keywords 'VM' or 'ESS' or 'LINUX', and maybe on the > job classification BCBDP4. This might be filled at a P3 or even a > P2, so check those too. I'd check once a week. These reg's > don't stay open very long when they do open up. The last time we > opened a req, we got 88 applications, interviewed 6 and hired none > of them. The position is still open.
i did much of the original virtual machine install at boeing. three people from cambridge science center http://www.garlic.com/~lynn/subtopic.html#545tech had come out to the university the last week in jan. '68 to install cp/67. I did extensive modifications on cp/67 (as well as os/360) during that spring and summer and got to make a presentation on a lot of the os/360 and cp/67 work at the aug. '68 SHARE meeting in boston. BCS was formed around dec(?). '68. BCS was to take over most of the data processing at boeing and had made some decision to do some amount of work with virtual machines (i think part of the idea was that BCS could sell services not only inside boeing but also to other customers). IBM and Boeing talked me into teaching a one week (40hr) cp/67 class at the univ. to the (then small) BCS technical staff.during spring break. BCS was still starting up and the core was located at BGS dataprocessing corporate hdqtrs across from Boeing field. They had a 360/30 for doing Boeing payroll. A "simplex" (uniprocessor) 360/67 was brought into the same machine room for cp/67. I was hired as a full-time BCS employee (even tho I was still an undergraduate) for that summer (69) at some level that gave me a badge allowing me to park in the management parking lot next to the bldg. (as opposed to the large parking lot behind it where most of the assembly workers parked). BCS hdqtrs people were still in discussions about absorbing the other datacenters (like the big one down in Renton). Everett was still starting up and "003" 747 was flying FAA certification test in the skies around Seattle that summer. When I first arrived, I was taken on tour of a number of facilities. One that I still remember was a mockup of a 747 interior and being told that the 747 were so large and carried so many people that they would never be served with fewer than four jetways (for passenger loading/unloading). What is the percentage of time that you've seen a wide-body with even two jetways (instead of just one)? For the summer, I was renting the basement from one of the engineers working on 747. They had remodeled their house and the basement was now its own apartment. He had stories about some sobotage that was occuring that summer on the 747 project in Everett. BCS also managed to latch onto a two-processor 360/67 multiprocessor that was down at Boeing Huntsville and have it moved to Seattle. It had been running a highly modified version of os/mvt release 13 supporting a lot of 2250 graphics work. The 2250 graphics work was long running jobs and MVT had significant memory fragmentation problems with long running jobs. Basically it was running 360/65 SMP code with a small modification to turn on the 67s virtual memory. There was no paging going on ... the virtual memory support was purely being used to re-organize memory allocation into contiguous locations (workaround for the underlying memory fragmentation). that summer at boeing one of the things I managed to do was rework some of the internal CP67 kernel linkage. I had previously done a lot of specific pathlength rewrites and fastpath work ... some of which were mentioned in the 68 boston share presentation. the original cp67 had all linkage using svc8 for calls and svc12 for returns. I had analyzed a number of high useage, short pathlength subroutines that could benefit from BALR linkages (i.e. the svc call/return pathlength was frequently as long as the subroutine pathlength). I modified call/return macro to do the BALR linkage convention (instead of SVC) for the selectively modified routines. Also that summer, I had done the first implementation pageable kernel structure (again with a hack in the call/return for the selective routines). I had started with specific (lower useage) functions/features in the console module ... which was a single large module. One of the things that I first needed to do was break it into multiple 4k sized chunks for the portions that were going to be paged. Breaking "console" into multiple 4k chunks created a lot of additional external entries which then caused a problem with the stand-alone loader used for cp67 system generation. The cp67 loader had started out life as standard "BPS" card loader with minor modifications. It had a limit of 255 external entries. The breakup of console pushed the number of entries in the cp67 kernel over 255, which in turn broke the loader. While every other piece of cp67 was shipped as source code, there was no source code for the laoder. It was a real pain in the rear to work around this problem. balr leakage stuff eventually shipped in cp67 3.1 ... but the pageable kernel stuff didn't show up in the product until vm370. random refs to the 68 boston share meeting: http://www.garlic.com/~lynn/94.html#18 CP/67 & OS MFT14 http://www.garlic.com/~lynn/94.html#20 CP/67 & OS MFT14 http://www.garlic.com/~lynn/97.html#22 Pre S/360 IBM Operating Systems? http://www.garlic.com/~lynn/98.html#21 Reviving the OS/360 thread (Questions about OS/360) http://www.garlic.com/~lynn/2001f.html#26 Price of core memory http://www.garlic.com/~lynn/2001k.html#37 Is anybody out there still writting BAL 370. http://www.garlic.com/~lynn/2002c.html#45 cp/67 addenda (cross-post warning) http://www.garlic.com/~lynn/2002m.html#3 The problem with installable operating systems http://www.garlic.com/~lynn/2002n.html#29 why does wait state exist? http://www.garlic.com/~lynn/2003d.html#72 cp/67 35th anniversary http://www.garlic.com/~lynn/2004f.html#6 Infiniband - practicalities for small clusters http://www.garlic.com/~lynn/2005m.html#16 CPU time and system load misc. past posts mentioning bps loader: http://www.garlic.com/~lynn/94.html#11 REXX http://www.garlic.com/~lynn/98.html#9 ** Old Vintage Operating Systems ** http://www.garlic.com/~lynn/99.html#135 sysprog shortage - what questions would you ask? http://www.garlic.com/~lynn/2000b.html#32 20th March 2000 http://www.garlic.com/~lynn/2001b.html#23 Linux IA-64 interrupts [was Re: Itanium benchmarks ...] http://www.garlic.com/~lynn/2001b.html#26 HELP http://www.garlic.com/~lynn/2001b.html#27 HELP http://www.garlic.com/~lynn/2002f.html#47 How Long have you worked with MF's ? (poll) http://www.garlic.com/~lynn/2002h.html#35 Computers in Science Fiction http://www.garlic.com/~lynn/2002i.html#2 Where did text file line ending characters begin? http://www.garlic.com/~lynn/2002n.html#62 PLX http://www.garlic.com/~lynn/2002n.html#71 bps loader, was PLX http://www.garlic.com/~lynn/2002n.html#72 bps loader, was PLX http://www.garlic.com/~lynn/2003f.html#26 Alpha performance, why? http://www.garlic.com/~lynn/2004g.html#45 command line switches [Re: [REALLY OT!] Overuse of symbolic constants] http://www.garlic.com/~lynn/2005f.html#10 Where should the type information be: in tags and descriptors http://www.garlic.com/~lynn/2005f.html#16 Where should the type information be: in tags and descriptors http://www.garlic.com/~lynn/2005g.html#52 Software for IBM 360/30 http://www.garlic.com/~lynn/2005s.html#50 Various kinds of System reloads -- Anne & Lynn Wheeler | http://www.garlic.com/~lynn/
