Hi,
My question is going to be very general. Our shop has the policy of running
daily back up from Mon-friday on a incremental basis(Volume Level). So we
have been using this Keyword at sysin control card : DATASET(INCLUDE(**)
BY(DSCHA,EQ,YES), which means that the backup would take place only if
m: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:>: Behalf Of Jake anderson
:>: Sent: Thursday, December 06, 2012 10:06 PM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Conditional Statement during Backup - Clarification
:>:
:>: Hi,
:>:
:>: My question i
On 6 Dec 2012 22:05:56 -0800, in bit.listserv.ibm-main
(Message-ID:)
justmainfra...@gmail.com (Jake anderson) wrote:
My question is going to be very general. Our shop has the
policy of running
daily back up from Mon-friday on a incremental
basis(Volume Level). So we
have been using this Keywo
"One possible solution would be to change the PROC by adding a step on each
side of the ADRDSSU step:The step prior would be a simple IDCAMS to create
a small dataset onthe volume. "
Apology for not showing up the entire JCL since we are having 65 volumes so
I guess it would create a huge proc to
Hope IBM DFSMS dev or Support Can Comment on this. But yes I would be
opening a PMR and Hope it might even need an APAR as well.
On Fri, Dec 7, 2012 at 3:13 PM, Jake anderson wrote:
> "One possible solution would be to change the PROC by adding a step on
> each side of the ADRDSSU step:Th
Hello,
is it possible that your output tape dd has gone onto an additional volser? i
seem to remember from a long time ago that this was often the issue
with these abends on multi label multi volume tape datasets.
Dave
---
I even tried with a brand new 3590 tape and it was same abend after some
label. Its a multi-label multi volume volume tape.
On Fri, Dec 7, 2012 at 6:00 PM, David Devine wrote:
> Hello,
> is it possible that your output tape dd has gone onto an additional
> volser? i seem to remember from a
Jake anderson wrote:
>I even tried with a brand new 3590 tape and it was same abend after some
>label.
Show IBM-MAIN how you have initialized your 3590. I think it was not done
properly.
> Its a multi-label multi volume volume tape.
Really 'multi volume'? Why are you using this statement
" I think it was not done properly."
IEHINITT does as expected with return code 00. Thats why the tape label was
recognized for few volumes during back up. To check if the initialization
had any problem I tried taking a Full volume back up without the
conditional statement and the job ended well.
Jake,
Is the expectation that it always write data? Is it possible that when you
got to LABEL=2 there was no changed data and therefore it did not write the
label? Can you confirm you had changed data for all volumes you are backing
up to the various labels?
Also what were the ADR messages besid
Jake anderson wrote:
>IEHINITT does as expected with return code 00.
Ok, this exclude any possibility of bad tapes. I always start at the begining
to exclude all possibilities.
I think (after reading all other's answers) you can do this:
Create/modify a dataset on EVERY volume to be dumped wh
We do full volume backups to virtual tape, excluding OMVS and
multivolume dsns. We don't get the tape created for a few volumes
that are full of multi-volume datasets, and for empty volume that
haven't been take offline yet.
--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get
M-MAIN@LISTSERV.UA.EDU] On
:>: Behalf Of Jake anderson
:>: Sent: Friday, December 07, 2012 1:43 AM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: Conditional Statement during Backup - Clarification
:>:
:>: "One possible solution would be to change the PROC by adding a ste
A.EDU]
> On
> :>: Behalf Of Jake anderson
> :>: Sent: Friday, December 07, 2012 1:43 AM
> :>: To: IBM-MAIN@LISTSERV.UA.EDU
> :>: Subject: Re: Conditional Statement during Backup - Clarification
> :>:
> :>: "One possible solution would be to change the PROC
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU
> ]
> > On
> > :>: Behalf Of Jake anderson
> > :>: Sent: Friday, December 07, 2012 1:43 AM
> > :>: To: IBM-MAIN@LISTSERV.UA.EDU
> > :>: Subject: Re: Conditional Statement during Backup - Clarification
&
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Jake anderson
> Sent: Monday, December 10, 2012 5:56 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Conditional Statement during Backup - Clarification
>
> I agree
> Lizette
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf
> > Of Jake anderson
> > Sent: Monday, December 10, 2012 5:56 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: Condi
; From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf
> Of Jake anderson
> Sent: Monday, December 10, 2012 8:00 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Conditional Statement during Backup - Clarification
>
> Hi lizette,
>
> Please find th
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
:>: Behalf Of Jake anderson
:>: Sent: Monday, December 10, 2012 7:00 AM
:>: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: Conditional Statement during Backup - Clarification
:>:
:>: Hi lizette,
:>:
:>: Please find the error
I had to break up a job recently due to too many steps... There is a limit.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
20 matches
Mail list logo
