There's also this problem trying to edit the dataset but I'm up to my stack depth in alligators already.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ISPF processor ended abnormally * * * * * * * * System abend code 0C4 * * * * Reason code 11 * * * * * * * * * * * * * * * * Note: The ABEND and REASON codes displayed above are * * * * HEXADECIMAL values for "SYSTEM" abends and DECIMAL * * * * values for "USER" abends. * * * * * * * * Enter HELP command for list of common ABEND codes. * * * * Press ENTER key for additional DIAGNOSTIC information. * * * * Enter END command to display primary option menu. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, January 15, 2013 12:44 PM To: [email protected] Subject: Re: Break a dataset into new record boundaries? On Tue, 15 Jan 2013 12:16:55 -0800, Charles Mills wrote: >Yeah, it seems to be working. Not sure yet. I think perhaps the apparent >blanks are just ISPF edit window dressing at the ends of the lines. It doesn't >know about short lines. > Of course, since you say the data are binary, a 0x40 at the end of a record (or where one was inadvertently broken) may be critical. Unfortunately, there's no way to tell ISPF not to add or remove trailing blanks. -- gil ---------------------------------------------------------------------- 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
