Defining OMS Command Sets for LOMS (SAP Library

Defining OMS Command Sets for LOMS

You can define a set of OMS commands to be used by a particular LOMS on a particular platform. When an output request is sent to this LOMS, the SUBMIT, QUERY, POLLING and other commands in this set are used to submit the output request to the OMS and query its status.

You need at least one command set for each operating system on which your R/3 servers are running. For more information, see Organizing OMS Output Devices in Logical OMSs.

Prerequisites

You have created at least one logical OMS (LOMS).

Procedure

Start the LOMS maintenance tool, if you are not already in the LOMS definition for which you want to define a command. Choose Tools ® CCMS ® Spool ® Spool administration. Choose Extended admin. and then Logical output management systems on the Output management systems tab page.

Select the LOMS for which you want to define commands and choose Change. Then choose This graphic is explained in the accompanying text Commands

Choose the operating system for this variant of the OMS commands.

If you have a heterogeneous system environment, you will need a variant for each host operating system on which your R/3 servers are running.

If you have a homogenous operating system environment, define only a single variant, for your operating system.

Background: If the SAP System uses a defined OMS command, it chooses the correct variant according to the local host operating system. Example: If a SUBMIT command is to be issued by an SAP spool server running on Windows NT, then the Windows NT SUBMIT command is used.

Here are the operating system names you can enter:

Value to Enter

Operating System

AIX

IBM UNIX

BOS/X

Honeywell-Bull UNIX

HP-UX

Hewlett-Packard UNIX

OSF/1

Digital Equipment UNIX

OSF1

Digital Equipment UNIX

SINIX

Siemens-Nixdorf UNIX

SunOS

Sun UNIX

Windows NT

Microsoft Windows NT

Enter the Command path. This is the full path name for the OMS commands. In this variant, the path name has a prefix for each of the OMS commands.

Ideally, the path name is the same regardless of the R/3 server from which a command is issued. However, you can define server-specific path names if required.

Enter definitions for each of the commands required by the LOMS.

These commands are described in the OMS documentation. The manufacturer should generally specify these so that you do not have to deal with different parameters. The commands are as follows:

Submit: Passes an R/3 output request to the external OMS for printing.

Definition is always required.

Polling: SAP spool servers issue this command periodically to query the status of output requests that they processed.

Definition required only if you selected Polling in the LOMS definition.

Queue query: This is an R/3 user query of the status and queue of an OMS output device.

Definition required only if you selected Queue query in the LOMS definition.

Job cancel: R/3 user command for canceling an output request sent to the OMS.

Definition required only if you selected Deletable in the LOMS definition.

Job query: R/3 user command query of the status of an R/3 output request in the OMS.

Definition required only if you selected Query in the LOMS definition.

For lists of the options available for each command, see the tables below.

Submit Command Options

This table includes the options you can use when defining a Submit command.

Attribute,
Required/Optional

Submit Parameter Name

Meaning

SAP spool ID
Required

&EI

Internal spool ID. Required by R/3 with RFC callback as the return parameter for identifying an R/3 output request.

Reply message group
Required

&EG

ID of an RMG This information is required during polling or callback for classification of the information to be returned.

Destination
Required

&P
or

Name of the target output device in the OMS (including path)

&p

Name of the target output device in the OMS (without path)

Document
Required

&F

Name of the file containing the print data (including path)

&f

Name of the target output device in the OMS (without path)

Attributes required if RFC callback control is implemented through the Submit command (see the OMS documentation to determine if this is the case)

SAP instance

&ES

SAP instance name for callback format

<hostname>_<system ID>_<system number>

‘-‘ if callback not required.

Interval

&ET

Maximum interval for collecting RMG-specific events before forced initiation of callback. Should fewer than Number of events occur, the callback client reports events after this interval elapses.

Number

&EA

Number of RMG-specific events to collect before initiating callback

Optional attributes

Number of copies

&C

Number of copies

Department

&D

Addressee’s department

R3LOMS indicators

&E1

LOMS option settings for OMS services.

LOMS indicators

&E2

OMS indicators of the LOMS
This option inserts the contents of the OMS Configuration field from the LOMS definition into the Submit command.
This field can be used to insert any desired OMS options or OMS arguments into the command.
See also: Defining a Logical OMS

R3 ROMS indicators

&E3

ROMS option settings for OMS services.
Currently, these are:

· Job query supported

· Job callback supported

· Device callback supported

· Fax supported
For the field structure, see table TSPROMS in the ABAP Dictionary. The options are inserted in the Submit command as a 60-character string.

ROMS indicators

&E4

OMS indicators of the ROMS
This option inserts the contents of the OMS Configuration field from the ROMS definition into the Submit command.
This field can be used to insert any desired OMS options or OMS arguments into the command.
See also: Defining a Real OMS

Fax recipient

&EP

Name of FAX recipient (future enhancement)

Cover page

&H/x/y/

Cover page wanted (alternative 2)? X = yes, Y = no.

Output request name

&I

Output request name (name in R/3) without the SAP System name (database ID)

Output request name

&J

Output request name (name in R/3) including the SAP System name (database ID)

Layout

&L

R/3 format of the output request

R/3 client – spool request owner

&M

Client of R/3 owner of the spool request (user who created the spool request)

R/3 client – output request generator

&m

Client of the R/3 user who created the output request

R/3 user – spool request owner

&O

R/3 user ID of the owner of the spool request

R/3 user – output request generator

&o

R/3 user ID of the owner of the output request

R/3 user

&R

R/3 user ID of the addressee (intended recipient) of the output (for delivery of print output)

R/3 printer

&S

Name of the printer in the SAP spool system

Title

&T

R/3 title user gave to the output request (if any)

Fax number

&t

Telephone number of the target fax device

Cover page

&U

Cover page wanted (alternative 1)? (X = yes, N = no)

Priority

&Y

R/3 priority (1-99), where 1 is the highest priority

Result

You have defined commands for use in an LOMS. You can now:

Define additional commands for other LOMSs

Connect a Printer to an External OMS

This graphic is explained in the accompanying text First Page of SAP Printing Guide

Value to Enter	Operating System
AIX	IBM UNIX
BOS/X	Honeywell-Bull UNIX
HP-UX	Hewlett-Packard UNIX
OSF/1	Digital Equipment UNIX
OSF1	Digital Equipment UNIX
SINIX	Siemens-Nixdorf UNIX
SunOS	Sun UNIX
Windows NT	Microsoft Windows NT

Attribute, Required/Optional	Submit Parameter Name	Meaning
SAP spool ID Required	&EI	Internal spool ID. Required by R/3 with RFC callback as the return parameter for identifying an R/3 output request.
Reply message group Required	&EG	ID of an RMG This information is required during polling or callback for classification of the information to be returned.
Destination Required	&P or	Name of the target output device in the OMS (including path)
	&p	Name of the target output device in the OMS (without path)
Document Required	&F	Name of the file containing the print data (including path)
	&f	Name of the target output device in the OMS (without path)
Attributes required if RFC callback control is implemented through the Submit command (see the OMS documentation to determine if this is the case)
SAP instance	&ES	SAP instance name for callback format <hostname>_<system ID>_<system number> ‘-‘ if callback not required.
Interval	&ET	Maximum interval for collecting RMG-specific events before forced initiation of callback. Should fewer than Number of events occur, the callback client reports events after this interval elapses.
Number	&EA	Number of RMG-specific events to collect before initiating callback
Optional attributes
Number of copies	&C	Number of copies
Department	&D	Addressee’s department
R3LOMS indicators	&E1	LOMS option settings for OMS services.
LOMS indicators	&E2	OMS indicators of the LOMS This option inserts the contents of the OMS Configuration field from the LOMS definition into the Submit command. This field can be used to insert any desired OMS options or OMS arguments into the command. See also: Defining a Logical OMS
R3 ROMS indicators	&E3	ROMS option settings for OMS services. Currently, these are: · Job query supported · Job callback supported · Device callback supported · Fax supported For the field structure, see table TSPROMS in the ABAP Dictionary. The options are inserted in the Submit command as a 60-character string.
ROMS indicators	&E4	OMS indicators of the ROMS This option inserts the contents of the OMS Configuration field from the ROMS definition into the Submit command. This field can be used to insert any desired OMS options or OMS arguments into the command. See also: Defining a Real OMS
Fax recipient	&EP	Name of FAX recipient (future enhancement)
Cover page	&H/x/y/	Cover page wanted (alternative 2)? X = yes, Y = no.
Output request name	&I	Output request name (name in R/3) without the SAP System name (database ID)
Output request name	&J	Output request name (name in R/3) including the SAP System name (database ID)
Layout	&L	R/3 format of the output request
R/3 client – spool request owner	&M	Client of R/3 owner of the spool request (user who created the spool request)
R/3 client – output request generator	&m	Client of the R/3 user who created the output request
R/3 user – spool request owner	&O	R/3 user ID of the owner of the spool request
R/3 user – output request generator	&o	R/3 user ID of the owner of the output request
R/3 user	&R	R/3 user ID of the addressee (intended recipient) of the output (for delivery of print output)
R/3 printer	&S	Name of the printer in the SAP spool system
Title	&T	R/3 title user gave to the output request (if any)
Fax number	&t	Telephone number of the target fax device
Cover page	&U	Cover page wanted (alternative 1)? (X = yes, N = no)
Priority	&Y	R/3 priority (1-99), where 1 is the highest priority