Is the file on the mainframe FB/80/3120? Or at least FB/80? If it somehow has incorrect LRECL or RECFM, it'll look good when browsing it but its unusable.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Farley, Peter x23353 Sent: Thursday, July 11, 2019 9:30 AM To: [email protected] Subject: [External] Re: XMIT manager unable to decode INMR02 Did you set binary transfer on? FTP command "I" (letter eye)? I think that FTP message is because the mget encountered non-printable characters in one or more members and you were downloading in ASCII mode instead of in binary mode. HTH Peter -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jake Anderson Sent: Thursday, July 11, 2019 10:25 AM To: [email protected] Subject: Re: XMIT manager unable to decode INMR02 I did a HEX ON and checked , it looks good to me. Then I did the receive the same .XMI and restored the same in a PDS. Compared and look good . Not sure what is it still. Missing On Thu, 11 Jul, 2019, 6:20 PM Lizette Koehler, <[email protected]> wrote: > I would browse the dataset on the Mainframe and make sure the file is > intact. > > The first couple of records should have INR0 in the beginning of the > line > > If it does not - then it is not an XMI file. > > Next on the mainframe do a RECEIVE of the file and see if there are > any errors during that process. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > Behalf Of > > Jake Anderson > > Sent: Thursday, July 11, 2019 2:07 AM > > To: [email protected] > > Subject: XMIT manager unable to decode INMR02 > > > > Hi > > > > I am trying to open a .XMI file using XMIT manager and I get a > > unable to decode INMR02. > > > > The XMI was downloaded from Mainframe as binary > > > > Has anyone faced this problem? > > > > Any clue how it was fixed ? > > > > Jake -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
