Milestone 8: Define Started Tasks

ISPW relies on four Started Tasks (CM, CI, CT, and SX) to perform all its operations. Without these Started Tasks, ISPW will not function. Follow the instructions in this Milestone to define those Started Tasks.

Important

  • Roles involved: ISPW Installer
  • The SX Started Task defined in this Milestone does not have a configuration screen because it is defined by the definitions for the other Started Tasks.

Task 8.1 Define Common Parameters

  1. On the ISPW Guided Configuration Dialog Main Menu, type 4 (Define Started Tasks) in the Option field and press Enter. The Define Parameters for Started Tasks screen is displayed.

    Define Parameters for Started Tasks Screen
    image2021-11-17_11-23-17.png

    If you do not want to import parameters from a prior release, skip ahead to Step 5 (not Option 5).

  2. To import parameters from a previous release of ISPW, type I in the Option field and press Enter. The Import Parameters screen is displayed.
    Import Parameters Screen

    image2021-11-17_11-23-46.png

  3. Make sure the dataset and member are correct for CM, CI, and CT, then type GEN in the Option field and press Enter. An ISPF edit session is opened for the job $IMPORT that will be run to import your site’s existing ISPW parameters.

  4. Review the job, then submit it. The imported parameters will form the basis of the CM, CI, and/or CT parameters used in this release of ISPW. The $IMPORT job should complete with one of the following return codes:

    • 0 – No issues.
    • 4 – Warning: Some parameters may have been skipped.
    • 12 – Error: Invalid parameters were found. These should be reviewed and corrected.

    These return codes will not prevent the job from running or cause it to fail, but they should be reviewed in order to make any necessary changes to your parameters.

    If you do not want to make changes to your imported parameters, skip ahead to Generate Started Task PARMLIB Members.

  5.  Type 1 (Update Common Parameters) in the Option field and press Enter. The Define Common Parameters for Started Tasks screen is displayed. Fields with defaults are pre-filled, but you can overtype them.

    Important

    The values here are illustrated in TCP/IP Configuration Overview.

    Define Common Parameters for Started Tasks Screen

    image2021-11-17_11-24-56.png

  6. These parameters can be made the defaults for the CMSC. In the Should these parameters... field, type Y or N based on the following:
    • If set to Y (Yes), the PARMLIB members generated will have the names IWCM00, IWCI00, and IWCT00. This will cause them to be used as the default by any ISPW instance on the CMSC, unless another set is specified in the PROC.

    • If set to N (No), the PARMLIB members generated will have names in the format IWCMxxxx, IWCIxxxx, and IWCTxxxx. Where xxxx is the SERVERID specified by the user. A corresponding DD will be added to each of the Started Task PROCs to signify which PARMLIB member to use.

      Important

      If the default status of the parameters needs to be changed at a later time, these PARMLIB members can be regenerated by entering option 5 on the Define Parameters for Started Tasks screen. They will then need to be copied into the PARMLIB and the PROCs updated accordingly.

  7. In the Server Names section of the screen, enter the following:
    1. In the SERVERID field, enter ISPW (CM) Server ID used by ISPW clients. This is the internal name given to the ISPW instance.
    2. In the WZCMNAME field, enter the internal name for the ISPW Server (CM) task.
    3. In the WZCINAME field, enter the internal name for the Communications Interface (CI) task that communicates with the CM specified in WZCMNAME.
    4. In the WZCTNAME field, enter the internal name for the Component Transfer (CT) task that communicates with the CM specified in WZCMNAME.
  8. In the Port Numbers section of the screen, enter the following:
    1. In the WZCMPORT field, enter the port number the CM task listens on for connections from CI and CT.
    2. Optional: If HCI or Topaz Workbench 18.02 and above or REST APIs will be used, in the WZCMXPRT field, enter the port number the CM task listens on for those REST APIs.
  9. In the Communications section of the screen, enter the following:
    1. In the XSYSPROT field, enter the communications protocol used by the CM.
    2. In the WZCMADDR field, enter the virtual IP address of CM.

Task 8.2 Extract Extra Parameters

If you are performing a new installation or do not have security or TRCMD records, skip ahead to Define CM Specific Parameters.

The migration program ignores security and TRCMD records. The security records are SECRULE, SECPREFIX, SECDELIM and SECCLASS. The extract utility copies these records to a file that is read by the CI, CM, or CT. Run this extract utility only if there were security and TRCMD records ignored by the migration tool.

Execute the extract utility for each CM, CI, and CT you currently run. JCL for the extract utility is provided in the SAMPLIB. There is one for each address space. You must supply the appropriate JOB card information and customize the JCL as required. You will need to modify and run each of the following JCL members located in the SPWMSAMP dataset:

  • XTRACCI
  • XTRACCT
  • XTRACCM

Important

In the following figure, INPTFILE file should be your previous version file names, and OTPTFILE file should be your current version file names.

The following figure shows sample JCL for extracting security and TRCMD records from the CM parameters.

Sample JCL for Parameter Extraction

image2021-11-17_11-25-47.png

Task 8.3 Define CM Specific Parameters

  1. Return to the Define Parameters for Started Tasks screen, type 2 (Update CM Specific Parameters) in the Option field, and press Enter. The Define Parameters for the CM Started Task screen is displayed. Fields with defaults are pre-filled, but you can overtype them.Define Parameters for the CM Started Task Screen

    image2021-4-14_18-36-42.png

  2. In the upper portion of the screen, enter the following:
    1. In the SECCLASS field, type the SAF security class used by ISPW. See Set Up an SAF Class.
    2. In the SECRULE field, type the Security Rule Specification.
    3. In the SETPROC field, type the name of the SX started task. CM will issue a z/OS START for this name when Set Processing is required.
    4. In the FXPROC field, type the name of the FX started task. CM will issue a z/OS START for this name when Custom Exit processing is required.

    5. In the TCPUSERID field, type the job name of the TCP/IP address space. The default is TCPIP.

      Important

      If you are using the RTCONFIG SECRULE, make sure that you provide the necessary security access to the userIDs of the RX, FX, EF, and SX started tasks for successful execution of these started tasks.

  3. In the Number of TCB’s section of the screen, enter the following:
    1. In the GPROCESS field, type the number of long running requests that can be processed against Db2 (threads). Maps to the number of long running TCBs.
    2. In the SPROCESS field, type the number of short running requests that can be processed against Db2 (threads). Maps to the number of short running TCBs.
  4. In the Authorized Users for Server Start section of the screen, enter a maximum of four userID(s) that can perform a server start. The userID of the installer should be the first entry.
  5. In the Optional Parameters section of the screen, enter the following:
    1. In the WEBAPI field, type Y or N . Specifying Y (Yes) enables the Web Services API to ISPW. The default is N (No).

    2. In the CUSTOM_DIALOGS field, type Y or N. Specifying Y (Yes) enables use of custom dialogs. the default is N (No).

      Important

      If using Topaz Workbench to access ISPW, you must specify Y in the CUSTOM_DIALOGS field.

    3. In the CONFIG_NAMES field, type Y or N. Specifying Y (Yes) enables loading of a list of valid runtime configuration names for this CM. The default is N (No).

Task 8.4 Define CI Specific Parameters

  1. Return to the Define Parameters for Started Tasks screen, type 3 (Update CI Specific Parameters) in the Option field, and press Enter. The Update the ISPW CI Parameters screen is displayed. Fields with defaults are pre-filled, but you can overtype them.Update the ISPW CI Parameters Screen

    image2021-11-17_11-26-51.png

  2. In the Cross-memory ID XMEMID field, enter the cross-memory ID to be used by ISPW clients to send messages to this CI.
  3. In the Port Numbers fields, enter the following:
    1. In the WZCIPORT field, enter the port number on which the CI task will listen for communications from Topaz Workbench 17.02 and below and Remote Servers.
    2. In the WZCIXPRT field, enter the port number on which the CI task will listen for CSS/XML messages from CES browser apps or CES REST API 18.02.01 and below.
  4. In the IP Addresses WZCIADDR field, enter the virtual IP address for the CI. Include only when VIPA will be used.

Task 8.5 Define CT Specific Parameters

  1. Return to the Define Parameters for Started Tasks screen, type 4 (Update CT Specific Parameters) in the Option field, and press Enter. The Update the ISPW CT Parameters screen is displayed. Fields with defaults are pre-filled, but you can overtype them.Update the ISPW CT Parameters screen

    image2021-4-14_18-43-53.png

  2. In the CT parms section of the screen, enter the following:
    1. In the TEMPPREFIX field, enter the prefix used to allocate temporary datasets. Created files are deleted by CT. Must be 12 characters or less.
    2. In the TEMPUNIT field, enter the unit for temporary datasets allocation. The default is SYSDA.
    3. In the TEMP_PRIMARY_SPACE field, enter the primary allocation space the address space will use for CT Started Task temporary datasets.
    4.  In the TEMP_SECONDARY_SPACE field, enter the secondary allocation space the address space will use for CT Started Task temporary datasets.
    5. In the CWIDLE field, enter the number of seconds the warehouse dataset can be idle before it is closed and deallocated. The default is 60 seconds.
    6. In the HKINTERVAL field, enter the number of minutes between warehouse housekeeping operations. The default is 60 minutes.
    7. In the COMPSTAT field, enter Y (Yes) or N (No) to specify whether compression statistical messages are to be written to SYSLOG. The default is N.

    8. In the HSMINT field, enter Y (Yes) or N (No) to specify whether to use HSM to recall migrated datasets. The default is Y.

      Important

      If you are using HSM, processing may be delayed while files are being recalled.

    9. In the TCPUSERID field, enter the job name of the TCP/IP address space. The default is TCPIP.
  1. In the IP Addresses WZCTADDR field, enter the virtual IP address for the CT. Include only when VIPA will be used—otherwise leave blank.
  1. In the External Function section of the screen, enter the following:
    1. In the EFPROC field, enter the name of the ISPWEF proclib member. Include only if you will be using the ISPW External Function Processor Enhancement.
    2. In the EFRTCONF field, enter the Runtime Config entry to be used by ISPWEF when communicating with CI. Include only if you will be using the ISPW External Function Processor Enhancement.
  2. In the Audit Log section of the screen, enter the following:

    1. In the AUDITGDG field, enter the dataset name for GDG created for the audit log.

    1. In the AUDITMAX field, enter the maximum number of GDG versions. The default is 10.
    2. In the AUDITUNIT field, enter the allocation unit for GDG datasets. The default is SYSDA.
    3. In the AUDITVOL field, enter the allocation volume for GDG datasets. The default is an asterisk (*) specifying to use SMS.
    4. In the AUDITSIZE field, enter the allocation size for GDG datasets, in tracks.

Task 8.6 Generate Started Task PARMLIB Members

  1. Return to the Define Parameters for Started Tasks screen, type 5 (Generate Parmlib Members) in the Option field, and press Enter. If the PARMLIB members have not yet been generated, the dialog will generate them, place them in the previously designated “Work” dataset, and display the Generate Manual Tasks screen. If the PARMLIB members have been previously defined, the popup shown in Popup on the Generate Manual Tasks Screen will be displayed asking whether they should be regenerated or not.Generate Manual Tasks Screen

    image2021-11-17_11-27-52.png

    Popup on the Generate Manual Tasks Screen

    image2021-11-17_11-28-18.png

  2. If the popup shown in Popup on the Generate Manual Tasks Screen is displayed, type Y (Yes) or N (No) in the Would you like to regenerate the Parmlib Members field, then press Enter to continue.

  3. To edit one of the PARMLIB members after they have been generated, type 1 , 2 , or 3 in the Command field and press Enter. An ISPF edit session will be displayed for the chosen member.

    Important

    Any changes made outside of the dialog will be lost if the members are regenerated.

    Warning

    If you are upgrading and have chosen to use the PARMLIB Migration Utility, use this step to confirm that your names match the standard described in the subsequent section. Then copy your PARMLIB members created by the Utility to the PARMLIB for your corresponding CMSC.

Once the tasks have been generated, go to the “Work” dataset you specified initially on the ISPW Configuration Dialog. You will find three members, the names of which are dependent on whether they were specified as the default or not in Define Common Parameters. Their names will be in the format IWCMxxxx, IWCIxxxx, and IWCTxxxx where xxxx is either the SERVERID (for non-default) or 00 (for default).

These three members will need to be copied into the PARMLIB that corresponds with the CMSC you plan to use for this instance of ISPW. Contact your CMSC administrator for complete details on where the PARMLIB resides and setting up the CMSC for use with ISPW. You might not have access to copy members to the PARMLIB.

When the three PARMLIB members have been copied over to the PARMLIB, a CMSC refresh command will be needed for the CMSC to recognize the new members. To do so, use the z/OS MODIFY (F) command to update the CMSC with the PARMLIB members you created or updated.

Refreshing All PARMLIB Members

F cmscname,PARMLIB REFRESH

Refreshing A Single Parameter Member

F cmscname,PARMLIB REFRESH member_name

Multiple CI and CT Started Tasks

If your site requires multiple CI and CT Started Tasks, you will need to create additional PARMLIB members, each with their own unique suffix. Appropriate DD statements will also need to be added or modified in the PROCs for the startup tasks. For more information on the format, see Multiple CIs and CTs.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*