Dictionary De - En
De - Es
De - Pt| Proverbs, aphorisms, quotations (English) | by Linux fortune |
| === ALL USERS PLEASE NOTE ======================== JCL support as alternative to system menu. In our continuing effort to support languages other than LISP on the CADDR, we have developed an OS/360-compatible JCL. This can be used as an alternative to the standard system menu. Type System J to get to a JCL interactive read-execute-diagnose loop window. [Note that for 360 compatibility, all input lines are truncated to 80 characters.] This window also maintains a mouse-sensitive display of critical job parameters such as dataset allocation, core allocation, channels, etc. When a JCL syntax error is detected or your job ABENDs, the window-oriented JCL debugger is entered. The JCL debugger displays appropriate OS/360 error messages (such as IEC703, "disk error") and allows you to dequeue your job. | |
| C++ is the best example of second-system effect since OS/360. | |
| Established technology tends to persist in the face of new technology. -- G. Blaauw, one of the designers of System 360 | |
| It is a very humbling experience to make a multimillion-dollar mistake, but it is also very memorable. I vividly recall the night we decided how to organize the actual writing of external specifications for OS/360. The manager of architecture, the manager of control program implementation, and I were threshing out the plan, schedule, and division of responsibilities. The architecture manager had 10 good men. He asserted that they could write the specifications and do it right. It would take ten months, three more than the schedule allowed. The control program manager had 150 men. He asserted that they could prepare the specifications, with the architecture team coordinating; it would be well-done and practical, and he could do it on schedule. Furthermore, if the architecture team did it, his 150 men would sit twiddling their thumbs for ten months. To this the architecture manager responded that if I gave the control program team the responsibility, the result would not in fact be on time, but would also be three months late, and of much lower quality. I did, and it was. He was right on both counts. Moreover, the lack of conceptual integrity made the system far more costly to build and change, and I would estimate that it added a year to debugging time. -- Frederick Brooks Jr., "The Mythical Man Month" | |
| It is a very humbling experience to make a multimillion-dollar mistake, but it is also very memorable. I vividly recall the night we decided how to organize the actual writing of external specifications for OS/360. The manager of architecture, the manager of control program implementation, and I were threshing out the plan, schedule, and division of responsibilities. The architecture manager had 10 good men. He asserted that they could write the specifications and do it right. It would take ten months, three more than the schedule allowed. The control program manager had 150 men. He asserted that they could prepare the specifications, with the architecture team coordinating; it would be well-done and practical, and he could do it on schedule. Futhermore, if the architecture team did it, his 150 men would sit twiddling their thumbs for ten months. To this the architecture manager responded that if I gave the control program team the responsibility, the result would not in fact be on time, but would also be three months late, and of much lower quality. I did, and it was. He was right on both counts. Moreover, the lack of conceptual integrity made the system far more costly to build and change, and I would estimate that it added a year to debugging time. - Frederick Brooks Jr., "The Mythical Man Month" | |
| transparent, adj.: Being or pertaining to an existing, nontangible object. "It's there, but you can't see it" -- IBM System/360 announcement, 1964. virtual, adj.: Being or pertaining to a tangible, nonexistent object. "I can see it, but it's not there." -- Lady Macbeth. | |
