| WRC0308
|
The monitoring rule is not allowed for numeric and alphabetical classes.
|
This is a result of a check on the entered data within the
Work with classes function. The product does not allow monitoring rules to be defined at class level for classes that can be associated with either numeric or alphanumeric fields.
|
|
|
| WRC0319
|
No file was found with the specified parameters.
|
A batch function has been launched by specifying, for the launch parameters, values that have no correspondence with a file loaded in the environment.
|
Make sure the files you want to process have been loaded with the
Work with files function and that the launch parameters specified for the processing are correct.
|
|
| WRC0321
|
The data set or member is empty.
|
The message displayed is a result of a check on the entered data.
|
|
|
| WRC0325
|
Number of steps required.
|
The field
From Step or
To Step of the
Deletion Job Generation mask contains non-numeric characters.
|
Insert numeric characters into the field.
|
Deletion Job Generation
|
| WRC0326
|
From Step cannot be greater than To Step.
|
The field
From Step cannot contain a number greater than that contained in the field
To Step.
|
Correct the number inserted into the
From Step field.
|
Deletion Job Generation
|
| WRC0327
|
Value
ValueName was not inserted in the list for method
MethodName, step
StepNumber
, class
ClassName.
|
This is a result of a check on the entered data. For DL/I, during each processing operation, an output is produced in the list between a parent segment and the following segment only for the first 9999 separate values.
|
|
Test environment generation
|
| WRC0328
|
File
FileName was not found for machine ID
MachineID, company
CompanyName.
|
A message has been generated in the error log at the end of the test environment generation phase. The product has highlighted that the specified file, which has been subjected to extraction, is missing from the repository. The file is likely to have been removed from the environment.
|
|
Test environment generation
|
| WRC0330
|
Unable to retrieve
Entity information for file
FileName.
|
The message displayed is a result of a check on the entered data for the file deleting function. The message prevents files for which there are balancing rules or test environment extraction methods from being deleted from the scheduler.
|
|
|
| WRC0332
|
Direct access for the file
FileName is not allowed for data masking routines.
|
The Data Masking batch phase has not been performed because it had been launched for a DL/I file with direct access. The Data Masking phase can be performed for a DL/I file only on sequential unload.
|
|
Data Masking
|
| WRC0333
|
Direct access for DL/I files is not allowed for environment creation.
|
The extraction batch phase has not been performed because it had been launched for a DL/I file with direct access. The Environment Creation phase can be performed for a DL/I file only on sequential unload.
|
|
Environment creation
|
| WRC0338
|
Specify method or group.
|
The field
Method or
group cannot contain spaces.
|
Insert the method name or the group name.
|
Deletion Job Generation/ Creation Delete Define Sources
|
| WRC0341
|
No parent segment was found for DL/I DBD
DatabaseName.
|
Extraction has not been performed because the name of a parent segment for a DL/I file has not been specified.
|
|
Environment creation
|
| WRC0348
|
The file
FileName is empty. 5000 records are assumed.
|
An informational message is generated after an empty file has been loaded. The number of 5000 records is assumed.
|
|
File loading
|
| WRC0356
|
Method
MethodName has been deactivated as field
FieldName is no longer listed in file
FileName but is still associated to a reduction rule.
|
The specified method has been deactivated. After a file structure change, a field that is no longer present in the new structure is associated to an association rule.
|
Check the reduction logic of the specified file and method, and apply the reduction criteria coherent with the new file structure.
|
Life Cycle
|
| WRC0363
|
Field
FieldName of file
FileName exceeds the maximum length for type
FieldType. The next elaboration phase cannot manage it.
|
An internal elaboration, phase cannot manage the field.
|
|
|
| WRC0364
|
Fixed point types are not supported; the field
FieldName of file
FileName will be treated as a 4-byte binary number.
|
|
|
|
| WRC0366
|
The record length must be less than 32760. Record
RecordNumber of file
FileName will be discarded.
|
Data Manager cannot handle files with record lengths greater than 32760.
|
|
|
| WRC0367
|
JobName - Start elaboration
|
The specified job has started.
|
|
|
| WRC0368
|
JobName - End elaboration
|
The specified job has ended.
|
|
|
| WRC0369
|
An error occurred during the edit of string
StringName in
SourceName.
|
During the preparation of the job, job parameters cannot be substituted.
|
|
|
| WRC0370
|
Error found in writing file
FileName - File status:
FileStatus.
|
Data Manager is not able to write the specified file.
|
Verify that the file exists, there is space in the file, and that the user has authorizations on file.
|
|
| WRC0371
|
Job
JobName submitted.
|
Data Manager has submitted the specified job.
|
|
|
| WRC0372
|
JCL
JCL-Name created.
|
Data Manager has created the specified JCL.
|
|
|
| WRC0373
|
The output file has more than 44 characters. File:
FileName, Prefix:
FilePrefix.
|
The output file is expected to be a MVS file, which has no more than 44 characters.
|
|
|
| WRC0374
|
Error in reading file
FileName - File status:
FileStatus.
|
Data Manager is not able to read the specified file.
|
Verify that the file exists and that the user has authorizations on file.
|
|
| WRC0375
|
An abend has occurred.
|
Data Manager has identified a batch phase that had an abnormal termination.
|
Check the MVS sysout to determine the reason for the abend.
|
|
| WRC0376
|
More than 249 files have been found for method
MethodName processing.
|
For each extraction job generated, no more than 249 files can be put in the same JCL.
|
|
Create Extraction Jobs
|
| WRC0377
|
Data set
Data-Set-Name and data set
Data-Set-Name have not been found in the SYSCOPYS table. Check the unload input file.
|
The DB2 system catalog information (SYSCOPYS table) does not contain the information about the specified image copybook data set.
|
Check the name of the specified image copybook data set.
|
Masking, subsetting
|
| WRC0378
|
The field
FieldName has a length of 16 bytes, which assumes 31 digits.
|
It is assumed that a binary field of 16 bytes has 31 digits.
|
|
File loading
|
| WRC0379
|
An error occurred during the Level ID calculation.
|
An internal error occurred in the Level ID calculation.
|
Check previous messages during the calculation for more information.
|
File loading
|
| WRC0380
|
The process identifier
ProcessID is not permitted for the job Load DB2 Table Information by Unload.
|
For the job Load DB2 Table Information by Unload, only access types R, U, and W are supported.
|
Verify the access type is appropriate for the process identifier you are using.
|
File loading
|
| WRC0381
|
The table name is not defined in the table-name statement in DCLGEN
DCLGEN-Member.
|
In the parsing of the DCLGEN, the keyword DECLARE has not been found.
|
|
File loading
|
| WRC0382
|
The DCLGEN will be discarded.
|
Due to a previous error, the DCLGEN has not been processed.
|
|
File loading
|
| WRC0383
|
The creator has not been defined in the table-name statement in DCLGEN
DCLGEN-Member.
|
In the parsing of the DCLGEN, the table creator has not been found.
|
|
File loading
|
| WRC0384
|
Unexpected column type
ColumnType was found in
DCLGEN-Member.
|
In the parsing of the DCLGEN, an unexpected or unhandled column type has been found.
|
|
File loading
|
| WRC0385
|
Unknown syntax was found in the table-name statement. Check the DCLGEN source
DCLGEN-Member.
|
In the parsing of the DCLGEN, the table name has not been found.
|
|
File loading
|
| WRC0386
|
Error opening data set
Data-Set-Name.
|
Data Manager is not able to open the specified file.
|
Verify the file exists, there is space in the file, and that the user has authorizations on file.
|
|
| WRC0387
|
Error closing file
FileName - File status:
FileStatus.
|
Data Manager is not able to close the specified file.
|
Verify the file exists, there is space in the file, and that the user has authorizations on file.
|
|
| WRC0388
|
DBD:
DatabaseName
|
Information about the processed file is written in the job output.
|
|
|
| WRC0389
|
File type:
FileType
|
Information about the processed file is written in the job output.
|
|
|
| WRC0390
|
File Name:
FileName
|
Information about the processed file is written in the job output.
|
|
|
| WRC0391
|
Version:
FileVersion
|
Information about the processed file is written in the job output.
|
|
|
| WRC0392
|
Format:
FileFormat
|
Information about the processed file is written in the job output.
|
|
|
| WRC0393
|
Records processed:
x
|
Information about the processed file is written in the job output.
|
|
|
| WRC0394
|
Skip factor:
SkipFactor
|
Information about the processed file is written in the job output.
|
|
|
| WRC0395
|
Unknown syntax was found in the input file at row
StatementNumber.
|
Unexpected syntax has been found in the input file for the DB2 Catalog Synchronization phase.
|
Check the syntax listed in the
Data Model Guide.
|
DB2 Catalog Synchronization
|
| WRC0396
|
Unable to retrieve the file image
FileImage.
|
An internal error occurred during processing of the phase.
|
Check previous messages for more information.
|
File-copybook relationship analysis
|
| WRC0397
|
File
File-Library-Name.
FileName does not contain information for the field. The file was discarded.
|
Field level information is missing in the file interface.
|
Check the syntax of the interface in the
Data Model Guide.
|
File loading
|
| WRC0398
|
The copybook library
Copybook-Library-Name contains invalid characters.
|
The copybook name specified in the interface is incorrect.
|
Check the syntax of the interface in the
Data Model Guide.
|
File loading
|
| WRC0399
|
A copybook name is required for copybook library
Copybook-Library-Name.
|
The copybook name specified in the interface is incorrect.
|
Check the syntax of the interface in the
Data Model Guide.
|
File loading
|
