SNAX/XF and SNAX/APN Configuration and Management Manual

SCF Commands for SNAX/XF and SNAX/APN
SNAX/XF and SNAX/APN Configuration and Management Manual—425836-006
13-79
SETMANAGER Command
the system, an operator can use the SCF NAMES commands to determine objects
added under each service-manager process.
Considerations
1. If you omit $process, any previously entered SETMANAGER command is cleared.
2. First use the ASSUME command to set the object type or object name. This
determines the subsystem to which subsequent commands are routed.
In addition, the following must be taken into consideration when using multiple service
managers:

SCF configuration definition files (SCF OBEY files) must use the new SCF
command SETMANAGER to identify the service-manager process with which they
want to communicate.

To send an OPEN request and issue WRITEREAD requests to multiple service
manager processes in the system requires the use of the SNAX/Creator-2 product.
The old Creator process cannot be used to communicate with any service
manager other than $SSCP.

All SPI applications must set the name of the desired service-manager process in
the ZSPI-TKN-MANAGER token when issuing WRITEREAD requests to the
service-manager process.

Other applications that communicate with the $SSCP process must be updated to
communicate with all of the required service-manager processes.

If there is a mismatch between the line-handler process and the service manager
either in the SPR or RVU versions or when using multiple service managers, an
error message is returned. For more information, see Appendix C, Error
Messages.
The following restrictions must be taken into consideration when using multiple service-
manager processes:
Remote Passthrough
Remote passthrough is established only if the primary and secondary lines are added
to a service-manager process named $SSCP. This means that no remote passthrough
can exist on a line added to a service-manager process whose name is not $SSCP
(such as $SSCP1 or $SSCP2). If the two lines are not added to the default service-
manager process and a remote passthrough is attempted, the same error messages
as for the local passthrough are displayed.
LUNS
If LUNS functionality is required, each service-manager process must have its own
ESS tables. ESS tables cannot be shared across service-manager processes.