skip book previous and next navigation links
go up to top of book: HP OpenVMS System Manager's Manual, Volume 2:... HP OpenVMS System Manager's Manual, Volume 2:...
go to beginning of chapter: Managing DECdtm ServicesManaging DECdtm Services
go to previous page: Planning Transaction LogsPlanning Transaction Logs
go to next page: Creating Transaction LogsCreating Transaction Logs
end of book navigation links

Planning for a DECnet-PlusNetwork  



This section contains the following information to help youplan for using DECdtm in a DECnet-Plus network:

PlanningYour DECnet-Plus Namespace 

DECdtm does not support multiple DECnet-Plus namespaces.

This means that if you want to use software that uses DECdtmservices, you cannot use both a local namespace and a DECdns namespace.

PlanningSCSNODE Names in Your DECnet-Plus Network 

SCSNODE is a system parameter that defines the name of thecomputer. You must follow certain rules when choosing SCSNODE namesif you have a DECnet-Plus network and you want to perform DECdtm transactionsthat span either different OpenVMS Clusters or different standalonecomputers.

Rules for SCSNODE Names  

If you have a DECnet-Plus network and want to perform DECdtmtransactions that span different OpenVMS Clusters or different standalonecomputers, you must make sure that your SCSNODE names obey the followingrules:


NoteACMS users, possibly Rdb users, and any other usersrunning a user-written application that calls DECdtm to participatein a distributed transaction with a remote system that has the HP DECnet-Plusfor OpenVMS network connection and whose nodes are connected usingonly an IP router might see the following error returned by DECnet:
IPC-E-BCKTRNSFAIL, failure on the back translate address request
This error is displayed upon a logical connection failurewhen DECnet-Plus cannot translate the remote node name. The errorcan be triggered when:
  1. TheDECnet-Plus node name for the remote system is not defined in thelocal DECnet-Plus database and is defined only as ALIAS in the TCP/IPname server for the remote node.

    For example, node XXYZZY might be defined as follows:
    20.43.136.54 XXYZZY.ABC.DEF.COM, XXYZZY
  2. The node name cannot be resolvedfrom the DECnet database. In this case, the address resolution mechanismwill fall back on the TCP/IP database. If the node name is stillnot resolved, the service might fail with the error cited above.

    To avoid this situation, register the SCSNAME in theTCP/IP database.

UnderstandingTransaction Groups  

A transaction group is a group of computersinvolved in DECdtm transactions whose SCSNODE names must obey therules described in Rules for SCSNODE Names.

A transaction group conforms to the following guidelines:

Transaction Group shows an exampleof a transaction group.  

Figure 2  Transaction Group  
transaction group

All nine computers shown in the figure are in the same transactiongroup because:


go to previous page: Planning Transaction LogsPlanning Transaction Logs
go to next page: Creating Transaction LogsCreating Transaction Logs