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.
But thanks again for the help - TYPE E MODE B is what I need for the GET as 
well.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jackson, Rob
Sent: Wednesday, May 16, 2018 4:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 defaults are 
not acceptable.

First Tennessee Bank
Mainframe Technical Support


-----Original Message-----
From: IBM Mainframe Discussion List <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: [Originated Externally]Re: trying to reload a pdse after it has been 
unloaded and ftp'd

[External Email]

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 <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Barkow, Eileen
Sent: Wednesday, May 16, 2018 3:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: trying to reload a pdse after it has been unloaded and ftp'd

[External Email]

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
//RESTFA    EXEC  PGM=ADRDSSU,COND=(0,NE)
 //SYSPRINT  DD  SYSOUT=*
 //IN  DD DSN=PBCDOFP.FA.HIST.DUMPED,DISP=SHR


COMMAND INPUT ===>                                            SCROLL ===> P
EZA1701I >>> PASS
230 FTPPMSA is logged on.  Working directory is "FTPPMSA.".
EZA1460I Command:
EZA1736I mode B
EZA1701I >>> MODE B
200 Data transfer mode is Block
EZA1460I Command:
EZA1736I type e
EZA1701I >>> TYPE E
200 Representation type is Ebcdic NonPrint EZA1460I Command:
EZA1736I LOCSITE TR PRI=500 SEC=60
EZA1460I Command:
EZA1736I LOCSITE  LRECL=1024 BLKSIZE=27648 RECFM=FB EZA1460I Command:
EZA1736I GET 'XCICS.FA.HIST.DUMPED' 'PBCDOFP.FA.HIST.DUMPED' (REPLACE EZA1701I 
>>> PASV

-----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: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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


-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Barkow, Eileen
Sent: Wednesday, May 16, 2018 12:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: trying to reload a pdse after it has been unloaded and ftp'd

[External Email]

THANK YOU Lionel!
The TERSE/UNTERSE  worked.
Although I think that these utilities should be able to work on their own.


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Dyck, Lionel B. (RavenTek)
Sent: Wednesday, May 16, 2018 12:02 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: 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 (Contractor)  <sdg><
Mainframe Systems Programmer - RavenTek Solution Partners

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Barkow, Eileen
Sent: Wednesday, May 16, 2018 10:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] 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 dataset and am able to restore it on the same lpar.
However, when i ftp the dumped dataset to the remote lpar, the restore fails 
because the input dataset is not valid for ADRDSSU (tried ftp with both BIN and 
EBCDIC default).

both datasets (remote and local) look the same to me when browsing them and 
have the same dcb info.
does anyone know how to restore an unloaded pdse that has been ftp'd?

thanks in advance for any info.
****************************************
 Data Set Name . . . . : XCICS.FA.HIST.DUMPED
                                   General Data
  Management class . . : **None**
  Storage class  . . . : **None**
  Volume serial . . . : W1STG2
  Device type . . . . : 3390
  Data class . . . . . : **None**
  Organization  . . . : PS
  Record format . . . : U
  Record length . . . : 0
  Block size  . . . . : 27998
  1st extent tracks . : 1500
  Secondary tracks  . : 60

***original job used to create XCICS.FA.HIST.DUMPED******
 //DUMP     EXEC  PGM=ADRDSSU
 //SYSPRINT DD    SYSOUT=A
 //DASD1    DD    UNIT=SYSDA,VOL=SER=XCICX0,DISP=SHR
 //TAPE     DD    UNIT=SYSDA,
 //  DISP=(NEW,CATLG),DSNAME=XCICS.FA.HIST.DUMPED,
 //  SPACE=(TRK,(1500,60),RLSE)
 //SYSIN    DD    *
  DUMP  LOGINDDNAME(DASD1) OUTDDNAME(TAPE) -
     DATASET(INCLUDE(XCICS.FA.HIST)) WAIT(0,0)
 /*
//****************************************************
**job to restore after ftp of XCICS.FA.HIST.DUMPED to remote lpar******
 //RESTFA    EXEC  PGM=ADRDSSU COND=((0,NE),(0,EQ))
 //*EST    EXEC  PGM=ADRDSSU,PARM='TYPRUN=NORUN'
 //SYSPRINT  DD  SYSOUT=*
 //IN  DD DSN=XCICS.FA.HIST.DUMPED,DISP=SHR  //OUT  DD 
VOL=SER=W1STG2,DISP=SHR,UNIT=SYSDA
 //SYSIN     DD  *
   RESTORE INDD(IN) OUTDD(OUT) DATASET(INCLUDE(XCICS.FA.HIST)) -
   CATALOG -
  RENUNC(XCICS.FA.HIST,XCICS.FA.HIST.RESTORED) REPLACE  //
*********************************************************************************
PAGE 0001     5695-DF175  DFSMSDSS V2R02.0 DATA SET SERVICES     2018.136 11:13
  RESTORE INDD(IN) OUTDD(OUT) DATASET(INCLUDE(XCICS.FA.HIST)) -
  CATALOG -
 RENUNC(XCICS.FA.HIST,XCICS.FA.HIST.RESTORED) REPLACE ADR101I (R/I)-RI01 (01), 
TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE '
ADR109I (R/I)-RI01 (01), 2018.136 11:13:26 INITIAL SCAN OF USER CONTROL 
STATEMEN ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK 
ADR006I (001)-STEND(01), 2018.136 11:13:26 EXECUTION BEGINS ADR389E (001)-TDDS 
(07), INVALID INPUT ON DDNAME IN, INPUT DATA SET NOT PRODUCED ADR415W 
(001)-TDDS (02), NO DATA SETS WERE COPIED, DUMPED, OR RESTORED FROM ANY ADR006I 
(001)-STEND(02), 2018.136 11:13:26 EXECUTION ENDS ADR013I (001)-CLTSK(01), 
2018.136 11:13:26 TASK COMPLETED WITH RETURN CODE 0008 ADR012I (SCH)-DSSU (01), 
2018.136 11:13:26 DFSMSDSS PROCESSING COMPLETE. HIGHEST







  ________________________________

This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments. Please notify the sender immediately by reply e-mail and delete 
the e-mail from your system.


----------------------------------------------------------------------
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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN FIRST TENNESSEE

Confidentiality notice:
This e-mail message, including any attachments, may contain legally privileged 
and/or confidential information. If you are not the intended recipient(s), or 
the employee or agent responsible for delivery of this message to the intended 
recipient(s), you are hereby notified that any dissemination, distribution, or 
copying of this e-mail message is strictly prohibited. If you have received 
this message in error, please immediately notify the sender and delete this 
e-mail message from your computer.

----------------------------------------------------------------------
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

----------------------------------------------------------------------
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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to