BusinessLink iSeries 400 Software Migration
Product: BusinessLink/WEB
Modified Date:

Successful migration of BusinessLink iSeries 400 software requires that all BusinessLink related user profiles and libraries are restored to the destination iSeries 400 while retaining all object authorities.

Note: changes to iSeries 400 serial number or TCP/IP addressing requires contact with BusinessLink Technical Support when migration is complete so appropriate modifications can be made.

Step 1 - Save BusinessLink Libraries
Different software versions will have different libraries to save. Any library in the following list must be saved if it exists:
  • ABL
  • ABLSPT
  • ATFM
  • ATFM19G

    Step 2 - Save BusinessLink User Profiles
    Different software versions will have different user profiles to save. Any user profile in the following list must be saved if it exists:
  • ATFMAUTO
  • ATFMOBJOWN
  • ATFMUSER
  • ATFMPGMR

    Step 3 - Note Twinax Device Names
    All dialup coprocessors will have a device description called 'AB_CONTROL' on the source iSeries 400. This twinax device is at address 0 on the primary twinax port of the coprocessor and is responsible for iSeries 400 - Coprocessor communications. A minimum requirement is that this device description be created on the destination iSeries 400. If other twinax devices need to be restored also, note their details as well.

    Step 4 - Restore Objects
  • Restore User Profiles
  • Restore Libraries
  • Restore Device Descriptions

    Step 4 - Start BusinessLink Subsystems / Verify Operation
  • Start BusinessLink Subsystems
  • Verify Remote Access Connection

    ** End of Technical Support Bulletin **