Date:         Wed, 5 Mar 1997 10:43:53 -0500
Reply-To:     TIM.LATENDRESS@LATENT62.CUSTOMS.SPRINT.COM
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Tim Latendress <TIM.LATENDRESS@LATENT62.CUSTOMS.SPRINT.COM>
Subject:      Re: Mainframe SAS/GRAPH Device Driver

Neil E. Ervin <ervineis@AOL.COM> wrote:
 
>In my very large company we have a device driver 'GOPTIONS
>DEVICE=B1LJ4A' that noone seems to remember how it was set up.  I need
>to set up a similiar driver but for a 4224 printer.  Is there a way for
>me to print out the contents (source code) of this driver?  I know that
>there are standard 4224 drivers available, but I need one that can
>format the graphics output to SYSOUT so that it can go into the JES2
>held queue.  We have a product named TSPRINT that will then route the
>held queue item to the printer.  Thanks. Neil. Neil E. Ervin,  Banc One
>Financial Card Services,  Columbus, Ohio
 
Neil,
 
The standard SAS/GRAPH device drivers can be found in SASHELP.DEVICES.
But, it sounds like you're using a custom device which should be located
in a catalog called DEVICES that is in a library assigned a libref of
GDEVICE0 (that's a zero on the end). If so, you can obtain the
parameters by submitting:
 
   proc gdevice catalog=GDEVICE0.DEVICES nofs;
      list B1LJ4A;
   quit;
 
You can copy to a new driver and modify:
 
   proc gdevice catalog=GDEVICE0.DEVICES nofs;
      copy B1LJ4A newname=MY4224;
      modify MY4224 description='My custom 4224 driver';
   quit;
 
Better yet, if you're comfortable in Display Manager, this will take you
interactive [see SAS/GRAPH Software Reference Volume 2] where you can
browse, copy, modify, etc using the various parameter windows:
 
   proc gdevice catalog=GDEVICE0.DEVICES;
   run;
 
 
That aside, I'm not sure what you mean by "format the graphics for
SYSOUT". When creating SAS/GRAPH output for a printer, you create a
graphics stream file (GSF) that is controlled by a variety of GOPTIONS.
This GSF contains the codes used by your device to recreate the
SAS/GRAPH output. There are quite a few additional parameters that you
can modify in the driver that will create a GSF which has everything the
printer needs. And, unless it is doing something magical, you might be
able to avoid the TSPRINT step altogether. Just a suggestion.
 
 
HTH,
 
Tim Latendress
latendress@latent62.customs.sprint.com