Re: trying to reload a pdse after it has been unloaded and ftp'd

I am not going to be doing PUT after the dump. The PUT is just to manually load some test data from a 3rd lpar. I have to use GET on the unloaded dump receiving lpar because the lpar creating the dump is prevented from doing a PUT to another lpar - It was set up to be a one way street only.

Re: trying to reload a pdse after it has been unloaded and ftp'd

I forgot to change the DCB info for the untersed datatset. It is working now - Thanks Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jackson, Rob Sent: Wednesday, May 16, 2018 4:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:

Re: trying to reload a pdse after it has been unloaded and ftp'd

Also, you should consider using a FTP PUT as the second step of the dump-creating job, if the FTP server is running on your target system. The FTP client does a good job of setting the SITE command appropriately for you. Then you just have to worry about setting size on the target, if the

Re: trying to reload a pdse after it has been unloaded and ftp'd

That looks like the DCB for a tersed dataset. DSS would be creating RECFM=U and BLKSIZE=27998 on disk. Try this instead: LOCSITE VARrecfm LRECL=27998 RECFM=U BLKSIZE=27998 First Tennessee Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List

Re: trying to reload a pdse after it has been unloaded and ftp'd

I used mode b type e and ADRSSSU is not recognizing the INPUT file ADR389E (001)-TDDS (07), INVALID INPUT ON DDNAME IN, INPUT DATA SET NOT PRODUCED //RESTFAEXEC PGM=ADRDSSU,COND=(0,NE) //SYSPRINT DD SYSOUT=* //IN DD

Re: trying to reload a pdse after it has been unloaded and ftp'd

On Wed, 16 May 2018 16:50:43 +, Barkow, Eileen wrote: >THANK YOU Lionel! >The TERSE/UNTERSE worked. >Although I think that these utilities should be able to work on their own. > +1 Archivers such as IEBCOPY, ADRDSSU, TRSMAIN, ... should generate portable archives which can be transmitted

Re: trying to reload a pdse after it has been unloaded and ftp'd

Thanks a lot for type e and mode b - I remember using them for something or other in the past. Getting rid of the terse will help. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jackson, Rob Sent: Wednesday, May 16, 2018 2:09 PM To:

Re: trying to reload a pdse after it has been unloaded and ftp'd

We DSS dump and FTP hundreds of PDSs and PDSEs every day (don't ask), both text and loadlibs. From z/OS to z/OS you don't need to worry about tersing for portability. You just need 'type e' and 'mode b' in your FTP control cards. First Tennessee Bank Mainframe Technical Support

Re: trying to reload a pdse after it has been unloaded and ftp'd

There is a 'mput' ftp command to ftp all the members but it takes a long time. I am not sure about the MVSPUT option. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Horein Sent: Wednesday, May 16, 2018 1:56 PM To:

Re: trying to reload a pdse after it has been unloaded and ftp'd

Forgot to include the link: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.halu001/mvsputsubcmd.htm On Wed, May 16, 2018 at 12:55 PM, Steve Horein wrote: > Although I haven't used it much, it would seem ftp's MVSPUT 'XCICS.FA.HIST' >

Re: trying to reload a pdse after it has been unloaded and ftp'd

Although I haven't used it much, it would seem ftp's MVSPUT 'XCICS.FA.HIST' 'XCICS.FA.HIST.RESTORED' (REALLOC could eliminate some steps? On Wed, May 16, 2018 at 10:57 AM, Barkow, Eileen wrote: > I am trying to reload an unloaded pdse after it has been ftp'd to a target

Re: trying to reload a pdse after it has been unloaded and ftp'd

You don't really need to worry about the XMIT userid - just specify anything at all, ABCD.DEFGHIJK will do. The basic idea is that you are using XMIT to set up a transportable copy of the PDSE and that you will be using FTP to send the file, not actually XMITting it. HTH Peter -Original

Re: trying to reload a pdse after it has been unloaded and ftp'd

You can easily use TSO Transmit (XMIT) to a dataset thus: XMIT x.y DS(input) ODS(xxx.xmit) Where x.y is node.userid but that can be anything as it is just going to a dataset -- Lionel B. Dyck (Contractor) < Mainframe

Re: trying to reload a pdse after it has been unloaded and ftp'd

I was going to try XMIT as a last resort but the TERSE/UNTERSE steps added to the ADRDSSU jobs worked. I think that XMIT needs a USERID to send to and there are different userids involved in each lpar. -Original Message- From: IBM Mainframe Discussion List

Re: trying to reload a pdse after it has been unloaded and ftp'd

You can FTP an XMIT unload. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Barkow, Eileen Sent: Wednesday, May 16, 2018 11:57 AM To:

Re: trying to reload a pdse after it has been unloaded and ftp'd

For this I have always used ADRDSSU and then Terse'd the results before doing a binary FTP transfer - all while retaining the Terse DCB. Then unterse and ADRDSSU restore and it has worked. Hope this helps -- Lionel B. Dyck

trying to reload a pdse after it has been unloaded and ftp'd

I am trying to reload an unloaded pdse after it has been ftp'd to a target lpar. there is a known problem with this using IEBCOPY UNLOAD/RELOAD described on IBMLINK and none of the work-around overrides to ftp work. TRSMAIN/TERSE does not support PDSE. So I switched over to ADRDSSU. I dump a