*********************************************************************** *RMC12013 - 03/09/2007 - Support for PPDS (Personal Printer Data Streams * is added as an enhancment. * *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, ROPETRCE * The following new object modules must be obtained from * technical support: * R51PPDSI * The following replacement source modules must be obtained from * technical support: * ROPESDEV * The following new source modules must be obtained from * technical support: * EXIT4247, INIT4247, RO$D4247, RO$FPPDS * *SPECIAL INSTRUCTIONS: * Please backup modules ROPEDRVR and ROPELPRP prior to implementing * this fix. Make sure this fix operates correctly in your test * environment before implementing it in production. * *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. * *Permanent Fix: * This problem will be corrected by PTF in the next release of * ROPES. * *End Of Document ***********************************************************************