Message ID Reference

IBM Z Open Editor has been localized for various display languages. It now also provides with each message that it displays as the result of a user action, a unique identifier. This identifier can be used when submitting tickets by simply mentioning the id. I also helps technical support to understand a message even when the text is provided in a foreign language, for example, in a screen shot or a log file. This page is the reference of all identifiers currently being used and the English text that comes with them.

  • CRRZG5001E
    • Could not get the URI of the preprocessor input file. Ensure that the workspace and input file is opened correctly in VS Code.
  • CRRZG5002E
    • PreprocessorCommand: The local preprocessor command "{0}" failed to execute. The error returned was "{1}".
  • CRRZG5003E
    • The local preprocessor command failed to execute. Check the Output view for details.
  • CRRZG5004E
    • Could not compare the files {0} and {1}.\n{2}
  • CRRZG5005E
    • A valid ZAPP profile of the type "preprocessor" was not found. Add it to your ZAPP file or ensure it is specified correctly.
  • CRRZG5006E
    • Could not read the "{0}" setting from ZAPP preprocessor profile. Check the documentation for preprocessor ZAPP profiles.
  • CRRZG5007E
    • The preprocessor profile in your ZAPP file does not have a command to run. Ensure that your ZAPP file has a valid preprocessor profile and that it has a command property.
  • CRRZG5008E
    • The preprocessor profile in your ZAPP file does not include an "outputPath" property to save the output file to. Ensure that your ZAPP file has a valid preprocessor profile and that it has all required properties.
  • CRRZG5009E
    • The location specified for the outputPath property in your preprocessor ZAPP profile was not found in your current VS Code workspace. Create the location or fix the property's value.
  • CRRZG5010E
    • Multiple output locations were specified for the "outputPath" property in your preprocessor ZAPP profile. You can only specify one of "{0}".
  • CRRZG5011W
    • The member name already starts with a special character $, it may be overwritten by the output file "{0}"
  • CRRZG5012W
    • Data set member exists, so changing output file name to "{0}"
  • CRRZG5013E
    • Could not create XML content on path "{0}".
  • CRRZG5014E
    • Unable to create "{0}". The error returned was "{1}"
  • CRRZG5015I
    • RemotePreprocessorCommand: data set "{0}" exists.
  • CRRZG5016E
    • Unable to fetch data set member "{0}".The error returned was "{1}"
  • CRRZG5017I
    • RemotePreprocessorCommand: Creating data set member "{0}".
  • CRRZG5018E
    • Unable to create data set member "{0}". The error returned was "{1}"
  • CRRZG5019I
    • RemotePreprocessorCommand: Deleting data set member "{0}".
  • CRRZG5020E
    • Unable to delete data set member "{0}". The error returned was "{1}"
  • CRRZG5021E
    • You specified an MVS Property Group in your settings, but no valid Zowe Profile was found to use for loading files from MVS. Create a Zowe Profile and try again.
  • CRRZG5022I
    • IssueTSOCommand: TSO command : "{0}", executed using "{1}" profile which returned response : "{2}"
  • CRRZG5023E
    • TSO command : "{0}", executed using "{1}" profile failed. Check the Output view for details.
  • CRRZG5024W
    • GetTsoParams: TSO profile does not exist, using account value of "". Please check your zowe config to update: {0}.
  • CRRZG5025W
    • TSO profile does not exist, using account value of "". Please check your zowe config to update.
  • CRRZG5026W
    • GetTsoParams: Using tso profile: "{0}", with value: {1}, which does not have an account value set. Using account value of "". Please check your zowe config to update: {2}.
  • CRRZG5027W
    • Using tso profile: "{0}", with value: {1}, which does not have an account value set. Using account value of "". Please check your zowe config to update.
  • CRRZG5028E
    • Could not read the "{0}" attribute from ZAPP preprocessor profile. Please check the high level qualifier. If not created, check the documentation for preprocessor ZAPP profiles.
  • CRRZG5029E
    • Unable to retrieve spool files for {0}({1}). The error returned was {2}
  • CRRZG5030E
    • Unable to download spool content for {0}:{1} - {2}. The error returned was "{3}"
  • CRRZG5031I
    • Successfully downloaded {0}:{1}.
  • CRRZG5032E
    • Unable to download {0}:{1}. The error returned was "{2}"
  • CRRZG5033E
    • Unable to download spool files for {0}. The error returned was "{1}"
  • CRRZG5034I
    • Successfully downloaded spool files for the following jobs: {0}.
  • CRRZG5035I
    • Issued stop command for {0}. {1}
  • CRRZG5036E
    • An error occurred while issuing stop command for {0}. The error returned was "{1}"
  • CRRZG5037I
    • No command provided. Action cancelled.
  • CRRZG5038I
    • Issued modify command for {0}. {1}
  • CRRZG5039E
    • An error occurred while issuing modify command for {0}. The error returned was "{1}"
  • CRRZG5040W
    • Are you sure you want to delete the following jobs:\n\n{0}
  • CRRZG5041E
    • An error occurred while deleting {0}. The error returned was "{1}"
  • CRRZG5042I
    • Successfully deleted the following job(s): {0}.
  • CRRZG5043E
    • An error occurred while cancelling {0}. The error returned was "{1}"
  • CRRZG5044I
    • Successfully cancelled the following job(s): {0}.
  • CRRZG5045E
    • Unable to retrieve JCL for {0}. The error returned was "{1}"
  • CRRZG5046E
    • Unable to load jobs for new filter. The error returned was "{0}"
  • CRRZG5047E
    • Unable to retrieve jobs. The error returned was "{0}"
  • CRRZG5048E
    • Unable to retrieve job with ID {0}. The error returned was "{1}"
  • CRRZG5049W
    • Filter already exists.
  • CRRZG5050I
    • Created new job filter: Owner: {0} | Prefix: {1} | Status: {2}
  • CRRZG5051E
    • Unable to create new filter.
  • CRRZG5052E
    • {0} cannot exceed 8 characters.
  • CRRZG5053E
    • The filter could not be added to the settings.
  • CRRZG5054I
    • Filter creation cancelled.
  • CRRZG5055I
    • Filter creation cancelled.
  • CRRZG5056I
    • Data set creation cancelled.
  • CRRZG5057I
    • Data set creation cancelled.
  • CRRZG5058E
    • Invalid data set name. Name must be shorter than 44 characters.
  • CRRZG5059E
    • Invalid data set name. Please provide qualifier.
  • CRRZG5060E
    • Invalid character {0}. Each qualifier must begin with an alphabetic character (A to Z) or the special character @, #, or $.
  • CRRZG5061E
    • Invalid data set name. Each qualifier must be 1 to 8 characters in length.
  • CRRZG5062I
    • Successfully created {0}
  • CRRZG5063E
    • Unable to create {0}. The error returned was "{1}"
  • CRRZG5064E
    • Failed to request migration of {0}. The error returned was "{1}"
  • CRRZG5065I
    • Requested migration of {0}
  • CRRZG5066E
    • Failed to request recall for {0}. The error returned was "{1}"
  • CRRZG5067I
    • Requested recall for {0}
  • CRRZG5068I
    • Successfully renamed {0} to {1}.
  • CRRZG5069E
    • Rename failed. The error returned was "{0}"
  • CRRZG5070I
    • Rename cancelled.
  • CRRZG5071I
    • Allocated a new data set "{0}" with the same attributes as "{1}".
  • CRRZG5072E
    • Allocation failed. The error returned was "{0}"
  • CRRZG5073I
    • Allocation cancelled.
  • CRRZG5075W
    • This will permanently remove these data sets and/or members from your system.
  • CRRZG5076E
    • Unable to open "{0}". The error returned was "{1}"
  • CRRZG5077E
    • Unable to retrieve members for "{0}". The error returned was "{1}"
  • CRRZG5080W
    • This will permanently remove these members from your system.
  • CRRZG5081W
    • This will permanently remove this member from your system.
  • CRRZG5082E
    • Unable to delete {0}. The error returned was "{1}"
  • CRRZG5083I
    • Successfully deleted "{0}".
  • CRRZG5084E
    • Unable to submit member "{0}" as job . The error returned was "{1}"
  • CRRZG5085I
    • Successfully submitted "{0}".
  • CRRZG5086I
    • Successfully created "{0}({1})".
  • CRRZG5087E
    • Unable to create {0}({1}). The error returned was "{2}"
  • CRRZG5088I
    • Successfully uploaded member(s).
  • CRRZG5089E
    • Failed to upload "{0}". The error returned was "{1}"
  • CRRZG5090E
    • Failed to push the new contents of "{0}" to z/OS host using the profile "{1}". The error returned was "{2}"
  • CRRZG5091E
    • Unable to delete "{0}". The error returned was "{1}"
  • CRRZG5092I
    • Successfully deleted the following data set(s): {0}.
  • CRRZG5093E
    • Unable to search for members {0} {1}. The error returned was '{2}'
  • CRRZG5094E
    • Unable to search for members {0} {1}. The error returned was '{2}'
  • CRRZG5095E
    • Unable to retrieve data sets for the requested pattern(s). The error returned was "{0}"
  • CRRZG5096I
    • No sequential data sets were found with the content "{0}".
  • CRRZG5097E
    • An error has occurred while searching sequential data sets for the requested content. Search results will not be displayed.
  • CRRZG5098I
    • No data sets were found that matched the pattern "{0}".
  • CRRZG5099E
    • An error occured while filtering data sets by the provided data set name. The error returned was "{0}"
  • CRRZG5100E
    • Unable to search for members {0} {1}. The error returned was '{2}'
  • CRRZG5101E
    • The active filter does not support listing multiple individual partitioned or sequentual data sets. If you want to match to multiple data sets, try using a wildcard (*).
  • CRRZG5102I
    • The z/OS Resources Table has been reloaded due to edits to the Zowe configuration file.
  • CRRZG5103E
    • Unable to locate the Zowe configuration file for the profile {0}.
  • CRRZG5104I
    • Creation cancelled.
  • CRRZG5105I
    • Creation cancelled.
  • CRRZG5106I
    • Edit attributes cancelled.
  • CRRZG5107I
    • Edit attributes cancelled.
  • CRRZG5108E
    • Unable to rename {0}. The error returned was "{1}"
  • CRRZG5110W
    • This will permanently remove the following file(s) or folder(s) from your system.
  • CRRZG5111I
    • Successfully created "{0}".
  • CRRZG5112E
    • Unable to create {0}. The error returned was "{1}"
  • CRRZG5113W
    • Nothing to paste. Copy a file or directory and try again.
  • CRRZG5114E
    • Unable to download {0}. The error returned was "{1}"
  • CRRZG5115I
    • Successfully updated attributes for "{0}"
  • CRRZG5116E
    • Unable to update attributes for "{0}". The error returned was "{1}"
  • CRRZG5117E
    • Failed to push the new contents of "{0}" to z/OS host using profile "{1}". The error returned was "{2}"
  • CRRZG5118I
    • Upload(s) Successful
  • CRRZG5119E
    • Failed to upload "{0}". The error returned was "{1}"
  • CRRZG5120E
    • Failed to paste "{0}". The error returned was "{1}"
  • CRRZG5121E
    • Unable to delete "{0}". The error returned was "{1}"
  • CRRZG5122I
    • Successfully deleted the following items(s): {0}.
  • CRRZG5123E
    • Failed to open file as text. Re-download file as binary?
  • CRRZG5124E
    • Unable to open "{0}" in an editor. The error returned was "{1}"
  • CRRZG5125E
    • Unable to get files for {0}. The error returned was "{1}"
  • CRRZG5126E
    • Unable to search USS files. The error returned was {0).
  • CRRZG5127W
    • Received command from the z/OS resources table that was unhandled. The requested handler was "{0}" and the command was "{1}"
  • CRRZG5128I
    • IBM Z Open Editor extension has (re)started.
  • CRRZG5129I
    • A VS Code settings change was detected that requires restarting the Z Open Editor extension. All language servers will be stopped now and restarted on demand.
  • CRRZG5130I
    • A VS Code workspace was added or removed which requires restarting the Z Open Editor extension. All language servers will be stopped now and restarted on demand.
  • CRRZG5131I
    • ZCodeFormat: A valid zcodeformat file change was detected that requires restarting the Z Open Editor extension. All language servers will be stopped now and restarted on demand.
  • CRRZG5132I
    • ZCodeFormat: A currently used zcodeformat file was deleted which requires restarting the Z Open Editor extension. All language servers will be stopped now and restarted on demand.
  • CRRZG5133E
    • Error: The zcodeformat file {0} has syntax errors and none of its settings can be used until fixed. Errors found: \n{1}
  • CRRZG5134E
    • Failed to get license key from secure storage. The error returned was "{0}".
  • CRRZG5135E
    • Failed to parse license key from secure storage. The error returned was "{0}"
  • CRRZG5136E
    • Cannot import same activation key twice. Please get an updated key.
  • CRRZG5137E
    • This license is not valid and cannot be added. The error returned was "{0}"
  • CRRZG5138E
    • This license has an empty body.
  • CRRZG5139E
    • This license is either expired or is not compatible with the current version of Z Open Editor.
  • CRRZG5140E
    • Error reading content of the file located at "{0}". The error returned was "{1}".
  • CRRZG5141E
    • This key is invalid and could not be decrypted.
  • CRRZG5142E
    • Could not determine current version of Z Open Editor extension.
  • CRRZG5143E
    • Local activation key does not have expiration data.
  • CRRZG5144E
    • Wazi license in secure storage has invalid format.
  • CRRZG5145E
    • Failed to decrypt the license in secure storage. The error returned was "{0}"
  • CRRZG5146W
    • The decryption key has most likely changed. The invalid activation key will be removed.
  • CRRZG5147I
    • Renewed advanced capabilities activation using profile "{0}". This status will be valid for the next {1} days.
  • CRRZG5148I
    • Advanced capabilities were enabled using RSE API. Please reload Visual Studio Code to start using advanced capabilities.
  • CRRZG5149E
    • Profile "{0}" failed to connect to "{1}" to determine and renew your advanced capabilities activation. Please review your Zowe profile's configuration and try again or contact your RSE API system administrator.
  • CRRZG5150E
    • Duplicate snippets were found while reading the IBM Developer for z/OS snippets file.
  • CRRZG5151E
    • An error occurred while reading the IBM Developer for z/OS snippets. Try exporting and importing a new snippets file.
  • CRRZG5152E
    • An error occurred while writing the snippets to a file. Check that the file has write permission and a valid name.
  • CRRZG5153E
    • An error occurred while parsing the snippets. Check that the snippets have not been modified since export from IBM Developer for z/OS.
  • CRRZG5154E
    • An error occurred while parsing the snippets after conversion to JSON. Check that the snippets have not been modified since export from IBM Developer for z/OS.
  • CRRZG5155E
    • The snippets contained nonstandard JSON after converting from XML. Check that the snippets have not been modified since export from IBM Developer for z/OS.
  • CRRZG5156E
    • An error occurred while converting the snippets from XML to JSON. Check that the snippets have not been modified since export from IBM Developer for z/OS.
  • CRRZG5157E
    • This platform is not supported. Please create an issue on our GitHub repository.
  • CRRZG5158I
    • Name a prefix string for organizing your snippets. This prefix will be placed in front of the name of every snippet imported, which allows you to group snippets by name, for example COBOL SQL.
  • CRRZG5159E
    • An error has occurred loading "{0}" as TextDocument
  • CRRZG5160I
    • ZAPP: A valid ZAPP file change was detected that requires reparsing all open programs.
  • CRRZG5161I
    • ZAPP: Compiler options for {0} were modified. Restarting Z Open Editor.
  • CRRZG5162I
    • ZAPP: An in-use ZAPP file was deleted which requires reparsing all open programs.
  • CRRZG5163E
    • Error: The ZAPP file {0} has syntax errors and none of its settings can be used until fixed. Errors found: \n{1}
  • CRRZG5164I
    • Zowe Explorer was modified for IBM Remote System Explorer API (RSE API) support by IBM Z Open Editor.
  • CRRZG5165W
    • The user or workspace setting "zopeneditor.zowe.defaultRseConversionMappingsFile" contains an invalid path to a RSE API mappings file. It needs to be either an absolute or workspace relative path to a JSON mappings file or a valid ZAPP file with mappings.
  • CRRZG5166W
    • The Zowe Explorer VS Code extension was not found or it failed to activate because of an error. Other reasons could be that you might have disabled it or are running an unsupported version. You will not be able to use Zowe Explorer with the IBM Remote System Explorer API (RSE API). The following error was found: "{0}"
  • CRRZG5167E
    • You have a previous version of IBM User Build installed in this instance of Visual Studio Code. All IBM User Build capabilities were migrated into the IBM Z Open Editor extension with version 1.1.0. Uninstall the IBM User Build extension and restart VS Code with Z Open Editor or it will not function correctly.
  • CRRZG5168E
    • A 64-Bit Java {0} or newer SDK or Runtime could not be found automatically. Verify that Java is installed correctly and the JAVA_HOME variable is set, or manually specify the location using either the java.home or zopeneditor.JAVA_HOME setting in the Visual Studio Code user settings. If you install Java now, you will need to restart VS Code after installing.
  • CRRZG5169W
    • JavaFinder: Something went wrong executing "{0}". Error: {1}
  • CRRZG5170E
    • JavaFinder: Something went wrong executing "{0}". Error: {1}
  • CRRZG5171E
    • JavaFinder: Could not get version for Java at "{0}". Make sure the path of JAVA_HOME does not end with "/bin/java". Error: {1}
  • CRRZG5172E
    • Internal error: Invalid call to UsageReporter.
  • CRRZG5173I
    • No encoding found for file {0}. Assigning default encoding {1}
  • CRRZG5174I
    • No encoding found for file {0}. Assigning default encoding {1}
  • CRRZG5175W
    • Failed to determine attributes with Git command. It is possible the git command is not installed. Z Open Editor will guess the encoding instead. It is recommended to install Git on the local system and setting the default PATH variable so Z Open Editor can provide better results finding the correct encoding.
  • CRRZG5176E
    • Error running Git check-attr command: {0}
  • CRRZG5177I
    • Welcome to IBM User Build. Run User Build from the pop-up menu in an open editor with a COBOL, PL/I, or HLASM program.
  • CRRZG5178I
    • Visit IBM Docs to learn about IBM User Build here: {0}.
  • CRRZG5179I
    • User build cancelled
  • CRRZG5180I
    • Build cancelled
  • CRRZG5181E
    • Error: userbuild.metadata LSP request is not supported in this language: {0}
  • CRRZG5182I
    • Checking user build compile message data set for information.
  • CRRZG5183E
    • Failed to fetch user build compile message data set {0}
  • CRRZG5184E
    • The MVS data set with compile messages is empty.
  • CRRZG5185E
    • Could not parse user build compile message data set results for display {0}
  • CRRZG5186E
    • Failed to delete compile message data set {0}
  • CRRZG5204W
    • Warning: Your workspace or ZAPP file settings for User Build contain a "--dependencyFile ${dependencyFile}" entry, which is not supported for HLASM programs. Stopping User Build. Remove the entry and rerun User Build.
  • CRRZG5205W
    • Warning: Your workspace or ZAPP file settings for User Build do not contain a valid "--dependencyFile ${dependencyFile}" entry. If you use the latest version of dbb-zappbuild, add this setting to your build arguments to improve performance.
  • CRRZG5206I
    • Checking if advanced features are unlocked
  • CRRZG5207I
    • Making sure user build is ran from a local file
  • CRRZG5208W
    • Warning: Stopping User Build. The selected file was detected as a temporary remote file from Zowe Explorer. Run User Build with local files only.
  • CRRZG5209I
    • Checking all settings
  • CRRZG5210I
    • Testing profile for errors
  • CRRZG5211E
    • Profile test failed
  • CRRZG5212I
    • Uploading additional dependencies
  • CRRZG5213I
    • Uploading program source code
  • CRRZG5214I
    • Fetching build file dependencies...
  • CRRZG5215I
    • Request build file metadata
  • CRRZG5216I
    • Getting list of copybooks
  • CRRZG5217I
    • Upload copybooks
  • CRRZG5218I
    • Setting build timestamp cache
  • CRRZG5219I
    • Handling dependency file
  • CRRZG5220E
    • Stopping User Build. {0}
  • CRRZG5221E
    • Stopping User Build. An error has occurred: {0}
  • CRRZG5222I
    • Invoking build script
  • CRRZG5223E
    • Stopping User Build. {0}
  • CRRZG5224E
    • An error has occurred: {0}
  • CRRZG5225I
    • Handling problems view
  • CRRZG5226I
    • Downloading logs
  • CRRZG5228E
    • Something went wrong parsing compilation messages for display in problems view {0}.
  • CRRZG5229I
    • Using .gitattributes file at {0}
  • CRRZG5230E
    • .gitattributes file not found at the root of the project or error reading file. Will use default encoding for file upload.
  • CRRZG5231I
    • Running User Build...
  • CRRZG5232I
    • Identified the local root workspace path as {0}
  • CRRZG5233W
    • Warning: the {0} language server is not running, User Build will continue without determining and uploading include files.
  • CRRZG5234I
    • User setting dbbDefaultZappProfile: {0}
  • CRRZG5235I
    • Will read settings from ZAPP profile called {0} defined in User Settings
  • CRRZG5236I
    • Will read settings from the first DBB profile found in your ZAPP file.
  • CRRZG5238I
    • Checking user settings...
  • CRRZG5239I
    • User settings should be defined in your VS Code Settings under {0}
  • CRRZG5240I
    • The program to build is not managed with Git. Any custom encoding specified in .gitattributes files will be ignored.
  • CRRZG5241E
    • Required settings are not defined. Visit the IBM Docs to learn User Build settings: {0}
  • CRRZG5242E
    • Error: Exiting User Build. Could not connect to z/OS. Ensure that Zowe profiles are valid and can connect to z/OS on your network.
  • CRRZG5243E
    • Required setting is missing
  • CRRZG5244W
    • Optional setting is missing
  • CRRZG5245I
    • Matching files for {0}
  • CRRZG5246I
    • No matched files found
  • CRRZG5247I
    • Uploading additional dependencies matched inside workspace of the build file ...
  • CRRZG5248E
    • Failed to upload directory {0}, returned with error: {1}
  • CRRZG5249E
    • Failed to upload file {0}, returned with error: {1}
  • CRRZG5250I
    • Failed to upload additional dependencies with error: {0}
  • CRRZG5251I
    • Checking if include files were updated since the last build...
  • CRRZG5252I
    • Updating {0}/{1} local include files.
  • CRRZG5253I
    • Found a total of {0} local include files:
  • CRRZG5254E
    • Error: Exiting User Build. Could not connect to z/OS. Ensure that Zowe profiles are valid and can connect to z/OS on your network.
  • CRRZG5255I
    • Generating the local dependencies file for this build in {0}
  • CRRZG5256I
    • Error: Could not write dependency file to disk.
  • CRRZG5257E
    • Could not read setting {0}.{1}. Check whether the setting is typed correctly, for example, no unnecessary commas, white spaces, or closing quotes.
  • CRRZG5258E
    • Could not get workspace URI. Ensure that the workspace is opened correctly in VS Code.
  • CRRZG5259E
    • Could not read {0} attribute from ZAPP DBB profile. Check whether the setting is typed correctly, for example, no unnecessary commas, white spaces, and closing quotes.
  • CRRZG5260E
    • Could not find the "${fullLocalFilePath}" path. Check your setting or ZAPP profile values.
  • CRRZG5261I
    • Uploading file {0} to {1} with encoding {2}
  • CRRZG5262I
    • Uploading file {0} to {1} with default encoding
  • CRRZG5263E
    • Error: Failed to upload the file {0}. Error returned: {1}
  • CRRZG5264I
    • Will download logs matching the following patterns: {0}
  • CRRZG5265I
    • Looking for user build logs in "{0}".
  • CRRZG5266I
    • Total log files found: {0}
  • CRRZG5267I
    • Downloading logs to {0}
  • CRRZG5268I
    • Downloading log file {0}. Binary: {1}
  • CRRZG5269E
    • Error while downloading {0}: {1}
  • CRRZG5270I
    • Successfully finished downloading of {0} log files to {1}.
  • CRRZG5271E
    • Error while getting logs: {0}
  • CRRZG5272I
    • The default Zowe CLI profile specified as {0} in {1} setting. Will try loading the profile.
  • CRRZG5273I
    • Searching for the default Zowe CLI profile...
  • CRRZG5274E
    • Could not find a Zowe CLI profile. Create a Zowe CLI profile.
  • CRRZG5275I
    • Using Zowe profile {0}
  • CRRZG5276I
    • Checking if RSE API profile {0} can connect:
  • CRRZG5277I
    • Could not find a Zowe CLI profile. Create a Zowe CLI profile.
  • CRRZG5278I
    • Connected successfully.
  • CRRZG5279E
    • Could not find the Zowe SSH profile. Create a Zowe SSH profile.
  • CRRZG5280E
    • Could not find the Zowe SSH profile username or password.
  • CRRZG5281I
    • Using ssh profile {0}
  • CRRZG5282E
    • Could not create SSH session. Ensure you have a valid zowe SSH profile.
  • CRRZG5283I
    • Executing SSH command: \n{0}
  • CRRZG5284E
    • Error: Something went wrong executing SSH command {0}
  • CRRZG5285E
    • Error: Something went wrong executing SSH command {0}
  • CRRZG5286I
    • Checking if SSH profile {0} can connect:
  • CRRZG5287I
    • Connected successfully.
  • CRRZG5288I
    • Executing UNIX command \n{0} at path \n{1}
  • CRRZG5289I
    • Executing UNIX command \n{0} at path \n{1}
  • CRRZG5290I
    • Success! A valid activation key was imported. Please reload Visual Studio Code to start using advanced capabilities.
  • CRRZG5291E
    • Error: The sequence number command failed to execute.
  • CRRZG5292E
    • Error: The sequence number removal command failed to execute.
  • CRRZG5293I
    • Updating the sequence numbers...
  • CRRZG5294I
    • Removing the sequence numbers...
  • CRRZG5295E
    • Error: The LSP launcher was not found, which means this build of IBM Z Open Editor is broken. Try reinstalling the extension.
  • CRRZG5296E
    • Error: A valid LSP configuration was not found for platform {0}, which means this platform may not be supported. Try reinstalling the extension.
  • CRRZG5297E
    • COBOL source could not be expanded. Check the Z Open Editor or COBOL Language Server log files for more details.
  • CRRZG5298E
    • Z Open Editor cannot generate a ZAPP file as you have not opened/created a VS Code workspace yet.
  • CRRZG5299I
    • Note that this default file will search all your local folders in all your open VS Code workspaces and can be highly inefficient. Modify the "locations" entries to be as specific as possible. Add a new entry of type "MVS" to specify remote locations. See the user documentation for more details: https://ibm.github.io/zopeneditor-about/Docs/setting_propertygroup.html
  • CRRZG5300I
    • IBM Z Open Editor generated a ZAPP file for you in "{0}" that searches in all your folders for include files as you do not have such a file yet. Edit the file to point to more specific folder locations for efficiency. Review the documentation about ZAPP files.
  • CRRZG5301W
    • Z Open Editor found more that 10 ZAPP files. Are you sure you want to open them all?
  • CRRZG5302W
    • You opened a file with include files, but do not have a Property Group defined that specifies where to find them. Review the documentation for Zapp files.
  • CRRZG5303I
    • You opened a file with include files, but do not have a ZAPP file with Property Groups defined that specify where to find them. We started creating one for you in "{0}". Once it is available the language server will use it for searching again in all your folders. Edit the file to point to more specific folders for efficiency. Review the documentation about Zapp files.
  • CRRZG5304W
    • You opened a file that has been had a preprocessor used on it, but do not have a any preprocessor profiles defined that specifies where to find the output. Review the documentation for Zapp files.
  • CRRZG5305W
    • The macro file "{0}" could not be found in or retrieved from data set(s) "{1}". Check the log for http errors and ensure that you have a valid Zowe Explorer connection defined that can be used to retrieve them. You can disable this function with the user setting "zopeneditor.hlasm.enableResolvingMacros".
  • CRRZG5306I
    • The {0} language server requested the include file "{1}", which was found and available as file "{2}".
  • CRRZG5307W
    • The {0} language server requested the include file "{1}", which was not found. {2} was set to {3}. Check your Zowe CLI profile and property group settings and if you have not already done so, switch to the "DEBUG" log level for more information.
  • CRRZG5308E
    • Data set member search request failed or retrieved invalid data set content because of a connectivity issue. Please check your connection details.
  • CRRZG5309E
    • Could not determine the active editor. Try closing the Output panel and running the command again.
  • CRRZG5310E
    • Could not automatically get the active VS Code workspace folder for this file. Ensure that you are running the command from a file that belongs to an active workspace opened in your editor locally.
  • CRRZG5311W
    • The file you are trying to save exceeds the maximum line length on line(s) {0}. Saving the file will truncate all text after column {1}.
  • CRRZG5312E
    • Error: Unable to register Z Open Editor with Zowe Explorer. Error returned: Zowe Explorer VS Code Extension "{0}" is not compatible. Update Zowe Explorer to 3.0.0 or higher.
  • CRRZG5313W
    • Warning: Unable to initialize secure credentials plugin for Z Open Editor. Check that you configured the "Zowe Security: Credential Key" user preferences with the value "Zowe-Plugin". Error returned: "{0}"
  • CRRZG5314W
    • Warning: IBM Z Open Editor was not able to register the RSE and SSH API. Error received from the API: "{0}"
  • CRRZG5315E
    • You specified an MVS Property Group in your Settings, but no valid Zowe Profile was found to use for loading files from MVS. Create a Zowe profile and try again.
  • CRRZG5316E
    • Temporary folder could not be deleted. "{0}"
  • CRRZG5317E
    • Found {0} setting in Preference file, but the value {1} refers to a non-existing path.
  • CRRZG5318I
    • Operation cancelled.
  • CRRZG5319E
    • There was a problem accessing the Zowe Explorer API with version {0} or newer. The following error was reported: {1}
  • CRRZG5320E
    • There was a problem accessing the Zowe Explorer API with version {0}. Verify that your Zowe Explorer installation is that version or newer.
  • CRRZG5321E
    • Unable to identify. Check if Zowe Explorer is installed and configured correctly.
  • CRRZG5322E
    • No SSH profile found
  • CRRZG5323W
    • IBM Z Open Editor was not able to find a valid Zowe CLI profile to use. Review the following error message and try to fix the problem by checking if valid entries were defined for zopeneditor.zowe in your VS Code user settings: {0}
  • CRRZG5324W
    • Issue getting IBM Open Editor settings for Zowe profiles.
  • CRRZG5325E
    • The authorization token for your Zowe profile "{0}" has expired. Please use the "login" operation from the Zowe Explorer context menu to renew your authorization.
  • CRRZG5326E
    • The property "{0}" for profile {1} needs to be updated to continue.
  • CRRZG5327W
    • No profile found, operation cancelled.
  • CRRZG5328W
    • Issue creating session, operation cancelled.
  • CRRZG5329I
    • Profile {0}'s password has been updated.
  • CRRZG5330E
    • MVS connection check failed for profile "{0}" with\nHTTP Status 401 - Unauthorized\nWould you like to update the credentials?
  • CRRZG5331I
    • Save entered credentials for future use with profile "{0}"?\nSaving credentials will update the profile's local information file.
  • CRRZG5332E
    • Stopping remote file resolving due to invalid credentials for the Zowe CLI profile. To resume remote file resolving for {0} files, use the "IBM Z Open Editor: Reload Zowe Profiles" command palette option or restart VS Code.
  • CRRZG5333E
    • Unable to open search results for "{0}". The error returned was "{1}"
  • CRRZG5334E
    • Unable to open search result for "{0}". The error returned was "{1}"
  • CRRZG5335I
    • Did not find property "additionalDependencies" in ZAPP profile. Skipping upload.
  • CRRZG5336I
    • Opened "{0}" with encoding "{1}". This encoding was derived from your mappings file.
  • CRRZG5337I
    • Opened "{0}" with encoding "{1}". This encoding was derived from your Zowe profile "{2}".
  • CRRZG5338I
    • Opened "{0}" with encoding "{1}". This matched to "{2}" in your "zopeneditor.encodings.filePatterns" setting.
  • CRRZG5339I
    • You can configure the maximum line length in settings.
  • CRRZG5340I
    • This warning may be inaccurate if you are working with a double-byte character set.\nYou can configure the maximum line length in settings.
  • CRRZG5341I
    • Successfully pasted {0} to "{1}".
  • CRRZG5342E
    • Z Open Editor tried generating a default ZAPP file in your first workspace, but failed as a file with that name already exist. Check if the log reports problems reading or parsing your ZAPP file because of syntax or other errors.
Last Updated:
Contributors: PETER HAUMER