Re: DSS dump and migrated datasets
Thanks Mike. ABARS is great for this type of use case. ABACKUP with the MOVE option will backup all data types (no recall for migrated data) and delete the original copies, including the migrated data sets. Thus creating a single backup of all of the related data. Essentially, an Archive type of function. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
ABARS does not recall datasets. ABARS copies the VTape ML1/2/backup to the new archive tape. https://www.ibm.com/docs/en/zos/2.3.0?topic=guide-aggregate-backup-recovery-support-abars On Thu, Nov 23, 2023 at 12:59 PM Jack Zukt wrote: > Hi, > You coul use HSM ABARs. It will recall any migrated dataset that matches > your filter. > Best wishes > Jack > > On Thu, Nov 23, 2023, 16:58 Radoslaw Skorupka < > 0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: > > > I need to dump a lot of small dataset with HLQ=user_to_be_deleted. > > Since the user is no longer active, most of datasets are migrated to ML1 > > and ML2. > > > > By default ADRDSSU does not process migrated datasets. > > Is there any method to circumvent it? > > It can be anything, including scripted "touch". > > > > -- > > Radoslaw Skorupka > > Lodz, Poland > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
On Thu, 23 Nov 2023 22:47:59 +0100, Radoslaw Skorupka wrote: >Well, Keith metioned *a switch*. Turning on the switch implies that everyone agreed that the feature benefits are more important than the risks. This is acceptable because IBM warned you and your company accepted the risks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
W dniu 23.11.2023 o 22:32, Jon Perryman pisze: On Thu, 23 Nov 2023 19:47:24 +, Keith Gooding wrote: I certainly would like the option to tell dss to recall datasets I feel your pain but I personally agree with IBM's decision. Realize this is z/OS with specialists instead UNIX with its jack of all trades. DASD sysprog, performance sysprog, scheduler and more should be involved in how this should occur because they have access to important knowledge, For instance, the DASD sysprog can tell you the importance of using HRECALL instead of ADRDSSU doing the recall. Very simply, HRECALL can group recalls by recall volume with fewer tape mounts and they can easily cancel the request if people are being impacted. The scheduler can schedule this non-time sensitive work when it won't impact others. Well, Keith metioned *a switch*. You don't like tape mounting? No problem, just don't use that feature. However I remember a lot of scenarios where there was a need to copy *all* dataset belonging to the mask/list, not jut those not migrated. And of course my current issue is yet another one. BTW: I don't care about mounting tapes. My virtual drives are certified for millions of mounts. Not to mention ML1. :-) Trivia: the last real tape drive for z/OS was released in May of 2011 and end of service was 28th Feb 2022. No further (directly attached) models for 12 years. And most virtual tape vendors do not offer any tape at backed. IBM, Fujitsu and one other (can't remember now) are exceptions. -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
On Thu, 23 Nov 2023 19:47:24 +, Keith Gooding wrote: >I certainly would like the option to tell dss to recall datasets I feel your pain but I personally agree with IBM's decision. Realize this is z/OS with specialists instead UNIX with its jack of all trades. DASD sysprog, performance sysprog, scheduler and more should be involved in how this should occur because they have access to important knowledge, For instance, the DASD sysprog can tell you the importance of using HRECALL instead of ADRDSSU doing the recall. Very simply, HRECALL can group recalls by recall volume with fewer tape mounts and they can easily cancel the request if people are being impacted. The scheduler can schedule this non-time sensitive work when it won't impact others. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
Jon. I certainly would like the option to tell dss to recall datasets so that they can be copied or backed up. A common use case for me is to back up , or copy and rename, a set of software libraries for archiving or distribution to another system (a bit like a zOSMF portable software instance). It certainly should not be the case that dss routinely ignores migrated datasets unless a patch byte is set. Keith Gooding > On 23 Nov 2023, at 19:23, Jon Perryman wrote: > > On Thu, 23 Nov 2023 18:18:23 +, Keith Gooding wrote: > >> I do not know why IBM do not have an option for adrdssu to go the recall >> automatically - there have been some requests on IBM ideas. > > The last thing you want is for ADRDSSU to become long running waiting on > multiple recalls from multiple tapes. There's also the problem that someone > inadvertently runs a backup that includes archived datasets. You have limited > disk space and unwitting users can potentially defeat the purposes of HSM > archiving. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
W dniu 23.11.2023 o 20:11, Jon Perryman pisze: On Thu, 23 Nov 2023 17:57:53 +0100, Radoslaw Skorupka wrote: I need to dump a lot of small dataset with HLQ=user_to_be_deleted. Since the user is no longer active, most of. datasets are migrated to ML1 and ML2. Do you really need another backup since HSM already backed them up? If HRECALL generics don't meet your needs, then you could write a REXX to be more granular. No, I don't want any backup. I need to delete inactive users and put their datasets into archive bucket. I could replace userid with same named group to keep protection, but I also have to clean up an SG with user data. Is it the best way to manage it? Not my decision. However HRECALL NOWAIT is a solution. Thanks. -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
That's the trick! I forgot about HRECALL and generics. Thank you. -- Radoslaw Skorupka Lodz, Poland W dniu 23.11.2023 o 19:18, Keith Gooding pisze: I usually run a batch TSO step which issues command HRECALL ‘HLQ.** WAIT’ immediately before the dump step. You may get a lot of messages sent to your TSO session - either saying dataset not migrated or that migration is complete. There is also a ADRDSSU patch ( from memory patch area offset 17 but check in the admin guide) which will warn you if any of the datasets are still migrated when you run the dump command. I do not know why IBM do not have an option for adrdssu to go the recall automatically - there have been some requests on IBM ideas. This recall method does not work for more complicated dss filters such as “MYID.**.DATA” Keith Gooding On 23 Nov 2023, at 17:32, Radoslaw Skorupka<0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: Well, First, I DON'T WANT TO DELETE datasets. I wan to dump them to archive file. Second, I want to avoid manual typing/clicking. :-) -- Radoslaw Skorupka Lodz, Poland W dniu 23.11.2023 o 18:01, Steve Beaver pisze: Bring the list up in 3.4 then do a hdelete By every dsn and hit enter Sent from my iPhone No one said I could type with one thumb On Nov 23, 2023, at 10:57, Radoslaw Skorupka<0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: I need to dump a lot of small dataset with HLQ=user_to_be_deleted. Since the user is no longer active, most of datasets are migrated to ML1 and ML2. By default ADRDSSU does not process migrated datasets. Is there any method to circumvent it? It can be anything, including scripted "touch". -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
On Thu, 23 Nov 2023 18:18:23 +, Keith Gooding wrote: >I do not know why IBM do not have an option for adrdssu to go the recall >automatically - there have been some requests on IBM ideas. The last thing you want is for ADRDSSU to become long running waiting on multiple recalls from multiple tapes. There's also the problem that someone inadvertently runs a backup that includes archived datasets. You have limited disk space and unwitting users can potentially defeat the purposes of HSM archiving. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
On Thu, 23 Nov 2023 17:57:53 +0100, Radoslaw Skorupka wrote: >I need to dump a lot of small dataset with HLQ=user_to_be_deleted. >Since the user is no longer active, most of. datasets are migrated to ML1 >and ML2. Do you really need another backup since HSM already backed them up? If HRECALL generics don't meet your needs, then you could write a REXX to be more granular. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
Hi, You coul use HSM ABARs. It will recall any migrated dataset that matches your filter. Best wishes Jack On Thu, Nov 23, 2023, 16:58 Radoslaw Skorupka < 0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: > I need to dump a lot of small dataset with HLQ=user_to_be_deleted. > Since the user is no longer active, most of datasets are migrated to ML1 > and ML2. > > By default ADRDSSU does not process migrated datasets. > Is there any method to circumvent it? > It can be anything, including scripted "touch". > > -- > Radoslaw Skorupka > Lodz, Poland > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
I usually run a batch TSO step which issues command HRECALL ‘HLQ.** WAIT’ immediately before the dump step. You may get a lot of messages sent to your TSO session - either saying dataset not migrated or that migration is complete. There is also a ADRDSSU patch ( from memory patch area offset 17 but check in the admin guide) which will warn you if any of the datasets are still migrated when you run the dump command. I do not know why IBM do not have an option for adrdssu to go the recall automatically - there have been some requests on IBM ideas. This recall method does not work for more complicated dss filters such as “MYID.**.DATA” Keith Gooding > On 23 Nov 2023, at 17:32, Radoslaw Skorupka > <0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: > > Well, First, I DON'T WANT TO DELETE datasets. I wan to dump them to archive > file. > Second, I want to avoid manual typing/clicking. > :-) > > -- > Radoslaw Skorupka > Lodz, Poland > > > > W dniu 23.11.2023 o 18:01, Steve Beaver pisze: >> Bring the list up in 3.4 then do a hdelete >> By every dsn and hit enter >> >> Sent from my iPhone >> >> No one said I could type with one thumb >> On Nov 23, 2023, at 10:57, Radoslaw Skorupka<0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: >>> >>> I need to dump a lot of small dataset with HLQ=user_to_be_deleted. >>> Since the user is no longer active, most of datasets are migrated to ML1 >>> and ML2. >>> >>> By default ADRDSSU does not process migrated datasets. >>> Is there any method to circumvent it? >>> It can be anything, including scripted "touch". >>> >>> -- >>> Radoslaw Skorupka >>> Lodz, Poland >>> > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
Well, First, I DON'T WANT TO DELETE datasets. I wan to dump them to archive file. Second, I want to avoid manual typing/clicking. :-) -- Radoslaw Skorupka Lodz, Poland W dniu 23.11.2023 o 18:01, Steve Beaver pisze: Bring the list up in 3.4 then do a hdelete By every dsn and hit enter Sent from my iPhone No one said I could type with one thumb On Nov 23, 2023, at 10:57, Radoslaw Skorupka<0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: I need to dump a lot of small dataset with HLQ=user_to_be_deleted. Since the user is no longer active, most of datasets are migrated to ML1 and ML2. By default ADRDSSU does not process migrated datasets. Is there any method to circumvent it? It can be anything, including scripted "touch". -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DSS dump and migrated datasets
Bring the list up in 3.4 then do a hdelete By every dsn and hit enter Sent from my iPhone No one said I could type with one thumb > On Nov 23, 2023, at 10:57, Radoslaw Skorupka > <0471ebeac275-dmarc-requ...@listserv.ua.edu> wrote: > > I need to dump a lot of small dataset with HLQ=user_to_be_deleted. > Since the user is no longer active, most of datasets are migrated to ML1 and > ML2. > > By default ADRDSSU does not process migrated datasets. > Is there any method to circumvent it? > It can be anything, including scripted "touch". > > -- > Radoslaw Skorupka > Lodz, Poland > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DSS dump and migrated datasets
I need to dump a lot of small dataset with HLQ=user_to_be_deleted. Since the user is no longer active, most of datasets are migrated to ML1 and ML2. By default ADRDSSU does not process migrated datasets. Is there any method to circumvent it? It can be anything, including scripted "touch". -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
