www.ibm.com: IBM Instructions for downloading packages from z/OS USS tools pages
How to get the package There are three ways to get a package: Through your browser Anonymous ftp If all else fails, For tools packages, send a note to Bill Schoen ( firstname.lastname@example.org) letting him know what problems you had and he’ll be happy to email the package to you. For PDF files (such as presentations), send a note to Henry Gorbsky ( email@example.com) letting him know what problems you had and he’ll be happy to email the file to you. We also have some general information on handling a tools package after it has been downloaded.
preview.reuters.com: How the Pentagon’s payroll quagmire traps soldiers
DFAS, for its part, inherited a pay operation that even at the time was an antique – a 20-year-old Air Force system that DFAS renamed the Defense Joint Military Pay System, or DJMS. It ran, and still runs, on Cobol, a computer language that dates to 1959. Most of the Cobol code the Pentagon uses for payroll and accounting was written in the 1960s, according to 2006 congressional testimony by Zack Gaddy, director of DFAS from May 2004 to September 2008.
Bernard PINON: August 2002. This document describes an implementation of a COBOL 85 parser for JavaCC
The current implementation violates the strict COBOL orthodoxy :
It’s a free format COBOL. Forget about areas, columns, etc. Text can be written from column 1. You can even write the entire program on a single line.
Comments starts with *> and ends at the end of the current line. You can put comments anywhere. I also plan to introduce Java-like comments, just for aesthetic reasons.
There is no need for continuation lines. But unfortunately debugging lines are ignored.
Preprocessing instructions COPY and REPLACE are not implemented and will not be.
Same remark for compiler options.
The parser does not check for clause unicity in a statement. For instance you could write “PERFORM UNTIL condition UNTIL other-condition” which is illegal. If you want to create a compiler from this parser, you will have to check for this, or allow it assuming that only the last clause of its kind will have an effect.
Some Tandem (oops…) extensions and IBM (nobody has bought them recently ?)
Firebird – The RDBMS that’s going where you’re going
Firebird is a relational database offering many ANSI SQL standard features that runs on Linux, Windows, and a variety of Unix platforms. Firebird offers excellent concurrency, high performance, and powerful language support for stored procedures and triggers. It has been used in production systems, under a variety of names, since 1981.
The Firebird Project is a commercially independent project of C and C++ programmers, technical advisors and supporters developing and enhancing a multi-platform relational database management system based on the source code released by Inprise Corp (now known as Borland Software Corp) on 25 July, 2000.
heise online – Unterhalt von Java-Software teurer als von Cobol-Programmen
Der Bericht (PDF) bewertet die Aspekte Robustheit, Leistung, Sicherheit, Einarbeitungsaufwand (Transferability) und Flexibilität. Transferability beschreibt den Aufwand einer neuen Entwicklergruppe für das Einarbeiten in die Anwendung, sodass sie produktiv an ihr arbeiten kann.
Bei der statischen Code-Analyse mit dem hauseigenen Werkzeug “Application Intelligence Platform” ermittelte CAST eine als “technische Schuld” (technical debt) bezeichnete Größe zum Messen der Code-Qualität. Sie beschreibe “die Kosten für die Behebung jener Probleme in einer Anwendung, die das Unternehmen einem ernsthaften Risiko aussetzen.”
Am höchsten liegen, so CAST, die durchschnittlichen Schulden bei J2EE-Anwendungen, während Cobol- und ABAP-Anwendungen sehr niedrige Werte haben. Dazu dürfte auch beitragen, dass Cobol-Programme im Durchschnitt wesentlich älter sind als etwa in .NET oder Java geschriebene, sodass viele Bugs bereits entdeckt und beseitigt sind.
Interfacing with C Programs – cobpostsighandler()
The cobpostsighandler() routine enables two or more handlers to be posted for the same signal. When that signal is generated by the operating system (such as a SIGINT generated when the interrupt key is pressed), each handler can take appropriate action and then let other handlers be executed (by returning a non-zero value). Alternatively, they can decide to make the signal “ignored” by returning a value of zero to prevent other handlers from being executed. However, so that your handler can work with other handlers for the same signal, a handler of priority 140 (or more) should return non-zero to let other handlers have the opportunity to also be notified. A handler of priority 128 can return zero if you do not want the run-time system default action to be executed (which may cause termination).