| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Hello,
I am Jackeline Laudanski from EIC Valbonne. I am the project leader for
PQM (PRINT QUEUE MANAGER).
We are currently working on a migration release for VMS 5.5 and also
as PQM creates print queue names in ALL-IN-1, we want to be able to
support ALL-IN-1 V3.0.
I have two requests :
with the new version of ALL-IN-1, there is a new file name
oa$siteprinters.dat : what this new file use for ?
Is this file complementary of the file oa$printers ?
I need also the record definition of oa$siteprinters.dat and
oa$printers.dat (for this one, only in case the structure as
changed with the new version of ALL-IN-1)
Thanks in advance,
Jacky
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 333.1 | SMPRINTERS... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Thu Mar 26 1992 10:43 | 6 |
I'll answer the easy bit of your question:
OA$SITEPRINTERS.DAT is mapped by the form SMPRINTERS in OAFORM. That
should give you the definition of its layout.
Graham
| |||||
| 333.2 | OA$SITEPRINTERS replaces OA$PRINTERS | IOSG::BUTTON | Thu Mar 26 1992 11:16 | 13 | |
Jacky,
As Graham said in .1, SMPRINTERS maps onto OA$SITEPRINTERS.DAT. This
replaces OA$PRINTERS.DAT which was used in V2.3 and V2.4. You can
still access OA$PRINTERS.DAT file via the V24_SMPRINTERS form. It is
only used during the upgrade from V2.3/V2.4 to V3.0, so all printers
defined previously will still be available in V3.0.
More details of the Print files and data sets can be found in the
Management Guide.
Jon
| |||||
| 333.4 | Data files can be customized in ALL-IN-1 | IOSG::TALLETT | Mit Schuh bish hi | Mon Mar 30 1992 11:13 | 14 |
Hi there!
Just a warning. Most ALL-IN-1 data files are mapped by an FMS
form so that they can be customized by customers. If a customer
modifies the record layout of a file, and the corresponding
file, then ALL-IN-1 will still function properly because we
use the FMS definition to parse out the fields. Hardcoding
record layouts is generally a bad idea, and will break on any
systems where the customer customizes the data file in question.
You have been warned!
Regards,
Paul
| |||||