Scenario RTE04: Converting a hub monitoring server to a remote
If you add a high-availability hub, or you clone a runtime environment (RTE) which has a hub monitor server in it, you might need to convert a hub monitoring server to a remote. In addition to converting the monitoring server, you must configure it to report to a hub.
Before you begin
Procedure
- Select the RTE in which you want to convert the monitoring server by specifying the fully-qualified name of the RTE (RTE_PLIB_HILEV and RTE_NAME).
- From the Primary Options menu, select Customize
PARMGEN configuration profiles.
The Customize PARMGEN Configuration Profile Members panel is displayed.
KCIP@PG6 ------ CUSTOMIZE PARMGEN CONFIGURATION PROFILE MEMBERS --------------- Option ===> Quick Configuration Mode (Required) Customize the RTE profile and the $GBL$USR user profiles: (Tip) Review KCIJPDLA autodiscovery job in Utility menu or type DLAJOB cmd. *1. SYSA RTE LPAR-specific CONFIG profile in WCONFIG (User copy) *2. $GBL$USR Global parameters CONFIG profile in WCONFIG (User copy) (Required) Customize the Variables profile if RTE_SYSV_SYSVAR_FLAG=Y: *3. SYSA Variables (system, user) CONFIG profile in GBL_USER_JCL PARMGEN global library (TDITN.IDTST.PARMGEN.JCL). Add/Modify system/user-defined symbols and their resolution values, for override variables used as parameter values in the $DOCRTE RTE and $GBL$USR global profiles. (Tip) Review/Customize WCONFIG Kpp$C*/Kpp$P*/Kpp$S* user imbeds: (Cloning Tip) Review KCIJPCCF job in Utility menu prior to customization. 4. WCONFIG TDITN.IDTST.$DOCRTE.WCONFIG (Tip) Review if you want to compare with IBM-supplied default profile values: 5. $CFG$IBM RTE LPAR-specific CONFIG profile in WCONFIG (IBM copy) 6. $GBL$IBM Global parameters CONFIG profile in WCONFIG (IBM copy) (Optional) Override SYSIN member to supply additional (User) profiles: 7. $SYSIN $PARSE/$PARSESV SYSIN controls (CONFIG/SELECT MEMBER) Press F1=Help for more information. Type UTIL to access utility menu. - Select option 1 to edit the RTE configuration profile.
- Reconfigure the monitoring server as follows.
If the environment is enabled for system variables, use variables to configure these values. You will also need to customize the variables profile before returning to the main Workflow panel.
- Change the KDS_TEMS_TYPE value
from HUB to REMOTE.
ISREDDE2 TSTEST.&userid.LPAR1.WCONFIG(LPAR1) Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000602 KDS$ BEGIN *--------- TIVOLI ENTERPRISE MONITORING SERVER --------* 000603 ** ============================ ================================ 000604 ** PARMGEN CONFIG Parameter PARMGEN CONFIG Value 000605 ** ============================ ================================ 000606 000607 ** TEMS configuration values: 000608 KDS_TEMS_TYPE REMOTE * HUB or REMOTE * ****** **************************** Bottom of Data **************************** - Do an EXCLUDE FIND on all KDS_HUB references.
(For information on the XF (“EXCLUDE FIND") macro, see XF edit macro.) Then specify the values for the hub to which
this remote monitoring server will connect.
SP22 TSTEST.&userid.LPAR1.WCONFIG(DEMO) Command ===> XF KDS_HUB Scroll ===> CSR 000829 000830 ** Note: The KDS_HUB_* values populate the xKANPARU(KDCSSITE) member 000831 ** that Remote TEMS reads to know how to connect to its Hub. 000832 KDS_HUB_TEMS_NAME_NODEID "PLBHUB" 000833 000834 ** If the TEMS is a Remote and requires VTAM SNA support: 000835 KDS_HUB_VTAM_APPL_GLB_BROKER "" * Hub KDS_TEMS_VTAM_APPL_GLB_BROKER 000836 KDS_HUB_VTAM_NETID "" * Hub KDS_TEMS_VTAM_NETID 000837 000838 ** If the TEMS is a Remote and requires TCP/IP support: 000839 KDS_HUB_TCP_HOST "OMEGHUB" 000840 000841 ** If the TEMS is a Remote, specify port numbers of its Hub: 000842 KDS_HUB_TCP_PIPE_PORT_NUM nnnnn * Hub KDS_TEMS_TCP_PIPE_PORT_NUM 000843 KDS_HUB_TCP_UDP_PORT_NUM nnnnn * Hub KDS_TEMS_TCP_UDP_PORT_NUM 000844 KDS_HUB_TCP_PIPE6_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6_PORT_NUM 000845 KDS_HUB_TCP_UDP6_PORT_NUM "" * Hub KDS_TEMS_TCP_UDP6_PORT_NUM 000846 KDS_HUB_TCP_PIPES_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPES_PORT_NUM 000847 KDS_HUB_TCP_PIPE6S_PORT_NUM "" * Hub KDS_TEMS_TCP_PIPE6S_PORT_NUM - - - - - - - - - - - - - - - - - - 853 Line(s) not Displayed ****** **************************** Bottom of Data **************************** - Press F3 to save the changes and return to the main Workflow panel.
- Change the KDS_TEMS_TYPE value
from HUB to REMOTE.
- Select Create the RTE
members and jobs. The $PARSE/$PARSESV : Create the RTE Members and Jobs panel is displayed.Note: If you are reconfiguring an RTE in which variables are enabled, the $PARSESV panel is displayed instead of $PARSE, as in the following example.
KCIP@PR1 -------------- CREATE THE RTE MEMBERS AND JOBS ----------------------- Option ===> Select option 1 to SUBMIT the full $PARSE job in WCONFIG for RTE=SYSA. $PARSE composite job creates product runtime members and jobs in all the PARMGEN WK* work libraries. Tips: o: Press F5 to access the library-specific $PARSE* jobs (ideal in an RTE reconfiguration scenario). First-time RTE deployment must run $PARSE. o: Select R to submit the KCIJPUP1 job to refresh the IK* product and WCONFIG *$IBM profiles before recreating the runtime members. Enter ns (1s-2s) for detailed job/task status. Description Job Name Status Date ---------------------------------------------- -------- --------- ---------- R Refresh IK* templates/WCONFIG *$IBM profiles. KCIJPUP1 1. Create runtime members/jobs in all WK* libs. $PARSE Press F1=Help for more information. Type UTIL to access utility menu. - Select option 1 to submit the generated
$PARSE (or $PARSESV) composite job. The JCL for the $PARSE (or $PARSESV) job is displayed.
- Review the job and submit it, then return to the main Workflow
panel. Tip: If you receive a bad return code (over 0004), enter 3s to view detailed status for the job. Use the online help to understand the error messages.
- From main menu, select Submit batch jobs to
complete PARMGEN setup The Submit Batch Jobs to Complete PARMGEN Setup panel (KCIP@SUB) is displayed.
- Depending upon your environment, complete one of the following
sets of steps:
- If your environment does not have system variables enabled:
- Select option 1 to submit the KCIJPSUB composite submit job, or, to submit each job
individually, select the other options.
KCIP@SUB -------- SUBMIT BATCH JOBS TO COMPLETE PARMGEN SETUP ----------------- Option ===> Select option 1 to SUBMIT the composite jobs in WKANSAMU for SYSA RTE. Tip: Review the SUBMIT commands in the KCIJPSUB composite job. Alternatively, select other options (2-12) to submit each job individually. Enter ns (1s-12s) for detailed job/task status. Description REQ Job Name Status Date --------------------------------------- ----- -------- --------- ---------- More: + 1. Composite SUBMIT job (See JCL comments) KCIJPSUB ** or ** 2. Allocate runtime RO and RW datasets (Yes) KCIJPALO 3. Copy SMP/E mbrs from TK*->RK* RO libs (Yes) KCIJPLOD 4. Run product security steps (Yes) KCIJPSEC 5. Update variable-named runtime mbrs (No ) KCIJPUPV 6. (Re)Create USS runtime mbrs in RKANDATV (Yes) KCIJPUSP 7. Create USS dirs./ (Re)Copy USS files (Yes) KCIJPUSS 8. Copy runtime mbrs to SYS1-type libs (Caution) KCIJPSYS 9. Run post-SMP/E RKANMODU ASM/LINK steps (Yes) KCIJPLNK 10. Verify the configuration jobs (Tip) KCIJPIVP 11. Back-up RK* product execution user libs (Tip) KCIJPCPR 12. Copy runtime mbrs from WK*->RK* RW libs (Yes) Enter 12 for details. Press F1=Help for more information. Type UTIL to access utility menu.If you select option 1, first review the KCIJPSUB job, and edit the job according to which of the conditional jobs need to be submitted automatically.
- Select option 1 to submit the KCIJPSUB composite submit job, or, to submit each job
individually, select the other options.
- If your environment has system variables enabled:
- On the Submit Batch Jobs to Complete PARMGEN Setup, select option 1 if
you want to submit the KCIJPSUB composite SUBMIT job, or select the other options to submit each job
individually. If you select option 1, review the KCIJPSUB job first and edit the job according to
which conditional jobs need be submitted automatically. If you select option 1, you are prompted
with the following message:
----------------------------- PARMGEN MESSAGES ----------------------------- Command ===> The KCIJVSUB composite job submits several PARMGEN configuration jobs via TSO SUBMIT commands. Some of those SUBMIT commands are commented out. Carefully review the comments in the JCL to determine which of those jobs you do or do not want to submit. Uncomment the SUBMIT commands of those jobs that you want to submit. Do NOT delete any SUBMIT commands as they may be needed in the future. - Press Enter. The following message is displayed:
----------------------------- PARMGEN MESSAGES ----------------------------- Command ===> In a system variable environment, job KCIJVSUB runs $PARSESV to customize then submit the KCIJPSUV job. EDIT and modify the KCIJPSUV job as appropriate. See comments in the JCL for further information. DO NOT MANUALLY SUBMIT THE KCIJPSUV JOB! - Press Enter to edit the KCIJPSUB job.
Jobs that require authorization or are conditional are not submitted automatically. You must either submit them manually, or uncomment them to run automatically.
- Press F3, and you are automatically be presented with the KCIJVSUB job for submission. Submit the job. Check the status of each of the jobs submitted. The allocation and load jobs must run successfully, or others jobs will not run.
- On the Submit Batch Jobs to Complete PARMGEN Setup, select option 1 if
you want to submit the KCIJPSUB composite SUBMIT job, or select the other options to submit each job
individually. If you select option 1, review the KCIJPSUB job first and edit the job according to
which conditional jobs need be submitted automatically. If you select option 1, you are prompted
with the following message:
- If your environment does not have system variables enabled:
Results
What to do next
- GBL_DSN_SYS1_PARMLIB
- GBL_DSN_SYS1_PROCLIB
- GBL_DSN_SYS1_VTAMLIB
- GBL_DSN_SYS1_VTAMLST
Restart the remote monitoring server.