That does not work. Devices and media are not bound to another at all.
This is logical for tapes as you should be able to use it in any device. But it is also true for disk media. And this makes sense.
You could even move the whole contents to another device path and use it here.
To my knowledge, wizard will offer also steps of labeling so I do not understand why do you label it if you used wizard? Anyway, using wizard, create new device (make sure unsuccessful references of previous attempts are gone - device and volume wise) and create new one. You may wish to create screenshot for each step in case you hit trouble and wish to share your path here. Another thing is that you may wish to check with your support to do it with you over webex and then you can see it how it is done and what exactly is done different from what you did - it might be a bit faster resolution wise.
So as a way of test i created a device called testfscl. I created a device pool called testfscl.
it created this device.
I then created another device using the testfscl device pool and it does not allow you to label it at all when creating it.NOTE no volume name.
Now when i go to label it it wants to relabel volume testfscl.001 to testfscl.002.
i am trying to understand how they were able to create these two devices as i need to create a third one. But i am exhibiting the same issues as above with these. I would like to know how these two device are in the same device pool yet have different volume names.
I can't see why you can't label device so key to what you experience must be in part "I created device". How exactly did you create device and what settings did you use while doing that?
Once again - a device is not tight to any pool at all.
Only in case you label it you must assign the media to a pool.
I am not using the wizard - i am using the context menu (aka right click menu).
I recommend you to do that as well as you will understand the process better.
So create the device without labeling it, then select the device and open the menu.
Now NW tries to find and read a valid label first.
If found, it will display the label found.
Next you must first select the pool (unfortunately, you find it below the label - that confuses users who think they must work top down).
This triggers NW to use the next free label according to the label emplate.
You can now modify the label (you must not even follow the template at all) and then click o.k. to start the job.
However, if you first modify the label an then select the pool, NW will just override your label and propose the next available one from the 'new' pool.
Ida, given that OP does not have experience and can only make mistake if access path for DD devices is not set correctly, let him use wizard. I suspect he might have done that before and used same access path for two different devices.