AMDSPZAP simply LINKs to IGWSPZAP. For a PDSEs, Extended Format Sequential Data Sets, or HFS/zFS files, IGWSPZAP (which was created when PDSEs were invented, and is now owned by the Binder) does all of the processing. For anything else (including VTOCs) , IGWSPZAP LINKs to AMAZAP. AMAZAP is pretty much the old AMASPZAP assembler language program from 50 years ago.
AMAZAP has 3 DCBs for the SYSLIB ddname:: MACRF=(E) MACRF=(RP),DSORG=(PS) MACRF=(R),DSORG=(PO) Under which circumstances it uses which access method, I don't know offhand. It is poorly documented gross old assembler code, and I only read pieces of it when I really have to. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY IBM Mainframe Discussion List <[email protected]> wrote on 01/19/2018 12:25:15 PM: > From: Tony Harminc <[email protected]> > To: [email protected] > Date: 01/19/2018 02:09 PM > Subject: Re: AMASPZAP usage > Sent by: IBM Mainframe Discussion List <[email protected]> > > On 19 January 2018 at 10:43, Seymour J Metz <[email protected]> wrote: > > AMASPZAP is AC(1) and can do what it wants. However, the ability > to zap an arbitrary CCHHR on a DASD volume is subject to SAF. > > Sure. But in order to have SAF control over datasets, it must either > OPEN them "normally" or make its own SAF call(s) and then build a DEB > and so on. I would expect it to open things normally except in odd > cases like zapping a VTOC. That's why I'm surprised that it can zap a > VSAM component, which surely a normal OPEN with a DCB will fail on. > > But who knows if this is old behaviour or if a whole lot was rewritten > when they did the PDSE support. > > An interesting test would be to see if it will zap an HFS "PDS" > dataset, or for that matter a ZFS VSAM one. > > Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
