Another way to copy a PDS to the pc is with ftp. cd to a pc directory and run a command line ftp program initiated from the pc and issue commands: (I use MOVE IT FREELY): cd 'MAINFRAME.PDS' ftp ftp parms HOST NAME PORT mget(*)
Each member will be downloaded to the pc directory. Eileen Barkow ebar...@doitt.nyc.gov CICS systems Desk: 718-403-8649 Cell: 917-436-0508 -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Joe Monk Sent: Monday, April 19, 2021 8:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Format PDS unloaded on an CD OK ... maybe now we're getting somewhere... I think we are having a case of deja vu here. Going back thru the archives I found where the exact same dataset was created in 2007: -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Day Sent: Thursday, May 24, 2007 5:34 PM To: ibm-m...@bama.ua.edu Subject: IEBCOPY Unloaded dataset to PC and back again...not successful I used IEBCOPY to create a sequentail backup of an ISPF panel library. I then used IND$FILE to transfer the dataset to my PC. Thought I'd test the backup out by transferring back to the mainframe, and got the following when I tried to use IEBCOPY to load the members back. STEP1COPY INDD=SYSUT1,OUTDD=SYSUT2 GENERATED STATEMENT IEB1128I *** COPYR1 (1ST PDSU PHYSICAL RECORD) 009400 1810 180C0100 00CA6D0F 02001810 | _ | 009410 0010 00509000 1810 3030200F 7FF8 | 8| 009420 0020 0D0C000F E5A2 2250 0002006B |Vs,| 009430 0030 008F 0080 0F000B08 A912 |z | 009440 0040 7F00 80807FF8 8800 0012 | 8 h | 009450 0050 6A78 1810 0200 9440 | | m | 009460 0060 6AA8 0C0067E8 6AA0 8800 | |y Y | h | 009470 0070 0002 3F000900 || 009480 0080 0612 20007FF8 | 8| 009490 0090 || IEB120I SYSUT1 VALIDATION ERROR IEB178I NOT AN IEBCOPY UNLOADED DATA SET - 1ST PHYSICAL RECORD NOT 64 BYTES LONG - ACTUAL VALUE IS X'001810' The IND$FILE for the GET or PUT operation did not specify CRLF as a parameter. Can someone tell me what I did wrong, or if there is a 'better' way to backup PDS data on a PC. Thanks. --Dave Day So, now you know what you have. An ISPF panel library, that was unloaded via IEBCOPY, then IND$FILE to a PC without specifying CRLF then back to the mainframe. Joe On Mon, Apr 19, 2021 at 4:04 AM Hilario Garcia <libr...@gmail.com> wrote: > Hello, > > Thank you very much for your answer. I had already tried the solution > you recommended and it gave me the following problem: > > IEBCOPY COPY INDD=SYSUT1,OUTDD=SYSUT2 GENERATED STATEMENT > > IEB1128I *** COPYR1 (1ST PDSU PHYSICAL RECORD) > > 0094A0 FFF8 00000000 00000000 7FE40000 7FE00000 | "U "\ | > > 0094B0 0008 00CA6D0F 020018B0 00509000 00807FF8 | _ & "8| > > 0094C0 0018 3030200F 00007FF8 2721000F E5A20000 | "8 Vs | > > 0094D0 0028 22520000 0002006B 00DE0000 00800000 | , | > > 0094E0 0038 01000B07 69300000 7F000000 80807FF8 | " "8| > > 0094F0 0048 00008800 0011F000 00006540 00007FE4 | h 0 "U| > > 009500 0058 02000000 000094E8 00006570 0C000014 | mY | > > 009510 0068 00006568 00008800 00000000 00000000 | h | > > 009520 0078 00000000 16000400 0611F000 20007FF8 | 0 "8| > > 009530 0088 00000000 00000000 00000000 00000000 || > > 009540 0098 00000000 00000000 00000000 00000000 || > > IEB120I SYSUT1 VALIDATION ERROR > > IEB178I NOT AN IEBCOPY UNLOADED DATA SET - 1ST PHYSICAL RECORD NOT 64 > BYTES LONG > IEB1030I DDNAME SYSUT1 REFERS TO PDSU DATA SET ON VOLUME SSSSSS NAMED > IBMUSER. > IEB1030I DDNAME SYSUT2 REFERS TO PDS DATA SET ON VOLUME SSSSSS NAMED > IBMUSER. > IEB166I NO MEMBERS LOADED TO DATA SET REFERENCED BY SYSUT2 > > IEB151I JOB HAS TERMINATED WITH ERROR(S) > > IEB147I END OF JOB - 8 WAS HIGHEST SEVERITY CODE > > > Do you recommend any other possible solution. > > Thank you very much in advance. > > Kind Regards > > Hilario > > El lun, 19 abr 2021 a las 10:29, Styles, Andy (ITS zPlatform Services) > (< > 000000d68f765d25-dmarc-requ...@listserv.ua.edu>) escribió: > > > Classification: Public > > > > I wonder if these are IEBCOPY unload format - that is, IEBCOPY from > > a PDS to a PS. It's been years since I had to deal with those, > > probably since > I > > installed products directly from a vendor tape (one of those round > > things with the write-protect ring). > > > > IEBCOPY seems to create unload format dasd datasets (here, at least) > > as > > > > Organization . . . : PS > > Record format . . . : VS > > Record length . . . : 32736 > > Block size . . . . : 32740 > > > > Worth uploading one of those files as binary and then using an > > IEBCOPY PS to PDS to reload it? > > > > Andy Styles > > z/Series System Programmer > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > > Behalf Of Hilario Garcia > > Sent: 19 April 2021 06:42 > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Fwd: Format PDS unloaded on an CD > > > > -- This email has reached the Bank via an external source -- > > > > > > ---------- Forwarded message --------- > > De: Hilario Garcia <libr...@gmail.com> > > Date: lun, 19 abr 2021 a las 7:40 > > Subject: Format PDS unloaded on an CD > > To: <IBM-MAIN@listserv.ua.edu> > > > > > > Hello, > > > > Thank you very much for your contributions. > > I have done multiple tests with different utilities (XMIT, FTP, IND > > $ > FILE, > > AMATERSE) and I have not been able to download them in a valid format. > > Attached I send in hexadecimal format the beginning of one of the > > PDS (loaded as FB, lrecl = 80) and it seems that at the beginning of > > the file is the directory of a PDS partitioned file. If the file is > > loaded as FB > and > > 80 bytes long, you can see the code in EBCDIC format. The original > > file > is > > in format binary and I have loaded it in binary. > > > > I would appreciate your help in this regard. > > > > Thank you very much in advance. > > > > Kind Regards > > > > Hilario > > > > > > > > -------------------------------------------------------------------- > > -- 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 Lloyds > > Banking Group plc. Registered Office: The Mound, Edinburgh EH1 > 1YZ. > > Registered in Scotland no. SC95000. Telephone: 0131 225 4555. > > > > Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. > > Registered in England and Wales no. 2065. Telephone 0207626 1500. > > > > Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. > > Registered in Scotland no. SC327000. Telephone: 03457 801 801. > > > > Lloyds Bank Corporate Markets plc. Registered office: 25 Gresham > > Street, London EC2V 7HN. Registered in England and Wales no. 10399850. > > > > Scottish Widows Schroder Personal Wealth Limited. Registered Office: > > 25 Gresham Street, London EC2V 7HN. Registered in England and Wales no. > > 11722983. > > > > Lloyds Bank plc, Bank of Scotland plc and Lloyds Bank Corporate > > Markets plc are authorised by the Prudential Regulation Authority > > and regulated > by > > the Financial Conduct Authority and Prudential Regulation Authority. > > > > Scottish Widows Schroder Personal Wealth Limited is authorised and > > regulated by the Financial Conduct Authority. > > > > Lloyds Bank Corporate Markets Wertpapierhandelsbank GmbH is a > wholly-owned > > subsidiary of Lloyds Bank Corporate Markets plc. Lloyds Bank > > Corporate Markets Wertpapierhandelsbank GmbH has its registered > > office at Thurn-und-Taxis Platz 6, 60313 Frankfurt, Germany. The > > company is registered with the Amtsgericht Frankfurt am Main, HRB > > 111650. Lloyds > Bank > > Corporate Markets Wertpapierhandelsbank GmbH is supervised by the > > Bundesanstalt für Finanzdienstleistungsaufsicht. > > > > Halifax is a division of Bank of Scotland plc. > > > > HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. > > Registered in Scotland no. SC218813. > > > > > > > > This e-mail (including any attachments) is private and confidential > > and may contain privileged material. If you have received this > > e-mail in > error, > > please notify the sender and delete it (including any attachments) > > immediately. You must not copy, distribute, disclose or use any of > > the information in it or any attachments. Telephone calls may be > > monitored or recorded. > > > > > > -------------------------------------------------------------------- > > -- 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 ________________________________ 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
