| ARI0950E | INPUT keyword keyword is not valid. |
Explanation: The submitted control statement keyword is unrecognized. The recognized trace formatter control statement keywords are: AGENTNO, COMP, DATE, DISK, DUMPALL, HEADER, RETCODE, SUBCOMP, TIME, TRACENO, and USERID.
System Action: The program ends.
Programmer Response: Select the correct control statement keyword. Each control statement can contain only one keyword.
| ARI0951E | Number of parameters in user ID exceeds six. |
Explanation: The maximum number of parameters used with the control statement keyword USER ID is six.
System Action: The program ends.
Programmer Response: Reduce the number of parameters to six or less. For more information about USER ID parameters, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0952E | Number of parameters in AGENTNO exceeds six. |
Explanation: The maximum number of parameters used with the control statement keyword AGENTNO is six.
System Action: The program ends.
Programmer Response: Reduce the number of parameters to six or less. For more information about AGENTNO parameters, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0953E | Nondigit character in one of the AGENTNO parameters. |
Explanation: Syntax error. At least one of the parameters used with the control statement keyword AGENTNO contains nonnumeric characters.
System Action: The program ends.
Programmer Response: Submit the parameters with the correct syntax. For more information about AGENTNO parameters, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0954E | Number of parameters in TRACENO exceeds six. |
Explanation: The maximum number of parameters used with the control statement keyword TRACENO is six.
System Action: The program ends.
Programmer Response: Reduce the number of parameters to six or less. For more information about TRACENO parameters, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0955E | Nondigit character in one of the TRACENO parameters. |
Explanation: Syntax error. At least one of the parameters used with the control statement keyword TRACENO contains nonnumeric characters.
System Action: The program ends.
Programmer Response: Submit the parameters with the correct syntax. For more information about TRACENO parameters, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0956E | Number of parameters in COMP exceeds one. |
Explanation: The maximum number of parameters used with the control statement keyword COMP is one.
System Action: The program ends.
Programmer Response: Enter only one of the allowed parameters: CONV, DBSS, DRRM DSC, RA, RDS, WUM, or STG.
| ARI0957E | Parameter in COMP not valid. |
Explanation: The parameter specified with the control statement keyword COMP can be CONV, DBSS, DRRM DSC, RA, RDS, WUM, or STG.
System Action: The program ends.
Programmer Response: Submit the correct parameter: CONV, DBSS, DRRM, DSC, RA, RDS, WUM, or STG.
| ARI0958E | Number of parameters in SUBCOMP exceeds eight. |
Explanation: The maximum number of parameters used with the control statement keyword SUBCOMP is eight.
System Action: The program ends.
Programmer Response: Reduce the number of parameters to eight or less. For more information about SUBCOMP parameters, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0959E | Parameter in SUBCOMP not valid. |
Explanation: At least one of the parameters used with the control statement keyword SUBCOMP is not valid. The allowable parameters for the subcomponents DBSS, DRRM, DSC, RA and RDS are:
For RDS: For DBSS: For DSC: For RA:
AU DC AGENT RA
AG DM COM COM
EXEC ENTRY
INT EXIT
OPT INDEX For DRRM:
PA LOCK
SG LOG DICT
LUW GEN
SORT PARSE
STAT RDIIN
STOR
System Action: The program ends.
Programmer Response: Submit the correct parameters. For more information about SUBCOMP parameters, refer to the DB2 Server for VSE & VM Operation manual.
| ARI0960E | Number of parameters in DATE exceeds two. |
Explanation: The maximum number of parameters used with the control statement keyword DATE is two.
System Action: The program ends.
Programmer Response: Input the two parameters 'start-date' and 'end-date' or the parameter 'target-date'.
| ARI0961E | Syntax error in one of the DATE parameters. |
Explanation: Syntax error. Each portion of the date must be specified as two digits; that is, a leading zero must be entered where needed. The delimiter must be /. The second date, if used, must be greater than the first date. An example of correctly specified dates is: DATE 01/23/85 02/08/85.
System Action: The program ends.
Programmer Response: Submit the parameters with the correct format.
| ARI0962E | Nondigit character in one of the DATE parameters. |
Explanation: Syntax error. At least one of the parameters used with the control statement keyword DATE contains nonnumeric characters. Each portion of the date must be specified as two digits; that is, a leading zero must be entered where needed. The second date, if used, must be greater than the first date. An example of correctly specified dates is: DATE 01/23/85 02/08/85.
System Action: The program ends.
Programmer Response: Submit the parameters with the correct syntax.
| ARI0963E | Number of parameters in TIME exceeds two. |
Explanation: The maximum number of parameters used with the control statement keyword TIME is two.
System Action: The program ends.
Programmer Response: Input the two parameters 'start-time' and 'end-time' or the parameter 'target-time'.
| ARI0964E | Syntax error in one of the TIME parameters. |
Explanation: Syntax error. Each portion of the time must be specified as two digits; that is, a leading zero must be entered where needed. The delimiter must be a colon (:).
Note: The second time specified should be greater than the first time. For example, specifying TIME 23:45:00 00:10:00 will cause no trace output to be selected (no warning message will be issued). Consequently, specifying an interval that passes through midnight must be done in two different runs of the trace formatter. An example of correctly specified times is: TIME 09:05:00 14:04:59. It is possible (but not very useful) to specify only one time with the TIME keyword. For example, TIME 12:00:00 specifies that only the trace records created during that second of time be formatted.
System Action: The program ends.
Programmer Response: Submit the parameters with the correct syntax.
| ARI0965E | Nondigit character in one of the TIME parameters. |
Explanation: Syntax error. At least one of the parameters used with the control statement keyword TIME contains nonnumeric characters. Each portion of the date must be specified as two digits; that is, a leading zero must be entered where needed. The delimiter must be ':'.
Note: The second time specified should be greater than the first time. For example, specifying TIME 23:45:00 00:10:00 will cause no trace output to be selected (no warning message will be issued). Consequently, specifying an interval that passes through midnight must be done in two different runs of the trace formatter. An example of correctly specified times is: TIME 09:05:00 14:04:59. It is possible (but not very useful) to specify only one time with the TIME keyword. For example, TIME 12:00:00 specifies that only the trace records created during that second of time be formatted.
System Action: The program ends.
Programmer Response: Submit the parameters with the correct syntax.
| ARI0966E | Number of parameters in RETCODE exceeds one. |
Explanation: The maximum number of parameters used with the control statement keyword RETCODE is one.
System Action: The program ends.
Programmer Response: Enter only one of the allowed parameters (P, N, or *).
| ARI0967E | Parameter in RETCODE not valid. |
Explanation: The submitted parameter used with the control statement keyword RETCODE is not valid. The parameter must be P, N, or *.
System Action: The program ends.
Programmer Response: Enter one of the following as the RETCODE parameter:
| ARI0968E | The trace file does not contain trace data. |
Explanation: The mounted tape or disk file does not contain the DB2 Server for VSE trace data. (The wrong tape may be mounted.)
System Action: The program ends.
Programmer Response: Ensure that the operator mounted the correct tape and that the correct JCL was submitted for the trace file. If the correct file is being accessed, it does not contain the trace data. (The tape is probably empty or rewritten.)
| ARI0969I | Trace file is empty. |
Explanation: The DB2 Server for VSE trace formatter program has detected that the DB2 Server for VSE trace file is empty. (It contains no records.) When database manager activity was being traced, no trace output data was created.
System Action: The program ends.
Programmer Response: None required. You may want to verify that the correct file was submitted as input to the trace formatter program.
| ARI0972E | Storage allocation error. Return Code = nn . |
Explanation: In allocating virtual storage during trace formatting, a VSE GETVIS macro failure occurred. The cause of the error is described by the Return Code value nn (which is the return code from GETVIS).
System Action: The program ends.
Programmer Response: Report the problem to your system programmer.
System Programmer Response:
|
| ARI0973E | Error releasing storage. Return Code = nn . |
Explanation: In releasing virtual storage during trace formatting, a CMS free storage macro |failure occurred. The cause of the error is described by the Return |Code value nn (which is the return code from the free storage |macro).
|System Action: The program ends.
|Operator Response: Report the problem to your system programmer.
|System Programmer Response: Make a record of the return code and contact the designed support group for |your installation.
| ARI0974E | operation error on DDNAME xxxxxxxx . Return Code = nn . EREASON= nn . |
Explanation: An error occurred during a sequential input/output operation on the xxxxxxxx file.
The Return Code value is the Primary Error Code value. The EREASON value is the Secondary Error Code value. For further explanation, look up the displayed error codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.
System Action: The program ends.
Operator Response: Return console output with the output listing.
System Programmer Response: For corrective action, look up the displayed error codes under either Chapter 20, Sequential File Errors, or "SEQ FILE ERRORS" in the HELP text.