/2018 02:09 PM
> Subject: Re: AMASPZAP usage
> Sent by: IBM Mainframe Discussion List
>
> On 19 January 2018 at 10:43, Seymour J Metz 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.
ason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Tony Harminc
Sent: Friday, January 19, 2018 12:25 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: AMASPZAP usage
On 19 January 2018 at 10:43, Seymour J Metz wrote:
> AMASPZAP is AC(1) a
On 19 January 2018 at 10:43, Seymour J Metz 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
: Thursday, January 18, 2018 5:18 PM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: AMASPZAP usage
On 18 January 2018 at 09:53, R.S. wrote:
> It is not necessarily PS dataset, it can be some component of VSAM. Actually
> I'm using SPZAP to inject some "illegal values" inside.
>
On Thu, 18 Jan 2018 17:18:50 -0500, Tony Harminc wrote:
>I'm a little surprised that SPZAP is willing/able to open a VSAM
>component
I'm not. It can dump or modify data on DASD that isn't even
in a data set. e.g. the VTOC.
--
Tom Marchant
--
On 18 January 2018 at 09:53, R.S. wrote:
> It is not necessarily PS dataset, it can be some component of VSAM. Actually
> I'm using SPZAP to inject some "illegal values" inside.
> And I'd like to make it automatically. Batch is automatic, online is manual.
I'm a little surprised that SPZAP is wil
Of course there are other tools, some of them provide batch interface,
but I wanted SPZAP because it is not licensed, that means available with
any z/OS installation.
Suppose you could copy the record to a temporary data set, modify it,
and rewrite it?
There are different unload and rewri
W dniu 2018-01-18 o 18:57, Peter Hunkeler pisze:
Of course I know the offset and old data. What I cannot predict is disk
address and in fact cannot understand why AMASPZAP wants me to provide
unnecessary information.
I think you may misunderstand the parameters. The offset on the VER and REP
>Of course I know the offset and old data. What I cannot predict is disk
address and in fact cannot understand why AMASPZAP wants me to provide
unnecessary information.
I think you may misunderstand the parameters. The offset on the VER and REP
statements is the byte offset from the beginning of
On Thu, 18 Jan 2018 15:53:35 +0100 "R.S."
wrote:
:>It is not necessarily PS dataset, it can be some component of VSAM.
:>Actually I'm using SPZAP to inject some "illegal values" inside.
:>And I'd like to make it automatically. Batch is automatic, online is
:>manual. ;-)
Edit can be done batch.
It is not necessarily PS dataset, it can be some component of VSAM.
Actually I'm using SPZAP to inject some "illegal values" inside.
And I'd like to make it automatically. Batch is automatic, online is
manual. ;-)
Of course I know the offset and old data. What I cannot predict is disk
address
I would suggest that AMASPZAP is the wrong tool for this. It requires knowing
the offset.
Why not simply an edit session with a hex change command? As you are doing a
PS dataset anyway, no big deal. Or a simple program?
On Thu, 18 Jan 2018 14:44:54 +0100 "R.S."
wrote:
:>Problem #1.
:>I want to
12 matches
Mail list logo
