Thank you. We are indeed using COBOL with the AFTER option. However, I am unsure what you are suggesting to me. Perhaps some more details are in order. We are zipping in order to send the file to a vendor to use on a non-hp3000 machine. The vendor uses the carriage control programmatically to understand such things as page breaks. We originally downloaded the file to a PC and used PKZIP to zip it prior to FTP'ing it. This scheme was successful. Carriage Control was perserved. In order to automate the process, we began using the ZIP utility on the 3000. To our dismay, the carriage control was not perserved. In doing some research, we zipped and unzipped the file on the 3000. The following are before and after pictures of two of the records. Before: 0000: 8120 2020 2020 5858 5858 5858 5858 5858 . XXXXXXXXXX 0008: SAME: TO 0010-1 0010: 5858 5858 2020 2020 2020 2020 2020 2020 XXXX 0018: SAME: TO 0020-1 0020: 2020 2039 3939 2C39 3939 2C39 3939 2E30 999,999,999.0 0028: 30 0 JCMSTMTB RECORD 305 (%461, #131) 0000: 3120 2020 2020 2020 2020 2020 2020 2020 1 0008: SAME: TO 0028-1 0028: 20 After: 0000: 2020 2020 2058 5858 5858 5858 5858 5858 XXXXXXXXXXX 0008: SAME: TO 0010-1 0010: 5858 5820 2020 2020 2020 2020 2020 2020 XXX 0018: SAME: TO 0020-1 0020: 2020 3939 392C 3939 392C 3939 392E 3030 999,999,999.00 JCMSTMTA RECORD 305 (%461, #131) 0000: SAME: TO 0000-1 "Tracy Pierce" <[log in to unmask]> wrote in message news:98b8e101aui@enews4.newsguy.com... > I don't know the exact details of this, but this will probably work; this > all assumes you're using COBOL and the AFTER [ADVANCING] <lines> clause. > > (In the old days, at least) the hardware, such as a 2566, wants to print, > then advance. This works poorly from a programming standpoint; thus the > AFTER clause. The COBOL compiler I believe, would see that you're using > post-print spacing, and would insert (after a "C" (%103) record which > overrides perf skipping) an "A" (%101) record which sets the pre-space > movement option. > > In the old days when you LISTed a spoofle via SPOOK, you'd at least get to > SEE the C & A records; when you'd TEXT the file, the C & A records would get > stripped. Nowadays I dunno ANY way to SEE the C & A records, and when you > grab the spoofle, they're not there. So just put them back in, and your > CCTL will work as it did before, assuming you still have the CCTL option > attached to the file. > > I'm sure 90% of that is technically marginal or just plain wrong, but the > fix works great; I got bought lots of beers for fixing critical spoofles > this way. > > YMMV; good luck! > > > > > -----Original Message----- > > From: JIM McINTOSH [mailto:[log in to unmask]] > > Sent: Friday, March 09, 2001 9:32 AM > > To: [log in to unmask] > > Subject: Loss of Carriage Control when Using ZIP on the 3000 > > > > > > Hello to all, > > > > When we use the ZIP utility on a file that contains carriage > > control, the CC > > is removed. If we download the file to a PC and use PKZIP, > > the carriage > > control is preserved. Does anyone have a explanation and, > > better yet, a way > > to preserve CC when zipping on the 3000? > > > > Thank you. > > > > Jim McIntosh > > >