00D70014   

Explanation

An attempt to extend a data set failed, because a problem was detected in media manager services.

System action

Abort the request.

Operator response

Notify the system programmer or database administrator.

System programmer response

Notify the database administrator if appropriate. Otherwise, check the packs available to the data set. They might merely be full or the data set might have reached its maximum allowable extents. For more information, see the description of message DSNP001I.

User response

Notify the operator, system programmer, or database administrator.

Problem determination

Obtain console sheet that shows associated DSNP001I, DSNO007I, or DSNP011I messages and any related messages that precede them. This documentation can assist you in determining the cause of the problem. For more information, see the description of these messages.

Start of changeIn some cases, this problem might occur because DB2® encountered unexpected user-created catalog index definitions that interfere with the migration process. See the information about migration job DSNTIJPM and the information about creating indexes on catalog tables in the description of CREATE INDEX.End of change

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • Dynamic dump, taken to SYS1.DUMPxx data set, by DB2 (04E and 04F abends).
  • SVC dump (or system dump), taken to SYS1.DUMPxx data set, as result of an operator-initiated dump command or SLIP trap exit.
  • SYSABEND, SYSUDUMP, or SYSMDUMP output.
  • Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.
  • IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the DB2 subsystem catalog that defined the failing index or table.
  • VTOC listing of the disk volume on which the failing operation occurred.
  • Listing of the results produced by the SQL statements.
  • SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
  • Definitions of views and tables involved in the error.