HP3000-L Archives

February 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael L Gueterman <[log in to unmask]>
Reply To:
Michael L Gueterman <[log in to unmask]>
Date:
Tue, 11 Feb 1997 22:25:41 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
An easier approach might simply be to create a list of variables that get set
at logon time of all valid printer ldevs.  If you want to show the user the
available printers, just read the variable(s) with an HPCIGETVAR.  You
can verify they entered a correct printer in the same fashion.  This method
works for ldev numbers, device class names, or both.  The only down side
is you have another file to maintain following any device changes you make.
With some creative parsing, you could probably even automate that by using
the output of SYSINFO.PRVXL.TELESUP!  [actual implementation left to
the reader :) ]

This method avoids the opening of a spoolfile, and you can also implement
a form of printer management by using different variables for different groups
of users (with their own valid printers contained within of course).
ex.:
:Payroll_Printers = "111,112,113"
:Personnel_Printers = "666"  ;)

Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (509) 943-5108
fax:   (509) 946-1170
--

Kevin writes:

> I am looking for an intrinsic that I can call from a COBOL program
> to determine if a printer device exists.  We need to allow our users to
> enter a device name on a view form.  Does anyone know of such a beast?

ATOM RSS1 RSS2