What can cause S001 abends accessing M4LIBs?

Document ID:  TEC479192
Last Modified Date:  07/21/2015
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA VISION:Builder for CMS
  • CA VISION:Builder for VSE
  • CA VISION:Builder for z/OS
  • CA VISION:Inform for CICS
  • CA VISION:Two for CMS
  • CA VISION:Two for VSE
  • CA VISION:Two for z/OS

Releases

  • CA VISION:Builder for z/OS:Release:15.0
  • CA VISION:Inform for CICS:Release:15.0
  • CA VISION:Two for CMS:Release:15.0
  • CA VISION:Two for z/OS:Release:15.0
  • CA VISION:Builder for CMS:Release:15

Components

  • CA VISION:Builder.:V:BLDR
  • CA VISION:Two:V:TWO

This abend is usually caused by a BDAM M4LIB having been migrated using any program other than COMLIB utilities. This could have happened in a complete DASD backup, even to the same drive type, which is transparent to users.

The solution is to backup and restore the M4LIB using MARKUTIL with the UCDUMP, UCREST parameters. MARKUTL and the other COMLIB utilities are documented in Chapter 12 of the Environment Manual.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >