Spring 1989 VAX SIG TAPE SUBMISSION [Update: formerly VAX-380] [see text at bottom of this file] Kent C. Brodie MIS Department Medical College of Wisconsin 8701 Watertown Plank Road Milwaukee, Wisconsin. 53226 Phone: (414) 257-8769 (414) 778-4561 BITNET: 7113BROD@MUCSD KEYWORDS for this submission: LASER, HP, LASERJET, PRINTER, FORM, QUEUE SYSTEM MANAGER UTILITIES This directory contains the command procedure and support files needed to easily support a Hewlett Packard HP-2000 laser printer on a VAX. You can use these files to support other laser printers as well, but some modules may have to be changed (Laserjet, Laserjet+ escape sequences are different in some areas). In any case, I hope this is a good example on how to manage a laser printer and its many available attributes. Additionally, this directory contains a few handy DCL utilities for system managers, including both a MANUAL and AUTOMATIC idle process killer. (what submission would be complete without them?) Please note that this submission contains the files necessary to use the "/FORM=xxxxx" qualifier when sending standard print files to the HP2000. This allows you to print regular "standard" files in a variety of fonts/styles, without having to use special text-formatting programs, such as RUNOFF, etc. The files are as follows: [.HP2000] HPFORMS.COM A command procedure that sets up some of the "stock" forms for a HP-2000 printer. Form names/numbers may have to be modified so they do no clash with definitions already present at your site. The procedure is fully commented. Sample form names are "PRESTIGE1" or "COURIER2". [.HP2000] REMOTEPRT.COM A sample command procedure that shows how we set up our print queue for the laser printer. Our site has a 2-node clustered system, with the printer port residing on a DECserver. This isn't really an official part of this submission - it is included only for completeness. [.HP2000] SYSDEVCTL.TLB A device-control text library of various tiny modules that control the HP-2000 printer. (Portrait vs. Landscape, 6 LPI vs. 8 LPI, etc). HPFORMS.COM uses various combinations of the device modules to totally define the form of choice. If you are already heavily using SYSDEVCTL.TLB, you may wish to rename this file. This file should belong in the directory SYS$LIBRARY. [.HP2000] [.MODULES] This directory contains all of the text modules that comprise the file SYSDEVCTL.TLB. You may wish to keep these so that you can modify them (for another printer perhaps), or add to them and thus have the entire source in case SYSDEVCTL.TLB gets trashed. [.HP2000] BARCODE_EXAMPLE.TXT A sample text file that uses the "W" font cartridge that we happen to have installed on our printer. The example is right out of the book that came with the cartridge. If you would ever get that cartridge, this would be a nice sample to have. Notes: HPFORMS.COM does NOT contain all of the possible forms that you can define. For example, Prestige Elite Italic is not defined because we have no use for it. It is simple enough to use however, all you do is look at how HPFORMS.COM extracts the necessary modules to compile the form. In this example, you would use one of the forms set up for PRESTIGE, and substitute the STY_ITALIC module for the STY_UPRIGHT one. ==================================================================== Update: 5/1/89 Formerly VAX-380. This is all of the old stuff, plus: The newest "form" for the HP2000 that has been included is the "shaded" greenbar (form name: GREEN1). If you've modified a previous copy of HPFORMS.COM, all you gotta di is extract the bottom-most portion of the new file, and include it in yours. Nothing else has been changed. Also, I've included the following as a bonus (why not?): KILL.COM A **MANUAL** idle interactive process killer. (how's THAT for a switch?). This is an extremely handy and quick utility that shows you each user, and asks if you want to knock that process off of the system. (you also get to see GETJPI info, such as username, PID, and IMAGE). The nicest part of this deal is that all "kills" are logged into (appended to) a text file, so that you have a record of who has to be knocked off a lot.... JKILLER.COM Slightly modified JKILLER.COM (from "ARIS") that can run under a cluster environment that shares disks. DIALUP.COM Tiny dcl that shows you all of the interactive DIALUP users that are on the system. ("are all of my modems in use?"). Note: All three of these DCL files refer to a logical name called "MCW$SYS", which is our common utilities directory. You can create your own assignment for MCW$SYS, or simply change it to your own site's naming conventions.