While DFSMShsm was writing the primary copy of a data set during a recall or recovery operation, an I/O error occurred or invalid data was found. If an I/O error occurred an access method or hardware error message should precede this message or be found in the DFSMShsm job log SYSMSG data set.
The recall or recovery operation ends. DFSMShsm processing continues.
If reascode in message ARC1001I is 0, 12, or 16, respond to the associated access method or hardware error message. If reascode in message ARC1001I is 4, DFSMShsm did not correctly allocate the space required for the data set. If reascode in message ARC1001I is 8, data records from a track of the source device (the original primary volume) will not fit on a track of the target device. This may be the result of the source device track length being larger than the target device track length. Another cause may be the result of hardware architecture. For example, at small block sizes (less than 256), more records will fit on a 3380 track than will fit on a 3390 track. This is true even though the maximum track capacity of a 3390 is greater than a 3380. At a blocksize of 80, the 3380 track will hold 83 records while only 78 records will fit on a 3390 track. Therefore, if such a data set is migrated from a 3380, then you need to recall the data set back to a 3380. Or, if the data is to be accessible by relative block addressing, then another option is to recall the data set to a 3390 using the DAOPTION(RELBLK) option. If reascode in message ARC1001I is 10, the data set may have an invalid count key data field.
DFSMShsm