Cloning an existing environment with system variables enabled
This scenario clones an existing runtime environment (RTE), which currently runs on LPAR SYSG, to create a new RTE, which will run on LPAR SP14. Support for system variables is enabled, to facilitate the deployment of the cloned RTE to other RTEs.
Before you begin
About this task
- Create the PARMGEN work environment.
- Clone the customized WCONFIG members from the model runtime environment.
- Update the interim libraries and create the configuration profiles for the new environment.
- Merge the LPAR profile from the model environment with the LPAR profile for the new environment.
- Customize the profiles for the new environment.
- Validate the profile parameter values.
- Create the runtime members and jobs.
- Submit the jobs to create the runtime environment.
Complete these steps to create sample runtime environment PLB3SP14.
Procedure
-
Set up the PARMGEN work environment for the new RTE.
-
On the PARAMETER GENERATOR (PARMGEN) WORKFLOW MENU (KCIPQPGA) panel, specify the parameters to identify the new RTE and press Enter.
Note that if you did not invoke the R (RESET) option, the values for GBL_USER_JCL, RTE_PLIB_HILEV, and RTE_NAME are carried forward from the last environment you created. If the values for the GBL_USER_JCL library and the high-level qualifier for the work libraries are correct, change the RTE_NAME to the name you want to use for the new environment.
- GBL_USER_JCL
- Specify the dataset name of the PARMGEN global user JCL library for the new runtime environment. If the dataset does not exist, you are prompted to correct the name or allocate the data set.
- RTE_PLIB_HILEV
- Specify the non-VSAM high-level qualifier you want to use for the PARMGEN work libraries for the new runtime environment.
- RTE_NAME
- Unique name for the runtime environment you are configuring. The name you specify is appended to the RTE_PLIB_HILEV values to make each set of PARMGEN and runtime libraries unique. PLB3SP14 is used in this example
-
Select option 1 from the menu.
The Set up PARMGEN Work Environment for an RTE (1 of 1) (KCIPQPG1) is displayed.
KCIPQPG1 SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) -------- Command ===> Quick Configuration Mode More: + Specify the RTE model profile to use: ==> ______________________________________________________ - To create a new RTE based on a predefined IBM model, type a ? in the field and press Enter, then select the appropriate template. - To create a new RTE that is a clone of an existing PARMGEN RTE, specify the WCONFIG profile library and RTE member name to clone; for example: (&hlq.&rte.WCONFIG(&clone_from)) - To create a new RTE that is a clone of an ICAT-created RTE, specify the ICAT RTE Batch member location and RTE member; for example: (&hlq.ICAT.INSTJOBS(SYSA)) - To create a new RTE from scratch, leave this field blank. - To reconfigure or upgrade this existing PARMGEN RTE, specify its values; for example: (TDITNT.IDTST.SYSA.WCONFIG(SYSA)) Customize jobcard data: ==> //TDITNT JOB (ACCT),'%SYSMEMBER% - NAME',CLASS=A,______________________ ==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M__________________ ==> //** 0 0 RTE_NAME=%RTE_NAME% SYSMEMBER=%SYSMEMBER%_____________________ ==> //** \_~_/ SYSJOBNAME=%SYSJOBNAME% JOBPARM SYSAFF=%SYSNAME%______________ Specify the Install Job Generator (JOBGEN) output library if you want PARMGEN to reuse CALLLIBS parameters from the JOBGEN repository: ==> ____________________________________________ (Type ? for last referenced JOBGEN library discovered, if any.) -
In the first field, specify the fully-qualified name of the RTE profile for the RTE you want to clone. In this example, the model environment is TSTEST.&userid.PLB3SP13.WCONFIG(PLB3SP13). If appropriate, supply the Install Job Generator output library and job card information.
KCIPQPG1 SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (1 OF 3) --------- Command ===> Quick Configuration Mode More: + Specify the RTE model profile to use: ==> TSTEST.&userid.PLB3SP13.WCONFIG(PLB3SP13)____________ - To create an RTE from scratch, leave this field blank. - To create an RTE based on a predefined IBM model, type a ? in the field and press Enter, then select the appropriate template. - To create an RTE that is a clone of an existing PARMGEN RTE, specify the WCONFIG profile library and RTE member name to clone; for example: (&hlq.&rte.WCONFIG(&clone_from)) - To create an RTE that is a clone of an ICAT-created RTE, specify the ICAT RTE Batch member location and RTE member; for example: (&hlq.ICAT.INSTJOBS(PLB3SP14)) - To reconfigure or upgrade this existing PARMGEN RTE, specify its values; for example: (TDITN.IDTST.DEMO.WCONFIG(PLB3SP14)) Customize jobcard data: ==> //&userid.J JOB (ACCT),'%SYSMEMBER% - NAME',CLASS=A,________________________ ==> // MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID.,REGION=0M__________________ ==> //** 0 0 RTE_NAME=%RTE_NAME% SYSMEMBER=%SYSMEMBER%_____________________ ==> //** \_~_/ SYSJOBNAME=%SYSJOBNAME% JOBPARM SYSAFF=%SYSNAME%______________ Press F1=Help for more information. Type UTIL to access utility menu. -
Press Enter to proceed to the next panel.
The second set up panel is displayed:
KCIP@PG2 SET UP/REFRESH PARMGEN WORK ENVIRONMENT FOR AN RTE (2 OF 3) --------- Command ===> Quick Configuration Mode GBL_USER_JCL: TDITN.IDTST.PARMGEN.JCL RTE_PLIB_HILEV: TDITM.IDTST RTE_NAME: SYSA Enter parameter values appropriate for your environment: UNIT / STORCLAS / VOLSER MGMTCLAS GBL_TARGET_HILEV: IBM.TARGET.ITM63055________________ ________ / ________ / HLQ of SMP/E target (TK*) datasets ______ ________ GBL_SYSDA_UNIT: SYSDA___ Work datasets UNIT name GBL_REGION: 0M______ JCL REGION (specify K/M suffix) Note: Type BACK to go back one panel. Type UTIL to access utility menu. -
Review the values on the panel and override them as necessary.
These values for the parameters on this panel are read from the RTE you are cloning from. You might want, for example, the new RTE to point to a different set of target libraries which has newer versions of the products installed.
-
Press Enter to display the next panel.
The third set up panel is displayed:
The values on panel are taken from the RTE that you are cloning (TSTEST.&userid.PLB3SP13.WCONFIG(PLB3SP13), in this case). Because this is a sharing RTE, you should set RTE_LOAD_SHARED_LIBS to N, so that only one RTE is loading the shared libraries. You do not need to make any other changes on this panel. However, if you do make changes to any of the following parameters, you will need to make the same changes to the corresponding Kpp_* parameters in the RTE profile of the new RTE.KCIP@PG3 ---- SET UP PARMGEN WORK ENVIRONMENT FOR AN RTE (3 OF 3) ------------- Command ===> Scroll ===> PAGE Enter parameter values appropriate for the LPAR RTE=&rte_name. Press F1=Help for more information. More: + RTE_DESCRIPTION: &rte_name____________________________________ RTE_SMS_PDSE_FLAG: Y (Y, N) (Allocate Non-VSAM PDSE libs) RTE_SMS_UNIT: __________ (Non-VSAM disk UNIT type) RTE_SMS_VOLUME: __________ (Non-VSAM disk VOLSER) RTE_SMS_MGMTCLAS: __________ (Non-VSAM disk MGMTCLAS) RTE_SMS_STORCLAS: __________ (Non-VSAM disk STORCLAS) RTE_SMS_VSAM_VOLUME: __________ (VSAM disk VOLSER) RTE_SMS_VSAM_MGMTCLAS: __________ (VSAM disk MGMTCLAS) RTE_SMS_VSAM_STORCLAS: __________ (VSAM disk STORCLAS) RTE_TYPE: SHARING____ (FULL, SHARING) RTE_HILEV: TSTEST.&userid____________ (&hlq portion of Non-VSAM RK* HLQ=&hlq.&rte_name) RTE_VSAM_HILEV: TSTEST.&userid_______________ (&hlq portion of VSAM RK* HLQ=&hlq.&rte_name) If RTE_TYPE is SHARING: RTE_X_HILEV_SHARING: TSTEST___________________ (&hlq portion of shared RTE's HLQ=&hlq.&rte_share) RTE_SHARE: BASE&SYSALVL.________________ ("SMP" value or *&rte_share) (*&rte_share portion of shared RTE's HLQ=&hlq.&rte_share) RTE_LOAD_SHARED_LIBS: Y (Y, N) (Is RTE updater of RO shared libs) If symbolics (system variables or user-defined variables) will be used: RTE_SYSV_SYSVAR_FLAG: Y (Y, N) (System variable flag) Security settings: RTE_SECURITY_USER_LOGON: NONE______ (RACF, ACF2, TSS, NAM, None) RTE_SECURITY_FOLD_PASSWORD_FLAG: Y (Y, N) (Fold password to upper case) RTE_SECURITY_CLASS: ________________________________________________ RTE_X_SECURITY_EXIT_LIB: TSTEST.&userid.PLB3&SYSNAME..RKANSAMU___________ GBL_DSN_ACF2_MACLIB: ________________________________________________ GBL_DSN_ACF2_MACLIB1: ________________________________________________ Local Tivoli Enterprise Monitoring Server (TEMS) settings in this LPAR RTE: RTE_TEMS_CONFIGURED_FLAG: Y (Y, N) (Configure TEMS in this RTE) RTE_TEMS_NAME_NODEID: PLB3&SYSNAME.:CMS ______________ (e.g.,CLONETST:cms) KDS_TEMS_TYPE: REMOTE (Hub, Remote) KDS_TEMS_HA_TYPE: __ (HA=High Availability Hub TEMS type) ITM components' communication-related and started tasks settings: RTE_TCP_PORT_NUM: 1918__________________ (1-65535 port number) RTE_VTAM_APPLID_PREFIX: TS&SYSCLONE.__________ (1-4 char.VTAM APPLID prefix) RTE_STC_PREFIX: TSS3__________________ (1-4 char.started task prefix) Note: Type BACK to go back one panel.- Started task prefix
- VTAM applid prefix
- Port number
- RTE high-level qualifier
- VSAM high-level qualifier
-
Press Enter to proceed to the next panel.
The Include Products in this PARMGEN RTE panel (KCIP@PGI) is displayed.
This panel lists all the installed products that are available for configuration by product code (Kpp) and product name and version. The products marked with a slash (/) are the ones already configured in the RTE being cloned, but the version represents the latest version available. If you include these products, they will be upgraded to the version in the target libraries. In this example, a monitoring server, OMEGAMON AI for z/OS, OMEGAMON AI for CICS, and the OMEGAMON enhanced 3270 user interface are already configured.
KCIP@PGI - INCLUDE (CONFIGURE) INSTALLED PRODUCT(S) IN THIS LPAR R Row 1 of 26 Command ===> Scroll ===> PAGE Select ("S" or "/") products to CONFIGURE those product(s) in DEMO RTE. Select or deselect products to include or exclude from configuration. Products configured in the model or current RTE (reconfiguring) are preselected When finished, change N to Y to confirm selections. Confirm ==> N (Y, N) Kpp Component or Product Name and Version ---- ---------------------------------------------------------------------- / KAH System Automation Monitoring Agent V350 / KC5 OMEGAMON AI for CICS V610 / KDO Tivoli Decision Support for z/OS Agent V181 / KDS Tivoli Enterprise Monitoring Server V630 / KD4 ITCAM for SOA Agent V711 / KD5 OMEGAMON AI for DB2 V610 / KGW OMEGAMON AI for CICS TG V610 / KI5 OMEGAMON for IMS V550 / KJJ OMEGAMON AI for JVM V610 / KMQ OMEGAMON for Messaging - MQ V750 / KM5 OMEGAMON AI for z/OS V610 / KNA NetView for z/OS Agent V621 / KN3 OMEGAMON AI for Networks V610 / KOB OMEGAMON Enhanced 3270 User Interface V750 / KQI OMEGAMON for Messaging - Integration Bus V750 / KRG Advanced Audit for DFSMShsm Agent V260 / KRH Advanced Reporting and Management for DFSMShsm Agent V260 / KRJ Advanced Allocation Management Agent V330 / KRK Automated Tape Allocation Manager for z/OS Agent V330 / KRN Advanced Catalog Management Agent V260 / KRV Advanced Backup and Recovery for z/OS Agent V240 / KRW Tape Optimizer for z/OS Agent V220 / KS3 OMEGAMON AI for Storage V610 / KYN ITCAM for Application Diagnostics, TEMA V710.03 End of data -
If you want to install additional products, select them by typing a slash next to the product code. Deselect any products you do not want to include in the new RTE. Then, change Confirm ==> N to Confirm ==>Y and press Enter.
The KCIJPCFG job is displayed, tailored with the values you have configured.
-
Review the notes, then submit the job.
You are returned to the main Workflow panel. Wait until you see a successful return code before you proceed to the next step.
-
On the PARAMETER GENERATOR (PARMGEN) WORKFLOW MENU (KCIPQPGA) panel, specify the parameters to identify the new RTE and press Enter.
-
Clone the customized members from the model environment.
-
Type U or UTIL from the Workflow main menu.
The UTILITIES (KCIPQPGU) panel is displayed.
- Type the option number for the KCIJPCCF job that clones customized members (Kpp$C*, Kpp$P*/Kpp@P*, Kpp$S*), $JOBCARD, and the $GBL$USR global profile) from an existing WCONFIG library to a new one.
-
Review the job to determine if you need to further modify the library concatenated in the OLDWCNFG DDNAME.
By default, this DDNAME already points to the WCONFIG library that you specified in the RTE profile library field of the first set up panel. Modify as needed to point to an existing WCONFIG library that contains the customized members you want cloned to the WCONFIG library of the new runtime environment.
-
Submit the job.
You are returned to the main Workflow panel.
-
Type U or UTIL from the Workflow main menu.
-
After you return to the main Workflow panel, merge the values from the model RTE profile into the new environment:
-
Type U or UTIL from the Workflow main menu.
The UTILITIES (KCIPQPGU) panel is displayed.
- Type the option number for the KCIJPMCF job.
-
Review and customize the KCIJPMCF job.
The WCONFIG(KCIJPMCF) job merges or clones another version of the WCONFIG profiles (the %RTE_NAME% RTE LPAR profile and $GBL$USR) into a refreshed copy or cloned copy. In this case, the PLB3SP13 runtime environment has already been fully customized; its PARMGEN profile already uses symbolics. So to save time, clone its values into PLB3SP14 by editing the OLDMEM() parameter to point to the WCONFIG(PLB3SP13) value.
========================================================================= EDIT TSTEST.&sysuid.PLB3SP14.WCONFIG(KCIJPMCF) Command ===> Scroll ===> CSR 000068 //* MERGECHG Step: 000069 //* Merge the changes in %OLDMEM% into %NEWMEM% member. 000070 //* ******************************************************************* 000071 //MERGECHG EXEC PGM=IKJEFT01,DYNAMNBR=99,REGION=4M 000072 //SYSEXEC DD DISP=SHR, 000073 // DSN=TSTEST.ITM62351.TKANCUS 000074 //SYSTSPRT DD SYSOUT=* 000075 //SYSPRINT DD SYSOUT=* 000076 //SYSTSIN DD * 000077 KCIRPLBX + 000078 BATCH + 000079 SKIPVAR(TSTEST.ITM62351.TKANCUS(KCIDPGNX)) + 000080 OLDMEM(TSTEST.&userid.PLB3SP13.WCONFIG(PLB3SP13)) + 000081 NEWMEM(TSTEST.&userid.PLB3SP14.WCONFIG(PLB3SP14)) 000082 /* ===============================================================================
- Submit the job.
-
Type U or UTIL from the Workflow main menu.
-
Customize the configuration profiles for the new RTE.
-
From the Workflow menu, select option 2.
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. -
Customize the LPAR configuration profile.
- Select option 1 to display the LPAR profile:
- Change any references to PLB3SP13 (the model environment) to PLB3SP14 (the current environment).
Important: In a system variables scenario, the only parameters that must have a nonsymbolic value are RTE_NAMESV, RTE_HILEVSV, and RTE_VSAM_HILEVSV parameters, as these are used directly in the WKANSAMU(KCIJV*) jobs. In the following example of the RTE_NAMESV parameter, the value must remain PLB3SP14:
ISREDDE2 TSTEST.&userid.PLB3SP14.WCONFIG(PLB3SP14) Command ===> C PLB3SP13 PLB3SP14 ALL Scroll ===> CSR ****** ***************************** Top of Data ****************************** - - - - - - - - - - - - - - - - - - 354 Line(s) not Displayed ==CHG> RTE_NAMESV PLB3SP14 - - - - - - - - - - - - - - - - - - 904 Line(s) not Displayed ****** **************************** Bottom of Data ****************************
- You must also change any Db2, IMS subsystem names, CICS regions specific to the LPAR, MQ manager and subsystem names, and their related load libraries, inherited from the model runtime environment.
-
Customize the system variables configuration profile to define all user symbols used in the LPAR profile.
- From the Customize PARMGEN Configuration Profile Members, select option 3.
The TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP14) system variables profile is displayed.
- Because the PLB3SP14 LPAR profile inherited its symbolics from the cloned PLB3SP13 LPAR profile, simply replace the contents of TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP14) with the TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP13) system variables profile parameters, then change the LPAR-specific symbolic values accordingly.
ISREDDE2 TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP14) - 01.16 Columns 00001 00072 Command ===> C SP13 SP14 ALL Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000100 * ****************************************************************** 000110 * Member: KCI$RTEV 000120 * Master Source: TSTEST.ITM62351.TKANSAM(KCI$RTEV) 000130 * KCIJPUP1 Batch Job Output (PART 3): 000131 * TSTEST.&userid.PLB3SYSG.IKANSAMU(KCI$RTEV) - IBM Default Copy 000140 * TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP14) - Customer Copy 000150 * Purpose: 000160 * TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP14) 000170 * member houses user-defined symbolics for this RTE if 000180 * System Variables mode is enabled. 000190 * Note: These are symbolics in addition to the typical static 000200 * system symbols defined in SYS1.IPLPARM and system variables 000210 * derived by KCIPARSE program (for TYPE:CE (CHAR extracted) 000221 * and TYPE:IE (INTEGER extracted) KCIPARSE-extracted symbolics 000222 * for System Variables use in the SYSPRINT DDNAME's GLOBAL 000224 * VARIABLE TABLE SUMMARY of a KCIPARSE run). 000227 * Instructions: 000228 * Add your user-defined symbolics below, if any. . . 000284 * ********************************************************************* 000285 * SECTION: PRE-DEFINED / USER-DEFINED SYMBOLICS * 000286 * ********************************************************************* 000287 * ----------- BEGIN - USER SECTION: PRE-DEFINED SYMBOLICS ----------- * 000288 * ====================== =============== 000289 * User-defined symbolic: Resolved value: 000290 * ====================== =============== 000291 AGT_TEMS_BKUP1_NAME_NODEID PLB1SP22:CMS 000292 AGT_TEMS_BKUP1_TCP_HOST SP22 000293 AGT_TEMS_BKUP1_VTAM_LU62_DLOGMOD CANCTDCS 000294 AGT_TEMS_BKUP1_VTAM_APPL_LLB_BKR CTDDSLB 000295 AGT_TEMS_BKUP1_VTAM_NETID USIBMNET 000296 * ----------- END - USER SECTION: PRE-DEFINED SYMBOLICS ----------- * 000297 * ----------- BEGIN - USER SECTION: USER-DEFINED SYMBOLICS ---------- * 000298 * ====================== =============== 000299 * User-defined symbolic: Resolved value: 000300 * ====================== =============== 000400 * ----------- END - USER SECTION: USER-DEFINED SYMBOLICS ---------- * 008300 * ----------- BEGIN - USER SECTION: USER-DEFINED SYMBOLICS ---------- * 000086 * Type 1: Static symbol override 000087 SYSNAME SP13 000088 SYSPLEX LPAR400J 000089 SYSALVL 2 000090 SYSCLONE SP13 000091 * Type 2: KCIPARSE-extracted symbols 000092 SYSVTAMNETID USIBMNET 000093 SYSIPHOSTNAME SP13 009400 * Type 3: User defined symbols 009500 RTE_USS_RTEDIR /tstest 009710 KDS_HUB_TEMS_NAME_NODEID "PLB1SP22:CMS" 009711 KDS_HUB_VTAM_APPL_GLB_BROKER CTDDSLB 009720 KDS_HUB_VTAM_NETID USIBMNET 009730 KDS_HUB_TCP_HOST SP22 009780 KDS_HUB_TCP_PIPE_PORT_NUM nnnnn 009790 KDS_HUB_TCP_UDP_PORT_NUM nnnnn 009800 GBL_HFS_JAVA_DIR1 /Java/J6.0 ****** **************************** Bottom of Data ****************************Since a secondary monitoring server was enabled for these agents, each backup (secondary) monitoring server now points to the same hub monitoring server (the static hub monitoring server, started task TSS0DSH1, in the PLB3SP14 environment).
If you need the PLB3SP13 remote monitoring server and agents to use other values, make further edits to the TSTEST.SYSPLEX.PARMGEN.JCL(PLB3SP14) variables profile.
- Save the changes and exit the profile. Press F3 to return to the main Workflow panel.
- From the Customize PARMGEN Configuration Profile Members, select option 3.
-
From the Workflow menu, select option 2.
-
Validate the profile parameter values you specified.
-
Type U or UTIL from the Workflow main menu.
The UTILITIES (KCIPQPGU) panel is displayed.
- Type the option number for the KCIJPVAL job.
-
Review the notes and submit the job.
The parameter validation report is written to &hilev.&rte.WCONFIG($VALRPT). Enter option number + s, for example 23s, in the UTILITIES menu to view the report.
- If the job gets a condition code greater than 4 (COND CODE 0004), review the $VALRPT. Return to the previous step and correct the parameter values, then resubmit the validation job.
-
Type U or UTIL from the Workflow main menu.
-
Create the WK* runtime members and the WKANSAMU jobs:
-
Select option 3.
The CREATE THE RTE MEMBERS AND JOBS (KCIP@PR1) panel is displayed.
- Select option 1 to submit the generated $PARSE composite job.
-
Review the job, then submit the job.
Return to the main Workflow panel.
-
Select option 3.
-
Complete the setup of the environment.
-
Select option 4 from the Workflow main menu.
The Submit Batch Jobs to Complete PARMGEN Setup (KCIP@SUB) panel is displayed.
-
Select option 1 to submit the KCIJVSUB composite SUBMIT job, or select the other options to submit each job individually. If you select option 1, review the KCIJVSUB job first, and edit the job according to which the conditional jobs can be submitted automatically, and which must be submitted manually by someone with the required authority.
If you select option 1, you are prompted with the following message:
KCIP@MSG -------------------- 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:
KCIP@PGP -------------------- 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 KCIJPSUV job, then press F3, and you are automatically presented with the KCIJVSUB job for submission.
-
Select option 4 from the Workflow main menu.