4. Operation › 4.5 Integrating CA MICS Data to NSM › 4.5.1 Integration with NSM Chargeback › 4.5.1.2 TNGCBCSV - The Consolidation Utility

4.5.1.2 TNGCBCSV - The Consolidation Utility

Sharedprefix.MICS.CNTL(TNGCBCSV) creates the CSV files for
NSM Chargeback from the SAS data sets created by the TNGAD1
inquiry described in the previous section.

o  Specifying the SAS data libraries to include in the
   consolidation:  Edit sharedprefix.MICS.CNTL(TNGCBCSV).
   After the DSNLIST DD, list the SAS data libraries that the
   consolidation utility should include in the CSVs.  You do
   not have to run the utility for each SYSID separately, the
   program will parse the data set names and create one data
   set for each SYSID and year.

o  Specifying a date limit:  By default, TNGCBCSV will sum
   together all the data sets for a SYSID.  You may, however,
   specify a date limit using the TODATE parameter.  If the
   TODATE parameter is specified, only data sets for dates up
   to and including the TODATE are summed together.  You
   could use this to create a CSV only containing data for
   the previous month, for example.

   The TODATE parameter is specified in the SYSPARM parameter
   on the EXEC statement, in mmddyyyy format.

o  Specifying environmental parameters:  Review
   sharedprefix.MICS.SOURCE(BASUCBXT) for a description of
   the parameters available to define DASD requirements and
   other environmental details.  The parameters are
   implemented via SAS macro variables and can be overridden
   as needed.

o  Output Data Set Naming Conventions:  The data sets created
   by TNGCBCSV are named as follows:

   Data Set:  sharedprefix.MICS.TNGCB.YRyyyy.@ssss
     Member:  DUmmddCB

   where:
          yyyy   Is a four digit number denoting the year of
                 the run date or the year of TODATE.

          ssss   Is a four character system identifier
                 (SYSID).

          mm     Is the month of the data.

          dd     Is the day of the data.

   One data set is created per system, per year.  Within each
   data set there is one member per day.

   Note that the TODATE parameter affects the name of the
   data set.  If the TODATE parameter is not used, the year,
   month and day used in the data set and member name will be
   derived from the run date.  If the TODATE parameter is
   used, the year, month and day will be derived from TODATE.