Troubleshooting Cloud Storage Solutions

Media status *TRF

Each BRMS volume has a status.  The status how the volume is currently being used. Status *TRF has been added to indicate a volume has pending cloud operations.   Run the following command to see all media that has a status of *TRF:

WRKMEDBRM TYPE(*TRF)



      Volume           Creation Expiration            Move     Media      Dup

 Opt  Serial    Status   Date      Date    Location   Date     Class      Sts

      Q07111     *TRF  10/20/16  11/10/16  HERBSTCLD  10/20/16 QCLDVRTTAP      



Most cloud transfers will be started by BRMS but run in jobs in subsystem QICCSBS.  To determine which jobs have been used to process cloud transfers for BRMS run the following command:

WRKSTSICC STATUS(*ALL)



                     --------- Job --------------                     Graphic% /

 Opt File name/Time  Name       User       Number Status      Oper    Complete%

     /QIBM/UserData/BRMS/cloud/Q1ACQ07111/Q07111                      *1

      10/20/16 14:34 L000000276 BRMSUSER   010875 Failed      TOCLD           11

     /QIBM/UserData/BRMS/cloud/Q1ACQ26819/Q26819                      **********

      10/21/16 06:30 L000000278 BRMSUSER   010930 Success     TOCLD          100

     /QIBM/UserData/BRMS/cloud/Q1ACQ07111/Q07111                      3

      10/21/16 06:30 L000000277 BRMSUSER   010929 Failed      TOCLD            3

     /QIBM/UserData/BRMS/cloud/Q1ACQ26819/Q12706                      **********

      10/21/16 06:30 L000000279 BRMSUSER   010931 Success     TOCLD          100

     /QIBM/UserData/BRMS/cloud/Q1ACQ26289/Q26289                      **********

      10/21/16 06:39 L000000280 BRMSUSER   010932 Success     TOCLD          100



Use the job information from the failed transfer to work with the job.  The job log will contain information about the transfer:

WRKJOB JOB(010875/BRMSUSER/L000000276)

option 4=Work with spooled files

option 5=Display

Diagnosing cloud transfer problems

CPE3455 - 'Broken pipe.' in QICCSBS job:

If an FTP cloud resource was used for the transfer, the target system may not have enough storage to receive the media.   Check the available storage on the target, for example if the FTP target is an IBM i, run the following command:

DSPSYSSTS



                                            Work with System Status              

                                                             10/21/16  07:14:45

 % CPU used . . . . . . . :         .1    Auxiliary storage:

 Elapsed time . . . . . . :   00:00:01      System ASP . . . . . . :    362.6 G

 Jobs in system . . . . . :       1298      % system ASP used  . . :    99.9730

 % perm addresses . . . . :       .007      Total  . . . . . . . . :    362.6 G

 % temp addresses . . . . :       .028      Current temporary used :     4723 M

                                            Peak temporary used  . :     5435 M            

Resolving cloud transfer problems

When a transfer to the cloud fails, the volumes may be left in *TRF status.  Once the transfer problem has been understood and fixed, if the volume still has a status of *TRF and the location is the cloud location, do the following recovery on the source system:

  • Use WRKMEDBRM option 8 'Move' to change the Storage location to *HOME

  • Run STRMNTBRM MOVMED(*YES) or MOVMEDBRM to retry the cloud transfer

Restore problems

CPF41B0 – Incorrect image catalog name specified.

Check the current location of the volume BRMS is trying to restore from in WRKMEDBRM.  If the volume does not have a status of *ACT and the location is not the cloud location, run STRMNTBRM MOVMED(*YES) on the source and remote system and verify the volume has a status of *ACT and the location is the cloud.  Retry the restore.

Collecting traces to diagnose IBM Cloud Solutions for IBM i

To collect flight recorders for IBM Cloud Solutions for IBM i, you can follow these instructions from IBM Support, or use the instructions below:

In order to debug issues using IBM Cloud Storage Solutions for i you need an activate flight recorder. To activate the "flight recorder" these 2 data areas in the program library (QICC) should be created:

CRTDTAARA DTAARA(QICC/QICCTRCLVL) TYPE(*CHAR) LEN(2) VALUE('55') TEXT('Trace Level')

The trace files will be in the /QIBM/ProdData/QICC directory. There will be one file for each transfer, file names are in the form QICC-YYYY-MM-DD-HH-MM-SS-jobnum-user-jobname.log. Use WRKSTSICC STATUS(*ALL) to find the job information for the transfer you are interested in.



NOTES:

  1. Together with flight recorder is necessary to collect also joblog.

  2. The flight recorder only generates output when copy jobs are run in batch. The Copy from/to jobs are run in batch by setting the ASYNC parameter to *YES. If the sub-system is not active, the jobs remain on the job queue waiting for the sub-system to start. The command STRSBS QICC/QICCSBS is used to start the sub-system as needed.