TS/MP Pathsend and Server Programming Manual (G06.24+, H06.03+)

Writing Pathsend Requesters
NonStop TS/MP Pathsend and Server Programming Manual–132500
3-7
Avoiding Coded PATHMON Names
This level of security is required because the LINKMON process must be able to open
the PATHMON process (to make link requests); the LINKMON process must be able to
open the server processes (to send user requests); and the PATHMON process must be
able to open the server processes (to send startup messages). All of these opens are
performed with the PATHMON user ID.
Server-Class Security
LINKMON processes perform authorization checks on each server-class send operation
to make sure that the user ID of the Pathsend process at the time of the send conforms to
the server class’s OWNER and SECURITY attributes. You set these attributes for server
classes at configuration time if those server classes are to be accessed by Pathsend
processes.
The NonStop TS/MP System Management Manual describes how to set the SERVER
OWNER and SERVER SECURITY parameters in PATHCOM.
RSC Client Security
Remote Server Call (RSC) workstation clients can be allowed or disallowed to
communicate with specified Pathway servers. You can set up security validation by
creating an Access Control Server (ACS). For more information about creating an ACS,
refer to the Remote Server Call (RSC) Programming Manual.
Avoiding Coded PATHMON Names
SCREEN COBOL requesters can send requests to Pathway server classes without
having to specify the name of the PATHMON process controlling the server class,
because the TCP has a default PATHMON process to send to. Pathsend processes,
however, must specify the PATHMON name of the server class to send to, because the
Pathsend procedures provide no default PATHMON name.
It is possible, however, to avoid coding PATHMON names in Pathsend programs. For
example, you can use ASSIGNs containing the PATHMON system and process name.
Or, if the Pathsend process is a Pathway server, the process can use the name of its
creator as the default PATHMON name to send to. This method of avoiding coding the
PATHMON name is reliable as long as the sending server is not associative, in which
case its creator might not be a PATHMON process.
The Pathsend program examples BREQ and PATHSRV in Appendix B, Examples
, use
ASSIGNs to avoid coding PATHMON names. The PATHSRV example also uses the
creator default method just described to avoid coding the PATHMON names.
Note. The user ID of the Pathsend process need not have remote passwords to the
PATHMON system or to the server-class system to access the server class. Moreover, the
Pathsend-process user ID need not be known on the PATHMON or server-class systems.