Installing the Agent for NSK

Installing the Agents

Installing the Agent for PeopleSoft

---

Installing the Agent for OS/400

This document describes the hotfix installation procedure for the OS/400 agent.

A three-figure abbreviation is provided for each supported OS/400 version. It is part of the agent's file name and is described in the Terminology (O41 for OS/400 version V4R1M0 and later).

Terminate the agent before you start the update installation.

Requirements

• TCP/IP

Supplied Files

The OS/400 agent is supplied as a binary SavFile. This file can be found in the subdirectory IMAGE:AGENTS\AS400.

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

Procedure

	1.	Transferring the file to the host

• Host
• Create a temporary library for Save File:

  CRTLIB LIB(UC4TMP)

• Create an empty Save File.

  CRTSAVF FILE(UC4TMP/UC4)

• Create a library for restoring the Save File.

  CRTLIB LIB(UC4AUSL) TYPE(*PROD) TEXT('Automation Engine version 11.0.0')

• Admin computer
• Log on to AS/400 via FTP and transfer UCXJO41.bin to the Save File UC4, UC4TMP library.
  Example for FTP via the Windows command prompt:

  ftp <MY.AS400>
  <USER>
  <PASSWORD>
  cd UC4TMP
  bin
  put UCXJO41.bin UC4
  quit

	2.	Creating the library

• Host
• Create the library.

  RSTOBJ OBJ(*ALL) SAVLIB(UC4AUSL) DEV(*SAVF) SAVF(UC4TMP/UC4)

• Delete the temporary library.

  DLTLIB LIB(UC4TMP)

• Rename the library.

  RNMOBJ OBJ(QSYS/UC4AUSL) OBJTYPE(*LIB) NEWOBJ(UC4)

	3.	Setting up the system environment

• Host
  The AE system must be running.
  
• Host
  Adjust the INI fileUC4/INI(UCXJO41).

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

There are two different methods that can be used to start the agent. Variant 1 requires a CL routine per agent that should start (more complex). Variant 2 starts or ends the agent via separate programs. 

Method 1

	4.	Creating the start and end programs

• Host
• The CL example programs that start and end the agent are provided in the supplied file member CLLE. They must be adjusted to the installation and the OS before you can compile them.

  UC4/CLLE(UCEX_RUN) - starts the agent
  UC4/CLLE(UCEX_END) - ends the agent 

	5.	Starting or ending the Agent

• Host
• You can use the program UCEX_RUN to start the agent.
  An Agent object is automatically created in the system client 0000 and stored in the HOST folder.
• The program UCEX_END ends the agent.
• Admin computer or Server computer
• Verify that the agent is logged on.  
  • Start the UserInterface for client 0000. Information about agents is available in the System Overview. A newly logged-on agent is only visible in client 0000 because it has not yet been assigned to a client. Via the Agent object, you can now assign the new agent including the required rights to the particular clients.

Method 2

	4.	Including the library in the library list

• Host
• The library (UC4) that includes the programs (such as the agent or CallAPI) must be included in the library list. You can use the following commands for this purpose:

  ADDLIBLE UC4
  adds the library to the library list
  
  or:
  CHGCURLIB UC4
  changes the current library for the particular job to UC4

	5.	Starting or ending the Agent

• Host

• Start the agent by using the command STRUCAGENT.
  The following examples explain the agent's starting procedure:
  
  STRUCAGENT LIB(UC4) FILE(UC4/INI) MBR(UCXJO41)
  Starts the agent from the library by using the INI file UC4/INI(UCXJO41).
  
  STRUCAGENT LIB(UC4) PATH('/user/uc4/ucxjo41.ini')
  Starts the agent from the library by using an INI file that is stored in the IFS file system.
  
  

• The command ENDUCAGENT ends the agent.
  
  ENDUCAGENT LIB(UC4) OPTION(*CNTRLD)
  Ends the agent that has been started from the library in a controlled manner.
  
  ENDUCAGENT LIB(UC4) OPTION(*IMMED)
  Aborts the agent that has been started from the library with ENDJOB.

• For further information about commands, see: KnowledgeBase.