The Table 1 shows the possible return codes from this tool. This tool can be used in scripts programming and the return code can be used to find the cause of the tool failure.
| Exit code | Description |
|---|---|
| 0 | Command successful |
| 1 | Invalid command: It should be any one of create, delete, list, verify, add, modify |
| 2 | Invalid object: It should be any one of wap, wapdb and so on. |
| 3 | Object argument is missing, an argument has to be passed to this object type. |
| 4 | 'all' is a reserved word and it is mandatory for listing plexdb or wapdb |
| 5 | Invalid option or the tool does not understand this option. |
| 6 | The user has specified an invalid option argument, probably missing argument for the previous option. |
| 7 | Invalid attribute or the tool does not understand this attribute. |
| 8 | The user has specified an invalid attribute value; for example dynamic attribute takes ‘yes’ or ‘no’ and so on. |
| 9 | Valid option but repeatedly used. |
| 10 | Valid option but used in the wrong place. |
| 11 | Valid attribute but used in the wrong place. |
| 12 | Valid attribute but repeatedly used. |
| 13 | The user has not specified a valid attribute value. Attribute value missing. |
| 14 | The user has specified an existing db name for create db command. |
| 15 | Could not locate the specified db_name under the db_location. |
| 16 | The user has not specified the db_name. |
| 17 | Could not locate the specified db_location. |
| 18 | The user has not specified the db_location. |
| 19 | The region already exists in the back end, no more duplicates. |
| 20 | The specified region does not belong to the specified group. |
| 21 | The specified region not found in the configuration file. |
| 22 | The region declaration not found in the configuration file. |
| 23 | The user has not specified the region name in the command. |
| 24 | The specified remote region was not found in the configuration file. |
| 25 | The user has not specified the remote region name in the command |
| 26 | The specified remote connection not found in the configuration file |
| 27 | The user has not specified the remote connection name of remote region in the command. |
| 28 | The connection already exists in the back end, no more duplicates. |
| 29 | The specified connection not found in the configuration file. |
| 30 | The user has not specified the connection name in the command. |
| 31 | The group already exists in the back end, no more duplicates. |
| 32 | The specified group not found in the configuration file. |
| 33 | The user has not specified the group name in the command. |
| 34 | The program already exists in the back end, no more duplicates. |
| 35 | The specified program not found in the configuration file. |
| 36 | The specified program not found in the specified group. |
| 37 | The user has not specified the program name in the command. |
| 38 | The transaction already exists in the back end, no more duplicates. |
| 39 | The specified transaction not found in the configuration file |
| 40 | The specified program not found in the specified group. |
| 41 | The user has not specified the transaction name in the command. |
| 42 | The specified host not found in the configuration file. |
| 43 | The user has not specified the host name in the command. |
| 44 | Not used (reserved for future) |
| 45 | The user has not specified the port in the command. |
| 46 | The plex already exists in the back end, no more duplicates. |
| 47 | Plex not found in the back end. |
| 48 | The user has not specified the plex in the command. |
| 49 | The WLM command bhgwlmload not found. |
| 50 | The WLM dictionary not found. |
| 51 | The WLM dictionary corrupted. |
| 52 | The region or program or transaction does not belong to any group. |
| 53 | The input configuration file has an unexpected string or character. |
| 54 | The output configuration file has an unexpected string or character, generated configuration file. |
| 55 | The plex object name has an invalid character, it should be [alpha][alphanumeric]* |
| 56 | The configuration file is invalid, as it may not have correct signature. |
| 57 | The specified region does belong to the another group, hence cannot be added into a specified group. |
| 58 | The valid option was unable to find its respective argument value. |
| 59 | The user has specified no to the delete command query. The delete command was stopped. |
| 60 | The user attempts to set an attribute while listing or deleting an object. |
| 61 | The user has specified a region name with more that 8 characters. |
| 62 | The user has specified a connection name with more that 4 characters. |
| 63 | The user has specified a transaction name with more that 4 characters. |
| 64 | The user has specified a program name with more that 8 characters. |
| 65 | A generic exception, better to set the trace and resubmit the command for further analysis. |