+Remote Printing: Required Processes and Programs
`
`The SAP System passes output to printers and other devices only by way of a host system spooler.
`It does not drive devices itself. To pass output to host spool systems, the SAP spool system must
`have either of the following:
`¯ a spool work process
`This is an SAP work process which passes print requests to host spoolers for output. You can
`set up one or more for your SAP System, but with a maximum of one per instance (server).
`¯ an instance of the spool formatting program
`This is a free-standing program which provides the same functionality as the spool work
`process.
`This program is not offered under Windows NT.
`The spool work process offers better performance than the formatting program in processing output
`requests and is much easier to manage (no separate start-up and shut-down procedures). The
`spool work process will also completely replace the spool formatting program in a future update of
`the system. You should use only the spool work process in your SAP System.
`The spool system also needs an instance of the SAP spool transfer program if both of the following
`are true:
`¯ a printer is not "locally" attached with respect to a spool work process or formatting program
`A printer is "locally attached" if it is accessible to the host spooler in the system in which the
`spool work process or formatting program is running.
`¯ the host spool system that is responsible for the printer does not use a Berkeley (BSD) protocol
`print command interface. A spool work process or formatting program can pass print
`commands only to Berkeley-standard printer daemons.
`This section explains how to set up and operate spool work processes, formatting programs, and
`transfer programs.
`P.r..o..c.e.s.s.e.s.aud.P.r..o.g ra ms..ir~.O.v..e ~.i.e.w.
`Re.c..o.mme.adatio.ns;......~..e.ttir] .U ...~ .o_o.I...P.r.o rams..~r~d.P.r..o.~.e.s.s.e.s.
`.~.e.tt i.~.o..o.I..W..o, r k P. r..o..c..e.s.s.
`.~.ta~J.ng.t he.E.o.rm~tt Jn~r.am
`.~.ta~ hlg..t b.~..T.r.~rxs.f.ef...P.f.o.g r.am
`Dis 1~ .in .P.x.o.r.~m..~.tatus.
`.~.to...pj~.P.r.int.e.~.P.r..o.gr.ams.
`D~.e.m...of..E.o.~m~t.th~ .p.m rams.
`P.r.in.t.Ei[e.s
`
`SAP-00011028
`
`

`
`Processes and Programs in Overview
`
`The figure below shows how output requests are passed from the SAP spool system to a printer.
`Host System I
`
`HostSpool System
`
`I
`t
`lSAP Spool Work Process
`
`I I
`
`HostSystem2
`
`Spool Transfer Process
`
`Host Spool System
`
`I I
`
`Spool System Output Programs
`
`In the figure,
`A spool work process or formatting program is responsible for formatting data so that it can be
`output. It performs the following tasks:
`¯
`reading data to be output from the database
`¯
`if required, converting from the character set used by the SAP System to the character set of by
`the output device
`¯ embedding device-specific escape sequences in the output byte stream, as defined in the
`device-type format for the output device
`
`SAP-00011029
`
`

`
`¯ embedding device-specific printer escape sequences, as indicated by SAP print control
`formatting commands.
`A spool work process or formatting program can communicate with the host spooler and/or with
`one or more SAP transfer program. A single spool work process can therefore be responsible for
`printing on all printers in your system, if you so desire.
`In UNIX hosts, a work process or formatting program uses a print command to pass an output
`request directly to the host spool system that is responsible for the output device.
`This direct communication is possible when the host spooler and the work process or formatting
`program are running in the same host. The print command that the spool system uses is
`defined in the SAP system profile.
`A work process or formatting program can also pass an output request over the network directly
`to a remote host spool system if the remote spooler is compatible with the Berkeley (BSD) Ipd
`(line printer daemon). However, this procedure is not recommended. You should instead use
`the SAPLPD transfer program when the work process or formatting program and host spooler
`are running in different systems.
`A work process or formatting program sends data to the host spooler by way of an SAP transfer
`program when the host spool system is running in another system than the work process or
`formatting program.
`An SAP transfer program passes output requests for remote printers from an SAP spool work
`process or formatting program to the spool system in the remote host system. A transfer program:
`¯ must run on host systems that have "remote" printers attached to them.
`A printer is "remote" when
`
`¯
`
`- there is no spool work process or formatting program running in the host to which it is
`attached and;
`- the printer is not accessible to the spool system in the host in which the spool work process
`or formatting program is running..
`is required only once on a system that has remote printers. The transfer program accepts
`output from all SAP Systems that use a remote printer and passes all such output to the host
`spool system.
`¯ does not require access to the database system or to SAP libraries and can therefore run in any
`host system, whether or not it is licensed for database software.
`¯ need not run in the same host system as a spool work process or formatting program. The
`formatting program can pass data for locally-attached printers directly to the host spool system.
`is provided to you in variants for UNIX, IBM OS/2, and Microsoft Windows and Windows NT
`systems.
`Host system spoolers print all SAP output.
`Output may be passed to a printer or other output device or may be used as input for further
`processing.
`
`¯
`
`SAP-00011030
`
`

`
`Recommendations" Setting Up Spool Programs and
`Processes
`
`SAP recommends the following strategy for setting up spool work processes and transfer programs
`in your system:
`¯ Set up a spool work process in the database server of each SAP System that you are running.
`Try to address all printers in your system with this spool process, if possible.
`Use this spool work process to reach any local printers attached to the database server and to
`pass output requests to printers attached to IBM OS/2 and Microsoft Windows systems.
`If possible, use the remote-printing facilities of the host system to make printers at other hosts
`local with respect to this spool work process. That is, use remote-printing to let the host
`spooler of the database server print on the remote printers.
`If you cannot reach remote printers from your database server with the host’s remote printing
`facilities, then set up a spool work process in the SAP application server that is running in the
`remote host. Only one spool work process may be set up per SAP instance (set of application
`servers that share the same instance profile).
`If no SAP application server is running on the remote host, then you can run the SAP transfer
`program on the host. The spool work process in the database server can reach the remote
`printers by way of the transfer program.
`Should you need to reduce the workload on the database server or on another host in your
`network, you can flexibly rearrange the transfer of output requests. To relieve the database
`server, for example, you could run spool work processes in other hosts that have SAP application
`servers.
`
`Spool Work Process: Additional Notes
`
`Do not try to set up communications directly between a work process and a remote host spooler
`except as shown in the table below. This communications link is possible with Berkeley (BSD) line
`printer daemons. However, the procedure is complex and difficult to manage.
`Note that a spool work process can process output requests only from a single SAP System. If
`more than one SAP System is to use a printer, each must have its own spool work process (or
`formatting program)
`The table below shows the recommended arrangements of spool work processes and SAP transfer
`programs or host spoolers. For the most up to date information, please see the online hypertext
`document R/3 Printer Installation (DRUCKERINST, language D).
`Remote Printing Partners for the Spool Work Process
`Host for Printers
`Recommended Partner/Connection
`
`Any UNIX system
`
`Three possibilities:
`1) Make the remote printer appear local to
`the spool work process with host remote
`printing facilities.
`2) Run a spool work process in the SAP
`application server on the UNIX system.
`3) Run the SAP transfer program on the UNIX
`system.
`
`SAP-00011031
`
`

`
`OpenVMS
`
`Systems with Novell
`Netware
`Siemens-Nixdorf
`SINIX
`
`MS-Windows 3.1,
`Windows for
`Workgroups 3.11
`
`Windows NT
`
`IBM OS/2 1.3
`
`IBM OS/2 2.0
`
`Three possibilities:
`1) Make the remote printer appear local to
`the spool work process with host remote
`printing facilities: UCX, Pathworks, or
`LAT.
`2) Run a spool work process on the host to
`which the printer is attached.
`3) Run the SAP transfer program on the
`system to which the printer is attached.
`(Non-OpenVMS hosts only. The transfer
`program is not available on OpenVMS).
`Novell Ipd. NFS option of Netware 3.11
`or later required.
`Two possibilities:
`1) Use Siemens-Nixdorf Spool 4.x to manage
`access to printers network-wide.
`2) Run a spool work process or transfer
`process in the SINIX system.
`SAPLPD (SAP transfer program). NovelI-LAN-
`Workplace or MS-LAN-Manager required or
`any network software that supports Windows
`sockets. Variants of SAPLPD are:
`LPDNOV:
`NovelI-LAN-Workplace
`Microsoft LAN-Manager
`LPDMS:
`Networks that support Windows
`LPDSO:
`sockets.
`Three possibilities:
`1) Define a shared printer as a local
`printer in the Windows NT Print Manager.
`Define the printer as a local printer in
`the SAP System.
`2) For Windows shared printers: Define
`printers in SAP with device type SAPWlN.
`Use the SAP LPDNT program to pass output
`to the shared printers.
`3) For Windows remote printers (not
`shared): Run the SAP LPDNT program on
`the local Windows NT host of each remote
`printer that you wish to use.
`SAPLPD (SAP transfer program). Essex
`TCP/2 required.
`OS/2 Ipd (provided with IBM or Essex TCP/2
`
`SAP-00011032
`
`

`
`network software).
`
`Transfer Program: Additional Notes
`
`Guidelines for setting up transfer programs include the following:
`¯ Only a single transfer program is required on any host system or PC.
`The transfer program forwards output from all SAP Systems to the host spooler.
`¯ You must use a transfer program to print on a printer that is attached to an IBM OS/2 or
`MS-DOSNVindows system.
`If you are using the Siemens-Nixdorf Spool 4.x, then you do not need a transfer process.
`Spool 4.x makes all printers at SINIX or UNIX systems or DOS PCs appear to be local.
`
`¯
`
`Sample Configurations
`
`The following two sample configurations show SAP connections to local and remote printers.
`Configuration 1: All printers are connected to the host system in which the SAP System is
`running.
`
`HostSystem
`
`Spool Work Process
`
`I
`
`Host Spool Sy~em
`
`Ilocally connected printers I
`
`SAP Spool System Programs: Single System
`
`Requirement: A single SAP spool work process. The SAP System can use all printers that are
`attached to the system, whether locally or remotely (through host system facilities for remote
`printing).
`
`SAP-00011033
`
`

`
`If another SAP System is to use the printers, it must have a spool work process in an application
`server in the host system. Or it must have an SAP transfer program running in the host.
`Configuration 2: Some printers are connected to the host system of the SAP System, others to
`remote hosts.
`
`Host System
`
`Spool Work Process
`
`TCP/IP
`
`I I
`
`SA P Transfer Process+
`
`Host Spool System
`
`I I
`
`I
`
`locally conneoted printers
`
`SAP Spool System Programs: Local and Remote Printers
`
`Requirements: An application server and spool work process in the host system in which the
`SAP System is running.
`The spool work process passes output requests directly to the host spooler in System A.
`To reach the remote printers at systems B and C, the spool work process passes output requests
`to an SAP transfer program or to a compatible spooler.
`
`SAP-00011034
`
`

`
`Only one transfer program is required on a remote system, no matter how many SAP Systems wish
`to use the system’s printers.
`
`SAP-00011035
`
`

`
`Setting Up a Spool Work Process
`
`To set up a spool work process, set the following system profile parameter rdisp/wp_no_spo to the
`value 1. The value 0 is the default; no SAP spool work process is started when an instance is
`started.
`You can display and manage spool work processes with the tools provided in
`Tools -~ Administration --> Monitoring --> System monitoring.
`Note the following guidelines:
`Set the parameter only in an instance profile, not in the global DEFAULT.PFL.
`Further, ensure that the instance includes only one application server per host system. Only
`one spool work process is allowed per host system and instance.
`Example: In host system A, two application servers of SAP System cll are running. Only one
`of the application servers may have a spool work process.
`If you have been using previous releases of the SAP System, check your start-up profiles to
`make sure that no SAP formatting program is being started in a host that is to have a spool work
`process. A spool work process and the spool formatting program may not run in the same host
`system to service the same SAP System.
`Example: In host system A, an SAP application server of SAP System cl 1 is to have a spool
`work process. You must check that no formatting program for cl 1 is started in system A.
`You may run a formatting program or spool work process in system A for another SAP System,
`other than cl 1.
`
`SAP-00011036
`
`

`
`Starting the Formatting Program
`
`You can start the formatting program with the SAP STARTSAP script. To do so, ensure that the
`entry shown below is present in a start-up profile.
`For additional start-modes, please see the online hypertext document R/3 Printer Installation
`(DRUCKERINST, language D).
`Windows NT
`Note that the formatting program (RSPOGET2) is not offered under Windows NT. Use the spool
`formatting process if your SAP System runs on a Windows NT host.
`Spool Work Process
`In general, you should use only the SAP spool work process and not the spool formatting program
`as of Release 2.0 of the SAP System. In Release 2.0, both the spool work process and the
`formatting process are offered. However, the formatting program will be completely replaced by
`the spool work process in a future release. The instructions in the following sections are provided
`for your convenience while the formatting program is still included in the SAP System.
`For the formatting program:
`Start_Program_<n> LOCALl<hostname> <SAP executables directory>/rspoget2
`pf=<formatting program profile> -F [nr=<SAP number> -v -z <hh:mm> -V -Q] <SAP printer
`name(s)>l-a]
`where
`<SAP executables directory> is the directory in which SAP programs have been stored. The
`directory path is specified in the system profile parameter dir/executables. By default, the
`pathname is/usr/sap/cl 1/SYS/exe/run.
`pf=<formatting program profile> is the profile that was generated for the formatting program
`when you installed the SAP System. Always enter an absolute pathname for the profile.
`-F causes the program to run as a child process. Without this option, RSPOGET2 runs as a
`daemon, or detached process.
`This option is required if you start RSPOGET2 with the STARTSAP script and a start-up profile.
`Otherwise, STARTSAP cannot shut down the formatting program when you shut down the SAP
`System.
`nr=<SAP number> is the number of the SAP instance, if not specified in the formatting
`program’s profile.
`-v switches on "verbose" mode. The program generates a log for tracing execution.
`-z <hh:mm> specifies how long RSPOGET2 may remain inactive before it automatically ends
`itself.
`-V directs output to standard output rather than to a printer. You can then analyse problems by
`checking the output.
`You can capture the output by adding these commands to the RSPOGET2 command:
`
`¯
`
`- in CSH (C-shell) >& ’filename’
`
`- in SH (Bourne shell) > ’filename’ 2>&1
`-Q causes RSPOGET2 to generate a dump if an error occurs.
`<printer name> I -a is the name in the SAP System of the printer for which the program is to
`
`SAP-00011037
`
`

`
`prepare output.
`You can enter a series of printer names, as long as all of the printers are connected to the same
`host system.
`With the -a option, you can have the formatting program take care of all printers that are defined
`in the spool system as attached to the host system in which the formatting program is running.
`
`Starting the Formatting Program in a non-SAP Host
`
`Should you need to start a formatting program on a host in which the SAP System has not been
`installed, you can do so by
`1. Preparing the formatting program host with the SAPINST program (described in the R/3
`Installation Guide
`This preparation ensures that the SAPSTART and RSPOGET2 programs are available on the
`host and that the programs can access the SAP System’s shared profile directory.
`Defining a start-up profile for starting the spool formatting program
`For more information, please see Maintaining~ys~em.a.n~,..~a~-y.E.~o~jJes_.
`Adding an entry like the following to the start-up profile of your central system. The entry starts
`a second SAPSTART in the host in which the formatting program is to run. The second
`SAPSTART uses the profile to start RSPOGET2.
`Start_Program_01 =<host> $(DIR_EXECUTABLE)/sapstart
`pf=$(DIR_PROFILE)/<formatting program start-up profile>
`
`,
`
`,
`
`Alternative Profile
`
`The formatting program can use the standard application server profile that is generated by the
`SAPINST programs. However, you can also define a special profile for the program that allocates
`fewer shared memory resources than for normal SAP programs. You must enter the profile
`yourself; you should store it in the SAP System’s central profile directory.
`A sample formatting program profile for an SAP System named cl 1 is shown below:
`SAPSYSTEM
`=00
`INSTANCE NAME
`=S00
`SAPSYSTEMNAME
`=cll
`
`ipc/shm_psize_l 2
`=0
`=0
`ipc/sem_mon_rec
`ipc/sem_pr_set_count
`=1
`=0
`rdisp/TRACE
`You should always start and stop the formatting program with the SAPSTART program. The
`program should run synchonously with the SAP System, which SAPSTART helps to ensure.
`Starting and stopping the program with SAPSTART also helps to prevent duplicate starts of the
`program. (Duplicate formatting programs that address the same printer(s) for the same SAP
`System may prevent the local instance of the System from starting.)
`
`Specifying Start-Up Parameters
`
`With system profile parameters (described later in this section in S.etti.n ...S ..9.o.!.S..s[e.r#..
`Parameters) you can configure a formatting program specifically for a particular host spooler.
`For example, you can specify the commands that the printer program must use to communicate
`with a host spooler. You should parameter values in the profile specific to a formatting program,
`not in the system default profile.
`
`SAP-00011038
`
`

`
`Starting the Transfer Program
`
`You can start the transfer program with the SAP STARTSAP script. To do so, ensure that the
`entry shown below is present in a start-up profile. The transfer program is a separately
`purchasable component. All versions are delivered with the product.
`Execute_<nn> LOCALl<hostname> <SAP executables directory>l<SAPLPD variant>
`The transfer program does not accept any arguments. For <SAPLPD variant>, substitute the
`name of the version of SAPLPD that is appropriate for the system in which it is to run. There are
`versions for UNIX, IBM OS/2, and Microsoft Windows systems. Please consult the installation
`documentation or README file on the delivery medium for the name of the variant for your system.
`You should allow the transfer program to run continuously. Shutting it down with an SAP System
`would make the program and the printers it serves unavailable to the formatting programs of other
`SAP Systems.
`The transfer program can only be started once in a particular host system. You can therefore
`allow the SAPSTART program to process the EXECUTE_PROGRAM entry each time that an SAP
`System is started. If the transfer program has terminated, then it will be restarted. If it is running,
`then the attempted restart or duplicate start will be refused by the host system.
`In PCs, you can use the mechanisms provided in the various PC environments to start SAPLPD
`automatically. For example, you can add the SAPLPD command to the AUTOEXEC.BAT file of
`PCs in which it should run.
`As noted above, the transfer program can run on any system. The transfer program does require
`TCP/IP socket 515, which is atthis time hard-coded in the program. This is the socket used by
`LPDs (line printer daemons) that are Berkeley (BSD)-compatible.
`
`SAP-00011039
`
`

`
`Displaying Program Status
`
`To display the status of transfer programs in UNIX hosts, enter the variants of the UNIX PS
`command that are appropriate for your host system:
`ps -earl fgrep <SAPLPD variant>
`transfer program
`
`SAP-00011040
`
`

`
`Stopping Printer Programs
`
`Normally, you should start and stop formatting programs with the rest of the SAP System using the
`system start-up and shutdown procedure. You should allow the transfer program to run
`continuously.
`Should you need to stop a spool system program separately, enter the following command (UNIX
`systems):
`
`kill <PID>
`where <PID> is the process number of the spool formatting program running on your local system.
`When you issue the command, the formatting program performs a graceful shutdown. That is, the
`program deletes its PID number from table TSP03 and performs other clean-up processing before
`terminating. The program also shuts down gracefully when you stop it with SAPSTART.
`The transfer program terminates immediately when killed.
`Whether you stop a formatting program automatically with SAPSTART or manually, you should
`ensure that the program is stopped before you shut down its database system and host system.
`
`Abnormal Terminations of Formatting Programs
`
`When a formatting program is restarted after an abnormal termination, it reprocesses the output
`request on which it was working when it crashed.
`If the abnormal termination of a formatting program was caused by a faulty print job, then the
`abnormal termination may occur repeatedly. The program attempts to restart itself about every
`10 minutes, if it is running as a daemon. If this situation occurs, analyze the spool request for
`problems and delete it, if necessary, before restarting the affected program.
`Spool system transfer programs do not write to the SAP system log, nor do they maintain their own
`log file. A transfer program also cannot be traced from the SAP System. If it is executing in a
`UNIX system, however, the formatting program generates a core file if it terminates abnormally.
`
`SAP-00011041
`
`

`
`Displaying Log Files of Formatting Programs
`
`In most cases, a formatting program responds to an error in a print job with an error log. The
`program stores the log in the output controller queue, where you can display it, as described earlier
`in this section.
`However, a formatting program also records error messages in the system log file and in its own
`log file. There are two naming conventions for log files:
`¯
`If the formatting process is
`
`not started with system start-up procedure (SAPSTART, in many systems); and
`
`¯
`
`- you do not use the -F command line option,
`then the log file of the formatting program follows this naming convention: <SAP System log
`directory>/rspo<printer name>.err, where printer name is the spool system name of the printer
`in which the errors occurred. The value for <SAP System log directory> is set with the system
`profile parameter DIR_PROTOKOLLS. By default, the path is in the instance log directory,
`/usr/sap/C11/<Instance name>/Iog in UNIX systems.
`If you have started formatting programs with the SAPSTART program and the -F command line
`option, then the logs are in the SAP System’s work directory. The logs are named stderrl,
`stderr2, and so on.
`A formatting program writes in its log file only in the event of a serious error, such as an internal
`programming error. Otherwise the file remains empty.
`The formatting program’s own log file is a plain ASCII file. You can display it with host system
`utilities or with Tools --> Administration --> Monitoring --~ Traces --~ Developer traces.
`
`Deleting Log Files
`
`Should you need to delete the log file of a formatting program, you must stop the program before
`deleting the file.
`When you restart the program, it creates the log file if it has not already been created.
`
`SAP-00011042
`
`

`
`Print Files
`
`The print files created by a formatting program are stored in the SAP data directory. The
`pathname of the data directory is specified in the system profile parameter DIR_DATA. By default,
`this is the instance data directory,/usr/sap/C11/<Instance name>/data in UNIX systems.
`With the rspo/to_host/data_file system profile parameter, you can specify a standard name for the
`print files generated by a formatting program. In all cases, you should include a string of seven +
`signs in the name. For the + signs, the spool system substitutes a unique seven-character string,
`which is generated by the formatting program according to the convention shown below.
`Print File Identifier
`Character
`
`Use
`
`Additional character for specifying the number of the
`output request. Initially set to "P" (See character 7,
`below).
`The number of the spool request.
`The number of the output request, expressed as a
`letter ofthe alphabet: A= 1,B= 2, etc.
`
`2-6
`7
`
`If more than 26 output requests have been generated,
`then character 1 is used as well to form a two-
`character identification code, starting with the letter "Q":
`QA, QB, QC .... QZ, RA, RB, etc.
`
`SAP-00011043
`
`

`
`+Setting Spool System Parameters
`
`You can configure the SAP formatting programs with the system profile parameters shown in the
`list below. You may have to change default values in some UNIX systems in order to
`accommodate manufacturer-specific print commands. In other operating systems, no change from
`the default values of these parameters is necessary.
`In Windows systems, the SAP spool system uses the Windows application interface for printing.
`You therefore do not need to set any spool parameter that specifies a print command or response
`format. No harm is done if the parameters are set, however.
`The spool system itself is internally configured.
`For help in setting the parameters, please see Maintaining Start-Up and System Profiles.
`¯
`rspo/host_spool/print: The command which a printer program should use to have a host
`spooler perform a output request.
`Not required for Windows systems.
`To have the formatting program pass spool request attributes to the host spooler, you can enter
`the following variables in the command text:
`
`- &P The host-system name of the output device
`
`- &F The name of the file to be printed.
`The name is supplied in the rspo/to_host/data_file parameter, described below.
`
`- &C The number of copies to print.
`To find out the print command of your host system, consult the system documentation.
`sample commands include the following:
`Print Commands.
`Host System
`
`Print Command
`
`Some
`
`/usr/bin/Ip -d&P -n&C -onb -or &F; rm &F
`HP-UX
`qprt -dp -P&P -Bnn -N&C -r -R14 -X850 &F
`AIX
`/usr/bin/Ip -d&P -n&C -c &F; rm &F
`Other UNIX
`The hypertext book R/3 Printer Installation in the R/3-System offers further explanations of these
`commands.
`rspo/host_spool/print_method: Not used at this time.
`rspo/host_spool/print_answer: Not used.
`rspo/host_spool/query: The command to use to request the status of a print job from the host
`spooler.
`Not required for Windows systems.
`You can enter the variables shown above in the description of the rspo/host_spool/print
`parameter in the command text.
`Sample commands are shown in the table below.
`Query Commands.
`Host System
`
`Query Command
`
`HP-UX, other UNIX /usr/bin/Ipstat-o&P
`
`SAP-00011044
`
`

`
`rspo/host_spool/answer_format: A code indicating the format in which the host spooler returns
`status information.
`Not required for Windows systems.
`At this time, you can specify either Ipq and Ipstat as the code. Select the value according to
`the query command that you specify for the rspo/host_spool/query parameter.
`rspo/to_host/datafile: The name for the files passed by the formatting proces to the host
`spooler.
`The name that you select must meet the following requirements:
`
`It must contain a string of seven + characters.
`The formatting program replaces these characters to create a unique file name.
`
`It must not exceed any length limitations imposed by the host spooler.
`In normal operation, these files are deleted almost immediately. Should you wish to check the
`contents of these files, change the print command in rspo/host_spool/print so that the files are
`not deleted.
`rspo/rspoget2_daemon/tcp_block_size: The block size for TCP/IP communications between
`the formatting program and the transfer program.
`Default: 1K blocks. In some network environments, larger block sizes, such as 8K, cause
`communications problems.
`rsts/ccc/cachesize: The size of the shared-memory area that is created for translation tables
`for character codes.
`Default: 60K. If it overflows, the buffer is automatically reorganized. The buffer is also
`reorganized if any character set is invalidated. Creation and reorganization of the buffer result
`in system log messages with the reference "Buffer RSTSCCC".
`You should enlarge the buffer if automatic reorganizations occur repeatedly. Before enlarging
`the buffer, you must invalidate all entries as described in "Activating Character Sets."
`rsts/ccc/max_sapcode: Contains the largest ID number in the SAP character list. Used to
`organize the character translation buffer.
`You need change this parameter only if you add characters to the SAP character list with the
`spool system’s character definition functions.
`J,,o.{;.a.t J.o.ll. f o.[..8.to.r.Jn ..~pS..o.o.l.D.ata.
`
`SAP-00011045
`
`

`
`Location for Storing Spool Data
`
`Use the following parameter to specify where the spool system is to store its data:
`¯
`rspo/store_location: Specifies whether the spool system is to store data in the SAP System’s
`database or in files in the host system.
`Possible values:
`
`rib: spool requests are stored in the database in table TST03.
`Advantage: spool files are protected by the backup and recovery mechanisms of the
`database system.
`
`- &G: spool requests are stored in the standard SAP "global" directory:
`/usr/sap/C11/SYS/global/(UNIX systems).
`Advantages: faster access to spool data; more flexibility. Disadvantage: files are not
`protected by database backup and recovery mechanisms.
`Specifying a pathname other than the predefined path is not recommended. Should this be
`absolutely necessary, you can alter the pathname in the file rsts/files/root/G. You should not
`change the file naming convention specified in the file.
`Also ensure that the directory is accessible to all instances in your SAP System and that the
`directory is the same for all instances.
`Enter the db and $G values exactly as shown; the capitalization is important.
`Disk storage requirements: In some cases, spool data may occupy several hundred
`megabytes of disk storage. If you use the &G option, you must ensure that enough free disk
`space is available for spool data.
`Naming convention: the naming convention used for spool files, as well as all other TemSe
`objects (background processing job logs, at this time), is as follows:
`
`Files are stored by type and client of origin in a subdirectory with the name <client><first five
`characters of object name>.
`Examples: 001SPOOL (spool requests directory, client 1), 001BCTLG (background
`processing job logs, client 1).
`
`SAP-00011046
`
`

`
`Host-Name Parameters
`Four parameters have a special function: abbreviating long host names to the maximum
`characters allowed in spool output device definitions.
`cpuid/<host name>=<abbreviation> One of two ways to abbreviate the name of a host system.
`With this parameter, you can define a short name for a host. Enter the host name as part of the
`parameter name. Enter the abbreviation used in output device definitions as the parameter
`value.
`If set for a particular host, this parameter overrides the three cpuid/parameters which follow.
`cpuid/before_first One of three parameters that the spool system can use to truncate a long
`host name.
`Default value: "." (period).
`If this parameter is set, the spool system uses only the part of the host name that appears
`before the first occurrence of this character.
`Example: Host name = "VENUS.MED.PITT.EDU", cpuid/before_first =.
`Spool host name = VENUS
`cpuid/behind_last One of three parameters that the spool system can use to truncate a long
`host name.
`Default value: empty (inactive)
`If this parameter is set, the spool system uses only the part of the host name that appears after
`the last occurrence of this character.
`Example: Host name = "VENUS.MED.PITT.EDU", cpuid/behind_last =.
`Spool host