Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
  Results
CMS-XML IOO313: After upgrading BMC Reorg Plus for DB2 software getting messages IEC991I IFG0RR0A when optimized by IOO
IOO313: After upgrading BMC Reorg Plus for DB2 software getting messages IEC991I IFG0RR0A when optimized by IOO
CMS-XML Batch DB2 job gets s0c4 abend with upgrade to IOO 3.1.5.02
Batch DB2 job gets s0c4 abend with upgrade to IOO 3.1.5.02
CMS-XML IOO313: Two job steps not being optimized by IOO
The following comments were supplied by the IOO development team regarding the System Rules and DCF Tables: We see no reference in DCF or the rules table for a stepname of DB2 BTCH as shown in the trace information: From the IOO User’s Guide on page 89, regarding the System Rules Table:
CMS-XML VSAM files buffered under release IOO 3.1.3 but not under IOO 3.1.4 possibly due to program override
- V314- DFH, - CICS V314- DSI, - NetView V314- DSN, - DB2 V314- DSX, - NetView V314
CMS-XML IOO313: Message ULTI2216 involved in ABEND
But even if I had, I wouldn't have known about the new name or owner (Serena's StarTool IOO), so thanks for that information. I'm not sure that excluding IOO from running on HSM will totally resolve the problem for you, because I believe it can happen in any address space in which more than one Open is being issued at the same time ... which probably means things like DB2 , IMS, and CICS. At any rate, go ahead and close this PMR whenever you're ready.

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs