Migrating Your IT Charge Manager Environment from SAS Version 6 to SAS Version 8

Introduction

You do not need to read this document if you are installing IT Charge Manger for the first time.

This document explains how to migrate your IT Charge Manger Release 2.0 (ITCM 2.0) that is currently running under SAS Version 6 to IT Charge Manager Release 2.3 (ITCM 2.3) running under SAS Version 8.  Please read through the instructions before acting on them, because the choices may make a difference at your site.

Preparation

  1. IMPORTANT! Make backup copies of your SAS Version 6 PDBs to be migrated.
  2. Verify that the release level of IT Service Vision (ITSV) on the server host is compatible with SAS Version 8 ITCM 2.3.  The release level of your ITSV should be 2.3 or later.  The release level of the SAS software that your ITSV installed on should be 8.1 or later. 
  3. Complete the migration of your ITSV Environment from SAS Version 6 to SAS Version 8 following the instructions in the document "Migrating Your IT Service Vision Environment from SAS Version 6 to SAS Version 8."  You should have the Version 6 ITSV PDBs successfully converted to Version 8 ITSV PDBs prior to migrating your ITCM environment.
  4. IMPORTANT! Make backup copies of the Version 8 ITSV PDBs.
  5. Make a backup copy of your ITCM 2.0 site definitions.  Whenever you invoke ITCM 2.0, you are greeted by the Welcome to IT Charge Manager window.  The Welcome window displays the Site Definition you have defined.  You may find the data set storing the site definition at your ITCM 2.0 installation path, drive:\[SAS Version 6 Install Path]\addon\cpe\chm\ec\ecsite\ec_sites.sd2.  To make a backup copy of this data set you need to use either the MS-DOS command or Windows Explorer to copy the ec_sites data set to a new location.

For example, if c:\sas6\addon\cpe\chm\ec\ecsite\ec_sites.sd2 is the site definition data set for ITCM 2.0, the MS-DOS command for making a backup copy in a new location, c:\backup, is

COPY c:\sas6\addon\cpe\chm\ec\ecsite\ec_sites.sd2 c:\backup

You will need to replace the default site definitions data set provided by ITCM 2.3 with this backup data set.  A later section in this document will walk you through the process of recovering your site definitions in ITCM 2.3.

  1. Install ITCM 2.3 on SAS Version 8 and the most recent maintenance package of ITCM 2.3 according to the Installation Guide for IT Charge Manager Software for Windows.

Your SASUSER Library

The first time you use ITCM 2.3, it will create a default SASUSER library, however, you may have information contained in your ITCM 2.0 SASUSER library and would like to continue to use it for ITCM 2.3.  Below are the instructions to copy the contents of the ITCM 2.0 SASUSER library to the ITCM 2.3 library.  

  1. Obtain the location of your ITCM 2.0 SASUSER library.  To determine this, invoke ITCM 2.0 and select Globals from the pull-down menu.  Click on Program Editor and type the following statements in the Program Editor window:

OPTIONS SOURCE NOTES;
LIBNAME SASUSER LIST;
PROC DATASETS DD=SASUSER;
RUN;

  1. Select Locals pull-down menu and click on Submit.
  2. Select Globals pull-down menu and click on Log.  You should see statements similar to below.  Your SASUSER library is identified by the label Physical Name.  In this example, the location of the SASUSER library is d:\SAS6\Addon\cpe\chm\ec\sasuser.

2 LIBNAME SASUSER LIST;
NOTE: Libref= SASUSER
Engine= V612
Filefmt= 607

Physical Name= d:\SAS6\Addon\cpe\chm\ec\sasuser

3 PROC DATASETS DD=SASUSER;

-----Directory-----

Libref: SASUSER
Engine: V612
Physical Name: d:\SAS6\Addon\cpe\chm\ec\sasuser

# Name Memtype Indexes
-----------------------------------------------------

1 EIS CATALOG
2 MBUSER DATA YES
3 PARMS CATALOG
4 PROFILE CATALOG
5 PROFILE2 CATALOG
6 SASMBC DATA YES
7 SASMBI DATA

4 RUN;

  1. Record the physical name of your Version 6 SASUSER library.  Exit ITCM 2.0 by selecting Exit IT Charge Manager and SAS.  
  2. Invoke IT Charge Manager Release 2.3 for SAS Version 8.  At the Welcome to IT Charge Manager window, press Exit and select Exit IT Charge Manager only.
  3. Select View from the pull-down menu and click on Program Editor.  Maximize the Program Editor window and type the statements shown at Step 1.
  4. Select Run pull-down menu and click on Submit.
  5. Select View pull-down menu and click on Log.  Maximize the Log window.  You should see the location of ITCM 2.3 SASUSER library indicated by Physical Name.  Record the physical name of your Version 8 SASUSER library.
  6. Select File pull-down menu and click on Exit to exit out of ITCM 2.3.  Now, you are ready to proceed the conversion of SASUSER library. 
  7. Invoke SAS Version 8 for Windows outside of ITCM 2.3.

NOTE: Do not invoke SAS Version 8 by launching ITCM 2.3.  Although the option exists to exit out of ITCM only and stay in SAS, the SASUSER library would be locked and could not be modified.

  1. In the Program Editor, type the following code, edit the location of your SASUSER libraries, and submit the edited code.

LIBNAME olduser 'location-of-your-ITCM 2.0-SASUSER-library' ACCESS=READONLY;
LIBNAME newuser 'location-of-your-ITCM 2.3-SASUSER-library';
PROC COPY IN=olduser OUT=newuser;
RUN;

  1. Select Log from the View pull-down menu.  You should see notes indicating that the contents of the old SASUSER have been successfully copied to the new SASUSER library.
  2. Select Exit from the File pull-down menu and exit out of SAS Version 8.

Your Site Libraries for IT Charge Manager

Below are the instructions of copying the contents of the ITCM 2.0 site libraries to the ITCM 2.3 site libraries.

  1. Obtain the location of your ITCM 2.0 site libraries.  An easy way to determine the location is to invoke ITCM 2.0 and select a site in the list box "Select Site to Administrator or Define."  You should see the IT Charge Manager Site Prefix in the Site Properties box below.  

If your ITCM 2.0 site prefix is OLDSITE, you should find the site libraries as following:

If your ITCM 2.0 site prefix is c:\oldsite, you should find the site libraries as following:.

  1. Decide your ITCM 2.3 site prefix.
  2. Allocate space for storing the ITCM 2.3 site libraries.

Run IEFBR14 or use ISPF 3.2 to allocate space for the ITCM 2.3 site libraries.  You will need to allocate the libraries as below for each site.  You may use the same DCB= as the one for the ITCM 2.0 library for allocation.  If your ITCM 2.3 site prefix is NEWSITE, allocate space for:  

If your ITCM 2.3 site prefix is c:\newsite, create the following directories:

  1. Copy the contents of the ITCM 2.0 site libraries to the ITCM 2.3 site libraries.
  1. Start with OLDSITE.EC.DATA and OLDSITE.EC.SITE.  These two libraries contain SAS objects such as catalogs, data sets, and views.  The SAS COPY procedure is used to convert the SAS objects from Version 6 to Version 8.

Invoke SAS Version 8 on the server host, type the following statements in the Program Editor window.  Edit the location of your ITCM site library and submit the edited code for the two libraries respectively.

LIBNAME oldlib 'location-of-your-ITCM 2.0-site-library' DISP=SHR;
LIBNAME newlib 'location-of-your-ITCM 2.3-site-library';
PROC COPY IN=oldlib OUT=newlib;
RUN;

For example, if OLDSITE.EC.SITE is your ITCM site library, the edited statements should be

LIBNAME oldlib 'OLDSITE.EC.SITE' DISP=SHR;
LIBNAME newlib 'NEWSITE.EC.SITE';
PROC COPY IN=oldlib OUT=newlib;
RUN;

If you check the ITCM 2.3 site libraries at this point, you should see SAS Version 8 objects, such as catalogs, data sets, and views, converted from the corresponding SAS Version 6 objects in the old site libraries.

  1. For the rest of the old site libraries, such as OLDSITE.EC.SCNTL and OLDSITE.EC.SLG, you need to use ISPF 3.3, IEBCOPY, or IEBGENER in a batch job to copy the contents to the new site libraries.  Depending on the data processed into your old site libraries, you may find that some of the libraries are empty. 
  1. Start with c:\oldsite\ec\data and c:\oldsite\ec\site.  These two libraries contain SAS objects such as catalogs, data sets, and views.  The SAS COPY procedure is used to convert the SAS objects from Version 6 to Version 8.

Invoke SAS Version 8 on the server host, type the following statements in the Program Editor window.  Edit the location of your ITCM site library and submit the edited code for the two libraries respectively.

For example, if c:\oldsite\ec\site is your ITCM site library, the edited statements should be

LIBNAME oldlib 'c:\oldsite\ec\site' ACCESS=READONLY;
LIBNAME newlib 'c:\newsite\ec\site';
PROC COPY IN=oldlib OUT=newlib;
RUN;

If you check the ITCM 2.3 site libraries at this point, you should see SAS Version 8 objects, such as catalogs, data sets, and views, converted from the corresponding SAS Version 6 objects in the old site libraries.

  1. For the rest of the old site libraries, such as c:\oldsite\ec\scntl and c:\oldsite\ec\slg, you need to either use the MS-DOS command or Windows Explorer to copy the contents to the new site libraries.  Depending on the data processed into your old site libraries, you may find that some of the libraries are empty.

For example, if c:\oldsite\ec\scntl is the site library, the MS-DOS command for copying the contents of the old site library to the new site library is

COPY c:\oldsite\ec\scntl\*.* c:\newsite\ec\scntl

Your PDBs

In the Preparation section earlier, you successfully migrated your PDBs from SAS Version 6 to SAS Version 8.  If you check the contents of the new Version 8 PDB, you should see nine standard ITSV libraries, e.g., detail, day, and so on, in the new PDB library.  If in doubt, check with your site's IT Service Vision administrator or the person who migrated the IT Service Vision environment from SAS Version 6 to SAS Version 8.

The following steps describe how to migrate the PDB contents that are ITCM-specific from the Version 6 PDB to the new Version 8 PDB.  

  1. Allocate space for storing the ITCM PDB libraries in the new Version 8 PDB.

Run IEFBR14 or use ISPF 3.2 to allocate space for the ITCM PDB libraries.  You may use the same DCB= as the one for the ITCM 2.0 library for allocation.  If your Version 8 PDB locates at NEWPDB, allocate space for:  

If your Version 8 PDB locates at c:\newpdb, create the following directories:

  1. Copy the contents of the Version 6 PDB libraries to the Version 8 PDB.
  1. In your Version 6 PDB, for example, OLDPDB, you should have three libraries, OLDPDB.EC.PDB, OLDPDB.EC.SUSP, and OLDPDB.EC.WORK.  These libraries contain SAS objects such as catalogs, data sets, and views.  You will need to run the SAS COPY procedure to convert the SAS objects from Version 6 to Version 8.  Depending on the data processed into your old PDB libraries, you may find that some of the libraries are empty. 

Invoke SAS Version 8 on the server host and type the following statements in the Program Editor window.  Edit the locations of your PDB libraries and submit the edited code for the three libraries respectively.

LIBNAME oldpdbec 'location-of-your-ITCM 2.0-PDB-library' DISP=SHR;
LIBNAME newpdbec 'location-of-your-ITCM 2.3-PDB-library';
PROC COPY IN=oldpdbec OUT=newpdbec;
RUN;

If OLDPDB.EC.PDB is your old PDB library, the edited statements should be

LIBNAME oldpdbec 'OLDPDB.EC.PDB' DISP=SHR;
LIBNAME newpdbec 'NEWPDB.EC.PDB';
PROC COPY IN=oldpdbec OUT=newpdbec;
RUN;

If you check the Version 8 PDB libraries at this point, you should see SAS Version 8 objects, such as catalogs, data sets, and views, converted from the corresponding SAS Version 6 objects in the old PDB libraries.

  1. For the rest of the libraries, such as OLDPDB.EC.CNTL, OLDPDB.EC.PLG, and OLDPDB.EC.SEQ, you need to use ISPF 3.3, IEBCOPY, or IEBGENER in a batch job to copy the contents to their corresponding libraries in the NEWPDB.  For instance, use ISPF3.3 to copy OLDPDB.EC.CNTL to NEWPDB.EC.CNTL.
  1. In your Version 6 PDB, for example, c:\oldpdb, you should have three libraries, c:\oldpdb\ec\pdb, c:\oldpdb\ec\susp, and c:\oldpdb\ec\work.  These libraries contain SAS objects such as catalogs, data sets, and views.  You will need to run the SAS COPY procedure to convert the SAS objects from Version 6 to Version 8.  Depending on the data processed into your old PDB libraries, you may find that some of the libraries are empty.

Invoke SAS Version 8 on the server host and type the following statements in the Program Editor window.  Edit the locations of your PDB libraries and submit the edited code for the three libraries respectively.

LIBNAME oldpdbec 'location-of-your-ITCM 2.0-PDB-library' ACCESS=READONLY;
LIBNAME newpdbec 'location-of-your-ITCM 2.3-PDB-library';
PROC COPY IN=oldpdbec OUT=newpdbec;
RUN;

If c:\oldpdb\ec\pdb is your old PDB library, the edited statements should be

LIBNAME oldpdbec 'c:\oldpdb\ec\pdb' ACCESS=READONLY;
LIBNAME newpdbec 'c:\newpdb\ec\pdb';
PROC COPY IN=oldpdbec OUT=newpdbec;
RUN;

If you check the Version 8 PDB libraries at this point, you should see SAS Version 8 objects, such as catalogs, data sets, and views, converted from the corresponding SAS Version 6 objects in the old PDB libraries.

  1. For the rest of the libraries, such as c:\oldpdb\ec\cntl, c:\oldpdb\ec\plg, and c:\oldpdb\ec\seq.sas, you need to use either the MS-DOS command or Windows Explorer to copy the contents to the new PDB libraries.

For example, if c:\oldpdb\ec\cntl is the PDB library, the MS-DOS command for copying the contents of Version 6 PDB library to the new PDB library is

COPY c:\oldpdb\ec\cntl\*.* c:\newpdb\ec\cntl

Your Account View Extract File

You may skip this section if you do not have the Account View extract file of ITCM 2.0.

The following are instructions of migrating your Account View extract file from ITCM 2.0 to ITCM 2.3:

  1. Obtain the location of your downloaded Account View extract file of ITCM 2.0.
  2. Decide the location on your computer where you want to store the Account View extract file of ITCM 2.3 migrated from ITCM 2.0.
  3. Convert the Account View extract file from ITCM 2.0 to ITCM 2.3. 

Invoke SAS Version 8 of Windows and type the following statements in the Program Editor window.  Edit the directories where your Account View extract files locate and submit the edited code.

LIBNAME oldav 'directory-where-your-ITCM 2.0 Account View-extract-file-locates' ACCESS=READONLY;
LIBNAME newav 'directory-where-your-ITCM 2.3 Account View-extract-file-locates';
PROC COPY IN=oldav OUT=newav;
RUN;

Launch IT Charge Manager Software, Release 2.3

  1. Before you invoke ITCM 2.3, you need to replace the default site definition provided by ITCM 2.3 with your own site definitions.  The default site definition may be found at drive:\[SAS Version 8 Install Path]\cpe\chm\ec\ecsite\ec_sites.sas7bdat.  Obtain the directory name of the backup ec_sites data set that you made in the Preparation section.  Invoke SAS Version 8 of Windows and type the statements below in the Program Editor window, edit it, and submit the edited code.

LIBNAME olddef 'directory-which contains-the-backup-ec_sites-table' ACCESS=READONLY;
LIBNAME newdef 'drive:\[SAS Version 8 Install Path]\cpe\chm\ec\ecsite';
PROC COPY IN=olddef OUT=newdef;
   SELECT EC_SITES;
RUN;

  1. Invoke IT Charge Manager Release 2.3 for SAS Version 8.  You should see your site definitions of ITCM 2.0 displayed at the Welcome to IT Charge Manager window.
  2. Select a site and modify the text fields, such as IT Charge Manger Site Prefix, displayed in the Site Properties box.  Check with your ITSV administrator if you need assistance for the following modifications.
  1. Click on the Save Properties button to save the information in the Site Properties box.
  2. Click on Open to open the site.
  3. If the site is on an OS/390 server host, press the Site Administration tab and click on Manage Site Defaults and Accounting Calendar.  Click on Execution Control on the right.  Modify the JCL parameters to correctly reflect the settings for your SAS Version 8 system.  Press OK to save the modifications.
  4. Under the Site Administration tab, click on Manage Site Defaults and Accounting Calendar.  Click on Calendar Definitions on the right.  Verify the calendar definitions for this site and click on OK.  This will update the definitions and upload them to the server.  This step is required to ensure the correct regeneration of the calendar definitions through ITCM 2.3.
  5. Choose a PDB of the site by clicking on the PDB selection button on the upper left corner.  Press the Manage PDBs tab.  Select Define Rate Models, Charges, and Assignments.
  6. If your site is on an OS/390 server host, click on Execution Control on the right.  Verify the JCL statements and click on OK.
  7. Click on Data Base Definition on the right.
  8. Select Apply Selections and Edit, Manual Submit and click on OK.  You should see the window of Edit and Submit CPDDUTL Batch Job.
  9. Verify the code of the batch job and make modifications if necessary.
  10. Click on Submit pull-down menu and select Save, Submit, and End to run the Data Base Definition job (CPDDUTL) for updating the dictionary.

For OS/390 server, you must disconnect from the site in ITCM 2.3 for the Data Base Definition job to complete.  ITCM 2.3 automatically detects this and presents a window to facilitate the disconnection as soon as you submit the job.

  1. To ensure that your batch jobs refer to the appropriate data sets in your new PDB and site libraries after the migration, regenerate the batch job code through the ITCM 2.3 graphical user interface.
  1. Press Operation tab at the ITCM 2.3 main window.  Select Consolidate Data.
  2. Select a proper invoice period and click on Apply selections and Edit, Manual Submit.  You should see the window of Edit and Submit CONSOL Batch Job.
  3. Verify the code and make necessary modifications.
  4. Save the batch job.  If appropriate, you may submit the job via the Submit pull-down menu at this time.
  5. Repeat steps a through d for other invoice periods.
  1. Press Reports tab at the ITCM 2.3 main window.  Select To-date Consolidation.
  2. Select a proper invoice period and click on Apply selections and Edit, Manual Submit.  You should see the window of Edit and Submit CONSOLz Batch Job.
  3. Verify the code and make necessary modifications.
  4. Save the batch job.  If appropriate, you may submit the job via the Submit pull-down menu at this time.
  5. Repeat steps a through d for other invoice periods.
  1. Press Operation tab at the ITCM 2.3 main window.  Select Run Standard Invoices.
  2. Select a proper invoice period and click on Apply selections and Edit, Manual Submit.  You should see the window of Edit and Submit SCHRPT Batch Job.
  3. Verify the code and make necessary modifications.
  4. Save the batch job.  If appropriate, you may submit the job via the Submit pull-down menu at this time.
  5. Repeat steps a through d for other invoice periods.
  1. Press Reports tab at the ITCM 2.3 main window.  Select To-date Reporting.
  2. Select a proper invoice period and click on Apply selections and Edit, Manual Submit.  You should see the window of Edit and Submit todate Batch Job.
  3. Verify the code and make necessary modifications.
  4. Save the batch job.  If appropriate, you may submit the job via the Submit pull-down menu at this time.
  5. Repeat steps a through d for other invoice periods.
  1. Press Reports tab at the ITCM 2.3 main window.  Select Site Configuration.
  2. Click on Apply selections and Edit, Manual Submit.  You should see the window of Edit and Submit conrpt Batch Job.
  3. Verify the code and make necessary modifications.
  4. Save the batch job.  If appropriate, you may submit the job via the Submit pull-down menu at this time.
  1. Repeat steps 5 through 14 for each PDB of the selected site.