|
|
|
The following messages are issued by the CA Earl component.
Reason:
The RECORD= clause of the SEGMENT file statement has a larger value than that on the DB statement.
Action:
Specify the RECORD= length on the DB statement equal to or greater than the length of the largest segment.
Reason:
Modify supplied defaults to your requirements.
Action:
Modify desired options and press PF2 to generate installation options.
Reason:
The installation options macro has been successfully assembled with the user specified options.
Action:
No action is required.
Reason:
The assembly of program ended with a return code of rc.
Action:
Examine the listing, correct the error, and reexecute the task.
Reason:
A GLOBAL command involving TXTLIB(s) ended with a return code of rc.
Action:
Check that the named TXTLIB(s) exists and reexecute the task.
Reason:
The CMS command TXTLIB function library program ended with a return code of rc.
Action:
Verify that there is enough space in the TEST system disk and retry this task. For assistance, contact CA Support at http://ca.com/support.
Reason:
The named TEXT file or TXTLIB member does not exist, or one or more unresolved external references were found.
Action:
Verify that the named TEXT or TXTLIB member exists, that other TXTLIBs exist in the accessed disks and are specified in any GLOBAL TXTLIB commands and reexecute the task. For assistance, contact CA Support at http://ca.com/support.
Reason:
An error occurred while generating the file specified by filename and filetype.
Action:
Examine the listing, correct the error, and regenerate the task.
Reason:
An error occurred copying the file specified by filename and filetype.
Action:
Verify that the named file exists and that the target disk has sufficient free space and reexecute the task. For assistance, contact CA Support at http://ca.com/support.
Reason:
Task taskname has completed successfully.
Action:
No action is required.
Reason:
Modify-supplied defaults to your requirements.
Action:
Modify desired options and press PF2 to execute the installation demonstration program.
Reason:
A return code greater than zero was returned from the execution of the CA Earl demonstration program.
Action:
Review the SYSPRINT output and consult the CA Earl Message Guide for any error messages. Take the appropriate actions to correct the error and rerun the demonstration. If task errors still occur, then verify that all CA Earl installation tasks were completed successfully.
Reason:
The CA Earl demonstration was successful. A return code of zero was returned from the execution of the CA Earl demonstration program.
Action:
No action is required.
Reason:
CA Earl could not find the named source program, MACLIB, or TXTLIB on any of the accessed disks.
Action:
Correct the spelling of the file information or access the required disk.
Reason:
The specified option is invalid.
Action:
Check that the option specified is spelled correctly and that it exists. See the CA Earl Systems Programmer Guide OS/390 for valid options and their syntax.
Reason:
A supplied filemode is invalid for one of the following reasons:
Action:
Correct the filemode.
Reason:
Conflicting parameters were specified.
Action:
Specify only one of the indicated parameters. Refer to the CA Earl Systems Programmer Guide for valid options and their syntax.
Reason:
The indicated user exit was not found.
Action:
Check the following:
Reason:
A return code, nnnn, was returned from the user exit name.
Action:
Correct the indicated error and reexecute the CAEARL EXEC.
Reason:
A TXTLIB command failed while saving a CA Earl program. The message text contains the member name, TXTLIB name, function, and return code rc.
Action:
Examine the CA Earl listing, correct the error, and reexecute the CAEARL EXEC. For assistance, contact CA Support at http://ca.com/support.
Reason:
A return code greater than zero was returned while executing CAEARL.
Action:
Review the SYSPRINT output from CA Earl and consult the CA Earl Message Guide for any error messages listed. Take the appropriate actions to correct all errors, and then reexecute CAEARL.
Reason:
The string literal following the PARM= keyword is invalid for one of the following reasons:
Action:
Shorten the literal, add a closing quote, or specify two quotes ('') to indicate a single quote in the middle of your string.
Reason:
You omitted the name of your CA Earl source program when invoking CAEARL EXEC. The correct syntax is:
CAEARL program-name (options
Action:
Correct the syntax and reexecute CAEARL.
Reason:
You omitted MACLIB or TXTLIB following the options MACLIB, TXTLIB, or SAVE.
Action:
Correct the syntax and reexecute CAEARL.
Reason:
The named file is required for the SQLDS interface, but CA Earl could not find it on any of the accessed disks.
Action:
Access the SQLDS files.
Reason:
The DISK keyword must be preceded by AFP, SYSEARL, or SYSPRINT, as specified.
Action:
Correct the syntax and reexecute CAEARL.
Reason:
The CA Earl program has been terminated by a user-directed branch to ABORT.
Action:
No action is required.
Reason:
No data has been selected to the hit file for any report of this run. The run is terminated at this point.
Action:
Check the record selection logic and input data and resubmit.
Reason:
No data has been selected to the hit file for report number nn.
Action:
Check the record selection logic for report number nn and resubmit.
The CALR804E message is issued by CA Earl when a file exit routine indicates that it cannot continue processing due to a fatal error. File exit routines are distributed with CA Earl, other products, or can be user-written. The file exit routine supplies the text of the message. The following CALR804E messages are issued by file exit routines distributed with CA Earl.
Reason:
An error has occurred during the execution of module xxxxxxx, which was called by CA Earl. Message yyyyyyyy is passed back from the user module.
The module can be:
Action:
Reason:
Bytes 1 to 4 of the CA Earl I/O area do not contain a valid function code. This is issued by the DL/I interface CAEADLI.
Action:
Correct and resubmit.
Reason:
The first character of the function field code is not G. This was issued by the DL/I interface CAEADLI.
Action:
Check for an incorrect function code.
Reason:
Bytes 5 to 6 of the CA Earl I/O area contain a value not in the range of 0 to 10 or not packed decimal. This was issued by the DL/I interface CAEADLI.
Action:
Modify the User Exit source code and reassemble if more than 10 SSAs are required.
Reason:
The number of SSAs supplied in bytes 15 to 255 of the CA Earl I/O area does not match the value specified in bytes 5 to 6. This was issued by the DL/I interface CAEADLI.
Action:
Correct and resubmit.
Reason:
The DL/I call is not successful—the status code returned is prefixed by A (AB, AC, AD, AF, and so forth). This could either be a genuine I/O error or a logical error in setting up the arguments within the CA Earl problem definition statements. This was issued by the DL/I interface CAEADLI.
Action:
See the IBM DL/I or IMS manual and take the appropriate action for this code.
Reason:
The PCB number specified in bytes 7 to 8 of the CA Earl communications region is not in the range 1 to 255. This was issued by the DL/I interface CAEADLI.
Action:
Correct and resubmit.
Reason:
The database name specified in bytes 7 to 14 of the communications region cannot be matched against any of the supplied PSB. This was issued by the DL/I interface CAEADLI.
Note: The PSB must be generated for assembler or COBOL.
Action:
Check the database name against the PSB.
Reason:
This message is issued if a wrong combination of DEFINE parameters has been specified. This will be followed by a CA Earl abort message, and the run will abort. This was issued by CAEAVSAM.
Action:
Correct the call to CAEAVSAM.
Reason:
aaaaaaaa indicates whether it is a generation error, an open error, or a read error.
Action:
See the relevant IBM manual for an explanation of the content of Register 15 and error code.
Related IBM Publication:
Reason:
CA Earl is unable to continue due to errors.
Action:
See the accompanying message on the listing and take the appropriate action.
Reason:
The name of a DB or the defined PCB number is not in the PSB.
Action:
Match the names of DB statements and PCBs.
Reason:
The Report Writer has found a record containing a report number that either is larger than the number of reports or is out of sequence.
Action:
Check for files overlapping the hit file extents or for failure of the sort.
Reason:
The record size of the hit file is greater than the track capacity of the device to which it has been assigned.
Action:
Move the hit file to a device with a larger track capacity or reduce the amount of data to be written in the hit file record.
Reason:
Your CA Earl program contains a CALL, GET, or OPTION PRTXIT= statement that references the module or phase named xxxxxxx, and this module or phase cannot be found.
Action:
Make sure that your STEPLIB DD statement points to the appropriate library. If necessary, point to an additional library or assemble and link edit the module into the appropriate library.
Reason:
CA Earl has read data from its work file, which it did not expect.
Action:
Check for overlapping files. For assistance, contact CA Support at http://ca.com/support.
Reason:
CA Earl detected a program interrupt (usually a data problem) at the indicated statement on input record number nnnn. Processing continues.
Action:
No action is required.
Reason:
More than one qualified segment on the same level allowed only for a fully-qualified GET without the SEARCH function.
Action:
Specify two GET statements if a search for two segments at the same level is required.
Reason:
In the first two bytes of this variable-length segment is a length greater than the defined maximum length for the database.
Action:
Specify a record size on the DB statement equal to the length of the longest segment.
Reason:
DL/I has returned a status code nn that CA Earl cannot handle.
Action:
See the IBM DL/I or IMS manual and take the appropriate action for this code.
Reason:
File EARLOBJ does not contain the CA Earl program or is corrupted.
Action:
Check for overlapping files or verify that the correct text deck has been copied in (if using EARLX).
Reason:
The CA Earl copy library is corrupt.
Action:
Restore from backup.
Reason:
The hit file has been assigned to an unsupported device, or the DISK= parameter of the EARLGEN macro, OPTION statement, or FILE statement is for an unsupported device.
Action:
Move the file to a supported device.
Reason:
A user-supplied exit routine has program checked.
Action:
Resolve the problem by using the registers and PSW saved by CA Earl.
Reason:
CA Earl could not open its files.
Action:
Check for missing or incorrect files.
Reason:
Either the record length of the data was not in the range of four to maximum record size, bytes 3 and 4 of the record descriptor were not zero, or CA Earl source statements are stored in variable-length files or copybooks.
Action:
Ensure that the file contains variable records and specify the maximum record length on the FILE statement, or save the CA Earl source statements in a fixed-length file with an LRECL of 80.
Reason:
The partition or region is too small.
Action:
Allocate more storage.
Reason:
The partition or region is too small.
Action:
Allocate more storage.
Reason:
A program check has occurred during CA Earl execution.
Action:
Check your console or JES2 log for system error messages that could have caused a CA Earl program check. Also refer to the CA Earl User Guide for debugging hints and suggestions.
For assistance, contact CA Support at http://ca.com/support.
Reason:
A block has been read on file xxxxxxxx and it is either larger than the BLOCK= value on the FILE statement or is not a multiple of the record size.
Action:
Correct the FILE statement if the BLOCK= value is too small or rewrite the file with the correct record size.
Reason:
A user file module has requested that CA Earl terminate.
Action:
See the accompanying message CALR804E for the reason.
Reason:
The Record length on the FILE statement is not equal to key length plus data length for unblocked ISAM records.
Action:
Correct the RECORD= parameter on the FILE statement.
Reason:
The DISK= parameter of the FILE or OPTION statement does not support ISAM.
Action:
Specify the correct DISK type on the FILE statement.
Reason:
A hardware error has been encountered.
Action:
Check for overlapping files and bad disk drives. Restore the file.
Reason:
A record read from an ISAM file is not the length specified on the FILE statement.
Action:
Check the file specification and check for overlapping files.
Reason:
The expected record was not found.
Action:
Ensure that the file was closed after the last update. Restore the file and rerun.
Reason:
The region is too small. CA Earl requires at least 260K. A large source program may require more storage, and CA Earl runs faster when given a larger region.
Action:
Increase the storage available to CA Earl. If attempting to compile a large program, specify OPTION WORKFILES.
Reason:
There is a program check in the compiler, object module, generator or Report Writer.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The hit file is out of sequence.
Action:
Check the sort for failure and overlapping files.
Reason:
There is insufficient storage for the report writer.
Action:
Run the program in a larger partition or region.
Reason:
The invoked sort has failed.
Action:
Check for overlapping extents or insufficient work areas.
Reason:
The FILEDEF for SORTOUT has been omitted or has failed.
Action:
Ensure that the FILEDEF for SORTOUT is issued before invoking CA Earl.
Reason:
The key specified by the user on the FILE VSAM statement does not match the values returned by OPEN.
Action:
Match the values specified on the FILE statement with those in the catalog.
Reason:
The record size on the FILE VSAM statement does not match the size returned by OPEN.
Action:
Match the RECORD= parameter on the FILE statement with that in the VSAM catalog.
Reason:
The user is trying to add records to a VSAM file while reading backwards or in ADR mode using the RBA.
Action:
Insert records by key or in sequential mode.
Reason:
A VSAM call has been terminated by VSAM. The contents of Register 15 and the reason code are given in the message.
Action:
Correct the error referencing the IBM VSAM Messages and Codes Manual for the reason code.
Reason:
In the definition of the database (DB-statement), the defined MAXLN is less than the longest segment in the PCB used for this database.
Action:
Change the MAXLN parameter to the correct value.
Reason:
It is impossible to hold more than one position for the same PCB. This would happen if two GETs for the same PCB are active at the same time. Two different PCBs for this database should be used if more than one position in the database is needed.
Action:
Specify another DB statement for the same database and refer to that on the second GET statement.
Reason:
In a GET statement, with the SEARCH function, the segments defined are not in the same hierarchical path.
Action:
Specify segments in only one hierarchical path.
Reason:
The same segment name appears twice in a GET.
Action:
Correct and resubmit.
Reason:
The filename shown does not conform to the standards of CMS for DDnames.
Action:
See the CMS manuals for the standards for DDnames.
Reason:
An ENDPROC statement has been executed and there is no return address in the stack.
Action:
Check for branches to labels defined within procedures from outside the procedure.
Reason:
A PERFORM statement is being executed and there is no room for the return address in the stack.
Action:
Check for recursive PERFORM loops and branches from within procedures to labels defined outside the procedure. Also check for GOTOs within PROCs. The only way to exit from a PROC prior to its ENDPROC statement is an EXITPROC.
Reason:
AFP could not be initialized due to some type of major error.
Action:
Ensure the following:
Reason:
AFP could not print the line you sent.
Action:
Review the AFP error messages to determine the cause of your problem.
Reason:
CA Earl could not connect to SQL/DS due to some type of major error.
Action:
Correct the userid and password in SYSPARM and rerun the job.
SQL filename SQL function ISSUED
SQL FLAG:-SQLCODE hex_value decimal_value
SQL FLAG:-SQLERRM IS: error message from SQL up to 70 characters
Limits: 8 characters
Limits: SELECT, FETCH
Reason:
An error occurred during query transmission to SQL.
Action:
Examine the SQL error message and SQLCODE to determine the cause and correct the problem. For more information about SQL error codes, refer to your SQL documentation.
SQL filename COLUMN NAME IS: name
SQL filename CAEARL NAME IS: name
Limits: 18 characters
Reason:
The data type specified on the CA Earl DEFINE statement does not match the data type stored in the SQL tuple.
Action:
Correct your CA Earl program so that the data types match.
SQL filename SQL FAILURE IN function
SQL FLAG:-ERRCODE = errcode
Limits: 8 characters
Limits: CONNECT, SELECT, FETCH, DISCONNECT, DATATYPE
Limits: One byte hex value
Reason:
An error occurred in SQL processing.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
A userid and password are required to connect to SQL/DS under VSE.
Action:
Specify the correct userid and password in SYSPARM and rerun the job.
Reason:
The syntax of userid and password was incorrectly specified.
Action:
Correct the syntax of userid and password and rerun the job.
Reason:
There was insufficient memory to execute SQL commands.
Action:
Increase memory and rerun the job.
SQL filename SQL function ISSUED
SQL FLAG:-ERRCODE hex_value decimal_value
Limits: 8 characters
Limits: CONNECT, DISCONNECT, SELECT, FETCH
Reason:
CA Earl could not connect to DB2 due to some type of major error.
Action:
Examine the R0 failure code to determine the cause and correct the problem.
For assistance, contact CA Support at http://ca.com/support.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |