[Info-vax] SHO DEV xxx/FILE on LD devices

[Jan-Erik Soderholm]

Johnny Billquist wrote 2011-07-05 14:14:
> On 2011-07-05 13.44, Jan-Erik Soderholm wrote:
>> Hi.
>> Can someone tell why the below happens.
>>
>>
>> $ dism/abo $1$lda1:
>> %DISM-W-CANNOTDMT, $1$LDA1: cannot be dismounted
>> %DISM-W-INSTIMAGE, 2 images installed on volume
>>
>> $ sh dev $1$lda1:/file
>>
>> Files accessed on device $1$LDA1: (OSSBY1) on 5-JUL-2011 13:29:49.84
>>
>> Process name PID File name
>> 00000000 [000000]INDEXF.SYS;1
>> $
>>
>>
>> I can see the images using INSTALL LIST :
>>
>> DISK$JFPLIB0004A:<LIBBZ2>.EXE
>> libbz2shr32-1_0_4;1
>>
>> DISK$JFPLIB0004A:<LIBZ>.EXE
>> LIBZSHR32-1_2_3_EV56;1
>>
>> $ sh log DISK$JFPLIB0004A
>> "DISK$JFPLIB0004A" = "$1$LDA1:" (LNM$SYSTEM_TABLE)
>> $
>>
>>
>> On the other LD drive I can see the installed files :
>>
>>
>> $ dism/abo $1$lda2:
>> %DISM-W-CANNOTDMT, $1$LDA2: cannot be dismounted
>> %DISM-W-INSTIMAGE, 3 images installed on volume
>> $
>>
>> $ sh dev $1$lda2:/file
>>
>> Files accessed on device $1$LDA2: (OSSBY1) on 5-JUL-2011 13:36:14.60
>>
>> Process name PID File name
>> 00000000 [000000]INDEXF.SYS;1
>> 00000000 [python254.vms.lib]PYTHON_LIBCRYPTO_SHR32.EXE;1
>> 00000000 [python254.vms.lib]PYTHON_LIBSSL_SHR32.EXE;1
>> 00000000 [python254.vms.lib]pythonshr.exe;2
>>
>>
>> The same files are visible with INSTALL LIST :
>>
>> DISK$JFPPY0021A:<PYTHON254.VMS.LIB>.EXE
>> pythonshr;2 Open Hdr Shared Lnkbl
>> PYTHON_LIBCRYPTO_SHR32;1
>> Open Hdr Shared Lnkbl
>> PYTHON_LIBSSL_SHR32;1
>> Open Hdr Shared Lnkbl
>>
>> $ sh log DISK$JFPPY0021A
>> "DISK$JFPPY0021A" = "$1$LDA2:" (LNM$SYSTEM_TABLE)
>> $
>>
>>
>> I do not understand why SHO DEV xxx/FILE shows different
>> results for these two LD drives...
>
> Open is not the same as installed. A file can be installed without being
> open. However, an installed file can also be open.
> So, on the first disk, you have images that are installed, but not open,
> while on the second disk you have images that are installed *and* open.
> Someone running python on your system, perhaps? :-)
>
> Johnny
>

Yes, me. :-) Nice tool b.t.w.

But OK, I thought it might have something with "known" vs. "open"
to do. I was fiddling with the shutdown routines so that my shadow
sets shouldn't go into a "merge" each reboot. Seems to be OK by now...

Thanks!

Jan-Erik.