Hi Marcel,
I have been looking at how imagelister handles AETITLE and was wondering if my logic is correct.
./dgate --imagelister:"local|0009703828|1.3.46.670589.5.2.10.2156913941.892665339.860724||"
produces
./data/HEAD_EXP_00097038/0001_002000_892665661.v2*./data/HEAD_EXP_00097038/0001_003000_892665662.v2
but
./dgate --imagelister:"CONQUESTSRV1|0009703828|1.3.46.670589.5.2.10.2156913941.892665339.860724||"
produces
./data/*./data/
with this message in the logs
Locating file:
***Located file on wrong device:MAG0 instead of
Locating file:
***Located file on wrong device:MAG0 instead of
The reason local works is that --imagelister calls ImageFileLister which calls QueryOnImag. The filename and device strings are then returned in the private tags 0x9999, 0x0800 and 0x9999, 0x0801.
The reason CONQUESTSRV1 does not work is that --imagelister calls ImageFileLister which calls VirtualQuery. VirtualQuery calls QueryOnImag which returns the same values, but then calls VerifyIsInDBE which removes fields that are not defined in the image database thereby removing both device and filename and causing the failure further on in ImageFileLister when FindPhysicalDevice is called.
If this is correct do you think it is possible to not filter out the private dgate tags or would this cause other problems?