CBR3861I Import operation for logical list volume volser in library library-name completed with exceptions or errors. Requested: requested-number Importable: importable-number Imported: imported-number Stacked volumes: stacked-number MBytes Imported: MBytes-imported MBytes Moved: MBytes-moved
Explanation
- Requested
- requested-number is the total number of stacked volumes found in the import list dataset. However, if the import list dataset contains a record that either has an invalid physical or logical volser or invalid syntax, it is not included in the count.
- Importable
- importable-number is the number of logical volumes found or requested in this library to import. This count includes the logical volumes explicitly listed in the import list data set and the logical volumes contained on a stacked if only the stacked volume is specified.
- Imported
- imported-number is the number of logical volumes successfully imported into this library.
- Stacked volumes
- stacked-number is the number of stacked volumes processed in this import operation. For a volume to be included in this count, it must have been specified in the import list data set and reside in the library.
- MBytes Imported
- MBytes-imported is the amount of data imported during this operation. Only the logical volumes that were successfully imported are included in this count. The amount reported is an integral multiple of 1,048,576 bytes (1 MB). Logical volumes imported that contain less than 1 MB are rounded up to 1 MB before being added to the count.
- MBytes Moved
- Mbytes-moved is the amount of data that was moved from one stacked volume to another as part of the import process. For the enhanced import support, this includes only the data for the logical volumes that had to be moved off of the physical volumes being imported for a selective-import. The amount reported is an integral multiple of 1,048,576 bytes (1 MB). Logical volumes imported that contain less than 1 MB are rounded up to 1 MB before being added to the count.
If the import operation did not complete due to being canceled or because of an error which caused the operation to end abruptly, another CBRxxxxI message accompanies this message with an explanation of what occurred.
Check the status file on the logical list volume volser for the disposition of the logical volumes that were not successfully imported to determine the error incurred. .
System action
OAM processing continues.
Operator response
If not already released, the stacked volumes used in the import process can be released at the library manager.
System programmer response
For a history of the import operation, the import list volume status file (file sequence 2) can be read. This file is updated by the library to indicate the success or failure of each logical volume in the list. Refer to message CBR3610I for a list of the logical volumes that were successfully imported/entered into the library, if any. If complete the import operation, restart the import operation after the problems have been resolved.
Source
Object Access Method (OAM)
Routing Code
2,3,5
Descriptor Code
4