Rational Developer for System z


Scheduled build

Though most builds and promotes are initiated in the SCLM Developer Toolkit Client, there is a function to set up build and promote configuration files within the z/OSĀ® HFS and initiate these builds or promotes through the CRON (time) service within Unix Systems Services. In this method, the SCLM Developer Toolkit Client is not required as the relevant build and promote parameters are read from an HFS configuration file and passed to the SCLM Developer Toolkit host component for SCLM processing. Below is a description of the SCLM Developer Toolkit samples that provide CRON initiated builds and promotes. These samples are available in the installed SCLM Developer Toolkit SAMPLIB data set.

BWBCRON1

This REXX sample calls the Developer Toolkit host interface and passes the function parameters. Output from the function process by default is displayed to STDOUT but may be re-directed to a HFS file or log. This sample may be copied into the HFS into a directory path of your choice to run. The sample will need to be customized as detailed within the sample. This REXX sample must be run in conjunction with input from sample BWBCRONB for a build or sample BWBCRONP for a promote.

BWBCRONB

This REXX sample sets up the build parameter input string that is passed to module BWBCRON1. The sample requires user customization to update all required build parameters. This sample must be copied into a user-determined HFS directory (optionally renamed) to be run with sample BWBCRON1.

BWBCRONP

This REXX sample sets up the promote parameter input string which will be passed to module BWBCRON1. The sample requires user customization to update all required promote parameters. This sample must be copied into a user-determined HFS directory (optionally renamed) to be run with sample BWBCRON1.

STEPLIB and PATH requirements

The PATH and STEPLIB variables in either the system-wide profile (/etc/profile) or your user profile (/u/userid/.profile) will need to be set to locate the cron jobs ($PATH) and locate the Developer Toolkit modules ($STEPLIB) if the DT data set is not in the LINKLIST. To RUN (parameter output is piped as input into BWBCRON1):

Parameter_exec | BWBCRON1 > output.log

For example:

BWBCRONB | BWBCRON1 >bwbcronb.log

Build example

The samples BWBCRON1 and BWBCRONB have been copied to a test directory /var/SCLMDT/CRONJOBS.

The following HFS PATH and STEPLIB variables have been set in /etc/profile.

PATH=/var/SCLMDT/CRONJOBS:$PATH
STEPLIB=BWB.V1R1M0.SBWBLOAD:$STEPLIB

The sample BWBCRON1 has been customized as below:

/* REXX */ 
/* Customize STEPLIB and CGI_DTCONF BELOW */ 
/* 
The STEPLIB should reflect the install load library for SCLM Developer 
toolkit. 
If this data set resides in the LINKLIST then set STEPLIB to '' . 
*/ 
STEPLIB = 'BWB.V1R1M0.SBWBLOAD' 
/* 
The Environment variable CGI_DTCONF determines the HOME directory 
path where the configuration files reside for SCLM Developer Toolkit. 
This was determined by the install directory specified in install 
job BWBINST1. By default /etc/SCLMDT . 
Also configure CGI_DTWORK to reference the base directory for the WORKAREA. 
By default /var/SCLMDT.*/ 
CGI_VCMPATH = '/etc/SCLMDT'
CGI_DTCONF = '/var/SCLMDT' 
/* */ 
/* SAMPLE USEAGE */ 
/* 
COMMAND : BWBCRONB|BWBCRON1 >BWBCRONB.log 
(passes build parameter list to BWBCRON1 & outputs to BWBCRONB.log) 
*/ 
/
/* DO NOT ALTER BELOW */ 
CALL ENVIRONMENT 'STEPLIB',STEPLIB 
CALL ENVIRONMENT 'CGI_DTCONF',CGI_DTCONF 
CALL BWBINT 
EXIT 

The sample BWBCRONB has been customized as below:

/* REXX */ 
/* SAMPLE BUILD PARAMETER FILE USED FOR CRON INITIATED BUILDS */ 
/* Update Build parameters below */ 
/* if parameter required as Blank then set as '' */ 
FUNCTION = 'BUILD' 
PROJECT = 'PROJ1' /* SCLM Project */ 
PROJDEF = '' /* Alt proj definition */ 
TYPE = 'SOURCE' /* SCLM Type */ 
MEMBER = 'TESTMEM' /* SCLM Member name */ 
GROUP = 'DEV1' /* SCLM Group */ 
GROUPBLD = '' /* Build at Group */ 
REPDGRP = 'DEV1' /* Users Development group */ 
BLDREPT = 'Y' /* Generate Build report */ 
BLDLIST = 'Y' /* Generate List on error */ 
BLDMSG = 'Y' /* Generate Build Messages */ 
BLDSCOPE = 'N' /* Build Scope E/L/N/S */ 
BLDMODE = 'C' /* Build Mode C/F/R/U */ 
BLDMSGDS = '' /* Message data set */ 
BLDRPTDS = '' /* Report data set */ 
BLDLSTDS = '' /* list data set */ 
BLDEXTDS = '' /* Exit data set */ 
SUBMIT = 'BATCH' /* Online or Batch */ 
/* DO NOT ALTER PARM BUILD VARIABLE BELOW */ 
PARM1 = 'SCLMFUNC='FUNCTION'&PROJECT='PROJECT'&PROJDEF='PROJDEF||, 
'&TYPE='TYPE'&MEMBER='MEMBER'&GROUP='GROUP'&GROUPBLD='GROUPBLD||, 
'&REPDGRP='REPDGRP'&BLDREPT='BLDREPT'&BLDLIST='BLDLIST||, 
'&BLDMSG='BLDMSG'&BLDSCOPE='BLDSCOPE'&BLDMODE='BLDMODE||, 
'&BLDMSGDS='BLDMSGDS'&BLDRPTDS='BLDRPTDS'&BLDLSTDS='BLDLSTDS||, 
'&BLDEXTDS='BLDEXTDS'&SUBMIT='SUBMIT 
/* outputs parameter string as input to BWBCRON1 */ 
SAY PARM1 

Build job execution

The following sample Build execution could be added to a crontab file:

BWBCRONB|BWBCRON1 >bwbcronb.log

For example, to run at 7:30 p.m. on Monday through Friday:

30 19 * * 1-5 BWBCRONB|BWBCRON1 >bwbcronb.log;

For further information on the CRON services available and the CRONTAB format, use the online manual help (man) under Unix System Services (man cron ; man crontab; man at ) or refer to the following manuals:


Terms of use | Feedback



This information center is powered by Eclipse technology. (http://www.eclipse.org)