Help/Systems SEQUEL Software PowerTech Skybot Software
Help/Systems
The World's Leader in IBM iSeries Software Solutions
Home › Support › Help/FACTS › Before You Add a New Node To Robot/NETWORK 9.0

Before You Add a New Node To Robot/NETWORK 9.0

Product: 
Robot/NETWORK

Before You Begin

This Help/FACTS describes the tasks you must perform before you can add (configure) a new Node to a network monitored by Robot/NETWORK.

Important: The person performing these tasks must have QSECOFR privileges.

If... Then...
You have performed an IPL of the new system since the first Help/Systems product was installed. Go to the On The Host procedure.
You have not performed an IPL of the new system since the first Help/Systems product was installed. You must either IPL the system or stop and restart the TCP Host server jobs. Then, go to the On The Host procedure.

On The Host

  1. From an OS/400 session on the network Host, ping the new Node using the command, ping newnodename.

    2. where: newnodename is the name of the new Node.

    If... Then...
    The name returned matches the name you entered. Go to Step 2.
    The name is not found, or if the name returned is fully-qualified (i.e., ends in .com).

    Do the following:

    Enter the command CFGTCP.

    Select option 10, Work with TCP/IP host table entries.

    Add a new system IP address and name.

    Go to Step 2.
  2. Repeat Step 1 using the command, ping hostname.

    3. where: hostname is the name of the network Host.

  3. Go to the On The New Node procedure.

On The New Node

  1. From an OS/400 session on the new Node, enter the command DSPNETA.
    2. If ... Then...
    The current system name is the name you want to use in Robot/NETWORK. Go to Step 2.
    The current system name is not the name you want to use in Robot/NETWORK. To change the system name, you must perform an IPL of the system and repeat Step 1.
  2. Page down two pages and check the value for DDM request access.
    3. If ... Then...
    DDM request access is equal to *OBJAUT (indicating there is no DDM checker). Go to Step 3.
    DDM request access is not equal to *OBJAUT (indicating there is a DDM checker).

    Your first attempt to configure the new Node will fail. After this failed attempt, you must do the following:

    Enroll the RBTNETPT profile into your DDM checker.

    Grant the RBTNETPT profile authority to the following functions: DDM, DRDA, DTAQ, and RMTCMD.

    Go to Step 3.

    Note: The person that performs these steps must have the necessary security authority.
  3. Enter the command CFGTCP and select option 12, Change TCP/IP domain information.
    4. If ... Then...
    The Host name is the same as the current system name displayed by the DSPNETA command and the Host name search priority is *LOCAL. Go to Step 4.
    The Host name is the same as the current system name displayed by the DSPNETA command but the Host name search priority is not *LOCAL.

    If you can change the Host name search priority to *LOCAL, change the priority and go to Step 4.

    If you cannot change the Host name search priority to *LOCAL, stop and call Help/Systems.
    The Host name is not the same as the current system name displayed by the DSPNETA command. Stop and call Help/Systems.
  4. Ping the new Node using the command, ping newnodename.

    5. where: newnodename is the name of the new Node.

    If ... Then...
    The name returned matches the name you entered. Go to Step 5.
    The name is not found, or if the name returned is fully-qualified (i.e., ends in .com).

    Do the following:

    Enter the command CFGTCP.

    Select option 10, Work with TCP/IP host table entries.

    Add a new system IP address and name.

    Go to Step 5.
  5. Repeat Step 4 using the command, ping hostname.

    6. where: hostname is the name of the network Host.

After You Are Done

You have completed all of the pre-configuration tasks and are ready to configure the Node. You will need to use the password ASABEKONE to configure the Node.

 

Updated July 28, 2005