SPI Programming Manual (G06.24+, H06.03+, J06.03+)

General SPI Programming Guidelines
SPI Programming Manual427506-006
5-10
Opening the Management Process
Opening the Management Process
Your application has complete responsibility for establishing contact with the
subsystem, sending and receiving the messages, and terminating contact. How your
application performs these tasks depends on the subsystem and the programming
language you are using. Usually, communication with the subsystem involves the file
systemeither directly by calling the file-system procedures from TAL, or indirectly by
using COBOL verbs, TACL built-ins, or C interface declarations. C programs also can
use the alternate-model I/O routines. The discussions in this section assume the use of
the file system.
Process-Name Qualifier for SPI
Your application must establish communication by opening the server with a process
name of the form:
$server-process-name.#ZSPI
The qualifier #ZSPI tells the server that the requester will be sending and receiving
messages in SPI format.
Certain rules for establishing communication depend on the particular management
process. These rules include which process to open, how many opens are allowed per
process and per opener, and considerations for remote use and security. For these
rules, see the appropriate subsystem management programming manual. The
programming language can also impose special considerations; for these
considerations, see the language-specific section of this manual and to the specific
programming-language manual.
Checking for File-System Errors
Your application should check for the usual file-system errors that might occur on
attempts to open a server process. These paragraphs provide causes and corrective
actions that apply specifically to programs using SPI.
For general information about other file-system errors, see the
Guardian Procedure
Errors and Messages Manual
.
Error 11 or 14: File or Device Does Not Exist
The management process rejected an open attempt because it did not recognize the
process-name qualifier used. Either the qualifier name given was not #ZSPI, or the
management process or subsystem does not support a programmatic command
interface based on SPI.
If you used a qualifier other than #ZSPI, use #ZSPI. If you used #ZSPI and still got this
error, specify the correct management process. If the subsystem does not support SPI,
use whatever other interface is available for this subsystem.