z/OS Connect EE runtime messages

BAQR0000I:  z/OS Connect Version {0} ({1})

   Explanation    The version and level of z/OS Connect that is currently running.
   Action    For information only.

BAQR0401E:  OSGI service {0} is not registered with the OSGI framework.

   Explanation    The mentioned service is not registered with the OSGI framework.
   Action    Review messages log for errors.

BAQR0402E:  Service {0} is not available to process work.

   Explanation    The specified service is not available to process work.
   Action    Review messages log and configuration files for possible errors.

BAQR0403W:  Service {0} specified under URL {1} is not available.

   Explanation    An attempt was made to process a service request. The service was not available.
   Action    Verify that the specified service was configured and that the service configuration contains all required attributes. Verify that the service name specified in the request URL matches the configured service name. Verify that the status of the service is STARTED. The HTTP response body of the failed request contains the associated message BAQR0431W.

BAQR0404W:  Service {0} encountered an error while processing a request under URL {1}.

   Explanation    The mentioned service encountered an error while processing a request.
   Action    Review messages log and HTTP response body for possible errors. The HTTP response body of the failed request contains the associated message BAQR0432W.

BAQR0405W:  The asynchronous request under URL {0} has timed out after {1} milliseconds.

   Explanation    The asynchronous request has timed out after the specified time.
   Action    Determine whether the request timed out because the value for the asyncRequestTimeout in server.xml is too low to allow for normal workload variation, or there was a problem in the processing of the request in the SOR. The HTTP response body of the failed request contains the associated message BAQR0433W.

BAQR0406W:  The {0} interceptor encountered an error while processing a request for service {1} under request URL {2}.

   Explanation    The named interceptor encountered an error.
   Action    Review messages log and the HTTP response body for possible errors. The HTTP response body of the failed request contains the associated message BAQR0434W.

BAQR0407W:  There is no authenticated user ID associated with the request.

   Explanation    The request can not be authorized as there is no authenticated user ID associated with the request.
   Action    Enable security authentication on the z/OS Connect EE server, or disable the authorization interceptor.

BAQR0409W:  User {0} is not authorized to perform the request.

   Explanation    The named user is not authorized to perform the request.
   Action    Verify that the user is authorized to perform requests.

BAQR0410E:  An attempt was made to obtain the {0} schema but the schema could not be located. Error: {1}.

   Explanation    The specified schema could not be located.
   Action    Verify that the specified schema is present and the data transformation configuration is correct.

BAQR0411E:  An error occurred while loading data transformation file {0} located at {1}. Error: {2}.

   Explanation    An error occurred while loading the specified data transformation file.
   Action    Verify that the transformation configuration files are valid and in the specified location.

BAQR0412E:  An error occurred during the data transformation for service {0}. The bind file in use is named {1} and located at {2}. Error: {3}.

   Explanation    The data transformation operation encountered an error.
   Action    Verify that the bind file is valid and the data transformation configuration is correct.

BAQR0413W:  The user registry for the currently active realm was not found.

   Explanation    The user registry for the currently active realm was not found.
   Action    Verify that a user registry is configured and security is enabled.

BAQR0414E:  Data transformer not found. Unable to process data transformation operations for service {0}.

   Explanation    A data transformer is not present to process data conversion.
   Action    Verify that a data transformer was configured and that an operation requiring transformation is not being called in error.

BAQR0415E:  A response payload was previously set while processing a request for service {0}. Subsequent attempts to set the response are rejected.

   Explanation    A response payload was previously set. Subsequent attempts to set the response are rejected.
   Action    Verify that the operation that sets the payload was not called in error more than once.

BAQR0416W:  An unsupported action parameter value of {0} was specified under request URL {1}.

   Explanation    An unsupported action parameter value was specified.
   Action    Verify that a supported action is entered in the request URL.

BAQR0417W:  The request payload could not be parsed. A JSON object format payload is expected. Error: {0}.

   Explanation    The request payload is not in the expected JSON format.
   Action    Verify that a request payload is of the appropriate format. Review messages log for more detailed error information.

BAQR0418W:  An unsupported media type of {0} was specified.

   Explanation    An unsupported media type was specified. A media type of application/json is required.
   Action    Verify that a correct media type was set in the request.

BAQR0419W:  A timeout or an error occurred that caused the complete method to be driven on the request's AsyncContext. Further actions on the request are not allowed.

   Explanation    A timeout or an error occurred that caused the complete method to be driven on the request's AsyncContext.
   Action    Verify that the timeout is appropriate for the work being executed. Review messages log for more detailed error information.

BAQR0420W:  The configured list of entries {0} under the invokeURI attribute definition for service {1} is invalid. The list is ignored.

   Explanation    The configured invokeURI attribute definition value does not contain a valid list of request URI strings.
   Action    Verify that the configured value contains valid request URI strings. If multiple URI entries are specified, they must be comma separated.

BAQR0421W:  The configured entry of {0} under the invokeURI attribute definition for service {1} is invalid. The entry is ignored.

   Explanation    The specified entry under the invokeURI attribute definition is not a valid request URI String.
   Action    Verify that the configured entry represents valid request URI string. For instance, spaces representing a request URI or empty request URIs are not allowed.

BAQR0422W:  The usage of the wildcard character in the configured invokeURI attribute definition entry of {0} for service {1} is invalid. The entry is ignored.

   Explanation    The configured invokeURI attribute entry for the mentioned service does not conform with the supported usage of the wildcard character.
   Action    Verify that the configured entry conforms with the documented usage of the wildcard character.

BAQR0423W:  The configured entry of {0} under the invokeURI attribute definition for service {1} is already assigned to service {2}. The entry is ignored.

   Explanation    The specified entry is already assigned to another service.
   Action    Verify that invokeURI entries representing valid request URI strings are unique for this installation.

BAQR0424W:  The service name associated with the service implementation {0} is invalid. The service registration is rejected.

   Explanation    The properties supplied with the service registration do not contain a valid name for the service.
   Action    Verify that the code used to register the service includes a service name as part of the registration call. Empty service names are not allowed.

BAQR0425W:  The service name {0} associated with service implementation {1} is already associated with another service. The service registration is rejected.

   Explanation    The name specified as part of the service registration is already associated with an existing service.
   Action    Use a unique name for the service being registered. All services registered with the z/OS Connect framework must have a unique service name.

BAQR0426W:  The response schema file location was not specified. The response schema file location is set to match the configured request schema location: {0}.

   Explanation    The response schema file location was not specified. The response schema file location is set to match the configured request schema location.
   Action    Verify that a response schema file location was specified and has a valid value.

BAQR0427W:  The {0} interceptor encountered an error while processing a request under request URL {1}.

   Explanation    The named interceptor encountered an error.
   Action    Review messages log and the HTTP response body for possible errors. The HTTP response body of the failed request contains the associated message BAQR0435W.

BAQR0428W:  The {0} interceptor encountered an error while processing a request for API {1} under request URL {2}.

   Explanation    The named interceptor encountered an error.
   Action    Review messages log and the HTTP response body for possible errors. The HTTP response body of the failed request contains the associated message BAQR0436W.

BAQR0429W:  API {0} encountered an error while processing a request under URL {1}.

   Explanation    The mentioned API encountered an error while processing a request.
   Action    Review messages log and HTTP response body for possible errors. The HTTP response body of the failed request contains the associated message BAQR0437W.

BAQR0430W:  User {0} is not authorized to perform the request on resource {1}.

   Explanation    The named user is not authorized to perform the request on the specified resource.
   Action    Verify that the user is authorized to perform requests on the specified resource.

BAQR0431W:  Service {0} is not available.

   Explanation    An attempt was made to process a service request. The service was not available.
   Action    Contact the system programmer to see message BAQR0403W in the messages log to determine the actions required.

BAQR0432W:  Service {0} encountered an error while processing a request.

   Explanation    The mentioned service encountered an error while processing a request.
   Action    Review messages log and HTTP response body for possible errors. Contact the system programmer to see message BAQR0404W in the messages log to determine the actions required.

BAQR0433W:  The asynchronous request has timed out after {0} milliseconds.

   Explanation    The asynchronous request has timed out after the specified time.
   Action    Contact the system programmer to see message BAQR0405W in the messages log to determine the actions required.

BAQR0434W:  The {0} interceptor encountered an error while processing a request for service {1}.

   Explanation    The named interceptor encountered an error.
   Action    Review messages log and the HTTP response body for possible errors. Contact the system programmer to see message BAQR0406W in the messages log to determine the actions required.

BAQR0435W:  The {0} interceptor encountered an error while processing a request.

   Explanation    The named interceptor encountered an error.
   Action    Contact the system programmer to see message BAQR0427W in the messages log to determine the actions required.

BAQR0436W:  The {0} interceptor encountered an error while processing a request for API {1}.

   Explanation    The named interceptor encountered an error.
   Action    Contact the system programmer to see message BAQR0428W in the messages log to determine the actions required.

BAQR0437W:  API {0} encountered an error while processing a request.

   Explanation    The mentioned API encountered an error while processing a request.
   Action    Contact the system programmer to see message BAQR0429W in the messages log to determine the actions required.

BAQR0438W:  API {0} is not available.

   Explanation    An attempt was made to process an API request. The API was not available.
   Action    Contact the system programmer to see message BAQR7012W in the messages log to determine the actions required.

BAQR0554E:  PassTicket generation failed. SAF return code: {0}, RACF return code: {1}, RACF reason code: {2}.

   Explanation    The generation of a PassTicket failed.
   Action    An exception occurred while trying to generate a PassTicket. Check the response codes in the error message to determine the cause of the error.

BAQR0555E:  PassTicket was not generated as no ID was found.

   Explanation    No ID was supplied on the HTTP request or in server configuration so no PassTicket was generated.
   Action    Ensure that the user attribute is set on the basicAuth element, SAF is configured, or that the user calling the service is authenticated with z/OS Connect EE.

BAQR0556E:  PassTicket was not generated as the ID {0} is greater than 8 characters in length.

   Explanation    The ID is too long.
   Action    Ensure that the supplied user ID is not greater than 8 characters in length.

BAQR7000I:  z/OS Connect EE API archive file {0} installed successfully.

   Explanation    The z/OS Connect EE API archive file for the named API installed successfully.
   Action    None.

BAQR7001E:  The z/OS Connect EE API archive file in {0} is incomplete.

   Explanation    The specified z/OS Connect EE API archive file is missing some required parts.
   Action    Correct the API archive file.

BAQR7003E:  z/OS Connect EE API archive file in {0} contains an invalid package.xml file. Error: {1}

   Explanation    The package.xml file does not contain a valid z/OS Connect EE API archive file definition.
   Action    Use supported z/OS Connect tooling to generate an API archive file with a valid package.xml file.

BAQR7004E:  z/OS Connect EE API {0} in {1} is already in use by another API.

   Explanation    The name of the API in the specified directory is already in use by another API.
   Action    Use a unique name for each API archive file to be installed.

BAQR7005E:  The base path {0} for z/OS Connect EE API {1} is already in use by z/OS Connect EE API {2}.

   Explanation    The base path for the specified z/OS Connect EE API is already in use by another z/OS Connect EE API.
   Action    Use a unique base path for each z/OS Connect EE API archive file to be installed.

BAQR7006E:  z/OS Connect EE API {0} has duplicate relative path {1}.

   Explanation    The specified z/OS Connect EE API contains duplicate relative paths.
   Action    Use a unique relative path for all path definitions.

BAQR7007E:  Invalid location for z/OS Connect EE API archive files. Error: {0}

   Explanation    The specified location for z/OS Connect EE API archive files cannot be used.
   Action    Correct the reported error and reload the configuration.

BAQR7008W:  z/OS Connect EE API {0} could not be installed.

   Explanation    The specified z/OS Connect EE API is required but the API archive file could not be installed.
   Action    Ensure the required z/OS Connect EE API archive file is correctly defined and available.

BAQR7009E:  z/OS Connect EE API {0} contains invalid relative path {1}.

   Explanation    The specified relative path is not valid.
   Action    Correct the relative path.

BAQR7012W:  API {0} specified under URL {1} is not available.

   Explanation    An attempt was made to process an API request. The API was not available.
   Action    Verify that the specified API was installed and that the API configuration contains all required attributes. Verify that the API name specified in the request URL matches the configured API name. The HTTP response body of the failed request contains the associated message BAQR0438W.

BAQR7013E:  z/OS Connect EE API archive file in {0} contains a package.xml file with no Swagger entry.

   Explanation    All z/OS Connect EE APIs must have an associated Swagger document.
   Action    Use supported z/OS Connect EE tooling to generate an API archive file with a valid package.xml file.

BAQR7014E:  z/OS Connect EE API {0} references a Swagger document {1} that does not exist

   Explanation    All z/OS Connect EE APIs must have an associated Swagger document.
   Action    Use supported z/OS Connect EE tooling to generate an API archive file with a valid package.xml file.

BAQR7015E:  z/OS Connect EE API {0} references a Swagger document {1} that either cannot be parsed or contains an invalid entry

   Explanation    The referenced Swagger document is not in the expected JSON format.
   Action    Verify that the Swagger document is formatted correctly. Review messages log for more detailed error information.

BAQR7016E:  z/OS Connect EE API archive file in {0} contains an invalid mapping file {1}. Error: {2}

   Explanation    The mapping file does not contain a valid mapping definition.
   Action    Use supported z/OS Connect EE tooling to generate an API archive file with supported mapping models.

BAQR7017E:  z/OS Connect EE API archive file in {0} uses unsupported mapping model type {1}.

   Explanation    The mapping file uses a mapping model type which is not supported by this version of z/OS Connect.
   Action    Use supported z/OS Connect tooling to generate an API archive file with supported mapping models.

BAQR7018E:  The HTTP request is missing parameter {0}.

   Explanation    The HTTP request is missing the named parameter.
   Action    Use the Swagger document to identify if the parameter is in the JSON payload, HTTP headers, query string or path.

BAQR7019E:  The parameter {0} could not be converted into the correct number format for API {1}.

   Explanation    The named parameter from a path, query string, or header could not be converted to the correct JSON number format.
   Action    Ensure the value of the named parameter is in a form which matches the correct JSON number format.

BAQR7021E:  An internal error occurred while loading the administration Swagger document.

   Explanation    An internal error occurred while loading the administration Swagger document.
   Action    If problems persist, contact IBM Software Support.

BAQR7022E:  Unknown status specified. Specify either started or stopped.

   Explanation    The status entered is not known.
   Action    Ensure the value of the status parameter is either 'started' or 'stopped'.

BAQR7023E:  The API is stopped.

   Explanation    The API is stopped and is not accepting requests.
   Action    Start the API.

BAQR7024E:  z/OS Connect EE API archive file install failed. The API contains an invalid package.xml file.

   Explanation    The package.xml file does not contain a valid z/OS Connect EE API archive file definition.
   Action    Correct the reported error.

BAQR7025E:  z/OS Connect EE API archive file install failed. The file is not a valid z/OS Connect EE API archive file.

   Explanation    The file is corrupt or decompression failed.
   Action    Validate that the file is correct and try again.

BAQR7026E:  z/OS Connect EE API archive file {0} install failed. An IO error occurred during installation.

   Explanation    An error occurred while saving files to disk.
   Action    Check for and resolve any storage or permission issues and try again.

BAQR7027E:  The z/OS Connect EE API status is started. The z/OS Connect EE API {0} cannot be deleted unless it is stopped.

   Explanation    The z/OS Connect EE API must be stopped before it can be deleted.
   Action    Stop the API and retry the delete.

BAQR7028E:  API has in flight requests. The z/OS Connect EE API {0} cannot be deleted until it has completed all outstanding requests.

   Explanation    The z/OS Connect EE API must have completed all outstanding requests before it can be deleted.
   Action    Wait for all requests to complete and retry the delete.

BAQR7029I:  z/OS Connect EE API archive file {0} deleted successfully.

   Explanation    The z/OS Connect EE API archive file for the named API deleted successfully.
   Action    None.

BAQR7030E:  An unsupported query string of {0} was specified.

   Explanation    An unsupported query string value was specified.
   Action    Verify that a supported query string is entered in the request URL.

BAQR7031E:  z/OS Connect EE API archive file install failed. The API name {0} is already in use.

   Explanation    The API name is in use by a previously installed API.
   Action    Use a unique name for each API archive file to be installed.

BAQR7032E:  The delete of z/OS Connect EE API archive file {0} failed. An IO error occurred during deletion.

   Explanation    An error occurred while removing the files from the disk.
   Action    Check for and resolve any storage or permission issues.

BAQR7033E:  Internal server error.

   Explanation    z/OS Connect EE encountered an error while processing a request.
   Action    Contact the z/OS Connect EE system administrator to check messages.log for the cause of the error.

BAQR7034I:  z/OS Connect EE API archive file {0} updated successfully.

   Explanation    The z/OS Connect EE API archive file for the named API updated successfully.
   Action    None.

BAQR7035E:  API not in stopped state. The z/OS Connect EE API {0} cannot be updated unless it is in the stopped state.

   Explanation    The z/OS Connect EE API must be stopped before it can be updated.
   Action    Stop the API and retry the update.

BAQR7036E:  API has in flight requests. The z/OS Connect EE API {0} cannot be updated until it has completed all outstanding requests.

   Explanation    The z/OS Connect EE API must have completed all outstanding requests before it can be updated.
   Action    Wait for all requests to complete and retry the update.

BAQR7037E:  z/OS Connect EE API archive file update failed. The API name in the API archive file {0} does not match the API being updated {1}.

   Explanation    The z/OS Connect EE API archive file must match the ID of the API being updated.
   Action    Ensure the correct API archive file is being used to update the API.

BAQR7038E:  Method not allowed.

   Explanation    The resource does not support the specified method.
   Action    Check the Allow header for a list of methods supported by the resource.

BAQR7039E:  z/OS Connect EE API archive file location {0} does not exist.

   Explanation    The API archive file location does not exist. z/OS Connect EE requires the location to exist to be able to deploy APIs.
   Action    Change the location to a directory that exists and restart the server, or create the required directories.

BAQR7040E:  Resource {0} not found.

   Explanation    The specified resource could not be located.
   Action    Correct the URL to match a configured resource, or configure an API or service to use the specified URL.

BAQR7041E:  Installation of the z/OS Connect EE service archive file failed. The file {0} is not a valid z/OS Connect EE service archive file. Error: {1}.

   Explanation    The service archive file is not valid. See the error message for more information.
   Action    Correct the reported error and try again.

BAQR7042E:  z/OS Connect EE service archive file location {0} does not exist.

   Explanation    The service archive file location does not exist. z/OS Connect EE must have a valid location to deploy services.
   Action    Change the location to a directory that exists or create the required directories, then restart the server.

BAQR7043I:  z/OS Connect EE service archive {0} installed successfully.

   Explanation    The z/OS Connect EE service archive for the named service was installed successfully.
   Action    None.

BAQR7044I:  z/OS Connect EE service archive {0} updated successfully.

   Explanation    The z/OS Connect EE service archive for the named service was updated successfully.
   Action    None.

BAQR7045I:  z/OS Connect EE service archive {0} deleted.

   Explanation    The z/OS Connect EE service archive for the named service was deleted.
   Action    None.

BAQR7046W:  The service name {0} in service archive {1} is already associated with another service. The service was not installed.

   Explanation    The name in the service archive is already associated with another service.
   Action    Use a unique name for the service being installed.

BAQR7047E:  Service {0} does not support the data transformation specified by the WSBind file.

   Explanation    The configured data transform is unable to process data for the service as the WSBind file uses multiple containers, which the service provider does not support.
   Action    If the CICS program uses a single container, create the WSBind file using REQMEM and RESPMEM instead of REQUEST-CHANNEL and RESPONSE-CHANNEL. If the CICS program uses multiple containers the WOLA service provider cannot be used.

BAQR7048E:  Service {0} did not return container {1} for data transformation.

   Explanation    The configured data transform is unable to process data for the service as the service did not return the named container which the data transformer requires.
   Action    Confirm whether the CICS program should return the named container and either correct the data transformer configuration or CICS program accordingly.

BAQR7049E:  Service {0} returned CHAR container {1} for BIT data transformation.

   Explanation    The configured data transform is unable to process data for the service as the service returned a CHAR container instead of a BIT container.
   Action    Confirm whether the container should be CHAR or BIT and either correct the data transformer configuration or CICS program accordingly.

BAQR7050E:  Service {0} is unable to process data returned by the configured data transformer.

   Explanation    The data transform configured for the service has produced data in a format that the service provider cannot process.
   Action    Ensure that the data transform is configured to produce data that the service provider is capable of processing.

BAQR7051E:  An unexpected error occurred. If the problem persists, contact IBM Software Support.

   Explanation    An unexpected error occurred.
   Action    If the error occurs again contact IBM Software Support.

BAQR7052E:  The service {0} requested the wrong type of data structure from the data transformer.

   Explanation    The service provider has requested the wrong structure for the configured service.
   Action    Confirm whether the service has been correctly configured or whether the service provider needs updating to support the structure type.

BAQR7053E:  The request payload for service {0} could not be parsed. Error: {1}.

   Explanation    The JSON payload sent by the service client is not valid to the service schema or API Swagger documentation.
   Action    Review the additional diagnostic message that describes the symptom. Check the service schema or API Swagger documentation against the client implementation.

BAQR7054E:  An error occurred during the data transformation for service {0}. Error: {1}.

   Explanation    The data transformation operation encountered an error.
   Action    Review the additional diagnostic message that further describes the symptom. Verify that the field values sent in by the client or out by the native application are valid for the data types specified in the service interface schema.

BAQR7055E:  z/OS Connect EE API archive file installation failed. The API archive file {0} is invalid.

   Explanation    The API archive file type is not recognized as a valid z/OS Connect EE API.
   Action    Ensure that the file extension of the API archive file that is used for installing an API is aar.

BAQR7056I:  z/OS Connect EE policy {0} is active.

   Explanation    The named z/OS Connect EE policy is active for API requests.
   Action    None.

BAQR7057E:  Installation failed for the z/OS Connect EE API archive file {0} associated with API {1}.

   Explanation    The z/OS Connect EE API archive file could not be installed because the API name already exists. This would delete an existing API.
   Action    Review the API archive file and ensure that names are unique.

BAQR7058E:  z/OS Connect EE API archive file installation failed. The z/OS Connect EE API archive file {0} already exists.

   Explanation    The z/OS Connect EE API archive file could not be installed because the file name already exists.
   Action    Remove the file and try again.

BAQR7059E:  The context {0} is not available.

   Explanation    The servlet attempted to initialize but the context is not available. This can be caused by the server being started and immediately stopped before initialization is complete.
   Action    Review messages log for errors.

BAQR7060E:  z/OS Connect EE service install failed. The service name {0} is already in use.

   Explanation    The service name is in use by a previously installed service.
   Action    Use a unique name for each service to be installed.

BAQR7061E:  z/OS Connect EE service install failed. Service archive file missing.

   Explanation    You must provide a service archive file in the body of the REST API invocation.
   Action    Call the REST API with a service archive file as the body of the call.

BAQR7062E:  z/OS Connect EE service install failed. The provider property {0} in the service archive file does not match any of the installed service providers.

   Explanation    An attempt was made to deploy a service archive file specifying a service provider that is not currently installed.
   Action    You must install the appropriate service provider before attempting to deploy a service of this type.

BAQR7063E:  z/OS Connect EE service delete failed. The service {0} was not installed using a service archive file.

   Explanation    Only service archive based services can be deleted using the RESTful administration interface.
   Action    Update the server configuration to delete a non service archive based service.

BAQR7064E:  The service archive file {0} was not found.

   Explanation    The service archive file might have previously been manually deleted.
   Action    No further action is necessary.

BAQR7065E:  The delete of z/OS Connect EE service archive file {0} failed. An IO error occurred during deletion.

   Explanation    An error occurred while removing the files from the disk.
   Action    Check for and resolve any storage or permission issues.

BAQR7066E:  The z/OS Connect EE service status is started. The z/OS Connect EE service cannot be deleted unless it is stopped.

   Explanation    The z/OS Connect EE service must be stopped before it can be deleted.
   Action    Stop the service and retry the delete.

BAQR7067E:  z/OS Connect EE service archive file install failed. An IO error occurred during installation.

   Explanation    An error occurred while saving files to disk.
   Action    Check for and resolve any storage or permission issues and try again.

BAQR7068E:  Service not in stopped state. The z/OS Connect EE service cannot be updated unless it is in the stopped state.

   Explanation    The z/OS Connect EE service must be stopped before it can be updated.
   Action    Stop the service and retry the update.

BAQR7069I:  z/OS Connect EE service {0} deleted successfully.

   Explanation    The z/OS Connect EE service archive file for the named service deleted successfully.
   Action    None.

BAQR7070E:  Service administration APIs are not available.

   Explanation    An attempt was made to invoke a service administration API. The <zosconnect_services> configuration element must be defined in order to make service administration APIs available.
   Action    Add the <zosconnect_services> element to the server configuration in order to make service administration APIs available.

BAQR7071E:  Installation of the z/OS Connect EE service archive file failed. The file provided on the administration API call is not a valid z/OS Connect EE service archive file. Error: {0}.

   Explanation    The service archive file provided in the administration API call is not valid. See the error message for more information.
   Action    Correct the reported error and try again.

BAQR7072I:  z/OS Connect EE policy {0} has been deactivated.

   Explanation    The named z/OS Connect EE policy is no longer active for API requests.
   Action    None.

BAQR7073E:  The service response property {0}, which is mapped to header {1}, is missing from the service response body for API {2}.

   Explanation    The header is required, but a value cannot be assigned unless the mapped service response property is present in the service response body.
   Action    Ensure that the mapped field is included in the service response body. The service might have been updated after it was imported into the API. The updated service archive needs to be re-imported into the API.

BAQR7074E:  The mandatory JSON response property {0} is missing for API {1}.

   Explanation    The JSON response property is required, by the API response mapping, but has not been provided by the service provider.
   Action    Ensure that the mapped field is included in the service response body. The service might have been updated after it was imported into the API. The updated service archive needs to be re-imported into the API.

BAQR7075E:  The mapping input path {0} is invalid for API {1}.

   Explanation    The input path should start with path parameters, query parameters, or headers.
   Action    Redeploy the API directly from the API project to ensure valid mapping metadata.

BAQR7076E:  The mapping array separator character {0} is invalid for API {1}.

   Explanation    The mapping array separator must be csv, ssv, or pipes. For path parameters you can also specify tsv. For query parameters you can also specify tsv or multi.
   Action    Redeploy the API directly from the API project to ensure valid mapping metadata.

BAQR7077E:  The value {0} for the path attribute and the value {1} for the shape attribute from the array mapping do not match for API {2}.

   Explanation    The output path does not contain the correct number of entries.
   Action    Redeploy the API directly from the API project to ensure valid mapping metadata.

BAQR7078E:  The shape attribute has an invalid level number for section {0} for API {1}.

   Explanation    The value of the shape attribute must be a sequence of comma-separated numbers starting with 1 and must increment by 1. A valid example would be shape="1,2,3[3..3]". An invalid example would be shape="1,2,4[3..3]".
   Action    Redeploy the API directly from the API project to ensure valid mapping metadata.

BAQR7079E:  A matching closing bracket is missing from the mapping shape attribute in section {0} for API {1}.

   Explanation    The corresponding closing bracket is missing in the shape attribute.
   Action    Redeploy the API directly from the API project to ensure valid mapping metadata.

BAQR7080E:  The shape attribute has an invalid array limits specification for section {0} for API {1}.

   Explanation    The array for the path does not contain the correct number of entries.
   Action    Redeploy the API directly from the API project to ensure valid mapping metadata.

BAQR7081E:  The number of values provided ({0}) for the JSON property {1} is invalid for API {2}.

   Explanation    The array passed in on the call does not contain the correct number of entries.
   Action    Update the client of the API to provide a valid number of entries.

BAQR7082I:  z/OS Connect EE policy {0} is active for API {1}.

   Explanation    The named z/OS Connect EE policy is active for API requests for the named API.
   Action    None.

BAQR7083I:  z/OS Connect EE policy {0} has been deactivated for API {1}.

   Explanation    The named z/OS Connect EE policy is no longer active for API requests for the named API.
   Action    None.

BAQR7084W:  The API archive file for the required z/OS Connect EE API {0} has been deleted.

   Explanation    The specified z/OS Connect EE API is required but the API archive file has been deleted.
   Action    Ensure the required z/OS Connect EE API archive file is correctly defined and available.

BAQR7085E:  Installation of the z/OS Connect EE service archive file failed. The service archive file {0} exploits capabilities that are not supported by the currently running version of the z/OS Connect EE server. Provider: {1}. Exploited capabilities: {2}. Supported capabilities: {3}.

   Explanation    The deployment of the service had to be blocked, because it exploits capabilities that are not supported by the currently running version of the z/OS Connect EE server.
   Action    Upgrade the z/OS Connect EE server to the latest level, and retry the deployment of the service.

BAQR7086E:  Installation of the z/OS Connect EE API archive file failed. The archive file for API {0} exploits capabilities that are not supported by the currently running version of the z/OS Connect EE server. Exploited capabilities: {1}. Supported capabilities: {2}.

   Explanation    The deployment of the API had to be blocked, because it exploits capabilities that are not supported by the currently running version of the z/OS Connect EE server.
   Action    Upgrade the z/OS Connect EE server to the latest level, and retry the deployment of the API.

BAQR7087E:  The boolean operator {0} is invalid.

   Explanation    The value of the boolean operator is not supported.
   Action    Redeploy the API directly from the API project to ensure valid mapping metadata.

BAQR7088E:  The property value {0} for path {1} is a data type that is incompatible with boolean operator {2}.

   Explanation    The response property data type is incompatible with the boolean operator specified in the API.
   Action    If the service has changed, reimport it into the API project, resolve any errors, and redeploy the API project.

BAQR7089E:  The property value {0} for path {1} is a data type that is incompatible with the compare value {2} specified in the API rule {3}.

   Explanation    The response property data type is incompatible with the compare value specified in the API rule.
   Action    If the service has changed, reimport it into the API project, resolve any errors, and redeploy the API project.

BAQR7090E:  The path {0} with property value {1} is an unsupported data type {2}.

   Explanation    An unexpected error occurred.
   Action    If the error occurs again contact IBM Software Support.

BAQR7091E:  z/OS Connect EE service update failed. The service {0} was not installed using a service archive file.

   Explanation    Only service archive based services can be updated using the RESTful administration API.
   Action    Update the server configuration to delete the non service archive based service and redeploy the service.

BAQR7092E:  z/OS Connect EE service update failed. The service name in the service archive does not match the service being updated.

   Explanation    The z/OS Connect EE service archive must match the ID of the service being updated.
   Action    Ensure the correct service archive is being used to update the service.

BAQR7093E:  The z/OS Connect EE API archive file in {0} is missing the mapping model file.

   Explanation    The specified z/OS Connect EE API archive file is missing the mapping model file.
   Action    Redeploy the API directly from the API project to ensure a valid mapping model file is included.

BAQR7094E:  The z/OS Connect EE API archive file in {0} is missing the HTTP transform file.

   Explanation    The specified z/OS Connect EE API archive file is missing the HTTP transform file.
   Action    Redeploy the API directly from the API project to ensure a valid HTTP transform file is included.

BAQR7095E:  Installation of the z/OS Connect EE API archive file {0} failed. The API contains an invalid manifest.yml file. Error: {1}.

   Explanation    The manifest file cannot be parsed.
   Action    If the API archive file was produced with a version of the API Toolkit prior to 3.0.5.0, the manifest file should be deleted from the API project and the API archive file regenerated. If the API archive file was produced with a version of the API Toolkit at 3.0.5.0 or later, use the API Toolkit to generate an API archive file with a valid manifest.yml file.

BAQR7096I:  z/OS Connect EE interceptor list {0} is active at the global level with interceptors: {1}.

   Explanation    The named z/OS Connect EE interceptor list is active for global requests. Interceptors referenced by the list will only be included in the message if they have valid configuration and have been activated.
   Action    None.

BAQR7097I:  z/OS Connect EE interceptor list {0} has been deactivated.

   Explanation    The named z/OS Connect EE interceptor list is no longer active for global requests.
   Action    None.

BAQR7098I:  z/OS Connect EE interceptor list {0} is active for API {1} with interceptors: {2}.

   Explanation    The named z/OS Connect EE interceptor list is active for requests for the named API. Interceptors referenced by the list will only be included in the message if they have valid configuration and have been activated.
   Action    None.

BAQR7099I:  z/OS Connect EE interceptor list {0} has been deactivated for API {1}.

   Explanation    The named z/OS Connect EE interceptor list is no longer active for requests for the named API.
   Action    None.

BAQR7100I:  z/OS Connect EE interceptor list {0} is active for service {1} with interceptors: {2}.

   Explanation    The named z/OS Connect EE interceptor list is active for requests for the named service. Interceptors referenced by the list will only be included in the message if they have valid configuration and have been activated.
   Action    None.

BAQR7101I:  z/OS Connect EE interceptor list {0} has been deactivated for service {1}.

   Explanation    The named z/OS Connect EE interceptor list is no longer active for requests for the named service.
   Action    None.

BAQR7102W:  No valid interceptors found in interceptor list {0}.

   Explanation    The named interceptor list has been activated but no interceptors have been provided for it. This may indicate the interceptorRef attribute on the zosconnect_zosConnectInterceptors element does not reference any interceptors, or there is a configuration error with all the interceptors it references.
   Action    For any referenced interceptors, check if they are configured correctly. If no interceptors are required, remove the zosconnect_zosConnectInterceptors element.

BAQR7103W:  No valid interceptors found in interceptor list {0} for API {1}.

   Explanation    The named interceptor list has been activated but no interceptors have been provided for it. This may indicate the interceptorRef attribute on the zosconnect_zosConnectInterceptors element does not reference any interceptors, or there is a configuration error with all the interceptors it references.
   Action    For any referenced interceptors, check if they are configured correctly. If no interceptors are needed, remove the zosconnect_zosConnectInterceptors element.

BAQR7104W:  No valid interceptors found in interceptor list {0} for service {1}.

   Explanation    The named interceptor list has been activated but no interceptors have been provided for it. This may indicate the interceptorRef attribute on the zosconnect_zosConnectInterceptors element does not reference any interceptors, or there is a configuration error with all the interceptors it references.
   Action    For any referenced interceptors, check if they are configured correctly. If no interceptors are needed, remove the zosconnect_zosConnectInterceptors element.

BAQR7105W:  Interceptors {0} and {1} are using the same stakeholder identifier {2} for selective tracking.

   Explanation    Two tracking interceptors are using the same stakeholder identifier. Selective tracking might not produce the expected results.
   Action    Contact the monitoring product interceptor providers to resolve the issue.

BAQR7106W:  Interceptor {0} has specified a stakeholder identifier {1} that is not in the range A-Z or a-z.

   Explanation    Stakeholder identifiers, used for selective tracking, must be in one of the specified character ranges.
   Action    Contact the monitoring product interceptor provider to resolve the issue.

BAQR7107W:  Stakeholder identifier {0} is not in the range A-Z or a-z.

   Explanation    An interceptor implementing selective tracking has used a stakeholder identifier that is not in one of the supported ranges.
   Action    Contact the monitoring product interceptor provider to resolve the issue.

BAQR7108W:  An interceptor has attempted to selectively track an administration request, using the stakeholder identifier {0}.

   Explanation    An interceptor implementing selective tracking has attempted to track an administration request. This is not supported.
   Action    Contact the monitoring product interceptor provider to resolve the issue.

BAQR7109W:  An interceptor has made an incorrect attempt to add a tracking token to a request, using the stakeholder identifier {0}.

   Explanation    An interceptor must implement the TrackingInterceptor interface and set the Tracking Token in the preInvoke method in order to selectively track requests.
   Action    Contact the monitoring product interceptor provider to resolve the issue.

BAQR7110W:  Insufficient space in the tracking token for this request to add the stakeholder identifier {0}.

   Explanation    The capacity for including stakeholder tokens for selective tracking of this request has been exceeded.
   Action    Contact the monitoring product interceptor provider to resolve the issue.

BAQR7111E:  z/OS Connect EE API archive file {0} install failed. An IO read error occurred during installation. Error: {1}.

   Explanation    An error occurred while reading files from disk.
   Action    Check for and resolve any storage or permission issues and try again.

BAQR7112E:  z/OS Connect EE API archive file install failed. The API archive file does not contain a package.xml file.

   Explanation    The package.xml file does not exist.
   Action    Ensure the z/OS Connect EE API archive file contains a valid package.xml file and redeploy.

BAQR7113E:  Unexpected error occurred during JSON serialization. Details: {0}

   Explanation    An error occurred while serializing JSON.
   Action    Review the additional diagnostic message that further describes the symptom.

BAQR7115E:  The asserted user ID {0} is not authorized to invoke the API requester on resource {1}.

   Explanation    The asserted user ID does not have authority to invoke an API requester on the specified resource.
   Action    Contact the system programmer to grant the asserted user access to invoke an API requester on the specified resource.

BAQR7116W:  Failed to obtain the SAF cache.

   Explanation    The SAF cache could not be obtained. SAF information will not be cached which may impact performance.
   Action    If problems persist, contact IBM Software Support.

BAQR7117I:  Successfully cleared the SAF cache.

   Explanation    A request was made to clear the SAF cache and the request was completed successfully.
   Action    None.

BAQR7118I:  The configuration {0} is not available.

   Explanation    The servlet attempted to initialize but the configuration is not available.
   Action    Review messages log for errors.

BAQR7119E:  The value {0} provided in the API call is not valid for data type {1}.

   Explanation    A header, path parameter, or query parameter is defined in the API with a certain data type. The value passed in on the call is not valid for that data type.
   Action    Find where the value noted in the error message is provided in the API call. Replace that value for subsequent calls with a value that is valid for the data type noted in the error message.

BAQR7120E:  The bidi configuration {0} referenced by service {1} was not found.

   Explanation    Service invocation cannot proceed when a referenced bidi configuration is missing.
   Action    Verify that the referenced bidi configuration is defined in server.xml and refresh the server configuration.

BAQR7121W:  An invalid input Arabic shaping option {0} is specified in bidi configuration {1}.

   Explanation    Referencing services cannot perform input bidi conversions when invalid input Arabic shaping options are specified.
   Action    Verify that the specified input Arabic shaping options are supported by this version of z/OS Connect.

BAQR7122W:  An invalid output Arabic shaping option {0} is specified in bidi configuration {1}.

   Explanation    Referencing services cannot perform output bidi conversions when invalid output Arabic shaping options are specified.
   Action    Verify that the specified output Arabic shaping options are supported by this version of z/OS Connect.

BAQR7123W:  Conflicting or duplicate input Arabic shaping options {0} and {1} are specified in bidi configuration {2}.

   Explanation    Referencing services cannot perform input bidi conversions when conflicting or duplicate input Arabic shaping options are specified.
   Action    Correct the specified input Arabic shaping options.

BAQR7124W:  Conflicting or duplicate output Arabic shaping options {0} and {1} are specified in bidi configuration {2}.

   Explanation    Referencing services cannot perform output bidi conversions when conflicting or duplicate output Arabic shaping options are specified.
   Action    Correct the specified output Arabic shaping options.

BAQR7125E:  An invalid input Arabic shaping option {0} was specified in bidi configuration {1} referenced by service {2}.

   Explanation    The service cannot perform input bidi conversions because an invalid input Arabic shaping option was specified in the referenced bidi configuration.
   Action    Verify that the input Arabic shaping options specified in the referenced bidi configuration are supported by this version of z/OS Connect.

BAQR7126E:  An invalid output Arabic shaping option {0} was specified in bidi configuration {1} referenced by service {2}.

   Explanation    The service cannot perform output bidi conversions because an invalid output Arabic shaping option was specified in the referenced bidi configuration.
   Action    Verify that the output Arabic shaping options specified in the referenced bidi configuration are supported by this version of z/OS Connect.

BAQR7127E:  Conflicting or duplicate input Arabic shaping options {0} and {1} were specified in bidi configuration {2} referenced by service {3}.

   Explanation    The service cannot perform input bidi conversions because conflicting or duplicate output Arabic shaping options were specified in the referenced bidi configuration.
   Action    Correct the input Arabic shaping options specified in the referenced bidi configuration.

BAQR7128E:  Conflicting or duplicate output Arabic shaping options {0} and {1} were specified in bidi configuration {2} referenced by service {3}.

   Explanation    The service cannot perform output bidi conversions conflicting or duplicate output Arabic shaping options were specified in the referenced bidi configuration.
   Action    Correct the output Arabic shaping options specified in the referenced bidi configuration.

BAQR7130I:  z/OS Connect EE API {0} was registered successfully for API Discovery.

   Explanation    The API documentation for the named z/OS Connect EE API is now available to the API Discovery feature.
   Action    None.

BAQR7131E:  API Discovery registration for z/OS Connect EE API {0} failed.

   Explanation    An error occurred when registering the named z/OS Connect EE API for use with the API Discovery feature.
   Action    Review messages log for errors.

BAQR7132I:  z/OS Connect EE API {0} was unregistered successfully for API Discovery.

   Explanation    The API documentation for the named z/OS Connect EE API is no longer available to the API Discovery feature.
   Action    None.

BAQR7133E:  API Discovery unregistration for z/OS Connect EE API {0} failed.

   Explanation    An error occurred when registering the named z/OS Connect EE API for use with the API Discovery feature.
   Action    Review messages log for errors.