NetBatch Management Programming Manual
SPI Programming Considerations for the NetBatch 
Subsystem
NetBatch Management Programming Manual—522462-003
3-6
Discontinuing a Command in Progress
4. Call procedure SSPUT or SSPUTTKN to assign values to tokens and to add the 
tokens to the message. 
5. Call procedure SSMOVE or SSMOVETKNif you are resending a command to 
retrieve the next response message in a seriesto move the context token from 
the previous response buffer into the command buffer. 
6. Send the command message using the mechanism applicable to your 
programming language (for example, Guardian procedure WRITEREADX for C 
and TAL, the READ verb for COBOL, or the #REQUESTER built-in function for the 
TACL program). The NetBatch subsystem receives the message, interprets the 
command request, executes the command (if there are no command-syntax 
errors), and returns a response buffer, including one or more error lists (if any 
errors occurred). 
Because the mechanism your application uses to send the command buffer to the 
NetBatch subsystem is independent of SPI, you can use features available to your 
programming language, such as nowaited or timed I/O for TAL. 
Your application must check for file-system errors when sending the buffer. For file-
system error details, see the Guardian Procedure Errors and Messages Manual. 
Discontinuing a Command in Progress
The NetBatch subsystem does not respond to requests for discontinuing a command in 
progress. The subsystem does not support the use of the standard SPI token ZSPI-
TKN-ALLOW-TYPE, which in other subsystems allows applications to specify, in a 
command operating on multiple objects, whether the subsystem is to continue to the 
next object if it failed on a previous one. The NetBatch subsystem continues to the next 
object if it fails on the previous object. 
Caution. An extensible structured token in a command must always be initialized by SSNULL. 
Using SSNULL to initialize an extensible structured token ensures every field of the token is 
initialized to its null value. This action is important because an operation will be performed if a 
field contains a value other than its null value. 
Using SSNULL is important even when your application assigns a value to every field of an 
extensible structured token. If you do not use SSNULL, the application does not work correctly 
later if it is compiled with a new version of the definition files that add new fields to the token. 










