i have a service rui program which build descriptor has the following:

<LinkageOptions name="pgms">
<description><![CDATA[iseries programs]]></description>
<callLink >
<remoteCall pgmName="CW000012" library="*LIBL" location="xxx1.xxxxxx.com" remoteBind="GENERATION" remoteComType="JAVA400" remotePgmType="STATEFUL" conversionTable="CSOE037" javaWrapper="YES" luwControl="SERVER" refreshScreen="YES"/>
</LinkageOptions>

I know the location section tells the service where the program resides so when i "call" it, it knows where to look.

We now have 2 systems (test,prod). Is there another way of setting the location rather then hardcoding it here?

I am using Tomcat server V7.

Use...

location="PROGRAMCONTROLLED"

in your callLink entry.

As in this example:

<LinkageOptions name="externalPrograms">
    <callLink >
        <remoteCall pgmName="*" conversionTable="CSOE037" library="*LIBL" location="PROGRAMCONTROLLED"

           luwControl="SERVER" remoteBind="GENERATION" remoteComType="JAVA400" remotePgmType="STATELESS"/>
    </callLink>
</LinkageOptions>

(BONUS INFO: Note in the above the pgmName of "*" which also allows this one callLink option to handle ANY program call.)

Before you make your program call in server logic, set the target server:

sysvar.remoteSystemId = "xxx1.xxxxxx.com";    

Dan

Instead to using PROGRAMCONTROLLED as location you can make up a fictional domainname and resolve this to the proper IP-adres in the host table of the application server. E.g. location="as400.mycompany.nl" and create the entry as400.mycompany.nl 10.20.30.1 in the host file (/etc/hosts on linux). This way you can point to different backend servers from different application servers.

Even better you can create a connection factory on the application server (WAS) and refer to it like: location="eis/myAppJ2C_CF". This way all backend calls go through the same connection pool even if they origin from different service projects.

Ortwin