Re: z/OS Container Extensions

I've seen bits and piecesI believe It's a blackbox secure setup. No on-site Linux administration aside from application admin or maintenance required, no ROOT access. All handled by IBM AFAIK.

Re: TSO Reconnect ABEND=S622

DMZ shouldn't matter. What's the logic in the IEFUTL exit? Is it doing different things based on system? Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On

Re: z/OS Container Extensions

Kind of like a z/OS address space. Includes application and user software and database software. Allows the hypervisor on a server to switch quickly to other applications instead of waiting for more transactions. On Thu, May 16, 2019 at 6:12 PM Farley, Peter x23353 wrote: > > Dumb question for

Re: z/OS Container Extensions

Dumb question for the day: What exactly is a "Docker Container"? Is there a very simple overview tutorial anywhere of what it does and how it does it that a mainframe programmer (with a small smattering of *ix knowledge) could use to understand what they are and how they could be used in z/OS?

Re: z/OS Container Extensions

We learned at Share Phoenix that the Linux kernel is Ubuntu. David On Thursday, May 16, 2019 Jousma, David wrote: I've seen bits and piecesI believe It's a blackbox secure setup.  No on-site Linux administration aside from application admin or maintenance required, no ROOT access.  All

Re: z/OS Container Extensions

Tina, Thanks for the link, but when viewed in IE11 none of the FAQ answers wraps at the screen boundary, and there is no slide bar at the bottom to slide the image to be able to see the rest of the text. It seems to work just fine in Firefox 60.6.3ESR, just not in IE11. Peter -Original

Re: [External] Re: Ancient DASD connectivity

On Thu, 16 May 2019 at 12:50, Alan Altmark wrote: > Disk, tape, and unit record devices of the same era had discrete > controllers. Unit record CU (2821) was interesting in that it talked to > devices that did different things: 1403/1404 printer and 2540 card > reader-punch. Clever of them.

Re: [External] Re: Ancient DASD connectivity

Some legacy devices, e.g., 1301, had external controllers, e.g., 7631. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Tony Harminc Sent: Thursday, May 16, 2019 3:34 PM To:

Re: DFDSS copy to pre-allocated dsn

Please post the full message. That 001 is not the reason code; that should be right after 'NOT PROCESSED'. If the reason code were actually 1, for an un-moveable dataset, I'd say add FORCE. You could also just delete the target. -Original Message- From: IBM Mainframe Discussion List

Re: z/OS Container Extensions

And I should have added before sending: Not a PHB airline magazine overview, a COBOL-and-assembler-programmer-level explanation. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Thursday, May 16, 2019

Re: z/OS Container Extensions

You can check out the details here --> https://www.ibm.com/support/z-content-solutions/container-extensions/ There are some FAQs that cover what you ask below, and more! And if that doesnt cover it, we can get the team to meet with you directly! Tina M. Tarquinio Director, IBM z/OS |

DFDSS copy to pre-allocated dsn

I've found a lot of " it's " confusing comments on this topic and I am beleaguered- I am trying to copy a file to an existing, pre-allocated new name. Seems that should be pretty straight forward... but having to specify rename to make a copy is anything but straight forward I'm getting ADR380E

Re: [External] Re: Ancient DASD connectivity

> Disk, tape, and unit record devices of the same era had discrete controllers. Some did, but not all. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Alan Altmark Sent: Thursday, May 16, 2019

Re: z/OS Container Extensions

On 5/16/2019 12:01 PM, Frank Swarbrick wrote: Don't really know anything about this, but does anyone know what advantage there is to running a Docker container on z/OS over just running it Linux for Z? Is it just for those who don't have Linux for Z but want to run Linux applications on the

Re: TSO Reconnect ABEND=S622

IEFUTL is exactly the same on both systems. Not sure if this is helpful, but the system with the short timeout is "in the DMZ" -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: DFDSS copy to pre-allocated dsn

Same names on a rename On Thu, May 16, 2019 at 5:51 PM Elaine Beal wrote: > I've found a lot of " it's " confusing comments on this topic and I am > beleaguered- > I am trying to copy a file to an existing, pre-allocated new name. > Seems that should be pretty straight forward... but having

Re: DFDSS copy to pre-allocated dsn

So you are making 3 copies on 3 different OUTDDNAMES? If it is one dataset on 3 volumes it would be one OUTDDNAME, right? On Thu, May 16, 2019 at 4:51 PM Elaine Beal wrote: > > I've found a lot of " it's " confusing comments on this topic and I am > beleaguered- > I am trying to copy a file to

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

John, I'm running 2.2 as well. I was able to run it successfully copying 2 datasets to a tape. And just for kicks and giggles, I removed the TYPRUN parm and it dumped the 2 datasets to a single tape. Here's my JCL/parms: //STEP005 EXEC PGM=ADRDSSU,REGION=0M,PARM='TYPRUN=NORUN'

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

I just changed my SYSIN to look as close to identical to yours as I can see, given the formatting problems you're having, and it still worked. Regarding the "column 1" question David had, I just tried it, and all DFDSS did was ignore the first character of the dataset name and tell me it

Re: DFDSS copy to pre-allocated dsn

I don't know for sure if OUTDD works exactly like OUTDY; I was wondering. I used (no longer a DSS shop) OUTDY to list candidate volumes; COPY makes only one copy, whether it exists on one volume or is spread across multiple ones. Anyway, since this is non-SMS managed, it can be on only one

File 228 CBT tape - HSM panel recovery

Hi I am trying to use this file for a panel based recovery of HSM managed backup . When I do HLIST DSN('XXX.YY.ZZ') BCDS I get the details of backup but when I use the CBTTAPE 228 it doesn't show up anything ? Is anyone using it and getting as expected ? Peter

Re: ISPF and newer COBOL keywords

It's certainly possible to create your own custom browsers and editor behaviors (with custom highlighting) in ISPF, and that's pretty well documented in the ISPF sections of the z/OS Knowledge Center. Past IBM practice was to roll up additional COBOL reserved word highlighting into ISPF in some

z/OS Container Extensions

Don't really know anything about this, but does anyone know what advantage there is to running a Docker container on z/OS over just running it Linux for Z? Is it just for those who don't have Linux for Z but want to run Linux applications on the mainframe? Does it allow "direct access" to

Re: File 228 CBT tape - HSM panel recovery

HELP HLIST says that HSM will allocate a dataset with RECFM=FBA,LRECL=121,BLKSIZE=1210 if a datatset doesn't exist, so those attributes should work fine for a pre-allocated dataset. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key -

Re: File 228 CBT tape - HSM panel recovery

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.arcf000/s4334.htm RECFM=FBA, LRECL=121. On Thu, May 16, 2019 at 7:15 AM Allan Staller wrote: > > HSM is *VERY PICKY* about the actual DCB characteristics of the ODS. > If the ODS does not match what HSM expects, HSM

Re: File 228 CBT tape - HSM panel recovery

Hi again Take a look to the following code section in File 228 and change the SUBSTR and the "BACKUP" to the HLQ matching your names. /* LOOK FOR BEGINNING OF BCDS SECTION */ IF (31:36,) =

Re: File 228 CBT tape - HSM panel recovery

HSM is *VERY PICKY* about the actual DCB characteristics of the ODS. If the ODS does not match what HSM expects, HSM gives up and produces nothing. I don’t remember what DCB characteristics are required, but it must be documented somewhere. HTH, -Original Message- From: IBM Mainframe

Re: [External] Re: Ancient DASD connectivity

Tom, No problem. I wasn't very clear in my comments. Kind of like wanting the computer to have a "DWIW" command - do what I want. :-) Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Marchant Sent: Wednesday, May 15, 2019 6:12 PM To:

Re: Address space dump for Exit usage

Using certain exits can also be defined outside control of the Address Space. E.g. SMFPRMxx defines whether certain exits are used or not for the address space. Or, PROGxx defines whether certain exit routines are used or not. Both situations will probably be invisible in a dump of the address

Fwd: IBM 'cloudifies' mainframe software pricing, adds hybrid, private cloud services | Network World

News article, see link below, in regards to IBM's software announcement of yesterday: IBM United States Software Announcement 219-014 or https://tinyurl.com/yykuaslr

Re: Metal-C exits

[Default] On 16 May 2019 04:55:33 -0700, in bit.listserv.ibm-main rel...@us.ibm.com (Peter Relson) wrote: > >...where IBM provides some guidelines for doing exit work in Metal-C > > >I'd say that the guideline is to get Metal C to do what you would have >done if you were coding in assembler.

Re: File 228 CBT tape - HSM panel recovery

Thanks Mark. I never could find that info in the FM's -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Jacobs Sent: Thursday, May 16, 2019 7:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: File 228 CBT tape - HSM panel recovery HELP HLIST says that HSM will

Re: Metal-C exits

...where IBM provides some guidelines for doing exit work in Metal-C I'd say that the guideline is to get Metal C to do what you would have done if you were coding in assembler. What you typically need are mappings in (Metal) C for the data structures that the exit routine needs to

Re: File 228 CBT tape - HSM panel recovery

I wrote a program to anaylize a IDCAMS output. Every few years the size of some fields would increase and the report literals would be moved to allow the larger fields. I would check these positions in the analysis program. Better would be to look at an IDCAMS DCOLLECT filed because those

Re: File 228 CBT tape - HSM panel recovery

No the BCDS is not hard coded it's basically doing a HLIST and writing to ODS. unfortunately the output file is not read properly to display the HSM backup On Thu, 16 May, 2019, 2:29 PM Peter Glanzmann, wrote: > Hi Peter > > I assume that the source code of the program in CBT file 228 has the

Re: [External] Re: Ancient DASD connectivity

W dniu 2019-05-15 o 21:53, Pommier, Rex pisze: It was sheer size of the componentry that drove this design. I think the 3990 was the last stand-alone disk controller. With the arrival of 2105s, the CU was inside the same cabinet as the drives and Logical CUs (LCUs) were born. One big

Re: Saving in memory data in case of operator cancel was Re: LE question

The choices are between saving the data yourself as you go, such as by some sort of checkpoint or other method, or saving the data yourself after the cancel (for which some sort of TERM=YES ESTAE-type recovery is necessary) or not allowing the CANCEL (whether by intercepting CANCEL or making

Re: File 228 CBT tape - HSM panel recovery

Hi Peter I assume that the source code of the program in CBT file 228 has the name of the BCDS hard coded. Please search for the BCDS name in the CLIST and replace it using the one of your installation. Best regards Peter --

Re: Address space dump for Exit usage

On Thu, 16 May 2019 09:06:46 +0400 Jake Anderson wrote: :>When we take a SVCDUMP for an active address space . Does the dump shows if :>that particular address space uses particular EXIT ? I am just trying to :>understand if a dump of an address space can help me to determine if a :>particular

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Could it be that you are missing a dash after the word DUMP? Or a space between these two keywords: INDDNAME(DASD1)OUTDDNAME(TAPE1) _ Dave Jousma AVP | Manager, Systems Engineering 

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

It's hard for me to read the reformatted text. But you need a comma between the two DSNs in the INCLUDE list. I don't see any comma. On Thu, May 16, 2019 at 9:51 AM John Dawes < 00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote: > G'Day, > I am encountering a problem performing a Physical

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Dave,I checked.  The DUMP statement is part of the INDDNAME.  It looks that it is missing the - because my post came out misaligned.Here it is again:  DUMP INDDNAME(DASD1)OUTDDNAME(TAPE1)    -   DATASET(INCLUDE(HESP.IMS.PROD.MATRIX      - 

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

John,The - or , are both acceptable.  I use the - all the time and never had a problem. On Thursday, 16 May 2019, 2:59:16 pm UTC, John McKown wrote: It's hard for me to read the reformatted text. But you need a comma between the two DSNs in the INCLUDE list. I don't see any comma. On

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.adru000/r2298.htm INCLUDE(data.set.one, - data.set.two) Commas are REQUIRED. On Thu, May 16, 2019 at 9:51 AM John Dawes <00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote: > > G'Day, > I am

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

David,The reason why I am doing a Physical backup of the dsns instead of a Logical backup it is because these dsns have a problem - no NVR.  They reside on a SMS volume but for some reason some of the dsn|(s) are non-SMS.DFDSS does not support a Logical backup of these problem dsns On

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Please excuse my post for being misaligned.  I do not know how to correct it.  Any ideas? On Thursday, 16 May 2019, 2:51:22 pm UTC, John Dawes <00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote: G'Day, I am encountering a problem performing a Physical dataset backup of several dsn

Re: [External] Re: Ancient DASD connectivity

On Thu, May 16, 2019 at 8:08 AM Pommier, Rex wrote: > Tom, > > No problem. I wasn't very clear in my comments. Kind of like wanting the > computer to have a "DWIW" command - do what I want. :-) > DWIW has been deprecated by the new DWIN (Do What I Need) instruction. Because end users don't

DFDSS QUESTION - PHYSICAL DATASET BACKUP

G'Day, I am encountering a problem performing a Physical dataset backup of several dsn which are on a specific volume.  For some reason it doesn't work. I receive the error message ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER Below is the job output and the JCL.  Can you spot my error? 

Re: [External] Re: Ancient DASD connectivity

DWIN was superesed by DWIM - Do what I meant! -Original Message- From: IBM Mainframe Discussion List On Behalf Of John McKown Sent: Thursday, May 16, 2019 9:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: Ancient DASD connectivity On Thu, May 16, 2019 at 8:08 AM Pommier,

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

I tried your suggestion but it didn't work: ADR129E (001)-RI01 (01), KEYWORD '      ' IS IMPROPER  On Thursday, 16 May 2019, 3:13:43 pm UTC, Mike Schwab wrote: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.adru000/r2298.htm INCLUDE(data.set.one, -      

Re: Ancient DASD connectivity

Well, for some devices the CU and device were in the same box, e.g., 2501. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Alan Altmark Sent: Wednesday, May 15, 2019 5:45 PM To:

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

I use a FILTER DD //FILTERDS DD DSN=.ISMF.COPY.D18004.T144134, // DISP=OLD //SYSIN DD * COPY DATASET(FILTERDD(FILTERDS)) - ALLDATA(*) - ALLEXCP - SELECTMULTI(ALL) - BYPASSACS(**) - LOGINDDNAME( - INVOL1 - ) - NULLMGMTCLAS - NULLSTORCLAS - FILTER DD CONTAINS. INCLUDE(

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Rex,I tried that as well but I got the same ADR129E error message.I tried the backup for one dsn and it works.  Which makes me believe that a multiple physical dsn backup is  not supported by DFDSS. On Thursday, 16 May 2019, 3:29:32 pm UTC, Pommier, Rex wrote: John, I see that

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Hi John, Physical Backups are usually a bad idea when doing backup by dataset. If these are non-VSAM and non-SMS-managed, you can still do it for specific volumes by coding LIDD instead of INDD. The INDD/INDY is used to determine Logical vs. Physical. If coded, it's Physical, otherwise, it's

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

On Thu, May 16, 2019 at 10:10 AM John Dawes < 00ff0e22811f-dmarc-requ...@listserv.ua.edu> wrote: > John,The - or , are both acceptable. I use the - all the time and never > had a problem. > Thanks. I misread the "railroad track" diagram for the DUMP command. > On Thursday, 16 May

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

John, I see that you're doing a TYPRUN=NORUN. What happens if you strip all the excess/optional lines from your SYSIN. Can you eliminate the error by eliminating most of the control cards and just re-add them until you hit the error again? Rex -Original Message- From: IBM Mainframe

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Do you have some kind of hidden hex character in your input stream? -Original Message- From: IBM Mainframe Discussion List On Behalf Of John Dawes Sent: Thursday, May 16, 2019 10:21 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP I

Re: Metal-C exits

Peter, A big thanks, what I would like to know are there restrictions for Metal C exits. For example, lets say i wanted to write RACF or JES2 exit. Is Metal C well suited for that purpose ? I dont want to assume . I would like to write Metal C for some of our functions and we primarily are

Re: Saving in memory data in case of operator cancel was Re: LE question

Peter/Clark, Since we are a ISV, we try to intervene ourselves. My issue was on how to do it. I know LE but I am faced with we cant just convert to pure HLASM or even threaded C or C++ . So i have to come up with an alternative solution that works. We have been using Subpool 231 and it works

Re: LE question

Brian, I would agree it must be a lot of overhead looking at everything and then having the code make the decision on what to do. Especially in a System exit. Scott On Thu, May 16, 2019 at 12:19 AM Brian Westerman < brian_wester...@syzygyinc.com> wrote: > HI, > > ALL commands issued at a

ISPF and newer COBOL keywords

Since Enterprise COBOL V5.1, IBM has been adding new COBOL language features with each release (and sometimes within a single "release"). On our system, at least, the ISPF "HILITE COBOL" Color Settings feature has not been keeping up. The new "inline comment" indicator that was added with

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

One other tidbit. The SYSIN data, and all of the lines must be contained between columns 2-72. Not column 1. It would be really helpful if you could post the job with the correct formatting. Whatever is messing it up appears to be removing spaces between some of your keywords.

Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

This would be correct syntax. Comma's are optional, dash is not. By your other post where you said it worked with one dataset, it almost looks like your HESP. Dataset name starts in column 1? //SYSINDD * DUMP INDDNAME(DASD1) OUTDDNAME(TAPE1)-

Re: Metal-C exits

Well, XLC already provides a DSECT to struct conversion tool. I haven't found its output to be as awful as it once was. One thing I might suggest is to get header files out of SAMPLIB. There are now two system-level header libraries (SYS1.SIEAHDR.H, and SYS1.SIEAHDRV.H), which could also be

Re: Fwd: IBM 'cloudifies' mainframe software pricing, adds hybrid, private cloud services | Network World

Test to see if this solves my formatting problem with this list (only).Please pardon the interruption. CharlesSent from a mobile; please excuse the brevity. Original message From: Charles Mills Date: 5/16/19 8:53 AM (GMT-08:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Fwd:

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

This actually is a "truncated ellipsis". Syntatically, it is not present. The below example is pseudo-code for the actual dfdss syntax/parameters. -Original Message- From: IBM Mainframe Discussion List On Behalf Of John Dawes Sent: Thursday, May 16, 2019 12:19 PM To:

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Alan,Could you confirm the following:a) after DSN=datasetname1. is it a period or a comma?b) in the statement Inddd=indd1outdd=outdd1 should there be a space between the indd1 and outdd?b) after the outdd1.. is there something else I should tack on? On Thursday, 16 May 2019, 4:54:38 pm

Re: Fwd: IBM 'cloudifies' mainframe software pricing, adds hybrid, private cloud services | Network World

"First, IBM rolled out  z/OS Container Extensions (zCX), which makes it possible to run Linux on Z applications that are packaged as Docker Container images on z/OS. "Linux under z/OS.Charles  Original message From: Mark Regan Date: 5/16/19 5:53 AM (GMT-08:00) To:

Re: [External] Re: Ancient DASD connectivity

On Wed, 15 May 2019 18:12:19 -0500, Tom Marchant wrote: >The s/360 POO (available on bitsavers), says, >"A control unit may be housed separately or it may be physically >and logically integral with the I/O device." The classic example of early CU integration was the 2701 communications

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

I just reread the manual. INDDNAME is OK. My other question still arises. Are both datasets on the same volume? Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Pommier, Rex Sent: Thursday, May 16, 2019 11:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Rex,I tried both INDDNAME & PHYSINDD as well.  I can confirm that both dsns are on the same volume.Maybe you can try a test to see if you can do a successful Physical backup of 2 dsns.I am curious if it works for you.  I am running V2R02.0  On Thursday, 16 May 2019, 4:47:56 pm UTC,

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Rex, No, there is none. As I had mentioned before, if I execute the job to select 1 dsn it works, however if I try with 2 or more dsns the job fails.  I suspect that DFDSS doesn't support a phyiscial dataset backup for more than 1 dsn.   On Thursday, 16 May 2019, 3:26:44 pm UTC, Pommier,

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

John, Do you need to change your INDDNAME to PHYSINDD? The 2.2 manual indicates that INDDNAME is used for full or track copying and PHYSINDD is used for datasets. Are both the datasets you're going after on the same volume? Rex -Original Message- From: IBM Mainframe Discussion List

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Alan,I'll try it out.  The only drawback is that I will be using more than 1 tape to backup the dsns.In your example I will be using 2 tapes. On Thursday, 16 May 2019, 4:54:38 pm UTC, Allan Staller wrote: Try this: //INDD1 dd //INDD2 dd . //OUTDD1 dd //OUTDD2 dd .

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Try this: //INDD1 dd //INDD2 dd . //OUTDD1 dd //OUTDD2 dd . //SYSIN DD * Parallel DUMP DSN=datasetname1. Inddd=indd1outdd=outdd1 DUMP DSN=datasetname2. Inddd=indd21outdd=outdd2 HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of

Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP

Yup. 2 datasets backed up in parallel to two separate tapes. -Original Message- From: IBM Mainframe Discussion List On Behalf Of John Dawes Sent: Thursday, May 16, 2019 12:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [External] Re: DFDSS QUESTION - PHYSICAL DATASET BACKUP