Migrating X.25 over ACC to X.25 over PSI

# LCI TYPE HOW MANY

lci 1 svc 255

#Flow Control, Throughput Class, Fast Select and Reverse Charge Settings

flowcontrol off

thruputclass off

fast_select_accept disabled

reverse_charge disabled

def_inpacketsize 128

def_outpacketsize 128

def_inwindow 2

def_outwindow 2

def_inthruputclass 11

def_outthruputclass 11

# IP Parameters

ipaddress 192.168.8.1 255.255.255.0

idletimer 600

holdtimer 300

mtu 1024

Note: The device used by X.25/PSI interface is /dev/x25_<inst>p<port> as compared to

/dev/zx25m<inst>p<port> in X.25/ACC interface,

Where,

<inst> = instance number of the adapter.

<port> = port number of the adapter.

The device for X.25/PSI interface is created by SAM or SMH while configuring X.25.

Application Migration

After the X.25/PSI interface is configured, the X.25 application uses the X.25/PSI interface to

communicate with the peer X.25 systems. The migration of X.25 from ACC to PSI is seamless. The

X.25 applications require minimal or no changes after migration to PSI adapters.

Note: X.25/PSI does not support ZCOM APIs. Any X.25 application that explicitly uses ZCOM

APIs to communicate with the peer application must be modified and recompiled after migrating to

X.25/PSI.

The application can use the same interface name for X.25/PSI and X.25/ACC or use a new

interface name. However, it must be modified and re-compiled if the interface name is altered after

migration.

X.25 applications are binary compatible if the applications do not use ZCOM API’s or requires no

change in the interface name while migrating to PSI adapters.