Workflow Manager SCLM Attachment

Transcription

1 Workflow Manager SLM Attachment

2 Micro Focus The Lawn Old Bath Road Newbury, Berkshire RG14 1QN UK opyright Micro Focus. All rights reserved. MIRO FOUS, the Micro Focus logo and are trademarks or registered trademarks of Micro Focus IP Development Limited 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 ii

3 ontents Introduction... 4 Software requirements... 4 Installation... 5 General considerations... 5 Basic installation procedure... 5 Download and unzip the software... 5 Upload the software to the mainframe... 5 Receive the software...6 The SLM Attachment... 7 Overview of REXX procedures... 7 Overview of ISPF skeletons... 9 Server and REXX customization...10 Add the SLM workflow model to the Master onfiguration file Add the EXE and SKELS datasets to the z/server User Task Optional: Add the EXE and SKELS datasets to ISPF.conf ustomizing REXX procedures and ISPF skeletons General customization...11 SLM Allocation exit TAUSXA File suffix assignment via exit TAUSXMS Exit TAUSXP1: Determination of the relevant SLM projects Exit TAUSXP2: Additional processing during SLM project initialization Exit TAUSXP3: Determine relevant SLM project definitions...13 ustomizing the generation of SLM architecture members...13 Adjustment of the skeleton support for creating new members...14 Integrating build notify exit TAUSXBD...14 Support for error feedback during SLM build for OBOL Support for error feedback during SLM build for PLI Support for error feedback during SLM build for Assembler Exit TAUSXBI: Determination of build information Exit TAUSXSL: Determination of the SYSLIB concatenation...16 ustomizing the SLM model...17 Action enabled conditions ontents 3

4 Introduction The Workflow Manager SLM Attachment consists of mainframe components that have to be installed in a z/os environment. IBM Software onfiguration and Library Manager (SLM) is part of TSO/ISPF and supports the development of mainframe applications under ISPF. With the Workflow Manager SLM Attachment, you can: Provide the SLM development process in an Eclipse-based development environment. ustomize the SLM development process to suit your needs. Model and customize the Eclipse-based SLM user interface without any programming effort. Seamlessly integrate existing home-grown and third party tools. This document is intended for system programmers and/or SLM administrators installing and configuring the Workflow Manager SLM Attachment on their z/os host system. Herein, this document refers to the Workflow Manager SLM Attachment as the SLM Attachment. Software requirements To use the SLM Attachment, you require Enterprise Developer version 2.2 Update 1 or later installed and configured. 4 Introduction

5 Installation General considerations Determine a dataset prefix that matches the naming conventions in your company. This document will use the prefix HLQ.SLM in all further specifications. Basic installation procedure Download and unzip the software Download the SLM 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. Upload the software to the mainframe The unzipped SLM 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. //ALLO1 EXE PGM=IEFBR14 //* //FTPALLO DD DSN=hlq.SLM.EXE.XMIT, // DISP=NEW,ATLG,DELETE), // DSORG=PS, // REFM=FB, // LREL=80, // BLKSIZE=3120, //* VOL=SER=vvvvvv, // UNIT=SYSALLDA, // SPAE=(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 mvsaddr TP/IP address or hostname of the z/os system Installation 5

6 User input tsouid tsopw hlq Your TSO user ID Your TSO password High-level qualifier used for the data set you allocated in the job above :\>ftp mvsaddr onnected to mvsaddr. 220-FTPD1 IBM FTP S V1R10 at custom.com, 12:03:32 on onnection 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 " " 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.slm.exe.xmit 200 Port request OK. 125 Storing data set hlq.slm.exe.xmit 250 Transfer completed successfully. Executing this procedure, transfers the following files to your mainframe: HLQ.SLM.EXE.XMIT HLQ.SLM.ARHDEF.XMIT HLQ.SLM.SKELS.XMIT HLQ.SLM.XML.XMIT Receive the software Use the TSO REEIVE command to create the partitioned datasets from the sequential XMIT files. HLQ.MG is the assumed installation prefix. Enter TSO or Workstation commands below: ===> receive indataset('hlq.slm.exe.xmit') When prompted, enter: INMR906A Enter restore parameters or 'DELETE' or 'END' + restore dataset('hlq.slm.exe ) The result is a partitioned dataset containing REXX procedures. Repeat the REEIVE process for the SKELS, the XML and the ARHDEF datasets. 6 Installation

7 The SLM Attachment Overview of REXX procedures All REXX procedures used within the SLM Attachment are listed in the SLM HLL architecture members. The top architecture member is TAUSLM and is contained in HLQ.SLM.ARHDEF. The dataset HLQ.SLM.ARHDEF is shipped for documentation only. However, you can migrate the shipped REXX procedures, ISPF skeletons and SLM architecture members into your own SLM project and use the architecture member TAUSLM to build and promote the complete SLM Attachment. The following REXX procedures are part of the SLM Attachment: REXX name SLM Member Actions TAUSINS TAUSIN2 TAUSPY TAUSIN TAUSOU TAUSLK TAUSBDO TAUSPMO TAUSDEL TAUSRES TAUSGVM TAUSAR TAUSRS TAUSRFR TAUSNDS TAUSSPR TAUSBMP TAUSG SLM Table Actions TAUSELI Lock a new SLM member and set its access key. A new member can be edited locally and later with check-in (TAUSIN) can be copied under the control of SLM reate a new member under SLM opy an SLM member heck-in an SLM member After local edit heck-out an SLM member For local edit Set SLM access key. SLM Build SLM Promote Delete an SLM member Remove SLM access key opy an SLM member from the version inventory to the development group Generate an SLMsource from an SLMarchitecturedefinition Remote syntax check for an SLM source member Determine copies related to an SLMsource Determine the next SLM dataset in the hierarchythat contains a given member (i.e. relevant in use with ompare Next ) hange ode and/or change/add Language Determine build map Information Determine Information relating to associated hange odes For table structures reate SLM member list The SLM Attachment 7

8 REXX name TAUSGVE TAUSDLI TAUSDL2 Determination of SLM Properties TAUSEPR TAUSGVP SLM Structure Actions TAUSGPR TAUSGPD TAUSGGR TAUSGTY SLM Value for Retrieve Actions TAUSVPR TAUSVPD TAUSVGR TAUSVTY TAUSGLA Utilities TAUSINF TAUSPRJ TAUSAPR TAUSMSU TAUSNGR TAUSLMS TAUSSR Exits for SLM TAUSXA1 TAUSXMS TAUSXBI TAUSXSL TAUSXP1 TAUSXP2 TAUSXP3 SLM Translator / Exits reate an SLM list of audit records corresponding to an SLM member SLMlistwith dependentmembers correspondingtoan SLMmember (Build Map ontext) SLM list with dependentmembers correspondingto an Archdef (Build Map ontext) To complete the Properties view Determine the properties of an SLM member (SLM Accounting Record) Determine the properties of a versioned SLM member (SLM Audit Record) For the tree structure Determine the SLM-Project Determine all SLM-Project definitions corresponding to an SLMproject Determine all SLM-Groups within a project definition Determine all SLM-Types within a project definition Determine valid SLM projects Determine valid SLM project definitions Determine valid SLM groups Determine valid SLM types Determine valid SLM languages Used as subroutines Determine valid SLM groups, types, and languages from the SLM-Project definition Determine SLM project Determine SLM project definitions Determine Eclipse file suffix for a given SLM member Determine next SLM group in the SLM hierarchy Remove SLM flag from ISPF Statistics SLM search function Allocation of (temporary) files for the SLM Attachment Assignment SLM member to Eclipse file suffix Exit to determine information from SLM for the Remote Syntax heck (SYSLIB, ompile Parameter) Exit to determine the SYSLIB concatenation from SLM Determine SLM project Exit when SLM project definition is changed Determine SLM project definitions 8 The SLM Attachment

9 REXX name TAUSBND TAUSPLA TAUSXBD TAUSXIN SLM Build/Promote REXX sample for DB2 relevant languages: Execute Bind Plan or Bind Package SLM Build Translator REXX sample for PLI languages: Allocate SYSXMLSD SLM Build Notify exit, to inform about generated Build Output member Skeleton support for a new member Overview of ISPF skeletons AllISPFskeletonsthat are usedas part of anslm Attachment are listed in the SLM architecture member: TAUSLM. The following ISPF skeletons are used: Skeleton name TAUSOM TAUSLNK TAUSHLL TAUSPKG TAUSPLN TAUSSA TAUSSAH TAUSSAP TAUSSAA Skeleton for the generation of SLM architecture definitions Generation of Archdef Skeleton for the generation of SLM architecture definitions Generation of Link Archdef Skeleton for the generation of SLM architecture definitions Generation of High Level Language (HLL) Archdef Skeleton for the generation of SLM architecture definitions Generation of Bind Package REXX Skeleton for the generation of SLM architecture definitions Generation of Bind Plan REXX Skeleton for a new OBOL member Skeleton for a new HLL Archdef member Skeleton for a new PLI member Skeleton for a new ASSEMBLER member The SLM Attachment 9

10 Server and REXX customization Before using the SLM Attachment for the first time, you have to perform some modifications to the supplied REXX procedures and ISPF skeletons. Add the SLM workflow model to the Master onfiguration file Edit the Master onfiguration file and insert the following reference to the SLM workflow model. * * SLM Workflow Model * * application name User: Appl: EDTE SLM Application * location of the application configuration file onf: MVS:HLQ.SLM.XML(SLME221) * application version number Version: * process information INFO: * end of application definition. Do not delete this line EndAppl: EndUser: You must customize the onf: entry to reference the installed XML dataset. If the SLM attachment is used within Rational Developer for System z with the IBM RSE daemon as server, refer to the SLMR221 member. Add the EXE and SKELS datasets to the z/server User Task Within the z/server User Task, you must concatenate the received dataset HLQ.SLM.EXE to the SYSEXE allocation, and add the received dataset HLQ.SLMSKELS to the ISPSLIB allocation. Micro Focus recommends that you customize the JL of the z/server User Task to perform this allocation (see Steps to activate z/server in the z/server Installation Guide for details on how to set up a User Server): //IVPISPF EXE PGM=IKJEFT1B,PARM='%IVPINIT1 &PORT ', // DYNAMNBR=200,REGION=0M //STEPLIB DD DSN=&TAURHLQ..LOADLIB,DISP=SHR //SYSEXE DD DSN=&TAURHLQ..EXE,DISP=SHR // DD DSN=HLQ.SLM.EXE,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.SLM.SKELS,DISP=SHR // DD DSN=ISF.SISFSLIB,DISP=SHR //ISPMLIB DD DSN=&ISPFHLQ..SISPMENU,DISP=SHR 10 Server and REXX customization

11 // DD DSN=ISF.SISFMLIB,DISP=SHR Alternatively, you can dynamically allocate by customizing the exit procedure TAUTOXA1. Optional: Add the EXE and SKELS datasets to ISPF.conf If the SLM attachment is used within Rational Develper for System z with the IBM RSE daemon as server, you must add the installation EXE and SKELS datasets to the configuration file ISPF.conf in the USS configuration path of the RSE daemon. ustomizing REXX procedures and ISPF skeletons General customization Regarding the SLM Attachment, the following adaptations are of special importance: REXX procedure TAUZAPP TAULAPPL TAUTOXA1 TAUTOXA2 TAUTOXA TAUTOX TAUTOXP If the SLM 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 If the SLM attachment is used within Rational Developer for System z with the IBM RSE daemon as server, adjust the reference to the location of the master configuration file, as required. Default: HLQ.ZSERVER.MASTER Tool interface exit: use this exit for dynamic allocations or to set ISPF environment variables necessary to run your specific SLM Application. With a standard SLM installation you do not need to customize this exit. General allocation exit: use the exit to allocate general temporary files. The REXX procedure is used within the SLM Attachment to allocate temporary datasets when executing a string search in SLM datasets. Exit for Assembler Remote Syntax heck: customize the load libraries, as required Exit for OBOL Remote Syntax heck: customize load libraries, as required Exit for PLI Remote Syntax heck; customize load libraries, as required Skeleton name TAUTOXIS Skeleton for batch support: allocates an ISPF batch environment The SLM Attachment uses this skeleton if you submit an SLM build for batch execution. Server and REXX customization 11

12 Skeleton name TAUTOXJ Skeleton for batch support: defines a default job card The SLM Attachment uses this skeleton if the user submits an SLM build for batch execution. Regardless of the SLM Attachment, it is necessary for you to perform some customization after the installation of the z/server. Refer to ISPF exits and Master configuration in the Workflow Manager onfiguration Guide. SLM Allocation exit TAUSXA1 Data is partially interchanged using files for the communication between the client and the SLM Attachment. The creation of the (temporary) files takes place in the procedure TAUSXA1. TAUSXA1 should be adjusted to the available environment, as required. Files that begin with userid TAUSTMP 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. File suffix assignment via exit TAUSXMS A file must contain the correct suffix (e.g. BL, JL) in order to be opened with the required editor. The assignment of an SLM member to a file suffix typically depends on its assigned SLM language. In some cases, the SLM type alone can also be enough to make this assignment possible. You can use the exit TAUSXMS to associate the values of the file suffix to the SLM member. As long as no specific editor exists for the SLM 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). Exit TAUSXP1: Determination of the relevant SLM projects The SLM application displays SLM projects as first level elements in its tree structure. Furthermore, different dialogs exist through which SLM projects can be selected, by using a Retrieve button. You can determine the relevant SLM projects for each respective user through the exit TAUSXP1. If this exit procedure is not adjusted, implying that no SLM projects are specified, the tool attachment uses the naming convention *.PROJDEFS.LOAD to determine all available SLM projects in the system. This process of determining all available SLM 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 SLM projects. Exit TAUSXP2: Additional processing during SLM project initialization Exit TAUSXP2 is invoked whenever the SLM Attachment accesses or changes an SLM 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 SLM project and SLM project definition. 12 Server and REXX customization

13 This is intended for the case where a custom-developed SLM translator and SLM exit uses environment variables that are set outside of SLM. As long as values of the environment variables are not dependent on the SLM project definition, Micro Focus recommends using the general exit TAUTOXAI instead of its SLM exit. Exit TAUSXP3: Determine relevant SLM project definitions The SLM application displays SLM project definitions in the second level of its tree structure. You can further define an SLM project using the Retrieve option. Use this exit to determine the relevant SLM 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 TAUSXP3 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. ustomizing the generation of SLM architecture members The SLM model contains an action that generates all necessary architecture members belonging to an SLM member. Before using this action, you should customize it, as required. The included generation example uses the following components: REXX /skeletons TAUSAR TAUSOM TAUSLNK TAUSHLL TAUSPKG TAUSPLN TAUSBND Generating SLM architecture definitions corresponding to an SLM source Adjustments are necessary during variable initialization (type names, language, and member) in the upper part of the procedure. Skeleton for generating SLM architecture definitions Adjustments to the layouts for generating Archdefs are necessary Skeleton for generating SLM architecture definitions Adjustments to the layouts for generating Link Archdefs are necessary Skeleton for generating SLM architecture definitions Adjustments to the layouts for generating HLL Archdefs are necessary Skeleton for generating SLM architecture definitions Adjustments for generating bind package REXX are necessary Skeleton for generating SLM architecture definitions Adjustments for generating bind plan REXX are necessary SLM REXX sample for DB2 relevant languages: Execute Bind Plan or Bind Package (Access is throughthe BindPackage / BindPk, process (compare Skeletons TAUSPKG, TAUSPLN)). Server and REXX customization 13

14 REXX /skeletons Adaptation to the existing promote structure is necessary. Adjustment of the skeleton support for creating new members The SLM model contains an action that you can use to create a new SLM member. A skeleton can be retrieved depending on the SLM 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. The included example uses the following components: REXX /skeletons TAUSXIN TAUSSA TAUSSAH TAUSSAP TAUSSAA Insert exit Depending on the parameter passed as SLM language, a skeleton is assigned Skeleton for a new OBOL member Skeleton for a new HLL Archdef member Skeleton for a new PLI member Skeleton for a new ASSEMBLER member Integrating build notify exit TAUSXBD If the SLM Attachment should insert the generated output members directly in the current Eclipse table after a successful SLM build, the build notify exit of the SLM language definition must be active and the procedure TAUSXBD must be submitted as an exit. If this exit has already been used, call the procedure TAUSXBD as a sub-routine in the already defined exit procedure. The definition of a build exit occurs in the project definition using the macro FLMNTRL: FLMNTRL AT=SLM.AOUNT.FILE, VERS=SLM.VERSION.FILE, BLDNTF=SELET, BLDNTFM=ISPLNK, BLDNTFOP='NEST MD(TAUSXBD,', MAXVIO=999999, VIOUNIT=VIO Support for error feedback during SLM build for OBOL The SLM Attachment supports error feedback for OBOL programs in connection with an SLM build. Use the compiler option ADATA together with the OBOL exit TAURTOX, and allocate the error feedback file as a member of a PDS file in a build translator. Use the REXX procedure TAUSPLA 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 ALLNAM='XMLDAT', FUNTN=BUILD, ALLMETH=ISPLNK, OMPILE=SELET, VERSION=1.0, GOODR=0, 14 Server and REXX customization

15 PDSDATA=Y, PORDER=1, OPTIONS='MD(TAUSPLA FLMMBR)NEST' FLMTRNSL ALLNAM='ENTERPRISE OBOL OMPILER', FUNTN=BUILD, OMPILE=IGYRTL, DSNAME=IGY410.SIGYOMP, VERSION=3.3.1, GOODR=4, PORDER=1, OPTIONS='FLAG(I,I),ADATA,LIB,LIST,TEST(NOHOOK,SEPARATE), EXIT(ADEXIT(''/N 100 /W 50'',TAURTOX))' * (* SYSADATA *) FLMALLO IOTYPE=W,REFM=VB,LREL=1020,RENUM=500000, DDNAME=SYSADATA Support for error feedback during SLM build for PLI The SLM Attachment supports error feedback for PLI programs in connection with the SLM 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 TAUSPLA for this translator. *********************************************************************** * BUILD TRANSLATOR * * (REXX-PROEDURE ALL TO ALLOATE XML FILE) * *********************************************************************** * FLMTRNSL ALLNAM='XMLDAT', FUNTN=BUILD, ALLMETH=ISPLNK, OMPILE=SELET, VERSION=1.0, GOODR=0, PDSDATA=Y, PORDER=1, OPTIONS='MD(TAUSPLA FLMMBR)NEST' FLMTRNSL ALLNAM='ENTERPRISE PL/I OMPILER', FUNTN=BUILD, OMPILE=IBMZPLI, DSNAME=IEL370.SIBMZMP, VERSION=3.3.0, GOODR=4, PORDER=1, OPTIONS=(MARO,OBJET,SOURE,XREF,XINFO(XML)) Support for error feedback during SLM build for Assembler The tool attachment supports error feedback for Assembler programs in connection with the SLM 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 TAUSPLA 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 ALLNAM='XMLDAT', FUNTN=BUILD, ALLMETH=ISPLNK, OMPILE=SELET, Server and REXX customization 15

16 VERSION=1.0, GOODR=0, PDSDATA=Y, PORDER=1, OPTIONS='MD(TAUSPLA FLMMBR)NEST' FLMTRNSL ALLNAM='ENTERPRISE OBOL OMPILER', FUNTN=BUILD, OMPILE=IGYRTL, DSNAME=IGY410.SIGYOMP, VERSION=3.3.1, GOODR=4, PORDER=1, OPTIONS='XREF(SHORT),LINEOUNT(75),OBJET,RENT,ADATA,EXI T(ADEXIT(TAURTOAX(''/N 100 /W 25'')))' * (* SYSADATA *) FLMALLO IOTYPE=W,REFM=VB,LREL=1020,RENUM=500000, DDNAME=SYSADATA Exit TAUSXBI: Determination of build information The exit TAUSXBI determines build information from SLM which is needed for remote syntax check. The shipped exit TAUSXBI uses the SLM build info command to determine this information. The result of the SLM 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, possibly less expensive, way. Exit TAUSXSL: Determination of the SYSLIB concatenation The exit TAUSXSL determines the SYSLIB concatenation from SLM. The shipped exit TAUSXSL determines the SYSLIB concatenation by a call to the exit TAUSXBI. The exit should be adapted if there is another, possibly less expensive way, at the customer site to determine the SYSLIB concatenation. 16 Server and REXX customization

17 ustomizing the SLM model If you do customize the SLM model, save the model member beforehand. Action enabled conditions Depending on the SLM project definitions, it makes sense to add some action-enabled conditions to the SLM model. Micro Focus recommends that you adapt the following action-enabled conditions (Element Type: ELEEditable), as required. (The given values PROD and SOURE below are sample values and have to be replaced by the values defined in the SLM project definition.) Relationship ondition(s) ATompareNext ATDeleteMember ATRemoteSyntaxheck ATGetVersionList ATRetrieveVersion ATArchgen The action should not be executable on the last group, for example: ondition: PROPGroup Equals not PROD The action should not be executable on productive members, for example: ondition: PROPGroup Equals not PROD The action should only be executable on program code, for example: ondition: PROPType Equals SOURE The action should only be executable on versioned members, for example: ondition: PROPGroup Equals PROD The action should only be executable on versioned members, for example: ondition: PROPGroup Equals PROD The action should only be executable on program code, for example: ondition: PROPType Equals SOURE ustomizing the SLM model 17

18 18 ustomizing the SLM model