BASEstartm Classic DAS
for OMNItm Software
Installation and User's Guide
Previous Contents Index

2.3.2.3 Editing Device Records

The following example shows the device records created by the configuration file.

NOTE: The device MUST be defined with the UNSOLICITED attribute. 


 
create dev MMS_IS_PLC_NO_01/path=MMS_IS_LCL_PATH/type=MMS_IS_TYPE- 
/netaddr=MMS_IS_PLC_NO_01/unsol/timeout=600/log 
 
create dev MMS_DIS_PLC_NO_01/path=MMS_DIS_LCL_PATH/type=MMS_DIS_TYPE- 
/netaddr=MMS_DIS_PLC_NO_01/unsol/timeout=600/log 
 
create dev S5_AP_PLC_NO_01/path=AP_LOCAL_PATH/type=AP_TYPE- 
/netaddr=S5_AP_PLC_NO_01/unsol/timeout=600/log 
 
create dev S5_H1_PLC_NO_01/path=H1_LOCAL_PATH/type=H1_S150U_TYPE- 
/netaddr=S5_H1_PLC_NO_01/unsol/timeout=600/log 
 
create dev S7_PLC_NO_01/path=S7_LOCAL_PATH/type=S7_TYPE- 
/netaddr=S7_PLC_NO_01/unsol/timeout=600/log

The device name is the name of a remote VMD. Remote VMD names and related definitions (variables, domains, etc.) need not be defined in the OMNI database. They are created at run-time by the DAS for OMNI software and are taken from the BASEstar Classic definitions ONLY.

NOTE
The device definition MUST be defined as UNSOLICITED. Failure to do so will prevent the DAS for OMNI software from being able to react to Abort or Conclude indications sent either by the target device or the local OSI network. ie. the DAS for OMNI software will be unaware that its connection with the remote device has been terminated. Recovery will require that the user disable and re-enable the device after which a connection will be re-established. Furthermore, failure to specify support for unsolicited data means that the DAS for OMNI software will buffer all unsolicited data from the device. This will eventually lead to utilization of all the available OpenVMS virtual memory. Subsequently the DAS for OMNI software and ILAN will be unable to continue and will automatically shut themselves down.

The timeout on the device definition controls the time that BASEstar Classic device connection management allows for a device operation to complete. The value for the device timeout should be larger than the expected time of the longest device operation and also longer than the network timeout. The network timeout is controlled by the keepalive timer and retransmit threshold on the OSI transport template. For Siemens devices the RESPTIMER and COMPLTIMER in the ODS configuration can also be used to time out requests.

The local and remote Application Simple Names must be configured with ODSCL. The following examples shows the ODSCL commands contained in the configuration file. 


 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=MMS_IS_LOCAL_PLC" 
REGISTER DIRECTORY NAME "/CN=MMS_IS_LOCAL_PLC"- 
ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 2 3}- 
/P_ADDR=0x01.0x01.0x01.INTERNET%49003FAA00040013FD21" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=MMS_IS_PLC_NO_01" 
REGISTER DIRECTORY NAME "/CN=MMS_IS_PLC_NO_01"- 
ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 2 3}- 
/P_ADDR=0x02.0x02.0x02.INTERNET%49003FAA00040013FD21" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=MMS_DIS_LOCAL_PLC" 
REGISTER DIRECTORY NAME "/CN=MMS_DIS_LOCAL_PLC"- 
ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 1 1}- 
/P_ADDR=0x01.0x01.0x01.INTERNET%49003FAA00040013FD21" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=MMS_DIS_PLC_NO_01" 
REGISTER DIRECTORY NAME "/CN=MMS_DIS_PLC_NO_01"- 
ATTRIBUTE "/OC=TAE/AEQ=11/APC={1 0 9506 1 1}- 
/P_ADDR=0x02.0x02.0x02.INTERNET%49003FAA00040013FD21" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=S5_AP_LOCAL_PLC" 
REGISTER DIRECTORY NAME "/CN=S5_AP_LOCAL_PLC"- 
ATTRIBUTE "/OC=OSAP/TSAP=OSAPHOST- 
/NETADDRESS=IEEE%AA00040013FD" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=S5_AP_PLC_NO_01" 
REGISTER DIRECTORY NAME "/CN=S5_AP_PLC_NO_01"- 
ATTRIBUTE "/OC=OSAP/TSAP=OSAPTSAP- 
/NETADDRESS=IEEE%AA00040013FD" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=S5_H1_LOCAL_PLC" 
REGISTER DIRECTORY NAME "/CN=S5_H1_LOCAL_PLC"- 
ATTRIBUTE "/OC=OSH1/TSAP={R:SH1HOSTR.W:SH1HOSTW.M:SH1HOSTM}- 
/NETADDRESS=IEEE%AA00040013FD" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=S5_H1_PLC_NO_01" 
REGISTER DIRECTORY NAME "/CN=S5_H1_PLC_NO_01"- 
ATTRIBUTE "/OC=OSH1/TSAP={R:SH1TSAPR.W:SH1TSAPW.M:SH1TSAPM}- 
/NETADDRESS=IEEE%AA00040013FD" 
EXIT 
 
$ RUN ODS:[EXE]ODSCL 
DEREGISTER DIRECTORY NAME "/CN=S7_PLC_NO_01" 
REGISTER DIRECTORY NAME "/CN=S7_PLC_NO_01"- 
ATTRIBUTE "/OC=OSAPS7/TSAP=%X0103- 
/NETADDRESS=IEEE%080006013431" 
EXIT

Table 2-4 lists the attributes for ODS Application Simple Names for MMS-IS and MMS-DIS Application profiles.

Table 2-4 MMS Application Simple Name attributes
Application Profile Attribute Description Value
MMS-IS OC Object Class TAE
  CN 1 Common Name  
  APT 2 3 Application Process Title  
  AEQ 2 3 Application Entity Qualifier  
  APC Application Context {1 0 9506 2 3}
  P_ADDR 4 3 Presentation Address  
MMS-DIS OC Object Class TAE
  CN 1 Common Name  
  APT 2 3 Application Process Title  
  AEQ 2 3 Application Entity Qualifier  
  APC Application Context {1 0 9506 1 1}
  P_ADDR 4 3 Presentation Address  

1The common name entry must equal the name specified in the corresponding VAXport definition.
2The APT, AEQ and P_ADDR must be unique for a given node. APT and AEQ are optional attributes. If APT and AEQ are not specified, then OMNI uses the P_ADDR only in matching incoming initiate requests.
3See the vendor documentation for the remote VMD to see how this item is defined in the remote VMD.
4The presentation address consists of the PSAP, SSAP, TSAP & NSAP. The NSAP consists of the OSI transport template and the OSI network address of the remote VMD.

Table 2-5 lists the attributes for ODS Application Simple Names of SINEC-S7, SINEC-AP and SINEC-H1 Application Profiles.

Table 2-5 Siemens Application Simple Name attributes
Application Profile Attribute Description Value
Sinec S7 OC Object Class OSAPS7
  CN 1 Common Name  
  TSAP 2 Transport Service Access Point  
  NETADDRESS 3 Network Address  
  RESPTIMER 4 Response Timeout  
  COMPLTIMER 5 Completion Timeout  
Sinec AP OC Object Class OSAP
  CN 1 Common Name  
  TSAP 6 Transport Service Access Point  
  NETADDRESS 7 Network Address  
  RESPTIMER 4 Response timeout  
  COMPLTIMER 5 Completion timeout  
  MUX 8    
  NEGOTIATION 8    
Sinec H1 OC Object Class OSH1
  CN 1 Common Name  
  TSAP 9 Transport Service Access Point  
  NETADDRESS 7 Network Address  
  RESPTIMER 4 Response Timeout  
  COMPLTIMER 5 Completion Timeout  

1The common name entry must equal the name specified in the corresponding VAXport definition.
2The TSAP is predefined and is dependent on the positioning of either the communication card or CPU in the rack and slot. See the Siemens S7 documentation for your CPU for details.
3The network address consists of the null internet OSI template and the ethernet address of the remote VMD. If using RFC-1006, the network address consists of the RFC-1006 OSI template and the TCP/IP address of the remote VMD.
4Timeout for a response from the device. See OSAP documentation for details.
5Timeout for completion of a request. The RESPTIMER is usually a submultiple of this value. See OSAP documentation for details.
6See the vendor documentation for the remote VMD to see how this item is defined in the remote VMD.
7The network address consists of the null internet OSI template and the ethernet address of the remote VMD.
8Optional parameter. See OSAP documentation for details.
9The TSAPs in the remote VMD should equal xxxxxxxR, xxxxxxxW, xxxxxxxM for read, write and message access points.

Make sure that the ODSCL attributes match your shop-floor configuration.

Previous Next Contents Index