Venkat, there are 2 possible methods for dataset allocation (SMS versus VATLST/EDT). Since you said your other system does not have storage volumes, then that system is must be using SMS. otherwise you would see these errors there.
If you don't want to use SMS, then you will need to configure EDT and VATLST. EDT has the unit names that can be specified and which volumes are eligible for the allocation. VATLST allows you to omit VOL=SER on DD's but only to volumes not defined as private. New datasets allocated that have a DSN without a volser will first try public volumes and if no space is available will allocate to storage. New datasets allocated without a DSN (or with DSN=&&xxx) will only allocate to storage volumes. As a side note If you are sharing disks with your other systems, then you should also ensure that you don't violate disk integrity. Jon Perryman On Monday, May 5, 2014 2:15 PM, Ed Gould <[email protected]> wrote: It orked in the past. >TSO *NEEDS* one storage volume. > >On May 5, 2014, at 10:37 AM, venkat kulkarni wrote: > >> No, I dont think adding at least 1 volumes marked as storage will make >> difference, because in our other system as well, we have defined only >> PRIVATE all working fine. But still suggest, if I really need to >> make any >> changes to solve this issue. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
