Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver Path: utzoo!linus!decvax!harpo!floyd!vax135!cornell!uw-beaver!laser-lovers From: laser-lovers@uw-beaver (laser-lovers) Newsgroups: fa.laser-lovers Subject: Re: More 9700 experience Message-ID: <786@uw-beaver> Date: Mon, 2-Jan-84 16:23:07 EST Article-I.D.: uw-beave.786 Posted: Mon Jan 2 16:23:07 1984 Date-Received: Sat, 7-Jan-84 01:24:02 EST Sender: root@uw-beave Organization: U of Washington Computer Science Lines: 28 From HEDRICK@RUTGERS.ARPA Mon Jan 2 13:23:02 1984 I do not understand the comment that JES is unable to pass all EBCDIC characters. We print Scribe output files, which use metacodes. These files are effectively binary, so the fact that they print correctly seems to indicate that every 8-bit combination can be printed. We use a separate forms type, since the 9700 must be started in a separate mode. But we do not open the device directly. The precautions that we have to take should not be applicable if you are really printing EBCDIC, as opposed to Scribe metacodes (which are in fact internal Xerox ASCII): - Be careful about DCB parameters. I don't recall which we use, but if you aren't careful, JES will add trailing blanks. I think we use VB, with machine carriage control instead of ANS (to cause JES to do the minimum amount of processing). - If you are printing ASCII on the 9700, be careful of the ASCII character that looks like an EBCDIC blank. If you end a line with it, JES may strip it. (We add an extra trailing ASCII blank in this case.) - If you are printing ASCII on the 9700, do something to keep JES from supplying burster pages, since theese will be in EBCDIC. We have hacked JES so that a certain SYSOUT class does not get burster pages. Under MVS/SP, JES seems to have a user exit that would make this change very easy. We are using MVS with JES2. We have used both MVS and MVS/SP. I think our MVS goes back to something like 8201. Our MVS/SP is quite recent. -------