Global Type Sequencing › How to Enable Global Type Sequencing › Create Your Site Type Sequence Member › Build a Type Sequence Member Using the BC1JBTSE Utility

Build a Type Sequence Member Using the BC1JBTSE Utility

To create a Type Sequence member for Global Type Sequencing, you can use the build utility BC1JBTSE.

Follow these steps:

1. Edit member BC1JBTSE to conform to the needs of your installation. Then execute this job. The build utility is member BC1JBTSE in your site's CA Endevor SCM CSIQJCL data set

   The JCL builds a Type sequence file to a sequential work file. The utility creates Type sequence records for all Types defined to a site. The utility reads the C1DEFLTS table to find the Master Control records and then extracts the necessary Type information from the MCF. For each unique Type name that is found, a Type sequence record is created.

   The utility does not merge one System's Type sequence with another. Unique Type records are written to the file as they are processed, starting with the first System in the first defined C1DEFLTS's environment, stage combination.

   The Type sequence record's description field contains the description from the first unique Type record. The utility produces comment records to identify each Type location occurrence. For example, if Type MAC is defined in environment DEV (stage 1, 2) under System BASE and in environment QA (stage 1,2) also under BASE, four comment records appear following the Type sequence record. The description field in the sequence record is set to the Type's description value.

   Note: If your site has environments that you want the utility to exclude, you can create a temporary C1DEFLTS table that excludes these environments and run the utility against the temporary C1DEFLTS. For example, you might have an environment with many test Systems that contain many elements that have never been promoted. Excluding this environment would limit the number of generated Type statements, which could help you define the initial Type sequence order. Any valid Types from the excluded environment could then be added manually.

2. Edit this file by rearranging the order of the Type record or by deleting Type records. The order of the records in the file will determine the order in which Types are processed.
3. Copy the file to the Parmlib data set.