Solution : https://service.sap.com/sap/support/notes/6753 (SAP Service marketplace login required)
Summary :
Symptom clarification highlights an alternative use of print output to save it for later processing, rather than printing it immediately. Users have deviated from the norm in R/3 systems, using print data in novel ways. The presented solution details adjustments starting from SAP R/3 Release 4.0A, allowing users to customize the 'rspo/host_spool/print' parameter for individual devices through transaction SPAD. Detailed steps involve editing device settings, creating scripts and setting parameters that different UNIX and NT environments will process alike. It also guides through modifying profile parameters and restarting R/3 for changes to take effect.
Key words :
\///'` a------------------------a-----------------------------rh a---------------------------------------------ss a----------------------------------rs packet=$outputdestination/${filename}, /usr/sap/c11/dvbemgs00/work/dev_w12 ', rspo/host_spool/print = /usr/local/bin/do_print, transaction spad->utilities->copy device type, 1101 7-bit ascii 1100 8-bit iso latin-1, } a------a-------------a------------------a----------, a------a-------------a------------------a--------, aa---------------------------------------------ss filename=`echo $, device typeto change title page, /usr/local/bin/do_print
Related Notes :
| 784233 | OS400: Print to ASCII file on iSeries using Access Method L |
| 161516 | Printing into a file or anywhere else in NT |
| 24834 | How to download spool requests? |
| 15355 | Command line parameter for access type L |