>It seems that the systems man made some changes to the zOS to fix this >problem before he left. He did not say what he did to fix it, and it >will be a couple of weeks before I can find out what he did.
You not only have a software problem (possibly) you have a management problem. If you have a systems programmer who can make changes and leave without leaving notes on those changes (minimal change management), and you have no backup systems programmer (employed OR "rented") to handle technical issues while the primary guy goes on vacation, then in my perhaps-not-so-humble opinion, management has put your system at risk. What happens if the OS decides to lay down and die in the middle of your business cycle (whatever it is), and no one is there with the skills and/or tools to fix it? Obviously, you can't employ two "guru-level" systems programmers just for z/OS, and another pair for CICS, and another pair for DB2 unless you have the kind of business that requires it and the kind of revenue that can pay for it - but you CAN do some cross-training and some policy-and-procedure writing to make the situation less risky. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 ---------------------------------------------------------------------- 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
