Installing the Agents

Installing the Agents

Installing the Agent for Databases

---

Installing the Agent for BS2000

This document describes the hotfix installation procedure for the BS2000 agent.

Because each BS2000 version requires its own agent, a one-character code has been assigned to each supported version. This code is used in the agent's file name and is described in the Terminology . In this document, the specific code has been replaced by the character "?."

Close the agent before you start the update installation.

Requirements

• The code $UC4 exists from the previous version.
• The TAR file on the installation CD can be unpacked using the already installed programs BS2 TAR or BS2 TOOLS (version 2.00W and later).

Supplied Installation Files

The files are packed in TAR files. The corresponding TAR file for each BS2000 version is found in the subdirectory IMAGE:AGENTS\BS2000. The file names indicate the current Automation Engine version. In the table below, the version has been replaced by the characters "x.xxx."

TAR files that contain "NK4" in their names are for NK4 pubsets and can also be unpacked with the BS2-TAR program.

 The CallAPI files and CallAPI implementation are described in a separate document.

Procedure

	1.	Transferring the TAR files to the host

• Admin computer
• Transfer the TAR file UCXJB2?.TAR or UCXJB2?NK4.TAR via FTP in text mode. 
• As an alternative, the TAR file can also be transferred to BS2000 with FTBS2000 or the EDT file transfer (also in text mode).

	2.	Unpacking the TAR files and setting up the system environment

• Host
• The TAR file can be unpacked in two ways:
1. Unpack with BS2 TAR:

   /FILE UCXJB2?.TAR,LINK=TAR or /FILE UCXJB2?NK4.TAR,LINK=TAR
   /EXEC BS2-TAR
    

2. Unpack with BS2 TOOLS:

   Show $UC4. Enter the command TAR into the command field next to the TAR file.

• The actual installation files are then created (with the version number as a prefix). The TAR file can be deleted after the files are unpacked.
• Delete or rename existing files from the previous version (except for INI and Enter files).
  Usually, the already adjusted enter job is not to be overwritten by the supplied sample job.
  Changes that might be necessary in the job are recorded in the Modification Archive.
  Likewise, the INI file is only to be adjusted if recommended in the Release Notes.
• Remove the prefix from the installation files.
•  Old files might still exist after the file names are changed. Check the Release Notes for old files.
•  The UCXJB2?M file must be shareable and the User ID and file name must correspond to the entry UC_EX_JOB_MD in the INI file.
•  The UCYBRFC? file must be shareable when the RFC mechanism is activated.

• Admin computer or user computer
• Adjust HEADER.BS2000, TRAILER.BS2000 and RESTART.BS2000 if necessary. See:Job - Execution.