Doug,
Probably the easiest way is to make the dasd volume where your source dataset resides online to VM/370.? Assign a real device address for the volume to be one recognized already by CP for that device type.? The MVS dasd addresses are usually already defined to VM in most of the Sixpack and VM/CE distributions, so you? can likely use the same device address that was used in MVS itself for that particular volume.
After you bring up VM with the dasd in question, attach that dasd to your userid.? To make the explanation simpler, lets make some assumptions:
dasd volume = 14C? 3350? VOL=SER=MYPACK
Dataset you want:?? MY.SOURCE.LIB(COBOL5)? attributes:? 3120/80/FB
So assuming you brought the dasd online to VM at address 14C, then:
cp attach 14c to userid
ACC 14C J
FILEDEF? IN? DISK X X J DSN MY SOURCE LIB (MEMBER COBOL5 BLKSIZE 3120 LRECL 80 RECFM FB
FILEDEF OUT COBOL5 COBOL A
MOVE IN OUT
Thats it.? The file should be on your A-disk.? Rinse and repeat for any other members by respecifying the FILEDEF IN again with a different member name, then MOVE IN OUT, as many times as needed.? This can be put into an EXEC also, of course.
Notes:? You need to know the dataset attributes and put them on the filedef command.? CMS will not? attributes from the VTOC on the volume.? There are no 'dots' (qualifier separators) in the DSNAME in the filedef command.? Separate the qualifiers with a blank.? Use a dummy filename and filetype on the IN filedef; you must use the filemode letter of the drive you accessed though.
Regards,
Bob
