It definitely could be the issue. If a VSAM dataset is compressed with Datapacker, the only way it can be read is with Datapacker. The compression algorithms are different from DFSMS compression.
> We are z/OS 2.1 and our customer is z/OS 1.11. Below is the description of > our situation. > > We are receiving customer VSAM data sets that have been dumped by > DF/DSS (dump by data set), the DF/DSS dump data set is tersed, and then > SFTP'ed (binary mode) to our SFTP server. When I reverse the process, and > look at the restored VSAM data sets, the key field is correct, but the data > portion is garbled. The customer knows that the Datapacker product for the > IMS is in use, but doesn't know if that is true for VSAM data sets. > > I've asked the customer to provide me with an IDCAMS PRINT DUMP of the > first 50 records. The keys in the customer's IDCAMS PRINT match the keys as > displayed by IBM's File Manager Data Set View function and an IDCAMS > PRINT DUMP on our system. > > Is the lack of Datapacker for VSAM, on our system, a possible reason for this? > > ************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
