It was pointed out earlier that creating a 'dummy enqueue' for serialization can be accomplished without actually specifying a data set name at all. I haven't tried that but won't contest it--as long as serialization is required only in a single task. But there is one very 'logical' place for a similar strategy. Some ancient and venerable MVS utilities require, for certain functions, that a *volume* be allocated separately from the function itself. In batch, one can code something like this:
//MYVOL DD DISP=OLD,VOL=SER=xxxxxx That does not work in TSO. The command 'alloc dd(myvol) old vol(xxxxxx)' gets the prompt 'IKJ56700A ENTER DATA SET NAME -'. I have used a zero-space data set (NEW) for this purpose. It works quite well. . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: "R.S." <r.skoru...@bremultibank.com.pl> To: IBM-MAIN@LISTSERV.UA.EDU Date: 08/27/2012 03:35 PM Subject: Re: Space Allocation In Bytes Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> W dniu 2012-08-25 17:49, Skip Robinson pisze: > Zero space allocation is perfectly valid. Valid, but illogical. Data set with zero size is illogical. > As is SPACE (0,1) also. The > result is just as requested. In either case, the data set exists in the > VTOC but takes up no space on disk. The data set is treated as 'real', > including GRS enqueue. Hence it can be used like any other exclusively > held data set to serialize execution. That's exploitation of "side effect". Stilla valid (it works, so it is valid), but it's still illogical. -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
