Robot/NETWORK 9.0 Profiles
Introduction
To function properly, Robot/NETWORK 9.0 needs specific user profiles on the network’s iSeries or AS/400 systems. On every Host system in the network, Robot/NETWORK requires the user profiles RBTNETN, RBTNETPT, and RBTNETH. On every Node system in the network, Robot/NETWORK requires the user profiles RBTNETN and RBTNETPT. These profiles:
- Must be enabled.
- Are not registered in SNADS.
- Are created with SAVSYS special authority.
- Are members of the group profile of RBTUSER.
- Own only the data queues they use.
- Are shipped with their authority for *PUBLIC set to *USE (you can use the command RBTNETNODE/RBNCHGAUT to change their authority to *EXCLUDE).
The following table describes these profiles in greater detail.
| Profile | Description | Notes |
| RBTNETN | The user profile used by the Node monitor jobs, NETNODE and NETNODE2. |
Password is set to *NONE. |
| RBTNETPT | The user profile used to communicate between systems. |
Requires a password. The profile and Does not own any objects. |
| RBTNETH | The user profile used by the HOST monitor jobs: NETHOST1, NETHOST2, NETHOST3, NETHOST4 and NETNOTIFY (most customers do not use NETHOST3 and NETHOST4). |
Password is set to *NONE. |
These profiles were created for the following reasons:
- Corporate auditors requested that our objects be owned by our profiles.
- These profiles allow us to build a secure product for your environment.
- These profiles isolate Help/Systems’ products from changes made by IBM to their profiles—QSECOFR and QPGMR.
Caution
These profiles have specific authorities that allow Help/Systems’ products to perform certain functions on your system. Without these profiles, our products will not perform as designed. If you decide to change any of the attributes on the RBTNETN, RBTNETPT, or RBTNETH profiles, Help/Systems
cannot guarantee the stability of Robot/NETWORK and unexpected results may occur.
Updated July 13, 2001




