I think OP could enlighten us considerably with an IDCAMS dump print of a few records from the mysterious sysmod. Something like
PRINT IDS() COUNT(10) DUMP Copy/past the output to this thread. I think we're all puzzled by the actual content. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Kurt Quackenbush Sent: Friday, September 21, 2018 7:10 AM To: [email protected] Subject: (External):Re: RECEIVE USERMOD IN BINARY On 9/20/2018 12:59 PM, Tom Conley wrote: > On 9/20/2018 12:02 PM, Lizette Koehler wrote: >> When a USERMOD is supplied like this, here is what it is >> >> IBM Creates on their end. They use TSO XMIT to create a transport >> file. You Download and UPLOAD in BIN format. >> >> On the MF Side the attributes are usually >> >> LRECL=80, BLKSIZE=3120 and RECFM=FB. You Upload to that file on the >> Mainframe with a BIN attribute. This will prevent issues with the file. >> >> On the MF Side once the file is there, user TSO RECEIVE >> INDSN(whatever) >> >> I usually pre-allocate on the MF then use IND$FILE, or FTP, other >> program with a BIN as the way it is transmitted to the MF >> >> Lizette >> >> > > It may or may not be in XMIT OUTDATASET format. Fixes in .bin format > should be uploaded binary to an FB80 file and inspected to determine > what's in it. If SMP/E format, job done, proceed to RECEIVE. If > INMR06, then RECEIVE INDATASET it and inspect the results (if SMP/E > format, proceed to RECEIVE). If garbage, go back to IBM. > > Regards, > Tom Conley This, right here. +1 Kurt Quackenbush -- IBM, SMP/E Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
