IZPDB messagesEdit online Messages that are issued during Db2® application provisioning have the format IZPDBnnnnx. IZPDB0011ECould not connect to the subsystem 'subsystemName' at URL 'hostname' with port 'port' and location 'location'.IZPDB0012Evariable1 is not valid for key variable2 in JSON body. Usage: variable3.IZPDB0013EJob FAILED - Name: '%1$s', Id '%2$s', Owner: '%3$s', Return code: '%4$s', Purpose: '%5$s'.IZPDB0039ECould not connect to the subsystem '%1$s' at URL '%2$s' with port '%3$s' and location '%4$s': Make sure hostname, port number, and location are correct. For encrypted connections, make sure the certificate for subsystem '%1$s' has been imported and SSL/TLS has been correctly configured. (SSL Exception: '%5$s').IZPDB0046EThe location '%1$s' provided for subsystem '%2$s' is incorrect. Make sure all parameters are correctly configured.IZPDB0047EThe following fields: '%1$s' are blank in '%2$s'. Those fields must have a value.IZPDB0048EYou cannot remove Db2 Object '%1$s' because it is referenced from instance '%2$s'.IZPDB0049IGRANT/REVOKE statements are commented out because subsystem attribute suppressDb2Grants = true.IZPDB0050WCould not determine the system name that the Db2 subsystem '%1$s' is running on.IZPDB0051IThe following GRANT/REVOKE statements were not executed because suppressDb2Grants=true:\n '%1$s'.IZPDB0052EThe name '%1$s' in the mapping is too long.IZPDB0053EThe name provided in the mapping '%1$s' is reserved for Db2 internal purposes.IZPDB0054WThe name provided: '%1$s' does not follow syntax rules. Probably, the subsystem was not updated.IZPDB0055W'%1$s' Contact your administrator to add the required object to the application using the PUT API. Adding a new object to the application may result in moving the instance '%2$s' to back-leveled state, so go to Instance details page and update the instance using Update from source option and retry submitting the PR.IZPDB0056W'%1$s' Contact your administrator to add the required object to the application using the PUT API. Adding a new object to the application may result in moving the instance '%2$s' to back-leveled state, so reopen the PR to sync it before using the Merge option.IZPDB0057ETempDatasetHlq must be specified globally or on a per subsystem level when using client authentication.IZPDB0060ESQL formatting does not support SET TERMINATOR, so retry without it.IZPDB0061ESQL formatting only supports US-ASCII characters, so retry with the supported characters.IZPDB0062EProblem identified on the ADB2FMP procedure. For more information, refer to Details.IZPDB0063EThere is a parsing error in the query.IZPDB0064ESQL formatting failed.IZPDB0065ESQL formatting has partially failed.IZPDB0066EThere is a syntax error in the query.IZPDB0067ESQL formatting for query has failed. {exception}.IZPDB0071ESet query acceleration failed for accelerator table '%1$s' in subsystem '%2$s' modified by user '%3$s'.IZPDB0072EJob FAILED - Name: 'job_name', ID: 'job_id', Return Code: 'rc', Submitted by User: 'user'. The following errors were encountered: 'error_text'.IZPDB0073EFailed to generate DDL using ADB2RE for the subsystem: 'subsystemName'. 'reason_text'.IZPDB0074EThe stored procedure ADB2RE (specifically, 'schema_name'.ADB2RE) is not found for the subsystem: 'subsystem_name'. Check the Subsystem Registration page.IZPDB0075WDDL generation has warnings or errors for some objects with the subsystem: 'subsystemName'. 'reason_text'.IZPDB0076EError(s) in specified ADB2RE parameters for the subsystem: 'subsystemName'.IZPDB0077EProcessing error in ADB2RE for subsystem: 'subsystemName'.IZPDB0078EError in dynamic allocation of the DDL data set (SQL-output) in ADB2RE for the subsystem: 'subsystemName'.IZPDB0079EError in dynamic allocation of the report data set (report-output) in ADB2RE for the subsystem: 'subsystemName'.IZPDB0080WThere are some warnings in ADB2RE while generating DDL for the subsystem: 'subsystemName'. 'reason_text'.IZPDB0081EObject type 'inputObjectType' is not supported for DDL generation for subsystem: 'subsystemName'.IZPDB0082EThe required object of type '%1$s' (specifically, '%2$s'.'%3$s') is not found while registering the subsystem:'%4$s'.IZPDB0083EThe 'specificName' value of object 'ObjectName'(in subsystem 'subsystemName') is missing, as it is required for object type 'Db2Function' to generate DDL using ADB2RE.IZPDB0084EThe 'database' value of object 'Table Space Object Name' (in subsystem 'subsystemName') is missing, as it is required for object type 'TableSpace' to generate DDL using ADB2RE.IZPDB0085EThe plan 'plan_name' or schema 'schema_name' is reserved for externally managed Db2 Administration Tool. Specify different plan or schema or enable option 'Use existing IBM Db2 Administration Tool'.IZPDB0086EThe drop operation is currently supported only by object type 'IX' and not by object type 'object_type'.IZPDB0087EDropping the following objects is not approved: 'objects'.IZPDB0088EOne or more dropped objects require approval before the pull request can be approved.IZPDB0089EObject with name 'object_name and type 'object_type' is not found in the instance 'instance'. IZPDB0090WCould not connect. Connection to url '%1$s' with '%2$s' returned null connection.IZPDB0091EFailed to synchronize the application: 'appName'. Reason: 'failureReason'.Parent topic: Messages