DELETE_BACKUP

An application uses this verb to delete a server from the list of backup master servers in the sna.net file, so that this server can no longer act as the master configuration file server.

You can use this verb to delete any server in the list, including the master server, whether or not the SNA software is running on the server you are deleting. The only restriction is that the list must always contain at least one server on which the SNA software is running (so that this server can take over as the master server); you cannot delete a server if it is the only server in the list or if it is the only server listed on which the SNA software is running.

This verb must be issued to the sna.net file.

VCB Structure

typedef struct delete_backup { AP_UINT16 opcode; /* verb operation code */ unsigned char reserv2; /* reserved */ unsigned char format; /* reserved */ AP_UINT16 primary_rc; /* primary return code */ AP_UINT32 secondary_rc; /* secondary return code */ unsigned char backup_name[64]; /* name of server to delete */ unsigned char reserv4[4]; /* reserved */ } DELETE_BACKUP;

Supplied Parameters

The application supplies the following parameters:

opcode

AP_DELETE_BACKUP

backup_name

The name of the server being deleted from the list of backup servers.

Returned Parameters: Successful Execution

If the verb executes successfully, SNAplus2 returns the following parameters:

primary_rc

AP_OK

secondary_rc

Not used.

Returned Parameters: State Check

If the verb does not execute because of a state check, SNAplus2 returns the following parameters:

primary_rc

AP_STATE_CHECK

secondary_rc

Possible values are:

AP_RECORD_NOT_FOUND

The server name specified is not listed in the file.

AP_CANT_DELETE_LAST_BACKUP

The server name cannot be deleted from the list, because it is the only server listed on which the SNA software is running (and hence the only server that can currently act as the master). Before attempting to delete it, either start the SNA software on one or more of the other servers listed, or add one or more new backup servers (using ADD_BACKUP) and ensure that the SNA software is started on these servers.

AP_INVALID_TARGET

The target handle on the NOF API call specified a configuration file or a node. This verb must be issued to the sna.net file.

Appendix A “Common Return Codes” lists further secondary return codes associated with AP_STATE_CHECK, which are common to all NOF verbs.

Returned Parameters: Other Conditions

Appendix A “Common Return Codes” lists further combinations of primary and secondary return codes that are common to all NOF verbs.