cancel
Showing results for 
Search instead for 
Did you mean: 

Vertex install issues with 46C - RFC setup?

Former Member
0 Kudos

Dear Fellow SAPoniSeries'ers,

We have installed the Vertex Q Series tax software with our SAP 46c implementation and we are having issues with the Remote Function Call (RFC) setup. We know that Vertex and SAP programs need to have the same "signatures" for the LIBRFC service program, and when we finally figured that out, but now we get the following message for the VERRFC but the RFCTEST works ok;

"time out during allocate /CPI-C error CM_PRODUCT_SPECIFIC_ERROR"

It appears that the RFC is trying to run as it does not immediately fail. VERRFC and RFCTEST are both now bound to VERQSU/LIBRFC service program.

We have upgraded to the ASCII database format, we are running OS/400 V5R3 and the Vertex software is Translink 2.0.22.

I would GREATLY appreciate any advice or lessons learned.

THANK-YOU!

Tim Murphy

Nalge Nunc International

Rochester, NY USA

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Tim,

first of all, I would be interested what LIBRFC you are using ...

I guess, you copied a LIBRFC to VERQSU/LIBRFC and used UPDPGM. Is this correct ?

You should check on the version of your LIBRFC with DSPSRVPGM and see a compilelib on the first screen. This will tell us what you are using.

You need to use an EBCDIC LIBRFC, because the VERTEX software is running in EBCDIC. If you are using ebcdic already, you should chekc for the version, because I'm not sure if e.g. 4.6B or 4.6C still works fine with the latest SAP release (it should, but I had issues as well).

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Former Member
0 Kudos

Tim, I don't recall just how we fixed this, but we had the same isses. Here is a cut/paste from an email I have from Vertex...this is a bit old, but may give some insight:

In the past, we have encountered issues when customers upgraded their SAP

Kernel on the AS400 (ex: going from LIBRFC 44 to LIBRFC 48)with a different

version of the SAP service program. For convenience Vertex started

providing a backup LIBRFC file in the event a problem was encountered that

caused calls to Translink (VERRFC) to fail because of incompatible or

unmatched signatures in a newer release of SAP's LIBRFC.

We have also encountered similar issues when upgrading Translink, as you

became aware when you applied your recent Vertex 3.0 & 3.1 upgrades.

Because we need to be compatible with various releases of R/3, we provide a

renamed copy of SAP's LIBRFC that we used at time of binding. This file is

LIBRFCBCK.

In the event of a signature violation, the Vertex LIBRFCBCK can be renamed

in-place to LIBRFC and Translink will find this version of the Service

Program first. Translink (VERRFC) will always look locally for the file. If

not found, it will find the one SAP provides in the SAP instance and

attempt to use it.

-


Volker, we use Vertex, issues with ASCII, ECC6.0?

Former Member
0 Kudos

Hi Tim & Jerry,

there are no general issues with Vertex and ASCII or Unicode, but you have to test.

AND ...

... you have to understand, that the SAP release has NOTHING to do with the LIBRFC release or codepage!

Vertex always needs an EBCDIC LIBRFC, which can be old as well. If you patch to a newer one, this in 99% runs into signature violations. But this is no issue, as you can use UPDPGM in order to "adjust" the Vertex-Pgm to the new LIBRFC. You should definetely copy the LIBRFC to the Vertex Lib and then you should not have any effort with doing an SAP Upgrade ... (hopefully)

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de