we're hoping to activate pkg backout, on the surface peice of cake, obviously. the problem is how to automate everything the move processor did for the original executable, after backout: 0-3 binds (do you need to rebind if dbrm and load are both backed out?), backbinds, 0-20 cics newcopy's, wlm refresh for db2 stored procedures? endevor is licensed to 3 single lpars on 3 separate sysplexes. the production db2 subsystems and/or cics regions are not necessarily on the same lpar (but within the same sysplex). In the move processor all this is done today by a combination of processor overrides, ite and assorted rexxes that route the binds and newcopys to the appropriate regions.
Basically, I need to get to the processor group name, db2sys and cics symbolics from exit7 (COBOL preferably) and I assume pass them to an external rexx routine that resembles the move processor. Keep in mind all these years the only exits I've touched were the ones you guys submitted for support issues .
I'm open to suggestions!
Thanks!
Karen