Extension in the QOUT Scheduler (Transaction SMQS) 

Use

The destinations used in tRFC or qRFC calls are automatically registered in SMQS. The QOUT Scheduler therefore transfers all tRFC or qRFC LUWs with a registered destination asynchronously to the application, and, depending on the resources of the sending system, to the required target system for processing.

 

Procedure

When using tRFC, qRFC, and other applications for communicating between two SAP systems, you are strongly recommended to use different destinations for different users. This avoids a delay when sending the tRFC and qRFC LUWs, and also facilitates later error analysis.

The maximum number of connections that can operate in parallel for a registered destination in SMQS is preset as follows:

·        Maximum 10 connections: The target system is an SAP system

·        Maximum 1 connection   : The target system is an external tRFC/qRFC program

 

These values also apply for a collective restart using report RSARFCEX for tRFC, or report RSQOWKEX for qRFC with outbound queue.

 

To improve performance (by enabling parallel transfer and processing), you can modify these preset values. The modification you make depends on the number of DIALOG processes in the local system (client), the number of DIALOG processes in the receiving system (for an SAP system), or the number of registered external tRFC/qRFC server programs with the same program ID.

 

Note that these are only the maximum values for the Scheduler. Depending on the configuration using RZ12, less DIALOG work processes may be available for the Scheduler in the local (sending) system.

 

Result

You can also use these values to monitor the load on the receiving system. It is particularly useful to implement the QOUT Scheduler when communicating with external programs, because restricting the maximum number of connections eliminates CPIC errors caused by a busy registered RFC server. Depending on the number of registered RFC servers under the same program ID, you can increase the value using SMQS.

 

Do not choose a number of maximum connections that is larger than the number of DIALOG processes in the target system, even if this is possible. If you do, the tRFC and the qRFC in the target system may be unable to run because all the DIALOG processes are busy.

 

You can prevent immediate transfer of the tRFC/qRFC LUWs by deregistering a destination in SMQS. It is not enough to delete the registration here because this destination is registered again automatically after the next RFC/qRFC call, if the client, user, password, and language have been entered in transaction SM59. You can later re-register the destination for the QOUT Scheduler using the transaction SQMS.