Reason:
This message indicates that the library file condense operation is complete.
Action:
None.
Reason:
Normal end of processing is indicated. The times indicate the duration of this run.
Action:
None.
Reason:
No more space is available in the library.
Action:
Condense the library. If the error persists, create a larger library.
Reason:
(DL/I) The DL/I call was not successful. The status code (xx) returned is prefixed with an A (for example: AB, AC, AD, AF, and so on).
Action:
Determine the error condition by referencing the proper IBM publication and rerun.
Reason:
The call name specified on the CALL command could not be found in the library. It may have been misspelled.
Action:
Check the name for errors and resubmit.
Reason:
(CA Datacom/DB, CA Dataquery DQF FILE) One of the parameters in the Communications Area has exceeded its maximum possible length. The following shows each possible parameter and its associated maximum length.
8
8
15
9
Action:
Enter the correct length of the parameter(s).
Reason:
(DL/I) The 8-byte alphanumeric database name (xxxxxxxx) in bytes 7 through 14 of the Communications Area was not found in the PCB address list. Upon entry to the CA Datacom/DB Reporting Facility from DL/I, register 1 points to 1 to 8 PCB addresses in a list. If the PCB address needed to process the request is deeper in the list than 8, the required database may be specified with a 2-byte packed decimal number in bytes 7 through 8 of the Communications Area. This number (in the range of 1 through 255) specifies the relative number of the address within the list to properly address the PCB.
Action:
Enter the correct database name.
Reason:
(DL/I) The relative PCB number (xxx) specified in bytes 7-8 of the Communications Area is not in the range 1 through 255.
Action:
Enter the correct PCB number.
Reason:
(CA Datacom/DB, CA Dataquery DQF FILE) The name of the pre-cataloged communication module was either omitted from the FILE/INPUT statement or exceeded the eight-character limit. This parameter is required on the first CA Datacom FILE statement processed. Subsequent FILE statements may optionally specify the parameter.
Action:
Enter the correct communication module name.
Reason:
(CA Datacom/DB, CA Dataquery DQF FILE) The return code (rr) describes the reason for the failure during the CA Datacom/DB command xxxxx, with zzzzzzz representing the sequential count of the number of calls to CA Datacom/DB. This count can be used to determine the number of successful calls to CA Datacom/DB prior to the abend condition.
Action:
See CA Datacom/DB Return Codes for an explanation of the return code.
Reason:
(DL/I) The first character of the function code xxxx in bytes 1 through 4 of the I/O area is not G.
Action:
Enter the correct function code.
Reason:
(CA Dataquery DQF FILE) The CA Datacom/DB return code (rr) describes the reason for failure.
Action:
See CA Datacom/DB Return Codes for an explanation of the return code.
Reason:
(CA Datacom/DB) The CA Datacom/DB command in positions 1 through 5 of the I/O area has been modified to something other than one of the 12 valid CA Datacom/DB Reporting Facility commands since the last call.
Action:
Change the command to GSETL, GETIT, REDKY, REDNX, REDNE, REDLE, REDID, LOCKY, LOCNX, LOCNE, LOCKX, or LOCNK.
Reason:
During a GETVIS or GETMAIN request, an insufficient amount of space was found to process your PUNCH request.
Action:
Rerun the job in a larger region or partition/virtual machine.
Reason:
During a GETVIS or GETMAIN request, an insufficient amount of space was found to process the internal index sort.
Action:
Rerun the job in a larger region or partition/virtual machine.
Reason:
(CA Datacom/DB, CA Dataquery DQF FILE) An internal processing error has occurred within the interface program, with xxxxx describing the failure.
Action:
Contact CA Support and provide a listing and dump. For information about contacting CA Support, see Troubleshooting.
Reason:
The specified name did not start with A through Z, included a letter other than A through Z, or was over eight characters in length.
Action:
Correct the name.
Reason:
(VSAM) An incorrect combination of DEFINE parameters was specified.
Action:
Ensure that the DEFINE parameters are properly specified.
Reason:
(CA Datacom/DB) The CA Datacom/DB command (xxxxx) in positions 1 through 5 of the I/O area is not one of the 12 CA Datacom/DB Reporting Facility commands.
Action:
Change the command to GSETL, GETIT, REDKY, REDNX, REDNE, REDLE, REDID, LOCKY, LOCNX, LOCNE, LOCKX, or LOCNK.
Reason:
The parameter specified was not LOAD, CONDENSE, DELETE, DISPLAY, INDEX, or PUNCH. Perhaps you misspelled one.
Action:
Correct any misspellings and resubmit the job.
Reason:
(CA Datacom/DB, CA Dataquery DQF FILE) The I/O area defined with the RECORD= parameter was not large enough to contain the requested element(s), and CA Datacom/DB has overlayed some of Reporting Facility's internal work areas. Continuation would cause unpredictable results.
Action:
Increase the record length and rerun.
Reason:
(CA Dataquery) The RECORD= parameter was found to be too small before any data was moved.
Action:
Increase the record length and rerun.
Reason:
This message indicates that library maintenance is complete.
Action:
No action required.
Reason:
SYSIPT/SYSIN END-OF-FILE or the END card was read before any library commands were processed.
Action:
Ensure the end of the deck was not dropped.
Reason:
A CA Datacom/DB Reporting Facility keyword was encountered before the end of processing.
Action:
Check the sequence of parameters in your library run. Remember no other type of processing is allowed while in library mode.
Reason:
(CA Dataquery DQF FILE) Member xxxxxxxx was not found.
Action:
Enter the correct member name.
Reason:
The module named was not found.
Action:
Check the name for accuracy and resubmit it.
Reason:
During the load to the library, a member was specified which had data included.
Action:
Make sure the cards required for each member to be loaded are available and that the end of the deck was not dropped.
Reason:
(DL/I) Bytes 1 through 4 of the file I/O area are blank.
Action:
Enter the function code.
Reason:
Information only. The number of records currently on file is displayed.
Action:
None.
Reason:
(DL/I) Bytes 5-6 of the file I/O area contain a value of less than 0, greater than 10, or the file I/O area is not in packed decimal format.
Action:
Put in the correct value or put the value in packed decimal format.
Reason:
This message is associated with the message Z1173E. This is an information message that indicates where in the dump the PSW and general registers 0 through 15 have been saved.
Action:
Supply this information when you contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
(CA Datacom/DB, CA Dataquery DQF FILE) Either END-OF-FILE has been previously reached, or a fatal abend condition was detected, causing the Reporting Facility to deny further access of the file, but another GET was encountered for that file.
Action:
Check for loops in the program logic and rerun. If the problem persists, contact CA Support. For information about contacting CA Support, see Troubleshooting.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|