Appendix A. MESSAGES › Messages
Messages
This appendix lists all messages that are generated by
CA MICS Accounting and Chargeback and printed in the MICSLOG
data set. Some messages are generated during the processing
of the control statements, while others are caused by various
conditions in the data. The messages are listed in ascending
numerical sequence and include the full text of the message,
the type, the reason for the message, appropriate user
action, and applicable document references.
The following type codes are used to categorize the messages:
Information A note to the user that documents an
Accounting and Chargeback option or
potentially important feature in the data.
Warning A condition of either the data or the
control statements that does not affect
the Accounting and Chargeback operation but
that may lead to unexpected results.
Error A problem with a control statement that
will prevent a successful run of the
product. Execution is stopped after all
control statements are processed.
Termination A critical problem with the data that
requires the product to terminate
processing immediately.
The message texts often include references to information
contained in a control statement, or values of variables from
temporary Accounting and Chargeback work files. In these
cases, the message text contains a blank line indicating that
a value will be substituted into the text at execution time.
For example, message ACT00108 reads as follows:
THE PANEL DEFINED STARTING DAY OF THE WEEK
IS INVALID. THE INVALID DAY VALUE IS:
______________.
+----------+
| ACT00100 |
+----------+
TEXT: GENERATION PROCESS COMPLETED
TYPE: Information
REASON: The generation process has successfully
completed.
ACTION: None
REFERENCES: None
+----------+
| ACT00101 |
+----------+
TEXT: EITHER NO TYPE D ROW WAS FOUND IN THE ACTACT
TABLE OR DISCOUNT TYPE _________ IS INVALID.
DISCOUNT = 0 GENERATED.
TYPE: Error
REASON: The TYPE D, or discount, row of the ACTACT table
was not found or the discount type displayed in
the message is invalid.
ACTION: This message refers to volume discounting. The
valid discount types are:
ACCUMULATIVE
MAXIMUM
PIECEWISE
Review the references below and determine the
correct specifications needed for the type of
discounting desired. Reenter the required
specifications and rerun the job. If the
discount type is specified correctly, or if the
error persists, contact CA Technical Support for
assistance.
Note: Lump sum discounts and fixed percentage
discounts are not valid options here.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.9.1, Specifying Volume Discounts, and
Section 4.9.3, Specifying Fixed Percentage and
Lump Sum Discounts.
+----------+
| ACT00102 |
+----------+
TEXT: NO TYPE O ROW WAS FOUND IN THE ACTACT TABLE.
TYPE: Error
REASON: The ACTXOPTS job was unable to access the
accounting options information, the type O row,
that was entered into CA MICS earlier using MWF.
ACTION: Reenter the options using MWF and then rerun
the ACTXOPTS job. Contact CA Technical Support
if the error recurs.
REFERENCES: Refer to the specific accounting option in
Chapter 4 of this guide. For example, for
invoice level refer to Section 4.5.1.
+----------+
| ACT00103 |
+----------+
TEXT: ________ TABLE OPEN FAILED. RC = __.
TYPE: Error
REASON: The attempt to open the table identified in the
message text failed. The ISPF return code is
included in the text of the message.
ACTION: An ISPF return code of 12 indicates that the
table is in use by another user and could not be
opened. Rerun the job at another time when the
table is available. Contact CA Technical
Support for assistance in resolving any other
ISPF return codes.
REFERENCES: None
+----------+
| ACT00104 |
+----------+
TEXT: ________ TABLE IS EMPTY.
TYPE: Termination
REASON: The table identified in the message text is
empty.
ACTION: An entry is required in the table and either the
table was not migrated correctly while applying
maintenance or the table entries have been
deleted. Recreate the table and rerun the job.
Contact CA Technical Support if you do not know
how to recreate the table. If the loss of the
table resulted from the application of
maintenance, be sure to contact CA Technical
Support before attempting to reapply it.
REFERENCES: None
+----------+
| ACT00105 |
+----------+
TEXT: ACCOUNTING IS INACTIVE. TO ACTIVATE, SPECIFY A
VALUE OF ACTIVE IN PREFIX.MICS.PARMS(EXECDEF).
TYPE: Warning
REASON: Accounting was not on. Accounting and
Chargeback will be executed but no observations
will be written to the journal or ledger files
for this unit.
ACTION: Specify a line with "ACCOUNTING ACTIVE" in
prefix.MICS.PARMS(EXECDEF). You can do this
online using the CA MICS Workstation Facility.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.1.
$SCOL
+----------+
| ACT00106 |
+----------+
TEXT: YOU MUST DEFINE YOUR ACCOUNTING CALENDAR VIA
PANELS. THE ________ TABLE DID NOT HAVE D ROWS
TO SUPPORT THE CALENDAR DEFINITION.
TYPE: Error
REASON: The option to use panels to define the special
Accounting and Chargeback calendar was chosen.
No calendar records exist in the ACT$AD table.
ACTION: Specify the accounting calendar by using the
online method to define it.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.6.3.
+----------+
| ACT00107 |
+----------+
TEXT: YOU MUST MODIFY YOUR ACCOUNTING CALENDAR
DEFINITION. THE CALENDAR DOES NOT HAVE AN ENTRY
FOR JULIAN DATE: ______________.
TYPE: Error
REASON: The online definition of your accounting
calendar does not contain the date that is in
your input records.
ACTION: Modify the accounting calendar by using the
online method to update your calendar for the
missing month.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.6.3.
+----------+
| ACT00108 |
+----------+
TEXT: THE PANEL DEFINED STARTING DAY OF THE WEEK
IS INVALID. THE INVALID DAY VALUE IS:
______________.
TYPE: Error
REASON: The online definition of your accounting
calendar specified a start of week that is not
valid.
ACTION: Modify the accounting week start day by using
the online panels to specify a valid week start
day.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.6.3.
+----------+
| ACT00109 |
+----------+
TEXT: THE ACCOUNTING DATE VARIABLES--ACTMONTH,
ACTYEAR, AND ACTDAY--WILL HAVE THE SAME VALUES
AS THE STANDARD CA MICS DATE VARIABLES UNLESS
SPECIAL CODING HAS BEEN PLACED IN THE AYEAR,
AMONTH, AND ADAY MACROS.
TYPE: Warning
REASON: You must supply user coding in the AYEAR,
AMONTH, AWEEK, and ADAY macro members; otherwise
assignments such as ACTMONTH=MONTH will be used.
ACTION: Modify the accounting date macros by using the
online panels to specify your SAS coding
assignments.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.6.3.
+----------+
| ACT00110 |
+----------+
TEXT: THE ACCOUNTING DATE MACROS--AYEAR, AMONTH,
AWEEK, AND ADAY--MUST BE MODIFIED TO TAKE OUT
THE GENERATED CODING. USE YOUR SAS CODING IN
THE MACROS TO DERIVE THE ACCOUNTING DATES.
TYPE: Error
REASON: Your panel parameters indicate that you do NOT
want to use panels to define the accounting
calendar. The panel parameters previously
indicated that panels were to be used to define
the accounting calendar. If this panel revision
is made, you must modify the four macros to take
out the coding that was previously generated
into these members.
ACTION: Modify the accounting date macros using the
online panels to specify your SAS coding
assignments instead of our generated SAS coding.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.6.3.
+----------+
| ACT00300 |
+----------+
TEXT: #ACTMSTR NOT REGENERATED BY LATEST MAGRUN DUE TO
ERROR. CORRECT AND RESUBMIT MAGRUN BEFORE
RESTARTING THE DAILY.
TYPE: Error
REASON: Errors that would not allow the regeneration
of #ACTMSTR were detected in the MAGRUN.
ACTION: Scan MICSLOG for any errors. Correct the errors
by following the instructions for each error
message in this appendix. When all errors have
been corrected, resubmit the MAGRUN.
+----------+
| ACT00301 |
+----------+
TEXT: EMPTY #ACTMSTR GENERATED BECAUSE THE RATE TABLE
DID NOT HAVE ANY SELECTED JOURNAL FILES. NO
JOURNAL FILES WILL BE CREATED DURING DAILY
PROCESSING FOR THIS UNIT.
TYPE: Error
REASON: All journal files in the rate table are marked
EXCLUDED.
ACTION: Use MWF 4;2;3;6 to select at least one journal
file in the rate table. You can use MWF
4;2;3;10 to specify ACCOUNTING INACTIVE.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.3.1.1.
+----------+
| ACT01001 |
+----------+
TEXT: NOTE: INPUT LISTING OF ______________.
TYPE: Information
REASON: A listing of the table or other data identified
in the message is being written to the MICSLOG
for informational purposes. This message is
followed by one or more ACT01002 messages that
list the actual data records.
ACTION: None
REFERENCES: MICSLOG message ACT01002.
+----------+
| ACT01002 |
+----------+
TEXT: _________
TYPE: Information
REASON: This message is used with message ACT01001 to
create a listing of data for informational
purposes. The text of this message is the
actual data being listed.
REFERENCES: MICSLOG message ACT01001.
$SCOL
+----------+
| ACT01003 |
+----------+
TEXT: KEYWORD NOT RECOGNIZED. KEYWORD=________.
TYPE: Error
REASON: The keyword identified in the message is not a
valid keyword for this process.
ACTION: The valid keywords for this job are:
COSTCTR1 COSTCTR6 BILLDATE TOBILLDT
COSTCTR2 COSTCTR7 COMPCODE WORKAREA
COSTCTR3 COSTCTR8 FRBILLDT WORKUNIT
COSTCTR4 COSTCTR9 INVCCAT ZONE
COSTCTR5 SYSID
ACTION: Correct the error and resubmit the job.
REFERENCES: MICSLOG messages ACT01004, ACT01018, and
ACT01019.
+----------+
| ACT01004 |
+----------+
TEXT: NO VALUE SPECIFIED WITH A KEYWORD OF ________.
TYPE: Error
REASON: The keyword shown in the message text identifies
a data item, such as a cost center or date, for
which information was to be selected and
reported on. However, data could not be
selected because no value was given for the data
item.
ACTION: Provide the value for the data item and resubmit
the job. You can use the CA MICS Workstation
Facility (MWF) to do this.
REFERENCES: MICSLOG messages ACT01003, ACT01018, and
ACT01019.
$SCOL
+----------+
| ACT01005 |
+----------+
TEXT: NOTE: DEFAULT SYSPARM VALUES ARE IN EFFECT.
ZERO CHARGES WILL NOT BE PRINTED.
THE AUDIT FILE WILL BE PRINTED.
TYPE: Warning
REASON: No SYSPARM information was provided. The
report program will use the audit tape as the
default file and will not print zero charge
values on the report.
ACTION: None
REFERENCES: None
+----------+
| ACT01006 |
+----------+
TEXT: THE INDICATED FILE IS EMPTY ________.
TYPE: Error
REASON: The file named in the message text is empty.
ACTION: Find the file named in the message in the list
below and take the action for that file.
ACTINPUT Identifies a file of user-supplied
data used as input for the standard
and recurring debits or credits,
budget amounts, or cost center
attributes. Determine the type of run
being made and supply the appropriate
data.
ACTJxxxx Identifies a journal file that
contains no observations. This
message appears in conjunction with
message ACT01030. See message
ACT01030.
ACTAUDIT Identifies an audit tape used as input
to the audit report. There were no
records in the tape file. Use the
correct tape and rerun the job.
BUDGTPRO Supply the budget projection
parameters and rerun the job.
COSTREC Supply the cost reconciliation data
and rerun the job.
RATE SIMULATION Identifies an audit tape used
as input to the audit report. There
were no records in the tape file.
Use the correct tape and rerun the
job.
ZEROBAL Supply the zero balance parameters
and rerun the job.
ZERO BALANCE ADJUSTMENTS There were no
adjustments in this file. Check the
zero balance parameters in the
sharedprefix.MICS.PARMS member
ZEROBAL. Ensure that both the zero
balance method and target amount are
correctly specified.
REFERENCES: CA MICS Accounting and Chargeback User Guide:
- Section 6.5.1.3 discusses the Audit Reports.
- Section 6.3.5 discusses the Cost
Reconciliation Report.
- Section 6.1.1.4 discusses the Zero Balance
Report.
$SCOL
+----------+
| ACT01007 |
+----------+
TEXT: ________ PROCESSING STARTED.
TYPE: Information
REASON: This message indicates that all preliminary
parameter checking is complete and that the
processing of data has begun.
ACTION: None
REFERENCES: None
+----------+
| ACT01008 |
+----------+
TEXT: INSUFFICIENT INPUT DATA SPECIFY _________.
TYPE: Error
REASON: The input data provided to the program could not
be processed. One or more data items were
omitted or incorrectly specified.
ACTION: This message is used to list the contents of the
erroneous input record. Message ACT01020 is
printed in conjunction with this message.
Message ACT01020 identifies the data item for
which information was incorrect or not provided.
REFERENCES: MICSLOG message ACT01020.
+----------+
| ACT01009 |
+----------+
TEXT: NOTE: END OF INPUT DATA, ________ FILE WILL BE
UPDATED.
TYPE: Information
REASON: The input data to the job was verified and the
file identified in the message will be updated
with the verified data.
ACTION: None
REFERENCES: None
+----------+
| ACT01012 |
+----------+
TEXT: SYSPARM VALUE MUST BE ________.
TYPE: Error
REASON: The SYSPARM for the job was specified
incorrectly.
ACTION: The value 'ACT01-99' in the message text
indicates that the SYSPARM in the JCL for the
cost reconciliation job was specified
incorrectly. The parameter ACTxx, where xx is a
number in the range of 01 to 99, indicates the
number of cycles of the Financial Recap File
that are to be included as input to the report.
Use the CA MICS Workstation Facility to correct
the SYSPARM and to resubmit the job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 6.3.5.
+----------+
| ACT01013 |
+----------+
TEXT: A COMBINATION OF TWO INPUT TYPES IS INVALID.
TYPE: Error
REASON: More than one reporting method was requested.
ACTION: Use MWF to specify either the TOTAL, INVCCAT, or
COMPCODE method of reporting. You can also use
MWF to resubmit the job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 6.3.5, Cost Reconciliation Report
Section 6.1.1.4, Zero Balance Report.
$SCOL
+----------+
| ACT01014 |
+----------+
TEXT: INVALID INPUT PARAMETER TO THE REPORT WAS
SPECIFIED. VALID TYPES ARE: TOTAL, INVCCAT, OR
COMPCODE.
TYPE: Error
REASON: An invalid reporting method was requested.
ACTION: Use MWF to correct the method being requested
and to resubmit the job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 6.3.5, Cost Reconciliation Report
Section 6.1.1.4, Zero Balance Report.
+----------+
| ACT01015 |
+----------+
TEXT: INV, CPC, RAT ARRAY SIZES EXCEEDED.
TYPE: Error
REASON: The invoice category, computation code, and rate
array sizes have been exceeded.
ACTION: Contact CA Technical Support.
REFERENCES: None
$SCOL
+----------+
| ACT01016 |
+----------+
TEXT: COST CENTER ATTRIBUTES FILE IS NOT INITIALIZED.
CHECK THE ACCOUNTING & CHARGEBACK INSTALLATION
PROCEDURES.
TYPE: Error
REASON: The Cost Center Attributes File is used to
define cost centers to CA MICS. A minimum of one
entry must be made to the file. The file
contains descriptive information about the cost
center, which includes the name and address of
the cost center, its billing status, invoice
format, and discounting data.
ACTION: Use MWF to set up the cost center attributes.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Sections 4.1 through 4.1.6.
+----------+
| ACT01017 |
+----------+
TEXT: THE REVENUE/CREDIT TREND REPORT WILL HAVE TO BE
MODIFIED. THE SPECIAL ACCOUNTING CALENDAR IS
NOT SUPPORTED IN THIS REPORT.
TYPE: Error
REASON: The Revenue/Credit Trend Report program detected
an accounting calendar with more than 13 months.
ACTION: Modify the report program in order to use this
special accounting calendar.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 6.3.2.6.
+----------+
| ACT01018 |
+----------+
TEXT: SYSID IS > 4 CHARACTERS IN LENGTH. SYSID=___.
TYPE: Error
REASON: The value for SYSID, shown in the message text,
is greater than four characters in length.
ACTION: Correct the value of the SYSID in the SYSID
selection record. The SYSID selection record is
found in the SELECTIN input file of the job.
Resubmit the job after correcting the SYSID.
REFERENCES: MICSLOG messages ACT01003, ACT01004, and
ACT01019.
+----------+
| ACT01019 |
+----------+
TEXT: SELECTIN DEFINITION IS IN ERROR. CORRECT THE
ERROR AND RUN AGAIN.
TYPE: Error
REASON: Errors were detected in one or more of the
control records for the selection of data to be
used for reporting.
ACTION: This message will appear in conjunction with
messages ACT01003, ACT01004, and/or ACT01018.
See these messages for the identification and
correction of the specific errors encountered.
REFERENCES: MICSLOG messages ACT01003, ACT01004, and
ACT01018.
+----------+
| ACT01020 |
+----------+
TEXT: INSUFFICIENT INFORMATION SPECIFIED FOR UPDATE OF
_______.
TYPE: Error
REASON: This message identifies the data item that
could not be updated because either it was
incorrectly specified or it was not provided.
ACTION: This message appears in conjunction with one or
more ACT01008 messages. The ACT01008 messages
list the data items from the record in error.
Correct the erroneous data item and resubmit the
job.
REFERENCES: MICSLOG message ACT01008.
+----------+
| ACT01021 |
+----------+
TEXT: POSSIBLE ERRORS IN INVOICE. CHECK SAS LOG FOR
SPECIFIC MESSAGES.
TYPE: Error
REASON: Errors were detected while creating the
invoices. An error flag was set and processing
continued until all data was processed. Once
all data was processed, the job was terminated
with a USER 0998 abend code.
ACTION: Check the SAS Log for errors. Correct the
errors and rerun the job.
REFERENCES: None
+----------+
| ACT01022 |
+----------+
TEXT: ALLOCATION FAILED FOR DATASET ____.
ERROR CODE- _____, INFO_CD-_______.
TYPE: Error
REASON: The dynamic allocation failed for the data set
identified in the message.
ACTION: The error codes and information reason codes are
displayed on the SAS Log. See the SAS Log for
more information on the failure.
REFERENCES: None
+----------+
| ACT01023 |
+----------+
TEXT: ACT COMPONENT ACTIVE IN _________ UNIT.
ALLOCATION COMPLETED FOR DATASET- _________.
ALLOCATION TO DDNAME- __________.
TYPE: Information
REASON: This is an informational message that indicates
that accounting is active in the unit shown in
the message and that the dynamic allocation of
the data set, also identified in the message,
was successful.
ACTION: None
REFERENCES: None
+----------+
| ACT01024 |
+----------+
TEXT: ACT COMPONENT NOT ACTIVE IN _________ UNIT.
TYPE: Warning
REASON: CA MICS Accounting and Chargeback has not been
activated in the unit identified in the message.
ACTION: Ensure that the job is pointing to the correct
unit. If it is not, correct the JCL and rerun
the job. If it is, turn on Accounting and
Chargeback by specifying a value of "ACCOUNTING
ACTIVE" in the prefix.MICS.PARMS(EXECDEF)
member. Activation can be done using MWF.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.1.
+----------+
| ACT01025 |
+----------+
TEXT: NO UNITS ARE TEST, UNIT OR PRIMARY.
CHECK THE #CPLXLST MEMBER.
TYPE: Error
REASON: No units have been defined as UNIT, TEST, or
PRIMARY for this complex.
ACTION: The #CPLXLST member of sharedprefix.MICS.SOURCE
contains no units defined as PRIMARY, UNIT, or
TEST. The units are defined at the time of
installation. Using the reference below,
properly define the units.
REFERENCES: PIOM, Section 2.3.1.4.3, which indicates
additional references.
+----------+
| ACT01026 |
+----------+
TEXT: UNABLE TO PARSE ACTACCT MACRO.
TYPE: Error
REASON: The values obtained by parsing the ACTACCT macro
were invalid.
ACTION: Check the ACTACCT macro as generated in the
sharedprefix.MICS.MACAUTOS library to determine
that the parameter specifications contained in
the macro are correct. If you are in doubt as
to the contents of the ACTACCT macro, contact
CA Technical Support for assistance.
REFERENCES: None
+----------+
| ACT01027 |
+----------+
TEXT: COSTCTR LEVEL NOT BETWEEN 1 AND 9. COSTCTR1
ASSUMED.
TYPE: Warning
REASON: The cost reconciliation cost center level was
not specified or it was specified incorrectly as
part of the input TOTAL parameter record. A
cost center level of one is assumed.
ACTION: None, if cost center one is the desired level.
If it is not, use the CA MICS Workstation
Facility to correct the TOTALn keyword, where n
represents cost center level 1-9. Then resubmit
the job.
REFERENCES: Refer to the online tutorial for the Cost
Reconciliation Parameters panel
(MWF;4;2;2;2;4;1).
$SCOL
+----------+
| ACT01028 |
+----------+
TEXT: REPORTKEY HAS INVALID VALUE _______. SUBSTITUTED-
DEFAULT, CORRECT AND RERUN.
TYPE: Error
REASON: The GROUP2 value on the REPORTKEY control
statement for the Generalized High Level Report
contains a value other than COSTCTR1-9, SYSID,
or EXTERNAL. The invalid value is shown in the
message.
ACTION: Use the online facilities of MWF to correct and
resubmit the report.
REFERENCES: None
+----------+
| ACT01029 |
+----------+
TEXT: REPORTKEY HAS INVALID VALUE- ________.
SUBSTITUTED- COSTCTR1, CORRECT AND RERUN.
TYPE: Error
REASON: The GROUP1 value on the REPORTKEY control
statement for the Generalized High Level Report
contains a value other than COSTCTR1-9 or SYSID.
The invalid value is shown in the message.
ACTION: Use the online facilities of MWF to correct and
resubmit the report job.
REFERENCES: None
+----------+
| ACT01030 |
+----------+
TEXT: JOURNAL FILE ______ EXISTS IN THE CA MICS DATA
BASE, BUT DOES NOT CONTAIN ANY OBSERVATIONS.
TYPE: Error
REASON: The journal file identified in the message text
was found but there were no observations in the
file.
ACTION: Determine whether the file accessed is the one
desired. If it is, then determine the cause of
the missing observations and correct the file
before attempting to rerun this job. If the
wrong file was accessed, change the SYSPARM
parameters in the JCL and resubmit the job.
REFERENCES: None
+----------+
| ACT01031 |
+----------+
TEXT: JOURNAL FILE ________ DOES NOT EXIST IN THE
CA MICS DATA BASE. REVIEW THE SYSPARM VALUE IN
THE JCL FOR A VALID 2 CHARACTER JOURNAL ID.
TYPE: Error
REASON: The database accessed does not contain the
selected file.
ACTION: Determine which file should be accessed, change
the SYSPARM of the JCL, and resubmit the job.
REFERENCES: None
+----------+
| ACT02000 |
+----------+
TEXT: NOTE: PROC MAACTCPY NOTE:
NOTE: ACTAUDT1 DSNAME IS ________.
NOTE: ACTAUDMN DSNAME IS ________.
NOTE: ACTAUDD1 DSNAME IS ________.
NOTE: ACTAUDD2 DSNAME IS ________.
TYPE: Information
REASON: This message consists of two parts. The first
line indicates that the MAACTCPY procedure is
being executed. The next four lines identify
the data set names associated with each of the
ddnames listed. Message ACT02001 is printed in
conjunction with this message.
ACTION: None
REFERENCES: MICSLOG message ACT02001.
+----------+
| ACT02001 |
+----------+
TEXT: NOTE: _____ LINES WERE READ FROM INFILE
ACTAUDT1.
NOTE: _____ LINES WERE WRITTEN TO FILE ACTAUDD1.
NOTE: _____ LINES WERE WRITTEN TO FILE ACTAUDD2.
NOTE: _____ LINES WERE WRITTEN TO FILE ACTAUDMN.
TYPE: Information
REASON: This message shows the number of lines read from
the ACTAUDT1 file and the number of lines
written to the other files.
ACTION: The sum of the lines written to the ACTAUDD1 and
the ACTAUDMN files should equal the number of
lines read from the ACTAUDT1. The number of
lines written to the ACTAUDD2 file should be the
same as was written to the ACTAUDD1 file.
REFERENCES: MICSLOG message ACT02000.
+----------+
| ACT02002 |
+----------+
TEXT: END FILE ON FT15F001.
TYPE: Error
REASON: The program failed to dynamically produce the
SAS code that was to be executed within this job
step.
ACTION: Contact CA Technical Support.
REFERENCES: None
+----------+
| ACT02003 |
+----------+
TEXT: NUMBER OF BYTES READ = ______.
TYPE: Information
REASON: This message is produced by the MAACTCPY and the
MAACTGNR procedures when an I/O error is
encountered. The message indicates the number
of bytes read from the file experiencing the I/O
error.
ACTION: Determine the cause of the I/O error and correct
it. Then rerun the abending step.
REFERENCES: None
+----------+
| ACT02005 |
+----------+
TEXT: NOTE: PROC MAACTGNR
NOTE: ACTAUDT1 DSNAME IS ________
NOTE: ACTAUDT2 DSNAME IS ________
TYPE: Information
REASON: The first line of this message indicates that
the MAACTGNR procedure is being executed. The
next two lines identify the data set names
associated with the ddnames ACTAUDT1 and
ACTAUDT2. Informational message ACT02006 will
be displayed along with this message.
ACTION: None
REFERENCES: None
+----------+
| ACT02006 |
+----------+
TEXT: NOTE: ______ LINES WERE READ FROM INFILE
ACTAUDT1
NOTE: ______ LINES WERE WRITTEN TO FILE ACTAUDT2
TYPE: Information
REASON: This message lists the number of records read
from the input file ACTAUDT1 and the number of
records written to the output file ACTAUDT2.
Message ACT02005 accompanies this message to
identify the data set names associated with the
ddnames ACTAUDT1 and ACTAUDT2.
ACTION: The number of records read and written should be
the same.
REFERENCES: None
+----------+
| ACT02007 |
+----------+
TEXT: THE ACTDATE OPTION HAS BEEN CHANGED AND THE JCL
HAS NOT BEEN UPDATED. REGENERATE THE MONTHLY,
MONTHACT, YEARLY, AND YEARACT JOBS WITH JCLGENU.
RESTART THIS JOB AFTER REGENERATION OF THE JCL.
TYPE: Error
REASON: The monthly split has detected that a change in
the specification of the ACTDATE option has
occurred without the required regeneration of
the JCL for the MONTHLY, MONTHACT, YEARLY, and
YEARACT jobs.
ACTION: Determine that the current specification for
ACTDATE is correct. If it is correct, and the
special accounting dates are requested, then
regenerate the JCL for the jobs named in the
message and restart the abending job in the same
step. Also, read the references below and be
sure to follow the instructions for the running
of the MONTHACT job at the appropriate time.
If the current ACTDATE specification is not
correct, respecify the ACTDATE option and run
the ACTXOPTS job. Restart the abending job in
the abending step.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Sections 4.6 through 4.6.1.
+----------+
| ACT02200 |
+----------+
TEXT: _____ NOT RECOGNIZED. ACCEPTED VALUES ARE:
"$TABLE", "$ADDLN", OR "$MODLN"
TYPE: Error
REASON: The update type identified in the message is not
valid. The three valid update types are listed
in the message. A print of the error record
image immediately follows message ACT02200 on
the MICSLOG in message ACT02230.
ACTION: Contact CA Technical Support for assistance with
this error. Have the MICSLOG listing available
for reference when you call.
REFERENCES: MICSLOG message ACT02230.
SPECIAL NOTE FOR ALL ACT022xx MESSAGES:
The ACT022xx series of messages are produced by
an ISPF table maintenance utility used during
the apply of CA MICS Accounting and Chargeback
product changes. This utility uses the ACTTBUTL
member of the sharedprefix.MICS.SOURCE library.
A comment block at the beginning of the member
explains which ISPF tables it will update,
explains which update functions are available,
and describes the control statements used as
input to the utility. This information should
help you to understand some of the terminology
used in the messages, as well as the
functionality of the utility in general.
The control statements processed by the ACTTBUTL
utility are provided as part of the product
change. The control statements cause revision
or additions to your production ISPF tables for
CA MICS and should not normally create any
conflicts when you run the utility job.
However, it is possible that someone in your
data center might have created an invoice,
credit category, or a charging element that
might conflict with the provided updates and
thus cause one of the ACT022xx error message
conditions to exist.
The product change text, which accompanies the
maintenance, will point out areas in which these
conflicts might occur. The product change text
will also contain specific instructions for
changing or eliminating any of the control
statements that might be causing the error.
Therefore, you should be familiar with the
product change text and have it available as a
reference when attempting to resolve any of the
ACT022xx error messages.
As always, in situations in which you are unsure
of the action to be taken to resolve the error,
or if the action you took did not resolve the
error, contact CA Technical Support for
assistance. When you call, have available for
reference both the change text that you are
using and all output from the job producing the
error.
+----------+
| ACT02201 |
+----------+
TEXT: _______ NOT RECOGNIZED. "RENAME" WAS EXPECTED.
TYPE: Error
REASON: The type of update shown in the message is not
valid. The program expected a rename instead.
The record image of the statement causing the
error is listed immediately after this message
on the MICSLOG as message ACT02230.
ACTION: Contact CA Technical Support for assistance with
this error. Have the MICSLOG listing available
for reference when you call.
REFERENCES: MICSLOG message ACT02230.
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02202 |
+----------+
TEXT: _______ NOT RECOGNIZED. "FORCE" WAS EXPECTED.
TYPE: Error
REASON: The requested update function was recognized by
the program. The program was expecting an
update type of FORCE. The entire update
record is shown in message ACT02230, which
immediately precedes this message on the
MICSLOG.
ACTION: Contact CA Technical Support for assistance.
REFERENCES: MICSLOG message ACT02230.
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02203 |
+----------+
TEXT: CONTROL DATA SET CONTAINS INSUFFICIENT DATA.
TYPE: Error
REASON: There are no control records in the control data
set.
ACTION: Change the JCL for the job so that the control
records are available for processing. This may
mean inserting the records directly into the
job stream or changing the JCL to point to the
data set containing the control records.
REFERENCES: None
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02204 |
+----------+
TEXT: MASTER TABLE ________ DOES NOT CONTAIN CONTROL
VARIABLE ________ WITH VALUE: ________
TYPE: Error
REASON: The master table, identified in the message,
does not contain an entry for the control
variable with the value as shown in the message.
ACTION: Contact CA Technical Support for assistance.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
$SCOL
+----------+
| ACT02205 |
+----------+
TEXT: CONTROL VARIABLE _______ IS ALREADY IN TABLE
______ WITH VALUE: ________
TYPE: Error
REASON: The control variable and its indicated value
already exist in the identified user table.
ACTION: Contact CA Technical Support for assistance.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02206 |
+----------+
TEXT: RENAME CONTROL VARIABLE ________ IS ALREADY IN
TABLE ______ WITH VALUE: _______
TYPE: Error
REASON: The control variable already exists in the
table. The table, the control variable, and the
value of the control variable are shown in the
message.
ACTION: Contact CA Technical Support for assistance.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02207 |
+----------+
TEXT: $ADDLN FAILED FOR CONTROL VARIABLE _____ WITH AN
ISPF CODE OF ______.
TYPE: Error
REASON: The $ADDLN, add operation, failed for the named
control variable with the ISPF return code shown
in the message.
ACTION: An ISPF return code of 08 indicates that a row
with the same key already exists in the table.
See the product change text for possible
instructions as to what to do in this situation.
If there are no instructions in the product
change text for this situation, or if you are
unsure of what action to take, contact CA
Technical Support for assistance with
this or any other ISPF return codes.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02208 |
+----------+
TEXT: TABLE _______ DOES NOT CONTAIN CONTROL VARIABLE
_______ WITH VALUE: ________.
TYPE: Error
REASON: The element is not in the table. The table and
the control variable with its value are shown in
the message.
ACTION: Contact CA Technical Support for assistance.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02209 |
+----------+
TEXT: $MODLN FAILED FOR CONTROL VARIABLE ______ BECAUSE
VALUE FOR ELEMENT _______ IS NOT AS EXPECTED.
SPECIFIED VALUE: ______ ACTUAL VALUE: _______
TYPE: Error
REASON: The element value in the update does not match
that found in the table. The control variable
and the element name are shown in the message,
along with the specified value of the element
name and the actual value found in the table.
ACTION: Contact CA Technical Support for assistance.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02210 |
+----------+
TEXT: $MODLN FAILED FOR CONTROL VARIABLE _____ WITH AN
ISPF CODE OF ______.
TYPE: Error.
REASON: The update for the control variable failed with
the ISPF return code shown in the message.
ACTION: An ISPF return code of 08 indicates that the
update statement key does not match the key in
the table. See the product change text for
possible instructions as to what to do in this
situation. If there are no instructions in the
product change text for this situation, or if
you are unsure of what action to take, contact
CA Technical Support for assistance with this or
any other ISPF return codes.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02211 |
+----------+
TEXT: UPDATE FOR CONTROL VARIABLE _______WILL "BE
FORCED BECAUSE VALUE FOR ELEMENT ______IS NOT AS
EXPECTED. SPECIFIED VALUE: ______ ACTUAL
VALUE: _____
TYPE: Warning
REASON: The update for the indicated control variable
will be forced. The value of the element in the
table did not match the verification value found
in the update record. The verification value
and the actual value found in the table are
shown in the message.
ACTION: None
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02213 |
+----------+
TEXT: ________ IS NOT VALID. NO PRECEDING $TABLE
STATEMENT HAS BEEN SPECIFIED.'
TYPE: Error
REASON: The update type indicated in the message is not
valid because a table control statement was not
present in the input. The entire record is
printed on the MICSLOG in message ACT02230,
which immediately precedes this message.
ACTION: Contact CA Technical Support for assistance with
this error. Have the MICSLOG listing available
for reference when you call.
REFERENCES: MICSLOG message ACT02230.
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02214 |
+----------+
TEXT: ______ IS NOT VALID. NAMED TABLE _______
WAS NOT SPECIFIED ON PRECEDING $TABLE STATEMENT.
TYPE: Error
REASON: The update type indicated in the message is not
valid because the table named in the message was
not listed in the preceding table control
statement. The entire record is printed on the
MICSLOG in message ACT02230, which immediately
precedes this message.
ACTION: Contact CA Technical Support for assistance with
this error. Have the MICSLOG listing available
for reference when you call.
REFERENCES: MICSLOG message ACT02230.
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02215 |
+----------+
TEXT: ________ STATEMENT CONTAINS EXTRANEOUS
INFORMATION. INFO IS ______.
TYPE: Error
REASON: The control statement contains more information
than is required for an update of this type.
The type of update and the "extra" information
are shown in the message. Message ACT02230
displays the entire control statement and is
printed on the MICSLOG immediately before this
message.
ACTION: Contact CA Technical Support for assistance with
this error. Have the MICSLOG listing available
for reference when you call.
REFERENCES: MICSLOG message ACT02230.
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02216 |
+----------+
TEXT: SORT FAILED FOR TABLE ________. REASON FOLLOWS.
TYPE: Error
REASON: The sort failed for the table identified in the
message. Message BAS00472 immediately follows
this message and contains the return code to
assist in resolving the problem.
ACTION: Contact CA Technical Support for assistance with
this error. Have the MICSLOG listing available
for reference when you call.
REFERENCES: MICSLOG message BAS00472.
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02220 |
+----------+
TEXT: $MODLN COMPLETED FOR CONTROL VARIABLE _______
WITH VALUE ________.
TYPE: Information
REASON: A table row, identified in the message by the
control variable name and its value, was
successfully scanned and was found to be free of
errors. If all other updates for the table are
error-free and this execution of the utility is
not a test, the row will be added to the table.
ACTION: None
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02221 |
+----------+
TEXT: $ADDLN COMPLETED FOR CONTROL VARIABLE ______
WITH VALUE: ______
TYPE: Information
REASON: An add statement for the table row, identified
in the message by the control variable name and
its value, was successfully scanned and was
found to be free of errors. If all other
updates for the table are error-free and this
execution of the utility is not a test, the row
will be added to the table.
ACTION: None
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02222 |
+----------+
TEXT: TEST OPTION SPECIFIED. NO UPDATES WILL BE
PERFORMED.
TYPE: Information
REASON: The TEST option allows the updates to be scanned
for errors but does not allow the updates to the
tables to be made. This allows new updates to
be checked out without jeopardizing the tables.
ACTION: No action is required for this message.
However, the MICSLOG should be reviewed for any
other errors or messages pertaining to the
updates.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02223 |
+----------+
TEXT: _______ SUCCESSFULLY UPDATED.
TYPE: Information
REASON: The table identified in the message was
successfully updated.
ACTION: None
REFERENCES: None
+----------+
| ACT02224 |
+----------+
TEXT: _______ TO BE PROCESSED FOR UPDATE.
TYPE: Information
REASON: The updates for the table identified in the
message have been processed and the table will
now be updated.
ACTION: None
REFERENCES: None
$SCOL
+----------+
| ACT02225 |
+----------+
TEXT: ACCOUNTING TABLE MAINTENANCE UTILITY
____________
TYPE: Information
REASON: This is an informational message that indicates
that the accounting table maintenance utility
program is being executed. This message also
acts as a header to help identify any messages
that follow as being issued by the ACTTBUTL
program.
ACTION: None for this message. Carefully review any
messages that follow it.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02230 |
+----------+
TEXT: CONTROL STMT - ______.
TYPE: Information
REASON: This message lists the input control statement
that is being processed. Any errors pertaining
to the statement will be listed as a separate
message following this one.
ACTION: None, for this message. See the error message
immediately following this one.
REFERENCES: MICSLOG messages ACT02200, ACT02201, ACT02202,
ACT02213, ACT02214, and ACT02215.
See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02233 |
+----------+
TEXT: ERRORS ENCOUNTERED. ABEND 998 ISSUED. NO TABLE
UPDATES PERFORMED. CORRECT ERRORS AND RERUN.
TYPE: Error
REASON: The Accounting Table Maintenance Utility program
does not allow the production tables to be
updated unless the entire file of updates is
found to be free of errors. If any errors are
detected in the update records, the utility
terminates abnormally with a user abend 998.
ACTION: Correct the errors identified on the MICSLOG and
rerun the job.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02234 |
+----------+
TEXT: NO $TABLE CONTROL STATEMENT FOUND. ABORT ABEND.
TYPE: Error
REASON: The Accounting Table Maintenance Utility program
does not allow the update to run unless a
$TABLES control statement is present in the
SYSIN.
ACTION: Correct the errors identified on the MICSLOG and
rerun the job.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02235 |
+----------+
TEXT: INVALID TABLE ____ IN $TABLES STATEMENT. ABORT
ABEND.
TYPE: Error
REASON: The Accounting Table Maintenance Utility program
does not allow the update to run unless a
$TABLES control statement has one of the valid
tables names in SYSIN.
ACTION: Correct the errors identified on the MICSLOG and
rerun the job.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02236 |
+----------+
TEXT: UNKNOWN TABLE NAME _____ FOUND. ABORT ABEND.
TYPE: Error
REASON: The Accounting Table Maintenance Utility program
does not allow the update to run unless a
$TABLES control statement has one of the valid
tables names in SYSIN.
ACTION: Correct the errors identified on the MICSLOG and
rerun the job.
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02237 |
+----------+
TEXT: ACT____ UPDATE COMPLETED FOR TABLE _____.
______ ROWS ADDED. ______ ROWS MODIFIED.
TYPE: Information
REASON: The Accounting Table Maintenance Utility program
will use the completed table update message to
indicate that the update completed successfully.
ACTION: None
REFERENCES: See the SPECIAL NOTE FOR ALL ACT022xx MESSAGES
in the reference section of message ACT02200.
+----------+
| ACT02238 |
+----------+
TEXT: INPUT PERCENT VALUE IS INVALID FOR -- _______.
VALUE. IS NOT BETWEEN 0-100. VALUE IS
________.
TYPE: Error
REASON: The percent values in the input records are not
in the 0 to 100 range.
ACTION: Validate the input record percentages. If the
prorating utility is being used for the first
time, ensure that the prorating input routine is
coded correctly.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.15.2.
+----------+
| ACT02239 |
+----------+
TEXT: PRORATE TOTALS FOR COST CENTER--_______. DO NOT
SUM TO 100. ACTUAL SUM IS ______.
TYPE: Error
REASON: The percent values in the input records do not
add up to 100 percent for the indicated cost
center.
ACTION: Validate the input record percentages. If the
prorating utility is being used for the first
time, ensure that the prorating input routine is
coded correctly.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.15.2.
+----------+
| ACT02240 |
+----------+
TEXT: A DUPLICATE _______ HAS BEEN ENCOUNTERED. THE
DUPLICATE HAS BEEN DROPPED. VALUE IS _______.
TYPE: Information
REASON: The COSTCTR1 value is associated with multiple
cost center groups. It can only be in one
group.
ACTION: Validate the input record COSTCTR1 values. If
this utility is being used for the first time,
ensure that the utility input routine is coded
correctly.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.15.2.
+----------+
| ACT02241 |
+----------+
TEXT: UPDATE COMPLETED FOR TABLE _name_ _number_ ROWS
ADDED.'
TYPE: Information
REASON: The table named has been successfully updated.
ACTION: None
REFERENCES: None
+----------+
| ACT02242 |
+----------+
TEXT: OPEN SUCCESSFUL FOR TABLE _name_
TYPE: Information
REASON: The CA MICS dialog processor has opened the
named table for input or update.
ACTION: None
REFERENCES: None
+----------+
| ACT02243 |
+----------+
TEXT: TABLE _name_ NOT FOUND.'
TYPE: Information
REASON: The table named could not be found in
sharedprefix.MICS.ISPTLIB. This message is
issued when a cost center validation table is
not found. The last character of the table
named is the cost center level of the validation
values.
ACTION: None, unless a validation table has been created
for this cost center level. In this case,
contact CA Technical Support.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.15.2.
+----------+
| ACT02244 |
+----------+
TEXT: INVOICE FORMAT _format_ SPECIFIED FOR COSTCTR1
_cost center value_ NOT FOUND IN ACTIVF01 FILE.
ABORT ISSUED.
TYPE: Error
REASON: The Cost Center Attributes entry for a cost
center with the COSTCTR1 value shown in the
message specifies the name of a format that has
not been defined.
ACTION: Define the format name via the Accounting
Options Invoice Formats panel.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Sections 4.5.2 through 4.5.2.4.
+----------+
| ACT02248 |
+----------+
TEXT: RETROFIT OF YTD FILE TO CURRENT INVOICE LEVELS
COMPLETED SUCCESSFULLY.
TYPE: Information
REASON: The ACTYTDRF job successfully completed the
retrofit of the year-to-date Financial Recap
File.
ACTION: None
REFERENCES: None
+----------+
| ACT02249 |
+----------+
TEXT: %OLDMOD IS OBSOLETE. USE MWF;4;2;1 TO
UPDATE THE ISPF DATA TABLE ONLINE AND RUN THE
GEN. OR YOU CAN USE THE BATCH UPDATE UTILITY
TO UPDATE THE SAS FILE AND ISPF DATA TABLE.
TYPE: Error
REASON: The module named is no longer supported.
ACTION: Use the specified job to update the ISPF table.
REFERENCES: None
+----------+
| ACT02250 |
+----------+
TEXT: INVALID VALUE FOR _cost center level_ = _value_
UPDATE WILL BE ABENDED. USE MWF;4;2;3;1;4 TO
UPDATE THE COST CENTER VALIDATION TABLE.
TYPE: Error
REASON: You have attempted to update the Applications
Database files with a COSTCTRn value that is
not contained in the cost center validation
table for the cost center level specified in the
message.
ACTION: Either change the cost center validation table
to include the cost center values that are in
your update data, or edit your update data prior
to attempting the update.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.1.6.
+----------+
| ACT02252 |
+----------+
TEXT: MONTHS LEDGER FILES ACTLGR01 FOR ALL UNITS
ARE EMPTY. CHECK THAT CA MICS MONTHLY RAN
CORRECTLY IN ALL ACCOUNTING AND CHARGEBACK
UNITS.
TYPE: Warning
REASON: None
ACTION: Check that CA MICS monthly ran correctly in
all Accounting and Chargeback units.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.2.
+----------+
| ACT02253 |
+----------+
TEXT: MONTHS LEDGER FILES ACTLGR01 AND STANDARD
DEBIT FILE ACTSDT01 ARE EMPTY. ABORT ISSUED.
TYPE: Error
REASON: There are no observations in the ledger and
debit files.
ACTION: Check that CA MICS monthly and the table
update ran correctly in all Accounting and
Chargeback units.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.2.
+----------+
| ACT02254 |
+----------+
TEXT: ACCOUNTING ADJUSTMENT TABLE LOAD STARTED
TYPE: Information
REASON: This message indicates that all preliminary
parameter checking is complete and that the
adjustment table loading has begun.
ACTION: None
REFERENCE: None
+----------+
| ACT02255 |
+----------+
TEXT: VALIDATION ERROR FOR INPUT RECORD ______
TYPE: Error
REASON: The input record ______ should have the value D
or C for ADJDBCR, and S or R for ADJENTRY.
Both quantity and rate are required if the
amount is missing. Predefined or valid
COMPUTATION CODE, INVOICE CATEGORY, and CREDIT
CATEGORY values must be used.
ACTION: Correct all flagged errors and resubmit.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 1.2.
$SCOL
+----------+
| ACT02256 |
+----------+
TEXT: RECORD _______ NOT ADDED BECAUSE OF PREVIOUS
ERRORS.
TYPE: Error
REASON: Previously flagged errors in the control stream
resulted in the termination of this run.
ACTION: Correct all flagged errors and resubmit.
REFERENCES: A print of the error record image immediately
follows message ACT02255 on the MICSLOG.
+----------+
| ACT02257 |
+----------+
TEXT: INPUT RECORD VALIDATION COMPLETED
RECORDS INPUT=___, RECORDS ACCEPTED=____
TYPE: Information
REASON: This number of records were validated and
accepted from the adjustment table.
ACTION: None
REFERENCE: None
+----------+
| ACT02258 |
+----------+
TEXT: UPDATE COMPLETE FOR TABLE _______ REPLACE
FUNCTION STARTED WITH _____ ROWS ADJDBCR
DELETE CRITERIA=(_ _) ADJENTRY DELETE
CRITERIA=(_ _) ___ ROWS WERE DELETED FROM THE
TABLE'
TYPE: Information
REASON: None
ACTION: None
REFERENCES: None
+----------+
| ACT02259 |
+----------+
TEXT: INVALID PARAMETER(S) PASSED TO ACTJADJO MACRO
%EMSG1
%EMSG2
%EMSG3
ADJUSTMENT TABLE LOAD PROCESS ABORTED
TYPE: Error
REASON: An incorrect parameter value was specified to
update the adjustment table.
ACTION: Correct the error and resubmit the job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.15.
+----------+
| ACT02265 |
+----------+
TEXT: SYSID is not defined for Linux input file.
TYPE: Error
REASON: SYSID is not specified in
prefix.MICS.PARMS(LINUXP). SYSID must be four
characters in length.
ACTION: Review and correct the SYSID specification in
members LINUXP of prefix.MICS.PARMS and rerun
MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02266 |
+----------+
TEXT: SYSID is greater than four characters in length
TYPE: Error
REASON: SYSID in prefix.MICS.PARMS(LINUXP) must be four
characters in length.
ACTION: Review and correct the SYSID specification in
member LINUXP of prefix.MICS.PARMS and rerun
MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02267 |
+----------+
TEXT: DSN IS GREATER THAN 44 CHARACTERS IN LENGTH.
TYPE: Error
REASON: DSN in prefix.MICS.PARMS(LINUXP) must be 44
characters in length or less.
ACTION: Review and correct the DSN specification in
member LINUXP of prefix.MICS.PARMS, and
rerun MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02268 |
+----------+
TEXT: DDNAME is greater than 8 characters in length.
TYPE: Warning
REASON: The ddname in prefix.MICS.PARMS(LINUXP) must be
8 characters in length or less.
ACTION: Review and correct the ddname specification in
member LINUXP of prefix.MICS.PARMS, and rerun
MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02269 |
+----------+
TEXT: Global must be PLATFORM and/or TIMESHIFT.
TYPE: Error
REASON: Global option in prefix.MICS.PARMS(LINUXP) must
be PLATFORM and/or TIMESHIFT.
ACTION: Review and correct the global specification in
member LINUXP of prefix.MICS.PARMS, and rerun
MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02270 |
+----------+
TEXT: Global Platform must be I or M
TYPE: Error
REASON: Global Platform option in
prefix.MICS.PARMS(LINUXP) must be PLATFORM
and/or TIMESHIFT.
ACTION: Review and correct the global specification in
member LINUXP of prefix.MICS.PARMS, and rerun
MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02271 |
+----------+
TEXT: TIMESHIFT must be between -12 and 12 hours
TYPE: Error
REASON: TIMESHIFT option in prefix.MICS.PARMS(LINUXP)
must be between -12 and 12 hours.
ACTION: Review and correct the TIMESHIFT specification
in member LINUXP of prefix.MICS.PARMS, and rerun
MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02272 |
+----------+
TEXT: Fourth or fifth DD statement keyword
must be P= or T=.
Correct the statement specification in
prefix.MICS.PARMS(LINUXP) and rerun the MAGRUN.
TYPE: Error
REASON: Fourth or fifth DD statement in
prefix.MICS.PARMS(LINUXP) must be P= or T=.
ACTION: Review and correct the TIMESHIFT or the PLATFORM
specification in member LINUXP of
prefix.MICS.PARMS, and rerun MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02273 |
+----------+
TEXT: Multiple PLATFORM/TIMESHIFT settings on same DD
Correct the statement specification in
prefix.MICS.PARMS(LINUXP) and rerun the MAGRUN.
TYPE: Error
REASON: Only one PLATFORM and TIMESHIFT setting can be
specified for each input data set.
ACTION: Review and correct the TIMESHIFT or the PLATFORM
specification in member LINUXP of
prefix.MICS.PARMS, and rerun MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT02274 |
+----------+
TEXT: Duplicate DDNAME or DSN or SYSID found.
Correct the statement specification in
prefix.MICS.PARMS(LINUXP) and rerun the MAGRUN.
TYPE: Error
REASON: Duplicate ddname, DSN, or SYSID STATEMENTS were
specified in member LINUXP of prefix.MICS.PARMS,
and rerun MAGRUN.
ACTION: Review and correct the duplicate ddname or DSN
or SYSID value in member LINUXP of
prefix.MICS.PARMS, and rerun MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.1.
+----------+
| ACT03000 |
+----------+
TEXT: ACTUALLO macro invoked with the following
parameters:
UNITS=______ LIBS=_____
REALLOC=________ FMTSR=______ DB=___
DBDISP=_______ EXIT=_____ FREE=_____
DBLIST=_______
TYPE: Information
REASON: None
ACTION: None
REFERENCES: None
+----------+
| ACT03001 |
+----------+
TEXT: ACTUALLO macro could not find any units with
Accounting installed. ACTUALLO is abending
TYPE: Error
REASON: This message lists the database unit ID,
database name, and database type.
ACTION: Check prefix.MICS.PARMS JCLDEF member for list
of components.
REFERENCES: Section 2.3.3.2.1 in the PIOM.
+----------+
| ACT03002 |
+----------+
TEXT: ACTUALLO macro will allocate the following
unit(s):
TYPE: Information
REASON: This informational message lists the database
unit IDs.
ACTION: None
REFERENCES: None
+----------+
| ACT03003 |
+----------+
TEXT: %ID(%NAME/%TYPE)
TYPE: Information
REASON: This informational message lists the database
unit IDs, database name, and database type.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.
+----------+
| ACT03004 |
+----------+
TEXT: ACTUALLO allocated DDN=_______
DSN=____
TYPE: Information
REASON: This informational message lists the allocated
ddnames and each allocated unit's data set name.
ACTION: None
REFERENCES: None
+----------+
| ACT03005 |
+----------+
TEXT: ACTUALLO freed DDN=_______
TYPE: Information
REASON: This informational message lists the ddnames
that are no longer allocated.
ACTION: None
REFERENCES: None
+----------+
| ACT03010 |
+----------+
TEXT: ACTCTCUP macro starting execution Checkpoint
function=________ Checkpoint
Year/Month=_______/______ Current
Year/Month=_______/______
TYPE: Information
REASON: None
ACTION: None
REFERENCES: None
+----------+
| ACT03011 |
+----------+
TEXT: CLOSETBL has already been successfully executed
in the current accounting period.
ACTCTCUP macro aborting.
TYPE: Error
REASON: The CLOSETBL job runs only once during an
accounting period because it ages the files in
the application database.
ACTION: CLOSETBL can be resubmitted after correcting
the problem, without running the RSTRTBLS or
the RSTRTLIB job, unless the CLOSETBL job
abends during the aging process. In that
case, you must first run the RSTRTBLS job as
described above, and then resubmit the
CLOSETBL job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.2.
+----------+
| ACT03012 |
+----------+
TEXT: _________ completed successfully
TYPE: Information
REASON: The identified process completed successfully.
ACTION: None
REFERENCES: None
+----------+
| ACT03013 |
+----------+
TEXT: CLOSETBL did not successfully complete in the
previous accounting period.
TYPE: Error
REASON: The CLOSETBL status in ACTCTC01 file is showing
incomplete, due to an error from the previous
run.
ACTION: Contact CA Technical Support for assistance with
this error. Have the MICSLOG listing available
for reference when you call.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.2.
+----------+
| ACT03019 |
+----------+
TEXT: ACTCTCUP macro successfully completed
TYPE: Information
REASON: The message indicates that the macro ACTCTCUP
was invoked and completed successfully.
ACTION: None
REFERENCES: None
+----------+
| ACT03032 |
+----------+
TEXT: _______ has been run in the current accounting
period.
TYPE: Information
REASON: The identified task has been run in the current
accounting period.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.2.
+----------+
| ACT03033 |
+----------+
TEXT: _______ has not been run in the current
accounting period
TYPE: Information
REASON: The identified task has not run in the current
accounting period.
ACTION: Run the identified task.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.2.
+----------+
| ACT03034 |
+----------+
TEXT: _______ ________ input is ____.
TYPE: Informational
REASON: The message indicates the type of input used for
this job.
ACTION: None
REFERENCES: None
+----------+
| ACT03035 |
+----------+
TEXT: ____ will be prorated.
TYPE: Informational
REASON: This message lists the type of input file that
is prorated. Message ACT03034 accompanies this
message to identify the input file.
ACTION: None
REFERENCES: MICSLOG message ACT03034
CA MICS Accounting and Chargeback User Guide,
Section 4.8.
+----------+
| ACT03036 |
+----------+
TEXT: YTD ________ input is ____.
TYPE: Informational
REASON: The message indicates the type of input used for
year-to-date.
ACTION: None
REFERENCES: None
+----------+
| ACT03037 |
+----------+
TEXT: Ledger file ________ in _______ does not contain
any observations.
TYPE: Warning
REASON: The ledger file identified in the message text
is empty.
ACTION: Check that CA MICS monthly ran correctly in
all Accounting and Chargeback units.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.1 and 5.2.
+----------+
| ACT03038 |
+----------+
TEXT: Ledger file ________ does not exist in _______.
TYPE: Error
REASON: This ledger file does not exist in the
indicated ddname. Message ACT03039 accompanies
this message to identify the database unit ID.
ACTION: Check that CA MICS monthly ran correctly in
all Accounting and Chargeback units.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.1 and 5.2.
+----------+
| ACT03039 |
+----------+
TEXT: Database is ______.
TYPE: Error
REASON: This message lists the types of jobs that have
not run in the current accounting period.
Message ACT03033 accompanies this message to
identify the jobs.
ACTION: Run the flagged jobs.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 5.2.
+----------+
| ACT03040 |
+----------+
TEXT: Monthly Complex Audit Tape Generation Started.
TYPE: Informational
REASON: None
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 7.4.
+----------+
| ACT03041 |
+----------+
TEXT: Monthly Complex Audit Tape Generation Bypassed.
TYPE: Informational
REASON: None
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 7.4.
+----------+
| ACT03042 |
+----------+
TEXT: _________ records written to _________
TYPE: Informational
REASON: This shows the number of records written to the
audit file.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 7.4.
$SCOL
+----------+
| ACT03043 |
+----------+
TEXT: Trial Balance invoice processing for ______
______ starting.
TYPE: Informational
REASON: The Accounting trial balance invoice processing
start for the month prior to CLOSETBL is run.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 6.1.7.
+----------+
| ACT03044 |
+----------+
TEXT: Ledger prorating has not been specified in
Accounting Options.
TYPE: Error
REASON: The Ledger File Prorating option was not
selected on the General Installation Accounting
Specifications panel.
ACTION: The ledger prorating option is activated by
specifying YES on the General Installation
Accounting Specifications panel
(MWF;4;2;3;2;1).
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.8.2.
+----------+
| ACT03058 |
+----------+
TEXT: Generation completed for journal file _______.
TYPE: Information
REASON: The selected journal file process is completed.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.3.1.1.
+----------+
| ACT03059 |
+----------+
TEXT: Both external and standard journal files are
active in this unit. External journal files
are not allowed in units with standard journal
files. MAGRUN abending. Contact CA Technical
Support.
TYPE: ERROR
REASON: Standard journal files and external journal
files must be activated in two different
units.
ACTION: Activate the standard and external files in
separate units.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.
+----------+
| ACT03060 |
+-------- -+
TEXT: External file update job abending because this
is not an external file unit. The unit contains
components other than MACT. See
prefix.MICS.PARMS(JCLDEF).
TYPE: ERROR
REASON: Unit-level external files can only contain the
Accounting component.
ACTION: Remove the component other than ACT in
prefix.MICS.PARMS(JCLDEF); then run JCLGENx
job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 2.3.4.
PIOM, Section 2.3.3.2.1.
$SCOL
+------- --+
| ACT03062 |
+------- --+
TEXT: Unit type has changed since the last MAGRUN
was run. Unit type at MAGRUN: ___. Current
unit type: ___. Contact CA Customer Support.
TYPE: ERROR
REASON: MAGRUN generated #ACTMSTR member with unit
type EXT for external journal files or unit
type DIA for the standard journal files.
ACTION: Update the journal file selection for the unit,
and run MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.3.1.
+----------+
| ACT03063 |
+----------+
TEXT: External file input routine must have
END=ACTEOF specified on the INFILE or SET
statement when duplicate date range checking
has been requested. External file update job
abending.
TYPE: Error
REASON: The date range validation option is turned on,
but the routine does not specify END=ACTEOF on
the INFILE or SET statement.
ACTION: When duplicate data checking is on for the
external journal file, you must do this:
1. Assign the unique timestamp to the ENDTS
element.
2. Put end=acteof on the set or INFILE
statement.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.3.1.7.2 .
+----------+
| ACT03064 |
+----------+
TEXT: Empty #ACTMSTR was generated because the Rate
Table did not have any selected journal files.
All external file update jobs will abend in this
unit.
TYPE: Error
REASON: At lease one journal file has to be selected in
the Rate Table in order to generate the #ACTMSTR
member in prefix.MICS.user.source
ACTION: Activate at least one journal and submit MAGRUN.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.3.1.
+----------+
| ACT03065 |
+----------+
TEXT: You have requested duplicate date-range
checking. You must assign a unique ENDTS value
in your input routine.
TYPE: Error
REASON: The date range validation option is turned on,
but the routine does not specify ENDTS on the
INFILE or SET statement.
ACTION: When duplicate data checking is on for the
external journal file, you must assign the
unique timestamp to the ENDTS element.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.3.1.7.2.
+----------+
| ACT03082 |
+----------+
TEXT: Journal file ______ ignored - component ___ is
not installed in this unit.
TYPE: Warning
REASON: The listed journal files are not installed in
the unit.
ACTION: Check prefix.MICS.PARMS JCLDEF member for a list
of components.
REFERENCES: Section 2.3.3.2.1 in the PIOM.
+----------+
| ACT03083 |
+----------+
TEXT: Euro conversion parameters have not been
defined.
USE MWF;4;2;3;2;7 to define them and rerun.
TYPE: Error
REASON: The lead and target currencies have not been
defined to enable currency conversion.
ACTION: To specify the required parameters, use the MWF
Euro Conversion Specifications panel (MWF
4;2;3;2;7).
Review the references below and determine the
correct specifications. Enter the required
specifications and rerun the job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 4.5.6.
$SCOL
+----------+
| ACT03084 |
+----------+
TEXT: Euro conversion parameters have been defined as:
Lead currency: _______ Target currency: _______
Conversion factor: ________
TYPE: Information
REASON: These values will be used by the Euro Rate Table
Conversion Utility.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03085 |
+----------+
TEXT: Invalid value specified for the REPPARM option:
________
Specify REPLACE or NOREPLACE and rerun.
TYPE: Error
REASON: An incorrect value was specified for the REPPARM
option used by the Euro Rate Table Conversion
Utility.
ACTION: To specify a valid option, edit the REPPARM data
definition in the Euro Rate Table Conversion
Utility. Rerun the job.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03086 |
+----------+
TEXT: REPPARM option was not specified. It defaults to
NOREPLACE.
Rate tables will not be replaced.
TYPE: Information
REASON: Because you did not specify a parameter for the
Euro Rate Table Conversion Utility's REPPARM
option, the default (NOREPLACE) will be used.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03087 |
+----------+
TEXT: REPPARM parameter specified as ________.
TYPE: Information
REASON: You specified a parameter for the Euro Rate
Table Conversion Utility's REPPARM option. It
controls whether the converted rate tables are
saved.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03088 |
+----------+
TEXT: Converting Rate Table for __.
TYPE: Information
REASON: Tells you which rate table is being converted to
euros.
ACTION: None
REFERENCES: None
+----------+
| ACT03089 |
+----------+
TEXT: Replacing Rate Table for __.
TYPE: Information
REASON: Tells you which rate table is being replaced.
In order for a converted rate table to replace
the existing rate table, the REPPARM option must
be specified as REPLACE.
ACTION: None
REFERENCES: None
+----------+
| ACT03090 |
+----------+
TEXT: No unit list specified. Rate tables of all
units with accounting installed will be
converted.
The complex-level rate table will be converted
if it exists.
TYPE: Information
REASON: You did not specify a parameter for the Euro
Rate Table Conversion Utility's UNITLIST option.
Therefore, all units with accounting installed
will have their rate tables converted. The
complex-level rate table will also be converted,
if it exists.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03091 |
+----------+
TEXT: Unit list specified as ________.
TYPE: Information
REASON: You specified a parameter for the Euro Rate
Table Conversion Utility's UNITLIST option. The
rate tables for these units will be converted.
If the list includes a $, the complex-level rate
table will be converted.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03092 |
+----------+
TEXT: Invalid unit id: _
No conversion for this unit id will be
attempted.
TYPE: Warning
REASON: The unit specified does not currently exist.
ACTION: The unit identifier must be a one-character
alphanumeric. Correct the unit identifier and
rerun the Euro Rate Table Conversion utility.
Use a $ to identify the complex-level rate
table.
REFERENCES: None
+----------+
| ACT03093 |
+----------+
TEXT: A rate has been reduced to zero as a result of
conversion:
_component_ _journal_ _algorithm_ _compcode_
_effective_date_
TYPE: Warning
REASON: Rates can have a maximum of six decimal places.
This message indicates that the rate for this
compcode is 0 after conversion and rounding.
ACTION: If a rate of 0 is not desired, change it.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03094 |
+----------+
TEXT: A rate is too large, after conversion, to fit in
the rate field
_component_ _journal_ _algorithm_ _compcode_
_effective_date_
The rate table for this unit cannot be converted
until this rate is reduced
TYPE: Error
REASON: The converted rate will not fit in the eight-
character rate field. Therefore, this converted
rate table cannot be saved.
If the REPPARM option is NOREPLACE, an after-
conversion rate report will be printed with
OVERFLOW displayed in the rate field. If the
REPPARM option is REPLACE, the utility will
abend.
ACTION: Reduce the rate for the compcode in question and
rerun utility.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03095 |
+----------+
TEXT: No conversion date was specified.
Specify a conversion date using the CONVDATE DD.
It must be in the form MM/DD/YY. Then rerun.
TYPE: Error
REASON: You did not provide the required CONVDATE value.
ACTION: Edit the CONVDATE data definition and enter a
CONVDATE value using the MM/DD/YY format and
rerun the utility
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03096 |
+----------+
TEXT: Invalid value specified for the conversion date:
________
Specify a conversion date in the form MM/DD/YY
and rerun
TYPE: Error
REASON: An invalid CONVDATE parameter value was
specified.
ACTION: To specify a valid value, edit the CONVDATE data
definition in the Euro Rate Table Conversion
Utility. The format is MM/DD/YY.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03097 |
+----------+
TEXT: Conversion date specified as: ________
TYPE: Information
REASON: You specified a value for the Euro Rate Table
Conversion Utility's CONVDATE parameter. It
controls the date when conversion rates will
take effect.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03098 |
+----------+
TEXT: The following algorithm specifications are being
dropped from the rate table:
_component_ _journal_ _algorithm_ _compcode_
_effective_date_
TYPE: Information
REASON: This message documents the actions of the Euro
Rate Table Conversion Utility. There is a limit
of two rows per compcode. These rows are not
being charged currently, and are being dropped
to make room for the conversion specifications.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03099 |
+----------+
TEXT: The following algorithm specifications are being
converted in place:
_component_ _journal_ _algorithm_ _compcode_
_effective_date_
TYPE: Information
REASON: This message documents the actions of the Euro
Rate Table Conversion Utility. The following
rows contain effective dates that are after the
conversion date. The rates for those rows are
being converted in place, with the effective
date left unchanged.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03100 |
+----------+
TEXT: The following algorithm specifications are being
converted with additional rows, effective
_tempdate_:
TYPE: Information
REASON: This message documents the actions of the Euro
Rate Table Conversion Utility. The following
rows contain no effective dates, or effective
dates that are before the conversion date.
Additional rows are being added for these
compcodes, with converted rates, and effective
dates set to the conversion date.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03101 |
+----------+
TEXT: _component_ _journal_ _algorithm_ _compcode_
_effective_date_
TYPE: Information
REASON: This message lists the characteristics of the
rate table rows being processed by the Euro Rate
Table Conversion Utility.
ACTION: None
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Appendix C.3.
+----------+
| ACT03210 |
+----------+
TEXT: The following Cost Centers have expended Budget
amounts and exceeded the user defined __%
Threshold.
COST CENTER
-----------------------------------------
-- __________
No Cost Center exceeded the user defined __%
Threshold. Report was not generated
TYPE: Information
REASON: This message lists the costs centers whose
budgeted amount exceeds the user-defined percent
threshold.
ACTION: This Budget Threshold Report can be very useful
in determining if the budget amount exceeds the
percent threshold.
REFERENCES: CA MICS Accounting and Chargeback User Guide,
Section 6.3.2.1.2.
Copyright © 2014 CA.
All rights reserved.
|
|