Troubleshooting
Problem
This document provides the customer with side instructions for copying a MSD from ASP (MSD Manager) to a Virtual Tape Image.
Resolving The Problem
Read this First: The 26 steps in this document can be replaced by installing and using QMGTOOLS to collect and transfer an MSD to IBM.
- Obtaining QMGTOOLS: https://www-01.ibm.com/support/docview.wss?uid=nas8N1011297
- Using QMGTOOLS to collect and transfer an MSD: https://www-01.ibm.com/support/docview.wss?uid=nas8N1020800
Read this Second: If you are running IBM i 7.2 or later, there are native commands for copying Main Storage Dumps directly to the Integrated File System (IFS). This method is covered in document N1020052 Copy MSD directly to and from IFS file
| Note: The Main Storage Dump Manager compresses most MSDs using LZH compression. Therefore, there is no need to compress the virtual tape image files using utilities such as WinZip, WinRAR, 7-Zip, or to save it in a SAVF, as it will only add additional processing time for you and for IBM support. |
Customer Instructions
Step 1 - * Copying a MSD from ASP (MSD Manager) to a Virtual Tape Image *
Important Note: These instructions will get rid of everything created to save the MSD to virtual tape.
*** Do not perform these cleanup instructions until Support has verified the data is valid. ***
Note: Once this procedure has been completed, the IBM Support Center representative will need to complete the copy of the MSD from Virtual Tape to the Main Storage Dump Manager for MSD analysis to begin.
| A. | Sign on the IBM i5/OS with *SERVICE authority. |
| B. | Create the Virtual Tape Device. From the operating system command line, type the following: CRTDEVTAP DEVD(TAPMSD) RSRCNAME(*VRT) TEXT('Virtual Tape Device TAPMSD') ONLINE(*NO) Press the Enter key. A completion message is sent: Description for device TAPMSD created. Pressing the 'F1' key over the completion message will show this: Additional Message Information Message ID . . . . . . : CPC2622 Severity . . . . . . . : 00 Message type . . . . . : Completion Date sent . . . . . . : 02/03/07 Time sent . . . . . . : 12:29:30 Message . . . . : Description for device TAPMSD created. Note: If you receive the message "Device name TAPMSD already exists.", you should replace the parameter DEVD with another value of your choice. However, if you do that, remember that you will have to replace the parameter DEVD, DEV, and CFGOBJ with the value you chose any time they are used in the rest of the document. |
| C. | Vary on the Virtual Tape Device. From the operating system command line, type the following: VRYCFG CFGOBJ(TAPMSD) CFGTYPE(*DEV) STATUS(*ON) Press the Enter key. A completion message is sent: Vary on completed for device TAPMSD. Pressing the 'F1' key over the completion message will show this: Additional Message Information Message ID . . . . . . : CPC2605 Severity . . . . . . . : 00 Message type . . . . . : Completion Date sent . . . . . . : 02/03/07 Time sent . . . . . . : 12:30:17 Message . . . . : Vary on completed for device TAPMSD. Cause . . . . . : The vary configuration (VRYCFG) command was issued requesting that device TAPMSD be varied on. Technical description . . . . . . . . : The status of device TAPMSD may be VARY ON PENDING until it is contacted or a device failure occurs. |
| D. | Create the Tape Image Catalog that will be used to store the MSD. From the operating system command line, type the following: CRTIMGCLG IMGCLG(MSD) DIR('/MSD') TYPE(*TAP) CRTDIR(*YES) TEXT('Main Storage Dump (MSD) catalog') Press the Enter key. A completion message is sent: Image catalog MSD created in library QUSRSYS. Pressing the 'F1' key over the completion message will show this: Additional Message Information Message ID . . . . . . : CPCBC00 Severity . . . . . . . : 00 Message type . . . . . : Completion Date sent . . . . . . : 02/03/07 Time sent . . . . . . : 12:30:50 Message . . . . : Image catalog MSD created in library QUSRSYS. Note: If you receive the message "Image catalog MSD already exists in library QUSRSYS.", you should replace the parameters IMGCLG and DIR with another value of your choice. However, if you do that, remember that you will have to replace the parameters IMGCLG, DIR, STMF, OBJ, and CMD with the value you chose any time they are used in the rest of the document. |
| E. | Add a new Virtual Tape Image to the Tape Image Catalog. For this step, you will need to know the CSP case number (TSxxxxxxxxx). Using the correct values is a key piece in IBM's ability to automatically associate the data to your case, and ensure the fastest possible processing. From the operating system command line, type the following: ADDIMGCLGE IMGCLG(MSD) FROMFILE(*NEW) TOFILE('TSxxxxxxxxx.MSD001') IMGSIZ(1000000) ALCSTG(*MIN) VOLNAM(MSDTAP) ** The IMGSIZ of 1000000 MB is a maximum volume size, intended to prevent creating multiple virtual tape volumes. The image will only allocate as much space as needed, up to that maximum size. ** Press the Enter key. A completion message should be seen:
Pressing the 'F1' key over the completion message will show this: Additional Message Information Message ID . . . . . . : CPCBC28 Severity . . . . . . . : 00 Message type . . . . . : Completion Date sent . . . . . . : 02/03/07 Time sent . . . . . . : 12:31:34 Message . . . . : Image catalog entry added to image catalog MSD. |
| F. | Let us see how the Tape Image Catalog looks like. From the operating system command line, type the following command: WRKIMGCLGE IMGCLG(MSD) Press the Enter key. You will see something like this: Work with Image Catalog Entries System: XXXXXXXX Catalog . . : MSD Status . . . : Not ready Type . . . . : Tape Device . . . : Directory . : /MSD Type options, press Enter. 1=Add 2=Change 4=Remove 6=Mount 8=Load 9=Unload 10=Initialize volume 11=Display 13=Dump 14=Duplicate Write Opt Index Status Volume Name Density Type Protect *AVAIL 1 Loaded MSDTAP *VRT256K *SL No Press the Enter key. |
| G. | Load the Tape Image Catalog in the Virtual Tape Device. From the operating system command line, type the following: LODIMGCLG IMGCLG(MSD) DEV(TAPMSD) OPTION(*LOAD) Press the Enter key. A completion message is sent: Image catalog MSD loaded in device TAPMSD. Pressing the 'F1' key over the completion message will show this: Additional Message Information Message ID . . . . . . : CPCBC10 Severity . . . . . . . : 00 Message type . . . . . : Completion Date sent . . . . . . : 02/03/07 Time sent . . . . . . : 12:32:18 Message . . . . : Image catalog MSD loaded in device TAPMSD. |
| H. | Initialize the Virtual Tape Image. From the operating system command line, type the following: INZTAP DEV(TAPMSD) NEWVOL(MSDTAP) CHECK(*NO) Press the Enter key. A completion message is sent: Volume MSDTAP prepared for operation with owner ID *BLANK. Pressing the 'F1' key over the completion message will show this: Additional Message Information Message ID . . . . . . : CPC6771 Severity . . . . . . . : 00 Message type . . . . . : Completion Date sent . . . . . . : 02/03/07 Time sent . . . . . . : 12:32:45 Message . . . . : Volume MSDTAP prepared for operation with owner ID *BLANK. Cause . . . . . : The tape was successfully initialized for operation as a standard label volume. The volume is MSDTAP on device TAPMSD with code EBCDIC and density *VRT256K. |
| I. | Sign-On to SST. From the operating system command line, type the following: STRSST Press the Enter key. The 'Start Service Tools (STRSST) Sign On' screen is shown: Start Service Tools (STRSST) Sign On SYSTEM: XXXXXXXX Type choice, press Enter. Service tools user ID. . . . __________ Service tools password . . . |
| J. | Sign on with a service service tool user profile and password that has authority to Main storage dump manager tool. |
| K. | Select Option 1, Start a service tool, and press the Enter key. |
| L. | Select Option 6, Main storage dump manager, and press the Enter key. |
| M. | Select Option 2, Work with copies of main storage dumps, and press the Enter key. |
| N. | The 'Work with Copies of Main Storage Dumps' screen is shown: Work with Copies of Main Storage Dumps Type option, press Enter. 4=Delete 5=Display/Print 7=Rename 8=Copy to media Opt ID Date Level SRC Description _ 1 06/01/11 V7R1M0 A2D03000 MSD for Case TSxxxxxxxxx F3=Exit F9=Copy from media F11=Display copy status F12=Cancel |
| O. | Select the MSD you want to copy with '8' (Copy to media): Work with Copies of Main Storage Dumps Type option, press Enter. 4=Delete 5=Display/Print 7=Rename 8=Copy to media Opt ID Date Level SRC Description 8 1 06/01/11 V7R1M0 A2D03000 MSD for Case TSxxxxxxxxx F3=Exit F9=Copy from media F11=Display copy status F12=Cancel Press the Enter key. |
| P. | The 'Select Media Type' screen is shown: Note: If your System does not have an Optical Device, you will be directed to the 'Copy Main Storage Dump to Media' screen, as shown in Step 1R below. Select Media Type Select one of the following: 1. Tape 2. Optical |
| Q. | Select Option 1, Tape, and press the Enter key. |
| R. | The 'Copy Main Storage Dump to Media' screen is shown: Copy Main Storage Dump to Media Type choices, press Enter. Volume ID . . . . . . . . . . . . MSDTAP____ Sequence number . . . . . . . . . 0001 0000-9999 Check for active files . . . . . 1 1=Yes, 2=No |
| S. | Leave the default values as is and press the Enter key. The 'Select Tape Unit' screen is shown: Select Tape Unit Type choice, press Enter. Tape unit . . . . . . . __________ Name, F4 for list |
| T. | Type TAPMSD on the 'Tape unit' field: Select Tape Unit Type choice, press Enter. Tape unit . . . . . . . TAPMSD____ Name, F4 for list Press the Enter key. |
| U. | The 'Copy Main Storage Dump to Media Status' screen is shown. The percentage of the copy completed is shown as the copy progresses: Copy Main Storage Dump to Media Status From: Dump description . . . . : MSD for Case TSxxxxxxxxx To: Output device . . . . . : Tape 12% Complete Press F15 to cancel copy. Press F11 to return and continue copy. |
| V. | If the image needs to span multiple volumes, you would see the message ' Waiting for reply to message on message queue QSYSOPR.' per each additional volume needed. Given the 1 TB maximum size specified in the earlier steps, you should not encounter this issue. If you do need multiple volumes, an FTP transfer of a 1+ TB virtual tape image is likely to take significantly longer than sending a physical tape containing the MSD. |
| W. | When the message 'Copy completed normally' is issued, the MSD copy has finished: Work with Copies of Main Storage Dumps Type option, press Enter. 4=Delete 5=Display/Print 7=Rename 8=Copy to media Opt ID Date Level SRC Description _ 1 06/01/11 V7R1M0 A2D03000 MSD for Case TSxxxxxxxxx F3=Exit F9=Copy from media F11=Display copy status F12=Cancel Copy completed normally. |
| X. | Unload the Tape Image Catalog: LODIMGCLG IMGCLG(MSD) DEV(TAPMSD) OPTION(*UNLOAD) |
| Y. | Vary off the Virtual Tape Device. From the operating system command line, type the following: VRYCFG CFGOBJ(TAPMSD) CFGTYPE(*DEV) STATUS(*OFF) Press the Enter key. A completion message is sent: Vary off completed for device TAPMSD. Pressing the 'F1' key over the completion message will show this: Additional Message Information Message ID . . . . . . : CPC2606 Severity . . . . . . . : 00 Message type . . . . . : Completion Date sent . . . . . . : 02/03/07 Time sent . . . . . . : 16:00:17 Message . . . . : Vary off completed for device TAPMSD. Cause . . . . . : The vary configuration (VRYCFG) command was issued requesting that device TAPMSD be varied off. Technical description . . . . . . . . : If ASCVRYOFF(*YES) was specified on the VRYCFG command, the status of device TAPMSD will be VARY OFF PENDING until device take down is completed. If ASCVRYOFF(*NO) was specified on the VRYCFG command, device take down is complete and the status of device TAPMSD is VARIED OFF. |
| A. | List the contents of the MSD directory: WRKLNK '/MSD/*' Press the Enter Key. You will see something like this: Work with Object Links Directory . . . . : /MSD Type options, press Enter. 2=Edit 3=Copy 4=Remove 5=Display 7=Rename 8=Display attributes 11=Change current directory ... Opt Object link __ TSxxxxxxxxx.MSD001 |
| B. | Record the image file size to provide to IBM Support Take option 8 (Display Attributes), and page down once. Record the "Size of object data in bytes" value. This is the size of the image file. |
| C. |
Now, you are ready to start an FTP session to testcase or ECuRep and send in those files:
Note: You should choose the upload server that is closest to the location from where you are going to upload the MSD: Americas testcase.boulder.ibm.com (IP 170.225.15.31) Europe, Middle East and Africa ftp.ecurep.ibm.com (IP 192.109.81.7) Asia Pacific ftp.ap.ecurep.ibm.com (IP 210.143.141.69) ftp testcase.boulder.ibm.com (login with your transfer ID and password.) alternatively, FTP RMTSYS('170.225.15.31') NOTE: Refer to this URL for information to obtain an Transfer ID and password.
Create a transfer ID to upload data to IBM or ftp ftp.ecurep.ibm.com (login with your transfer ID and password) alternatively, FTP RMTSYS('192.109.81.7') NOTE: Refer to this URL for information to obtain an Transfer ID and password. Create a transfer ID to upload data to IBM or ftp ftp.ap.ecurep.ibm.com (login with your transfer ID and password.) alternatively, FTP RMTSYS('210.143.141.69') NOTE: Refer to this URL for information to obtain an Transfer ID and password.
Create a transfer ID to upload data to IBM namefmt 1 bin lcd /MSD cd /toibm/os400 mput TSxxxxxxxxx.MSD001 quit Note: Where TSxxxxxxxxx is the actual PMR, branch, and country number accordingly. |
| D. | Let your IBM Support representative know when the transfer has completed, and what the original image file size is from Step 2B. |
| E. | If you encounter trouble transferring the whole image file, you can use the native split command to break the image file into manageable pieces: You should try to determine how much data can be reliably transferred without interruption. For example, if you are able to get to approximately 2000 MB before the transfer fails, pick a split size of 1500 MB. Let's call this the split size, SSSS, which is a whole number of Megabytes (no decimal places). The 'split' command has the limitation of only being able to split into a maximum of 676 pieces ('aa' through 'zz'). Needing to split into that many pieces is a good indication that it would likely be faster to send a copy of the MSD on physical tape instead (refer to Rochester Support Center knowledgebase document Copy MSSD and LIC Logs to Tape at SST - RISC) To determine how many split pieces you will create, divide the original image file size from Step 2B by 1048576 (1 MB), and then divide that by the split size (SSSS) , and add 1. If this number is greater than 676.0, you cannot split the image, and the MSD needs to be sent on physical tape media (refer to Rochester Support Center knowledgebase document Copy MSSD and LIC Logs to Tape at SST - RISC). You can perform the split command through PASE ('call qp2term'). QSHELL is 32 bit-based and has file size limitations: SBMJOB CMD(CALL PGM(QP2SHELL) PARM('/QOpenSys/usr/bin/-sh' '-c' 'split -b SSSSm /MSD/TSxxxxxxxxx.MSD001 /MSD/TSxxxxxxxxx.MSD001_')) JOB(SPLIT_MSD) JOBQ(QSYSNOMAX) Once this completes, you need to record a few pieces of information for IBM Support to ensure proper joining of the files. i) Record the first split file name, and size in bytes. ii) Record the last split file name, and size in bytes. This will tell IBM Support the exact split size (size of first file), how many files to expect (name of last file), and the size of the last split piece which is likely less than the split size. Once the transfer is complete, you should relay the original file size, the first split file name and its size in bytes, the last split file name and its size in bytes. |
Important Note: These instructions will get rid of everything created to save the MSD to virtual tape.
*** Do not perform these cleanup instructions until Support has verified the data is valid. ***
| 1. | Delete the Tape Image Catalog: DLTIMGCLG IMGCLG(MSD) KEEP(*NO) |
| 2. | Delete the Image Catalog Directory: Note: If you are running IBM i V6R1 or newer, skip to Step 3. QSH CMD('rm -r /MSD') |
| 3. | Delete the Virtual Tape Device: DLTDEVD DEVD(TAPMSD) |
Note: Once this procedure has been completed, the IBM Support Center representative will need to complete the copy of the MSD from Virtual Tape to the Main Storage Dump Manager for MSD analysis to begin.
[{"Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m3p000000PCSOAA4","label":"Internal LIC and Partitions-\u003EDisk"}],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.3.0;7.4.0;7.5.0","Type":"MASTER"}]
Historical Number
500836904
Was this topic helpful?
Document Information
Modified date:
10 December 2024
UID
nas8N1018687