***********************************************************************
*  ROPES Version 12.0 Fix RMC12015 to base Version 12.0 - 07/26/2006  *
*                 This fix applies to ROPES V12.0.                    *
***********************************************************************
*Installation Instructions
*    1. Create the data set to receive the TRANSMITed data set.  The
*       JCL in ALLOC.JCL will do this for you. Upload this job and
*       tailor it for your installation.  Run the job to create the
*       data set.
*    2. Upload the .XMI files to the data sets created in step 1. The
*       OBJECT.XMI file is uploaded to the &SYSUID.RMC12015.OBJECT.XMI
*       data set, etc.
*    3. Upload the INSTALL.JCL file.  Tailor this job for your in-
*       stallation and run the job to install the modification.
*    4. Add PPT entries for the new modules RO$D4247, RO$FPPDS,
*       EXIT4247, INIT4247, R51PPDSI, RO$DSOKT, and ROPESOCP.
*       All are LANGUAGE(ASSEMBLER).
*  OPTIONAL STEPS:
*    5. Define a test printer to use Device Block Suffix 4247 and
*       define a test report to use Forms Control Block suffix PPDS.
*    6. Define a test printer to use Device Block Suffix SOKT.
*    7. Add entries for the two printers in ROLI.
***********************************************************************
*RMC12013 - 03/09/2007 - Support for PPDS (Personal Printer Data Streams
*                        is added as an enhancment.
*
*    THIS FIX IS SUPERCEDED BY RMC12015.
*
*Problem Summary:
*    Bar code capable printers such as the IBM 4247 cannot function in
*    IPDS mode when the data transport used is IP (LPR or Direct Socket
*    printing).  A method for migrating ROPES IPDS support to such
*    printers is required.  The PPDS data stream permits the printing
*    of bar codes over the IP protocols, and has been implemented in
*    this enhancement.
*
*Symptoms:
*    IPDS bar code data streams cannot be transmitted over IP.
*
*Temporary Fix:
*    The following replacement object modules must be obtained from
*    technical support:
*        ROPEDRVR, ROPELPRP, ROPEPROP, ROPETRCE
*    The following new object modules must be obtained from
*    technical support:
*        R51PPDSI, EXIT4247, INIT4247, RO$D4247, RO$FPPDS
*    The following replacement source modules must be obtained from
*    technical support:
*        ROPESDEV, ROPESFRM
*    The following new source modules must be obtained from
*    technical support:
*        EXIT4247, INIT4247, RO$D4247, RO$FPPDS
*
*Documenation Changes:
*    A new keyword is added to the ROPESDEV TYPE=CONTROLS statement.
*    DSTYPE is now used to specify the data stream type to be used.
*    This was previously implied by the DEVTYPE keyword, and the
*    DEVTYPE keyword value is used as the DSTYPE default if DSTYPE is
*    not coded.  DSTYPE will also accept PPDS as a value to indicate
*    that the PPDS data stream is to be used.
*
*    Device initialization and termination codes are transmitted using
*    the Extended Device Controls mechanisms.
*
*    A new keyword is added to the ROPESFRM macro.  TYPE=PPDS will
*    generate controls used to modify the PPDS data streams generated
*    to adapt to the needs of certain forms.  HADJ, XADJ and YADJ
*    options allow the user to specify the direction and amount of bar
*    code height, x-axis and y-axis adjustment.
*
*Permanent Fix:
*    This enhancement will be incorporated in the next release of
*    ROPES.
*
*End Of Document
***********************************************************************
*RMC12015 - 04/17/2007 - Support for direct printing to an IP socket
*                        is added as an enhancment.
*
*    THIS FIX SUPERCEDES FIX RMC12013 (PPDS)
*
*Problem Summary:
*    Some IP attached printers can support direct printing to a socket
*    without requiring that the data be presented in LPR/LPD format.
*    Printing in this way requires somewhat less overhead, and will
*    allow IP printers that do not have inboard LPD software to be used
*    for ROPES printing without the need for an intermediate LPD spool-
*    ing device or server.
*
*Symptoms:
*    IP communication with some printers will not work when only the
*    LPR/LPD method (DEVTYPE=LPRP) is available.
*
*Temporary Fix:
*
*    Note: Because of the overlap of changes in this enhancement and
*          the RMC12013 (PPDS) enhancement, the changes in RMC12013
*          are included in this fix and RMC12013 is hereby superceded.
*
*    The following replacement object modules must be obtained from
*    technical support:
*        ROPEDRVR, ROPEDCTL, ROPEPROP, ROPETRCE, ROPELPRP, R51LPM0S,
*        ROPEWAKE
*    The following new object modules must be obtained from
*    technical support:
*        ROPESOCP, R51PPDSI, EXIT4247, INIT4247, RO$D4247, RO$FPPDS,
*        RO$DSOKT
*    The following replacement source modules must be obtained from
*    technical support:
*        ROPESDEV, ROPESFRM
*    The following new source modules must be obtained from
*    technical support:
*        RO$DSOKT, EXIT4247, INIT4247, RO$D4247, RO$FPPDS
*
*Documenation Changes:
*    A new value is supported on the ROPESDEV TYPE=CONTROLS statement.
*    DEVTYPE=SOKT can be used to specify that direct to socket printing
*    is to be used to transport the print data.
*
*Permanent Fix:
*    This enhancement will be incorporated in the next release of
*    ROPES.
*
*End Of Document
***********************************************************************