Migrating an instance of Alliance FTP Manager to Assure Secure File Transfer - 7.0

Assure Security Installation (Manual) Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure Security > Assure Elevated Authority Manager (EAM)
Assure Security > Assure Encryption
Assure Security > Assure Secure File Transfer
Assure Security > Required for All Modules
Assure Security > Assure Monitoring and Reporting (AMR)
Assure Security > Assure Security Multi-Factor Authentication (MFA)
Assure Security > Assure DB2 Data Monitor (DB2MON)
Assure Security > Assure System Access Manager (SAM)
Assure Security > Assure Secure File Transfer with PGP
Version
7.0
Language
English
Content type
Installation (Manual) Guide
Product name
Assure Security
Title
Assure Security Installation (Manual) Guide
Copyright
2023
First publish date
1999
Last updated
2025-01-05
Published on
2025-01-05T12:58:06.220000
You must have an instance of Assure Security available that has license keys for the Assure Secure File Transfer feature before you start the migration. You must also ensure that the Alliance product is installed at a version listed in Supported upgrade and migration paths.
Note: If FTP Manager was installed in an iASP, it is necessary to set the ASP group before running the migration. To set the ASP group, run the following command:

SETASPGRP ASPGRP(ASPNAME)

where ASPNAME is the name of the iASP in which FTP Manager is installed

Do the following:

  1. End the FTP Manager product in library ALLFTM100. Run the following command:
    ENDSBS SBS(ALLFTM100) OPTION(*IMMED)
  2. Optionally, clear the ANLOGA file in the ALLFTM100 library to reduce the time required for the migration. The ANLOGA file contains all the logs for FTP Manager. If you want to retain the logs without copying them, back up the ANLOGA file before clearing it.
    To clear the ANLOGA file, end the ALLFTM100 subsystem and run the following command:
    CLRPFM FILE(ALLFTM100/ANLOGA)
    Alternatively, you can clear logs before a specified date and keep the later ones. To retain some logs but not all, end the ALLFTM100 subsystem and run the following command:
    FTMSTRMNT PRGDATE(yyyymmdd) PRGWRKFIL(*YES) PRGHIST(*YES) PRGLIBSCAN(*YES)
    where yyyymmdd represents the date specified. This method generally takes longer to run.
  3. Optionally, remove all files beginning with an "F" in the "/Alliance/SSH" directory to reduce the time required for the migration. The F* files are work files which are not required for Assure Secure File Transfer. To remove the files, end the ALLFTM100 subsystem and run the following command:
    RMVLNK OBJLNK('/Alliance/SSH/F*')
  4. Access the main menu for Assure Security using the command:
    product-library-name/SECMAIN
  5. Select option 8, Secure File Transfer (FTP) Management Menu.
  6. From the Assure Secure File Transfer (FTP) Management Main Menu, select option 1, Installation menu.
  7. From the FTP Management Installation Menu, select option 20 (Migrate ALLFTM100 library).
  8. A confirmation panel appears. To continue with the migration, press Enter.
  9. If FTP Manager was installed in an iASP and scans libraries in the iASP, the FTMSTRT job description for Library Scans must be adjusted to add the initial ASP group to the SCAN_LIBR job:
    CHGJOBD JOBD(SECOPS/FTMSTRT) INLASPGRP(iASP_name)
    The library used for archived library files after they have been processed must also be a library that is in the iASP. If Library Scans used the ALLFTM100B library for archiving files, the migration will change the library to SECOPS_0 which will reside in the system ASP. This must be changed to a library in the iASP. The setting for where files are archived can be found by starting on the AMMAIN menu (GO AMMAIN), take option 2 for the configuration menu, option 4 to work with scan libraries, then option 12 by any Library Scans that are used to see the File Action. Each File Action has its own archive settings on the 2nd panel of the File Action.
    If FTP Manager was monitoring any output queues in an iASP, the FTMSPLQ job description must also be changed:
    CHGJOBD JOBD(SECOPS/FTMSPLQ) INLASPGRP(iASP_name)
    Monitored output queues can archive processed spool files to an output queue that resides in an iASP or the system ASP.
    If FTP Manager has user defined exit programs that are located in an iASP, the FTMDIRS job description will need to be changed:
    CHGJOBD JOBD(SECOPS/FTMDIRS) INLASPGRP(iASP_name)
Any configuration for Assure Secure File Transfer created in the product library for Assure Security will be replaced by the configuration migrated from the ALLFTM100 library.

The following subdirectories are migrated as follows:

Subdirectory Migrated to:
/ALLIANCE/PDF /VISIONSOLUTIONS/SECOPS/product-library-name/PDF
/PGP /VISIONSOLUTIONS/SECOPS/product-library-name/PGP
/ALLIANCE/SSH /VISIONSOLUTIONS/SECOPS/product-library-name/SSH
Note: FTP Manager job description attributes are copied to the corresponding Assure Security job descriptions from service pack 7.0.08.00 and later. Service packs prior to 7.0.08.00 do not copy job description attributes from FTP Manager to the corresponding Assure Security job descriptions. The job descriptions are also renamed during the migration as follows:
FTP Manager job description attribute Assure Security job description
ALLAESKEY AESKEY
ALLAESTAP AESTAP
ALLFTMAUTS FTMAUTS
ALLFTMDIRS FTMDIRS
ALLFTMENCR FTMENCR
ALLFTMEXEC FTMEXEC
ALLFTMMQSS FTMMQSS
ALLFTMPRG FTMPRG
ALLFTMRTY FTMRTY
ALLFTMSCAN FTMSCAN
ALLFTMSNMP FTMSNMP
ALLFTMSPLQ FTMSPLQ
ALLFTMSSH FTMSSH
ALLFTMSTRT FTMSTRT
ALLFTMUSR FTMUSR
ALLFTM100 FTMJOBD