Re: Serialization of PDS Member update/deletion through IBM Utilities

2005-08-03 Thread Binyamin Dissen
On Tue, 2 Aug 2005 20:48:43 -0500 Hank Medler [EMAIL PROTECTED] wrote: :Does anyone happen to know the QNAME that is used by IDCAMS for member :deletion when using the FILE parameter on the DELETE statement? Is it :SYSZOPEN? I read through z/OS 1.6 DFSMS Access Method Services for Catalogs

Re: Serialization of PDS Member update/deletion through IBM Utilities

2005-08-03 Thread ibm-main
From: Binyamin Dissen Nowadays one gets an abend if more than one job opens the same PDS for output. mm - maybe. *if* everybody is playing with the same deck of cards. Go edit a member of a PDS and whilst in the edit session run a batch UPDTE to replace the same member. You'd better be

Re: Serialization of PDS Member update/deletion through IBM Utilities

2005-08-03 Thread John P Kalinich
From: Binyamin Dissen Nowadays one gets an abend if more than one job opens the same PDS for output. From: Shane mm - maybe. *if* everybody is playing with the same deck of cards. Abend S213-30 addresses the situation of a PDS opened for OUTPUT with DISP=SHR. Regards, John Kalinich

Re: serialization of PDS Member update/deletion through IBM Utilities

2005-08-03 Thread john gilmore
Shane has said all that needs to be said, viz., Use DISP=OLD, or migrate it to a PDSE. It may be indeed that he has said more than enough. I would delete the first term in his disjunction. John Gilmore Ashland, MA 01721 USA

Re: serialization of PDS Member update/deletion through IBM Utilities

2005-08-03 Thread john gilmore
Shane, In Flaubert's much abused words, Le bon Dieu est dans le détail. The original poster was talking of writing an HLASM routine to (a) cope with an old, old problem that he understood imperfectly and (b) with one that, moreover, the design of PDSEs addresses bang on. I am not

Serialization of PDS Member update/deletion through IBM Utilities

2005-08-02 Thread Hank Medler
Does anyone happen to know the QNAME that is used by IDCAMS for member deletion when using the FILE parameter on the DELETE statement? Is it SYSZOPEN? I read through z/OS 1.6 DFSMS Access Method Services for Catalogs manual, but I don't see any indication of what is happening under the covers. In