Creating SCLMBuildConfig records

An SCLMBuildConfig record is a stateless, reusable, SCLM configuration record that specifies such SCLM host system parameters as the host name, the project, and the build and promote operation options needed to run and promote a build of SCLM objects. If needed, you can perform multiple promote operations through all of the levels of your group hierarchy. An SCLMBuildConfig record is used in conjunction with an SCLMBuild record to run and promote an SCLM build.
Note: Except for the Configuration Name and Description fields, the editable fields of this record can accept only ASCII characters, regardless of the character set in use. This limitation is due to a restriction with the server component of the SCLM integration running on z/OS®.
  1. Click ClearQuest > Create > youruseridanddbname > Other > Create SCLMBuildConfig.
  2. Do one of the following:
    • To populate the fields in the SCLMBuildConfig window with default entries, click the Template list, select the SCLMBuildConfig record you want, and click the Load button. You can then edit the newly populated fields as needed. For example, you must edit at least the text in the Configuration Name and Description fields to distinguish a new record from existing SCLMBuildConfig records. When you finish editing the defaults, proceed to step 6.
    • If you do not want to populate the fields in this record with the defaults, or if there is no existing record with defaults you can use, proceed to step 3.
  3. In the SCLMBuildConfig window, click the Main tab:
    Configuration Name
    Enter a meaningful, unique name for the configuration record.
    Description
    Enter a meaningful description for the record.
    Host
    Enter the fully qualified host name of the host system where the artifacts to be built are located.
    Port
    Enter the port number of the host system.
    User ID
    Enter your TSO user ID.
    Password
    Enter your TSO password.
    Project
    Enter the name of the SCLM project to be built. This name corresponds to the HLQ used for the project.PROJDEFS.LOAD data set on the specified host system.
    Project Definition
    Enter the SCLM project definition. By default, this definition corresponds to the member name of the project.PROJDEFS.LOAD data set.
  4. Click the Options tab:
    Build Options
    Scope
    Select the scope of the action. The options are Extended, Normal, Subunit, and Forced. The default is Normal.
    Mode
    Select the build mode. The options are Conditional, Forced, Report, or Unconditional. The default is Conditional.
    List
    To specify where to copy or print translator listings on the specified host, select a list option. If errors occur, Yes copies the listings only to the build LIST data set specified in the List Dataset field. Printer sends the listings to your printer and is valid only for batch builds. The default is Yes.
    Report
    To specify where to generate a build report on the host, select a report option. Yes routes a report to the BUILD REPORT data set specified in the Report Dataset field. Printer sends a report to your batch job output printer and is valid only for batch builds. The default is Yes.
    Message
    To specify where to route build messages on the host, select a message option. Yes routes the messages to the BUILD MESSAGES data set specified in the Message Dataset field. Printer sends the messages to your batch job output printer and is valid only for batch builds. The default is Yes.
    List Dataset
    To specify a destination for the build listings on the host, enter the name of the list destination data set.
    Report Dataset
    To specify a destination for the build report on the host, enter the name of the report destination data set.
    Message Dataset
    To specify a destination for build messages on the host, enter the name of the destination message data set.
    Exit Dataset
    To specify a destination for build user exit data on the host, enter the name of the destination exit data set.
    Promote Options
    Scope
    Select the scope of the promote action. The options are Extended, Normal, Subunit, and Forced. The default is Normal.
    Mode
    Select a promote operation mode. The options are Conditional, Forced, Report, or Unconditional. The default is Conditional.
    Report
    To specify where to generate a promote operation report, select a report option. Yes routes a report to the promote operation REPORT data set. Printer sends a report is to your batch job output printer and is valid only for batch builds. The default is Yes.
    Message
    To route promote operation messages, specify a message option. Yes routes the messages to the PROMOTE MESSAGES data set. Printer sends the messages to your batch job output printer. Printer is valid only when you run builds in batch mode. The default is Yes.
    Report Dataset
    To specify a destination for the promote operation report, enter the name of the report destination data set.
    Message Dataset
    To specify a destination for promote operation messages, enter the name of the message destination data set.
    Exit Dataset
    To specify a destination for promote operation user exit data, enter the name of the exit destination data set.
  5. Optional: Click the JCL tab. The fields on this page are used only for batch builds. If you do not use this page, the defaults in the SCLM build and promote operation batch skeletons (FLMCQSKB, FLMCQSKP) are used. These defaults are determined by the z/OS systems programmer during host customization. If you enter information on this page and specify an online build in your SCLMBuild record, the entries on this page are ignored:
    Build Job Control
    The build job control statement provides administrative information, including security, accounting, and identification information. Every build job has one and only one job control statement.
    Job Name
    Enter a name for the job. Entries can be no longer than eight (8) characters. This field marks the beginning of the build job and assigns it a name.
    Accounting Data
    Enter your site-specific, host accounting data, such as the account data and any other information your installation requires. (See your z/OS System Administrator for these details.)
    Description
    Enter a description of the build job or of user details.
    Notify
    Enter a user ID to specify where to send completed information about the build job. You can enter "&SYSUID" to insert your user ID so that the information is sent to you.
    Message Class
    Enter a message class to specify what to do with messages the system sends to you as it processes the build job. For example, you might use a held output class to allow reviewing the build messages later.
    Message Level
    Enter a message level to reproduce the JCL code in the output of the build job and to include allocation messages.
    Class
    Enter a class to specify the system resource requirements for the build job.
    Region
    Enter a region to specify the amount of virtual storage space required by the build job.
    Freeform JCL
    As an alternative to specifying JCL information in the Build Job Control fields, you can use the Freeform JCL fields to enter JOBCARD information in free-form text.

    Each line of JCL must start with two slashes ('//') in columns 1 and 2. Then, beginning with line 2, column 3 must be a blank space. Use columns 4 through 71 to code your JCL statement, and terminate the statement on the last line by using two slashes in columns 1 and 2.

    If the Freeform JCL field is clear and the Build Job Control fields are blank, SCLM uses the default job control statement. The default JOBCARD is determined by the systems programmer during z/OS host customization in the SCLM build and promote operation batch skeletons (FLMCQSKB, FLMCQSKP). The maximum number of JOBCARD lines is four. Here is an example using only two lines:
    //HOGESJOB JOB (ACCT),'Paul Hogans Build',MSGCLASS=X,CLASS=A,
    // MSGLEVEL=(1,1),REGION=6M,NOTIFY=HOGANP 
    Promote Job Control
    The promote operation job control statement provides certain administrative information, including security, accounting, and identification information. Every promote job has one and only one job control statement.
    Job Name
    Enter a name for the job. This field also marks the beginning of the promote job and assigns it a name.
    Accounting Data
    Enter your site-specific, host accounting information, such as account data and any other information your installation requires. (See your z/OS System Administrator for these details.)
    Description
    Enter a description of the promote job or of user details.
    Notify
    Enter a user ID to specify where to send completed promote job information. You can enter "&SYSUID" to insert your user ID here so that the information is sent to you.
    Message Class
    Enter a message class to specify what to do with messages the system sends to you as it processes your promote job. For example, use a held output class to allow reviewing the build messages later.
    Message Level
    Enter a message level to reproduce the JCL code in the output of the promote job and to include allocation messages.
    Class
    Enter a class to specify the system resource requirements for the promote job.
    Region
    Enter a region to specify the amount of virtual storage space needed by the promote job.
    Freeform JCL
    As an alternative to specifying JCL information in the Promote Job Control fields, you can use the Freeform JCL fields to enter JOBCARD information in free-form text.

    Each line of JCL must start with two slashes ('//') in columns 1 and 2. Then, beginning with line 2, column 3 must be a blank space. Use columns 4 through 71 to code your JCL statement, and terminate the statement on the last line by using two slashes in columns 1 and 2.

    If you leave the Freeform JCL field clear and leave all of the Promote Job Control fields blank, SCLM uses the default job control statement. The default JOBCARD is determined by the systems programmer during z/OS host customization in the SCLM build and promote operation batch skeletons (FLMCQSKB, FLMCQSKP). The maximum number of JOBCARD lines is four. Here is an example using only two lines:
    //HOGESJOB JOB (ACCT),'Paul Hogans Build',MSGCLASS=X,CLASS=A,
    // MSGLEVEL=(1,1),REGION=6M,NOTIFY=HOGANP 
  6. Optional: You can save the entries for the record you are creating as defaults by selecting the arrow next to the Load button and clicking Save As Default. By saving these entries, you can populate the fields of SCLMBuildConfig records you create in the future by selecting the record from the Template list and clicking the Load button.
  7. Click OK to create the record.
Related tasks
Tutorial: Building across platforms
Creating CCBuildConfig records

Feedback