RFCs started from job in dialog

[Former Member]

Hi,

when run the job in background (prg. RSARFCEX), it calls internally RFCs in dialog and theese dialogs runs accidentally in other application server than the job is running.

It is possible to tell  to the dialog RFCs, where should be run? (on specified application server only?) and if so, where can I specify it?

Thaks in advance

zdenek bittner

[Former Member · Accepted solution]

Hi Zdenek,

I think I've got an idea how you can solve this issue.

Let's say your instance have 3 SAP Servers (CI/AS), A, B and C. Let's assume you will schedule your job on a fixed destination, server A. And I assume you know how long this job should run approximately, let's say 2 hours and the scheduled time is daily at 21:00.

What you should do:

• Create a "special, daily" Operation Mode for servers B & C, which make sure that daily between 20:30-23:30 (slightly more than those 2 hours jobs as an example, or less, up to you) on these servers there will be NO DIALOG workprocess running. You can set them to background workprocess for example. After that it will switch to "normal/existing" Operation Mode.

This will make sure that during the job running-time, there is only 1 server (A) who has DIA-workprocess, and this is where the job itself is running at that time.

I hope this will help you.

Regards,

Andre

[Reagan]

Hello

You can use server groups for background processing. Tx SM61.

Additionally if there is an RFC connection used then check whether there is load balancing enabled and the logon group used here to balance the load.

Check the AS's that are part of the logon group - Tx SMLG

Also check the RFC Server Group Maintenance - RZ12

Regards

RB

[Former Member]

Hi,

we dont use  load balancing  (i.e. no logon group in SMLG).

In RZ12 the appserver, which RFCs started on , is not included in any logon group.

So we had assumed this app-server is not accessed by any process (so no dialog RFCs will be started on it).

[former_member206552]

Hi Zdenik,

Why not just fix the rfc that it works on all the application server ?

Best Regards

Marius

[Former Member]

Hi Marius,

The job has the destination server specified, but the dialog RFCs starting on another application server (which is not even in any logon or FRC group).

I have to restrict starting of dialog RFCs there, because this server has not connectivity to RFC destination and theese RFCs aborts.I want to say "RFC dialogs must start on the same server, as bacground runs".

Zdenek

[Reagan]

Hello

Could you please clarify this:

The job has the destination server specified, but the dialog RFCs starting on another application server (which is not even in any logon or FRC group).
I have to restrict starting of dialog RFCs there, because this server has not connectivity to RFC destination and theese RFCs aborts.I want to say "RFC dialogs must start on the same server, as background runs".

Is this an application server which is part of the instance where the job is running or is this a completely a separate SAP system with different SID ?

How are the jobs triggered ? Do you have any schedulers in place ?

Regards

RB

[Former Member]

Hello,

the app-server has separate SID :

in SM51:

hpci_AB2_39  ... job runs	hpuxepci	Dialog Update Enqueue Backg Spool Upd2
app12_AB2_00 ... RFCs runs	sapapp12	Dialog Spool

RZ12:

	sapapp12_AB2_00
ALL	hpuxepci_AB2_39

Job is sheduled via SM64 (periodic job).

Regards

zdenek

[former_member206552]

Hi Zdenki

please have a look at Note 786412 - Determining execution server of jobs w/o target server

Best Regards

Marius

[Former Member]

Hi Zdenek,

Since RSARFCEX is a "Standard SAP Report", I don't see any "restrictions" or "limitations" in the way you are describing your issue, eg it has to be run and using rfc-->Dia in it's own server.

Please do check these Notes:

Note 1483845 - Using the report RSARFCEX

Note 1636949 - RSARFCEX - exclude RETRY entries from execution

Note 1675601 - Status of RETRY tRFC qRFC LUWs not correct

The first Note says: "For a fast and stable system, you must track and solve the causes for the errors mentioned above. Scheduling the report RSARFCEX is a temporary workaround that should only be used until the actual problems have been finally determined and solved."

I hope this will help you.

Regards,

Andre

[Former Member]

Hi Andre,

theese notes describes the program RSARFCEX (why to run and so on),

but not the problem we have (really job runs in one server, RFC dialogs starts accidentaly on othesr servers independently on wheather the job has defined target server or not.

Nevertheless it seems we managed some solution: we defined gateway (the same server as job is running) in RFC definition (SM59).

Thanks to all for Your help

Best regards

Zdenek

[Former Member]

Don't forget to mark your post as the "correct/helpful/assumed answered" answer, so future viewers know what resolved the issue.

[Nibu]

Hi ,

Have you tried specifying the Application server in Exec target while scheduling the job? It will ensure that the job will run in that particular application server , and hopefully the selection of dialog would happen there only ..

[AtulKumarJain]

Hi Bittner,

While defining the background job ,you can provide desired application server to run JOB .

It will help you.

BR

Atul

[Former Member]

Hi Bittner,

                Please specify the application server here to run the job at particular server.

               

             Also take into consideration below point.

             If all the dialog process are occupied at the time when your job is running then it will try to redirect the internal RFC's to other application server

Thanks and Regards,

Kunal Gahlot

[Former Member]

Hi,

this does not work - I tried before create this issue.

The job hes the destination server specified, but the dialog RFCs starting on another application server (which is not even in any logon or FRC group).

Regards

zdenek