zimport creates DSD with garbage in "STORAGE CLASS" field
Hi,
When I run zimport, it creates DSDs, and fills in the DSD fields with the characteristics of the datasets referenced during the import.
The "STORAGE CLASS" field is being filled in with the correct storage class, but it is prefixed with a garbage (binary) character.
Has anyone else seen this before? Has anyone else reported this as a bug?
Is there a work around?
It prevents loading the files back into a workspace.
Frank
When I run zimport, it creates DSDs, and fills in the DSD fields with the characteristics of the datasets referenced during the import.
The "STORAGE CLASS" field is being filled in with the correct storage class, but it is prefixed with a garbage (binary) character.
Has anyone else seen this before? Has anyone else reported this as a bug?
Is there a work around?
It prevents loading the files back into a workspace.
Frank
One answer
Hi Frank,
This was seen before in bug 185660, but we've not been able to reproduce the behavior to figure out why it's happening. I'd encourage you to chime in on that work item -- every new data point we have will help in the investigation.
In the meantime, you should be able to edit the DSD in the Eclipse client to remove the extraneous leading character.
This was seen before in bug 185660, but we've not been able to reproduce the behavior to figure out why it's happening. I'd encourage you to chime in on that work item -- every new data point we have will help in the investigation.
In the meantime, you should be able to edit the DSD in the Eclipse client to remove the extraneous leading character.