IBM Storage The online community where IBM Storage users meet, share, discuss, and learn. Join the Community
We have recently started testing HSM migrates and have been issuing some manual migrates. At this time we have 116 objects and it appears there are 2 containers with the following SYSZARC.ARCPLEXT.MIG.2023093.xxxxxxxx, but both containers appear to be empty. According to the redbook in order to list the prefix of the objects you have to include the cloud name and container, so I'm trying to understand why these objects are not going to the containers. I even tried an hsend migrate with the cloud name and container name but nothing happened. I'm thinking it's because we are doing this testing manually and do not have it setup in the parms yet.
I was able to display the cloud and one container and found that it had some prefixes in it. Although I can't equate the number of objects to the number of prefixes, but assume that each prefix contains several objects. In the MI for the 7700 however when I look at the the cloud and drill down to the container I see nothing in objects as far as objects. It's not 0 but it's just blank, and as far as space it 0 GB. I'm thinking it has to show at least 1 GB before it shows anything but don't know.
Hi John, This is a known issue and the TS7700 development team has a defect open for this. Lourie
Hi John,I recommend using the Host commands to view the containers and objects. The HSM LIST CLOUD(cloud_name) will list all of the containers in the specified cloud. Then issue the LIST CLOUD(cloud_name) CONTAINTER(container_name) to list all of the object prefixes in a container. You can then issue LIST CLOUD(...) CONTAINTER(...) OBJECT(obj_prefix) to list all of the objects with that prefix. Note that with HSM, the containers are managed entirely within HSM. You cannot direct a migration to a particular container, only to a particular cloud. The HSM AUDIT of a Cloud will do a bi-directional verification of the HSM CDS records and the objects in a cloud.
Yes that's what we saw, although we can't explain why when we tried those commands on the previous day we didn't see anything, perhaps we where trying to list the wrong container. Can you tell me are you able to use wildcard characters? I'm asking because at the time we had two containers with 2023093.xxxxxxxx and I was trying to do a list stopping at the 2023093. Now we only have one container so secondary space management must have cleaned up the empty container.
Senior Systems Management Analyst – zSeries Storage Delivery
11000 Optum Circle MN102
Eden Prairie, MN 55344
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or intended recipient's authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
They take fully-qualified names. A fully-qualified container name is required because only the contents of a single container will be listed.Makes sense that SSM would have cleaned up the empty container.