The reason I am hesitant to use the FIX command is that I am not sure if it
would impact HSM i.e. cause a slow down on other functions. This is why I was
looking at running the FIXCDS for each dsn.
Would you know if there could be any impact on HSM?
: EDITING DFHSM DSN CREATED FROM HSM COMMAND
To: IBM-MAIN@LISTSERV.UA.EDU
Received: Monday, July 28, 2014, 7:42 AM
And what is the answer to my other
question?
Are you using a REXX to edit the ODS and using ISPF File
Tailoring to make it what you what?
I always use an REXX/ISPF File tailoring
AUDIT
do it.
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Willie Bunter
> Sent: Monday, July 28, 2014 7:16 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: EDITING DFHSM DSN CREATED FROM HSM CO
Are you opposed to the FIX (as opposed to NOFIX) operand of the Audit command?
I am trying to edit the output from a AUDIT DATASETCONTROLS(MIGRATION) NOFIX
Here is an example of the output :
/* ERR 36 BACKUP VERSION ENTRY HSM.BACK.T253700.TSO.FOCUS.H9347 CONTAINS 0,
SHOULD CONTAIN 020
/* FI
Lizette,
Yes, I wrote the output to a dsn : Here is it is
AUDIT DATASETCONTROLS(BACKUP) NOFIX -
ODS(PT2001.AUDIT.DATASET.CONTROLS.BCDS1)
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list
DU] On
> Behalf Of willie bunter
> Sent: Monday, July 28, 2014 5:21 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: EDITING DFHSM DSN CREATED FROM HSM COMMAND
>
> Good Day,
>
> I am trying to edit the output from a AUDIT DATASETCONTROLS(MIGRATION)
> NOFIX
>
> Here is
Good Day,
I am trying to edit the output from a AUDIT DATASETCONTROLS(MIGRATION) NOFIX
Here is an example of the output :
/* ERR 36 BACKUP VERSION ENTRY HSM.BACK.T253700.TSO.FOCUS.H9347 CONTAINS 0,
SHOULD CONTAIN 020
/* FIXCDS B TSO.FOCUS.FOCEXEC.DATA VERIFY(X'0088' X'')
PATCH(