ClearPath IX Systems Installation and Configuration Guide
ClearPath IX Systems Installation and Configuration Guide ClearPath IX Systems Installation and Configuration Guide
Customizing the Site − DEPCON 2200 − DEPCON PC − UniAccess ODBC Integration Expert provides assistance ranging from totally automated services to step-bystep instructions. Capabilities include • Intrinsic capabilities—Fully automated solutions are provided. An example is basic print management for ClearPath IX servers. • Tools—Single-purpose applications are provided to help manage integrated technologies. For example, a configuration utility creates basic configurations to get ClearPath IX server software up and running. • Templates—Overall structures are provided that sites can customize. An example is the sample Excel macro for accepting OS 2200 application output. • Demonstrations—These provide ideas or techniques that can be used to develop a similar solution. An example is creating a distributed transaction between the UNIX and OS 2200 environments. • How To—Instructions, explanations, and background information are centralized and summarized for several tasks. References to product documentation are provided if more detailed information is needed. An example is the process for designing OLTP applications. The introductory overview describes the kinds of problems and solutions in each category. The overview for each category describes the problems and solutions in more detail and links directly to the appropriate process or procedure. 16.2. Customizing CMS 1100 To customize CMS 1100, execute the Config ACE tool included in Integration Expert. See the section of Integration Expert labeled Perform Basic Software Configuration for a ClearPath IX Server for complete details. The Config Ace tool provides an interactive interface that simplifies basic software configuration tasks for a ClearPath IX server. The dialogue for each product is in the form of a wizard that steps through the procedure and returns to the main Config Ace form when finished. Make sure you read the general prerequisites section as well as the CMS 1100 prerequisites section before customizing CMS 1100 using the Integration Expert Config Ace tool. Config Ace places the new CMS 1100 configuration in the following default output file: CLEARPATH*CMS.CONFIG/NODE1 (You can change the name of the output file using Integration Expert. The procedure below assumes the default name.) Follow these steps to start the newly configured CMS 1100 after using Config Ace to create the configuration: 16–2 Version 009B (Web Only) 7850 5104–009
Customizing the Site 1. Copy the new configuration file, CLEARPATH*CMS.CONFIG/NODE1, to the following file: CMS1100$*CONFIG$.CONFIG 2. At the 2200 node console, terminate the old CMS 1100 by entering the following keyin: II CMS TERM 3. Start the new CMS 1100 by entering the following keyin: ST STARTCMS,1 16.3. Considerations for the IX Network Identity Repository An IX Network Identity Repository contains management information base (MIB) data, such as network names, addresses, and object identifiers, needed to manage ClearPath IX server components using SPO Basic Edition when integrated with Unicenter TNG. You need to use Integration Expert to create the repository and add or remove network components to be managed. Use the ClearPath HMP IX Network Identity Repository Manager (RepoMan) tool to populate, update, and view the ClearPath HMP IX Network Identity Repository. See the section of Integration Expert labeled Update the ClearPath HMP IX Network Identity Repository for complete details. 16.3.1. Configuring CMS 1100 for the IX Network Identity Repository Before you set up an IX Network Identity Repository, the CMS 1100 configuration must include the following statements: Note: These statements are generated automatically when you use Integration Expert to configure CMS 1100. • A process statement for the IX network identity repository object manager, IXNAGX: PROCESS,IXNAGX PASSWORD,SNMP TYPE,TSAM Note: If you change the password to something other than SNMP, you also must change the IXNAGX runstream to specify a new password for the IXNAGX processor call. • An SNMP management statement enabling write access in order to update the repository. This write access can be restricted to community name and to specific IP addresses. The community name PUBLIC should not be given write access. SNMP-MGMT,snmp-mgmt-id COMMUNITY-NAME,community-name ; WRITE-ACCESS,YES ; [SECURITY-IP-ADDRESS,ip-address1] ; ... [SECURITY-IP-ADDRESS,ip-address10] ; where: snmp-mgmt-id 7850 5104–009 Version 009B (Web Only) 16–3
- Page 305 and 306: Installing and Configuring SPO Work
- Page 307 and 308: Section 12 Configuring Intel Nodes
- Page 309 and 310: Configuring Intel Nodes for Monitor
- Page 311 and 312: Configuring Intel Nodes for Monitor
- Page 313 and 314: Configuring Intel Nodes for Monitor
- Page 315 and 316: Configuring Intel Nodes for Monitor
- Page 317 and 318: Configuring Intel Nodes for Monitor
- Page 319 and 320: Configuring Intel Nodes for Monitor
- Page 321 and 322: Section 13 Installing the Basic OS
- Page 323 and 324: Installing the Basic OS 2200 IOE Yo
- Page 325 and 326: Installing the Basic OS 2200 IOE 5.
- Page 327 and 328: Installing the Basic OS 2200 IOE 2.
- Page 329 and 330: Installing the Basic OS 2200 IOE Yo
- Page 331 and 332: Section 14 Verifying the Interconne
- Page 333 and 334: 14.2.1. Installing HLC-2 Microcode
- Page 335 and 336: Verifying the Interconnects and Ach
- Page 337 and 338: Verifying the Interconnects and Ach
- Page 339 and 340: Verifying the Interconnects and Ach
- Page 341 and 342: Verifying the Interconnects and Ach
- Page 343 and 344: Verifying the Interconnects and Ach
- Page 345 and 346: Verifying the Interconnects and Ach
- Page 347 and 348: Section 15 Installing the Remaining
- Page 349 and 350: 15.2.2. Setting Up the TIP Environm
- Page 351 and 352: APP 3 ROLLBACK INITIALIZATION START
- Page 353 and 354: INAP3 MAX PAGES Installing the Rema
- Page 355: Section 16 Customizing the Site Cus
- Page 359 and 360: Customizing the Site 5. Verify your
- Page 361 and 362: Customizing the Site A dialogue box
- Page 363 and 364: Customizing the Site lan-address la
- Page 365 and 366: 14. Select the Changes menu bar ite
- Page 367 and 368: Customizing the Site b. Select CP_U
- Page 369 and 370: Customizing the Site l. Repeat thes
- Page 371 and 372: 16.6. Testing TCP/IP Communications
- Page 373 and 374: Customizing the Site ClearPath IX50
- Page 375 and 376: Section 17 Installing Optional OS 2
- Page 377 and 378: Appendix A Tables of Documentation,
- Page 379 and 380: Major Hardware or Software Changes
- Page 381 and 382: Major Hardware or Software Changes
- Page 383 and 384: Intel Platform Tables of Documentat
- Page 385 and 386: Tables of Documentation, Support, a
- Page 387 and 388: Appendix B Communication Settings S
- Page 389 and 390: Communication Settings Specific to
- Page 391 and 392: Appendix C SPO/HMP IX Interface Lic
- Page 393 and 394: SPO/HMP IX Interface License Key Re
- Page 395 and 396: Appendix D Configuring the FDDI Int
- Page 397 and 398: INVENTORY_INCLUDE: Limited Comprehe
- Page 399 and 400: The HLC-2 Subsystem Connections FDD
- Page 401 and 402: Appendix E Installing OPE and SysAd
- Page 403 and 404: Glossary A ACID properties The esse
- Page 405 and 406: Glossary central electronics comple
Customizing the Site<br />
− DEPCON 2200<br />
− DEPCON PC<br />
− UniAccess ODBC<br />
Integration Expert provides assistance ranging from totally automated services to step-bystep<br />
instructions. Capabilities include<br />
• Intrinsic capabilities—Fully automated solutions are provided. An example is basic<br />
print management for <strong>ClearPath</strong> <strong>IX</strong> servers.<br />
• Tools—Single-purpose applications are provided to help manage integrated<br />
technologies. For example, a configuration utility creates basic configurations to get<br />
<strong>ClearPath</strong> <strong>IX</strong> server software up <strong>and</strong> running.<br />
• Templates—Overall structures are provided that sites can customize. An example is<br />
the sample Excel macro for accepting OS 2200 application output.<br />
• Demonstrations—These provide ideas or techniques that can be used to develop a<br />
similar solution. An example is creating a distributed transaction between the UN<strong>IX</strong><br />
<strong>and</strong> OS 2200 environments.<br />
• How To—Instructions, explanations, <strong>and</strong> background information are centralized <strong>and</strong><br />
summarized for several tasks. References to product documentation are provided if<br />
more detailed information is needed. An example is the process for designing OLTP<br />
applications.<br />
The introductory overview describes the kinds of problems <strong>and</strong> solutions in each category.<br />
The overview for each category describes the problems <strong>and</strong> solutions in more detail <strong>and</strong><br />
links directly to the appropriate process or procedure.<br />
16.2. Customizing CMS 1100<br />
To customize CMS 1100, execute the Config ACE tool included in Integration Expert. See<br />
the section of Integration Expert labeled Perform Basic Software <strong>Configuration</strong> for a<br />
<strong>ClearPath</strong> <strong>IX</strong> Server for complete details.<br />
The Config Ace tool provides an interactive interface that simplifies basic software<br />
configuration tasks for a <strong>ClearPath</strong> <strong>IX</strong> server. The dialogue for each product is in the form<br />
of a wizard that steps through the procedure <strong>and</strong> returns to the main Config Ace form<br />
when finished. Make sure you read the general prerequisites section as well as the CMS<br />
1100 prerequisites section before customizing CMS 1100 using the Integration Expert<br />
Config Ace tool.<br />
Config Ace places the new CMS 1100 configuration in the following default output file:<br />
CLEARPATH*CMS.CONFIG/NODE1<br />
(You can change the name of the output file using Integration Expert. The procedure<br />
below assumes the default name.)<br />
Follow these steps to start the newly configured CMS 1100 after using Config Ace to create<br />
the configuration:<br />
16–2 Version 009B (Web Only) 7850 5104–009