Sánchez V (2011) , tuvo como objetivo describir el conocimiento y las actitudes sexuales acerca de las ITS y el VIH-SIDA que tienen los
78 VIII REFERENCIAS BIBLIOGRÁFICAS:
Use the CCF components to configure the server entities as follows:
CCF Component Entity
Router PCM
CUCI Device and Service
TCPIP Port
Add PCM <name> codefile = <filepath> Enable PCM <name> Example: Add PCM ratlpcm codefile = system/linc/pcm/ratl Enable PCM ratlpcm CUCI
As part of the CCF configuration you must configure a:
• Connection Device
• Connection Service
Connection Device
Configure a device to the CUCI PCM to associate device connection attributes with each dialog. Attributes are assigned using the following syntax:
Add Device <device name> acvt = <VTname>, ccenable = <boolean>, controlcapable = <boolean>, dynamic = <boolean>, marccapable = <boolean>, maxinput = <number>, maxoutput = <number>, messages = <category>, securitycatlist = <name>, ndlheader = <boolean>, screen = <boolean>, usage = <category> Attributes Description
<name> Identifies a valid server name. <file path> Specifies the codefile path.
Attributes Description
<device name> Defines a unique device name.
controlcapable Indicates if control commands can be entered or not. This attribute is optional.
This attribute can only be set to False.
dynamic Indicates if the connection is to be kept by COMS when the connection terminates.
This attribute is optional.
marccapable Indicates if the connection can handle screen output from MARC. This attribute must be set to True if you are to use the RATL Services attribute MARCOpenText.
maxinput Specifies the maximum number of bytes in an input message. For Big Buffer Ispecs, this must be set to 45300 (65000 for Big Buffer Ispecs not using POF).
<number> must be a minimum of 2500.
maxoutput Specifies the maximum number of bytes in an output message. For Big Buffer Ispecs, this must be set to 45300 (65000 for Big Buffer Ispecs not using POF).
<number> must be a minimum of 2500.
messages Determines whether application messages are displayed at the client. <category> must be set to None.
securitycatlist Specifies a COMS Security Category List configuration entity that is defined in COMS. When set, the value of this attribute is the default value used when connecting to COMS. It can be overridden by the service attributes of NOFidentity.
This attribute is optional. ndlheader This attribute is optional.
This attribute can only be set to False.
screen Indicates whether the client is a screen device. This attribute is optional.
This attribute can only be set to False.
usage Identifies whether the client can receive input messages, send output messages, or both.
<category> must be set to one of In, Out, or IO.
The recommended value is IO, so that the client can both send and receive messages.
Example:
Add Device RATLweb acvt = transparent, ccenable = false, controlcapable = false, dynamic = true, marccapable = false, maxinput = 10000, maxoutput = 10000, messages = none, securitycatlist = SCL_NOF, ndlheader = false, screen = false, usage = IO Connection Service
Configure a service to the CUCI PCM to associate device connection attributes and to identify the connection path for each dialog. Attributes can be assigned using the following syntax:
Add Service RATLon
closeaction = <number>, device = <name>,
logoffdisconnect = <boolean>, dynamic = <boolean>
Enable Service RATLon
Attribute Description
closeaction The SYSTEM/COMS Close Action as defined on the SYSTEM/COMS Usercode menu. The close action is also defined on the Station menu of the COMS Utility.
You must enter a value in the range 1 to 4.
Note: If the dynamic attribute is set to True, the action is that of the DefaultStation definition in COMS.
device You must provide a CUCI Device Name. This does not need to be a valid SYSTEM/COMS Device name.
dynamic Indicates if the connection is to be kept by COMS. This attribute is optional. Allowed values are: • True, the connection will not be kept by COMS • False, the connection will be kept by COMS.
logoffdisconnect Indicates whether the session is automatically logged off when the connection is terminated.
Example:
Add Service RATLon closeaction = 3, device = ratlweb, logoffdisconnect = true Enable Service RATLon
Note: For services, the service name associated with the declared service is the name of the next service in the connection path.
TCPIP Port
Define a port to the TCPIP PCM to associate port attributes for the dialogs. Attributes can be assigned using the following syntax:
Add Port <port name>
stationname = <name>, checkinterval = <number>, device = <name>, framing = <category>, maxoffer = <number>, maxoutput = <number>, service = <name>, socket = <number>, transport = <category>, windowsize = <number> Enable Port <port name>
Attribute Description
<port name> Specifies a unique port name.
<port name> must correspond with an identified service. stationname Specifies a unique station name.
See “Using StationName” below.
checkinterval Specifies the period of inactivity before “keep alive” packets are sent. <number> is specified in seconds, and must be in the range 0 through 1440. device Specifies the name of a device to be used for all subport connections that
are passed to the CUCI PCM.
<name> must be a previously configured device.
framing Specifies the type of message delineation to be used. Message delineation indicates where a message starts and ends.
<category> must be set to Standard.
maxoffer Specifies the number of subports to be offered (made available for connection) at any time.
<number> must be in the range 0 through 31.
Example:
Add Port RATL
stationname = actlinc/#, checkinterval = 5, device = ratlweb, framing = standard, maxoffer = 1, maxoutput = 10000, service = ratl, socket = 2449, transport = tcpip, maxoffer = 500 Enable Port RATL
Using StationName
This attribute names a connection to COMS. It provides a flexible format from which station names can be generated.
Note: See the <tcpip psnf> field of the Add or Modify TCPIP PCM command in the
ClearPath HMP Series CCF Administration Guide for all possible stationname values.
When developing a station name, you need to consider uniqueness and determinability. For example, you may require that the station name be consistent each time a
particular user connects, and will not change over time. You may also require that more than one connection be used from the same client or from any number of clients and each name used is unique.
You also need to consider any COMS security that is applied to station names and how service Specifies the name of a service to be used for inbound subport
connections. This is the next service in the connection path. <name> defaults to <port name>.
socket Specifies the socket number used by the client to connect to the port file. <number> should be set to the recommended value of 2449, unless a non- standard port configuration exists.
transport Identifies the transport to be used.
<category> must be set to TCPIP, or it will default to null.
windowsize Specifies the maximum number of bytes that can be queued, on input, per dialog before more is received. For Big Buffer Ispecs, this must be set to 45300.
On some networks, such as Dynamic Host Configuration Protocol (DHCP), IP addresses are not consistent over time. In this situation there are two possible alternatives:
• Reserving a period of time where the IP address will remain stable.
• Configuring a Domain Name Server (DNS) so TCP/IP can resolve an IP address to a
known hostname.
For details on configuring a DNS Resolver, see your TCP/IP Distributed System
Services (DSS) Operations Guide.
Overriding the Stationname by Client
When a station name is set by the client it will override the configured setting defined
for RATL connections above. Refer to the Component Enabler User Guide for details
on setting the station name by client. The station name supplied by the client may have a numerator applied to uniquely qualify the name, where multiple connections are desired from the same client. The numerator is represented by a string of one or more consecutive hash characters (#) appended to the station name which will be converted to a unique ascending number. The number of consecutive hash characters indicates the minimum number of digits to be appended. For example, a supplied station name of 'user###' will result in names of the form: USER001, USER002, USER003 ... USER999, USER1000, USER1001 etc
The effect of StationName on station name (Glb.Stn)
The setting of the internal station name, or attribute Glb.Stn, is affected by the external (COMS) station name.
For Component Enabler (or NOF) based connections the value of Glb.Stn is based on the COMS station name value and the Remote Access service attribute
StationNamePrefix value. If the StationNamePrefix is not defined then Glb.Stn is prefixed by the letters “RAT”, as shown in the first example below. If the derived station name is longer than the limit of 17 characters, the connection attributes for
yourhost is used, as shown in the second example below. If the value for yourhost is not known or it is longer than the 17 character limit, the value for youripaddress is used. If this value is also too long the IP address is converted to its integer equivalent, as shown in the third example below.
The following example shows the resulting COMS and station names for a client with the specified Port Stationname format, a station name prefix set or not set to “SNP”, a hostname of Timbertown, and an IP address of 123.132.213.231:
TCPIP Port StationName
RATL Service StationName
Prefix COMS Station Name Glb.Stn
RATL Configuration
Configure the following entities:
• Service
• View
• Language
RATL Configuration Syntax
You can use the following verbs in CCF to configure the server for Component Enabler, or Web Enabler:
$youripaddress/# <null> 123_132_213_231/1 RAT2072303079/1 SNP SNP123_132_213_231/1 123_132_213_231/1
Verb How it is Used
Add To define attributes for Views, Languages, Services, MQservers, MQclients, and MQrequests.
Delete To change existing Views, Languages, Services, MQservers, MQclients, and MQrequests. The View, Language, Service, MQserver, MQclient, or MQrequest must be disabled before it can be deleted or modified.
Disable To change existing Views, Services, and MQrequests. The View, Service, or MQrequest must be disabled before it can be deleted or modified.
Enable To enable existing Views, Services, and MQrequests.
List To list Dialogs, Services, Languages, Views, MQservers, MQclients, and MQrequests.
Modify To define attributes for Views, Languages, Services, MQservers, MQclients, and MQrequests. The View, Language, Service, MQserver, MQclient, and MQrequest must be disabled before it can be deleted or modified.
Option To change server program runtime options.
Show To show existing Views, Services, Languages, connected Dialogs, MQservers, MQclients, and MQrequests.
TCPIP Port StationName
RATL Service StationName
Service
Identify a service to the PCM to associate the connection path for dialogs. Attributes are assigned using the following syntax:
Add Service <service name> service = <name>, NOFidentity = <name>, SwitchToFireUp = <boolean>, StationNamePrefix = <name> Enable Service <service name>
Attribute Description
<service name> Defines a unique service name.
service Specifies the name of a service to which inbound stations should be connected.
This is the next service in the connection path. <name> must be a previously configured service. NOFidentity Identifies the connection types of the applications.
<name> is a COMS Security Category List configuration entity that is defined in COMS.
If the attribute is not configured in the service definition, it must be defined using the SecurityCatList attribute in the CUCI service definition before the server can handle the Component Enabler connections. SwitchToFireUp Specifies behavior when switching back to an application from which a
switch previously occurred. This attribute is optional.
If True, returns to the Fireup Ispec instead of the Ispec from which the original switch occurred.
If False, returns to the Ispec from which the original switch occurred. If the client has not previously been displayed, the Fireup Ispec is retrieved.
Any data contained in the SwitchTo command overrides the setting of this attribute.
StationNamePrefix Prevents the "RAT" station name prefix appearing in Glb.Stn for Component Enabler connections.
<name> will prefix the COMS Station Name. See “Using StationName”.
This attribute is optional.
MARCOpenText Allows input to be passed to the MARC dialog when a new COMS connection is established from the server to a desired application. The value must be enclosed in double quotation marks.
Example:
Add Service RATL service = LINC, NOFidentity = SCL_NOF, SwitchToFireUp = False, StationNamePrefix = AL/ Enable Service RATL
Configuring Remote Access Server Entities
The Remote Access configuration entities for the COMS Security Category List names must be configured in at least one of the following attributes of the CCF configuration:
• SecurityCatList in the CUCI service definition
• NOFidentity in the service definition
See “RATL Configuration Syntax” for a description of the syntax used to configure the server in an MCP environment.
When configuring entities you can change their names, but the names must remain unique. You can define additional Port and Service entities ensuring that a connection path can be resolved through CCF, encompassing the PCMs from TCIP using the
Remote Access server to CUCI. See the ClearPath HMP NX/Services Administration
Guide or ClearPath HMP Series CCF Administration Guide for information on using CCF.
View
You can identify Views to the PCM to associate connection criteria for Component Enabler users to access applications. A View can refer to one or more applications, or different Views may apply to the same application.
To identify at least one application, you can assign attributes using the following syntax:
Add View <view name>
application = <system>, level = <number>, window = <name>, usercode = <usercode>, language = <language> comsstatuscheck = <boolean> Enable View <view name>
Example:
Add View sample_auto
application = (USER1)SAMPSYS on DICTPACK, level = 0,
window = SAMPLE, usercode = anonymous, language = english Enable View sample_auto Language
Identify a language to associate the ISO Country code and an ISO Language code with a language name. The ISO Language code is defined in ISO 639 while the ISO Country code is defined in ISO 3166. These standards are available in the official ISO website, http://www.iso.ch/.
Language names are configured in the application. Attributes can be assigned and application Indicates the name of the initial application to be accessed through this
View.
This attribute is optional.
<system> may contain the usercode, the application name and the Dictionary name of the built application.
The Dictionary contains the LINCGLI, LINCFORM, and LINCCNTL files for the built application.
ComsStatusCheck Specifies behavior when the transaction encounters a COMS Disabled Database on the MCP server.
If True, an error 202 is returned to the client immediately. If False, the transaction will timeout.
level Indicates the command level for dialogs using this View.
This attribute is optional and only applies to NOF based connections. window Specifies the COMS window to be used by this View.
This attribute is optional, but is required when the application to which you may need to switch is not already in use.
usercode Indicates the usercode for every dialog that is established for this View. If it is not present, the client is asked for a usercode.
This attribute is optional.
<usercode> must be valid for the purposes of workstations connected to Runtime through COMS.
language Indicates the preferred language to be used for this View. This attribute is optional.
<language> must be a previously identified language.
ISOL = <language code>
Example:
Add Language english ISOC = EN, ISOL = EN Message Queuing
Message Queuing allows multiple concurrent users of Component Enabler to access an Agile Business application, by making more efficient use of system resources, and reducing the overheads associated with establishing and maintaining individual connections for each user session. This is an alternative to the existing method of connecting to the Runtime application using individual TCP/IP connections.
See your Unisys Agile Business Suite Component Enabler Developer's Guide for
further details of using message queuing for Component Enabler Scalability.
The following entities are added to the PCM section of the CCF params file to configure the request queues and connection details of the FalconMQ Server and FalconMQ Client library:
• MQServer
• MQclient
• MQrequest
MQServer
Add MQServer <name> Servername = <name>, IPaddress = <ipaddress>, Port = <number>, Domain = <name>, UserName = <name>, Password = <name>,
Set attributes associated with the FalconMQ server using the following syntax:
Attribute Description
ISOC Specifies the ISO Country code to be associated with the language name. ISOL Specifies the ISO Language code to be associated with the language name.
Note: Case sensitive names that refer to a Windows entity can be enclosed by single quotes to prevent uppercasing.
You can also use the following commands: • Modify attributes of existing server entities
modify MQServer <name>
<attribute> = <value>,
• Itemize all declared MQServers
list MQServers
• Display the attributes for the selected server
show MQServer <name>
• Remove the selected server entity
delete MQServer <name or list>
Example (italics denote responses):
Add MQserver FMQS IPaddress = 123.1.2.3, Port = 1100, Domain = realm, UserName = dnote, Password = test, MQserver FMQS added Show MQserver FMQS 1 FMQS IPaddress = 123.1.2.3 Port = 1100 Domain = realm UserName = dnote Password = test MQClient
Port The required port number. Default: 0
Domain The Windows security domain. Default: nulls
UserName The Windows user name. Default: nulls
Password The password associated with the Windows user name. Default: nulls
Functionname = <name>
You can also use the following commands: • Modify attributes of existing client entities.
modify MQclient <name> <attribute> = <value>,
• Itemize all declared MQclients.
list MQclient
• Display the attributes for the selected client.
show MQclient <name>
• Remove the selected client entity.
delete MQclient <name or list>