HTTP response status codes and reason phrases

The following table shows the status codes and reason phrases the DTCN profile manager might send to your application:
Table 1. Explanation of reason phrases
Status code Reason phrase Explanation
200 OK The DTCN profile manager completed the method (action) successfully.
200 Profile_Already_Exists_With_Identical_Resources A PUT request was sent specifying resources that are already used by another profile in the DTCN profile repository. The DTCN profile manager did not create a new profile.
200 Profile_Already_Exists_With_Same_Owner A PUT request was sent specifying a profile ID that is already used by another profile in the DTCN profile repository. The DTCN profile manager did not create a new profile.
201 Profile_Created_OK The DTCN profile manager successfully created a new profile.
400 Unsupported_Client_Version A client version that is 2 or more levels higher or lower than the server version was specified.
400 Invalid_Client_Version The syntax of the clientversion symbol is incorrect. For the correct syntax, see Compatibility of different versions.
400 Invalid_Profile_Record_Number Starting profile record number is incorrect.
400 No_Resource_Specified No resources were specified in the HTTP request body.
400 Site_Rules_Require_Terminal_ID_Specified The HTTP request body does not specify a terminal ID. The DTCN profile manager requires that you specify a terminal ID.1
400 Site_Rules_Require_Transaction_ID_Specified The HTTP request body does not specify a transaction ID. The DTCN profile manager requires that you specify a transaction ID.1
400 Site_Rules_Require_At_Least_One_Load_Mod_Name_Specified The HTTP request body does not specify the name of a load module. The DTCN profile manager requires that you specify the name of at least one load module.1
400 Site_Rules_Require_At_Least_One_Program_Name_Specified The HTTP request body does not specify the name of a compile unit. The DTCN profile manager requires that you specify the name of at least one compile unit.1
400 Site_Rules_Require_User_ID_Specified The HTTP request body does not specify a user ID. The DTCN profile manager requires that you specify a user ID.1
400 Site_Rules_Require_NetName_Specified The HTTP request body does not specify a netname. The DTCN profile manager requires that you specify a netname.1
400 Site_Rules_Require_Client_IP_Specified The HTTP request body does not specify the IP address of the client. The DTCN profile manager requires that you specify the IP address of the client.1
400 Invalid_Session_Address For a PUT or POST request, the HTTP request body is missing the <sessaddr> tag or a value in the <sessaddr> tag, which is required if you specify TCP in the <sessiontype> tag.
400 Invalid_Session_Type The HTTP request body specifies a value for the <sesstype> tag that is invalid. MFI or TCP are the only valid values for the <sesstype> tag.
400 Invalid_Session_Port The HTTP request body specifies a value for the <sessport> tag that is not numeric or specifies a port number when the session type is MFI. A port number is used only when the session type is TCP.
400 Invalid_UrmDeb_Flag The HTTP request body specifies a value for <urmdebug> tag that is invalid. Y or N are the only valid values for the <urmdebug> tag.
400 Invalid_Activation_Flag The HTTP request body specifies a value for the <activation> tag that is invalid. A or I are the only valid values for the <activation> tag.
400 Invalid_Trigger The HTTP request body specifies a value for the <trigger> tag that is invalid. TEST or NOTEST are the only valid values for the <trigger> tag.
400 Invalid_Test_Level The HTTP request body specifies a value for the <level> tag that is invalid. The only valid values for the <level> tag are ALL, ERROR, or NONE.
400 Error_Parsing_XML_Doc z/OS® XML parser failed to parse the HTTP request.
400 Bad Request The URI is invalid.2
401 No_Write_Access_For_Unauthorized_User The user ID specified in the <userid> tag is not authorized (through RACF®) to update or delete another user's profile.
401 CICS_Default_Userid_Not_Allowed The CICS® default user ID can not be used to access profiles.
401 Create_Not_Allowed_By_Non_Owner Only the owner of a profile can create a profile with the same user ID.
404 Profile_Not_Found For the GET, POST, or DELETE request, the DTCN profile manager did not find a profile with the specified profile (user) ID.
500 CICS_Error There was an error in the CICS region.
500 Dtcn_Manager_Received_Invalid_Function The DTCN profile manager had internal error.
500 Unknown_Return_Code_Error The DTCN profile manager had internal error.
503 DEBUGTOOL_System_Setting_Is_On The CICS DEBUGTOOL system setting is on. Turn it off to use the DTCN profile manager.
Note:
  1. When z/OS Debugger was installed, it was customized so that when a user created a DTCN profile, z/OS Debugger verifies that the user specifies a specific resource or resources. If you receive this message, it means that your site requires that you specify the indicated resource when you create a DTCN profile.
  2. A DFHWB0723 message appears in the CICS region job output that shows a response code of 8 and one of the following reason codes:
    5
    Profile collection name is missing
    6
    Profile collection name is invalid
    7
    Profile ID is missing
    8
    Profile ID is too long
    9
    Profile ID is invalid
    10
    Query string is missing
    11
    Client version is invalid
    12
    Query string is invalid
    13
    Starting profile record is invalid

    The following example shows how the message appears in the CICS region job output:

    
DFHWB0723 04/29/2009 19:30:10 S07CICP8 CWXN The CICS Web analyzer program 
           returned an error response. Program name: EQADCAN0. 
           RESPONSE: 8. REASON: rsnCode. Host IP address: 9.26.177.141. Client IP 
           address: 9.30.247.101. TCPIPSERVICE: EQAHTTP8