>The COBOL requirement seems a bit odd for a system programming position. It's >not a bad idea in a COBOL shop, but it limits the audience to those in or from >application programming. Same comment for the PL/I requirement.
I see no problem with a SYSPROG with a knowledge of COBOL and/or PL1. One job a true SYSPROG has is to help application programmers with problems. At my last job, if I didn't know COBOL, I wouldn't have been able to help application programmers solve API problems with a new product. I also know PL1, FORTRAN, PASCAL, C/C++, SQL, VB, some JAVA, ASM, SAS, REXX, and CLIST (though I don't use it much), and many non-SYSPROG languages. That helps me help them. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
