|
|
|
|
|
Each VisualAge message has a message number and message text to give you additional information about the message.
The format of the message number is as follows:
PPP.XXX.NNNN.y
Only those messages originating from the Composition Editor, Class Editor, and Part Interface Editor are listed here.
Messages
Message
The class <class_name> was not found.
Explanation
The implementation file (.vbf) that contains this class must be loaded to complete the operation.
Action
Load the .vbf file and retry the operation.
Message
The class <class_name> cannot be created because a class with the same name is already loaded in VisualAge.
Action
Enter a unique class name or unload the file containing the duplicate class name.
Message
<class_name1> is not a valid base class for <class_name2>.
Explanation
You were trying to create a new part, and you specified an inappropriate base class.
Action
Specify a different base class for your new part.
Message
The part <part_name> is not loaded into Visual Builder.
Explanation
The part was not found.
Action
Load the file (.vbe or .vbf) that holds this part.
Message
An error occurred in opening <file_name> (<error_string>).
Action
Try the following in order:
Message
An error occurred in opening <file_name>. The file was not created.
Action
Try the following in order:
Message
The internal cache of Visual Builder is full.
Action
Save your files; then, close and restart Visual Builder.
Message
An error occurred in reading from <file_name> (<error_string>).
Action
Try the following in order:
Message
An error occurred in writing to <file_name> (<error_string>).
Action
Try the following in order:
Message
<file_name> is not a valid .vbb file.
Explanation
The file is not in the format that VisualAge expects, either because the file is not a binary implementation file (.vbb) or because it has been damaged.
Action
Contact IBM Service.
Message
<file_name> was not loaded because a file with the same name is already loaded.
Action
If a file with the same name is loaded from a different directory, unload the previously loaded file and try the operation again. Otherwise, no action is required; the file you requested is already loaded.
Message
The part <part_name1> was not loaded because it contains the part <part_name2>, which is already loaded.
Explanation
The part <part_name2> has already been loaded from a different implementation file (.vbf).
Action
Unload the file that contains the duplicate part, or delete the duplicate part.
Message
VisualAge did not save <file_name> because it is a read-only file.
Action
Try the following in order:
If you are trying to save a part that was shipped with VisualAge, be aware that changes of this kind are not supported.
Message
VisualAge did not save the following files: <file names>. Select Help for corrective action.
Action
Check for these problems:
If you are trying to save parts that were shipped with VisualAge, be aware that changes of this kind are not supported.
Message
The file <file_name> is in use. The operation was not completed.
Action
Check your open applications and close any that might be using this file. This includes other Composition Editor sessions that have this file loaded.
Message
<DLL_name> was not initialized. An error occurred in calling the entry point <label>.
Explanation
VisualAge could not start because it could not find the cppvib40.dll file.
Action
Be sure that the subdirectory containing cppvib40.dll is on your LIBPATH statement in your config.sys file.
Message
<DLL_name> was not reset. An error occurred in calling the entry point <label>.
Explanation
VisualAge could not start because it could not find the specified DLL.
Action
Be sure that the subdirectory containing this DLL is on your LIBPATH statement in your config.sys file.
Message
This DLL is not valid. Check the LIBPATH statement in your config.sys file.
Explanation
VisualAge could not find the specified DLL.
Action
Be sure that the subdirectory containing this DLL is on your LIBPATH statement in your config.sys file.
Message
To delete this row, the following parts must be deleted: <part_names>. Is it okay to delete them?
Explanation
VisualAge is about to delete the specified row.
Action
To confirm that you want to delete the specified row, select OK. The row and the specified parts are deleted.
If you do not want to delete the row, select Cancel.
Message
To delete this column, the following parts must be deleted: <part_names>. Is it okay to delete them?
Explanation
VisualAge is about to delete the specified column.
Action
To confirm that you want to delete the specified column, select OK. The column and the specified parts are deleted.
If you do not want to delete the column, select Cancel.
Message
The constructor for part <part_name> is not valid.
Explanation
The syntax of the constructor for the specified part is not valid, or VisualAge could not find the constructor in the DLL.
Action
Use the Part Interface Editor to correct the syntax. Then try again.
Message
The constructor parameter <parameter_name> for part <part_name> is not valid.
Explanation
One of the following problems exists:
Action
Use the Part Interface Editor to correct the syntax. Then try again.
Message
The constructor for part <part_name> failed.
Explanation
The constructor failed, or it returned a part that is not valid. Combinations that are not valid for the constructor can cause failures.
Action
Be sure the constructor settings contain a valid combination for the part. Then try again.
Message
The class <class_name> is not defined in the files that are loaded.
Explanation
VisualAge could not find the class definition for the specified class. The class definition is missing from the files that VisualAge loaded.
Action
Close the Composition Editor. Use the Class Editor to create the class definition for this class, or reload the file containing the class. Then try again.
Message
VisualAge was not able to load the entry point <label> from DLL <DLL_name>.
Explanation
VisualAge could not find the specified DLL or this particular entry point in the specified DLL.
Action
Be sure that the subdirectory containing this DLL is on your LIBPATH statement in your config.sys file and that the DLL contains the specified entry point.
Message
The cell (<row_number>, <column_number>) is already occupied.
Explanation
VisualAge has already placed (in the upper-left corner) a part in the requested cell. Only one part can be placed in that cell.
Action
In the property sheet for the part, do one of the following:
Message
An error occurred in creating the new class <class_name>.
Explanation
VisualAge could not create the specified class because of a file error.
Message
The class <class_name> already exists. Choose another name.
Action
Rename and save the class.
Message
<class_name> is not a valid class name. Choose another name.
Action
Rename and save the class.
Message
An error occurred in saving the palette information: <error_string>.
Explanation
VisualAge could not add your part or category to the palette as a result of this error.
Action
The action you should take depends on the error stated in the message. Correct the error based on the specific text.
Message
An error occurred in loading the palette information: <error_string>. The default palette will be used.
Explanation
VisualAge could not use the file that contains the information about the parts palette. This file probably has one of the following problems:
Action
Check the file's access permissions. If access does not seem to be causing the problem, delete the palette file and then try again to load the part. When no palette file is present, VisualAge loads the palette definition shipped by IBM.
Message
The loaded object is not a palette. The default palette will be used.
Explanation
VisualAge could not load your parts palette because the data in the file you specified did not contain palette information.
Action
Be sure that the file you specified for your parts palette contains palette information and that the file name is correct. Then try again.
Message
The part <part_name> cannot be edited.
Explanation
VisualAge could not load your part into the Composition Editor. Either the data in the file you specified did not contain part information, or the part cannot be edited. This can happen with certain system parts and typedefs.
Action
Be sure that the file you specified for your part contains part information and that the file name is correct. Then try again.
Message
<class_name> has been marked by the supplier as a class that cannot be used in a variable.
Action
Specify a different class for the type of the variable.
Message
The only valid input for this field is a code expression preceded by a number sign (#).
Explanation
The property setting that you entered could not be used in string form.
Action
Starting with a number sign (#), enter a C++ expression.
Using Code Strings in
Part Properties
Message
The attribute type is missing.
Explanation
The Attribute type field in the Part Interface Editor is blank.
Action
Enter a type in the Attribute type field in the Part Interface Editor. Then try again.
Message
The member function signature is missing or not valid.
Explanation
Either the member function does not exist, or the syntax for it is not valid.
Action
Be sure that the member function exists and that the syntax is correct.
To check this, use the Part Interface Editor, or select Browse Part Features from the pop-up menu for the part in the Composition Editor.
Message
The event identifier is missing.
Explanation
The event identifier does not exist.
Action
In the Part Interface Editor, enter an event identifier in the Event identification field on the Attribute or Event page. Then try again. To do this, use the Part Interface Editor or select Browse Part Features from the pop-up menu for the part.
Message
<feature_name> is already in the list of preferred features.
Explanation
The feature you tried to add already appears in the list of preferred features on the Preferred page of the Part Interface Editor.
Action
Select a different feature.
Message
An error occurred in opening file <file_name>: <part_name>.
Explanation
VisualAge could not open the specified file to generate the feature source code. This file might not exist. If it does not exist, it will be created.
Action
Be sure that you have write access to the directory and that you have enough space on the disk. Then try again.
Message
The feature source code generation is complete. Code was appended to the following files: <file_names>
Action
Select OK to continue.
Message
Do you want to remove all features from the list of preferred features?
Explanation
You indicated that you want to remove all features from the list of preferred features on the Preferred page of the Part Interface Editor.
Action
Review the features that are to be removed. Then select OK to confirm.
If you do not want to remove them all, select Cancel.
Message
Do you want to remove <feature> from the list of preferred features?
Explanation
You indicated that you want to remove the specified feature from the list of preferred features on the Preferred page of the Part Interface Editor.
Action
Select OK to confirm. If you do not want to remove it, select Cancel.
Message
The set member function must have at least one input parameter. The part interface was not changed.
Explanation
You must specify at least one input parameter in the attribute's set member function. If you specify more than one parameter, you must also supply default values for all parameters except the first one.
Action
Specify the set member function again for this attribute, and select the Add or Update push button, as appropriate.
Message
The parameter <parameter_name> is not valid.
Explanation
VisualAge does not allow you to use parameter names that conflict with reserved feature names, such as actionResult and exceptionOccurred.
Action
Change the name of the parameter.
Message
The base class that you specified is not valid.
Explanation
One of the following occurred:
Action
Make sure that both of the following are true:
Message
The access type of the base class is not valid.
Action
Change the access type of the base class to public, protected, or private.
Message
An expression lacks the opening parenthesis.
Explanation
You omitted the opening parenthesis in the declaration of a member function. This could occur in the following places:
Action
Insert the missing parenthesis.
Message
A function name was not found.
Explanation
The name of a member function that you entered is missing. This could occur in the following places:
Action
Insert the missing member function name.
Message
A syntax error occurred in the function declaration.
Explanation
You entered a member function declaration that contains a C++ syntax error. This could occur in the following places:
Action
Correct the syntax error.
Message
The file <file_name> already exists. Do you want to overwrite it?
Explanation
You are about to perform an action that will overwrite an existing part file.
Action
Do one of the following:
Message
Parameter <parameter_name> does not include a type and a name. Both are required.
Explanation
You entered a function signature with at least one input parameter in prototype form (parameter type but no name).
Action
For each parameter specified, be sure to include both a type and a name.
Message
File selection failed. Too many files were selected. Please try again with fewer files.
Explanation
In Windows, file selection dialogs use a single buffer to store the file names you select. This buffer has filled up.
Action
Select fewer files. For files in 8.3 format, the limit is approximately 20 files.
Message
EXPORT Connection <connection_number>: An attribute-attribute connection to actionResult has been changed to an event-action connection.
Explanation
You migrated a part created using an earlier release of VisualAge, and VisualAge updated a connection in the part to meet new specifications. The original connection linked two attributes.
The actionResult attribute has been changed to an event; the return value itself is now passed as event data. The change enables you to connect to a wider variety of return types than in past releases of the product. Prior to this change, you could connect to only those return types that had a default constructor, and the use of references (ClassName&) in the return type was not enabled.
In this case, VisualAge redrew the connection from the actionResult event to the target attribute's set member function.
Action
No immediate action is required. However, consider reviewing your actionResult connections to make sure they still provide the appropriate behavior in the finished application.
Message
EXPORT Connection <connection_number>: **USER ACTION REQUIRED**--actionResult is connected to another connection. This is no longer valid, and it cannot be updated automatically. Please see the release documentation for more information.
Explanation
You migrated a part created using an earlier release of VisualAge, and VisualAge updated a connection in the part to meet new specifications. The original connection linked the actionResult attribute of one connection to a parameter on another connection.
The actionResult attribute has been changed to an event; the return value itself is now passed as event data. The change enables you to connect to a wider variety of return types than in past releases of the product. Prior to this change, you could connect to only those return types that had a default constructor, and the use of references (ClassName&) in the return type was not enabled.
In this case, VisualAge redrew the connection using a newly added Variable part as an intermediary. The new variable was given the name actionResult of Conn<connection_number>. VisualAge then drew the following connections:
Action
At the time VisualAge added the Variable part, information about the return type of actionResult was not available, so the Variable part could not be preset to the correct type. You must open the composite and manually set the variable's type. Otherwise, VisualAge cannot generate code for the composite.
Message
You cannot specify an inherited feature (<feature_name>) as preferred. This preference was not migrated.
Explanation
Previous versions of VisualAge enabled you to specify inherited features as preferred. This is no longer the case.
Action
No action is required. However, you might want to review the list of preferred features for this part.
Message
EXPORT PartLayout: Subpart <part_name> - Class <class_name> was not migrated because it is not valid.
Action
This message indicates an internal error. Contact IBM Service.
Message
EXPORT PartLayout: Subpart <part_name> - Attribute <attribute_name> was not migrated. It was reset in the migrated part.
Explanation
VisualAge found the specified attribute setting during migration. The setting was not carried over into the migrated part.VisualAge will set this attribute independently.
Action
No action is required, but you might want to open the migrated part to see how it was set.
Message
For performance, migration has turned on the IContainerControl::noSharedObjects style in subpart <part_name> (IVBContainerControl). If they really should be shared, reset the style flag.
Action
If shared objects are not required in the container part, no action is required. Otherwise, reset the noSharedObjects style using the part's property sheet.
Property Sheets
Editing Part Properties
IVBContainerControl
Message
Promoted Ready on subpart <part_name> removed. They are no longer valid.
Explanation
The VisualAge migration utility detected that the ready event was promoted from the specified part. This promotion is no longer supported, so VisualAge deleted it. The ready event is now available only for use within a part.
Action
No action is required.
Message
Connection to Ready from subpart <part_name> removed. They are no longer valid.
Explanation
The VisualAge migration utility detected a connection from the ready event of an embedded part to a target elsewhere in the composite. This connection is no longer supported, so VisualAge deleted it. The ready event is now available only for use within a part.
Action
No action is required.
Message
Visual Builder cannot write to <file_name>. If this file already exists, it might be in use. Otherwise, ensure that you have write access to this file or directory.
Explanation
You were trying to create a new part. As part of this process, VisualAge checks for write access to the implementation file (.vbf) you specified for the new part. For some reason, you do not have write access to this file.
Action
Try the following in order:
Message
An error occurred in opening the file <file_name>. Ensure that the file exists.
Explanation
You tried to open the IDE or create a new part using a wizard. VisualAge could not load the specified part implementation file (.vbf).
Action
Make sure that the file exists in the stated directory.
Message
The end of the file was reached in the middle of a part definition.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The keyword <keyword_in_error> is not valid.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The class contraints <constraint_names> are not valid. They were ignored.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
<part_name1> already exists as <part_name2>. Ensure that all part, type definition, and enumeration names are unique.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
<part_name> already exists in the file <file_name>. It was not loaded into <file_name>.
Action
If you do not want to replace the part, correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
A keyword was specified with no parameters. The line was ignored.
Action
No action is required, but you might want to correct the problem and reload the file. For more information, see Part Information Statement Descriptions.
Message
The feature flag <flag_name> is not known.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The set member function of a VBAttribute statement must contain at least one parameter. Any additional parameters must contain default values.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The composer view type that was specified is not known.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The part type that was specified is not known.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The composer class that was specified is not valid.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The generator class that was specified is not valid.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The part information export failed: <error_string>
Explanation
VisualAge tried to export a part for you. For some reason, VisualAge could not open a new file for the part.
Action
Correct the problem indicated by the error string. If you cannot correct the problem, contact IBM Service.
Message
The VBAttributeSetting tag for a ConnValue tag was not found.
Explanation
You were trying to load a part that uses another class as an attribute type, and information was missing from the implementation file.
VisualAge records implementation information about the part's use of the type as well as the implementation of the type itself. Information about the part's use of the class (a VBAttributeSetting statement) must occur before the VBConnValue statement in the implementation file.
Action
Add or move the VBAttributeSetting statement so that it occurs before the corresponding VBConnValue statement. Then try again to load the file. For more information about VBAttributeSetting and VBConnValue, see Part Information Statement Descriptions
Message
The VBInitializationStream tag is missing.
Explanation
VisualAge could not find the VBInitializationStream statement in apart information file (.vbe or .vbf).
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The version in the VBInitializationStream tag is missing.
Explanation
VisualAge could not find version notation in the VBInitializationStream statement in a part information file (.vbe or .vbf).
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The version in the VBInitializationStream tag is not valid.
Explanation
VisualAge found version notation in the VBInitializationStream statement in a part information file (.vbe or .vbf), but the notation is not valid. This is probably because the part was saved using a previous release of VisualAge.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The name of a tearoff attribute is missing.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The VBAttributeSetting tag for a PartValue tag was not found.
Explanation
You were trying to load a part that uses another class as an attribute type, and information was missing from the implementation file.
VisualAge records implementation information about the part's use of the type as well as the implementation of the type itself. Information about the part's use of the class (a VBAttributeSetting statement) must occur before the VBPartValue statement in the implementation file.
Action
Add or move the VBAttributeSetting statement so that it occurs before the corresponding VBPartValue statement. Then try again to load the file. For more information about VBAttributeSetting and VBPartValue, see Part Information Statement Descriptions
Explanation
Part implementation information was not valid or missing. VisualAge issued a CPP.IMP error message numbered somewhere between 1010 and 1019, between 2000 and 2163, or between 2170 and 2223.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
Part family must be interface, vb, or dax.
Explanation
VBBeginPartInfo statements in your part information file (.vbe or .vbf) must include one of these values. This value determines edit behavior for the part later on.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
Pointer types are not allowed in the type field of an AttributePart tag.
Action
Correct the part information syntax; then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
<part_information_statement> is not valid when the part family is interface. It has been ignored.
Action
No action is required, but you might want to correct the part information syntax and then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The keyword <keyword_name> is not known. It was ignored.
Action
No action is required, but you might want to correct the part information syntax and then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The keyword <keyword_name> is obsolete. It was ignored.
Action
No action is required, but you might want to correct the part information syntax and then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
The feature flags <flag_list> were ignored.
Action
No action is required, but you might want to correct the part information syntax and then try again to load the file. For more information, see Part Information Statement Descriptions.
Message
An error occurred when loading information about options that you changed in the Visual Builder window. The default option selections will be used.
Explanation
When you change the options that are selected in the Options menu, VisualAge saves those changes in a file named vbopts.dat in your working directory. An error occurred when VisualAge tried to open this file. The options will be reset to the default selections when you select the Cancel push button.
Action
If the error persists, erase the vbopts.dat file. VisualAge will create a new vbopts.dat file in your working directory the next time you change option selections.
Message
An error occurred when loading information about options that you changed in the Visual Builder window: <error_string>. The default option selections will be used.
Explanation
When you change the options that are selected in the Options menu, VisualAge saves those changes in a file named vbopts.dat in your working directory. An error occurred when VisualAge tried to open this file. The options will be reset to the default selections when you select the OK push button.
Action
If the error persists, erase the vbopts.dat file. VisualAge will create a new vbopts.dat file in your working directory the next time you change option selections.
Message
An error occurred when saving information about options that you changed in the Visual Builder window: <error_string>.
Explanation
When you change the options that are selected in the Options menu, VisualAge saves those changes in a file named vbopts.dat in your working directory. An error occurred when VisualAge tried to write information about the changed options to this file.
Action
Make sure that your working directory has space available.
Message
<file_name1> is an invalid file name because <file_name2> is already loaded from another path.
Explanation
You tried to create an implementation file (.vbf) that has the same name as a .vbf file that you loaded from another path.
Action
Do one of the following:
During standalone operation, you can see the full path of the loaded .vbf files by selecting Options and then Show full file names.
Message
The file name was not specified.
Explanation
You tried to move a part into an implementation file (.vbf) without specifying the file name.
Action
Enter the name of the .vbf file that you want to move the part to.
Message
<file_name> is already loaded. It was not loaded again.
Explanation
You tried to load an implementation file (.vbf) that was already loaded.
Action
No action is necessary.
Message
<file_name1> cannot be loaded because <file_name2> is already loaded from another path.
Explanation
You tried to load an implementation file (.vbf) that has the same name as one that you loaded from another path.
Action
Unload the .vbf file that is already loaded and then load the new .vbf file.
You can see the full path of the loaded .vbf files by selecting Options and then Show full file names.
Message
This operation was canceled because file replacement was not allowed.
Explanation
You canceled an operation that would have caused VisualAge to replace an implementation file (.vbf) if you had continued. For example, you would receive this message if you migrated data that would have replaced an existing file, but you did not allow VisualAge to replace the existing file.
Action
No action is required.
Message
<file_name> is not loaded and is about to be replaced. Is it okay to replace this file?
Explanation
You are saving a new part or migrating data into an implementation file (.vbf). The new .vbf file has the same name as one that already exists in your working directory. If you continue, VisualAge will replace the existing .vbf file with the new one.
Action
Do one of the following:
Message
Do you want to exit Visual Builder?
Explanation
You did one of the following:
Action
Do one of the following:
Message
At least one Visual Builder editor window is open. Select Yes to close it and exit.
Explanation
You did one of the following with one or more VisualAge editor windows open:
Action
Do one of the following:
Message
The exit operation was canceled.
Explanation
You selected No when VisualAge displayed a message asking if you wanted to exit.
Action
No action is required. To exit VisualAge, do one of the following:
When VisualAge displays a message asking if you really want to exit, select Yes.
Message
Visual Builder was not able to open <file_name>: <error_text>.
Action
The action you must take depends on the error stated in the message. Correct the error based on the specific text.
Message
Because of incompatible selections, this operation was canceled.
Explanation
The response you gave in one window contradicts the response you gave in another window.
Action
No action is required.
Message
The class <class_name> was not found.
Explanation
You specified a class name that VisualAge could not find in any of the loaded implementation files (.vbf).
Action
Load the .vbf file that contains the class.
Message
Visual Builder was not able to open an editor window for <part_name>: <file_name>.
Explanation
You tried to open a part, but your system did not have enough free resources to let VisualAge display the editor.
Action
Release system resources that are currently being used by closing applications that you are not using. Then, try again to open the part.
Message
VisualAge was not able to change the working directory to <disk_name>: <working_directory>.
Explanation
You attempted to change the working directory but specified a path that is not valid.
Action
Do one of the following:
Message
<part_name> is already on the parts palette in the category that you specified. It was not added again.
Explanation
You tried to add a part to the parts palette, but a part with that name is already in the category that you tried to add the part to.
Action
To add the part, do one of the following:
Message
Base Parts cannot be unloaded. It has been removed from the unload list.
Explanation
You tried to unload the base implementation file, which VisualAge does not allow you to do. This file must always be loaded.
Action
No action is required.
Message
<part_name> has been marked by the supplier as a non-editable class.
Explanation
Most classes in this category are reserved for use by the supplier of the part.
Action
Specify a different class as the base for your new part.
Message
<part_name> has been marked by the supplier as a class that cannot be added to the palette.
Explanation
Most classes in this category are reserved for use by the supplier of the part.
Action
Specify a different class as the base for your new part.
Message
The file <file_name> is in a file format that is totally incompatible with this version of Visual Builder.
Explanation
This implementation file (.vbf) is not in the expected file format and cannot be converted.
Action
No action is possible using VisualAge.
Message
The file <file_name> is in an unknown file format. Do you want to continue and try to load it?
Explanation
This part file is not in the expected file format but might be convertible.
Action
To keep a copy of the file in its original format, cancel this request, make a backup copy of the file, and try again.
To attempt the format conversion and load the file, select Yes.
To cancel the request to load the file, select No.
Message
Attention: If you continue loading <file_name>, it will be converted to a new file format. You will no longer be able to use it with the version of Visual Builder that created it. Do you want to continue anyway?
Explanation
This part file is not in the expected file format but is convertible. However, after VisualAge converts the file, you will not be able to use the file with the version of VisualAge that originally created it.
Action
If you want to keep a copy of the file in its original format, cancel this request, make a backup copy of the file, and try again.
To proceed with the format conversion and load the file, select Yes.
To cancel the request to load the file, select No.
Message
This save operation failed.
Explanation
VisualAge was unable to save a part in the specified implementation file (.vbf) because of one of the following reasons:
Action
Check for the conditions listed above. Once any have been corrected, try the operation again.
Message
This part was copied successfully.
Action
No action is required.
Message
This part was renamed successfully.
Action
No action is required.
Message
The new name is not a valid class name. Choose another name.
Explanation
You tried to copy or rename a class to a name that is not supported in the C++ language.
Action
Check the new name for the following:
Message
The new name is not a valid class name. Choose another name.
Explanation
You specified a class name that is not supported in this programming language.
Action
Check the class name for the following:
Message
<part_name> already exists. Choose another name.
Explanation
You cannot enter the name of a part that is already loaded.
Action
Do one of the following:
Message
VisualAge cannot write to file <file_name>.
Explanation
VisualAge was not able to write information to the specified implementation file (.vbf) because of one of the following reasons:
Action
Check for the conditions listed above. Once any have been corrected, try the operation again.
Message
VisualAge cannot write to file <file_name>. Nothing was deleted.
Explanation
VisualAge was not able to write information to the specified implementation file (.vbf) because of one of the following reasons. The file was not changed.
Action
Check for the conditions listed above. Once any have been corrected, try the operation again.
Message
The base class <class_name> must be loaded before the new part can be created.
Action
Load the implementation file (.vbf) that contains the base class you want to use.
Message
The class IWindow is not loaded.
Explanation
The base implementation file must be loaded to create or open a visual part. All visual parts inherit from IWindow.
Action
Contact IBM Service.
Message
<class_name1> must inherit from <class_name2>.
Explanation
You tried to create a part from an inappropriate base class.
Action
Do one of the following:
About Implementing
Nonvisual Parts
About Implementing
Custom Visual Parts
IVBMain
Message
<class_name> has been marked by the supplier as a class that cannot be used as a base class.
Explanation
Most classes in this category are reserved for use by the supplier of the part.
Action
Specify a different class as the base for your new part.
Message
The base class must also be a <part_type>.
Explanation
When opening a new part, you specified a part type that was different from that of the base class. Both base and derived classes must be of the same type.
Valid part types are visual, nonvisual, and class interface.
Action
Message
This type cannot be constructed using the 'new' keyword.
Action
This message indicates an internal error. Contact IBM Service.
