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  
Pages [Next]
  Results
CMS-XML IOO313: VSAM return code of 30 from the application, and a user abend 100 when running under IOO
IOO313: VSAM return code of 30 from the application , and a user abend 100 when running under IOO
CMS-XML SC03 abend when IOO 3.1.4 uses large block interface (LBI)
When LBI is enabled, SC03 abend occur when invoking large blocksizes with application reading files. ---------------------- IEF233A M 522C,M70107,,PCCG05DD,CCG05S20, 664
CMS-XML IOO VSAM issue with Easytrieve v11.6
IOO does not appear to be providing buffers for a particular VSAM file some of the time, but not others. In doing so, it is masking a coding error in the application that accesses the VSAM file. The application in question is an Easytrieve program.
CMS-XML Licensing implications of z15 System Recovery Boost feature on ChangeMan ZMF, ChangeMan SSM, Comparex, StarTool FDM, and StarTool IOO
“System Recovery Boost is a new feature that is implemented in z15 CPC firmware. It delivers improved overall system and application availability by minimizing the downtime that results from system shutdown and restart operations.
CMS-XML IOO311: Getting Message ULTI254I
The internal table hold 50 RPLs. The user application must be using more than 50 RPLs, and thus got the message about the RPL Support Table. The message means they went over our internal maximum number of supported RPLs per ACB.
CMS-XML Questions on XML licensing and CSA
Answer: Run the LICUPDAT utility with the ‘LOAD’ parameter and then re-run the application . Installing new licenses with the ADD or REP parameter does not automatically load the new licenses into CSA. If new licenses are installed, you must run LICUPDAT a second time with the LOAD parameter to update the licenses cached in CSA.
CMS-XML IOO312: StarTool IOO V3.1.2 new install still showing IOO 311 as the product VRM in the Statistics Block
The pre-release module(s) or patch that you have requested from Serena Software is not yet Generally Available. Upon application of the module(s) or patch, some risk is assumed since it has not successfully completed a rigorous test cycle in a released product.
CMS-XML IOO311: Problem with opening of file, and running out of storage.
understanding the customers issue correctly, their application is OPENING/CLOSING different ACB's for the same file? If that's so, then they can do what we did, and each OPEN should use one LSR pool. Here is our table entry:
CMS-XML IOO311: Upgraded to this release from R200, and jobs are not being optimized.
I would tend to leave things alone. Unless they know of other applications that perform some sequential I/O followed by tons of direct I/O.
CMS-XML IOO311: How does IOO Buffering/Reblocking operate in FOCUS jobs.
With BSAM, you can do a POINT (by using TTR's) . Unless the FOCUS routine is doing POINTS, then it is reading sequentially. If FOCUS indeed reads the first block of data, only references the first 4K of data, then does a point to another 4K block of data, etc, etc; then additional buffering and increased blocksize would hurt their application by reading in data that never gets referenced.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs