Hi Max
Thank you for your input
We will do that
Regards
Jack
On Thu, 9 Jan 2025 at 16:01, Max Smith wrote:
> Jack,
> I would definitely open a case to IBM, we can help you get this cleaned
> up. The ERR 39 does not generate a fix for this so you are on your own, not
> necessarily a problem if
Jack,
I would definitely open a case to IBM, we can help you get this cleaned up. The
ERR 39 does not generate a fix for this so you are on your own, not necessarily
a problem if the backup version was an actual name. I think you might be able
to clean it up with the BDELETE command with a versi
. Check the fine manuals.
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of Jack Zukt
> Sent: Wednesday, January 8, 2025 10:52 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: HSM Audit Problem
>
> [CAUTION: This Email is from outside the
uary 8, 2025 10:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: HSM Audit Problem
[CAUTION: This Email is from outside the Organization. Unless you trust the
sender, Don't click links or open attachments as it may be a Phishing email,
which can steal your Information and compromise your
It should overwrite the dataset with the DCB and space characteristics
of the good dataset.
If not, delete then recreate without the REPLACING option.
On Wed, Jan 8, 2025 at 8:54 AM Jack Zukt
<059cd493dd41-dmarc-requ...@listserv.ua.edu> wrote:
>
> Hi Mike,
> Thank you for your suggestion. I su
Hi Nigel,
That is exactly what I did run. The ERR 39 are what remains after I managed
to fix all the other errors. Three different backups with that error. I get
the name of the PDS to be backed up, the names of the existing backups and
the ERR39 error messages, with binary zeros where a backup nam
Did you run the audit dsctl command with the FIX parameter? IIRC it
doesn't actually fix a problem that it identifies but it creates the FIXCDS
commands for you to review and then issue if you're happy with them.
On Tue, 7 Jan 2025 at 11:28, Jack Zukt <
059cd493dd41-dmarc-requ...@listserv.ua.
Hi Mike,
Thank you for your suggestion. I suppose that the rationale behind it would
be that the records that I now have in error would not be copied to the new
file? It may be worth a try. How
Regards
Jack
On Tue, 7 Jan 2025 at 17:56, Mike Schwab <
05962a42dc49-dmarc-requ...@listserv.ua.edu>
Try an ADRDSSU COPY hlq.valid.name TO hlq.error.name REPLACE.
https://www.ibm.com/docs/en/zos/2.4.0?topic=ccd-copy-dataset-command-syntax-logical-data-set
On Tue, Jan 7, 2025 at 5:28 AM Jack Zukt
<059cd493dd41-dmarc-requ...@listserv.ua.edu> wrote:
>
> Hi all,
> Unfortunately, after reading the
Hi all,
Unfortunately, after reading the manual about the FIXCDS command I am not
much better than I was before. So, I have a ten generation backup that has
seven valid backups and three entries in error, which means that what I
really have is a seven generation backup. There are three entries that
Thank you Mark.
I will look into it
Regards
Jack
On Mon, 6 Jan 2025 at 18:05, Mark Jacobs <
0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
> Take a look at the fixcds command.
>
>
> https://www.ibm.com/docs/en/zos/3.1.0?topic=commands-maintenance-command-fixcds
>
> Mark Jacobs
>
> Sent
Take a look at the fixcds command.
https://www.ibm.com/docs/en/zos/3.1.0?topic=commands-maintenance-command-fixcds
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com
On Monday, January 6
Hi all,
I am running a HSM AUDIT DSCTL(BACKUP), which is ending with a few ERR 39:
ERR 39 dataset name IS MISSING, with a lot of dots afterward. When I
execute the LIST BCDS LEVEL (dataset name) command, it wil display, for a
ten generation backup, seven good backups and three error lines "ARC0184I
13 matches
Mail list logo
