Check to make sure you re-assembled all JES2 "interface tables" and/or interface modules for the various products. We had a problem like this once when we changed z/OS levels, JES2 control blocks and data areas had changed; the vendors were able to handle it, but it took place when you ran their job which assembled what they needed using the new JES2 macros. What was happening, for us, was that the vendor products were "monitoring" things in JES2 (sometimes inserting themselves into exit points, etcetera) but they were using bad mappings for data areas. The abends would show up in odd places, for example they'd seem to be in the initiator after the job had ended - because some code had hooked itself into the IEFACTRT exit point, passing control and information to a vendor module - but that module had an old view of how the data areas were supposed to look.
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
