DataMuseum.dk

top - metrics - download

    Length: 5624 (0x15f8)
    Types: TextFile
    Names: »V«

└─⟦d10a02448⟧ Bits:30000409 8mm tape, Rational 1000, ENVIRONMENT, D_12_7_3
    └─⟦fc9b38f02⟧ »DATA« 
        └─⟦9b46a407a⟧ 
            └─⟦12c68c704⟧ 
                └─⟦this⟧ 
└─⟦5f3412b64⟧ Bits:30000745 8mm tape, Rational 1000, ENVIRONMENT 12_6_5 TOOLS 
    └─⟦91c658230⟧ »DATA« 
        └─⟦458657fb6⟧ 
            └─⟦220843204⟧ 
                └─⟦this⟧ 

TextFile

procedure Printers (Site_Config_File_Name  : String  :=
                       "!Machine.Initialization.Site.Printer_Configuration";
                    Local_Config_File_Name : String  :=
                       "!Machine.Initialization.local.Printer_Configuration";
                    User_Map_File_Name     : String  :=
                       "!Machine.Initialization.local.User_Printer_Map";
                    User_Map_Output_File   : String  :=
                       "!Machine.Queues.User_To_Printer_Map";
                    Ftp_Class_Directory    : String  := "!Machine.Queues.Ftp";
                    Effort_Only            : Boolean := True);
pragma Loaded_Main;
--
-- Initialize the print spooler and related print routing files.  Use the
-- file Site_Config_File_Name and Local_Config_File_Name (above) as the
-- specification of what to do.  Either or both files may be absent.
-- If both are present, the site and local specifications are treated
-- as one (ie, both are processed).  The file named in User_Map_File_Name
-- is used to provide a mapping from user to printer name and its
-- information is used by the Print command (!Commands.Abbreviations.Print).
-- If this file is absent, then the first printer listing processed in either
-- the site or local configuration files, in that order, is used as the
-- default printer for all users.  Running this procedure will configure the
-- spooler and create the User_Map_Output_File which is actually used by the
-- Print command.  As part of configuring the spooler, output files are written
-- to the Ftp_Class_Directory, as well.
--
-- If run with Effort_Only, this procedure will indicate what would have
-- been written where and what spooler actions would be taken, but no
-- files are actually written and the spooler is unaffected.
--
-- Configuration file format:
--
--  File            ::= Entry*
--  Entry           ::= Printer_Name '=>' '(' Device Queue_Machine ')'
--  Printer_Name    ::= <identifier>
--  Device          ::= Device_Kind Device_Options
--  Device_Kind     ::= 'Direct' '=>' Protocol ',' 'Device' '=>' Term_Number
--                  ::= 'Telnet' '=>' Host_Name ',' 'Device' '=>' Term_Number
--                              (',' 'Socket' '=>' Socket_Id)
--                  ::= 'File' '=>' R1000_Pathname
--                  ::= 'Workstation' '=>' Host_Name ',' 'Path' '=>' Pathname
--                          'Suffix' '=>' Suffix_Name
--  Device_Options  ::=
--                  ::= ',' 'Laser_Comm'
--                      ( ',' ('~') 'Reverse_Output_Pages')
--
--  Printer_Name    ::= identifier
--  Protocol        ::= 'Xon_Xoff' | 'Rts'
--  Term_Number     ::= identifier      -- eg Terminal_23
--  Host_Name       ::= identifier
--  Socket_Id       ::= '(' Byte ',' Byte ')'
--  Byte            ::= natural range 0..255
--  Path_Name       ::= contiguous_string
--  Suffix_Name     ::= contiguous_string
--  Queue_Machine   ::= ',' 'On_Node' '=>' identifier
--                  ::=                     -- all nodes if not specified
--
-- Each entry in the file provides information about a printer.
-- Each entry must start on a new line, but the information can extend over
--  several lines and include single and in-line comments.
-- Printers can be connected to R1000s in roughly 4 ways:
--      1. Direct wire connection.  Use Direct => ...  The protocol
--         for printer flow control is either Xon_Xoff or DTR.  See the
--         printer manual for details.  The Device => Term_Number
--         specifies the hardwired port to which the printer is connected.
--         Term_Number must not be enabled for login.
--      2. Telnet connection.  The printer is on the network and is connected
--         to the R1000 via Telnet.  Use Telnet => Host_Name where Host_Name
--         is the name server name of the printer.  A telnet port must be
--         reserved for communications.  This is specified by Device =>
--         Term_Number and must not be enabled for login.
--      3. Output goes to a file.  All spooler output goes to an R1000 file.
--         Manual processing is later required for getting the output printed.
--         Use File => R1000_Pathname, which specifies the file to which
--         output is written.  Group Spooler must have access to this file.
--      4. Individual print jobs are placed in a file and transferred via
--         FTP to another machine for printing.  Use Workstation => Host_Name.
--         Host_Name is the network name of the host to which the files
--         will be transferred.  Path => Pathname is the workstation
--         directory into which they will be transferred.  Its syntax must be
--         such that the file name can be string appended to it to form a
--         legal filename on the workstation.  Some workstation program
--         will then be responsible for actually printing the file.
--
--      In the Direct and Telnet cases, the option 'Laser_Comm' must be
--      specified if a laser printer is connected.  This enables a two-way
--      printer communication protocol.
--
--
-- The Print command uses a table to route print requests to printers.
-- The mapping is be specified in User_Map_File_Name.  This file has the
-- format:
--
--  User-to-printer-map file:
--
--  File            ::= Line*
--  Line            ::= Printer_Name ' ' User_Name*
--  Printer_Name    ::= identifier
--  User_Name       ::= identifier | pattern | 'others'
--
-- When the Print command is run, if no printer is specified, the printer
-- is chosen based on the contents of the map file.
--
--|No_Wait
--|Parameters Effort_Only => false