workflow manager - sclm attachment
TRANSCRIPT
Workflow Manager - SCLM Attachment
Workflow Manager - SCLM Attachment
Page: 2
Micro Focus
The Lawn
22-30 Old Bath Road
Newbury, Berkshire RG14 1QN
UK
http://www.microfocus.com
Copyright © 2011-2014 Micro Focus. All rights reserved.
MICRO FOCUS and the Micro Focus logo are trademarks or registered
trademarks of Micro Focus or its subsidiaries or affiliated
companies in the United States, United Kingdom and other countries.
All other marks are the property of their respective owners.
Workflow Manager - SCLM Attachment
Page: 3
Contents
1 Introduction ...................................................................................................... 5
1.1 Software requirements .................................................................................................................................. 5
2 Installation ........................................................................................................ 6
2.1 General considerations .................................................................................................................................. 6
2.2 Basic installation procedure .......................................................................................................................... 6
2.2.1 Download and unzip the software ...................................................................................................... 6
2.2.2 Upload the software to the mainframe .............................................................................................. 6
2.2.3 Receive the software .............................................................................................................................. 8
3 The SCLM Attachment ................................................................................... 9
3.1 Overview of REXX procedures .................................................................................................................. 9
3.2 Overview of ISPF skeletons ........................................................................................................................ 12
4 Server and REXX customization ................................................................. 13
4.1 Add the SCLM Workflow Model to the Master Configuration File ................................................. 13
4.2 Add the EXEC and SKELS datasets to the z/Server User Task ......................................................... 13
4.3 Optional: Add the EXEC and SKELS data sets to ISPF.conf ............................................................... 14
4.4 Customizing REXX procedures and ISPF skeletons ............................................................................. 14
4.4.1 General customization ......................................................................................................................... 14
4.4.2 SCLM Allocation exit TAUSCXA1 ................................................................................................... 15
4.4.3 File suffix assignment via exit TAUSCXMS ..................................................................................... 16
4.4.4 Exit TAUSCXP1: Determination of the relevant SCLM projects.............................................. 16
4.4.5 Exit TAUSCXP2: Additional processing during SCLM project initialization ........................... 16
4.4.6 Exit TAUSCXP3: Determine relevant SCLM project definitions .............................................. 16
4.4.7 Customizing the generation of SCLM architecture members .................................................... 17
4.4.8 Adjustment of the skeleton support for creating new members .............................................. 17
4.4.9 Integrating build notify exit TAUSCXBD ........................................................................................ 18
4.4.10 Support for error feedback during SCLM build for COBOL ................................................... 18
4.4.11 Support for error feedback during SCLM build for PLI ............................................................. 19
4.4.12 Support for error feedback during SCLM build for Assembler ............................................... 20
4.4.13 Exit TAUSCXBI: Determination of build information................................................................ 21
4.4.14 Exit TAUSCXSL: Determination of the SYSLIB concatenation ............................................... 21
5 Customizing the SCLM Model ..................................................................... 22
5.1 Action enabled conditions........................................................................................................................... 22
Workflow Manager - SCLM Attachment
Page: 4
Workflow Manager - SCLM Attachment
Page: 5
1 Introduction
The Workflow Manager SCLM Attachment consists of mainframe components that have to be
installed in a z/OS environment.
IBM Software Configuration and Library Manager (SCLM) is part of TSO/ISPF and supports the
development of mainframe applications under ISPF.
With the Workflow Manager SCLM Attachment, you can:
Provide the SCLM development process in an Eclipse-based development environment.
Customize the SCLM development process to suit your needs.
Model and customize the Eclipse-based SCLM user interface without any programming
effort.
Seamlessly integrate existing home-grown and third party tools.
This document is intended for system programmers and/or SCLM administrators installing and
configuring the Workflow Manager SCLM Attachment on their z/OS host system.
Herein, this document refers to the Workflow Manager SCLM Attachment as the SCLM
Attachment.
1.1 Software requirements
To use the SCLM Attachment, you require Enterprise Developer version 2.2 Update 1 or later
installed and configured.
Workflow Manager - SCLM Attachment
Page: 6
2 Installation
2.1 General considerations
Determine a dataset prefix that matches the naming conventions in your company. This document
will use the prefix HLQ.SCLM in all further specifications.
2.2 Basic installation procedure
2.2.1 Download and unzip the software
Download the SCLM Attachment from a download link you will receive from Micro Focus.
Unzip the download file to a temporary folder. A folder named ‘host’ is created, which contains all
mainframe installation components in binary XMIT format.
There are no client components to install.
2.2.2 Upload the software to the mainframe
The unzipped SCLM Attachment contains four XMIT files. Upload all files from the ‘host’ folder, in
binary format, to sequential datasets with a record length of 80 and a block size of 3120, using the
following procedure:
Firstly, on z/OS, allocate the datasets to use as the upload target files. To do this, create a dataset
with the same characteristics as the sample job below (or by submitting the job below). If you
choose to submit the following job, note the following:
hlq is the high level qualifier you choose to use for this dataset.
Before submitting, add a job card and modify the parameters to meet your site's
requirements.
Optionally, add a valid VOLSER and/or change the UNIT parameter.
//ALLOC1 EXEC PGM=IEFBR14
//*
//FTPALLOC DD DSN=hlq.SCLM.EXEC.XMIT,
// DISP=NEW,CATLG,DELETE),
// DSORG=PS,
// RECFM=FB,
// LRECL=80,
// BLKSIZE=3120,
//* VOL=SER=vvvvvv,
Workflow Manager - SCLM Attachment
Page: 7
// UNIT=SYSALLDA,
// SPACE=(TRK,(45,15))
To upload the files, you can use FTP from a command prompt. In the sample dialog shown below,
commands or other information entered by a user are displayed in bold, and the values in the
following table are assumed:
User input Description
mvsaddr TCP/IP address or hostname of the z/OS system
tsouid Your TSO user ID
tsopw Your TSO password
hlq High-level qualifier used for the data set you allocated in the job above
C:\>ftp mvsaddr
Connected to mvsaddr.
220-FTPD1 IBM FTP CS V1R10 at custom.com, 12:03:32 on 2011-08-02.
220 Connection will close if idle for more than 5 minutes.
User (mvsaddr:(none)): tsouid
331 Send password please.
Password: tsopw
230 tsouid is logged on. Working directory is "tsouid.".
ftp> cd ..
250 " " is the working directory name prefix.
ftp> cd hlq
250 "hlq." is the working directory name prefix.
ftp> binary
200 Representation type is Image
ftp> put d:\host\hlq.SCLM.EXEC.XMIT
200 Port request OK.
125 Storing data set hlq.SCLM.EXEC.XMIT
250 Transfer completed successfully.
Workflow Manager - SCLM Attachment
Page: 8
Executing this procedure, transfers the following files to your mainframe:
HLQ.SCLM.EXEC.XMIT
HLQ.SCLM.ARCHDEF.XMIT
HLQ.SCLM.SKELS.XMIT
HLQ.SCLM.XML.XMIT
2.2.3 Receive the software
Use the TSO RECEIVE command to create the partitioned datasets from the sequential XMIT files.
HLQ.CMG is the assumed installation prefix.
Enter TSO or Workstation commands below:
===> receive indataset('hlq.SCLM.EXEC.XMIT')
When prompted, enter:
INMR906A Enter restore parameters or 'DELETE' or 'END' +
restore dataset('hlq.SCLM.EXEC’)
The result is a partitioned dataset containing REXX procedures.
Repeat the RECEIVE process for the SKELS, the XML and the ARCHDEF datasets.
Workflow Manager - SCLM Attachment
Page: 9
3 The SCLM Attachment
3.1 Overview of REXX procedures
All REXX procedures used within the SCLM Attachment are listed in the SCLM HLL architecture
members. The top architecture member is TAUSCLM and is contained in HLQ.SCLM.ARCHDEF.
The dataset HLQ.SCLM.ARCHDEF is shipped for documentation only. However, you can migrate
the shipped REXX procedures, ISPF skeletons and SCLM architecture members into your own
SCLM project and use the architecture member TAUSCLM to build and promote the complete
SCLM Attachment.
The following REXX procedures are part of the SCLM Attachment:
REXX name Description
SCLM Member
Actions
TAUSCINS Lock a new SCLM member and set its access key. A new member can
be edited locally and later with check-in (TAUSCCIN) can be copied
under the control of SCLM
TAUSCIN2 Create a new member under SCLM
TAUSCCPY Copy an SCLM member
TAUSCCIN Check-in an SCLM member – After local edit
TAUSCCOU Check-out an SCLM member – For local edit
TAUSCLCK Set SCLM access key.
TAUSCBDO SCLM Build
TAUSCPMO SCLM Promote
TAUSCDEL Delete an SCLM member
TAUSCRES Remove SCLM access key
TAUSCGVM Copy an SCLM member from the version inventory to the development
group
TAUSCARC Generate an SCLM source from an SCLM architecture definition
TAUSCRSC Remote syntax check for an SCLM source member
TAUSCRFR Determine copies related to an SCLM source
TAUSCNDS Determine the next SCLM dataset in the hierarchy that contains a given
Workflow Manager - SCLM Attachment
Page: 10
REXX name Description
member (i.e. relevant in use with Compare Next )
TAUSCSPR Change Code and/or change/add Language
TAUSCBMP Determine build map Information
TAUSCGCC Determine Information relating to associated Change Codes
SCLM Table Actions For table structures
TAUSCELI Create SCLM member list
TAUSCGVE Create an SCLM list of audit records corresponding to an SCLM
member
TAUSCDLI SCLM list with dependent members corresponding to an SCLM member
(Build Map Context)
TAUSCDL2 SCLM list with dependent members corresponding to an Archdef (Build
Map Context)
Determination of
SCLM Properties
To complete the Properties view
TAUSCEPR Determine the properties of an SCLM member (SCLM Accounting
Record)
TAUSCGVP Determine the properties of a versioned SCLM member (SCLM Audit
Record)
SCLM Structure
Actions
For the tree structure
TAUSCGPR Determine the SCLM-Project
TAUSCGPD Determine all SCLM-Project definitions corresponding to an SCLM
project
TAUSCGGR Determine all SCLM-Groups within a project definition
TAUSCGTY Determine all SCLM-Types within a project definition
SCLM Value for
Retrieve Actions
TAUSCVPR Determine valid SCLM projects
TAUSCVPD Determine valid SCLM project definitions
TAUSCVGR Determine valid SCLM groups
Workflow Manager - SCLM Attachment
Page: 11
REXX name Description
TAUSCVTY Determine valid SCLM types
TAUSCGLA Determine valid SCLM languages
Utilities Used as subroutines
TAUSCINF Determine valid SCLM groups, types, and languages from the SCLM-
Project definition
TAUSCPRJ Determine SCLM project
TAUSCAPR Determine SCLM project definitions
TAUSCMSU Determine Eclipse file suffix for a given SCLM member
TAUSCNGR Determine next SCLM group in the SCLM hierarchy
TAUSCLMS Remove SCLM flag from ISPF Statistics
TAUSCSRC SCLM search function
Exits for SCLM
TAUSCXA1 Allocation of (temporary) files for the SCLM Attachment
TAUSCXMS Assignment SCLM member to Eclipse file suffix
TAUSCXBI Exit to determine information from SCLM for the Remote Syntax
Check (SYSLIB, Compile Parameter)
TAUSCXSL Exit to determine the SYSLIB concatenation from SCLM
TAUSCXP1 Determine SCLM project
TAUSCXP2 Exit when SCLM project definition is changed
TAUSCXP3 Determine SCLM project definitions
SCLM Translator /
Exits
TAUSCBND SCLM Build/Promote REXX sample for DB2 relevant languages: Execute
Bind Plan or Bind Package
TAUSCPLA SCLM Build Translator REXX sample for PLI languages: Allocate
SYSXMLSD
TAUSCXBD SCLM Build Notify exit, to inform about generated Build Output
member
TAUSCXIN Skeleton support for a new member
Workflow Manager - SCLM Attachment
Page: 12
3.2 Overview of ISPF skeletons
All ISPF skeletons that are used as part of an SCLM Attachment are listed in the SCLM architecture
member: TAUSCLM.
The following ISPF skeletons are used:
Skeleton name Description
TAUSCCOM Skeleton for the generation of SCLM architecture definitions
Generation of CC Archdef
TAUSCLNK Skeleton for the generation of SCLM architecture definitions
Generation of Link Archdef
TAUSCHLL Skeleton for the generation of SCLM architecture definitions
Generation of High Level Language (HLL) Archdef
TAUSCPKG Skeleton for the generation of SCLM architecture definitions
Generation of Bind Package REXX
TAUSCPLN Skeleton for the generation of SCLM architecture definitions
Generation of Bind Plan REXX
TAUSCSAC Skeleton for a new COBOL member
TAUSCSAH Skeleton for a new HLL Archdef member
TAUSCSAP Skeleton for a new PLI member
TAUSCSAA Skeleton for a new ASSEMBLER member
Workflow Manager - SCLM Attachment
Page: 13
4 Server and REXX customization Before using the SCLM Attachment for the first time, you have to perform some modifications to
the supplied REXX procedures and ISPF skeletons.
4.1 Add the SCLM Workflow Model to the Master
Configuration File
Edit the Master Configuration file and insert the following reference to the SCLM workflow model.
*
* SCLM Workflow Model
*
* application name
User:
Appl: EDTE SCLM Application
* location of the application configuration file
Conf: MVS:HLQ.SCLM.XML(SCLME221)
* application version number
Version: 2.2.1
* process information
INFO:
* end of application definition. Do not delete this line
EndAppl:
EndUser:
You must customize the Conf: entry to reference the installed XML dataset. If the SCLM attachment
is used within Rational Developer for System z with the IBM RSE daemon as server, refer to the
SCLMR221 member.
4.2 Add the EXEC and SKELS datasets to the z/Server User
Task
Within the z/Server User Task, you must concatenate the received dataset HLQ.SCLM.EXEC to the
SYSEXEC allocation, and add the received dataset HLQ.SCLMSKELS to the ISPSLIB allocation.
Micro Focus recommends that you customize the JCL of the z/Server User Task to perform this
allocation (see z/Server Installation Guide for details on how to set up a User Server):
Workflow Manager - SCLM Attachment
Page: 14
……
//IVPISPF EXEC PGM=IKJEFT1B,PARM='%IVPINIT1 &PORT ',
// DYNAMNBR=200,REGION=0M
//STEPLIB DD DSN=&TAURHLQ..LOADLIB,DISP=SHR
//SYSEXEC DD DSN=&TAURHLQ..EXEC,DISP=SHR
// DD DSN=HLQ.SCLM.EXEC,DISP=SHR
// DD DSN=&TAURHLQ..REXX,DISP=SHR
//ISPPLIB DD DSN=&ISPFHLQ..SISPPENU,DISP=SHR
// DD DSN=ISF.SISFPLIB,DISP=SHR
//ISPSLIB DD DSN=&ISPFHLQ..SISPSENU,DISP=SHR
// DD DSN=HLQ.SCLM.SKELS,DISP=SHR
// DD DSN=ISF.SISFSLIB,DISP=SHR
//ISPMLIB DD DSN=&ISPFHLQ..SISPMENU,DISP=SHR
// DD DSN=ISF.SISFMLIB,DISP=SHR
……
Alternatively, you can dynamically allocate by customizing the exit procedure TAUTOXA1.
4.3 Optional: Add the EXEC and SKELS datasets to ISPF.conf
If the SCLM attachment is used within Rational Develper for System z with the IBM RSE daemon as
server, you must add the installation EXEC and SKELS datasets to the configuration file ISPF.conf in
the USS configuration path of the RSE daemon.
4.4 Customizing REXX procedures and ISPF skeletons
4.4.1 General customization
Regarding the SCLM Attachment, the following adaptations are of special importance:
REXX procedure Description
TAUZCAPP If the SCLM attachment is used within Enterprise Developer with
z/Server as server, adjust the reference to the location of the master
configuration file, as required.
Default: HLQ.ZSERVER.MASTER
TAULAPPL If the SCLM attachment is used within Rational Developer for System z
with the IBM RSE daemon as server, adjust the reference to the location
Workflow Manager - SCLM Attachment
Page: 15
of the master configuration file, as required.
Default: HLQ.ZSERVER.MASTER
TAUTOXA1
Tool interface exit: use this exit for dynamic allocations or to set ISPF
environment variables necessary to run your specific SCLM Application.
With a standard SCLM installation you do not need to customize this
exit.
TAUTOXA2 General allocation exit: use the exit to allocate general temporary files.
The REXX procedure is used within the SCLM Attachment to allocate
temporary datasets when executing a string search in SCLM datasets.
TAUTOXCA
Exit for Assembler Remote Syntax Check: customize the load libraries, as
required
TAUTOXCC
Exit for COBOL Remote Syntax Check: customize load libraries, as
required
TAUTOXCP
Exit for PLI Remote Syntax Check; customize load libraries, as required
Skeleton name Description
TAUTOXIS
Skeleton for batch support: allocates an ISPF batch environment
The SCLM Attachment uses this skeleton if you submit an SCLM build for
batch execution.
TAUTOXJC
Skeleton for batch support: defines a default job card
The SCLM Attachment uses this skeleton if the user submits an SCLM
build for batch execution.
Regardless of the SCLM Attachment, it is necessary for you to perform some customization after
the installation of the z/Server. Refer to chapters titled ISPF Exits and Master Configuration of the
Workflow Manager Configuration Guide.
4.4.2 SCLM Allocation exit TAUSCXA1
Data is partially interchanged using files for the communication between the client and the SCLM
Attachment. The creation of the (temporary) files takes place in the procedure TAUSCXA1.
TAUSCXA1 should be adjusted to the available environment, as required.
Files that begin with userid TAUSCTMP are created by default. These files are temporary in nature,
but are not deleted automatically within the tool attachment. Instead, they can be reused once
created, if necessary.
Micro Focus recommends that you place these files on a work unit and allow them to be deleted
when inactive for a long period of time.
Workflow Manager - SCLM Attachment
Page: 16
4.4.3 File suffix assignment via exit TAUSCXMS
A file must contain the correct suffix (e.g. CBL, JCL) in order to be opened with the required editor.
The assignment of an SCLM member to a file suffix typically depends on its assigned SCLM language.
In some cases, the SCLM type alone can also be enough to make this assignment possible.
You can use the exit TAUSCXMS to associate the values of the file suffix to the SCLM member.
As long as no specific editor exists for the SCLM member, TXT should be assigned as a suffix.
Note: This exit returns an output parameter called ‘Property Set name’; although not currently
supported, you must still return a non-blank value (e.g. NONE).
4.4.4 Exit TAUSCXP1: Determination of the relevant SCLM projects
The SCLM application displays SCLM projects as first level elements in its tree structure.
Furthermore, different dialogs exist through which SCLM projects can be selected, by using a
Retrieve button. You can determine the relevant SCLM projects for each respective user through
the exit TAUSCXP1.
If this exit procedure is not adjusted, implying that no SCLM projects are specified, the tool
attachment uses the naming convention *.PROJDEFS.LOAD to determine all available SCLM projects
in the system. This process of determining all available SCLM projects may lead to unfavorable
performance or the process being stopped by the system. In some systems, such dataset queries are
not allowed. Therefore, Micro Focus strongly recommends that you provide the exit with the
appropriate logic enabling it to determine the relevant SCLM projects.
4.4.5 Exit TAUSCXP2: Additional processing during SCLM project initialization
Exit TAUSCXP2 is invoked whenever the SCLM Attachment accesses or changes an SCLM project
definition for the first time. For example, use this exit to set specific environment variables (ISPF
shared pool or profile variables) relating to an SCLM project and SCLM project definition.
This is intended for the case where a custom-developed SCLM translator and SCLM exit uses
environment variables that are set outside of SCLM. As long as values of the environment variables
are not dependent on the SCLM project definition, it is recommended to use the general exit
TAUTOXAI instead of its SCLM exit.
4.4.6 Exit TAUSCXP3: Determine relevant SCLM project definitions
The SCLM application displays SCLM project definitions in the second level of its tree structure. You
can further define an SCLM project using the Retrieve option. Use this exit to determine the
relevant SCLM project definitions for each user.
All available load modules are defined in the ‘project.PROJDEFS.LOAD’ file, and without adaptation
the tool attachment would interpret these member names as valid names for the project definitions.
Micro Focus recommends that you use exit TAUSCXP3 to determine the relevant project
definitions according to appropriate rules (e.g. naming conventions), or to filter out names that do
not correspond to any project definition or that are for administrative purposes only.
Workflow Manager - SCLM Attachment
Page: 17
4.4.7 Customizing the generation of SCLM architecture members
The SCLM model contains an action that generates all necessary architecture members belonging to
an SCLM member. Before using this action, you should customize it, as required.
The included generation example uses the following components:
REXX
/skeletons
Description
TAUSCARC Generating SCLM architecture definitions corresponding to an SCLM source
Adjustments are necessary during variable initialization (type names, language, and
member) in the upper part of the procedure.
TAUSCCOM Skeleton for generating SCLM architecture definitions
Adjustments to the layouts for generating CC Archdefs are necessary
TAUSCLNK Skeleton for generating SCLM architecture definitions
Adjustments to the layouts for generating Link Archdefs are necessary
TAUSCHLL Skeleton for generating SCLM architecture definitions
Adjustments to the layouts for generating HLL Archdefs are necessary
TAUSCPKG Skeleton for generating SCLM architecture definitions
Adjustments for generating bind package REXX are necessary
TAUSCPLN Skeleton for generating SCLM architecture definitions
Adjustments for generating bind plan REXX are necessary
TAUSCBND SCLM REXX sample for DB2 relevant languages: Execute Bind Plan or Bind
Package (Access is through the Bind Package / Bind Pk, process (compare
Skeletons TAUSCPKG, TAUSCPLN)).
Adaptation to the existing promote structure is necessary.
4.4.8 Adjustment of the skeleton support for creating new members
The SCLM model contains an action that you can use to create a new SCLM member. A skeleton
can be retrieved depending on the SCLM language. If no skeleton is assigned, an empty member is
created. Generally, this action, including the skeleton to be used, must be adapted for each
implementation.
Workflow Manager - SCLM Attachment
Page: 18
The included example uses the following components:
REXX
/skeletons
Description
TAUSCXIN Insert exit
Depending on the parameter passed as SCLM language, a skeleton is assigned
TAUSCSAC Skeleton for a new COBOL member
TAUSCSAH Skeleton for a new HLL Archdef member
TAUSCSAP Skeleton for a new PLI member
TAUSCSAA Skeleton for a new ASSEMBLER member
4.4.9 Integrating build notify exit TAUSCXBD
If the SCLM Attachment should insert the generated output members directly in the current Eclipse
table after a successful SCLM build, the build notify exit of the SCLM language definition must be
active and the procedure TAUSCXBD must be submitted as an exit. If this exit has already been
used, call the procedure TAUSCXBD as a sub-routine in the already defined exit procedure.
The definition of a build exit occurs in the project definition using the macro FLMCNTRL:
FLMCNTRL ACCT=SCLM.ACCOUNT.FILE, C
VERS=SCLM.VERSION.FILE, C
BLDNTF=SELECT, C
BLDNTFCM=ISPLNK, C
BLDNTFOP='NEST CMD(TAUSCXBD,', C
MAXVIO=999999, C
VIOUNIT=VIO
4.4.10 Support for error feedback during SCLM build for COBOL
The SCLM Attachment supports error feedback for COBOL programs in connection with an SCLM
build. Use the compiler option ADATA together with the COBOL exit TAURTOCX, and allocate
the error feedback file as a member of a PDS file in a build translator. Use the REXX procedure
TAUSCPLA for this purpose.
A maximum of 250 messages are returned from the exit. You can reduce this amount using the
option /N. The maximum number of warning and informational messages is specified with /W, and
this value must be fewer than the one specified for /N. If not specified, the default value is set to 20.
FLMTRNSL CALLNAM='XMLDAT', C
FUNCTN=BUILD, C
Workflow Manager - SCLM Attachment
Page: 19
CALLMETH=ISPLNK, C
COMPILE=SELECT, C
VERSION=1.0, C
GOODRC=0, C
PDSDATA=Y, C
PORDER=1, C
OPTIONS='CMD(TAUSCPLA §§FLMMBR)NEST'
FLMTRNSL CALLNAM='ENTERPRISE COBOL COMPILER', C
FUNCTN=BUILD, C
COMPILE=IGYCRCTL, C
DSNAME=IGY410.SIGYCOMP, C
VERSION=3.3.1, C
GOODRC=4, C
PORDER=1, C
OPTIONS='FLAG(I,I),ADATA,LIB,LIST,TEST(NOHOOK,SEPARATE),C
EXIT(ADEXIT(''/N 100 /W 50'',TAURTOCX))'
* (* SYSADATA *)
FLMALLOC IOTYPE=W,RECFM=VB,LRECL=1020,RECNUM=500000, C
DDNAME=SYSADATA
4.4.11 Support for error feedback during SCLM build for PLI
The SCLM Attachment supports error feedback for PLI programs in connection with the SCLM
build. Use the XINFO (XML) compiler option for this and ensure that the XML file is allocated to a
build translator. You can use the REXX procedure TAUSCPLA for this translator.
***********************************************************************
* -- ZUSAETZLICHER BUILD TRANSLATOR *
* (REXX-PROCEDURE CALL TO ALLOCATE XML FILE) *
***********************************************************************
*
FLMTRNSL CALLNAM='XMLDAT', C
FUNCTN=BUILD, C
Workflow Manager - SCLM Attachment
Page: 20
CALLMETH=ISPLNK, C
COMPILE=SELECT, C
VERSION=1.0, C
GOODRC=0, C
PDSDATA=Y, C
PORDER=1, C
OPTIONS='CMD(TAUSCPLA §§FLMMBR)NEST'
FLMTRNSL CALLNAM='ENTERPRISE PL/I COMPILER', C
FUNCTN=BUILD, C
COMPILE=IBMZPLI, C
DSNAME=IEL370.SIBMZCMP, C
VERSION=3.3.0, C
GOODRC=4, C
PORDER=1, C
OPTIONS=(MACRO,OBJECT,SOURCE,XREF,XINFO(XML))
4.4.12 Support for error feedback during SCLM build for Assembler
The tool attachment supports error feedback for Assembler programs in connection with the SCLM
build. Use the compiler option ADATA together with the Assembler exit TAURTOAX, and allocate
the error feedback file as a member of a PDS file in an already started build translator. You can use
the REXX procedure TAUSCPLA for this purpose.
A maximum of 250 messages are returned from the exit. You can reduce this amount using the
option /N. The maximum number of warning and informational messages is specified with /W, and
this value must be fewer than the one specified for /N. If not specified, the default value is set to 20.
FLMTRNSL CALLNAM='XMLDAT', C
FUNCTN=BUILD, C
CALLMETH=ISPLNK, C
COMPILE=SELECT, C
VERSION=1.0, C
GOODRC=0, C
PDSDATA=Y, C
PORDER=1, C
Workflow Manager - SCLM Attachment
Page: 21
OPTIONS='CMD(TAUSCPLA §§FLMMBR)NEST'
FLMTRNSL CALLNAM='ENTERPRISE COBOL COMPILER', C
FUNCTN=BUILD, C
COMPILE=IGYCRCTL, C
DSNAME=IGY410.SIGYCOMP, C
VERSION=3.3.1, C
GOODRC=4, C
PORDER=1, C
OPTIONS='XREF(SHORT),LINECOUNT(75),OBJECT,RENT,ADATA,EXIC
T(ADEXIT(TAURTOAX(''/N 100 /W 25'')))'
* (* SYSADATA *)
FLMALLOC IOTYPE=W,RECFM=VB,LRECL=1020,RECNUM=500000, C
DDNAME=SYSADATA
4.4.13 Exit TAUSCXBI: Determination of build information
The exit TAUSCXBI determines build information from SCLM which is needed for remote syntax
check. The shipped exit TAUSCXBI uses the SCLM build info command to determine this
information.
The result of the SCLM build information is parsed and returned partly by Shared Pool variables and
partly as return values.
The exit has to be adapted when the build info command provides other information on the
customer site than that expected by the exit, e.g. another compiler name.
The exit can also be adapted if the required build information can be determined by another,
possbily less expensive, way.
4.4.14 Exit TAUSCXSL: Determination of the SYSLIB concatenation
The exit TAUSCXSL determines the SYSLIB concatenation from SCLM. The shipped exit
TAUSCXSL determines the SYSLIB concatenation by a call to the exit TAUSCXBI.
The exit should be adapted if there is another, possibly less expensive way, at the customer site to
determine the SYSLIB concatenation.
Workflow Manager - SCLM Attachment
Page: 22
5 Customizing the SCLM Model
If you use the SCLM attachment within Enterprise Developer with z/Server as server, you must
customize the SCLME221 model. If you use the SCLM attachment within Rational Developer for
System z with the IBM RSE daemon as server, you must customize the SCLMR221 model.
If you do customize the SCLM model, save the model member beforehand.
5.1 Action enabled conditions
Depending on the SCLM project definitions, it makes sense to add some action-enabled conditions
to the SCLM model.
Micro Focus recommends that you adapt the following action-enabled conditions (Element Type:
ELEEditable), as required. (The given values PROD and SOURCE below are sample values and
have to be replaced by the values defined in the SCLM project definition.)
Relationship Condition(s)
ACTCompareNext The action should not be executable on the last group,
for example:
Condition: PROPGroup Equals not… PROD
ACTDeleteMember The action should not be executable on productive
members, for example:
Condition: PROPGroup Equals not… PROD
ACTRemoteSyntaxCheck The action should only be executable on program code,
for example:
Condition: PROPType Equals… SOURCE
ACTGetVersionList The action should only be executable on versioned
members, for example:
Condition: PROPGroup Equals… PROD
ACTRetrieveVersion The action should only be executable on versioned
members, for example:
Condition: PROPGroup Equals… PROD
ACTArchgen The action should only be executable on program code,
for example:
Condition: PROPType Equals… SOURCE
Workflow Manager - SCLM Attachment
Page: 23
Figure 1. Sample "Action Enabled Conditions" in the Model editor
Workflow Manager - SCLM Attachment
Page: 24