home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!uwm.edu!psuvax1!psuvm!wvnvm!bryan
- Date: Sat, 21 Nov 1992 18:41:07 EST
- From: Jerry Bryan <BRYAN@wvnvm.wvnet.edu>
- Message-ID: <92326.184107BRYAN@wvnvm.wvnet.edu>
- Newsgroups: bit.listserv.ibm-main
- Subject: Re: IEFBR14
- References: <IBM-MAIN%92112020533595@RICEVM1.RICE.EDU>
- Lines: 24
-
-
- In article <IBM-MAIN%92112020533595@RICEVM1.RICE.EDU>, Leonard D Woren
- <LDW@USCMVSA.BITNET> says:
- >
- >On Fri, 20 Nov 1992 10:18:54 PST,
- > "Mark C. Lawrence" <M.Lawrence@STANFORD.BITNET> said:
- >> (lots of detailed explanation deleted)
- >> Now, suppose that you specified UNIT and VOL on the DD statement. Since
- >> volume information is available, MOD is treated (for allocation/disposition
- >> purposes) like OLD.
- >
- >Interesting. I'm glad I tested this before replying. I was going to
- >claim that this was incorrect, but now I think that MVS is just
- >broken. I got interesting results from the tests. In both batch and
- >TSO, with or without a SPACE specification, it cataloged the dataset
- >WITHOUT CREATING IT when MOD,CATLG was used for a non-existant dataset
- >and a specific volume was coded.
- >
-
- I am not sure why you consider this behavior of MVS to be broken.
- It is exactly what would happen if you said (OLD,CATLG) and did not
- open the data set, for example by running IEFBR14.
-
-
-