TMSMR99E CA 1 EXTEND PROCESS ABORTED. REASON=005
search cancel

TMSMR99E CA 1 EXTEND PROCESS ABORTED. REASON=005

book

Article ID: 74500

calendar_today

Updated On:

Products

CA 1 Flexible Storage CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options

Issue/Introduction

Trying to extend my TMC in a shared environment. I started TMSRINIT on my shared system as requested by TMSXTEND with message

*TMSXT50I CPU(cccc) HAS NOT ACCESSED NEW TMC. RUN TMSRINIT ON THAT CPU. 

but TMSRINIT on this CPU failed with message

*TMSMR99E CA 1 EXTEND PROCESS ABORTED. REASON=005
 

Environment

Release:
Component: 1

Resolution

This message means, that TMC.N could not be accessed. In a nonshared MVS/catalog environment be sure TMC.N has been cataloged manually on all shared systems before running TMSXTEND.

Following related messages in the TMSXTEND joblog in case TMSRINIT fails with above TMSMR99E message:

*TMSXT59E CPU(cccc) NEW TMC ACCESS FAILED!.   
 TMSXT14E SOME CPU(S) DID NOT ACCESS NEW TMC.


and finally TMSXTEND will abend with

USER COMPLETION CODE=1022 REASON CODE=0000003B
 

Additional Information

In a nonshared MVS/catalog environment perform the following steps on the systems not running TMSXTEND, after TMSXTEND has finished successfully and all systems have switched to the new TMC confirmed by message TMSMR04I CA 1 SWITCHED TO NEW TMC
  • uncatalog the old TMC
  • Catalog the TMC on the new volume where you allocated TMC.N.