Defining OMS Command Sets for LOMS 
Use
You want to 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 of this type for each operating system on which your SAP servers are running. For more information, see Assigning OMS Output Devices to Logical OMSs.
Prerequisites
You have defined at least one logical OMS (LOMS).
Procedure
To create a command set for an LOMS, follow the procedure below:
...
1. Call transaction SPAD, and choose Extended Administration or Full Administration.
2. Then, on the Output Management Systems tab page, choose Logical Output Mgmt Systems.
The list of defined LOMSs appears.
3. Select the LOMS for which you want to define commands and choose Change.
The LOMS definition appears.
4.
Then choose
Commands.
If you want to create a new command set, choose Operating systems ® Create.
5. 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 SAP 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.
If a SUBMIT command is to be issued by an SAP spool server running on Microsoft Windows NT, then the Microsoft Windows NT SUBMIT command is used.
You can enter the following operating system names:
Value to Enter |
|
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 |
6. 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 SAP server from which a command is issued. However, you can define server-specific path names if required.
7. 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 SAP 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 SAP 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: SAP user command for canceling an output request sent to the OMS.
Definition required only if you selected Deletable in the LOMS definition.
– Job Query: SAP user command query of the status of an SAP 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, |
Submit Parameter Name |
|
SAP spool ID Required |
&EI |
Internal spool ID; Required by SAP system with RFC callback as the return parameter for identifying an SAP 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 or |
Name of the file containing the print data (including path). |
|
&f |
Name of the file containing the print data (without path). |
Attributes required if RFC callback control is implemented through the Submit command (see OMS documentation) |
||
SAP Instance |
&ES |
SAP instance name for callback format <Hostname>_<System ID>_<System Number> ‘-‘ if callback is not required. |
Interval |
&ET |
Maximum interval for creating RMG-specific events before the forced start of callback; if less than the specified Number of events occur, the callback client reports the events after this period of time has elapsed. |
Number |
&EA |
Number of RMG-specific events to collect before initiating callback |
Optional Attributes |
||
Copy count |
&C |
Number of copies |
Department |
&D |
Addressee’s department |
SAPLOMS Flags |
&E1 |
LOMS option settings for OMS services
|
LOMS flags |
&E2 |
OMS flags 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. |
SAP ROMS Flags |
&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 flags |
&E4 |
OMS flags 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) |
Title page |
&H/x/y/ |
Title page wanted (alternative 2)? X = yes, Y = no. |
Output request name |
&I |
Output request name (internal SAP name) without the SAP system name (database ID) |
Output request name |
&J |
Output request name (internal SAP name) with the SAP system name (database ID) |
Layout |
&L |
SAP format of the output request |
SAP client – spool request owner |
&M |
Client of the SAP owner of the spool request (user who created the spool request) |
SAP client – creator of the output request |
&m |
Client of the SAP user who created the output request |
SAP user – spool request owner |
&O |
SAP user ID of the owner of the spool request |
SAP user – creator of the output request |
&o |
SAP user ID of the owner of the output request |
SAP User |
&R |
SAP user ID of the addressee (intended recipient) of the output (for delivery of print output) |
SAP printer |
&S |
Name of the printer in the SAP spool system |
Title |
&T |
SAP title user gave to the output request (if any) |
Fax number |
&t |
Telephone number of the target fax machine |
Title page |
&U |
Title page wanted (alternative 1)? (X = yes, N = no) |
Priority |
&Y |
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
· Define an Output Device for Printing with an Output Management System.
