Response header fields
A successful HTTP response does not mean that the command was successful: it indicates only that the Web User Interface server was able to interpret the command and the result status is indicated in the header record.
Each header record contains at least the fields shown in Table 1. There can also be other header fields, as described for individual commands under Data interface command reference. The order in which header fields appear in the header record is undefined.
| Header field | Description |
|---|---|
| CMASSYSID | SYSID of the CMAS to which the Web User Interface server is connected, if known. |
| CPSMREL | The version and release number character string of CICSPlex® SM. |
| SERVERAPPLID | The CICS® APPLID of the Web User Interface server. |
| STATUS | Main response status indicator. See Table 2 for details. |
| TASKID | The task identifier of the CICS task that generated the response. |
| Status | Meaning |
|---|---|
| BADCOMMAND | The specified command is unknown. |
| BADTICKET | The ticket (cookie) was invalid or missing. This could be, for example, because the user session has expired. |
| FAILURE | The command failed with an undefined error. |
| OK | The command executed successfully, and additional header fields can contain the results, depending on the command. |
| TIMEOUT | The command timed out. See Dealing with time out failures |