IBM Support

Importing SVC / Storwize Performance Data into IBM i Database files

Troubleshooting


Problem

This document describes how to import performance data collected from SVC / Storwize storage systems into database files on the IBM i using QMGTOOLS. This applies to svc_snap data and iostats files collected from SVC, V3700, V5000, V7000, V840 and so on.

Resolving The Problem

The SVC Import command (QMGTOOLS/SVCIMPORT) will import data from within a snap file or from iostats XML files that have already been restored to an IFS directory. Optionally, if the data was collected with the SVC Snap command (QMGTOOLS/SVCSNAP) configuration files will be imported as well.

The data is imported into the following files. The target library and member name is specified on the command.

Performance statistics:

QSVCMDISK: MDISK (Managed Disk) statistics.

QSVCVDISK: VDISK (Virtual Disk) statistics.

QSVCDISK: Physical Disk statistics. This file will be empty for SVC systems since they do not have internal disks.

QSVCCPU: System CPU utilization statistics.

QSVCNODE: Node level statistics.

QSVCCACHES: Cache statistics at the system level / node level.

QVCSCACHEP: Cache partition statistics.

QSVCPORTS: Fiber Channel, iSCSI, SAS, PCIe, and IPREP statistics.

Optional configuration files collection by QMGTOOLS/SVCSNAP:

HOSTDISKMAP: Output from LSHOSTVDISKMAP command.

LSVDISK: Output from LSVDISK command.

LSNODE: Output from LSNODE command.

SVCIMPORT Instructions:

1. ADDLIBLE QMGTOOLS.

2. GO MG, Option 14 for External Storage.


image of GO MG #14 menu

3. Select Option 1 for SVC/Storwize.

Image of selecting Option 1 for SVC/Storewize

4. Select Option 3 for SVC/Storwize data import. This option will prompt the QMGTOOLS/SVCIMPORT command.

Image of selecting option 3

If importing an svc_snap file form an SVC or Storwize system, use the instructions in Step 5.

If importing SVC or Storwize iostats files from an IFS directory, use the instructions in Step 6.

5. Fill out the following parameters if you are importing an svc_snap file from an SVC or Storwize system.

.tgz file? (N = stats files) . . UNZIP > Y
Snap .tgz file name . . . . . TGZFILE > 'your snap file here'

Collected with QMGTOOLS ? . . QMGTOOLS > Y

Note: Only use QMGTOOLS 'Y' if the svc_snap was collected with the QMGTOOLS/SVCSNAP command.

Source Directory . . . . . . . . DIRECTORY > 'your IFS directory path'
Target member name . . . . . . . TARGETMBR > YOURMEMBER
Target Library . . . . . . . . . TARGETLIB > YOURLIB

Note: The library and files will be created if they do not exist on the system. Additional members may be added to existing files each time the command is run. For example, data from Jun 12 specify TARGETMBR(JUN12), Jun 13, TARGETMBR(JUN13) and so on.

Example command syntax and screen capture:

QMGTOOLS/SVCIMPORT UNZIP(Y) TGZFILE('78N1APD-1.140504.134610.tgz') QMGTOOLS(Y) DIRECTORY('/tmp/mysvcsnap') TARGETMBR(SNAP0610) TARGETLIB(SVCSNAPS)


Image is an example of QMGTOOLS/SVCIMPORT command

6. Fill out the following parameter if you are importing SVC or Storwize iostats files from the IFS.

SVC/Storwize Data Import (SVCIMPORT)

Type choices, press Enter.

.tgz file? (N = stats files) . . UNZIP N
Source Directory . . . . . . . . DIRECTORY > 'your IFS directory here'



Target member name . . . . . . . TARGETMBR > YOURMEMBER
Target Library . . . . . . . . . TARGETLIB > YOURLIB

Note: The library and files will be created if they do not exist on the system. Additional members may be added to existing files each time the command is run. For example, data from Jun 12 specify TARGETMBR(JUN12), Jun 13, TARGETMBR(JUN13) and so on.

Example command syntax and screen capture:

QMGTOOLS/SVCIMPORT DIRECTORY('/tmp/mysvcsnap') TARGETMBR(SNAP0610) TARGETLIB(SVCSNAPS)

Image is an example of QMGTOOLS/SVCIMPORT example



[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]

Document Information

Modified date:
18 December 2019

UID

nas8N1020148