Page 2 of 2

Re: Difference between KEEP and CATLOG

PostPosted: Fri Jun 01, 2012 9:21 pm
by dick scherrer
Hello,

IMHO, no application process should EVER specify (NEW, KEEP). I know SMS will "forgive" you and catalog the dataset anyway, but i believe the better practice is to specify (NEW,CATLG).

On systems that do not use SMS (yup, there still are some), the same dataset can be propogated across all of the devices in the UNIT specified. At one client when someone asked for help as to why they could not allocate a dataset, i looked at their vtocs and found the same dataset "all over the place". . .

Re: Difference between KEEP and CATLOG

PostPosted: Sat Jun 02, 2012 12:10 am
by sinmani
Here I agree with you completly Robert, Actually I am an application programmer so I may not understand the priorities of a system programmmer, be thats the reason for this apartheid towards system programmers.

I am sure the priorities are diff for system programmers. Though I have learned an imp point here and probable I will try to note down Vol ser no in future...this cd be an aded advantage.

:) Thanks

Re: Difference between KEEP and CATLOG

PostPosted: Sat Jun 02, 2012 12:29 am
by dick scherrer
Hello,

Suggest you ensure that all datasets are cataloged.

There is no good reason for application programmers to track which volser(s) are where their datasets reside. . .

Re: Difference between KEEP and CATLOG

PostPosted: Thu Jun 07, 2012 7:53 pm
by ashwin1990
thanks everyone for the replies