Date: Thu, 7 Jan 1999 11:30:15 -0800
Reply-To: Paul OldenKamp <paul.oldenkamp@BOEING.COM>
Sender: "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From: Paul OldenKamp <paul.oldenkamp@BOEING.COM>
Organization: The Boeing Company
Subject: More (Spooling) OS/390 SAS/GRAPH Output to a HP Printer (Deskjet
720C)
Content-Type: text/plain; charset=us-ascii
Hello SAS-Ler's:
Like SI the Boeing Company closes down most of its operations during
the period between Christmas and New Years so I was gone and did not
participate in the thread started by Dave Oesper on printing graphs
on a HP printer through a NT print server.
Dave's question was very timely for me since I had been working for
a couple of weeks to do the same thing he was attempting and had
opened a problem tracking number with SI on 12/22. I now have things
working and thought some of you might find what I have learned
helpful and you might be able to help me with some follow-on questions
that I still have.
OBJECTIVE: What I wanted to do is have an interactive Display
Manager environment set up so I can print text in the pgm and
output windows and print graphs from the graph window by simply
entering the 'print' command in each of those windows.
ENVOIRNMENT: I am using SAS, Version 6.09, TS455 on two different
mainframes. Let's call one the KKMF and the other DDMF. My NT
print server is connected to KKMF using VPS. My printer is a HP
MP5si MX PS. The printer has a VPS name like U1234 and a LU name
like NQ9900P9 defined on the KKMF mainframe. I use SAS's Emulus
software running on a Solaris server as my mainframe emulator and
use Hummingbird's HCL Exceed to provide X-windows emulation on my
desktop PC to get to the Sun. We use SAS, Version 6.12, TS020 on
the PC's for some of our SAS programming and send text and
postscript graphs to the same NT print server and printer I want
to use from the mainframe.
RTFM: SI Tech Report TS-519, "Spooling Mainframe SAS/GRAPH Output
to ASCII Printers" and SAS Notes V6-GPROTOCOL-6756 and
V6-GPROTOCOL-E733 document how to set things up.
HOW IT WORKS: Here is the program that works from display manager:
filename gsasfile sysout=B dest=U1234;
goptions reset=all dev=IBM3179 target=LJ3SIPS gsfname=gsasfile
gsfmode=replace gsflen=80 gprotocol=sasgpasc trantab=gtabcms;
run;
proc gtestit
pic=1;
run;
/* subtop to this point to display graph and then 'print' if OK */
/* 'end' graph window and execute following line */
filename gsasfile clear;
The sysout class 'B' is set up with 'VPS tranparency'. It also seems
to work for me when I use sysout=A and gprotocol=sasgpstd and I let VPS
do the EBCDIC to ASCII conversion even though SAS Tech Support
thought this was unlikely to work. The reason I opened the tracking
number with tech support is that I would always get a text listing
of the postscript commands printed instead of a graph. What I have
learned is that some of the SAS/GRAPH drivers for HP postscript
printers on the mainframe will produce text of the commands and
others will produce a graph. I have also learned that the HPGL and
PCL device drivers work with this printer. All of the device
drivers produce graphs when used on the Windows95 PC and are sent
to the printer through the Windows print drivers. Here are the
mainframe drivers I tested and my results:
driver sysout gprotocol result note
HPGL3SI B sasgpasc OK--Graph Printed HPGL driver, monochrome
HPGL3SI A sasgpstd ??--Graph Printed No straight lines in graph
HPLJ3SI B sasgpasc OK--Graph Printed PCL driver, monochrome
LJIVPS B sasgpasc Postscript Commands Works at SI
LJIV600 B sasgpasc ??--Graph Printed 'TOP' is the only text
LJ3SIPS B sasgpasc OK--Graph Printed
LJ3SIPS A sasgpstd OK--Graph Printed
LJESIPSL B sasgpasc OK--Graph Printed
PS B sasgpasc Postscript Commands Works on PC
PSL B sasgpasc Postscript Commands "
PSEPSF B sasgpasc Postscript Commands "
PS300 B sasgpasc Postscript Commands "
REMAINING PROBLEM: On the DDMF machine we route batch job output by
using the printer name of KKMF.U1234. In the SAS filename statement
and in the DEST field of the FSFORMS subsystem only eight characters
are allowed for this name. In the past I used the LU name to send
output to an SNA GDDM printer but the LU name never seems to work
with this VPS printer.
V7 QUESTION: What will happen with the SAS/GRAPH device drivers in
Version 7? Will the behavior of these device drivers remain as I
found it in 6.09E?
--
----------------------------------------------------------------------
// Paul OldenKamp
// Boeing Commercial Airplane Group .
// P. O. Box 3707, MS 36-40 |\
// Seattle, WA 98124-2207 | \____oo_
//==========================================((__| /___>
// ___ ___ ___ ___ __ | //
// /__// //__ / /\ // _ |//
// /__//__//__ _/_ / //__/ ''
//
