Restoring job dependency files and hashed files

Restore job dependency and hashed files to the new installation.

  1. To restore each job dependency file, complete these tasks:
    1. Find the location for the file in the new IBM® InfoSphere® Information Server directory structure. For example, if the file was in the project directory in the previous installation, find the project directory to which you imported the project contents.
    2. Use operating system commands to copy the saved file to the required location. Verify that the file ownership and permissions will allow appropriate access by using your InfoSphere DataStage® credentials.
    3. Ensure that the job that references the file can locate it. If the file is referred to directly, you must edit the path name in the job design. If the file is referred to by a job parameter, you might need to edit the default value of the parameter to reference the new location for the file.
  2. To restore hashed files, complete these steps:
    1. Open the IBM InfoSphere DataStage and QualityStage® Director client and attach to the migrated project that uses the hashed files.
    2. Run or validate the job that creates the hashed files.
    3. Close all InfoSphere DataStage clients and stop the InfoSphere DataStage services.
    4. Locate the newly created files in the directory structure and copy the hashed files on top of them. For a dynamic file, ensure that the .Type30 file accompanies the DATA.30 and OVER.30 files in the hashed file directory.
  3. If the hashed files come from a computer that uses a different byte order, complete these steps. Note that file formats are compatible between certain operating systems. Files moved between Microsoft Windows, Suse, and Redhat should not require this step. The same is true for relocating files between IBM AIX®, HP-UX , and Z Linux®.
    1. Log in as dsadm or an equivalent user.
    2. Linux cue graphicUNIX cue graphicChange to the ../InformationServer/Server/DSEngine directory.
    3. Linux cue graphicUNIX cue graphicSource the dsenv file to set up the required environment variables: 
      ./dsenv
    4. Linux cue graphicUNIX cue graphicChange to the project home directory.
    5. Linux cue graphicUNIX cue graphicRun $DSHOME/bin/fnuxihash_file.
    6. Windows cue graphicRun ..\InformationServer\DSEngine\bin\fnuxihash_file.
  4. If the hashed files come from a non-globalized (non-NLS) installation and you are migrating to a globalized (NLS) installation, complete these steps to run the UNICODE.FILE:
    1. Log in as dsadm or an equivalent user.
    2. Linux cue graphicUNIX cue graphicChange to the ../InformationServer/Server//DSEngine directory.
    3. Linux cue graphicUNIX cue graphicSource the dsenv file to set up the required environment variables: 
      ./dsenv
    4. Run bin/uvsh (Linux or UNIX) or bin\uvsh (Microsoft Windows) to get the DSEngine shell prompt.
    5. The shell converts uppercase characters to lowercase characters, and vice-versa. To turn off this feature, enter the command PTERM CASE NOINVERT.
    6. Enter the command LOGTO project_name to change to the project.
    7. Enter the command UNICODE.FILE hash_file.
    8. Repeat steps f and g for each project.
    9. Enter QUIT to exit the DSEngine shell.
  5. Restart the InfoSphere DataStage services.