>Let me point out two possible security risks.
>Assume that the real file name is 44 characters long and that is the way
>it is held in the VTOC.
>Now, let's assume that you do not have permission to that file. BUT, you
>know that if you build a "long name" that uses your userid as the HLQ
>and p
The BCS itself is just another KSDS. The code directly accessing the BCS
limits itself to using 45-byte keys. That is obviously part of what would
have to change. The 45-byte catalog key (44 for DSN and 1 to indicate an
extension record) is not dictated by some universal law. It is merely a
number
Try using ATTACH. Have your main program allocate the SYSTSPRT file first,
then attach a routine that performs both calls before returning. IIRC when
the attached TCB is detached, the open files associated with it will be
closed. Then the main routine can free the file and repeat the process ad
nau
>Are you now saying that you want to use the same set of target volumes for
>Z\os AND Z\VM source volumes?
Yes, and z/VM guest volumes as well.
I could potentially bring up a z/OS guest under z/VM and want to share the
DASD with other z/OS systems. Although that is not our current intent, it
sho
4 matches
Mail list logo
