Informative Messages

Messages › CA IDMS Log Analyzer Messages › Informative Messages

Informative Messages

CA IDMS Log Analyzer Informative Messages are prefixed by an Innn number. The following list provides an explanation of each message.

I001 Log Analyzer started/ended date & time

Reason:

The starting/ending date and time of CA IDMS Log Analyzer processing are displayed.

Action:

None.

I002 INPUT PARAMETER STATEMENT statement

Reason:

The parameter statement as read is displayed.

Action:

None.

I003 PROCESSING OPTIONS options

Reason:

The processing options as interpreted by CA IDMS Log Analyzer are displayed.

Action:

None.

I004 ARCHIVE RECORDS WILL BE PROCESSED FOR report type

Reason:

The report types for which archive records are to be processed are displayed.

Action:

None.

I005 EXTRACT PROCESSING started/ended date & time

Reason:

The starting/ending date and time of the extract phase of CA IDMS Log Analyzer are displayed.

Action:

None.

I006 ARCHIVE RECORDS PROCESSED FOR THIS TYPE log-record-type count

Reason:

A count of archive records of a specific type on the Archive Log File is displayed.CA IDMS Log Analyzer reports on the task and transaction statistic records. Check the STATISTICS parameter of your central version (CV) sysgen if your CA IDMS Log Analyzer Audit Report does not show I006 messages for record types 6-02 and 6-03.

Action:

None.

I007 TOTAL ARCHIVE RECORDS PROCESSED count

Reason:

A count of archive records on the log archive file is displayed.

Action:

None.

I008 EXTRACT RECORDS WERE CREATED FOR report-type count

Reason:

A count of extract records created for a specific report type is displayed.

Action:

None.

I009 TOTAL EXTRACT RECORDS CREATED count

Reason:

A count of extract records created is displayed.

Action:

None.

I010 REPORT PROCESSING started/ended date & time

Reason:

The starting/ending date and time of the report phase of CA IDMS Log Analyzer are displayed.

Action:

None.

I011 REPORT WAS CREATED FOR YOUR PARAMETER parameter

Reason:

The report options selected for a specified report request are displayed. Your options, as well as the defaults supplied by CA IDMS Log Analyzer are included with this message.

Action:

None.

I012 PARAMETER PROCESSING TOTALS category count

Reason:

A count of parameter statements processed of a specific category is displayed.

Action:

None.

I013 TOTAL RECORDS ADDED TO THE BILLING FILE count

Reason:

A count of the Billing Records that were created as a result of a REPORT=BILLING request(s) is displayed. This count should be equal to the sum of the counts of type 6-28 and type 6-34 (CA ADS dialogs) records.

Action:

None.

Two types of errors can be reported by the return codes of n1, n2, n3, and n4--non-VSAM file errors and VSAM file errors. The error is described by n2 and n4. For VSAM file errors, n4 is always equal to 28. The error is described by n1, n2, and n3. A general return code is given by n4 for both non-VSAM and VSAM errors. All return codes are decimal values.

Return Codes:

n4	Reason	Action
4	End-of-file	Call Product Support.
8	Open error or file is not open	Look for JCL errors or for the use of improper files.
12	An I/O error has occurred	Find cause for I/O error.
16	Request not recognized	Call Product Support.
20	File was already opened	Call Product Support.
24	Parameter list error	Call Product Support.
28	VSAM error n1=R15 return code from VSAM n2=low order byte from R0 GENCB/MODCB type of error n3=VSAM feedback byte error in I/O request	Use n1, n2, and n3 to check for possible user errors. If there are no user errors, call Product Support.
32	Insufficient storage	Increase storage for job step.
36	SYNAD error occurred n1=byte 1 of DECB n2=byte 2 of DECB N3=byte 3 of DECB	For BDAM files.
40	BPAM FIND error n1=R15 n2=R0	Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors.
44	BPAM STOW error n1=R15 n2=0	Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors.
n2	Reason	Action
0	n4=8, use of unopened file n4=24, parameter list error	Call Product Support. Call Product Support.
1	JCL/label overrode parm list	Remove DCB information from JCL and ensure that the correct files are referenced.
2	Parm list overrode JCL/label	Remove DCB information from JCL and ensure that the correct files are referenced.
3	Unrecognized request	Call Product Support.
4	OS x13 ABEND trapped at open	Fix cause for x13 ABEND.
5	Tried to update seq. file	Call Product Support.
6	VSAM write at other than load	Call Product Support.
7	SOS table could not expand	Call Product Support.
8	OS DCB open failed	Call Product Support.
9	SOS table buffer pointer lost	Call Product Support.
10	SOS table file CB not built	Call Product Support.
11	OS DD statement Missing	Supply missing DD statement.
12	VSAM ACB open failed	Call Product Support.
13	Record format invalid	Call Product Support.
14	Macro format invalid	Call Product Support.
15	Record length not numeric	Call Product Support.
16	Record length too large	Call Product Support.
17	Block size not numeric	Call Product Support.
18	Block size too large	Call Product Support.
19	Invalid DOS sysname table	Assemble a valid sysname table.
20	DOS sysname table entry missing	Assemble a sysname table with an entry for the missing one.
21	DOS LU number too large	Use an LU number within range.
22	DOS sysname is not numeric or is misspelled	Correct to a valid sysname.
23	DOS sysname blank	Do not use blank sysname.
24	DOS LU not assigned	Call Product Support.
25	DOS DTF prototype missing	Call Product Support.
26	DOS logic module missing	Generate missing logic module.
27	DOS CCW mismatch	Call Product Support.
28	File is not a PDS	Allocate file to a PDS.