This section contains the following topics:
Messages Generated by CA IDMS Dictionary Migrator
Using CA IDMS Dictionary Migrator Reports
This section lists all messages generated by CA IDMS Dictionary Migrator. Included are the codes for messages, reasons for their occurrences, and suggestions for appropriate remedial actions.
CA IDMS Dictionary Migrator produces messages that state that a migrated entity is in use by other entities that are not being migrated. If this is the case, CA IDMS Dictionary Migrator produces a message (VALD219) that lists the related entity. CA IDMS Dictionary Migrator also produces syntax that saves the current definition of the entity from the target dictionary. That definition is readded to the dictionary as part of the upload process after the migrated entity is updated. This updating is called forced regeneration.
Although this process does not allow the migrated entity to be updated, compatibility of the migrated entity and related entity is not assured. You must verify that the migrated structure is compatible with the entity in the target dictionary.
Another situation is a migrated entity that is related to another entity in the extract set, but the related entity is not being migrated because of selection criteria (DATE, DOMAIN, or CHANGEONLY). This results in a VALD219 message.
The message indicates that the relationship area exists. It does not describe exactly what the relationship is, or whether the migrated entity is compatible with the target dictionary entity. You should verify the compatibility, or change the migration strategy to where the relationship is not an issue.
After completing CA IDMS Dictionary Migrator upload, or a combined migrator/upload step, review the output. What is migrated has an effect on the target dictionary.
The following messages should be investigated:
All CA IDMS Dictionary Migrator messages are preceded by a unique eight-character code. The message code is in xxxxnnns format, where xxxx is the ID of the module issuing the message, nnn is the message number for the message within the module, and s is the severity code for the message. The severity code is either I, W, E, F, or C. This chapter lists for each message the code, the text, and an explanation.
Some messages can have their severity altered by the user. The severity shown here is for the unaltered product.
Different conditions cause varying degrees of impact. Different sites view the impact with different degrees of warning. Each site should determine what should be investigated.
When an entity that already exists in the target dictionary is migrated, the following conditions arise with regard to other entities in the target dictionary:
Conditions 1 and 2 do not cause any repercussions on the other entities because they are not related, or because they are also being migrated in the existing target entity and are being updated with the source definition.
It is condition three where one or more of the problems can arise:
Messages are printed on four CA IDMS Dictionary Migrator reports in the sequence in which they are generated.
The Parameter Verification Report contains parameter-related messages in a two-column format. The left column contains the message code and text; the right column shows user input. Part of the information in the right column may be underscored by asterisks (*****) to show the precise location of the error. Information may also be underscored by a series of Xs (XXXXX) to indicate portions of the parameter that were not checked because of a previous error.
Processing messages are also listed on the following reports:
These reports list messages in the right column. Entity names, types, and versions appear to the left of many of the messages.
For more information and samples of CA IDMS Dictionary Migrator reports, see the chapter "Reports".
Reason:
The module could not be called because of an internal problem.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The module cannot be located in the available load or core-image libraries.
Action:
Locate the load or core-image library that contains the module and make the library available to the job.
Reason:
The module cannot be loaded due to insufficient GETVIS area.
Action:
To increase the GETVIS area:
Reason:
An internal error has been detected.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error has been detected.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A command was entered that is inactive for the current function, or is a command that DMA does not recognize.
Action:
Enter a command that is active for the current function.
Reason:
A PF key was pressed. However, the PF key is associated with a command that is inactive for the current function.
Action:
Press a PF key that is associated with a command that is active for the current function.
Reason:
An invalid select code was entered.
Action:
Enter a correct select code, and press the ENTER key.
Reason:
An internal error has been detected; DMA cannot be reaccessed through normal procedures.
Action:
For assistance, contact Technical Support at http://ca.com/support.
To reaccess DMA, choose one:
Reason:
A user ID and/or password were not correctly entered.
Action:
Correctly enter a user ID and password.
Reason: A security violation has occurred; the associated return-code points to the exact reason for the security violation.
Action: Choose one:
Reason:
The PF keys cannot be used until the sign-on is completed.
Action:
Complete sign-on.
Reason:
A command was entered in an attempt to access a DMA function that is not accessible from the current function.
Action:
Enter a command to access a function that is accessible from the current function.
Reason:
A subroutine error, indicated by message text x, has occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
One or more incorrect values were entered on a DMA screen.
Action:
Enter correct values and press ENTER.
Reason:
An entry required on the DMA screen has not been made.
Action:
Provide the required entry.
Reason:
More than one value was entered on a DMA screen when only one is permitted.
Action:
Enter only one value on the DMA screen.
Reason:
The user's default parameter file name (ID) is other than DEFAULT. DMA attempted to find, but could not locate the default parameter file.
Action:
Choose one:
Reason:
A command to transfer to another DMA function was entered. However, the current function does not permit transferring to another function
Action:
Enter a command that is active for the current function.
Reason:
The contents of a DMA parameter file (PARMFILE) structure are invalid.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The contents of a DMA parameter file (PARMFILE) structure are invalid.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The contents of a DMA parameter file (PARMFILE) structure are invalid.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A default parameter file was successfully created.
Action:
None.
Reason:
An ESAM/EDITOR interface call failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An ESAM/EDITOR interface call failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An ESAM/EDITOR interface call failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An ESAM/EDITOR interface call failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An ESAM/EDITOR interface call failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An ESAM/EDITOR interface call failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The contents of a DMA parameter file (PARMFILE) structure are invalid.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A previously aborted session was successfully restarted.
Action:
None.
Reason:
The PF key handler routine returned an invalid code, indicated by x.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The command NEXT was entered. However, it was entered for a function that has no naturally occurring function following it, that is, no NEXT function.
Action:
Enter another command.
Reason:
Correct values were entered at a DMA screen, the user pressed ENTER or NEXT, and the current session acquired the values entered.
Action:
None.
Reason:
Y for yes was entered for more than one of the DMA screen options.
Action:
Enter Y for yes for ONE option.
Reason:
N for no and/or blanks were entered for all of the DMA screen options.
Action:
Enter Y for yes for ONE option.
Reason:
A date field entered does not match the standard date criteria.
Action:
Enter a day within the range for the specified month, and enter a month within the range 01 to 12.
Reason:
A request was made to see a list of parameter files (PARMFILES) for a user who has no parameter files.
Action:
Choose one:
Reason:
A line command was entered in a selection list. However, the line command that was entered cannot be used on this screen.
Action:
Enter a line command that can be used on this screen.
Reason:
Upon viewing the Confirm DELETE of PARMFILE, the user terminated the deletion by using the PREVIOUS command.
Action:
None.
Reason:
A command has been entered to access a function that requires an established setup. However, a setup has not been established.
Action:
Establish a setup. You can establish a setup by providing DMA with the minimal values required for DMA to generate a parameter file. From the Select a DMA Activity screen, select or specify a parameter file, or else type Y after Define a new Migration? Press ENTER. Choose one:
Reason:
A D for delete was entered to the left of a parameter file belonging to a user other than the signed-on user.
Action:
Remove the D for delete.
Reason:
The ENTER command was used on the System Commands screen. However, a command was not typed in the command line, nor was an S for select typed to the left of the commands in the command list.
Action:
Choose one:
Then, press Enter.
Reason:
Upon viewing the Confirm Setup RESET screen, the user pressed ENTER, erasing all non-stored values and returning to the Select DMA Activity screen.
Action:
None.
Reason:
Upon viewing the Confirm Setup RESET screen, the user used the PREVIOUS command. Consequently, DMA returned the user to the System Commands menu.
Action:
None.
Reason:
A severe error occurred as DMA attempted to generate parameters.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A severe error occurred as DMA attempted to generate parameters.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
From the Store into a PARMFILE screen, the user attempted to store a session. And, the parameter file name typed in at the right of 'Save as PARMFILE' is the same as another parameter file name. However, N for no was typed to the right of the 'Replace Existing PARMFILE'.
Action
Choose one:
Note: If Y is entered for the replace option, the contents of the parameter file that is replaced are erased.
Reason:
A severe error occurred as DMA attempted to generate parameters.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A severe error occurred as DMA attempted to generate parameters.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The parameter file (PARMFILE) named in the message was successfully stored.
Action:
None.
Reason:
DMA attempted to upload CA IDMS Dictionary Migrator JCL to DMA. However, no JCL was available.
Action:
Provide CA IDMS Dictionary Migrator JCL to the syntax batch upload utility in file XDMPJCL.
Reason:
DMA successfully uploaded JCL to the parameter file (PARMFILE) named in the message.
Action:
None.
Reason:
An attempt was made from the batch environment to use parameters generated by DMA. However, no parameter file (PARMFILE) was available for the user named in the message.
Action:
Sign on to DMA.
Reason:
An attempt was made from the batch environment to use parameters generated by DMA. However, no parameter file (PARMFILE) by the name given in this message was available.
Action:
Choose one:
Reason:
When DMA was installed, the JCL batch upload utility XDMPJCL was not executed. Therefore, CA IDMS Dictionary Migrator JCL has not been uploaded to DMA.
Action:
Execute the JCL batch upload utility XDMPJCL. Retain as values:
USER=DEFAULT
PARMFILE=DEFAULT
Reason:
A STARTING POINT has been established. If the user just began to define a new migration, this message indicates that DMA collected values for the first starting point defined for the migration. If DMA collected values for the first starting point, this message means that values for a new starting point, either added to the parameter file, or to replace previously-specified values, have been collected.
Action:
None.
Reason:
At the Specify a New STARTING POINT screen, ENTER was pressed. However, no starting point was specified on the screen.
Action:
Provide values on the screen for one starting point.
Press Enter.
Reason:
Upon viewing the Confirm Session EXIT screen, the user used the PREVIOUS command. Consequently, DMA returned the user to the previous screen.
Action:
None.
Reason:
A severe error occurred when DMA attempted to display starting points
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
From the List of STARTING POINTS screen, S for select was typed to the left of a starting point that was not the active--current--starting point, and ENTER was pressed. The newly selected starting point was made the active, or current starting point.
Action:
None.
Note: Values subsequently supplied by DMA or provided by the user on DMA screens are for the newly selected starting point.
Reason:
Upon viewing the Confirm DELETE of Starting Point screen, the user used the PREVIOUS command. Consequently, DMA returned the user to the List of STARTING POINTS screen.
Action:
None.
Reason:
An attempt was made to delete the active--current--starting point.
Action:
Type S for select to the let of another starting point and press ENTER. This makes the newly selected starting point the active--current--starting point.
You can now type D for delete to the left of the previously active (previously current) starting point, and press Enter.
Reason:
The JCL contains changes that prevent DMA from submitting parameters and JCL to CA IDMS Dictionary Migrator.
Action:
Make the following changes in the JCL in the member USMXTRCT step USMGRTR:
For z/OS users: after
//MIGRPARM DD *
delete all parameters (syntax) for CA IDMS Dictionary Migrator.
For z/VSE users: after
//EXEC USMGRTR
delete all parameters (syntax) for CA IDMS Dictionary Migrator.
For VM/ESA users: let
OSRUN=USMGRTR
Reason:
The parameters for CA IDMS Dictionary Migrator and the JCL to run CA IDMS Dictionary Migrator were successfully submitted.
Action:
None.
Reason:
An attempt was made to submit parameters for CA IDMS Dictionary Migrator and JCL to run CA IDMS Dictionary Migrator. However, the attempt failed because DMA is installed in a CV that has an active operating system other than z/OS; z/VSE; or z/VM.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An attempt was made to submit parameters to CA IDMS Dictionary Migrator and JCL to run CA IDMS Dictionary Migrator. However, JCL to run CA IDMS Dictionary Migrator was not available.
Action:
All JCL lines may have been deleted when the JCL was edited. If so, choose one:
If the JCL lines were not deleted when the JCL was edited, contact Technical Support at http://ca.com/support.
Reason:
An attempt was made to submit parameters to CA IDMS Dictionary Migrator and JCL to run CA IDMS Dictionary Migrator. However, parameters (syntax) were not available.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An attempt to use the SHOW or JCL functions failed.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
During the use of the SHOW or JCL functions, extra commands were specified in addition to the PREVIOUS or END commands.
Action:
Delete the extra commands.
Reason:
From the JCL FOR MIGRATION screen, JCL was modified, ENTER was pressed, and the changes to the JCL were successfully processed.
Action:
None.
Reason:
From the Store into a PARMFILE screen, ENTER was pressed. However, no parameter file (PARMFILE) name was provided to the right of the line 'Save as PARMFILE'.
Action:
Choose one:
Reason:
The syntax batch download utility XDMPSYN was successfully executed. This execution means that the parameter file named in the message was copied from the PARMFILE database to a sequential file.
Action:
None.
Reason:
While extracting a map or a CA ADS dialog module, a DISPLAY MESSAGE CODE statement was encountered, but the indicated message number was not in the source dictionary.
Action:
If the message in question already resides in the object dictionary, the migration is still valid and no action is needed. If the message is not in the object dictionary, the dialog terminates when it tries to execute the message display, so the migration is invalid. You must either add the message to the source dictionary and rerun CA IDMS Dictionary Migrator or add the message directly to the object dictionary.
Reason:
A CA ADS INCLUDE statement referenced a module that is not in the source dictionary.
Action:
Correct the INCLUDE statement and rerun CA IDMS Dictionary Migrator
Reason:
An unexpected field was encountered in a CA IDMS Dictionary Migrator work file.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An unexpected record currency was returned to CA IDMS Dictionary Migrator.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An unexpected program communication was passed between CA IDMS Dictionary Migrator modules.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The LOADS option was specified for the referenced entity, but there is no corresponding load module.
Action:
If you are migrating load modules only, or if you are not going to regenerate load modules from the migrated source, take either of these actions: regenerate the load module into the source dictionary and rerun CA IDMS Dictionary Migrator, or regenerate the object dictionary load modules from the migrated source.
Reason:
An embedded code or edit table associated with an extracted map is not in source code form in the indicated dictionary.
Action:
If the map includes the table in link format, then the map is still usable. Otherwise, if the source for the table has been accidentally erased, it must be reconstructed for the migration to proceed correctly.
Reason:
Using the INCLUDE feature of CA ADS, a module attempts to include itself.
Action:
This is a clear indication that this module has not been processed by the CA ADS compiler. ADSC processing ensures that generated dialogs cannot have this sort of nested dialog. Change the INCLUDE statement.
Reason:
In processing one of the nested entity types, CA IDMS Dictionary Migrator has detected more than 500 levels of nesting. This message indicates an internal processing error during CA IDMS Dictionary Migrator processing.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
If a schema currently has a compilation error, an error flag is set in the schema record.
Action:
Correct the schema source in the syntax file before uploading the schema.
Reason:
A CA ADS verb DISPLAY, included in the source module of an extracted dialog, may contain a syntax error or a variable name.
Action:
If the verb DISPLAY contains a syntax error, correct the error. If the verb DISPLAY contains a variable name, you must extract the possible messages from the source dictionary.
Reason:
A CA ADS verb INCLUDE included in the source module of an extracted dialog contains syntax errors that prevents regeneration.
Action:
Correct the source of the dialog module.
Reason:
While parsing for dialog name, an invalid value was found.
Action:
Correct the source statement at the indicate line number.
Reason:
An internal error has been detected.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
In processing one of the nested entity types, CA IDMS Dictionary Migrator has detected more than 500 levels of nesting. In this case, one of the entity occurrences has as a component another entity occurrence of the same type, and the second entity occurrence also has as a component the first entity occurrence.
Action:
Check the relationships of the entities in the dictionary, decide which one of the entity occurrences should have as a component the other entity occurrence, and correct the connections.
Reason:
The indicated SOURCE entity has been changed without recompiling the associated LOAD version.
Action:
Recompile the indicated SOURCE entity and resubmit the migration.
Reason:
This message appears in the Source Dictionary Verification report when a subordinate entity has been changed, but one of its owners has not.
Action:
Review the relationship between the entities and determine whether to continue with the migration.
Reason:
An error has occurred in table processing. See the return codes table for a list of possible return codes.
Action:
Processing continues, results of the migration will be the same. However, performance degradation may occur. If errors occur repeatedly, contact Technical Support at http://ca.com/support.
Reason:
A CA ADS process module contains references to more than 500 different dialogs. An internal table has filled up.
Action:
The EXSOURCE=SUBPROGRAM parameter may be used to avoid the extraction of all referenced dialogs.
Reason:
The user named in the IDSOURCE parameter does not have IDD authority for the entity type named.
Action:
The user must have at least DISPLAY authority for entity types which may be migrated from the source dictionary. Either update the user to grant DISPLAY authority for the entity types needed, or change the parameters for the CA IDMS Dictionary Migrator run to avoid entity types for which the user ID has no authority.
Reason:
The ADSA system related a function to a dialog, but the dialog is not in the dictionary.
Action:
If the system designer intended to migrate a partially completed system, no action is necessary. If the intent was to migrate a completed system, but no dialog was located, then locate or create the appropriate dialog and add it to the dictionary.
Reason:
An unexpected record currency was returned to CA IDMS Dictionary Migrator.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A global record specified by a ADSA system was not located in the dictionary.
Action:
Add the record to the dictionary and rerun CA IDMS Dictionary Migrator.
Reason:
The load module for the ADSA application was not located in the dictionary.
Action:
If the load module is in a load library, copy the load module to the load area and rerun CA IDMS Dictionary Migrator. If the load module is not in a load library, regenerate the ADSA application and rerun CA IDMS Dictionary Migrator.
Reason:
An internal error has occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal error was detected.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An invalid value was encountered in a CA IDMS Dictionary Migrator work file.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
In processing one of the nested entity types during extraction, an invalid record currency was encountered.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An item that was specified for extraction could not be found in the source dictionary.
Action:
Review the EXTRACT statement for which this message is issued. Note the date and version used to identify items that are to be extracted. If you do not specify the desired date and version in your EXTRACT statement, these parameters default to values specified in the PROCESS statement, or CA IDMS Dictionary Migrator assigns default values in accordance with rules described in the chapter "Parameters".
Reason:
The bind of the object database failed.
Action:
Check the meaning of the returned CA IDMS error status code in the CA IDMS Messages and Codes Guide manual. If the status code is 1469, check your NODE and DICTIONARY statements for accuracy. If the status code is 0966, check that your cv.sysctl file was correctly specified and that all dictionary areas are available to that CV.
Reason:
Nothing was extracted for the specified EXTRACT statement.
Action:
No action is required. Note that this message applies only to the specified EXTRACT statement.
Reason:
None of the EXTRACT statements resulted in an extraction.
Action:
Review the selection criteria you specified to determine why no extractions were performed.
Reason:
A user ID was specified in an IDSOURCE statement but the user is not in the source dictionary.
Action:
Correct the user ID.
Reason:
In an EXTRACT statement, a subschema that has duplicates of the same name was identified only by its subschema name. Because there are duplicate subschemas with that name, the schema name is also needed to conclusively identify the subschema.
Action:
Add the name of the appropriate schema to the statement in question. See the chapter "Parameters" for information on correct syntax.
Reason:
The release level of a source dictionary defined in an EXTRACT statement is different from the release level of a source dictionary defined in the PROCESS statement.
Action:
The EXTRACT statement is bypassed.
Reason:
In processing one of the nested entity types, CA IDMS Dictionary Migrator has detected more than 500 levels of nesting.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An application has been encountered that was generated using an obsolete level of ADSA.
Action:
Recompile the indicated application using the current ADSA compiler, or use CA IDMS Dictionary Migrator Release 2.3 or earlier.
Reason:
Dictionary security requires a signon. IDSOURCE was not specified.
Action:
Provide the IDSOURCE parameter and rerun.
Reason:
The user ID named in IDSOURCE does not have authority all and cannot use Responsibility override.
Action:
Remove the Responsibility override parameter or use a user ID that has authority all. Rerun the job.
Reason:
An error has occurred in table processing. See the return codes table for a list of possible return codes.
Action:
Processing continues, results of the migration are the same. However, performance degradation may occur. If errors occur repeatedly, contact Technical Support at http://ca.com/support.
Reason:
An error has occurred in table processing. A return code of 4 indicates a possible GSSLOAD failure for the exclusion table module. Ensure the exclusion table specified in the EXCLTAB= process parameter is in the load library concatenation for the Dictionary Migrator run.
Action:
Processing continues, results of the migration are the same. However, performance degradation may occur. If errors occurs repeatedly, contact Technical Support at http://ca.com/support.
Reason:
The indicated file function could not be performed with the specified file.
Action:
See the following table to determine the reason the error occurred and appropriate action. If you receive a return code combination 0, 24, 0, 8, see z/VSE File Assignments for more information.
Reason:
The indicated file is not a VSAM file (z/VSE only).
Action:
CA IDMS Dictionary Migrator attempted to open the indicated file for VSAM processing. No action is required.
Reason:
An unexpected CA IDMS status error occurred during database processing.
Action:
See the CA IDMS Messages and Codes Guide manual for the status as indicated by y. If the cause is not apparent, contact Technical Support at http://ca.com/support.
Two types of errors can be reported by the return codes of n1, n2, n3, and n4--non-VSAM file errors and VSAM file errors. The error is described by n2 and n4. For VSAM file errors, n4 is always equal to 28. The error is described by n1, n2, and n3. A general return code is given by n4 for both non-VSAM and VSAM errors. All return codes are decimal values.
|
n4 |
Reason |
Action |
|---|---|---|
|
4 |
End-of-file |
Contact Technical Support. |
|
8 |
Open error or file is not open |
Look for JCL errors or for the use of improper files. |
|
12 |
An I/O error has occurred |
Find cause for I/O error. |
|
16 |
Request not recognized |
Contact Technical Support. |
|
20 |
File was already opened |
Contact Technical Support. |
|
24 |
Parameter list error |
Contact Technical Support. |
|
28 |
VSAM error n1=R15 return code from VSAM n2=low order byte from R0 GENCB/MODCB type of error n3=VSAM feedback byte error in I/O request |
Use n1, n2, and n3 to check for possible user errors. If there are no user errors, Contact Technical Support. |
|
32 |
Insufficient storage |
Increase storage for job step. |
|
36 |
SYNAD error occurred |
Contact Technical Support. |
|
40 |
BPAM FIND error n1=R15 n2=R0 |
Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors. |
|
44 |
BPAM STOW error n1=R15 n2=0 |
Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors. |
|
n2 |
Reason |
Action |
|
0 |
n4=8, use of unopened file n4=24, parameter list error |
Contact Technical Support. Contact Technical Support. |
|
1 |
JCL/label overrode parm list |
Remove DCB information from JCL and ensure that the correct files are referenced. |
|
2 |
Parm list overrode JCL/label |
Remove DCB information from JCL and ensure that the correct files are referenced. |
|
3 |
Unrecognized request |
Contact Technical Support. |
|
4 |
z/OS x13 ABEND trapped at open |
Fix cause for x13 ABEND. |
|
5 |
Tried to update seq. file |
Contact Technical Support. |
|
6 |
VSAM write at other than load |
Contact Technical Support. |
|
7 |
SOS table could not expand |
Contact Technical Support. |
|
8 |
z/OS DCB open failed |
Contact Technical Support. |
|
9 |
SOS table buffer pointer lost |
Contact Technical Support. |
|
10 |
SOS table file CB not built |
Contact Technical Support. |
|
11 |
z/OS DD statement Missing |
Supply missing DD statement. |
|
12 |
VSAM ACB open failed |
Contact Technical Support. |
|
13 |
Record format invalid |
Contact Technical Support. |
|
14 |
Macro format invalid |
Contact Technical Support. |
|
15 |
Record length not numeric |
Contact Technical Support. |
|
16 |
Record length too large |
Contact Technical Support. |
|
17 |
Block size not numeric |
Contact Technical Support. |
|
18 |
Block size too large |
Contact Technical Support. |
|
19 |
Invalid z/VSE sysname table |
Assemble a valid sysname table. |
|
20 |
z/VSE sysname table entry missing |
Assemble a sysname table with an entry for the missing one. |
|
21 |
z/VSE LU number too large |
Use an LU number within range. |
|
22 |
z/VSE sysname is not numeric or is misspelled |
Correct to a valid sysname. |
|
23 |
z/VSE sysname blank |
Do not use blank sysname. |
|
24 |
z/VSE LU not assigned |
Contact Technical Support. |
|
25 |
z/VSE DTF prototype missing |
Contact Technical Support. |
|
26 |
z/VSE logic module missing |
Generate missing logic module. |
|
27 |
z/VSE CCW mismatch |
Contact Technical Support. |
|
28 |
File is not a PDS |
Allocate file to a PDS. |
Reason:
The module could not be called because of an internal problem.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The module cannot be located in the available load or core-image libraries.
Action:
Locate the load or core-image library that contains the module and make the library available to the job.
Reason:
The module cannot be loaded due to insufficient GETVIS area (z/VSE only).
Action:
To increase the GETVIS area:
Allocate a smaller amount of space for the problem program area, using the SIZE= parameter; and, if necessary,
Reason:
An internal error has been detected.
Action:
For assistance, contact Technical Support http://ca.com/support.
Reason:
The major keyword underscored by asterisks (*******) is misspelled or is in error and cannot be processed.
Action:
Correct the spelling of the keyword and resubmit the job.
Reason:
The minor keyword underscored by asterisks (*******) has already been entered on the parameter statement underscored.
Action:
Delete the duplicate minor keyword phrase and resubmit the job.
Reason:
The required equal sign and value after the keyword are missing.
Action:
At the location underscored by an asterisk (*), enter an equal sign followed by an appropriate value for the parameter. Resubmit the job.
Reason:
A set of open and closed parentheses is required.
Action:
Enter a right parenthesis to enclose the phrase or list, and resubmit the job.
Reason:
The last phrase in this statement is a list (enclosed in parentheses) that ends with a comma. However, the next statement entered does not continue the list.
Action:
Continue the list by adding another keyword after the comma inside the parentheses; or move the comma outside the final parenthesis. Resubmit the job.
Reason:
The previous statement ended with a comma, but this statement begins with a major keyword.
Action:
Supply a continuation card or delete the comma, and resubmit the job.
Reason:
The value underscored by an asterisk (*) is incorrect for the keyword.
Action:
Supply the appropriate value, which is specified in the message, and resubmit the job.
Reason:
Two keyword phrases are not separated by a comma.
Action:
Supply a comma at the location underscored by an asterisk (*) and resubmit the job.
Reason:
The minor keyword underscored by asterisks (*******) is misspelled or is in error and was not processed.
Action:
Correct the spelling of the minor keyword and resubmit the job.
Reason:
A minor keyword was omitted at the location underscored by an asterisk (*).
Action:
Enter the missing minor keyword and resubmit the job.
Reason:
The minor keywords listed in the message were omitted. CA IDMS Dictionary Migrator cannot continue processing unless the indicated keyword or keywords are entered.
Action:
Supply the missing keyword or keywords and resubmit the job.
Reason:
A keyword was entered without a value. The acceptable values are listed in the variable portion of the error message.
Action:
Enter the correct value at the location underscored by an asterisk (*) and resubmit the job.
Reason:
The value underscored by asterisks (****) was already entered in the list. CA IDMS Dictionary Migrator cannot process this parameter unless you supply two different values.
Action:
Correct the value and resubmit the job.
Reason:
The value underscored by asterisks (******) must be in ascending numerical sequence from the previous value in the list.
Action:
Rearrange the values in the list in ascending sequence and resubmit the job.
Reason:
The value underscored by asterisks (*******) must be in descending numerical sequence from the previous value in the list.
Action:
Rearrange the values in the list in descending sequence and resubmit the job.
Reason:
An irrecoverable error has been detected.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A module call processor error occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A module load processor error occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An error occurred during a call of the printer module.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A JCL DD card was not supplied.
Action:
Correct the JCL and resubmit the job.
Reason:
An ASSGN card was not supplied.
Action:
Correct the JCL and resubmit the job.
Reason:
A parameter file with an LRECL other than 80 was supplied.
Action:
Create a parameter file with an LRECL of 80 and resubmit the job.
Reason:
The file handler is unable to open the file.
Action:
See the previous table to determine the reason the error occurred and appropriate action.
Reason:
The file handler is unable to read the file.
Action:
See the previous table to determine the reason the error occurred and appropriate action.
Reason:
The file handler is unable to close the file.
Action:
See the previous table to determine the reason the error occurred and appropriate action.
Reason:
Because of a previous error, the phrase or phrases underscored by the letter X in the Parameter Verification Report have not been processed.
Action:
None.
Reason:
Because of a previous error, the value or values underscored by the letter X in the Parameter Verification Report have not been processed.
Action:
None.
Reason:
A CA IDMS Dictionary Migrator input parameter statement has been read. The entire 80-byte image is displayed. Columns 1 through 72 are processed.
Action:
None.
Reason:
The parameter statement continues a previous statement entered.
Action:
None.
Reason:
The parameter statement contains an asterisk (*) as the first non-blank character. This indicates that it is a comment statement, and it is not processed.
Action:
None.
Reason:
All parameters that were entered have been read and processed by CA IDMS Dictionary Migrator.
Action:
None.
Reason:
The parameter statement contains only blanks in columns 1 through 72 and is not processed.
Action:
Correct and resubmit the job.
Reason:
A value was entered that contains an odd number of apostrophes. Literal values must begin and end with single apostrophes. To represent a single apostrophe within a literal, you must enter two apostrophes. The acceptable values are listed in the variable portion of the error message.
Action:
Correct the value underscored by asterisks (****) and resubmit the job.
Reason:
A literal value was entered with improperly placed apostrophes. Literal values must begin and end with single apostrophes. To represent a single apostrophe within a literal, you must enter two apostrophes. The acceptable values are listed in the variable portion of the error message.
Action:
Correct the value underscored by asterisks (****) and resubmit the job.
Reason:
The first statement in the input stream was not a PROCESS statement.
Action:
Correct the input stream so that the first statement it contains is a PROCESS statement.
Reason:
Only one parameter was specified in the CLSATTR= clause.
Action:
Enter the missing class or attribute. Both the class and the attribute must be inside parentheses, separated by a comma.
Reason:
LEVEL=ENTITY was specified for one of these extract types, but CA IDMS Dictionary Migrator has changed it to LEVEL=DIALOG because LEVEL=ENTITY is not permitted in this context.
Action:
If you specified LEVEL=ENTITY intentionally because you wanted to extract only one entity occurrence, you will need to find another way to migrate the record. One way is to use OnLine IDD to add the entity to the object dictionary. If you specified LEVEL=ENTITY unintentionally, no action is needed.
Reason:
The input stream did not contain any CA IDMS Dictionary Migrator statements.
Action:
Specify CA IDMS Dictionary Migrator statements in the job stream.
Reason:
The input stream did not include an EXTRACT statement.
Action:
Enter at least one EXTRACT statement.
Reason:
The code returned by the keyword processor identifies an irrecoverable error.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An invalid value has been specified for NEWVERSION.
Action:
Correct the NEWVERSION value and resubmit.
Reason:
An invalid value has been specified for CLISTVERSION.
Action:
Correct the CLISTVERSION value and resubmit.
Reason:
CHANGE command was entered, but a SEARCH and REPLACE were not provided.
Action:
Correct the CHANGE command and resubmit.
Reason:
CHANGE command was entered, but the SEARCH string was null (").
Action:
Correct the SEARCH string of the CHANGE command to an explicit value.
Reason:
If only a message number is given, it can be no longer than 6 digits.
Action:
Correct the message number and resubmit the run.
Reason:
When the message prefix is specified, the message ID must be in the format AA999999 (A = Alphanumeric, 9 = numeric)
Action:
Correct the message ID and resubmit the run.
Reason:
Entity type of system can only be used with LEVEL=DIALOG.
Action:
Processing continues, the specified level parameter is ignored and dialogs related to the system are migrated.
Reason:
CVSOURCE and CVOBJECT are not valid parameters.
Action:
The processing environment for CA IDMS Dictionary Migrator must be defined using the SYSCTL and SYSIDMS files, For more information, see the chapter "Operations" for details.
Reason:
An EXTRACT statement has been specified when the run type is IMPORT or CREATESYNTAX. For these run types the extract processing has been done in a previous job step and cannot be respecified now.
Action:
Correct the parameters and resubmit.
Reason:
The specified identifier does not conform to correct SQL naming standards. Identifiers can be at most 18 characters long. Tables and view identifiers must be qualified by a schema name.
Action:
Correct the name of the SQL identity and resubmit.
Reason:
SQLONLY parameter requires runtype to be EXPORT or PARMCHECK.
Action:
Change the runtype to EXPORT or PARMCHECK and resubmit.
Reason:
An irrecoverable error condition has been detected.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An unexpected end-of-file has been encountered in a CA IDMS Dictionary Migrator work file.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An unexpected value has been encountered in a CA IDMS Dictionary Migrator work file.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An unexpected value has been encountered in a CA IDMS Dictionary Migrator work file.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
A utility has returned an error code that implies syntax errors in PUNCH statements.
Action:
Review the utility output messages for PUNCH statements, and evaluate the severity of the error based on the context in which it occurred. If necessary, correct the source dictionary and rerun CA IDMS Dictionary Migrator.
Reason:
Syntax created by CA IDMS Dictionary Migrator for schemas may require review.
Action:
Review the contents of the file and change the syntax in the appropriate syntax file (SCHMUPD).
Reason:
The file named in this message does not contain any transactions.
Action:
Do not include this file in the upload processing.
Reason:
The utility can process only one transaction each time it accesses a file. The file, however, contains multiple transactions that must be separated.
Action:
Edit the file to separate the transactions before performing the upload steps. Delete the message.
Reason:
A utility returned an empty syntax file that should have contained syntax statements.
Action:
Review the utility output error messages listed on the Syntax Production Report. Correct the error and rerun CA IDMS Dictionary Migrator.
Reason:
This message appears after a successful non-IMPORT run. The name and version of the MODULE containing a CLIST of VARY NEW-COPY statement is provided. This module is to be executed after migration load modules have been generated, thereby enabling the new copies.
Action:
Refer to the indicated module name and version for new-copying the migration components.
Reason:
An attempt to change the dictionary failed.
Action:
Contact Technical Support and report the return code. Ensure that the dictionary and node specifications in the parameters are correct.
Reason:
An error has occurred in table processing. See the return codes table for a list of possible return codes.
Action:
Processing continues, results of the migration will be the same. However, performance degradation may occur. If error occurs repeatedly, contact Technical Support at http://ca.com/support.
Reason:
While generating hard copy of all the control statements that are used during the migration, CA IDMS Dictionary Migrator has found that one of the control statement files contains no statements.
Action:
The file is empty because the user-specified extraction criteria did not yield any control statements of the kind stored in this file.
Reason:
Unexpected condition encountered in load module processing.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The new string of a change command is longer than the old string and there is not enough space on the line to absorb the difference.
Action:
The change must be made manually.
Reason:
A CA IDMS Dictionary Migrator internal sort procedure encountered a fatal sort error.
Action:
Review the sort messages in the output. If the cause of the error is apparent, correct it and rerun CA IDMS Dictionary Migrator. If you cannot find the error, contact Technical Support at http://ca.com/support.
Reason:
This message appears during sort of CHANGEONLY extractions. A user has been specified in the IDOBJECT statement that is not in the OBJECT dictionary.
Action:
Correct the IDOBJECT user and resubmit.
Reason:
This message appears when NEWVERSION=NULL has been specified, and the installed values of default versions for new and existing entities do not meet the requirements of CA IDMS Dictionary Migrator.
Action:
Correct the values of default version in the Object dictionary, or do not use the NEWVERSION=NULL feature. The default version for new and existing entities must be a numeric integer (that is, not NEXT HIGHEST or LOWEST, etc.), and new and existing default specifications must be equal.
Reason:
An invalid action was requested for the submit function.
Action:
For assistance, contact Technical Support at http://ca.com/(have a listing of the dump available for reference).
Reason:
An internal error has occurred.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The submit function was unable to obtain storage.
Action:
Check the meaning of the return code from the get storage request in the CA IDMS Messages and Codes Guide manual and take the action suggested there
Reason:
The file passed to the submit function was empty.
Action:
Ensure that the correct file is being used for the submit and that the file has the proper content.
Reason:
An invalid operating system code was provided to the submit function.
Action:
The value of 'var' was determined by the program calling the submit function. Contact Technical Support (have the listing of the dump available for reference).
Reason:
The submit function is being used by another user.
Action:
Try to submit again. The submit function must have exclusive use of certain resources to avoid conflicts, but the resources are held for a short period of time.
Reason:
An attempt to dynamically allocate the internal reader failed with the codes indicated.
Action:
Refer to the IBM System Macro and Facilities manual SVC 99 for explanations of code and take the action indicated.
Reason:
The online job submission facility received an unsuccessful return code from z/VSE macro XPCC invoking the IDENTIFY or CONNECT function. The ID CDE indicates which macro call and situation occurred. Further information can be determined from the ERR CDE and INFO CDE values. See the IBM z/VSE Power Application Programming manual for further details.
Action:
This situation may be temporary. Re-issue the submit request. If the problem persists, make note of all information in the message and notify your DBA of the situation.
Reason:
The online job submission facility received an unsuccessful return code from z/VSE macro XPCC invoking the DISCONNECT or TERMINATE function. The ID CDE indicates which macro call and situation occurred.
Action:
This situation can only occur after the JCL has successfully been submitted. If the problem persists, make note of all information in the message and notify your DBA of the situation.
Reason:
The online job submission facility received an unsuccessful return code from z/VSE macro XPCC invoking the SENDR function. Further information can be determined from the ERR CDE and the INFO CDE values. See the IBM z/VSE Power Application Programming manual for further details.
Action:
This situation may be temporary. Re-issue the submit request. If the problem persists, make note of all information in the message and notify your DBA of the situation.
Reason:
The OBJECTDICTIONARY OBJECTNODE as specified for the migration run was not able to be bound.
Action:
Correct the invalid parameter and resubmit.
Reason:
There are no users in the USERUPD file. This error can be caused by specifying the DISCONNECT=(USER) parameter, or by the lack of USER associations in the source dictionary.
Action:
Either remove the DISCONNECT=USER parameter, or continue the migration without change
Reason:
The indicated USER cannot be located in the Object dictionary for password restoration.
Action:
Review the migration to determine whether the USER was migrated. If the USER was deleted prior to this step, no further action is required. Otherwise, the USER should be in the Object dictionary and eligible for modification.
Reason:
Each migrated USER now has their password converted to the value in the SOURCE dictionary.
Action:
None.
Reason:
Navigation of the SQL catalog has been successfully completed.
Action:
None.
Reason:
An extract record has been written for the named SQL schema and table.
Action:
None.
Reason:
An extract record has been written for the named SQL schema and view.
Action:
None.
Reason:
An extract record has been written for the named SQL schema.
Action:
None.
Reason:
An invalid type code for an SQL entity was passed to the catalog navigation program.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An error has occurred in table processing during catalog navigation. See Figure 7.2 for a list of possible return codes.
Action:
Processing continues but catalog navigation terminates for the SQL entity being extracted.
Reason:
An out-of-storage condition has occurred which will limit the number of SQL entities to be extracted.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An extract statement for an SQLVIEW was submitted but the named SQL entity is a table.
Action:
None. Processing continues and an extract is written for the named SQL schema and table.
Reason:
Network references are not extracted from the SQL catalog.
Action:
None. Processing continues.
Reason:
An extract record has been written for the named SQL constraint.
Action:
None.
Reason:
An extract record has been written for the named table procedure.
Action:
None.
Reason:
An extract record has been written for the name key.
Action:
None.
Reason:
The requested SQL entity was not found in the catalog.
Action:
Correct the extract statement and resubmit
Reason:
An invalid primary command was encountered. The cursor is on the command.
Action:
Check the syntax of the command. Correct and reenter the command.
Reason:
A valid command has been entered with an unrecognizable parameter.
Action:
Check the syntax of command parameter. Correct and reenter the parameter.
Reason:
A line number was not included as a parameter in the LOCATE command.
Action:
Check the syntax of the command. Correct the command (include line number parameter) and reexecute.
Reason:
An illegal option has been used with the LEFT, RIGHT, UP, or DOWN command.
Action:
Check the syntax of the parameter. Correct the parameter (you may have included some erroneous characters in the syntax line) and reexecute
Reason:
An illegal option has been used with the NULLS command.
Action:
Check the syntax of the parameter. Correct the parameter (you may have included some erroneous characters in the syntax line) and reexecute.
Reason:
A parameter has been included in the syntax of the CANCEL command which excludes parameters.
Action:
Check the syntax of the command. Correct the command (delete the parameter) and reexecute.
Reason:
The string indicated has been found in the text. The cursor will be positioned at the beginning of the found string.
Action:
None.
Reason:
The string indicated has been replaced with the replacement string. The cursor is positioned after the replacement string.
Action:
None.
Reason:
The RFIND (repeat find) or RCHANGE (repeat change) command was entered without a FIND or a CHANGE command being entered first.
Action:
Be sure to enter the FIND command or the CHANGE command before the RFIND command or the RCHANGE command.
Reason:
The bottom of the text was reached before the string was found. If you enter an RFIND (repeat find) or an RCHANGE (repeat change) at this time, the editor begins searching for the string at the top of the text.
Action:
None.
Reason:
A single quotation mark was found where a pair is required or embedded blanks were found in the search string.
Action:
Check quotation marks, correct, and reenter the command. If a string has embedded blanks, enclose it in quotation marks.
Reason:
The string specified in the FIND command is invalid. If the string has embedded blanks or quotation marks, it may appear to the editor to be more than one string: you can only specify one string in the FIND command.
Action:
Check the syntax of the command. If the string has embedded blanks, enclose it in quotation marks. If the string has embedded single quotation marks, enclose it in double quotation marks. If the string has embedded double quotation marks, enclose it in single quotation marks. Then reenter the command.
Reason:
A string specified in the CHANGE command is invalid. If one of the strings has embedded blanks or quotation marks, it may appear to the editor that you are entering more than two strings: you can only specify two strings in the CHANGE command.
Action:
Check the syntax of the command. If a string has embedded blanks, enclose it in quotation marks. If a string has embedded single quotation marks, enclose it in double quotation marks. If a string has embedded double quotation marks, enclose it in single quotation marks. Then reenter the command.
Reason:
The editor has searched the entire text without finding the indicated string.
Action:
None.
Reason:
The string used to replace the one found is too long.
Action:
Adjust the length of the found string or reduce the length of the replacement string to match the length of the one found.
Reason:
A string specified in the FIND ALL command has been found the specified number of times.
Action:
None.
Reason:
A string specified in the CHANGE ALL command has been changed in the text the specified number of times.
Action:
None.
Reason:
The CHANGE command was used in the Browse Option to search for and change the next occurrence of a string.
Action:
None. The CHANGE command can only be used when editing text (Edit Option) and not while in Browse mode.
Reason:
The string identified in the CHANGE ALL command has been changed successfully (nnn OCCURRENCES) with (nnn ERRORS) unsuccessful changes.
Action:
Look for the error message on the line number field(s) and make the necessary correction(s).
Reason:
An invalid line command has been entered.
Action:
Check the syntax of the line command on the line number field. Correct and reenter the command.
Reason:
A line command has been entered on a line for which the command is invalid.
Action:
Reenter the line command on an appropriate line.
Reason:
An invalid Scroll Option was entered in the SCROLL field.
Action:
Check the syntax of the Scroll Option next to the word SCROLL. Be sure the option starts in the left-most position of the field. Correct syntax or position.
Reason:
A partial sequence of Line Commands, in block form (CC, DD, MM, RR), is incomplete and cannot be executed.
Action:
If you are just scrolling or using the FIND command to locate the line to complete the block command, this message serves as a warning. Complete the command and execute. Otherwise, check the syntax of the commands to be sure all commands in block form are in pairs. Correct the commands and reexecute.
Reason:
A sequence of Line Commands cannot be executed.
Action:
Check the order of the commands. Correct the commands and reexecute.
Reason:
A move or a copy cannot be executed because of a missing A (after) or B (before) line command.
Action:
Enter an A or a B command to indicate the location to which lines are to be moved or copied. This message serves as a warning if you are just scrolling or using the FIND command to locate the line for the A or B command.
Reason:
A set of repeat (RR) line command iterations have conflicting values.
Action:
Check the syntax of the command. Make sure that the values of the iterations match (one or both may be left blank).
Reason:
A sequence of Line Commands cannot be executed because the range of one line command overlaps the range of another.
Action:
Check the order of the commands. Correct the commands and reexecute.
Reason:
An unexpected value has been encountered in a CA IDMS Dictionary Migrator work file.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
An internal file error occurred during CA IDMS Dictionary Migrator processing.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason
A relationship encountered in the object dictionary is not among the entities extracted from the source dictionary.
Action:
Review the missing relationship to determine the impact of extracting or not extracting the entity.
Reason:
An element override has been specified for a record element.
Action:
Review the element in the source dictionary to see whether the override should be migrated. Otherwise, correct the element on the source dictionary and rerun CA IDMS Dictionary Migrator or edit the syntax in the syntax subfiles.
Reason:
An unexpected value has been encountered in a CA IDMS Dictionary Migrator work file.
Action:
For assistance, contact Technical Support at http://ca.com/support.
Reason:
The bind of the object database failed.
Action:
Review the OBJDICTIONARY and parameters of the PROCESS statement and SYSCTL and SYSIDMS file allocations to determine the cause of the invalid run-unit.
Reason:
A user ID was specified for the IDOBJECT parameter, but the user is not authorized to access the object dictionary.
Action:
Correct the user ID in the IDOBJECT parameter to allow the upload to process correctly.
Reason:
The file named in the message contains no transactions.
Action:
step for the file named in the above message. Remove this set of JCL statements from the upload job.
Reason:
The utility can process only one transaction each time it accesses a file. The file, however, contains multiple transactions that must be separated.
Action:
Edit the file to separate the transactions before performing the upload steps.
Reason:
While checking to see whether an application can be loaded into the object dictionary, CA IDMS Dictionary Migrator encountered in the object dictionary a PROG-051 record for an entity other than an application.
Action:
To load the application:
Reason:
Because the VSAMEXT file is in some format other than VSAM, processing has terminated.
Action:
Check whether an allocation was made for a VSAM dataset. If not, allocate a VSAM data set. If an allocation was made for a VSAM data set, delete any dataset with the same name as the VSAMEXT VSAM data set. Resubmit the job.
Reason:
This message appears when the primary picture clause in the source and object dictionaries do not match. "a" and "b" represent the COBOL picture clause associated with the element.
Action:
Review the information and make a decision based upon the context of the picture mismatch.
Reason:
An entity, which is to be migrated, cannot be changed unless the entity named in this message is regenerated. The entity named was found in the source dictionary while traversing the extraction path, but was not extracted due to selection criteria.
Action:
Review the named entity and the changes to the entity that caused the forced regeneration. If there is no effect, upload the files as created. If the effect is detrimental, either the entity causing the forced regeneration must be removed from the migration, or the entity requiring regeneration added to the migration. Because the entity was part of the structure being migrated from the source dictionary, the regeneration often has no adverse effects.
Note: If the entity named in the message is related to several migrated entities, this message appears repeatedly, listing each relationship. The entity is regenerated only once.
Reason:
When using NEWVERSION option, two entities with the same type and name, but with different versions were extracted. Because only one version can exist after migration, the conflicting entity occurrences are eliminated.
Action:
Review all versions of the entity occurrence named to determine if the single version (shown in the entity detail report) can be used in all instances. If it can, proceed with the migration; otherwise, resolve the conflict in entity names.
Reason:
When using NEWVERSION option, the two entities with the same type and name, but with different versions, were extracted.
Action:
Review all versions of the entity occurrence named to determine if the single version (shown in the entity detail report) can be used in all instances. If it can, proceed with the migration, otherwise, resolve the conflict in entity names.
Reason:
A loadhdr-156 record was found in the source DDLDCLOD area for the entity named, but no loadtext-157 records are connected to it.
Action:
This is an error in the object dictionary load area. Run CA IDMS/DB Audit to determine if there are other errors.
Reason:
A map has been migrated or forced to regenerate, which in turn requires the programs using it to be recompiled to update the map date stamp. Dialogs are automatically forced to regenerate.
Action:
Recompile the named program.
Reason:
The CHANGEONLY or ADDONLY parameters were not consistently specified in the EXPORT and IMPORT run.
Action:
Determine which parameter should be used and rerun the appropriate steps.
Reason:
An internal error has occurred (possibly insufficient region size for a get storage request). See the return codes table for a list of return codes.
Action:
Processing continues, results of migration are the same. Performance degradation may occur, however. If error occurs repeatedly, contact Technical Support at http://ca.com/support.
Reason:
Target dictionary security requires a IDOBJECT user ID be provided.
Action:
Supply a valid IDOBJECT
Reason:
The IDOBJECT user ID provided does not have authority to use Registration-Override.
Action:
Either omit the Registration-Override option from IDOBJECT, or provide an IDOBJECT user ID with authority to use Registration-Override.
Reason:
The IDOBJECT user ID does not have at least DISPLAY authority for the named entity type and validation processing (for this run) requires access to that entity type. The authorization at an entity type level is only done when the entity type is actually encountered.
Action:
Use an IDOBJECT user ID with at least display authority for all entity types, OR insure that entity types for which the IDOBJECT user ID does not have authority are not selected for migration.
Reason:
The free storage request for an internal table failed.
Action:
In the short run, this error should have no effect on a migration run, or its results unless the region/partition is not large enough to allow that storage not to be reused.
Reason:
An entity, which is to be migrated, cannot be changed unless the entity named in this message is regenerated. The entity named is not among the entities extracted from the source dictionary.
Action:
Review the named entity and the effect changes to the entity causing the forced regeneration has upon the named entity. If there is no effect, upload the files as created. If the effect is detrimental, either the entity causing the forced regeneration must be removed from the migration, or the entity requiring regeneration is added to the migration (after correcting whatever ill effects that might occur).
Note: If the entity named in the message is related to several migrated entities, this message appears repeatedly, listing each relationship. The entity is regenerated only once.
Reason:
The table named has different characteristics in the source and object dictionaries. The characteristics cannot be changed in a MODIFY command, therefore the update of the table is complete unless remedial action is taken first.
Action:
Determine which characteristics should be used and correct the appropriate entity.
|
Copyright © 2014 CA.
All rights reserved.
|
|