Skip to main content

IBM Systems  >   z Systems  >   z/VM  >  

RSCS 3.2.0 Setting up an LPR-type Link


Product Number: 5684-096 Release 3.2.0

To receive a notice whenever this web page changes, click here.

  1. Issue the following to make sure the RSCS server is running at the 9803 (or higher) RSU service level:
    sm rscs q s lev
    
    A response from RSCS indicating it is at the appropriate level would be:
    RSCS Networking Version 3, Release 2.0-9803
    
    If RSCS is not at this level, it is recommended to install the latest RSU before proceeeding with these instructions (some steps may not produce desired results).
  2. Choose an exit environment
    • LPRXONE for use with non-postscript capable printers
    • LPRXPSE for use when printing either plain text or postscript files on postscript capable printers
  3. Change RSCS's PROFILE GCS so it can load the above exits. On the RSCS install ID's (P684096K) 401 minidisk (also the RSCS ID's 191 minidisk), locate the line:
    'global loadlib RSCS'
    
    and change it to:
    'global loadlib RSCS RSCSEXIT'
    
  4. Change RSCS's PROFILE GCS so it can load a configuration file for the LPR-type link exit routines. First locate a line containing a filedef statement, then add the following lines:
    'FILEDEF LPR DISK LPR CONFIG'
    'FILEDEF LPRP DISK LPRP CONFIG'
    
  5. Copy the LPREXITS CONFSAMP file from the RSCS install ID's 406 minidisk to it's 401 minidisk as LPR CONFIG and LPRP CONFIG.
  6. Define the LPR-type printer links in the RSCS CONFIG file (located again on the install ID's 401 minidisk) by adding one (or both) of the following:
    • For a non-postscript printer
      LINKDEFINE LPR TYPE LPR FORM * AST
      PARM LPR EXIT=LPRXONE ITO=0 USER=Y SYS=Y EPARM='S=N FF=N C=LPR'
      
      USER=Y will allow users to specify a hostname, and printer queue name when using the LPR or PPS exec's. S=N will suppress generation of a separator page, and FF=N will suppress any additional form feeds (before or after the file being printed).
    • For a postscript printer
      LINKDEFINE LPRP TYPE LPR FORM * AST
      PARM LPRP EXIT=LPRXPSE ITO=0 USER=Y SYS=Y #
                EPARM='S=N EH=N EOT=N C=LPRP'
      
      USER=Y will allow users to specify a hostname, and printer queue name when using the LPR or PPS exec's. S=N will suppress generation of a separator page, EH=N will suppress sending the postscript error handler, and EOT=N will suppress sending an End Of Transmission command sequence after completion of the file being printed.
  7. Setup the RSCSDNS user ID.
  8. Next time RSCS is re-cycled (IPLed), the LPR printers will be available for use.
  9. To use the link defined with name LPR, issue the following from a CMS user ID:
    • PPS fn ft fm (HOSTN hostname PRINTQ printer_queue_name PR LPR
    The PPS exec can be found on the RSCS install ID's 406 minidisk.
    Some sample printer queue names certain printers accept (depending on the manufacture) are "raw", "text", "lp", or "print_cr".
  10. To use the link defined with name LPRP, issue the following from a CMS user ID:
    • PPS fn ft fm (HOSTN hostname PRINTQ printer_queue_name PR LPRP
    The PPS exec can be found on the RSCS install ID's 406 minidisk.
    Some sample printer queue names certain printers accept (depending on the manufacture) are raw, text, or lp.
  11. Advanced topics:
    1. If you plan moderate to heavy use of the RSCS LPR support, consider defining multiple LPR-type links and group them together. For example, define 8 links named LPR1-LPR8 and 8 links named LPRP1-LPRP8 in the RSCS CONFIG file then add the following records:
      ROUTE GROUP LPR TO LINK LPR1 LPR2 LPR3 LPR4 LPR5 LPR6 LPR7 LPR8
      ROUTE GROUP LPRP TO LINK LPRP1 LPRP2 LPRP3 LPRP4 #
                               LPRP5 LPRP6 LPRP7 LPRP8
      
    2. Use the LPRXFORM exits to define system settings for the hostname, printer queue name, prefix (printer setup) string, suffix (printer reset) string, among others which can be selected by specifying a spool file form.
    3. To avoid having a link hang due to connect problems, use the TImeout=nnn and FILEHOLD=YES link parameters in conjunction with an RSCS EVENTS file entry as follows:
      1. Add a filedef for the RSCS EVENTS file by adding the following entry in RSCS's PROFILE GCS file:
        'FILEDEF EVENTS DISK EVENTS CONFIG *'
        
      2. Create an EVENTS CONFIG file on the install ID's 401 minidisk and add the following entries:
        *----------------------------------------------------------*
        *                       RSCS Events File
        *----------------------------------------------------------*
        *              Days-of-    Range
        * Date   Time  the-week  Low  High  Command
        *------- ----- -------- ----- ----- -----------------------*
           *     M:020    *       *     *   CHANGE LPRP1 HOLD NOHOLD
           *     M:020    *       *     *   CHANGE LPR1  HOLD NOHOLD
        
        This will change all held files for the LPR links to nohold every 20 minutes so that another connect attempt can be made.
      3. Add the TIMEOUT parameter to each LPR-type link definition in the RSCS CONFIG file. If the timeout value is set too small, it can cause a job that is printing to be cancelled. Recommendation is to set the timeout value between 10 and 30 minutes depending on an estimate of printout sizes.
      4. Add the FILEHOLD parameter to each LPR-type link definition in the RSCS CONFIG file.
    4. To transfer a file which has not been delivered to a remote daemon for a specified number of days to a notify link, add the following:
      1. Copy the LPRHOLD TEMPSAMP file from the install ID's 406 minidisk to the 401 minidisk as LPRHOLD TEMPLATE.
      2. Add the following notify link definition to the RSCS CONFIG file:
        LINKDEF *LPRHOLD TYPE NOTIFY QUEUE PR AST
        PARM *LPRHOLD  PURGE=1 MSGFILE=LPRHOLD NETD=YES
        
        PURGE=1 will cause the file to be purged from the notify link after one day.
      3. Add the DAYSHOLD parameter to each LPR-type link definition in the RSCS CONFIG file.
    5. The translate tables used within the LPR-type link exit routines can be replaced within the exit configuration file.
    6. Review all the features provided with the PPS exec.
    7. See Appendix F of the RSCS program directory for further details on other enhancements provided with the RSCS LPR support

If you'd like to provide feedback on setting up an LPR-type link, you can e-mail Leslie Geer