R.S. wrote:
IMHO it's good. At least for the companies. System programmers should do
system programming, working in companies which produces systems.
Companies which *buys* systems should have system exploitation staff.
Last but not least: it is much less probable to blow up the system when
using tools.
I've worked both sides of the fence, and found the same problems - you
follow IBM documentation and write bullet-proof code, then IBM makes a
bomb! How many programs broke when IBM decided the 3880 control units
would terminate a CCW chain after the second index point, even if it was
on a different CCW, and working correctly? Even IBM got caught on that
(CVOL and VTOC data update chains).
Gerhard Postpischil
Bradford, VT
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
