|
|
|
|
The following sections list the NOF verbs that are relevant to particular SNAP-IX functions. For more information about individual verbs, see NOF API Verbs.
A NOF verb can be issued to a node, to the domain configuration file, or to the SNA network data file. To access the target node or file, use one of the following verbs:
OPEN_FILE
CONNECT_NODE
When you issue the verbs shown above to access the target, you are initially restricted to issuing verbs that query the configuration; you cannot issue verbs to modify it. To obtain write access to the target node or file so that you can issue verbs that modify the configuration, use the following verb:
SET_PROCESSING_MODE
To register for indications when the target configuration changes, use the following verb:
REGISTER_INDICATION_SINK
To unregister when indications are no longer required, use the following verb:
UNREGISTER_INDICATION_SINK
To release the target node or file when you have finished issuing NOF verbs, use one of the following verbs:
DISCONNECT_NODE, CLOSE_FILE
The CONNECT_NODE and DISCONNECT_NODE verbs can be issued on Solaris client computers as well as on a server; this enables you to use SET_CS_TRACE, QUERY_CS_TRACE, SET_TRACE_FILE, and QUERY_TRACE_FILE to control client-server tracing for the client. For more information, see SET_CS_TRACE, QUERY_CS_TRACE, SET_TRACE_FILE, and QUERY_TRACE_FILE. No other NOF verbs can be issued on client computers.
The first step is to define the SNAP-IX node that runs on each computer, and its communications links to other computers. To define these components, use the following verbs:
DEFINE_NODE
DEFINE_DLC, DEFINE_PORT, DEFINE_LS
After defining these components, activate them to establish the link
to the remote system. (DLCs, ports, and LSs can be defined to be initially
active
using the DEFINE_* verbs described previously, so that they
are started automatically when the node is started; in this case, it is not
necessary to start them manually.) To activate components, use the following
verbs:
INIT_NODE
START_DLC, START_PORT, START_LS
The components must be started in the order shown because each component relies on the one before it.
To stop these components when access to the remote system is no longer required, use the following verbs:
STOP_LS, STOP_PORT, STOP_DLC
To obtain information about the configuration or current status of these components, use the following verbs:
QUERY_NODE
QUERY_DLC, QUERY_PORT, QUERY_LS
To obtain information about the usage of an LS or port, use the following verb:
QUERY_STATISTICS
To delete connectivity components when they are no longer required, use the following verbs:
DELETE_DLC, DELETE_PORT, DELETE_LS
If you are communicating with many nodes on the same shared-access transport facility (SATF), you can set up a connection network (CN) to represent these nodes, instead of having to define explicit LSs to each node. CNs cannot be used if the local node is a LEN node.
To set up the CN, you first define a DLC and port to access each of the nodes on the SATF.
You then define a CN that includes all these ports; you do not need to define any LSs because a dynamic LS to the CN will be set up as required. To define the CN, or to add ports to an existing CN, use the following verb:
DEFINE_CN
To obtain information about defined CNs, or about the ports on a CN, use the following verbs:
QUERY_CN, QUERY_CN_PORT
To delete a CN when it is no longer required, or to remove ports from a CN without deleting the CN, use the following verb:
DELETE_CN
To stop the node, which deactivates all resources associated with it, use the following verb:
TERM_NODE
To define default parameters used by the node, or to query the definition of these parameters, use the following verbs:
DEFINE_DEFAULTS, QUERY_DEFAULTS
To query the options and limits permitted by your SNAP-IX license for the node, use the following verb:
QUERY_NODE_LIMITS
If SNAP-IX users will be using 3270 emulation to communicate with host systems, you need to define the communications link to the host. For more information, see Getting Started. The definition of the LS to the host must include the name of a local PU to own the LUs required for 3270 emulation and must have the solicit_sscp_sessions parameter set to AP_YES.
You then need to define LUs that can be used for 3270 emulation and also the users that can access these LUs. To define LUsand users, use the following verbs:
DEFINE_LU_0_TO_3, DEFINE_LU_0_TO_3_RANGE
DEFINE_EMULATOR_USER
To obtain information about the configuration or current status of LUs, use the following verb:
QUERY_LU_0_TO_3
To obtain information about the PU that owns an LU, use the following verb:
QUERY_PU
To obtain information about the definition of a 3270 user, about the user's current 3270 emulation program usage, or about individual sessions being accessed by the user, use the following verbs:
QUERY_EMULATOR_USER_DEF, QUERY_3270_USER, QUERY_3270_USER_SESSIONS
To delete LUs when they are no longer required, or to delete users so that they can no longer access 3270 emulation, use the following verbs:
DELETE_LU_0_TO_3, DELETE_LU_0_TO_3_RANGE
DELETE_EMULATOR_USER
If you want to provide LU pools (groups of LUs that can be assigned to user sessions as required, rather than having an LU explicitly defined for each user session), use the following verbs to define a pool, to obtain information about the definition, or to delete a pool or remove LUs from it when no longer required:
DEFINE_LU_POOL, QUERY_LU_POOL, DELETE_LU_POOL
If you want to enable 3270 users to send alert messages to the host NetView operator, or if you want to specify how the 3270 emulation program should classify response-time information that users can view with the Response Time Monitor feature, use the following verbs to define alerts and response-time boundaries or to obtain information about the current definitions:
DEFINE_3270_DIAG, QUERY_3270_DIAG
If SNAP-IX users will be using 5250 emulation to communicate with AS/400 systems, you need to define the communications link to the AS/400. For more information, see Getting Started.
You then need to define local LUs that can be used for 5250 emulation. To define LUs, use the following verb:
DEFINE_LOCAL_LU
If the 5250 emulation program identifies a partner LU by its LU alias, you need to define the partner LU to associate the alias with an LU name. (If the program identifies a partner LU by its LU name, this step is not required.) To define partner LUs, use the following verb:
DEFINE_PARTNER_LU
You then need to define the users that can access these LUs. To define users, use the following verb:
DEFINE_EMULATOR_USER
To obtain information about the configuration of 5250 users, the configuration or current status of local LUs, the current status of partner LUs, or the definition of partner LUs, use the following verbs:
QUERY_EMULATOR_USER_DEF
QUERY_LOCAL_LU
QUERY_PARTNER_LU, QUERY_PARTNER_LU_DEFINITION
To delete users so that they can no longer access 5250 emulation or to delete LUs when they are no longer required, use the following verbs:
DELETE_EMULATOR_USER
DELETE_LOCAL_LU, DELETE_PARTNER_LU
If SNAP-IX users will be using RJE to submit jobs to host systems for processing, you need to define the communications link to the host. For more information, see Getting Started. The definition of the LS to the host must include the name of a local PU to own the LUs required for RJE and must have the solicit_sscp_sessions parameter set to AP_YES.
You then need to define LUs that can be used for RJE and the RJE workstations that can access these LUs.
To define LUs, use the following verbs:
DEFINE_LU_0_TO_3, DEFINE_LU_0_TO_3_RANGE
To obtain information about the configuration or current status of LUs, use the following verb:
QUERY_LU_0_TO_3
To obtain information about the PU that owns an LU, use the following verb:
QUERY_PU
To define workstations, use the following verb:
DEFINE_RJE_WKSTN
To obtain information about the definition of a workstation or about its current status, use the following verbs:
QUERY_RJE_WKSTN_DEF, QUERY_RJE_WKSTN
To delete LUs or workstations when they are no longer required, use the following verbs:
DELETE_LU_0_TO_3, DELETE_LU_0_TO_3_RANGE
DELETE_RJE_WKSTN
If applications running on SNAP-IX will be using LU0 or LUA to communicate with host programs, you need to define the communications link to the host. For more information, see Getting Started. The definition of the LS to the host must include the name of a local PU to own the LUs, and must have the solicit_sscp_sessions parameter set to AP_YES.
You then need to define LUs that can be used for LU0 or LUA. To define the LUs, use the following verbs:
DEFINE_LU_0_TO_3 to define an individual LU or DEFINE_LU_0_TO_3_RANGE to define multiple LUs with a single verb
To delete LUs when they are no longer required, use the following verbs:
DELETE_LU_0_TO_3 to delete an individual LU or DELETE_LU_0_TO_3_RANGE to delete multiple LUs with a single verb
To obtain information about the configuration or current status of LUs, use the following verb:
QUERY_LU_0_TO_3
To obtain information about the PU that owns an LU, use the following verb:
QUERY_PU
If you want to provide LU pools (groups of LUs that can be assigned to applications as required, rather than having LUs explicitly defined for each application), use the following verbs to define a pool, to obtain information about the definition, or to delete a pool or remove LUs from it when no longer required:
DEFINE_LU_POOL, QUERY_LU_POOL, DELETE_LU_POOL
If applications running on SNAP-IX will be using APPC to communicate with applications running on host or peer computers, you need to define LUs that can be used for APPC.
APPC configuration in an APPN network is much simpler than in a pre-APPN SNA network. Many of the required components, and the interactions between them, can be defined or determined dynamically when sessions are started and do not need to be specified explicitly in the initial configuration.
Each node includes a default APPC local LU (the control point
LU
). An APPC application can use this LU, or you can define additional
LUs so that different applications can use different LUs. To define the LUs,
use the following verb:
DEFINE_LOCAL_LU
To obtain information about the configuration or current status of LUs, including the control point LU, use the following verb:
QUERY_LOCAL_LU
Because APPN can locate a partner LU dynamically when a local application needs to start a session to it, normally you do not need to define partner LUs. However, you may need to define partner LUs if you need to enforce the use of particular APPC features such as conversation security. To define a partner LU, use the following verb:
DEFINE_PARTNER_LU
To obtain information about the current status of a partner LU or about its definition if it was explicitly defined, use the following verbs:
QUERY_PARTNER_LU, QUERY_PARTNER_LU_DEFINITION
If the local application communicates with its partner using one of the standard SNA-defined modes, you do not need to define a mode. However, you may want to define additional modes for applications that have particular requirements not covered by the standard modes. To define a mode, use the following verb:
DEFINE_MODE
To define or query the default mode, which specifies parameters that will be used for any unrecognized mode name, use the following verbs:
DEFINE_DEFAULTS, QUERY_DEFAULTS
The class of service (COS) used for a mode is normally one of the standard SNA-defined classes of service. However, the node can be configured to support mapping each mode to a specific COS (the mode_to_cos_map_supp parameter on the DEFINE_NODE verb). In this case, you may want to define additional COSs for applications that have particular requirements not covered by the standard COSs. To define a COS, use the following verb:
DEFINE_COS
To specify the default COS to which any unrecognized modes will be mapped, use the following verb:
DEFINE_MODE
To obtain information about the definition or current usage of a mode, about the COS used by a mode, or about the definition of a COS, use the following verbs:
QUERY_MODE_DEFINITION, QUERY_MODE, QUERY_MODE_TO_COS_MAPPING
QUERY_COS, QUERY_COS_NODE_ROW, QUERY_COS_TG_ROW
If the local and partner LUs use session-level security, you need to define the password used to establish a session between the local LU and partner LU. To define the password, check the current definition, or delete the password when it is no longer required, use the following verbs:
DEFINE_LU_LU_PASSWORD, QUERY_LU_LU_PASSWORD, DELETE_LU_LU_PASSWORD
To delete local LUs, partner LUs, modes, or COSs when they are no longer required, use the following verbs:
DELETE_LOCAL_LU, DELETE_PARTNER_LU
DELETE_MODE, DELETE_COS
SNAP-IX negotiates session limits with the partner LU automatically when sessions are established. If you need to manage session limits between a local LU and its partner LU explicitly, use the following verbs:
INITIALIZE_SESSION_LIMIT, CHANGE_SESSION_LIMIT, RESET_SESSION_LIMIT
To manage individual sessions and conversations, use the following verbs:
QUERY_SESSION, QUERY_ISR_SESSION, QUERY_CONVERSATION
ACTIVATE_SESSION, DEACTIVATE_SESSION, DEACTIVATE_CONV_GROUP
Normally you do not need to define SNAP-IX invokable TPs if they are operator-started. If a TP is to be automatically started by SNAP-IX when a remote TP allocates a conversation to it, if it is to be operator-started and a broadcast queued TP (which means that incoming conversation requests can be routed dynamically to the TP wherever it is running), or if it is to be operator-started and requires a specific Receive_Allocate timeout value, you need to specify it in the SNAP-IX invokable TP data file. For more information about this file, refer to the SNAP-IX Administration Guide.
In addition, if a TP (either operator-started or auto-started) needs to be restricted to particular values for conversation security, confirm synchronization, or conversation type (mapped or basic), or if you need to limit the number of instances of the TP that can be running at any time, you need to define the TP. Use the following verb:
DEFINE_TP
To obtain information about the definition of a TP, about its current usage, or about currently active invokable TPs, use the following verbs:
QUERY_TP_DEFINITION, QUERY_TP, QUERY_AVAILABLE_TP
To delete a defined TP when it is no longer required, use the following verb:
DELETE_TP
If the invokable TP requires conversation-level security, you need to define user IDs and passwords that remote TPs can use to access SNAP-IX TPs. To define user IDs and passwords, check the current definitions, or delete user IDs and passwords when they are no longer required, use the following verbs:
DEFINE_USERID_PASSWORD, QUERY_USERID_PASSWORD, DELETE_USERID_PASSWORD
To restrict the use of the TP to a specific list of authorized user IDs, check the current list of authorized user IDs, or delete a list of user IDs when it is no longer required, use the following verbs:
DEFINE_SECURITY_ACCESS_LIST, QUERY_SECURITY_ACCESS_LIST, DELETE_SECURITY_ACCESS_LIST
CPI-C applications use the same resources as APPC applications; the information in APPC Communications, applies to CPI-C as well as to APPC.
In addition, you can set up side information entries for use by CPI-C applications; each entry defines a particular partner application and the information required to access it. The local CPI-C application can then identify its partner application simply by the name of a side information entry, instead of having to specify explicit partner LU and TP names, mode name, and conversation security requirements. To define side information entries, check the current definitions, or delete entries when they are no longer required, use the following verbs:
DEFINE_CPIC_SIDE_INFO, QUERY_CPIC_SIDE_INFO, DELETE_CPIC_SIDE_INFO
If the node supports PU concentration (the pu_conc_support parameter on the DEFINE_NODE verb), to enable type 0-3 LUs on downstream computers to communicate with host systems using LUs defined on the SNAP-IX node, you must first define the following:
A DLC, port, and LS from SNAP-IX to the downstream computer. For information about defining these components, see Getting Started. The LS must be defined with the following parameters:
solicit_sscp_sessions =NO dspu_services =PU_CONCENTRATION dspu_name = the name of the PU serving the LUs on the downstream computer pu_name = all zeros
One or more type 0-3 LUs on the SNAP-IX node (and optionally an LU pool containing these LUs) for communications with the host. For information about defining LUs and LU pools, see 3270 Communications.
You then define the LUs on the downstream computer and map these to the LUs on the SNAP-IX node. To define the downstream LUs, use the following verbs:
DEFINE_DOWNSTREAM_LU, DEFINE_DOWNSTREAM_LU_RANGE
To obtain information about the configuration or current status of downstream LUs or about the downstream PU that serves them, use the following verbs:
QUERY_DOWNSTREAM_LU, QUERY_DOWNSTREAM_PU
To delete downstream LUs when they are no longer required, use the following verbs:
DELETE_DOWNSTREAM_LU, DELETE_DOWNSTREAM_LU_RANGE
If the node supports DLUR (the dlur_support parameter on the DEFINE_NODE verb), and LUs on the SNAP-IX node will be using DLUR to communicate with host systems, you need to define the PU on the local SNAP-IX node that owns these LUs. This is not the same as defining a PU for LUs that communicate directly with the host (which is done using the DEFINE_LS verb).
To define the PU, use the following verb:
DEFINE_INTERNAL_PU
To obtain information about the PU, use the following verb:
QUERY_PU
To define and manage the LUs associated with this PU, see 3270 Communications, RJE Communications, or LU0 or LUA Communications, earlier in this section.
To start the PU (to request an ACTPU from the host) in order to use the LUs or to stop it when applications are no longer using the LUs, use the following verbs:
START_INTERNAL_PU, STOP_INTERNAL_PU
To delete the PU when it is no longer required, use the following verb:
DELETE_INTERNAL_PU
If the local node is a network node, and LUs on downstream PUs will be using DLUR to communicate with host systems, you need to define the communications link to the downstream PU, as described in Getting Started. The LS definition must specify that the local node provides DLUR services to the downstream PU.
You do not need to define the downstream PUs; SNAP-IX will obtain the necessary information dynamically when communications links are established. To obtain information about downstream PUs and LUs currently using DLUR, use the following verbs:
QUERY_DOWNSTREAM_PU, QUERY_DOWNSTREAM_LU
To set up defaults to simplify DLUR configuration and reduce the information required on other DLUR verbs, use the following verb:
DEFINE_DLUR_DEFAULTS
To obtain information about PUs and LUs currently using DLUR (either on the local node or on downstream PUs), or about the DLUS nodes they are using, use the following verbs:
QUERY_DLUR_PU, QUERY_DLUR_LU, QUERY_DLUS
If TN3270 users will be using the TN server feature on a SNAP-IX node to communicate with host systems, you need to define the communications link to the host. For more information, see Getting Started. The definition of the LS to the host must include the name of a local PU to own the 3270 LUs and must have the solicit_sscp_sessions parameter set to AP_YES.
You then need to define LUs that can be used for 3270 emulation and optionally group these LUs into LU pools. For more information about defining LUs and users, see 3270 Communications.
To define parameters that apply to all TN Server users, use the following verb:
DEFINE_TN3270_DEFAULTS
To define the TN3270 users that can access TN server and assign them to SNAP-IX 3270 LUs, use the following verb:
DEFINE_TN3270_ACCESS
To define the association between TN3270 display and printer LUs, so that a TN3270E client can connect to the printer LU that is associated with a display LU without knowing the name of the printer LU, use the following verb:
DEFINE_TN3270_ASSOCIATION
To obtain information about the configuration of TN Server and TN3270 users, use the following verbs:
QUERY_TN3270_ACCESS_DEF, QUERY_TN3270_ASSOCIATION, QUERY_TN3270_DEFAULTS
To delete TN3270 users so that they can no longer use TN server for 3270 emulation, or to delete LU association information, use the following verbs:
DELETE_TN3270_ACCESS, DELETE_TN3270_ASSOCIATION
If applications running on SNAP-IX will be using the MS API to communicate with remote MS applications, you do not need to define any resources for this explicitly, because the node will locate the appropriate remote applications as required. However, you can define the resources explicitly if you want to specify a particular remote application to use.
To specify a default PU for use by NMVT-level applications (so that they access the NetView program at a specific host), use the following verb:
DEFINE_DEFAULT_PU
To specify a focal point application for use by MDS-level applications (instead of enabling the remote focal point application to determine which nodes it manages), use the following verb:
DEFINE_FOCAL_POINT
To obtain information about the focal point currently in use, or to delete a previously defined focal point, use the following verbs:
QUERY_FOCAL_POINT, DELETE_FOCAL_POINT
To obtain information about active applications (NMVT-level or MDS-level) using MS functions, use the following verbs:
QUERY_NMVT_APPLICATION, QUERY_MDS_APPLICATION
To obtain information about outstanding requests from MDS-level applications, or to obtain statistical information about previous requests, use the following verbs:
QUERY_ACTIVE_TRANSACTION, QUERY_MDS_STATISTICS
If you want to enable operators at the host NetView console to issue commands on the SNAP-IX computer using either the Service Point Command Facility (SPCF) or the UNIX Command Facility (UCF), you need to define the access permissions for these operators.
To define these permissions and enable NetView operators to access SPCF or UCF or both, use the following verb:
DEFINE_RCF_ACCESS
To check the permissions currently defined, use the following verb:
QUERY_RCF_ACCESS
To prevent operators from using either SPCF or UCF, use the following verb:
DELETE_RCF_ACCESS
To remove access to one function but leave the other available, use the following verb:
DEFINE_RCF_ACCESS
The SNAP-IX default setting for log messages is to log problem and exception messages but not audit messages, and to use central logging (messages from all servers sent to a central log file on the master server). Succinct logging is used (that is, logging of header parameters and message text, but not full details of cause and action for each message). The error log file, used for problem and exception messages, is /var/opt/sna/sna.err; the audit log file, used for audit messages if these are enabled, is /var/opt/sna/sna.aud. Each of these files is backed up and reset when the file size reaches 1 megabyte. The default settings for succinct logging, exception and audit logging, file names, and file sizes can all be overridden using NOF verbs, as described in the following information.
The verbs to manage central logging and global logging options apply to Windows clients as well as to Solaris computers. However, other diagnostics settings on Windows clients are controlled by options in the Windows Program Registry, and not by NOF verbs. For more information, refer to the SNAP-IX Administration Guide.
SNAP-IX also maintains a usage log file /var/opt/sna/sna.usage, which is used to record information about the current and peak usage of SNAP-IX resources. This file is backed up and reset in the same way as the error and audit log files, and the file name and file size can be specified in the same way.
To specify whether central logging is enabled, use the following verb:
SET_CENTRAL_LOGGING
To specify whether exception messages or audit messages or both are logged, or to specify whether succinct logging or full logging is to be used, either to establish global default settings for all servers or to override the defaults for a particular server, use the following verbs:
SET_GLOBAL_LOG_TYPE, SET_LOG_TYPE
To change the file names or directories used for log messages or to change the size at which files are backed up and reset, use the following verb:
SET_LOG_FILE
To check which server is currently defined as the central logger or to check whether central logging is enabled, use the following verbs:
QUERY_CENTRAL_LOGGER, QUERY_CENTRAL_LOGGING
To check the types of messages being recorded or to check whether succinct logging or full logging is being used, either globally or on a particular server, use the following verbs:
QUERY_GLOBAL_LOG_TYPE, QUERY_LOG_TYPE
To check the file, file size, or directory being used for a particular log type, use the following verb:
QUERY_LOG_FILE
If you want to activate tracing to diagnose problems with connectivity components on a particular SNAP-IX node or to deactivate it after collecting the required data, use the following verbs:
ADD_DLC_TRACE, REMOVE_DLC_TRACE
If you want to activate tracing to diagnose problems with other SNAP-IX kernel components or to deactivate it after collecting the required data, use the following verb:
SET_TRACE_TYPE
If you want to activate tracing to diagnose problems with communications between clients and servers across the SNAP-IX LAN or to deactivate it after collecting the required data, use the following verb:
SET_CS_TRACE
If you want to activate tracing to diagnose problems with the SNAP-IX TN server feature or to deactivate it after collecting the required data, use the following verb:
SET_TN_SERVER_TRACE
The default files used for trace data are as follows:
/var/opt/sna/sna1.trc and /var/opt/sna/sna2.trc for tracing on a particular computer
/var/opt/sna/snacs1.trc and /var/opt/sna/snacs2.trc for LAN tracing
/var/opt/sna/snatnsv1.trc and /var/opt/sna/snatnsv2.trc for TN server tracing
If you want to use different files or directories for either of these trace types or to send all tracing of a particular type to one file instead of two files, use the following verb:
SET_TRACE_FILE
To check the current settings for a particular trace type or to check the files used for a particular trace type, use the following verbs:
QUERY_DLC_TRACE, QUERY_TRACE_TYPE, QUERY_CS_TRACE, QUERY_TN_SERVER_TRACE, QUERY_TRACE_FILE
The verbs relating to client-server tracing can be issued on Solaris client computers as well as on a server. For more information, see SET_CS_TRACE, QUERY_CS_TRACE, SET_TRACE_FILE, and QUERY_TRACE_FILE.
If the local node is a LEN node, you need to set up entries in the local node's directory to identify the adjacent nodes that SNAP-IX will communicate with and the LUs associated with these nodes. If a particular node contains a range of LUs with similar names, you can set up wildcard entries in the directory to indicate that all LUs in the range are on the specified node.
To define a node and the LUs associated with it, use the following verb:
DEFINE_ADJACENT_LEN_NODE
To obtain information about a specific node or LU entry in the database (however, this verb cannot be used to return information about wildcard entries), use the following verb:
QUERY_DIRECTORY_ENTRY
To obtain information about a specific LU entry or wildcard entry in the database, use the following verb:
QUERY_DIRECTORY_LU
To obtain statistical information about directory entries, use the following verb:
QUERY_DIRECTORY_STATS
To delete a node and the LUs associated with it or to delete LUs from a node entry, use the following verb:
DELETE_ADJACENT_LEN_NODE
If the local node is an end node or network node communicating with a LEN node, or if the local node is the network node serving a LEN node, you need to set up directory entries for the LEN node and its LUs, using the verbs described above. For communications with other node types, you do not need to set up directory entries because the node will locate these resources dynamically as required (and add them to the directory so that they can be used again).
However, you may want to set up entries for particular nodes or LUs so that the local node can communicate with these resources without having to search for them. Because setting up entries for particular nodes or LUs overrides the normal APPN resource location process, you can have problems at this node or at other nodes in the network if the definitions are not correct. Do not define explicit entries for resources at other nodes unless you are sure that the definitions are correct.
To define an individual node, LU, or wildcard entry for a range of LUs, use the following verb:
DEFINE_DIRECTORY_ENTRY
To delete an individual node, LU, or wildcard entry from the directory, use the following verb:
DELETE_DIRECTORY_ENTRY
Delete only directory entries that
were explicitly defined using the verbs described previously (these entries
return an entry type of
To obtain information (on a network node) about adjacent network nodes, use the following verb:
QUERY_ADJACENT_NN
To obtain information about the TGs to adjacent network nodes, use the following verb:
QUERY_LOCAL_TOPOLOGY
To obtain information (on a network node) about network nodes and virtual routing nodes (VRNs) in the network, or about the TGs to these nodes, use the following verbs:
QUERY_NN_TOPOLOGY_NODE, QUERY_NN_TOPOLOGY_TG
To obtain statistical information (on a network node) about the use of entries in the local node's topology database, use the following verb:
QUERY_NN_TOPOLOGY_STATS
To check that a particular target LU can be accessed (that the node owning the LU is active and that there is a communications path to the LU), use the following verb:
APING
To obtain a list of servers (nodes) on the SNAP-IX LAN, use the following verb:
QUERY_NODE_ALL
To obtain detailed information about a particular node, use the following verb:
QUERY_NODE
To find out which servers are acting as the master configuration file server and backup master servers, use the following verb:
QUERY_SNA_NET
To add new backup master servers to the list or to remove existing servers from the list so that they can no longer act as master servers, use the following verbs:
ADD_BACKUP, DELETE_BACKUP
To add a descriptive comment string to the domain configuration file, use the following verb:
DEFINE_DOMAIN_CONFIG_FILE
To obtain information about the SNAP-IX version number for which the domain configuration file was created or about the comment string stored in it, use the following verb:
QUERY_DOMAIN_CONFIG_FILE
There are no corresponding verbs for the node configuration file because the header information in the node configuration file is for SNAP-IX internal use only; do not attempt to modify it.
To set a limit on the amount of kernel memory that SNAP-IX can use for internal data structures or to specify the maximum amount of memory available for STREAMS buffers, use the following verbs:
SET_KERNEL_MEMORY_LIMIT, SET_BUFFER_AVAILABILITY
To obtain information about the current limits and usage, use the following verbs:
QUERY_KERNEL_MEMORY_LIMIT, QUERY_BUFFER_AVAILABILITY
|
|
|
 |
|