Previous Topic: VMBSCAN Utility MessagesNext Topic: Abends


VMBTCPY Utility Messages

0001R

IS volser MOUNTED ON vaddr THE VOLUME YOU WANT TO {COPY | SCAN}? RESPOND YES OR NO:

Reason:

The indicated volume is mounted at virtual address vaddr and ready to be copied or scanned. VMBTCPY waits for you to respond.

Action:

If you want to copy or scan this volume, enter YES. To exit VMBTCPY, enter NO.

0003I

THE TARGET VOLUME MOUNTED ON vaddr HAS A VALID STANDARD LABEL OF volser.

Reason:

The volume mounted on the indicated drive has a valid standard label. If VMBTCPY overwrites this volume with the source tape, the contents of the target volume mounted on virtual address vaddr will be erased. VMBTCPY sends message 0004R.

Action:

None.

0004R

DO YOU WANT TO CONTINUE AND OVERWRITE THE TARGET VOLUME MOUNTED ON vaddr? RESPOND YES OR NO:

Reason:

This message follows message 0003I. VMBTCPY issues this message to make sure you really want to copy the source tape over the volume mounted on virtual address vaddr and erase the target tape's existing contents. VMBTCPY waits for you to respond.

Action:

If you want to copy the source tape over the indicated target volume, enter YES. To exit VMBTCPY, enter NO.

0005I

BEGINNING TO { COPY | SCAN } TAPE volser.

Reason:

VMBTCPY is starting to copy or scan the indicated tape. This may take some time; VMBTCPY issues a message, either 0007I or 0008I, when it finishes copying or scanning each tape volume. Processing continues.

Action:

None.

0006I

ENDING THE TEST RUN WITH NO ERRORS.

Reason:

The TEST option ran with no errors.

Action:

None.

0007I

VOLUME volser HAS BEEN SUCCESSFULLY {COPIED | SCANNED}.

Reason:

VMBTCPY successfully copied or scanned the indicated volume and encountered no errors during the copy or scan phase. VMBTCPY sends this message when the tape contains only one data set. Processing continues.

Action:

None.

0008I

number DATASETS ON VOLUME volser HAVE BEEN SUCCESSFULLY { COPIED | SCANNED }.

Reason:

VMBTCPY successfully copied or scanned the indicated volume and encountered no errors during the copy or scan phase. VMBTCPY sends this message when the tape contains multiple data sets. Processing continues.

Action:

None.

0009I

VMBTCPY HAS ENDED.

Reason:

VMBTCPY ended normally with no errors.

Action:

None.

0011I

VMBTCPY HAS BEEN TERMINATED.

Reason:

VMBTCPY ended prematurely because you entered a NO response to either message 0001R or 0004R.

Action:

If you replied NO to message 0001R, mount the correct source tape. If you replied NO to message 0004R, mount the correct target tape. After mounting the correct tape, start VMBTCPY again.

0012R

ENTER THE DENSITY OF THE INPUT VOLUME volser AT VIRTUAL ADDRESS vaddr.

Reason:

VMBTCPY encountered an invalid HDR2 tape label. Because you specified the NOVAL option, VMBTCPY does not end and copying continues. Because VMBTCPY normally obtains the density of the input tape from a field in the HDR2, you must provide the volser's density. VMBTCPY issues message 0013I.

Action:

Enter one of the valid densities specified in message 0013I.

0013I

VALID DENSITIES ARE: 800, 1600, 6250, 38K, XF, E, EXF, ENH, and EXF.

Reason:

This message, which follows message 0012R, lists the valid densities for input tapes.

Action:

None. See message 0012R.

0021E

YOU MUST SPECIFY THE VIRTUAL ADDRESS OF THE TARGET TAPE DRIVE.

Reason:

You did not specify the target tape drive's virtual address (the second parameter) on the command line.

Action:

Enter the virtual address for the target tape drive and start VMBTCPY again. If you need assistance with the VMBTCPY command format or its options, enter VMBTCPY ? for help.

0022E

PARAMETER parameter SPECIFIED AFTER vaddr IS EXTRANEOUS.

Reason:

You specified an extra parameter after the target tape drive virtual address. A maximum of two parameters are allowed on the command line.

Action:

Delete the extraneous parameter and start VMBTCPY again. If you need assistance with the VMBTCPY command format or its options, enter VMBTCPY ? for help.

0023E

THE VIRTUAL ADDRESS OF THE TARGET TAPE DRIVE MUST BE DIFFERENT FROM THE VIRTUAL ADDRESS OF THE SOURCE TAPE DRIVE.

Reason:

You specified the same virtual address on the command line for both the source and target tape drives.

Action:

Specify a virtual address for the source tape drive that is not the same as the virtual address entered for the target tape drive (or vice versa) and start VMBTCPY again.

0024E

vaddr IS NOT A VALID CMS VIRTUAL ADDRESS FOR A TAPE DRIVE.

Reason:

The indicated virtual address is not a valid address for a tape drive. The virtual address must be in the range 180-187 or 288-28F.

Action:

Specify a valid virtual address and start VMBTCPY again.

0025E

THERE IS NO DEVICE ATTACHED AT VIRTUAL ADDRESS vaddr.

Reason:

No device is attached at the indicated address. You may have mistyped the virtual address.

Action:

Either correct the address specified or attach a tape drive at virtual address vaddr. Start VMBTCPY again.

0026E

THE DEVICE ATTACHED AT VIRTUAL ADDRESS vaddr IS NOT A TAPE DRIVE.

Reason:

The device attached at the indicated virtual address is not a tape drive. You may have mistyped the virtual address.

Action:

Either correct the address or attach a tape drive at the indicated virtual address. Start VMBTCPY again.

0027E

THE TAPE DRIVE AT VIRTUAL ADDRESS vaddr IS NOT READY. RESTART VMBTCPY WHEN THE TAPE IS READY.

Reason:

This tape drive has not been readied.

Action:

Mount the tape you want, ready the tape drive, and start VMBTCPY again.

0028E

INVALID OPTION option.

Reason:

You specified an invalid option on the command line.

Action:

Correct the command line format and start VMBTCPY again. If you need assistance with the VMBTCPY command format or its options, enter VMBTCPY ? for help.

0029E

OPTION option WAS SPECIFIED MORE THAN ONCE.

Reason:

You specified the indicated option more than once on the command line. An option can be listed only once.

Action:

Delete the duplicate options and start VMBTCPY again. If you need assistance with the VMBTCPY command format or its options, enter VMBTCPY ? for help.

0031E

THE TARGET TAPE DRIVE AT VIRTUAL ADDRESS vaddr DOES NOT SUPPORT THE DENSITY density.

Reason:

The target tape drive does not support the density of the input tape.

Action:

Attach a target tape drive that supports the indicated density.

0032E

THE INPUT VOLUME volser WAS WRITTEN WITH IMPROVED DATA RECORDING CAPABILITY (IDRC).

Reason:

The source volume was written using IDRC. VMBTCPY sends message 0033E to provide additional information.

Action:

None. See message 0033E.

0034E

THE TARGET TAPE DRIVE AT VIRTUAL ADDRESS vaddr DOES NOT SUPPORT IMPROVED DATA RECORDING CAPABILITY (IDRC).

Reason:

The indicated tape drive does not support the IDRC feature.

Action:

Attach a drive at virtual address vaddr that supports IDRC and start VMBTCPY again.

0041E

VMBTCPY REQUIRES THE USE OF RXTAPIO MODULE.

Reason:

VMBTCPY could not find RXTAPIO MODULE on any accessed disk.

Action:

Access a disk that has a copy of RXTAPIO MODULE. This MODULE is part of the CA VM:Backup program material and is on the CA VM:Backup distribution tape.

0042E

THE DISK OPTION REQUIRES A READ/WRITE A-DISK.

Reason:

VMBTCPY requires a read/write A-disk to use the DISK option.

Action:

Link and access your A-disk in read/write mode and start VMBTCPY again.

0051E

THE SOURCE TAPE AT VIRTUAL ADDRESS vaddr DOES NOT HAVE A VALID labeltype LABEL.

Reason:

VMBTCPY encountered an invalid CA VM:Backup header label on the tape at virtual address vaddr.

Action:

Make sure the tape at the indicated virtual address was written by CA VM:Backup. If necessary, your CA VM:Backup system administrator can contact Technical Support. When the problem is corrected, start VMBTCPY again.

0052E

THE SOURCE TAPE AT VIRTUAL ADDRESS vaddr HAS TWO VOL1 LABELS THAT ARE NOT DUPLICATES.

Reason:

VMBTCPY found two different VOL1 labels at the beginning of the tape at the indicated virtual address.

Action:

Make sure this tape was written by CA VM:Backup. If necessary, your CA VM:Backup system administrator can contact Technical Support.

0053E

THE SOURCE TAPE AT VIRTUAL ADDRESS vaddr HAS TWO DUPLICATE VOL1 LABELS.

Reason:

VMBTCPY found the same VOL1 label two times on the tape at the indicated virtual address. If you specified the FIX option with VMBTCPY, the utility will correct this problem and continue copying the tape. If you did not specify the FIX option, one of the following will occur:

0061E

TAPE AT VIRTUAL ADDRESS vaddr IS NOT WRITE-ENABLED.

Reason:

The output tape on this target virtual address is not capable of write operations.

Action:

Remount the tape with a write ring and start VMBTCPY again.

0062E

TAPE AT VIRTUAL ADDRESS vaddr IS TOO SHORT TO COMPLETE THE COPY.

Reason:

The output tape at this virtual address is not long enough to hold all the data being copied from the source tape. The target tape must be at least as long as the source tape.

Action:

Use a target tape that is at least as long as the source tape and start VMBTCPY again.

0063E

ERROR COPYING TAPE volser. A NULL TRAILER LABEL WAS ENCOUNTERED AFTER number TAPE FILES.

Reason:

VMBTCPY unexpectedly encountered a NULL tape file instead of the trailer labels.

Action:

Make sure the tape at the indicated virtual address was written by CA VM:Backup. The CA VM:Backup system administrator can contact Technical Support. When the problem is corrected, start VMBTCPY again.

0064E

number TAPE FILES WERE COPIED FROM VOLUME volser. THIS IS AN INVALID NUMBER FOR A VM:BACKUP TAPE.

Reason:

VMBTCPY copied an invalid number of tape files from the source tape.

Action:

Make sure the indicated volume was written by CA VM:Backup. The CA VM:Backup system administrator can contact Technical Support. When the problem is corrected, start VMBTCPY again.

0065I

LOGICAL END-OF-TAPE HAS BEEN REACHED ON THE TARGET DRIVE vaddr. COPYING WILL CONTINUE UNTIL PHYSICAL END-OF-TAPE.

Reason:

VMBTCPY has reached the logical end-of-tape for the tape mounted on the target tape drive at virtual address vaddr. VMBTCPY continues copying the input tape until the physical end-of-tape is reached.

Action:

None, if the target tape is long enough to hold all of the data being copied from the input tape. Otherwise, use a target tape that is longer than the input tape. You may receive VMBTCPY message 0062E if the target tape is shorter than the input tape.

0091W

I/O ERROR OCCURRED WHILE WRITING VMBTCPY REPORT A; RETURN CODE = code.

Reason:

An error occurred writing the output messages to VMBTCPY. The return code from EXECIO is code. If the return code is 113, the A-disk is full. Disk output is suspended but execution continues.

Action:

If the A-disk is full (return code = 113), clear some space on the disk. If EXECIO issues a return code other than 113, see the IBM documentation on the CMS EXECIO command for an explanation of the return code and correct the problem. Start VMBTCPY again.

0092E

INVALID RESPONSE: response

Reason:

You replied to message 0001R or 0004R with an invalid response. Valid responses are either YES or NO.

Action:

Enter the appropriate valid response, either YES or NO.

0093E

ERROR DURING operation; RETURN CODE = code.

Reason:

An error occurred during the indicated operation. The return code indicates the cause of the problem.

Action:

If the operation is a CMS command, see the IBM documentation for the command for an explanation of the return code. Correct the problem and start VMBTCPY again. If the operation is not a CMS command, your CA VM:Backup system administrator must contact Technical Support.

0096W

DUPLICATE FOUND: TAPE RECORD recnum, VM:BACKUP BLOCK blknum.

Reason:

VMBTCPY found a duplicate tape record on the input volume. If you specified the DUPFIX option with VMBTCPY, the utility corrects this problem and continues copying the tape. If you specified the DUPSCAN option with VMBTCPY, the utility reports this condition and continues processing.

Action:

None.

0098W

RECORDS MISSING BETWEEN REC recnum1 BLK blknum1 AND REC recnum2 BLK blknum2.

Reason:

VMBTCPY determined that tape records between the indicated values are missing.

Action:

Your CA VM:Backup system administrator must contact Technical Support.

0099E

INTERNAL ERROR 99: INVALID MESSAGE NUMBER number.

Reason:

An internal error occurred in the VMBTCPY message handler.

Action:

Your CA VM:Backup system administrator must contact Technical Support.