8464ch10_OperSW.fm Draft Document for Review February 7, 2020 3:15 pm The categories to be assigned by the host can be changed dynamically by using the  DEVSERV  QLIB,CATS command or by modifying the values that are specified in the DEVSUPxx member  and IPLing.  Special consideration should be given to the effects that the change that occurs on the host.  The most common problem is that, after the change, users might forget that all of the virtual  volumes in the scratch pool still belong to the initially defined categories.  If no volumes were assigned the new categories, requests for scratch mounts fail and OAM  surfaces the CBR4105I and CBR4196D messages.  This issue can be resolved by using several methods. If the categories were changed  because you want to partition the library, a scratch pool must be created for this host by  adding a range of volumes that are accepted by the TMS during cartridge entry processing.  If the old scratch pool was intended to be used by this host, the category of a single volume or  range of volumes can be updated by using the ISMF windows to ALTER one or the use  attribute from SCRATCH to SCRATCH. This step sets the category of the volume in the  library manager to match the associated newly defined category on the host (in DEVSUPxx).  If a large range of volumes must be changed, consider the use of the CBRSPLCS utility to  make such a change. For more information about how to use this utility, see  z/OS DFSMS  Object Access Method Planning, Installation, and Storage Administration Guide for Tape  Libraries , SC23-6867 . Note:  Modifying the volume entries in the TCDB by using IDCAMS does  not  change the  categories that are stored in the library manager and should not be used for this purpose. Some messages can be useful to capture by automation. In particular, the following  messages represent issues with the library being unable to call home. All library messages,  including these three, are prefaced with CBR3750I: The advised action for these messages is to contact the service center and hardware support  to determine why the call home was being attempted. For more information about a full list of  the conditions that are surfaced within the CBR3750I message, see  IBM TS7700 Series  Operator Informational Messages White Paper , WP101689. With OA56836 (available on z/OS 2.2 and above), OAM Object added the ability to use  XTIOT support. OAM’s use of XTIOT reduces SYSZTIOT contention in the OAM address  space during high levels of object store/retrieve activity to and from tape libraries. This  functionality is enabled by specifying the NON_VSAM_XTIOT=YES statement in the  DEVSUPxx parmlib member that is used for the system.  GLYPH<SM590000> OP0463: A TSSC error has occurred. The TSSC is unable to call home. GLYPH<SM590000> OP0625: A system reboot interrupted a call home.  GLYPH<SM590000> OP0550: Service Call Home, TSSC was unable to generate a PMR number. 10.7 Library messages and automation 10.8 OAM Object SYSZTIOT enhancement Chapter 10. z Host Console operations  615