COBOL Copybook return codes and messages
If the COBOL copybook input file specified to the Importer Wizard contains incorrect or invalid COBOL copybook statements, the Importer Wizard maps will attempt to skip the erroneous statements and continue on with the next valid statement. Invalid statements are reported in the COBOL Copybook importer error and warning report.
Trying to import a file that contains a large number of errors or is not a valid COBOL copybook definition might result in the failure of the Importer Wizard to create a type tree. When this situation occurs, the maps executed by the Importer Wizard might report warning and error messages when you run the COBOL Copybook importer wizard.
The following is a list of return codes and messages along with hints or instructions for trying to resolve the problem:
- Return Code
- Message
- N/A
-
Unable to rename ...
An attempt might have been made to write to a read-only directory, an output file directory might be missing, or there might not be sufficient disk space on the output drive.
- 1
- User aborted map
If you cancel execution before the map completes, this message is displayed.
- 2
- Not enough memory to execute map
Close other running applications and re-try.
- 3
- Could not open map
One of the map executable files (.mmc) cannot be found. Check that the following four files are present in the install directory: UnBlock.mmc, NormalizeCopyBook.mmc, TranslatFile.mmc, BuildTTMakerScript.mmc
- 4
- Could not read map
- 5
- Could not read inputs
- 6
- Invalid map handle
- 7
- Invalid card number was specified
Your map might be corrupt.
- 8
- One or more inputs was invalid
Check to make sure a proper copybook input file was specified.
- 9
- Target not available
This might be a security/authorization problem. Verify that you have authorization for read access for the input copybook file and write access for the specified output directory and the product installation directory.
- 10
- Internal error
- 11
- Could not build one or more outputs
An attempt might have been made to write to a read-only directory, an output file directory might be missing, or there might not be sufficient disk space on the output drive.
- 12
- Source not available
An incorrect file name or path for the copybook input file might have been specified.
- 13
- Could not open work files
There might not be sufficient disk space on the drive where the install directory exists to create necessary importer work files.
- 15
- Map must be recompiled
You might have an outdated version of the importer maps versus the installed version of the Command Server. Re-install the correct version of the importer.
- 16
- Disk write error
An attempt might have been made to write to a read-only directory or file. Also, check the amount of available disk space.
- 17
- Disk read error
An attempt might have been made to access a file on a shared resource that is not accessible. Also, check the amount of available disk space.
- 18
- Page usage count error
An internal paging problem exists.
- 19
- Internal calling error
- 20
- Reopen file failed
A map did not run correctly.
- 21
- Input valid but unknown data found
The input specified is likely not a valid copybook. Check to make sure a proper copybook input file was specified.
- 22
- Page size too small
- 28
- Input type contains errors
Invalid copybook statement(s) were found in the specified input. The COBOL Copybook Importer error report file should contain details on the problem statement(s).
- 50
- Type exists and is not overwritten
A duplicate definition was found in the .mts file. The COBOL Copybook Importer uses the first definition found for a given field or group name and ignores or warns about any duplicate names.