Downloading the PrintKit Savesets ------------------------------------------------------------------------- The downloadable kit for the PrintKit 2.3-7 software is a single self-extracting archive. Once you've transferred this file to your OpenVMS system, you run the file to unpack the individual components of the distribution, which consist of VMSINSTAL savesets and installation notes. Separate versions of the kit are provided for each of the OpenVMS hardware architectures, identified by their file types: PRINTKIT023-7.AXP_EXE Alpha systems PRINTKIT023-7.IA64_EXE Integrity systems PRINTKIT023-7.VAX_EXE VAX systems Each version contains a full kit -- once unpacked, it can be installed on any of the hardware architectures -- but each architecture requires its matching version of the self-extract code. The downloadable kits are binary files. Be sure to keep this in mind if you need to transfer them between systems. (For instance, use TYPE IMAGE with FTP.) They should appear on your OpenVMS system with fixed-length 512-byte records. For example, to download the PrintKit 2.3-7 distribution to an Alpha system, you select the PRINTKIT023-7.AXP_EXE kit. Once you've transferred this file to your system, run it: $ RUN PRINTKIT023-7.AXP_EXE inflating: printkit023-7.readme inflating: printkit023-7.a inflating: printkit023-7.b inflating: printkit023-7.c inflating: printkit023-7.d inflating: printkit023-7.e inflating: printkit023-7.f If you have any questions, send email to PRINTKIT@NLS.COM. Quick Start Installation ------------------------------------------------------------------------- Here are the steps required to install and configure the PrintKit software. You perform the installation using the VMSLICENSE and VMSINSTAL commands. After installing the software, you use the KITCP command, supplied with PrintKit, to configure the software for the printers on your system. Once installation and configuration are complete, PrintKit queues are available to all users on the system. If you are familiar with typical OpenVMS installation procedures, these instructions will give you a "quick start" with the PrintKit software. If you need additional information about installing or configuring the software, or you encounter problems, these instructions will direct you to additional information in the PrintKit User Manual. Installing PrintKit ------------------------------------------------------------------------- To install PrintKit you must be logged in to the SYSTEM account, or another account with privileges to create and modify files in the system directories. You can install the software on an active OpenVMS system without disturbing other operations. The PrintKit VMSINSTAL kit verifies that your system configuration allows the software to operate successfully, or tells you how to make any required changes. Changing your system's SYSGEN parameters may require a reboot. If you prefer to check your configuration before performing the installation, refer to page 5-3 of the PrintKit User Manual. Step 1. Register and Load License PAK Before installing PrintKit, use the VMSLICENSE command to register and load the license Product Authorization Key (PAK) supplied with your distribution kit. If you are replacing an existing PAK in the course of upgrading your PrintKit software, it is safest to delete the old PAK before registering the new one. When you do this, be sure all PrintKit queues are stopped, so the PAK is not in use. Otherwise, you may end up with an incompletely deleted license that interferes with the newly registered license. Once the queues are stopped, use the following command to delete the license: $ LICENSE UNLOAD PRINTKIT /PRODUCER=NORTHLAKE $ LICENSE DELETE PRINTKIT /PRODUCER=NORTHLAKE To load your new PrintKit license PAK, use the VMSLICENSE command: $ @SYS$UPDATE:VMSLICENSE When the license procedure prompts you, select option 1 and respond to the questions using the information from your PAK. Step 2. Install the PrintKit Software The VMSINSTAL command prompts you for the information needed to install PrintKit on your system. The installation displays progress messages, and upon completion it lists the files it has created or modified. To start VMSINSTAL, enter the following command. Make the appropriate substitution for the DEVICE and DIRECTORY when you enter the VMSINSTAL command. Specify OPTIONS N to review the release notes before performing the installation. $ @SYS$UPDATE:VMSINSTAL PRINTKIT023-7 device:[directory] Example: $ SYS$UPDATE:VMSINSTAL PRINTKIT023-7 BERT$DKA200:[ERIK.TEMP] Here are some tips to remember during the installation: o Enter a question mark (?) after any prompt to display help information. o Most prompts display a default response, enclosed in brackets ([]), which you can select by pressing RETURN. o You may cancel the installation at any time by pressing CTRL-Y. The system will do some cleanup, which may take some time. Do not type CTRL-Y during the cleanup -- this may stop the cleanup before it has removed all files from the installation, leaving an unusable combination of new and old files. VMSINSTAL asks you a series of questions as it installs the PrintKit software: o Are you logged in to the SYSTEM account? o Have you backed up your system disk? o Have you registered and loaded all your license PAKs with LMF? o Do you want to purge old PrintKit files? o Do you want to run the Installation Verification Procedure? o Do you want to copy definitions from your existing database? (Asked only when upgrading from a pre-2.3 version of PrintKit.) For more information on the VMSINSTAL utility, refer to the OpenVMS System Manager's Manual: Essentials. For PrintKit's system requirements and a list of the files created or modified by the installation, refer to Chapter 5 of the PrintKit User Manual, Troubleshooting PrintKit. If you answered YES when asked if you wanted to run the Installation Verification Procedure (IVP), your installation will be verified immediately after the installation process is complete. Step 3. Review Results of Installation Verification Procedure The Installation Verification Procedure (IVP) creates a test queue (directed to a null output, so it can be used without a printer connected), prints jobs to it, and then removes it. You should see messages announcing the startup of the test queue, and submit and completion messages for each test job. You can run the IVP at any time using the PRINTKIT_IVP command: $ @SYS$TEST:PRINTKIT_IVP For help with any problems during the IVP, refer to Chapter 5 of the PrintKit User Manual, Troubleshooting PrintKit. This completes the installation of the software. To configure PrintKit queues, proceed to the next section. Configuring PrintKit Queues ----------------------------------------------------------------------------- To configure PrintKit queues, you must be logged in to the SYSTEM account, or another account with privileges to perform operator functions. You can configure queues on an active OpenVMS system without disturbing other operations. If you need more information on managing OpenVMS print queues, refer to the OpenVMS System Manager's Manual: Essentials. Step 1. Get Ready To Configure Make sure you have done the following before starting to configure a PrintKit queue: o Enable operator messages. The PrintKit software reports configuration and printer communications problems using operator messages. These messages are an important source of information when troubleshooting problems, particularly when configuring a new queue. Enter the following command to enable delivery of operator messages to your terminal: $ REPLY/ENABLE=PRINTER o Define the KITCP command. The KITCP administration utility, provided with the PrintKit software, lets you create, display, and modify PrintKit queues. Define the KITCP command as follows: $ KITCP :== $KITCP Step 2. Collect Configuration Information Your printer should be configured and connected to your network before you configure its PrintKit queue. Once your printer is configured and connected, generate a configuration page on the printer. You will use it in creating the PrintKit queue. Consult your printer's User Manual for instructions on producing the configuration page. Step 3. Start KITCP If you enter the KITCP command with no arguments, it responds with a KITCP> prompt. You can then enter the commands you need to configure PrintKit queues. $ KITCP KITCP> You can also enter a command directly on the KITCP command line. When the command is finished, KITCP returns you directly to the system prompt. $ KITCP ADD QUEUE /INTERACTIVE queue_name KITCP accepts normal DCL command qualifiers, but it can also be told to prompt interactively for the information it needs. If you are configuring your PrintKit queues for the first time, you will probably find it much easier to use the /INTERACTIVE option when entering KITCP commands. Used interactively, KITCP will supply default values for most queue settings, and will prompt you for those that cannot be supplied from defaults, such as the printer's model and address. Adding a queue interactively, you'll be shown the default setting for each prompt. You can enter a "?" at any prompt to get more information. If the answer is one of a list of choices, you can browse through the list using the up and down arrows. Step 4. Create Print Queue Create a print queue for your printer using KITCP's ADD QUEUE command, where queue_name is the name you have chosen for this print queue: $ KITCP ADD QUEUE /INTERACTIVE queue_name KITCP asks you a series of questions; the exact questions asked vary depending on the type of printer and interface being configured. Type a "?" at any prompt for more information, and use the up and down arrows to browse through available choices. Step 5. Check Queue Configuration You can check the settings of the queues you have configured using KITCP's SHOW QUEUE command: $ KITCP SHOW QUEUE /FULL queue-name The /FULL option displays all configuration settings, not just those you were prompted for by the /INTERACTIVE option. Step 6. Adjust Queue Settings The KITCP ADD QUEUE /INTERACTIVE command prompts you for the settings that configure a queue for a particular printer; it initializes the rest with their default values. If you make a mistake when adding a new queue, or simply wish to make changes, use the KITCP MODIFY QUEUE command. Like ADD QUEUE, MODIFY QUEUE also has an /INTERACTIVE option. The PrintKit software normally selects North American Letter size paper by default. If your locale uses A4 paper, you will need to configure this as the default for your queues: $ KITCP MODIFY QUEUE queue_name /DEFAULT=SHEET_SIZE=A4 This should be enough to get you started with a typical configuration. However, there is more to KITCP. For details on configuring PrintKit, refer to Chapter 4 of the PrintKit User Manual. For descriptions of all the KITCP commands, refer to Appendix B of the PrintKit User Manual. Step 7. Start the Queue To start the queue: $ START/QUEUE queue-name Step 8. Verify Queue Operation You can run the Installation Verification Procedure on the queue to verify its operation. The IVP prints test files to verify the correct operation of the queue: $ @SYS$TEST:PRINTKIT_IVP queue-name Step 9. Make It Automatic The final step in configuring a new queue is to ensure that it starts correctly when your OpenVMS system is restarted. You can configure PrintKit queues as autostart queues, so they are started automatically by the ENABLE AUTOSTART command, or you can start them individually using START/QUEUE commands. To start the queue explicitly during system startup, add a START/QUEUE command to your System Startup File, SYS$MANAGER:SYSTARTUP_VMS.COM. To autostart the queue, use KITCP to set the autostart attribute for the queue. $ KITCP MODIFY QUEUE queue-name /AUTOSTART_ON=node::device: See the OpenVMS System Manager's Manual: Essentials for more information on setting up autostart queues. o Make sure your system startup procedure initializes any communications interfaces required by PrintKit queues before the queues are autostarted or started by individual START/QUEUE commands. The PrintKit software attempts to verify its printer connection when a queue is started, and it will fail if the communications interface is not yet initialized. o For a print queue using a LAT interface, make sure you add the LATCP CREATE PORT for the queue's LAT device to the system startup procedure. This completes the queue configuration.