Advanced Communications Controller B.03.32.00 Release Notes

Patches and Fixes for this Version

Chapter 116

• JAGad94415

Symptoms: ACC 3.xx sends the calling address in call accept packet.

Defect/Fix: ACC 3.xx has a non NULL calling address in the call accept packet, which is

refused by some X.25 implementations. This problem has been fixed by providing a

tunable parameter, which can be set using /opt/acc/bin/n2z_cntrl. By default this flag

is set to 0. So, the calling address in call accept packet is 0 by default. If set to 1, the call

address packet contains the calling address.

• JAGad96420

Symptoms: ioctls in n2z_cntrl fails with “Bad address” error.

Defect/Fix: When trying to set the tunable values using n2z_cntrl, it fails with “Bad

address” error. For example, n2z_cntrl -d0 will display “n2z_cntrl: Bad address”.

The reason is that the ioctls were called directly instead of using I_STR as the second

parameter of ioctl and strioctl structure as the third parameter. This has been fixed

as follows:

Instead of calling ioctl as follows:

ioctl(ssmfd, N2Z_CTS_CD_FLAG, &flag)

ioctl is now be called by filling the strioctl structure and then calling:

ioctl(ssmfd, I_STR,&strioctl)

• JAGad71268

Symptoms: The processing in ZCOM API zconfig terminal clear/delete is incomplete. If

this feature is used, it may result in a memory leak in the ZCOM buffer pool and/or a

system panic.

Defect/Fix: A new queue “pendg_txreq” was added to the PTT in order to support the

DAM's $DATA processing. This queue is used as a temporary holding place for the

selected tx requests while building a $DATA backplane transaction. However, in zconfig

terminal CLEAR & DELETE, this new queue is not checked or cleared at all. This means

the DAM may be actively using this queue while the LDM is clearing or deleting the

associated terminal.

The Proper codes are added in the LDM to ensure this queue is also checked and cleared.