Installing the Agent for BS2000

This document guides you through the installation of a BS2000 agent. It describes how to install an agent in an AE system in which authentication is not used. Additional installation steps are required before the agent can be started and used if you intend to use one of the available authentication methods. For more information, see Agent Authentication.

Various BS2000 versions require their own agent; a one-character code is assigned to each supported version. This code is part of the agent's file name. In this document, the specific code is replaced by the character "?."

Requirements

• The User ID $UC4 in BS2000 must be set with approximately 10.000 PAM pages.
• The program BS2 TAR has been installed in BS2000. Unpack the TAR file from the supplied installation CD. For more information, see Program BS2-TAR and BS2000 Text Archive (TAR file).

  This might not be required when using BS2 TOOLS version 2.00W and later. BS2 TOOLS is used to receive files in a text archive and to unpack text archives.

Supplied Installation Files

The files are packed in TAR files. Each respective TAR file is stored in a subdirectory of IMAGE:AGENTS\BS2000, depending on the BS2000 variant. The file name indicates the current Automation Engine version. In the table shown below, the version is represented by the characters "x.xxx."

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

• File name: x.xxx.UCX2?.LIB

  Description: Program Library

  Library Elements:

  • UCXBB2?C: CallAPI Utility
  • UCXEB2?U: Utility for the console event (UCON connection)
  • UCXJB2?: Agent
  • UCXJB2?M: Message program for BS2000 agent
  • UCYBRFC?: Service program for RFC task
    For more information, see Service Program for Remote Function Call (RFC) Tasks.

• File name: x.xxx.UCXJB2?.INI
  Description: INI file for BS2000 agent

• File name: x.xxx.UCXEB2?U.INI
  Description: INI file for the utility

• File name: x.xxx.UCYEBXXZ
  Description: Utility for recalling commands through a console (only for console events)

• File name: x.xxx.E.UCXJB2?
  Description: Sample - Enter file for BS2000 agent

• File name: x.xxx.E.UCXEB2?U
  Description: Sample - Enter file for the utility

• File name: x.xxx.E.UCXEB2?U
  Description: Message Library

For information about CallAPI files and their implementation, see CallAPI for BS2000.

Potential Problems

• TSOS Rights
• K, NK
• PUBSET Right (Sysout)

To Install the Agent for BS2000

1. Transfer the TAR files to the host (admin computer).

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

2. Unpack the TAR files and set up the system environment (host).

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

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

   2. Unpacking with BS2 TOOLS:

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

   • The actual installation files are created. The TAR file can then be deleted.
   • Remove the prefix from the installation files.
   • Adjust the INI file and Enter job, see Agent BS2000.
   • Adjust HEADER.BS2000, TRAILER.BS2000 and RESTART.BS2000 if necessary, see Executing Jobs.

     The file UCXJB2?M must be shareable, and the user ID and file name must correspond to the INI file entry UC_EX_JOB_MD.

     The UCYBRFC? file must be shareable if the RFC mechanism is activated, see Service Program for Remote Function Call (RFC) Tasks.

3. Start the agent.

   • The AE system must be running (server computer), see Multi-Server Operation .
   • Start the agent under $TSOS (host).

     Set priority and category.
     An agent object is automatically created in system client 0000 and stored in the folder HOST.
     

   • Verify whether the agent is logged on (admin or server computer).
     • Start the AWI for client 0000. More detailed information about agents is provided in the Administration perspective. Because a newly logged-on agent has not yet been assigned a client, it can only be viewed in client 0000. The new agent can now be assigned to clients with the required rights using the Agent object. For more information, see Authorizations Page.

4. Shut down the agent (host) .

   • Quit the agent using the command /INTR Tsn, END or using the Task Manager of BS2 TOOLS.