I always take a peek at the DCB attributes of the tersed file and preallocate the same on the receiving system. FTP is then simply binary and get/put into the newly allocated file.
On Sun, Apr 22, 2018 at 11:52 PM, CM Poncelet <[email protected]> wrote: > 'm afraid I can't help much with this. I FTP'd from mainframe to > mainframe server, but not to/from my PC (I used TN3270 Plus or QWS3270 > for that). > > However, from vague memory, tersed files used to have to be RECFM=FB > BLKSIZE=6144 LRECL=1024 and the PGM=FTP step's SYSIN required a LOCSITE > <parms> and BINARY before the "GET <to DSName> '<from DSName>' (REPLACE" > card. The PGM=TRSMAIN,PARM=UNPACK ran as a separate step, afterwards. > > Cheers, CP > > > On 21/04/2018 10:27, Wayne Bickerdike wrote: > > I always terse the dump first, seems problematic if you don't. > > > > ADRDDSU DUMP, TERSE, FTP in Binary. > > > > Reverse the process on the next MVS platform. > > > > On Sat, Apr 21, 2018 at 4:03 PM, CM Poncelet <[email protected]> > wrote: > > > >> (a) Is the original ADDRSSU dump dataset still on the mainframe? If yes > >> transfer it to a *.dat (or *.bin) file on the PC, using e.g. TN3270 > >> Plus, and as binary (no EBCDIC to ASCII). You should then be able to > >> upload that from the PC to a preallocated mainframe dataset (specifying > >> BLKSIZE=27998). > >> (b) If the original dump dataset is no longer on the mainframe, *how* > >> was it transferred to the PC and to what file extension? If not to .dat > >> or .bin and the PC's OS is Windows, the file will need to be renamed to > >> *.dat (or *.bin) *after* it has been backed up 'just in case'. You > >> should then be able to upload it to a preallocated mainframe dataset > >> with BLKSIZE=27998 using e.g. TN3270 Plus. > >> (c) Else, please explain how the dump dataset was uploaded to the PC and > >> to what file name.extension - and also what the PC's OS is. > >> > >> Thanks, CP (retired sysprog) > >> > >> > >> > >> On 20/04/2018 15:35, Jerry Paper wrote: > >>> Hello all, > >>> > >>> this one is for the old-timers on the list (I guess :). > >>> A colleague has made a logical data set DUMP of important data and > >> downloaded to his PC in binary (by mistake, without additional steps). > As > >> expected, after uploading from PC to z/OS, the format is broken, and > >> ADRDSSU doesn't recognize the DUMP (uploaded as blksize=27998, lrecl=0, > >> recfm=u). > >>> Any recovery ideas for this situation, how to recover the PC data to a > >> RESTORE-able dataset? :) > >>> Thanks! > >>> > >>> Jerry > >>> Mainframe Operations > >>> > >>> ---------------------------------------------------------------------- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to [email protected] with the message: INFO IBM-MAIN > >>> . > >>> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO IBM-MAIN > >> > > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
