SCLM Education Manual

SCLM EDUCATION

Northern Trust Chicago, IL

SCLMBNK, SCLMFIN, SCLMHRM, SCLMTEC, and SCLMTFS Applications

October 27, 2004

Rene Ford IBM Global Services

Modified by Karen Leisten Northern Trust

(c) Copyright IBM Global Services 1997, 2003. All rights reserved.

Permission to use, copy, modify, and/or distribute this documentation for any purpose without express written consent of the IBM Global Services Software Configuration Management Services support team is expressly

prohibited.

SCLM Education for Northern Trust Applications – October 27, 2004

2

Table of Contents SUMMARY OF CHANGES.......................................................................................................... 5 INTRODUCTION........................................................................................................................... 6 Part 1. SCLM OVERVIEW........................................................................................................ 8 Topic 1. SCLM - What It Means ................................................................................................... 9

SC: Software Configuration................................................................................................ 9 LM: Library Manager......................................................................................................... 9 SCLM Puts the Two Together ............................................................................................. 9

Topic 2. SCLM - What Is It? ....................................................................................................... 10 SCLM Terminology................................................................................................................. 10 Software Configuration........................................................................................................... 11

Architecture Definitions.................................................................................................... 11 Library Manager..................................................................................................................... 11

Project Definition.............................................................................................................. 11 Language Definitions........................................................................................................ 11

Part 2. SCLM Customization for SCLMBNK, SCLMFIN, SCLMHRM, SCLMTEC, and SCLMTFS Applications ............................................................................................................. 12 Topic 3. SCLM Library Structure ................................................................................................ 13

Project Definitions .................................................................................................................. 13 Project Hierarchy ................................................................................................................... 13 SCLM Alternates..................................................................................................................... 15 SCLM Groups ......................................................................................................................... 16 Authorization Codes ............................................................................................................... 16 SCLM Types ............................................................................................................................ 17 Versioning ............................................................................................................................... 18 Language Definitions.............................................................................................................. 19

Topic 4. SCLM Processes............................................................................................................ 20 SCLM Main Menu................................................................................................................... 20 SCLM Edit............................................................................................................................... 21 SCLM Edit with SCLMINFO .................................................................................................. 22 SPROF Command................................................................................................................... 23 EDIT/COMPARE Tool............................................................................................................ 24

Adding/Updating a Member in SCLM ......................................................................................... 25 Steps to Add a New Member in SCLM.................................................................................... 26 Steps to Edit an Existing Member in SCLM............................................................................ 26 SCLM Member Edit ................................................................................................................ 27 SCLM ARCHDEF Edit ........................................................................................................... 28 Steps to Add a New LECDEF Member in SCLM.................................................................... 28 Steps to Add a New ARCHDEF Member in SCLM................................................................. 29

SCLM Build.................................................................................................................................. 32 BLDLIST ................................................................................................................................. 35 BLDREPT ............................................................................................................................... 36

SCLM Promote – Conditional Mode............................................................................................ 37 Promote User Exits ................................................................................................................. 41

SCLM Package Processing ........................................................................................................... 42


3

SCLM Package Naming Conventions..................................................................................... 42 Steps to Create a New Package .............................................................................................. 43 Steps to Edit an Existing Package in SCLM ........................................................................... 43

Creating Delete Packages.............................................................................................................. 45 Steps to Create a New Delete Package................................................................................... 45 Steps to Edit an Existing Delete Package in SCLM................................................................ 45 Package Build Process ........................................................................................................... 48 Package Promote Approval Process....................................................................................... 49 Package Promote Process ...................................................................................................... 52 Steps to Edit an Existing Member in a Promoted Package .................................................... 55

Topic 5. Architecture Definitions ................................................................................................ 57 What Archdefs Do ................................................................................................................... 57 Four Kinds of Archdefs........................................................................................................... 57

HL - High Level ................................................................................................................ 57 LEC - Link Edit Control.................................................................................................... 57 CC - Compilation Control ................................................................................................ 57 Generic.............................................................................................................................. 57

How Archdefs Work.. an Example .......................................................................................... 58 Understanding Archdef Language.......................................................................................... 59 Rules for Coding Archdefs ...................................................................................................... 59 Some Archdef Keywords ......................................................................................................... 60 Archdefs for Northern Trust ................................................................................................... 62 SCLM Sample Archdefs Table ................................................................................................ 63

SCLM ARCHDEFS – Samples According to New Endevor Types............................................ 66 ASMB ...................................................................................................................................... 66 CO3B....................................................................................................................................... 67 CO3B2..................................................................................................................................... 67 CO3BI ..................................................................................................................................... 68 CO3BM ................................................................................................................................... 69 CO3X....................................................................................................................................... 69 CO3X2..................................................................................................................................... 70 BMS......................................................................................................................................... 71 MLOD ..................................................................................................................................... 71 EZTB ....................................................................................................................................... 72 PL1B ....................................................................................................................................... 72 CO3U2#06 .............................................................................................................................. 73 CCDEF Example for CO3B.................................................................................................... 76 CCDEF Example for CO3B2.................................................................................................. 77 CCDEF Example for PL1B..................................................................................................... 78 CCDEF Example for PL1B2................................................................................................... 79 Example for SOURCE2 Program ........................................................................................... 80

Topic 6. SCLM and DB2 ............................................................................................................. 81 What SCLM Types Are Used for DB2?................................................................................... 81 DB2 Types – Examples by Type.............................................................................................. 82 CO3B2..................................................................................................................................... 82


4

PL1B2 ..................................................................................................................................... 83 EZTB2 ..................................................................................................................................... 83 Steps to Create a New DB2 Program ..................................................................................... 84 Steps to Edit an Existing DB2 Member................................................................................... 87

Topic 7. SCLM Utilities .............................................................................................................. 90 SCLM Utilities Menu .............................................................................................................. 90 Library Utility (SCLM option 3.1) .......................................................................................... 91 Migration Utility (SCLM option 3.3) ...................................................................................... 93 Database Utility (SCLM option 3.4)....................................................................................... 94 Audit and Version Utility (SCLM option 3.8) ......................................................................... 97 Delete Group Utility (SCLM option 3.9) .............................................................................. 100

Topic 8. SCLM Customized Tools for Northern Trust.............................................................. 102 SCLM Productivity Tools (SCLM option 3.T) ...................................................................... 102 Copybook Search Utility (SCLM option 3.T.1)..................................................................... 103 Subroutine Search Utility (SCLM option 3.T.2) ................................................................... 104 Breeze Approval Functions (SCLM option 3.B) ................................................................... 105

Approver Maintenance (SCLM option 3.B.1) ................................................................. 106 Approver Group Maintenance (SCLM option 3.B.2)...................................................... 107 Approver Group Approver Maintenance (SCLM option 3.B.3)...................................... 108 Inventory Junction Record Maintenance (SCLM option 3.B.4)...................................... 109 Inventory Watch Record Maintenance (SCLM option 3.B.5) ......................................... 110 Package Report (SCLM option 3.B.6) ............................................................................ 111 Cross Reference Report (SCLM option 3.B.7)................................................................ 112 Package Status (SCLM option 3.B.8).............................................................................. 113 Package Approval (SCLM option 3.B.9) ........................................................................ 114 Package Voting Utility (SCLM option 3.B.10) ............................................................... 115

Topic 9. Viewing and Voting on Packages Using the Breeze Web Interface............................ 116 Breeze Main Panel ................................................................................................................ 117 Selecting a Package for Viewing or Voting .......................................................................... 118

Filtering Packages from the List..................................................................................... 119 Voting on a Package ............................................................................................................. 119

How Voting Results in Approved or Vetoed Status......................................................... 121 Viewing Package Information......................................................................................... 123 Summary ......................................................................................................................... 123 Contents .......................................................................................................................... 125 Log .................................................................................................................................. 126 Collisions ........................................................................................................................ 127 Ballot Box........................................................................................................................ 128 Notes ............................................................................................................................... 129


5

SUMMARY OF CHANGES

October 6, 2004:

• Updated SCLM Source to Language Mapping Chart with correct LECDEF samples

• Added SCLM Type to Language Mapping Chart

• Updated DELETPKG section with better details

October 27, 2004:

• Under SPROF Command – changed Change code description to optional.


6

INTRODUCTION This education package is intended as a high-level introduction to SCLM. For further details about SCLM, refer to the following documents:

SCLM Resources

� ISPF SCLM Project Manager’s and Developer’s Guide z/OS V1R2.0 (SC34-4817-01) – This is a step-by-step guide for the SCLM Users and Administrators to reference while setting up projdefs and langdefs. It provides detailed information concerning all SCLM functions and architecture definitions. This manual can be found at:

http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/books/ispzsc10/contents

� SCLM ISPF Reference z/OS V1R2.0 (SC34-4818-01) – This reference invokes SCLM services through APIs and detailed information on SCLM macros, parsers, translators, and SCLM variables. It is intended for the SCLM Administrator. This manual can be found at:

http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/ISPZSR10/CCONTENTS

� ISPF Messages and Codes z/OS V1R2.0 (SC34-4815-01) – This reference lists all SCLM error messages (FLM*). It is intended for SCLM Users and Administrators. This manual can be found at:

http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/ISPZMC10/CCONTENTS

Breeze Resources

� Breeze for SCLM Functional Overview z/OS (SC31-8818-01) – Step by step guide to completing the installation. Intended audience is system Administrators who are familiar with installing products under z/OS or OS/390.

� Breeze for SCLM Planning and Administration Guide z/OS (SC31-8817-02) – Step by step guide to completing the installation. Intended audience is system Administrators who are familiar with installing products under z/OS or OS/390.

� Breeze for SCLM User’s Guide z/OS (SC31-8820-02) – Guide to promoting packages, and using the Web interface to view packages, and approve or veto package promotion. Intended audience is Developers, Approvers, and general Users. See the following web page:

http://www.software.ibm.com/ad/sclmsuite/breeze/library/

� Breeze for SCLM Installation Guide z/OS (SC31-8819-02) – Step by step guide to completing the installation. Intended audience is system Administrators who are familiar with installing products under z/OS or OS/390. Select Installation Guide from the following web page:

http://www.software.ibm.com/ad/sclmsuite/breeze/library/


7

Other Resources

� Visit the ISPF/SCLM homepage for more information about SCLM at: http://www.software.ibm.com/ad/ispf.

� Standard IBM Service is available for issues concerning the SCLM product through

1-800-IBM-SERV. � Visit the SCLM forums and news discussion groups for more information about SCLM at:

http://www.software.ibm.com/ad/sclmsuite/support. The forums are reviewed by the SCLM Developers. You can ask questions and get answers through:

- SCLM e-Group Discussion

- IBM SCLM newsgroups


8

Part 1. SCLM OVERVIEW


9

Topic 1. SCLM - What It Means

SC: Software Configuration

How the pieces of an application fit together

LM: Library Manager

Keeps track of and controls your members

SCLM Puts the Two Together

For detailed information refer to publication ISPF Software Configuration and Library Manager (SCLM) Developer's Guide.


10

Topic 2. SCLM - What Is It? SCLM Terminology Project Organized collection of PDS datasets

representing an application

Project Definition A load module that defines a library structure Resides in project.PROJDEFS.LOAD(project)

Hierarchy The arrangement of groups which defines the promotion paths

Layer/Level One horizontal tier of the hierarchy

Group Collection of libraries associated by their location in the hierarchy

Type A specific type of data under SCLM control

Member Individual part of an SCLM library

Language Definition Defines the translators (compilers, linkage editors, etc.) applied to a member during BUILD and PROMOTE

Architecture Definition Specify to SCLM how library parts are related and how they should be built and promoted

Build Apply the translators defined in the language definition to generate outputs

Promote Move a member to the next higher level in the hierarchy

SCLM Library A PDS that contains members of a single type. Collections of these libraries are called Groups. One library for each group and type. Library name: project.GROUP.TYPE Example: SCLMBNK.PRD.SOURCE


11

Software Configuration

� Find the proper source objects

�� Apply the proper language translators

�� Generate the proper output objects

Architecture Definitions

� Identify the source objects

� Identify the output objects

Library Manager

� Store the source and output objects

� Associate languages with members

Project Definition

� Identify the groups and types used in a project

� Identify control information

� Identify language definitions

Language Definitions

� Identify what actions to take

� Identify inputs and outputs

� Identify parser to use


12

Part 2. SCLM Customization for SCLMBNK, SCLMFIN, SCLMHRM,

SCLMTEC, and SCLMTFS Applications


13

Topic 3. SCLM Library Structure Project Definitions � SCLMBNK, SCLMFIN, SCLMHRM, SCLMTEC, SCLMTFS

� In: PROJECT.PROJDEFS.LOAD

� Required on SCLM Main Menu

� High Level Qualifier for PDS under SCLM

Project Hierarchy

Note: BACKUP group is not available to programmers. BACKUP group is for SCLM Administrator use only.

SCLMTFS Package,and Pkgdebug

PRD FIRECALL

FREEZE

HOLDCHOLDA HOLDB

P

P PP

P

P

PREP

P, D

BACKUP

P

PRD FIRECALL

PP

SCLMTFS Firecall,and Firebug BACKUP

P

SCLMTFS, andDebug Alternate

FREEZE

HOLDCHOLDA HOLDB

DEVB

P, D

DEVA

P, D

P, D P, DP, D

P

DEVC

P, D

PREP

P, D

PRD FIRECALL

PP

BACKUP

P


14

PRD FIRECALL

PP

Firecall Alternate,and Firebug

SCLMBNK, SCLMFIN,SCLMHRM, SCLMTEC,and Debug Alternate

FREEZE

HOLDA

P

P

PRD FIRECALL

PP

Package Alternate,and Pkgdebug

PREP

P, D

BACKUP

P

BACKUP

P

PRD

FREEZE

HOLDA

DEVA

P, D

P, D

P

P

FIRECALL

P

PREP

P, D

BACKUP

P


15

SCLM Alternates

SCLM alternate project definitions allow the SCLM main project to be redefined so that only specific groups will be included in the alternate project. With the implementation of SCLM at Northern Trust several alternate projects were defined for each SCLM main project. To make the process of selecting an alternate easier for the users, switches have been added to the bottom of the SCLM main menu.

Debug – The Debug alternate allows the user to set the compile options in the DEV groups so that Xpediter will be used during the compile process. Leave the Xpediter switch set to ‘Y’.

Package – The Package alternate allows the HOLD SCLM groups to become the lowest groups within the hierarchy. This will enable the user to create/build packages in the HOLD groups. Set the package switch to ‘Y’.

Pkgdebug – The Pkgdebug alternate is used to promote packages from the HOLD group to the FREEZE group using the Xpediter compile process. In order to invoke the build process during the promote to Freeze the package member name must have a ‘2’ in the 4th position. Set the package and Xpediter switch to ‘Y’.

Firecall – The Firecall alternate allows the user to include only the PROD and FIRECALL groups within the hierarchy. This will remove the requirement for the users to provide authorization codes in the DEV and HOLD groups. Set the Firecall switch to ‘Y’.

Firebug – The Firebug alternate will allow the user to use the firecall alternate with the Xpediter compile process. Set the Xpediter and firecall switch to ‘Y’.


16

SCLM Groups

GROUP NAME DESCRIPTION PRD PRODUCTION BACKUP BACKUP FREEZE USER ACCEPTANCE TESTING PREP STAGING FOR FREEZE HOLDA HOLD A HOLDB HOLD B HOLDC HOLD C DEVA DEVELOPMENT A DEVB DEVELOPMENT B DEVC DEVELOPMENT C FIRECALL FIRECALL PRODUCTION

Authorization Codes SCLM uses authorization codes to control promotion of members in the project hierarchy. Each group has at least one authorization code. In order to promote from one group to the next higher group, each must have one common authorization code. Groups at the same level (for example, DEVA and DEVB groups) with the same authorization code will lock members from each other. If you want to edit a member already in one of the other DEV groups you will need to use a “D” authorization code.


17

SCLM Types

TYPE VERSIONED LANGUAGE ARCHDEF YES ARCHDEF BACKUP YES N/A BIND YES BIND BMSLIB NO N/A CBKLIB YES CO3B, PL1B CCDEF YES ARCHDEF CPTLIB YES TEXT DBRMLIB NO N/A DB2OUT NO N/A DELETPKG NO ARCHDEF EGLLIB YES TEXT FEXLIB YES TEXT FMALIB YES TEXT FQLLIB YES TEXT LECDEF YES ARCHDEF LECDEFA YES ARCHDEF LECDEFC YES ARCHDEF LECDEFI YES ARCHDEF LECDEFO YES ARCHDEF LECDEFR YES ARCHDEF LECDEFSP YES N/A LOAD NO N/A LOADA NO N/A LOADC NO N/A LOADI NO N/A LOADO NO N/A LOADR NO N/A LOADSP NO N/A MACLIB YES TEXT OBJ NO N/A OBJ2 NO N/A PACKAGE YES ARCHDEF SOURCE YES CO3B, ASMB, ASMC, BMS, CO3B2, CO3B2R,

CO3B2RT, CO3C, CO3C2, EZTB, EZTB2, PL1B, PL1B2 SOURCE2 YES See Administrator.

Note: Not all Types are in all projects.


18

Versioning SCLM saves 20 versions in DEVA, DEVB, DEVC, HOLDA, HOLDB, HOLDC, FREEZE, FIRECALL, and PRD groups for each of the following types in SCLM:

TYPE Description ARCHDEF Architecture Definition BIND Bind Control Member CBKLIB Cobol Copybooks CCDEF Compile Definitions CPTLIB CULPRIT DELETPKG Package for Deleting Members EGLLIB EAGL88 FEXLIB Focus Execs FMALIB Focus Master FQLLIB Focus SQL LECDEF Link Edit Definitions for LOAD LECDEFA Link Edit Definitions for LAODA LECDEFC Link Edit Definitions for LOADC LECDEFI Link Edit Definitions for LOADI LECDEFO Link Edit Definitions for LOADO LECDEFR Link Edit Definitions for LOADR LECDEFSP Link Edit Definitions for LOADSP MACLIB Macro PACKAGE SCLM Promote Package SOURCE Program Source Code SOURCE2 Extra Cobol Source Code

Note: Versions are only maintained at the level of all non-PRD groups, until

a promotion. Then they are deleted. PRD versions are maintained at all times.


19

Language Definitions LANGUAGE DESCRIPTION PROJECT

ARCHDEF ARCHITECTURE DEFINITION BNK, FIN, HRM, TEC, TFS ASMB ASSEMBLER BATCH BNK, FIN, HRM, TEC, TFS ASMC ASSEMBLER CICS BNK, FIN, HRM, TEC, TFS BIND DB2 BIND FOR BUILD BNK, TFS BMS CICS MAPS FIN, TEC, TFS CO3B LE COBOL BATCH FIN, HRM, TEC, TFS CO3B2 LE COBOL BATCH DB2 TEC, TFS CO3B2R LE COBOL BATCH DB2 WITH SMART

RESTART TEC, TFS

CO3B2RT LE COBOL BATCH DB2 WITH SMART RESTART WITH TSO ATTACHMENT

TEC, TFS

CO3C LE COBOL CICS BNK, FIN, HRM, TEC, TFS CO3C2 LE COBOL CICS DB2 TEC, TFS DB2OUT DB2 BIND FOR PROMOTE BNK, TEC, TFS EZTB EZTRIEVE BATCH BNK, FIN, TEC, TFS EZTB2 EZTRIEVE BATCH DB2 BNK, TEC, TFS LECMN LINKAGE EDITOR FOR LE BNK, FIN, HRM, TEC, TFS LECMNRNT LINKAGE EDITOR FOR LE RENT BNK, TEC, TFS LEEZT LINKAGE EDITOR FOR EZTRIEVE BNK, TEC, TFS LELET LINKAGE EDITOR FOR LE LET BNK, TEC, TFS PL1B PL1 BATCH BNK, FIN, HRM, TEC, TFS PL1B2 PL1 BATCH DB2 BNK, FIN, TEC, TFS LOD LOAD FIN, TEC, TFS TEXT TEXT LANGUAGE BNK, FIN, HRM, TEC, TFS


20

Topic 4. SCLM Processes

SCLM Main Menu

SCLM Main Menu can be accessed using option 10 from the ISPF Main menu. The group specified here determines which leg of the hierarchy is used for Edit, Build, and Promote. For SCLMTFS use DEVA, DEVB, and DEVC. For all other projects use DEVA. Set Xpediter switch to ‘Y’ (yes) if the Xpediter version of the compiler should be used. Set Package switch to ‘Y’ (yes) to create a package or promote to the Freeze or Production groups. Set Firecall Switch to ‘Y’ (yes) if editing in group Firecall or promoting from group Firecall. A combination of switches can be set to utilize multiple functions. For example to use Xpediter and Package processing set both switches to ‘Y’, to use both Firecall and Xpediter set both switches to ‘Y’.

Menu Utilities Help ----------------------------------------------------------------------- SCLM Main Menu Option ===> Enter one of the following options: 1 View ISPF View or Browse data 2 Edit Create or change source data in SCLM databases 3 Utilities Perform SCLM database utility/reporting functions 4 Build Construct SCLM-controlled components 5 Promote Move components into SCLM hierarchy 6 Command Enter TSO or SCLM commands 7 Sample Create or delete sample SCLM project X Exit Terminate SCLM SCLM Project Control Information: Project . . . . SCLMBNK (Project high-level qualifier) Alternate . . . (Project definition: defaults to project) Group . . . . . DEVA (Defaults to TSO prefix) Xpediter => Y (Y/N) Package => N (Y/N) Firecall => N (Y/N)


21

SCLM Edit

� Always use SCLM Edit instead of ISPF Edit.

� Always use SCLMINFO edit macro.

� Draw Down – copies member from higher group to the edit group.

� Parse – gathers statistics and dependencies.

� Save – updates SCLM accounting data.

� The Authorization code will be hard coded on the screen.

SCLM controlled members cannot be edited under ISPF. If SCLM members are copied using ISPF 3.3 Copy, then the SCLM Setting option on the COPY Panel must have Option 2, (Non-SCLM), selected, or the member will still not be eligible for edit, even under a user’s private dataset.

Menu RefList RefMode SCLM Utilities Workstation Help ---------------------------------------------------------------------------- SCLM Edit - Entry Panel Command ===> SCLM Library: Project . . :SCLMBNK Group . . . :DEVA . . . HOLDA . . . FREEZE . . . PRD Type . . . .SOURCE Member. . . .IBM01 (Blank or pattern for member selection list) Initial Macro . . SCLMINFO Profile Name . . . (If blank, defaults to data set type) Options /Confirm/Cancel/Move/Replace Mixed Mode Edit on Workstation Preserve VB record length Change code . . . . . .12345 Authorization code . .P (If blank, the default auth code is used) Parser Volume . . . . . (If blank, the default volume is used)


22

SCLM Edit with SCLMINFO

SCLMINFO provides helpful info about the member:

� Who last edited the member.

� When the member was last edited.

� Where else in the hierarchy the member exists.

� Sends TSO message to others that are also working with member.

� Detects potential predecessor verification errors with members in higher groups.

� Lists any previous change codes related to this member.

� Where related copybooks are being changed (activated by typing SCLMINFO COPY on the command line inside the edit session).

File Edit Confirm Menu Build SCLM Utilities Test Help ------------------------------------------------------------------------------- EDIT SCLMBNK.DEVA.SOURCE(IBM01) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR

�****** ***************************** Top of Data ****************************** =NOTE= IBM01 WAS LAST MODIFIED ON 01/08/29 AT 18:40:00 BY RF30 ==MSG> =NOTE= CHANGE CODES: 123456 ON 01/08/29 AT 18:40:00 ==MSG> ==MSG> IBM01 ALSO FOUND IN GROUPS: ==MSG> ==MSG> GROUP MODIFIED BY ON DATE AT TIME =NOTE= HOLDA RF30 01/08/29 18:40:00 ==MSG> ==MSG> -CAUTION- Profile changed to CAPS ON (from CAPS OFF) because the ==MSG> data does not contain any lower case characters. ==MSG> -CAUTION- Data contains invalid (non-display) characters. Use command ==MSG> ===> FIND P'.' to position cursor to these ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 IDENTIFICATION DIVISION. 000002 PROGRAM-ID. TEST1. 000003 *


23

SPROF Command

� The SPROF (SCLM Profile) command allows users to update the language or change code of a member.

� Type SPROF on the command line inside the edit session to access.

� To see a list of valid languages for the project, leave it blank and press Enter. Then select the desired language from the displayed list.

� Change code is optional.

Menu SCLM Utilities Help ------------------------------------------------------------------- SCLM Edit Profile Command ===> SCLM Library: SCLMBNK.DEVA.SOURCE Member: IBM01 Press the Enter key with the language field blank to view a list of valid languages or enter the desired values and press Enter. Enter the Cancel command to exit with no change. Language . . . . CO3B Change code . . 12345 (Use "=" to retrieve last entry)


24

EDIT/COMPARE Tool Use the EDIT/COMPARE function to compare 2 members in the SCLM hierarchy, highlight the differences in one member, and retrofit any changes or fix work as needed.

To use the tool:

1. Edit the member under SCLM (through option 3.1).

2. Type HILITE ON RESET on the command line, press Enter. This highlights the member in different colors according to the syntax of its language. This command is only needed if HILITE is off.

3. Enter a valid COMPARE command on the command line:

Type COMPARE to set options for the COMPARE command.

Type COMPARE NEXT to compare this member to one with the same name in a higher group in the hierarchy.

Type COMPARE ‘pdsname’ to compare against a member that exists in another PDS. Replace pdsname with the actual dataset name. This can also be an SCLM dataset from a separate leg of the hierarchy.

Type COMPARE ‘pdsname’ X to show only lines that are different between the 2 members.

4. EDIT/COMPARE will color all lines in white that exist in the member specified in step 3, but do not exist in the member being edited. These lines can be merged into the member being edited with the MD (Make Data) line command. Just type MD next to lines you want. Use MDD to block several lines to merge. Use MD9999 on the first line to merge all lines in the member.

All lines colored in blue represent lines in the member being edited that do not exist in the member specified in step 3.

5. Type L SPECIAL NEXT to locate the next line for merge consideration.

6. Type L LABEL to locate the next line in blue not found in the member specified in step 3.


25

Adding/Updating a Member in SCLM

Always use SCLMINFO edit macro.

Menu RefList RefMode SCLM Utilities Workstation Help ----------------------------------------------------------------------------- SCLM Edit - Entry Panel Command ===> SCLM Library: Project . . :SCLMBNK Group . . . :DEVA . . . HOLDA . . . FREEZE . . . PRD Type . . . .SOURCE Member. . . .IBM01 (Blank or pattern for member selection list) Initial Macro . . SCLMINFO Profile Name . . . (If blank, defaults to data set type) Options / Confirm Cancel/Move/Replace Mixed Mode Edit on Workstation Preserve vB record length Change code . . . . . . 123456 Authorization code . . P (If blank, the default auth code is used) Parser Volume . . . . . (If blank, the default volume is used)


26

Steps to Add a New Member in SCLM

1. Select Option 2 from the SCLM main menu for the SCLM Edit panel.

2. Specify Type (example: SOURCE) and Member (IBM01) being added.

3. Press Enter on the SCLM Edit panel.

4. Copy or enter the new member (IBM01) code.

5. Press End to return to the SCLM Language Selection panel.

6. Do one of the following:

a) Enter a Language (example: CO3B) on the SCLM Edit Profile panel and press Enter.

b) Leave the Language field ‘blank’ and press Enter.

� A selection panel will appear.

� Select a language and press Enter.

Steps to Edit an Existing Member in SCLM 1. Select Option 2 from the SCLM main menu for the SCLM Edit panel.

2. Specify a Type. Press Enter. A list of members will appear.

3. Select the member you would like to edit.

4. Press Enter for the Edit session.

5. Make changes to save the member to the lowest level of the hierarchy.

6. If Language definition needs to be changed enter ‘SPROF’ on the command line. A change panel will appear.

Note: Only SOURCE types require their own Archdefs/Lecdefs. All other types

will not need Archdefs/Lecdefs specifically for them. To promote these members, include them in a package. (See Steps to Create a New Package.) CBKLIB members are referenced through SOURCE types and are automatically built and promoted with the SOURCE member’s ARCHDEF.


27

SCLM Member Edit Do an ISPF edit copy. Results of ISPF copy: Assign the SCLM Language to the source member.

EDIT SCLMBNK.DEVA.SOURCE(IBM01) - 01.00 Member IBM00 copied Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 IDENTIFICATION DIVISION. 000002 PROGRAM-ID. IBM00. 000003 AUTHOR. 000004 R FORD. 000005 INSTALLATION. 000006 000007 DATE-WRITTEN. 000008 SEPTEMBER 1979. 000009 DATE-COMPILED

File Edit Edit_Settings Menu Build SCLM Utilities Test Help ------------------------------------------------------------------------------- EDIT SCLMBNK.DEVA.SOURCE(IBM01) - 01.00 Columns 00001 00072 Command ===> COPY Scroll ===> CSR ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. '''''' '''''' '''''' ''''''

SCLM Edit Profile Command ===> SCLM Library: SCLMBNK.DEVA.SOURCE Member: IBM01 Press the Enter key with the language field blank to view a list of valid languages or enter the desired values and press Enter. Enter the Cancel command to exit with no change. Language . . . . CO3B Change code . . 123456 (Use "=" to retrieve last entry)


28

SCLM ARCHDEF Edit

� SCLM LECDEFs/ARCHDEFs

- Define how to process members or groups of members.

- Specify options for components of SCLM processes.

- Determine how members are tracked.

- Describe the application system's internal structure.

- Specify inputs and outputs for each translator. � SCLM LECDEFs and ARCHDEFs are required for every compiled

member in SCLM. Steps to Add a New LECDEF Member in SCLM


2. Specify Type (example: LECDEF) and Member (IBM01) being added.


4. Copy or enter the new member code (IBM01).



a) Enter a Language (ARCHDEF) on the SCLM Edit Profile panel and press Enter.

b) Leave Language ‘blank’ and press Enter.


� Select ‘ARCHDEF’ as the language and press Enter.

Note: Some languages require more than one LECDEF member. See the SCLM Sample Archdefs Table to determine which LECDEF* types to use for new members. For example, an Endevor language CO3U2#06 requires new LECDEF members in the following types: LECDEF, LECDEFA, LECDEFC, LECDEFI, LECDEFO, LECDEFR, LECDEFSP.


29

Steps to Add a New ARCHDEF Member in SCLM


2. Specify Type (ARCHDEF) and Member (IBM01) being added.


4. Copy or enter the new member code (IBM01).



a) Enter a Language (ARCHDEF) on the SCLM Edit Profile panel and press Enter.

b) Leave Language ‘blank’ and press Enter.


� Select ‘ARCHDEF’ as the language and press Enter.

Note: If the compiler control parms need to be overridden use the SCLM CCDEF type. See the ARCHDEF samples by language section of this document to determine how to code the CCDEF and modify the LECDEF to provide for the compiler parm overrides.


30

Menu RefList RefMode SCLM Utilities Workstation Help ---------------------------------------------------------------------------- SCLM Edit - Entry Panel Command ===> SCLM Library: Project . . :SCLMBNK Group . . . :DEVA . . . HOLDA . . . FREEZE . . . PRD Type . . . .LECDEF Member. . . .IBM01 (Blank or pattern for member selection list) Initial Macro . . SCLMINFO Profile Name . . . (If blank, defaults to data set type) Options / Confirm Cancel/Move/Replace Mixed Mode Edit on Workstation Preserve VB record length Change code . . . . . . 123456 Authorization code . . P (If blank, the default auth code is used) Parser Volume . . . . . (If blank, the default volume is used)

EDIT SCLMBNK.DEVA.LECDEF(IBM01) - 01.00 Columns 00001 00072 Command ===> copy IBM00 Scroll ===> CSR ****** ***************************** Top of Data ****************************** ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. '''''' '''''' '''''' '''''' ''''''


31

Change the names in the archdef to your member.

Assign the SCLM Language of ‘ARCHDEF’ to the archdef member. After you create the lecdef for the source member, you can use the same steps above to create the archdef. After the lecdef and archdef are created you can build the archdef, which will compile and link the member in SCLM, so that the source member can be tested.

EDIT SCLMBNK.DEVA.LECDEF(IBM01) - 01.00 Member IBM00 copied Command ===> Scroll ===> CS ****** ***************************** Top of Data *************************** ==MSG> -CAUTION- Profile changed to NUMBER OFF (from NUMBER ON STD). ==MSG> Data does not have valid standard numbers. ==MSG> -CAUTION- Profile changed to CAPS OFF (from CAPS ON) because data ==MSG> contains lower case characters. ==MSG> -Warning- The UNDO command is not available until you change ==MSG> your edit profile using the command RECOVERY ON. 000001 * 000002 * Link Edit (LEC) LECDEF FOR IBM01 000003 * 000004 INCLD IBM01 SOURCE * Compile object 000005 LOAD IBM01 LOAD * Link Edit Load Module

SCLM Edit Profile Command ===> SCLM Library: SCLMBNK.DEVA.LECDEF Member: IBM01 Press the Enter key with the language field blank to view a list of valid languages or enter the desired values and press Enter. Enter the Cancel command to exit with no change. Language . . . . ARCHDEF Change code . . 123456 (Use "=" to retrieve last entry)


32

SCLM Build

BUILD is option 4 from the SCLM Main Menu. It can also be accessed with the SCLM menu item on the action bar. A valid Jobcard must be set up under the Jobcard menu item on the action bar. Set up the Jobcard in SCLM, using the Jobcard toolbar option at the top of the SCLM Build entry panel.

Menu SCLM Utilities Jobcard Workstation Build Help ---------------------------------------------------------------------------- SCLM Build - Entry Panel Command ===> Build input: Project . : SCLMBNK Group . . . DEVA Type . . . . ARCHDEF Enter "/" to select option Member . . IBM01 Error Listings only Workstation Build Mode . . 1 1. Conditional Scope . . . 2 1. Limited 2. Unconditional 2. Normal 3. Forced 3. Subunit 4. Report 4. Extended Output control: Ex Sub Process . . 1 1. Execute Messages . . 1 2 1. Terminal 2. Submit Report . . . 1 2 2. Printer Listings . . 3 2 3. Data set Printer . .* 4. None Volume . .


33

Build . . .

� From an ARCHDEF � Compiles, links, processes by language of member � Generates outputs and stores in SCLM � Can be done for one load module, several load modules, or an

entire application � Only builds what is impacted by change � Creates BUILD Report � Generates Build Map �� Must be successful before doing PROMOTE �� Check SDSF �� for job output correctness if process = 2

(or check your job spooler) Build Functions

1. Verification � Determines which members will be involved � Verifies that all accounting information is correct

2. Build Map generation - used for SCLM internal processing 3. Translator Calls - compilers, link editors, binds, etc. 4. Report generation

Build Scopes

1. Limited - process only components named in archdef 2. Normal - process named and all referenced components 3. Subunit - process ADA parts 4. Extended - process as Normal plus downward dependencies

Build Modes

1. Conditional - Stop if any unacceptable return codes 2. Unconditional - Continue processing despite translation errors 3. Forced - Force all components to be reprocessed 4. Report - Generate Build Report only, without performing the Build


34

Both Conditional and Unconditional modes will only select the parts that have changed to rebuild. If only a copybook changes and a Build is done with an archdef that points to 50 modules, then only those modules that reference the changed copybook will be selected for compiling and linking. Forced mode ignores any checking for changed parts. All referenced modules in the archdef are recompiled and re-linked. Report mode only produces a report of the outputs that Build would create under Conditional or Unconditional mode. This is a dry run tool. Build Outputs Three files are generated from the Build process:

� BLDMSGS

� BLDLIST

� BLDREPT

In spooled output, select the Build job with a ? to list it by files. Check the BLDMSGS, BLDLIST, and BLDREPT files for correctness. BLDMSGS The build messages list all of the translators and resulting return codes that the Build processed. Any compile or link errors are indicated by return codes here. Any SCLM accounting errors or verification problems are also listed here.

********************************* Top of Data ********************************** FLM42000 - BUILD PROCESSOR INITIATED - 02:04:34 ON 2002/12/31 FLM44500 - >> INVOKING BUILD TRANSLATOR(S) FOR TYPE: SOURCE MEMBER: IBM01 FLM06501 - TRANSLATOR RETURN CODE FROM ===> COBOL/MVS ===> 0 FLM06501 - TRANSLATOR RETURN CODE FROM ===> COMPILER LISTING ===> 0 FLM44500 - >> INVOKING BUILD TRANSLATOR(S) FOR TYPE: LECDEF MEMBER: IBM01 FLM06501 - TRANSLATOR RETURN CODE FROM ===> LINK EDIT ===> 0 FLM06501 - TRANSLATOR RETURN CODE FROM ===> LINKAGE LISTINGS ===> 0 FLM46000 - BUILD PROCESSOR COMPLETED - 02:04:50 ON 2002/12/31 ******************************** Bottom of Data ********************************


35

BLDLIST This report contains the listings from the compiles and links. Use this report to troubleshoot any errors. Specify Error Listings Only on the Build panel to suppress these listings.

PP 5648-A25 IBM COBOL for OS/390 & VM 2.1.1 Date 02/13/2001

Time 10:57:58

Invocation parameters:

XREF,LIB,APOST,NODYNAM,LIST,NONUMBER,NOSEQ PROCESS(CBL) statements:

CBL RENT,RES,NODYNAM,LIB

Options in effect:

NOADATA

ADV

NOANALYZE

APOST

NOAWO

BUFSIZE(4096)

NOCMPR2

NOCOMPILE(S)

NOCURRENCY

DATA(31)

NODATEPROC

NODBCS

NODECK

NODLL

NODUMP

NODYNAM

NOEXIT


36

BLDREPT The following report lists all outputs created or deleted by SCLM during the BUILD. Build Maps, which SCLM creates during BUILD to associate related members, are also created or deleted.

********************************* Top of Data ********************************** ******************************************************************************* ******************************************************************************* ** ** ** ** ** SOFTWARE CONFIGURATION AND LIBRARY MANAGER (SCLM) ** ** ** ** B U I L D R E P O R T ** ** ** ** 2002/12/31 02:04:34 ** ** ** ** PROJECT: SCLMTFS ** ** GROUP: DEVA ** ** TYPE: ARCHDEF ** ** MEMBER: IBM01 ** ** ALTERNATE: SCLMTFS ** ** SCOPE: NORMAL ** ** MODE: CONDITIONAL ** ** ** ** ** ******************************************************************************* ******************************************************************************* ******* B U I L D O U T P U T S G E N E R A T E D ******* Page 1 MEMBER TYPE VERSION KEYWORD ------ ---- ------- ------- IBM01 OBJ 2 OBJ IBM01 LOAD 2 LOAD ******* B U I L D M A P S G E N E R A T E D ******* Page 2 (REASON FOR REBUILD) MEMBER TYPE VERSION MEMBER TYPE ------ ---- ------- ------- ---- IBM01 ARCHDEF 3 IBM01 LECDEF IBM01 LECDEF 2 IBM01 SOURCE IBM01 SOURCE 2 IBM01 SOURCE ******* B U I L D O U T P U T S D E L E T E D ******* Page 3 MEMBER TYPE VERSION KEYWORD ------ ---- ------- ------- ******* NO MODULES DELETED ******* ******* B U I L D M A P S D E L E T E D ******* Page 4 (REASON FOR DELETE) MEMBER TYPE VERSION MEMBER TYPE ------ ---- ------- ------- ---- ***** NO BUILD MAPS DELETED ***** ******************************** Bottom of Data ********************************


37

SCLM Promote – Conditional Mode PROMOTE is Option 5 from the SCLM Main Menu. It can also be

accessed using the SCLM Library utility panel (SCLM option 3.1). The conditional promote will initiate the Breeze approval process for promotes to the FREEZE and PRD groups. The package switch on the SCLM main menu must be set to ‘Y’ and the type must be ‘PACKAGE’ to promote to the FREEZE and PRD groups. 1. Fill in the promote input fields (Type and Member) with names that are

applicable to your project. Project and From group fields will default to the project and group that was entered on the SCLM Main Menu panel.

2. Ensure that Process = 1 (Execute) to exectute SCLM promotes in the FOREGROUND. Process = 2 (Submit) will execute SCLM promotes in BATCH.

3. Enter Breeze control dates (a start date and an end date) that define a valid range of time during which the package can be promoted. This will only be used for promotes to the FREEZE and PRD groups.

Menu SCLM Utilities Jobcard Help ----------------------------------------------------------------------------- SCLM Promote - Entry Panel Command ===> Promote input: Project . . . : SCLMBNK From group . . DEVA Type . . . . . ARCHDEF Member . . . . RENECOB Mode . . 1 1. Conditional Scope . . . 1 1. Normal 2. Unconditional 2. Subunit 3. Report 3. Extended Output control Ex Sub Process . . 1 1. Execute Messages . . 1 2 1. Terminal 2. Submit Report . . . 1 2 2. Printer 3. Data set Printer . . * 4. None Volume . . Breeze control: Override: N (Y/N) Window (yy/mm/dd - hh:mm) 02 / 08 / 07 13 : 30 Thru 02 / 08 / 20 13 : 00 Description: Type: ST (ST/EM)


38

Promote . . .

• Using an ARCHDEF from the DEV groups, Using a Package from the HOLD and FREEZE groups

• Verifies completeness and data integrity with the build map

• Scope of the archdef determines what gets promoted

• Copies members to the next highest group of the hierarchy

• Foreground or background

• Creates promote report

• Purges members from the current group

• Check spooled output for job output correctness if process = 2

Promote Functions

1. Verification

� Verifies that all accounting information is correct

� Determines if all eligible members have been successfully built

2. Copy – copies all associated members to the next higher level group

3. Purge – Deletes all associated members from current group

4. Report generation

Promote Scopes

1. Normal – process named components and all referenced components

2. Subunit – process ADA parts

3. Extended – process as Normal plus downward dependencies .


39

Promote Modes

1. Conditional • Bypass COPY and PURGE phases if verification error

2. Unconditional • Continue processing despite verification errors • Process members with correct accounting information only • Not recommended for use

3. Report • Perform verification phase only • Report contains members eligible for promotion

PROMOTE OUTPUTS

Two files are generated from the Promote process:

� PROMMSGS � PROMREPT

If submitted as a background job, select the Promote job from SDSF. Check PROMMSGS and PROMREPT files for correctness. PROMMSGS

This report is a summary of the Promote process. Any errors in the Promote

will be listed in this report.

PROMREPT

The following report indicates all members that were promoted. An X beneath the columns COPIED TO and PURGED FROM indicate actions performed by the Promote.

******************************* Top of Data ******************************** FLM51000 - PROMOTE PROCESSOR INITIATED - 02:09:08 ON 2002/12/31 FLM52000 - INITIATING VERIFICATION PHASE - 02:09:08 ON 2002/12/31 FLM55000 - INITIATING COPY PHASE - 02:09:09 ON 2002/12/31 FLM57000 - INITIATING PURGE PHASE - 02:09:24 ON 2002/12/31 FLM57001 - INITIATING PURGE FROM GROUP: DEVA FLM58000 - PROMOTE PROCESSOR COMPLETED - 02:09:26 ON 2002/12/31 ******************************* Bottom of Data *****************************


40

********************************* Top of Data ********************************* ** SOFTWARE CONFIGURATION AND LIBRARY MANAGER (SCLM) ** ** ** ** P R O M O T E R E P O R T ** ** 2002/12/31 02:09:08 ** ** PROJECT: SCLMTFS ** ** TO GROUP: HOLDA ** ** FROM GROUP: DEVA ** ** TYPE: ARCHDEF ** ** ARCH. MEM.: IBM01 ** ** ALTERNATE: SCLMTFS ** ** SCOPE: NORMAL ** ** MODE: CONDITIONAL ** ** NOTE: "*" INDICATES "OUT OF SCOPE" ITEMS. ** ******************************************************************************* PAGE 2 TYPE: ARCHDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 01:46:17 X X PAGE 3 TYPE: LECDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 01:46:46 X X PAGE 4 TYPE: LOAD COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:04:00 X X PAGE 5 TYPE: OBJ COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:04:42 X X PAGE 6 TYPE: SOURCE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:04:17 X X PAGE 7 ******************************************************************************* ** B U I L D M A P S ** ******************************************************************************* PAGE 8 TYPE: ARCHDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:04:34 X X PAGE 9 TYPE: LECDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:04:34 X X PAGE 10 TYPE: SOURCE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE HOLDA DEVA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:04:34 X X ******************************** Bottom of Data ********************************


41

Promote User Exits The following additional actions occur with a Promote:

� Stop Promote

Stops the SCLM promote if not type package when promoting to FREEZE and PRD.

� Create Breeze Inventory Records

Based on the naming conversion of the SCLM package. Create Breeze approval records for promotes to groups FREEZE and PRD.

� Copy to the current Endevor Load libraries

During the build and the promote processes all load types will be copied to the corresponding current Endevor libraries

� Copy to Staging CICS Load libraries

During the promote process to the PRD group the CICS loads and BMS loads will be copied to the staging CICS library.


42

SCLM Package Processing

SCLM package process must be used to promote SCLM members to the FREEZE and PRD groups. Package processing will invoke the SCLM Breeze process. Breeze provides package approval processing within SCLM.

SCLM Package Naming Conventions Characters 1 – 3 = Current Endevor Subsystem. This will be validated through SCLM. If a new subsystem needs to be created contact the SCLM administrator. Character 4 = Recompile package contents If this character is a ‘2’ the package contents will be recompiled.

2 = Recompile package contents.

Characters 5 – 8 = variable characters

May be a combination of alpha and numeric characters.

Example: AIM2RSF1 is a valid Package name for the AIM subsystem. The package contents will be recompiled when promoted to the FREEZE group.


43

Steps to Create a New Package 1. Set the Package switch to ‘Y’ on the SCLM main menu. (This will place

‘PACKAGE’ in the SCLM alternate project field.)

2. Type a “hold” group name in the group field on the SCLM main menu.


4. Specify Type (PACKAGE) and Member (package name) being created.


6. Select the types for the Package and press Enter.

7. Select the members for the package and press Enter.

� The package member will be displayed.

� Add a comment for a description of the changes if desired.

8. Press End to return to the SCLM Main Edit panel.

Steps to Edit an Existing Package in SCLM 1. Set the Package switch to ‘Y’ on the SCLM main menu. (This will place

‘PACKAGE’ in the SCLM alternate project field.)

2. Type a “hold” group in the field on the SCLM main menu.


4. Specify Type (PACKAGE). Press Enter. A member list will appear.

5. Select the package member you would like to edit.

6. Press Enter to invoke package processing.

7. Select the types for the package and press Enter.

8. Select the members for the package press Enter.

� The package member will be displayed with the additional members added to the package.

9. Press End to return to SCLM Main Edit panel.

This panel allows selection by Type of what will be in the package archdefs.


44

Place an ‘S’ next to each member from this type that will be included in the package for promotion.

Menu Functions Utilities Help ------------------------------------------------------------------------------ MEMBER LIST SCLMBNK.DEVA.ARCHDEF Row 00001 of 0005 Command ===> Scroll ===>PAGE Name Prompt Lib Size Created Changed ID . BR14 2 8 2001/08/29 2001/08/29 09:36:19 QAG097 S IBM01 1 3 2001/08/29 2001/08/29 18:54:27 QAG096 . LODONLY 1 8 2001/08/29 2001/08/29 09:33:50 QAG097 . RRBBOBY 1 1 2001/08/29 2001/08/29 11:33:45 QAG097 . TEST1 4 2 2001/08/24 2001/08/24 13:20:24 QAG098 **End** |-----------------------------------------------------| | Select all ARCHDEF members to add to PACKAGE IBM001 | |-----------------------------------------------------|

Menu Functions Utilities Help ------------------------------------------------------------------------------ MEMBER LIST SCLM.PROJDEFS.PKGTYPES Row 00001 of 00006 Command ===> Scroll ===> CSR Name Prompt Size Created Changed ID S ARCHDEF . CPTLIB . EGLLIB . FEXLIB . FMALIB . FQLLIB **End** |-----------------------------------------------------------| | Select all types that you wish to include in this package | |-----------------------------------------------------------|


45

Creating Delete Packages

You would use this process to get approval to delete SCLM members from FREEZE or PRD. DELETPKG deletes from the TO group (or the group you are promoting to). Please NOTE: Type DELETPKG works differently than Type PACKAGE. With DELETPKG you need to select all the types you want to delete for that program. Selecting type Archdef, will only delete the archdef member. If you want to delete everything for a member, you need to select archdef, lecdef(if any), lecdefa(if any), lecdefc(if any), lecdefi(if any), lecdefo(if any), lecdefr(if any), lecdefsp(if any), bind(if any), ccdef(if any) and source. Steps to Create a New Delete Package 1. Select option 2 from the SCLM main menu for the SCLM Edit panel.

2. Specify Type (DELETPKG) and Member (package name) being created.


4. Select the types for the Delete Package and press Enter.

5. Select the members for the delete package and press Enter.

� The delete package member is displayed.

� Add a comment for a description of the changes if desired.

6. Press End to return to the SCLM Library Utility panel.

Steps to Edit an Existing Delete Package in SCLM 1. Select Option 3.1 from the SCLM main menu for the Library Utility panel.

2. Specify Type (DELETPKG). Press Enter. A member list appears.

3. Enter an ‘E’ next to the delete package member you would like to edit.

4. Press Enter to invoke delete package processing.

5. Select the types for the delete package and press Enter.

6. Select the members for the delete package press Enter.

7. The delete package member will be displayed with the additional members added to the delete package.



46

This panel allows selection by Type of what will be in the package archdefs. Place an ‘S’ next to each member from this type that will be included in the package for promotion.

Menu Functions Utilities Help ----------------------------------------------------------------------------- MEMBER LIST SCLM.HOLDA.ARCHDEF Row 00001 of 0005 Command ===> Scroll ===>PAGE Name Prompt Lib Size Created Changed ID . BR14 2 8 2001/08/29 2001/08/29 09:36:19 QAG097 S IBM01 1 3 2001/08/29 2001/08/29 18:54:27 QAG096 . LODONLY 1 8 2001/08/29 2001/08/29 09:33:50 QAG097 . RRBBOBY 1 1 2001/08/29 2001/08/29 11:33:45 QAG097 . TEST1 4 2 2001/08/24 2001/08/24 13:20:24 QAG098 **End** |-----------------------------------------------------| | Select all ARCHDEF members to add to PACKAGE IBM001 | |-----------------------------------------------------|

Menu Functions Utilities Help ------------------------------------------------------------------------------ MEMBER LIST SCLM.PROJDEFS.DELTYPES Row 00001 of 00006 Command ===> Scroll ===> CSR Name Prompt Size Created Changed ID S ARCHDEF . BINDCTL . CCDEF . CPYLIB . LECDEF . LOADB . LOADO . MACLIB S SOURCE **End** |-----------------------------------------------------------| | Select all types that you wish to include in this package | |-----------------------------------------------------------|


47

This is an example of what the package member will look like. The member can then be edited to add a description of the deletion as comments after line 2.

------------------------------------------------------------------------------ EDIT SCLM.UT2.DELETPKG(DELIBM01) - 01.00 Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ***************************** * NAME: DELIBM01 * DESC: DELETPKG FOR DELIBM01 * * * SOURCE MEMBERS * PROM IBM01 SOURCE * Promote member * * ARCHDEF MEMBERS * PROM IBM01 ARCHDEF * Promote member ****** **************************** Bottom of Data ****************************


48

Package Build Process Once the Package has been created use the SCLM build process to build the package. Use SCLM PACKAGE alternate. The package will only be built in the HOLD groups. The package build will only create a build map for the package. (For complete instruction see SCLM Build process in this manual). The following is an example of a build report for the package build.

********************************* Top of Data ********************************* ******************************************************************************* ******************************************************************************* ** ** ** ** ** SOFTWARE CONFIGURATION AND LIBRARY MANAGER (SCLM) ** ** ** ** B U I L D R E P O R T ** ** ** ** 2002/12/31 02:04:34 ** ** ** ** PROJECT: SCLMTFS ** ** GROUP: HOLDA ** ** TYPE: PACKAGE ** ** MEMBER: IBMTEST ** ** ALTERNATE: PACKAGE ** ** SCOPE: NORMAL ** ** MODE: CONDITIONAL ** ** ** ** ** ******************************************************************************* ******************************************************************************* ******* B U I L D O U T P U T S G E N E R A T E D ******* Page 1 MEMBER TYPE VERSION KEYWORD ------ ---- ------- ------- ******* B U I L D M A P S G E N E R A T E D ******* Page 2 (REASON FOR REBUILD) MEMBER TYPE VERSION MEMBER TYPE ------ ---- ------- ------- ---- IBMTEST PACKAGE 1 IBMTEST PACKAGE ******* B U I L D O U T P U T S D E L E T E D ******* Page 3 MEMBER TYPE VERSION KEYWORD ------ ---- ------- ------- ******* NO MODULES DELETED ******* ******* B U I L D M A P S D E L E T E D ******* Page 4 (REASON FOR DELETE) MEMBER TYPE VERSION MEMBER TYPE ------ ---- ------- ------- ---- ***** NO BUILD MAPS DELETED ***** ******************************** Bottom of Data ********************************


49

Package Promote Approval Process

When promoting to the SCLM FREEZE or PRD groups the SCLM promote will have to run 2 times. This first promote will invoke the Breeze approval process. After the users have approved the SCLM package. (For more detail on how to approve a package see the Package Approval section in this manual). The second promote will actually promote the SCLM members.

The promote will be invoked using the same process as described in the SCLM promote process. (For more details see the SCLM Promote process in this manual).

The following is a sample of the Breeze promote messages issued during the first promote process.

******************************************************* * Now verifying package with Promote Report request. * ******************************************************* ******************************************************* * Promote Report (verify function) succeeded. * * Note SCLM message FLM87107 means that the Promote * * Report for this package was successful. * ******************************************************* ******************************************************* * Copying Package Defaults from Breeze Promote Panel * * Promotion Start Date: 03/01/01 * * Promotion Start Time: 13:30 * * Promotion End Date: 03/08/20 * * Promotion End Time: 13:00 * * Desc: * * Package Type: STANDARD * ******************************************************* ******************************************************* * Content and approver collection in progress for * * Package RENETRST. * * From Group = HOLDA * * To Group = FREEZE * ******************************************************* ******************************************************* * Breeze message: STARTING APPROVAL * * Package RENETRST has 0009 individual * * approvers of which 0000 are required. * * * * The package is not eligible for promotion * * until the package is approved. All users * * have been notified that their vote is * * required. * ******************************************************* RETURN CODE FROM PROMOTE VERIFY = 4


50

The following is a sample of the promote messages (PROMMSGS) issued during the first promote process. When the Breeze approval process is invoked.

The following is a sample of the promote report (PROMREPT) issued during the first promote process when the Breeze approval process is invoked.

********************************* Top of Data ********************************* ** SOFTWARE CONFIGURATION AND LIBRARY MANAGER (SCLM) ** ** ** ** P R O M O T E R E P O R T ** ** ** ** 2002/12/31 02:09:08 ** ** ** ** ** ** PROJECT: SCLMTFS ** ** TO GROUP: FREEZE ** ** FROM GROUP: HOLDA ** ** TYPE: PACKAGE ** ** ARCH. MEM.: IBMTEST ** ** ALTERNATE: PACKAGE ** ** SCOPE: NORMAL ** ** MODE: CONDITIONAL ** ** ** ** ** ** NOTE: "*" INDICATES "OUT OF SCOPE" ITEMS. ** ******************************************************************************* PAGE 2 TYPE: ARCHDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:46:17 PAGE 3 TYPE: LOAD COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:46:46 PAGE 4 TYPE: OBJ COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________

********************************* Top of Data ********************************** FLM51000 - PROMOTE PROCESSOR INITIATED - 18:28:14 ON 2003/01/01 FLM52000 - INITIATING VERIFICATION PHASE - 18:28:14 ON 2003/01/01 FLM06512 - VERIFICATION ERROR FROM USER EXIT ROUTINE: PROMEXT1, CODE: 4 FLM58000 - PROMOTE PROCESSOR COMPLETED - 18:28:19 ON 2003/01/01 ******************************** Bottom of Data ********************************


51

(Promote report continued)

IBM01 2002/12/31 03:04:00 PAGE 5 TYPE: PACKAGE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBMTEST 2002/12/31 03:04:42 PAGE 6 TYPE: SOURCE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:17 PAGE 7 ******************************************************************************* ** ** ** B U I L D M A P S ** ** ** ******************************************************************************* PAGE 8 TYPE: ARCHDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:34 PAGE 9 TYPE: LECDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:34

PAGE 10 TYPE: PACKAGE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBMTEST 2002/12/31 03:04:34 PAGE 11 TYPE: SOURCE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:34 ******************************** Bottom of Data ********************************


52

Package Promote Process After the package has been approved the user will need to run a second SCLM promote to actually promote the members to the next SCLM group.

The promote will be invoked using the same process as described in the SCLM promote process or the user can wait for the Batch SCLM sweep job to run. The sweep job will promote all approved packages in 30 minutes intervals. (For more details see the SCLM Promote process in this manual.)

The following is a sample of the Breeze promote messages issued during the promote process.

The following is a sample of the SCLM promote messages (PROMMSGS) issued during the promote process.

******************************************************* * Now verifying package with Promote Report request. * ******************************************************* ******************************************************* * Promote Report (verify function) succeeded. * * Note SCLM message FLM87107 means that the Promote * * Report for this package was successful. * ******************************************************* ******************************************************* * Package RENETRST is approved and can be promoted. * * From Group = HOLDA * * To Group = FREEZE * ******************************************************* RETURN CODE FROM PROMOTE VERIFY = 0 ******************************************************* * PACKAGE IBMTEST has been promoted and the * * Breeze database has been updated. * *******************************************************

FLM51000 - PROMOTE PROCESSOR INITIATED - 19:55:36 ON 2003/01/01 FLM52000 - INITIATING VERIFICATION PHASE - 19:55:36 ON 2003/01/01 FLM55000 - INITIATING COPY PHASE - 19:55:42 ON 2003/01/01 FLM57000 - INITIATING PURGE PHASE - 19:55:48 ON 2003/01/01 FLM57001 - INITIATING PURGE FROM GROUP: TEST FLM58000 - PROMOTE PROCESSOR COMPLETED - 19:55:49 ON 2003/01/01


53

The following is a sample of the SCLM promote report (PROMREPT) issued during the promote process. Error!

********************************* Top of Data ********************************* ** SOFTWARE CONFIGURATION AND LIBRARY MANAGER (SCLM) ** ** ** ** P R O M O T E R E P O R T ** ** ** ** 2002/12/31 02:09:08 ** ** ** ** ** ** PROJECT: SCLMTFS ** ** TO GROUP: FREEZE ** ** FROM GROUP: HOLDA ** ** TYPE: PACKAGE ** ** ARCH. MEM.: IBMTEST ** ** ALTERNATE: PACKAGE ** ** SCOPE: NORMAL ** ** MODE: CONDITIONAL ** ** ** ** ** ** NOTE: "*" INDICATES "OUT OF SCOPE" ITEMS. ** ******************************************************************************* PAGE 2 TYPE: ARCHDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:46:17 X X PAGE 3 TYPE: LOAD COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 02:46:46 X X PAGE 4 TYPE: OBJ COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:00 X X PAGE 5 TYPE: PACKAGE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBMTEST 2002/12/31 03:04:42 X X PAGE 6 TYPE: SOURCE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:17 X X


54

(Promote report continued)

PAGE 7 ******************************************************************************* ** ** ** B U I L D M A P S ** ** ** ******************************************************************************* PAGE 8 TYPE: ARCHDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:34 X X PAGE 9 TYPE: LECDEF COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:34 X X

PAGE 10 TYPE: PACKAGE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBMTEST 2002/12/31 03:04:34 X X PAGE 11 TYPE: SOURCE COPIED TO PURGED FROM MEMBER DATE TIME MESSAGE FREEZE HOLDA ________ __________ ________ ________ _________ ___________ IBM01 2002/12/31 03:04:34 X X ******************************** Bottom of Data ********************************


55

Steps to Edit an Existing Member in a Promoted Package


2. Specify Type. Press Enter. A list of members will appear.

3. Select the member you want to edit.

4. Press Enter to invoke the Edit panel.

5. Make changes to save the member to the lowest level of the hierarchy. (For complete instructions see Adding/Updating a Member in SCLM.)

6. If the Language definition needs to be changed, enter ‘SPROF’ on the command line. A change panel will appear.

7. Build the changed member’s Archdef. (For complete instructions see SCLM Build in this document.)

8. Promote the changed member’s Archdef to one of the SCLM hold groups. (For complete instructions see SCLM Promote – Conditional Mode.)

9. Set the Package switch to ‘Y’ on the SCLM main menu.

10. If changes are needed to the package, edit the package in one of the SCLM Hold Groups. (For instructions see Steps to Edit an Existing Package in SCLM.)

11. Build the package in the hold group where the edit took place in step 10. (For complete instructions see Package Build Process.)

12. Start the SCLM package promotion process by using SCLM option 5. This will re-send the approvals for this package. (For complete instructions see Package Promote – Approval Process.)

13. Once the package has been approved the user can promote the approved package to the FREEZE group. (For complete instructions see Package Promote Process.)


56

14. After testing in the Freeze group the programmer can request the package be promoted to the PRD group. Start the SCLM package production promotion process by using SCLM option 5. This will send the production approvals for this package to the users. (For complete instructions see Package Promote – Approval Process.)

15. Once the package has been approved to promote to production. The SCLM package sweep job will run. The sweep job will look for all packages in approved status. For each approved package the SCLM promote process will in invoked and SCLM will promote the members of the package to the PRD group. (For complete instructions see Package Promote Process.)


57

Topic 5. Architecture Definitions

What Archdefs Do

� Define how to process a member or group of members.

� Specify options for components of SCLM processes.

� Determine how members are tracked.

� Describe the application system's internal structure.

� Specify inputs and outputs for each translator. Four Kinds of Archdefs

HL - High Level

Group other archdefs. Controls process of functions at application or sub-application level. Used to package various members together for processing.

LEC - Link Edit Control

Used to link edit modules. LEC archdefs reference input source with a CC archdef or an INCLD statement. All LEC ARCHDEFS have a LOAD statement.

CC - Compilation Control

Create object module from source. Primarily used to override a compiler option. CC archdefs are referenced by LEC archdefs.

Generic

Process special components that do not create a load module or object.


58

How Archdefs Work.. an Example

PGM1 PGM2

SRCC

SRCC

SRCB

SRCA

SRCD

SRCE

CCDEF

SOURCE

PACKAGE

ARCHDEF(PGM1)**LE(Link Edit) Archdef for PGM1*INCLD SRCA SOURCEINCLD SRCB SOURCEINCL SRCC CCDEFINCLD SRCD SOURCEINCLD SRCE SOURCELOAD PGM1 LOAD

ARCHDEFSCLM

IBMP001

JCL JCL JCL PROC PROC PROC

PACKAGE(IBMP001)**Package Archdef*

ARCHDEFINCL ARCHDEFPGM2INCL PGM1

PROM EGLLIBJCL1

PROM CPTLIBPROC1


59

Understanding Archdef Language Most architecture definition statements have the format:

<keyword> <member> <type> <comment>

<keyword> is an SCLM reserved word. See the SCLM Developer's Guide

for a complete list of keywords. <member> is the name of a part under SCLM control. <type> is the third qualifier of the PDS where the member resides. <comment> is user information appended to the statement. No special

character is needed to indicate a comment at the end of a line. Rules for Coding Archdefs

� One archdef statement per line.

� Columns 1 through 72 only.

� No continuation allowed to next line.

� Upper or lower case allowed.

� Blanks are free format except for CMD, PARM and PARMx keywords.

� Order of statements is generally free format except when multiple inputs must be concatenated together as one input stream.

�� Use MODEL command under Edit session, SCLM option 2, to see ARCHDEF keyword formats.


60

Some Archdef Keywords * Comment

* <comment>

CCODE Identifies a change code to be included or excluded from a build or promote. Used to build related members selectively based on a change code

CCODE <chg code> <INCL¦EXCL> <comment>

CMD Identifies command statements as input to the linkage editor.

Used to include external references, set entry points, etc.

CMD <command statement>

INCL Include another archdef that this archdef references Cannot reference source members directly

INCL <member> <type> <comment>

INCLD Include source member that this archdef references.

Used to identify inputs to a compiler.

INCLD <member> <type> <comment> LIST Identifies member and type for compiler listing

LIST <member> <type> <comment>

LKED Identifies an override linkage editor

LKED <language> <comment>

LMAP Identifies member and type for link edit listing

LMAP <member> <type><comment>


61

LOAD Identifies load module name and type

LOAD <member> <type> <comment> OBJ Identifies object member and type for output

OBJ <member> <type> <comment>

OUTx Identifies output member and type

OUTx <member> <type> <comment>

PARM Parameters(options) passed to all translators in the language definition

PARM <parameters>

PARMx Parameters(options) passed to specific translators; PARMx must be coded on one translator in the language definition

PARMx <parameters>

PROM Identifies a text member to be promoted

PROM <member> <type> <date check>

SINC Identifies source member and type input. Used primarily in a

CC archdef.

SINC <member> <type> <comment>


62

Archdefs for Northern Trust The following arrangement is suggested for archdef members:

� A High-Level archdef is in the PACKAGE library for each grouped promotion.

� Static subroutines do not have LEC archdefs; instead they are referenced by the archdefs for the main modules which statically link them. To create a new HL archdef containing all modules referenced by a given subroutine, use the Subroutine Search Utility, SCLM option 3.T.2.

� All Compilation control archdefs are placed in the CCDEF library, using the same name as the source member.

A programmer should always promote with the PACKAGE member when moving to FREEZE or PRD. The ARCHDEF member is used for all other promotions.


63

SCLM Sample Archdefs Table

On the following page is a chart that will help determine what SCLM language to assign to a source member, how many LECDEF types will be needed, and if a Bind member is to be included in the ARCHDEF.

Column 1 shows the Endevor type used in New Endevor. This column also gives the name of the sample Archdef to use as a guide to create an Archdef.

Column 2 shows the SCLM language to assign to the SCLM source member.

Column 3 shows if a LECDEF member exists for this sample Archdef. If this column is populated, use the name that appears in the column as a sample to create the LECDEF under the source member name.

Column 4 shows if a LECDEFA member exists for this sample Archdef. If this column is populated, use the name that appears in the column as a sample to create the LECDEFA under the source member name.

Column 5 shows if a LECDEFC member exists for this sample Archdef. If this column is populated, use the name that appears in the column as a sample to create the LECDEFC under the source member name.

Column 6 shows if a LECDEFI member exists for this sample Archdef. If this column is populated, use the name that appears in the column as a sample to create the LECDEFI under the source member name.

Column 7 shows if a LECDEFO member exists for this sample Archdef. If this column is populated, use the name that appears in the column as a sample to create the LECDEFO under the source member name.

Column 8 shows if a LECDEFR member exists for this sample Archdef. If this column is populated, use the name that appears in the column as a sample to create the LECDEFR under the source member name.

Column 9 shows if a LECDEFSP member exists for this sample Archdef. If this column is populated, use the name that appears in the column as a sample to create the LECDEFSP under the source member name.

Column 10 shows if a Bind member is needed. If this column is populated, then the user should create a bind member under the source member name.


64

SCLM Source to Language Mapping Chart project.group.load i.e. SCLMTFS.DEVA.LOADC

ENDEVOR TYPE

SCLM SOURCE LANG

LOAD LECDEF

LOADA LECDEFA

LOADC LECDEFC

LOADI LECDEFI

LOADO LECDEFO

LOADR LECDEFR

LOADSP LECDEFSP

BIND

ASMB ASMB LEC ASMC ASMC LEC ASMX ASMB LEC BMS BMS BMS CO3B CO3B LEC CO3BI CO3B LECI CO3BJ CO3B LECIS CO3BM CO3B2 LECI BIND CO3BN CO3B2 LECIS BIND CO3B2 CO3B2 LEC2 BIND CO3B2#R CO3B2#R LECSR BIND CO3B2#RT CO3B2RT LEC2 BIND CO3C CO3C LECC CO3C##C CO3C LECC CO3C2 CO3C2 LECC2 BIND CO3F2 CO3B2 LECI2 BIND CO3II CO3B LECI CO3IJ CO3B LECIS CO3IM CO3B2 LECI BIND CO3IN CO3B2 LECIS BIND CO3M CO3C LECCM CO3M2 CO3C2 LECCM2 BIND CO3P CO3B LECSP CO3P2 CO3B2 LECSP2 BIND CO3Q CO3B LECR CO3Q2 CO3B2 LECQ2 BIND CO3S CO3C LECCS CO3S##CS CO3C LECCCS CO3S##S CO3C LECCS CO3S2 CO3C2 LECCS2 BIND CO3S2#CS CO3C2 LECCCS2 BIND CO3U##01 CO3B LECR LECSP CO3U##02 CO3B LECR LECC LECSP CO3U2#01 CO3B2 LEC2SP LECSP2 BIND CO3U2#02 CO3B2 LEC2SP LECC2 LECSP2 BIND CO3U2#03 CO3B2 LEC2SP LECIS BIND CO3U2#06 CO3B2 LEC2SP LECA2 LECC2 LECIR LECO LECR2 LECSP2 BIND SPCU##01 CO3B LECSP LECCSP LECSPSP SPCU##02 CO3C LECCSP LECCCSP SPCU##03 CO3C LECCSP LECCCSP LECSPCSP CO3X CO3B LECR LECR CO3X2 CO3B2 LEC2R LEC2 BIND CO3XM CO3B2 LEC2R LEC2 LECIR BIND PL1B PL1B LECP1 PL1BI PL1B LECPI PL1B2 PL1B2 LECP2 BIND PL1II PL1B LECP PL1IM PL1B2 LECP BIND EZTB EZTB EZTB EZTB2 EZTB2 EZTB2 BIND MLOAD N/A LOD MRCB MRCB MRCB


65

SCLM Type to Language Mapping Chart

TYPE LANG ARCHDEF -----------> ARCHDEF BIND -----------> BIND CBKLIB -----------> same as SOURCE (see below) CCDEF -----------> ARCHDEF CPTLIB -----------> TEXT DELETPKG -----------> ARCHDEF EGLLIB -----------> TEXT FEXLIB -----------> TEXT FMALIB -----------> TEXT FQLLIB -----------> TEXT LECDEF -----------> ARCHDEF

LECDEFA -----------> ARCHDEF

LECDEFC -----------> ARCHDEF

LECDEFI -----------> ARCHDEF

LECDEFO -----------> ARCHDEF

LECDEFR -----------> ARCHDEF

LECDEFSP -----------> ARCHDEF

MACLIB -----------> TEXT

PACKAGE -----------> ARCHDEF

SOURCE -----------> *

*see column SCLM SOURCE TYPE above


66

Samples of each type of LECDEF, ARCHDEF and BIND can be found in the following datasets (where XXX is BNK, FIN, HRM, TEC, or TFS):

� ‘SCLMXXX.PRD.ARCHDEF’

� ‘SCLMXXX.PRD.LECDEF’

� ‘SCLMXXX.PRD.LECDEFA’

� ‘SCLMXXX.PRD.LECDEFC’

� ‘SCLMXXX.PRD.LECDEFI

� ‘SCLMXXX.PRD.LECDEFO’

� ‘SCLMXXX.PRD.LECDEFR’

� ‘SCLMXXX.PRD.LECDEFSP’

� ‘SCLMXXX.PRD.BIND’

SCLM ARCHDEFS – Samples According to New Endevor Types

ASMB

Assembler Batch ASMB (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR

Assembler Batch ASMB (ARCHDEF)

* NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION


67

CO3B

COBOL Batch CO3B (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR

COBOL Batch CO3B (ARCHDEF)


CO3B2

COBOL Batch/DB2 CO3B2 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR COPY DSNELI ARCHDEF * COPY IN DB2 LINK STMTS

COBOL Batch/DB2 CO3B2 (ARCHDEF)

* NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCLD XXXXXXXX BIND * DB2 BIND STATEMENTS


68

CO3BI

COBOL Batch/IMS CO3BI (LECDEFI) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADI * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR COPY DFSLI000 ARCHDEF * COPY IN IMS LINK STMTS COPY DLITCBL ARCHDEF * COPY IN IMS LINK STMTS

COBOL Batch/IMS CO3BI (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEFI * LINK-EDIT DEFINITION


69

CO3BM

COBOL Batch/IMS/DB2 CO3BM (LECDEFI) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADI * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR COPY DFSLI000 ARCHDEF * COPY IN IMS/DB2 LINK STMTS COPY DLITCBL ARCHDEF * COPY IN IMS/DB2 LINK STMTS

COBOL Batch/IMS/DB2 CO3BM (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEFI * LINK-EDIT DEFINITION INCLD XXXXXXXX BIND * DB2 BIND STATEMENTS

CO3X

COBOL Batch/CICS CO3X (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR

COBOL Batch/CICS CO3X (LECDEFC) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADC * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR

COBOL Batch/CICS CO3X (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFC * LINK-EDIT DEFINITION


70

CO3X2

COBOL Batch/CICS/DB2 CO3X2 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DSNELI ARCHDEF * COPY IN DB2 LINK STMTS

COBOL Batch/CICS/DB2 CO3X2 (LECDEFC) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADC * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DSNELI ARCHDEF * COPY IN DB2 LINK STMTS

COBOL Batch/CICS/DB2 CO3X2 (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFC * LINK-EDIT DEFINITION INCLD XXXXXXXX BIND * DB2 BIND STATEMENTS


71

BMS

CICS MAP BMS (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX BMSLIB * CREATE LOAD MODULE LKED LEBMS * LINKAGE EDITOR

CICS MAP BMS (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION

MLOD

LOAD ONLY/NON-SCLM LOAD MLOD (LECDEF) * * LINK EDIT CONTROL ARCHDEF FOR LOAD ONLY MEMBER XXXXXXXX LOAD XXXXXXXX LOAD * LINK EDIT LOAD MODULE LKED LOD * LINK WITH LOAD ONLY LANGUAGE SINC DUMMY SOURCE * INCLUDE DUMMY SOURCE INPUT CMD DSNAME INPUT.DATASET.NAME * INPUT DATASET NAME CMD NAME XXXXXXXX * INPUT MEMBER NAME

LOAD ONLY/NON-SCLM LOAD MLOD (ARCHDEF)

* NAME: XXXXXXXX * DESC: INCLUDE LOAD ONLY CONTROL MEMBER FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION


72

EZTB

Eztrieve Batch EZTB (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR

Eztrieve Batch EZTB (ARCHDEF)


PL1B

PL1 Batch PL1B (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LELET * LINKAGE EDITOR

PL1 Batch PL1B (ARCHDEF)



73

CO3U2#06

Common DB2 Batch/CICS/IMSB/IMSO/SP/DSNRLI/DSNALI CO3U2#06 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DSNRLI ARCHDEF

Common DB2 Batch/CICS/IMSB/IMSO/SP/DSNRLI/DSNALI CO3U2#06 (LECDEFA) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADA * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DSNALI ARCHDEF

Common DB2 Batch/CICS/IMSB/IMSO/SP/DSNRLI/DSNALI CO3U2#06 (LECDEFC) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADC * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DFHELII ARCHDEF COPY DSNCLI ARCHDEF

Common DB2 Batch/CICS/IMSB/IMSO/SP/DSNRLI/DSNALI CO3U2#06 (LECDEFI) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADI * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DFSLI000 ARCHDEF


74

Common DB2 Batch/CICS/IMSB/IMSO/SP/DSNRLI/DSNALI CO3U2#06 (LECDEFO) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADO * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DFSLI000 ARCHDEF

Common DB2 Batch/CICS/IMSB/IMSO/SP/DSNRLI/DSNALI CO3U2#06 (LECDEFR) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADR * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DSNRLI ARCHDEF

Common DB2 Batch/CICS/IMSB/IMSO/SP/DSNRLI/DSNALI CO3U2#06 (LECDEFSP) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOADSP * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DSNRLI ARCHDEF


75

Common DB2 Batch/CICS/IMSB/IMSO/SL/DSNRLI/DSNALI CO3U2#06 (BIND) /* rexx */ trace o ARG parm parse upper var parm . '('option')' . '('group')' option = strip(option) group = strip(group) /*--------------------------------------------------------------------*/ /* specify a dbrm include statement for each dbrm: */ /* (this comment is required by sclm bind parser) */ /* */ /* %INCLUDE XXXXXXXX */ /*--------------------------------------------------------------------*/ /* change the next two lines to dbrm/package name */ /*--------------------------------------------------------------------*/ dbrm = 'XXXXXXXX' pkg = 'XXXXXXXX' colid = 'CCC' /*--------------------------------------------------------------------*/ /* change the next two lines to desired system and subsy/subset */ /*--------------------------------------------------------------------*/ syst = 'PPP' sset = 'SSS' /*--------------------------------------------------------------------*/ /* call bindplan to perform bind */ /*--------------------------------------------------------------------*/ parms=option","group","colid","dbrm","pkg","syst","sset EX "'SCLM.PROJDEFS.REXX(BINDPLAN)'" "'"parms"'" exit rc

Common DB2 Batch/CICS/IMSB/IMSO/SL/DSNRLI/DSNALI CO3U2#06 (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFA * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFC * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFI * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFO * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFR * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFSP * LINK-EDIT DEFINITION INCLD XXXXXXXX BIND * DB2 BIND PARMS


76

CCDEF Example for CO3B

COBOL Batch CO3B (CCDEF) * COMPILATION CONTROL ARCHDEF COBOL II MODULE * MEMBER NAME: XXXXXXXX (LEC) OBJ XXXXXXXX OBJ * CREATE OBJECT SINC XXXXXXXX SOURCE * INCLUDE SOURCE PARM1 DATA(24)

COBOL Batch CO3B (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX CCDEF * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR



Go in CCDEF PARM1 is for Cobol or PL1 parm overrides PARM2 is for DB2 pre-compiler parm overrides PARM3 is for CICS translator parm overrrides PARM4 is for BMS, BMSC, BMSD map csect overrides PARM5 is for BMS, BMSC, BMSD map dsect overrides Go in LECDEFs PARM6 is for linkage editer overrides


77

CCDEF Example for CO3B2

COBOL Batch CO3B2 (CCDEF) * COMPILATION CONTROL ARCHDEF COBOL II MODULE * MEMBER NAME: XXXXXXXX (LEC) OBJ XXXXXXXX OBJ * CREATE OBJECT OUT1 XXXXXXXX DBRMLIB * CREATE DBRM SINC XXXXXXXX SOURCE * INCLUDE SOURCE PARM1 DATA(24) PARM2 APOST, APOSTSQL, STDSQ(NO)

COBOL Batch CO3B2 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX CCDEF * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR COPY DSNELI ARCHDEF * COPY IN IMS/DB2 LINK STMTS

COBOL Batch CO3B2 (ARCHDEF)

* NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCL XXXXXXXX BIND * DB2 BIND PARMS


78

CCDEF Example for PL1B

PL1 Batch PL1B (CCDEF) * COMPILATION CONTROL ARCHDEF COBOL II MODULE * MEMBER NAME: XXXXXXXX (LEC) OBJ XXXXXXXX OBJ * CREATE OBJECT SINC XXXXXXXX SOURCE * INCLUDE SOURCE PARM1 DATA(24)

PL1 Batch PL1B (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX CCDEF * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LELET * LINKAGE EDITOR

PL1 Batch PL1B (ARCHDEF)



79

CCDEF Example for PL1B2

PL1 Batch PL1B2 (CCDEF) * COMPILATION CONTROL ARCHDEF COBOL II MODULE * MEMBER NAME: XXXXXXXX (LEC) OBJ XXXXXXXX OBJ * CREATE OBJECT OUT1 XXXXXXXX DBRMLIB * CREATE DBRM SINC XXXXXXXX SOURCE * INCLUDE SOURCE PARM1 DATA(24) PARM2 APOST, APOSTSQL, STDSQ(NO)

PL1 Batch PL1B2 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX CCDEF * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LELET * LINKAGE EDITOR COPY DSNELI ARCHDEF * COPY IN IMS/DB2 LINK STMTS

PL1 Batch PL1B2 (ARCHDEF)

* NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCL XXXXXXXX BIND * DB2 BIND PARMS


80

Example for SOURCE2 Program

COBOL CICS CO3C (CCDEF) * COMPILATION CONTROL ARCHDEF COBOL II MODULE * MEMBER NAME: XXXXXXXX (LEC) OBJ XXXXXXXX OBJ2 * CREATE OBJECT SINC XXXXXXXX SOURCE2 * INCLUDE SOURCE

COBOL Batch CO3B (LECDEF)

* NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR

COBOL Batch CO3C (LECDEFC) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX CCDEF * CREATE OBJECT LOAD XXXXXXXX LOADC * CREATE LOAD MODULE LKED LECMNRNT * LINKAGE EDITOR COPY DFHECI ARCHDEF


* NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCL XXXXXXXX LECDEFC * LINK-EDIT DEFINITION


81

Topic 6. SCLM and DB2

What SCLM Types Are Used for DB2?

� SOURCE – This is the COBOL/PL1/EZTRIEVE source program. The Language associated with this type of source member can be one of the following: CO3B2, CO3B2#R, CO3C2, PL1B2, EZTB2.

� BIND – This is a bind proxy member used in SCLM to specify the package name and DBRMs used for the DB2 Bind. This member was initially created during the migration from Endevor. If no new DBRMs need to be added this member does not need to be modified. SCLM uses the member to perform DB2 package binds.

� LECDEF – This is the link-edit Architecture Definition. This is used to define the DB2, CICS, and LOAD modules to SCLM. For more information on architecture definitions see the Architecture definitions section of this guide. For samples of DB2 LECDEF look in ‘SCLMBNK.PRD.LECDEF’ member CO3B2 (batch DB2) or CO3C2 (CICS DB2). If no new link-edit control statements need to be added this member does not need to be modified. SCLM uses the member in production to build the ARCHDEF.

� ARCHDEF – This is the high level Architecture Definition that ties the link-edit and bind process together. This is used to define the LECDEF and BIND member to SCLM so they can be built and promoted as one unit. For samples of DB2 ARCHDEF look in ‘SCLMBNK.PRD.ARCHDEF’ member CO3B2 (batch DB2) or CO3C2 (CICS DB2). This member should not need to be modified once created. SCLM uses the member in production to build the ARCHDEF.


82

DB2 Types – Examples by Type (BIND)

/* rexx */ trace o ARG parm parse upper var parm . '('option')' . '('group')' option = strip(option) group = strip(group) /*--------------------------------------------------------------------*/ /* specify a dbrm include statement for each dbrm: */ /* (this comment is required by sclm bind parser) */ /* */ /* %INCLUDE XXXXXXXX */ /*--------------------------------------------------------------------*/ /* change the next two lines to dbrm/package name */ /*--------------------------------------------------------------------*/ dbrm = 'XXXXXXXX' pkg = 'XXXXXXXX' colid = 'CCC' /*--------------------------------------------------------------------*/ /* change the next two lines to desired system and subsy/subset */ /*--------------------------------------------------------------------*/ syst = 'PPP' sset = 'SSS' /*--------------------------------------------------------------------*/ /* call bindplan to perform bind */ /*--------------------------------------------------------------------*/ parms=option","group","colid","dbrm","pkg","syst","sset EX "'SCLM.PROJDEFS.REXX(BINDPLAN)'" "'"parms"'" exit rc

CO3B2

COBOL Batch/DB2 CO3B2 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LECMN * LINKAGE EDITOR COPY DB2LINK LECDEF * COPY IN DB2 LINK STMTS

COBOL Batch/DB2 CO3B2 (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCLD XXXXXXXX BIND * DB2 BIND STATEMENTS


83

PL1B2

PL1 Batch/DB2 PL1B2 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LELET * LINKAGE EDITOR COPY PLISTART LECDEF * COPY IN DB2 LINK STMTS

PL1 Batch/DB2 PL1B2 (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCLD XXXXXXXX BIND * DB2 BIND STATEMENTS

EZTB2

EZTRIEVE Batch/DB2 EZTB2 (LECDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL (LEC) ARCHDEF FOR XXXXXXXX * INCLD XXXXXXXX SOURCE * CREATE OBJECT LOAD XXXXXXXX LOAD * CREATE LOAD MODULE LKED LEEZT * LINKAGE EDITOR

EZTRIEVE Batch/DB2 EZTB2 (ARCHDEF) * NAME: XXXXXXXX * DESC: LINK-EDIT CONTROL ARCHDEF FOR XXXXXXXX * INCL XXXXXXXX LECDEF * LINK-EDIT DEFINITION INCLD XXXXXXXX BIND * DB2 BIND STATEMENTS


84

Steps to Create a New DB2 Program


2. Specify Type (SOURCE) and Member (IBM01) being added.


4. Copy or enter the new member (IBM01) code.



a. Enter a Language (example: CO3B2) on the SCLM Edit Profile panel and press Enter.

b. Leave Language ‘blank’ and press Enter.


� Select a DB2 language (example: CO3B2) and press Enter.

7. Create the Bind Proxy member. Select Option 2 from the SCLM main menu for the SCLM Edit panel.

8. Specify Type (BIND) and Member (IBM01) being added.


10. Copy member (BIND) this will provide a sample of the bind member to edit. Change the XXXXXXXX to IBM01. Change CCC to collection id. Change PPP to the Endevor systems. Change SSS to the Endevor Subsystem.


12. Do one of the following: a. Enter a Language (BIND) on the SCLM Edit Profile panel and press Enter. b. Leave Language ‘blank’ and press Enter.


� Select BIND as the language and press Enter.

13. Create the LECDEF member. Select Option 2 from the SCLM main menu for the SCLM Edit panel.

14. Specify Type (example: LECDEF) and Member (IBM01) being added.


16. Copy in the appropriate sample LECDEF from the SCLM Sample Archdef Table. Change the XXXXXXXX to IBM01.


85


18. Do one of the following: a. Enter a Language (ARCHDEF) on the SCLM Edit Profile panel and press

Enter. b. Leave Language ‘blank’ and press Enter.


� Select ARCHDEF as the language and press Enter.

Note: Steps 13 – 18 might need to be executed several times depending on how many Lecdef types you have. Refer to the SCLM Sample Archdefs Table.

19. Create the ARCHDEF member. Select Option 2 from the SCLM main menu for the SCLM Edit panel.

20. Specify Type (ARCHDEF) and Member (IBM01) being added.


22. Copy in the appropriate sample ARCHDEF from the SCLM Sample Archdef table. Change the XXXXXXXX to IBM01.



a. Enter a Language (ARCHDEF) on the SCLM Edit Profile panel and press Enter.

b. Leave Language ‘blank’ and press Enter.


� Select ARCHDEF as the language and press Enter.

25. Build the DB2 Archdef member (IBM01) using SCLM. (For complete instructions see SCLM Build.)

26. Promote the DB2 Archdef member (IBM01) from the DEVA group to HOLDA. (For complete instructions see SCLM Promote – Conditional Mode.)

27. Create a Package (Set the package switch to ‘Y’ on the SCLM main menu) add the DB2 archdef member to the package. (For instructions see Steps to Creating a New Package.)


86

28. Build the package in the HOLDA group (Set the package switch to ‘Y’ on the SCLM main menu) using SCLM. (For complete instructions see Package Build Process.)

29. To promote the package from the HOLDA group to the Freeze group. (Set the package switch to ‘Y’ on the SCLM main menu.) To start the SCLM Breeze approval promotion process use SCLM option 5. This will send out the approval to the user groups. (For complete instructions see Package Promote Approval Process.)

30. Once the package has been approved the programmer can:

� Use SCLM option 5 to promote the package to the SCLM Freeze group.

� Or wait for the SCLM Batch Promote Job to run to promote the package to the next group. (For complete instructions see Package Promote Process.)

31. When ready to promote the package to the PRD group, the programmer should set the package switch on the SCLM main menu to ‘Y’. To start the SCLM Breeze approval promotion process use SCLM option 5. This will send out the approval to the user groups. (For complete instructions see Package Promote Approval Process.)

32. Once the package has been approved the programmer can use SCLM option 5 to promote the package to the SCLM PRD group or the programmer can wait for the SCLM Batch Promote Job to run to promote the package to the next group.) (For complete instructions see Package Promote Process.)

Notes:

1. If the only member within SCLM that needs to be changed is the source DB2 program, the programmer does not need to edit the ‘BIND’ member, the ‘LECDEF’ member, or the ‘ARCHDEF’ member. SCLM automatically pulls the correct member from the SCLM hierarchy. If the ‘BIND’ member is in production, SCLM uses the member in production to create the DB2 bind control cards. Then SCLM binds the package in the correct DB2 subsystem.

2. During the promote to the Freeze group you can have SCLM recompile the programs within the package. By placing a ‘2’ in the 4th position of the package name and SCLM will recompile the package contents when promoted to the FREEZE group.

3. If you would like Xpediter to be used during the build or promote process within SCLM set the Xpediter switch on the SCLM main menu to ‘Y’.


87

Steps to Edit an Existing DB2 Member 1. Edit the source member first, the DB2 program.


3. Specify ‘SOURCE’ in the Type. Press Enter. A list of members appears.





8. Edit the BIND member.

Note: If the BIND member does not need to be modified skip to step 15.


10. Specify ‘BIND’ in the Type. Press Enter. A list of members will appear.





15. Edit the LECDEF member.

Note: If the LECDEF member does not need to be modified skip to step 22.


17. Specify ‘LECDEF’ in the Type. Press Enter. A list of members will appear.





88


Note: Steps 15 – 21 might need to be executed several times depending on how many Lecdef types you have. Refer to the SCLM Sample Archdefs Table.

22. Edit the ARCHDEF member.

Note: If the ARCHDEF member does not need to be modified skip to step 29.


24. Specify ‘ARCHDEF’ in the Type. Press Enter. A list of members appears.





29. Build the DB2 Archdef member using SCLM. (For complete instructions see Package Build Process.)

30. Either:

� Create a Package (Set the package switch to ‘Y’ on the SCLM main menu) and add the DB2 archdef member to the package. (For instructions see Steps to Create a New Package.)

� Or Edit the existing package if needed. (For instructions see Steps to Edit an Existing Package in SCLM.)

31. Build the package in the HOLDA group (Set the package switch to ‘Y’ on the SCLM main menu) using SCLM. (For complete instructions see Package Build Process.)

32. To promote the package from the HOLDA group to the Freeze group (Set the package switch to ‘Y’ on the SCLM main menu.) To start the SCLM Breeze approval promotion process use SCLM option 5. This will send out the approval to the user groups. (For complete instructions see Package Promote Approval Process.)

33. Once the package has been approved the programmer can use SCLM option 5 to promote the package to the SCLM Freeze group or the programmer can wait for the SCLM Batch Promote Job to run to promote the package to the next group. (For complete instructions see Package Promote Process.)


89

34. When the programmer is ready to promote the package to the PRD group. The programmer should set the package switch on the SCLM main menu to ‘Y’. To start the SCLM Breeze approval promotion process use SCLM option 5. This will send out the approval to the user groups. (For complete instructions see Package Promote Approval Process.)

35. Once the package has been approved the programmer can use SCLM option 5 to promote the package to the SCLM PRD group or the programmer can wait for the SCLM Batch Promote Job to run to promote the package to the next group. (For complete instructions see Package Promote Process.)

Notes:

1. If the only member within SCLM that needs to be changed is the source DB2 program, the programmer does not need to edit the ‘BIND’ member, the ‘LECDEF’ member, or the ‘ARCHDEF’ member. SCLM automatically pulls the correct member from the SCLM hiearchy. If the ‘BIND’ member is in production, SCLM uses the member in production to create the DB2 bind control cards. Then SCLM binds the package in the correct DB2 subsystem.

2. During the promote to the Freeze group you can have SCLM recompile the programs within the package. By placing a ‘2’ in the 4th position of the package name and SCLM will recompile the package contents when promoted to the FREEZE group.

3. If you would like Xpediter to be used during the build or promote process within SCLM set the Xpediter switch on the SCLM main menu to ‘Y’.


90

Topic 7. SCLM Utilities

SCLM Utilities Menu

Menu Utilities Help ----------------------------------------------------------------------------- SCLM Utilities Menu Option ===> 1 Library View, browse, edit, delete, build or promote SCLM controlled members and update member authorization codes 2 Sublib Mgmt Browse or delete intermediate records and forms 3 Migration Register the contents of a library with SCLM 4 Database Contents Create reports and tailored data sets against SCLM database 5 Architecture Report Create architecture report 6 Export Extract SCLM accounting information 7 Import Incorporate exported data into the hierarchy 8 Audit and Version Display Audit and Version members 9 Delete Group Delete members, accounting records, build maps, intermediate code and records from a group 10 Package Functions View, delete and restore backed-up packages B Breeze Approval Functions T Tools Productivity tools


91

Library Utility (SCLM option 3.1)

� Browse members, accounting records, build maps

� Delete members, accounting records, build maps

� Update authorization codes

� Like ISPF option 3.1

� View from one group or hierarchy

� Member selection list processing

� Omit M from TAM on Select and rank member list data to view languages

Menu SCLM Utilities Help -------------------------------------------------------------------------- SCLM Library Utility - Entry Panel Option ===> blank Display member list E Edit member A Browse accounting record V View member M Browse build map C Build member B Browse member P Promote member D Delete member, acct, bmap U Update authorization code SCLM Library: Project . : SCLMBNK Group . . . DEVA Type . . . . ARCHDEF Member . . . RENECOB (Blank or pattern for member selection list) Select and rank member list data . . TA (T=TEXT, A=ACCT, M=BMAP) Enter "/" to select option / Hierarchy view Process . . 3 1. Execute / Confirm delete 2. Submit / View processing options for Edit 3. View options


92

Menu SCLM Functions Utilities Help ------------------------------------------------------------------------------ Member List : SCLMBNK.DEVA.SOURCE - HIERARCHY VIEW - Member 1 of 11 Command ===> Scroll ===> PAGE A=Account M=Map B=Browse D=Delete E=Edit V=View C=Build P=Promote U=Update Member Status Text Chg Date Chg Time Account Language IBMP00 PRD 98/11/10 11:54:00 PRD CO3B A IBMP01 PRD 98/01/29 08:50:00 PRD CO3B IBMP02 PRD 99/01/29 11:06:00 PRD CO3B IBMP03 DEVA 99/12/23 10:41:00 DEVA CO3B IBMP04 PROD 98/12/23 14:27:00 PRD CO3B IBMP05 DEVA 98/11/09 14:17:00 DEVA CO3B IBMP06 PRD 98/11/10 12:32:00 PRD CO3B IBMP07 DEVA 98/11/19 11:52:00 DEVA CO3B IBMP08 PRD 98/11/06 16:26:00 PRD CO3B *******************************Bottom of Data *****************************

SCLMBNK.PROD.SOURCE(IBMP01): Accounting Record Command ===> Physical Data Set . : SCLMBNK.PRD.SOURCE Accounting Status . : EDITABLE Change Group . . . . : DEVA Change User ID . . : QAG096 Authorization Code . : P Member Version . . : 10 Auth. Code Change . : Language . . . . . : CO3B Translator Version . : Creation Date . . . : 98/04/07 Change Date . . . . : 99/01/29 Creation Time . . . : 13:50:48 Change Time . . . . : 08:50:00 Promote User ID . . : RBSTC Access Key . . . . . : Promote Date . . . : 99/01/29 Build Map Name . . . : Promote Time . . . : 08:52:56 Build Map Type . . . : Predecessor Date . : 99/01/28 Build Map Date . . . : 99/01/29 Predecessor Time . : 07:35:01 Build Map Time . . . : 08:50:00 Enter "/" to select option Display Statistics Number of Change Codes : 1 Number of Includes : 5 Number of Compilation Units : 0 Number of User Entries : 0


93

Migration Utility (SCLM option 3.3)

� Identify new members to SCLM

� Create accounting records for new members

� Use for large number of new members

� Parse members for dependencies and statistics

� For only one member, EDIT and SAVE are equivalent

� Omit language to use the language value from higher accounting record

Menu SCLM Utilities Jobcard Help ______________________________________________________________________________ SCLM Migration Utility - Entry Panel Command ===> Selection criteria: Project . : SCLMBNK Group . . . DEVA Type . . . . SOURCE Member . . . * (Pattern may be used) Member information: Authorization code . . Mode . . . 1 1. Conditional Change code . . . . . . 2. Unconditional Language . . . . . . . CO3B 3. Forced Output control: Ex Sub Process . . 1 1. Execute Messages . . 1 2 1. Terminal 2. Submit Listings . . 1 2 2. Printer 3. Data set Printer . . * 4. None Volume . .


94

Database Utility (SCLM option 3.4)

� Retrieve information from SCLM

� Generate report from the data

�� Search based on selection criteria �� Can use SCLM variables to create a tailored report

@@FLMMBR - Member Name

@@FLMTYP - Type

@@FLMLAN - Language

@@FLMCDT - Change Date

@@FLMCTM - Change Time

@@FLM$IN - Copybooks

@@FLM$CC - Change Code

@@FLMTLL - Total line in member

See SCLM Reference for a complete list of variables.

Menu SCLM Utilities Jobcard Help ----------------------------------------------------------------------------- SCLM Database Contents Utility - Entry Panel Command ===> Selection criteria: (Pattern may be used for Group, Type or Member) Project . . : SCLMBNK Group . . . . DEVA . . . HOLDA . . . FREEZE . . . PRD . . . . . . Type . . . . * Member . . . * Enter "/" to select option / Change additional selection criteria / Change customization parameters Output control: Ex Sub Process . . 1 1. Execute Messages . . 1 2 1. Terminal 2. Submit Report . . . 1 2 2. Printer Tailored . . 3 2 3. Data set Printer . . * 4. None Volume . .


95

Database Utility (option 3.4 Additional Selection Criteria)

Tailored Report Customization

Menu ________________________________________________________ SCLM Database Contents - Additional Selection Criteria Command ===> Selection criteria: (Patterns may be used) Authorization code . . * Data type . . 1 1. Account Change code . . . . . . 123456 2. Build map Change group . . . . . * 3. Both Change user id . . . . * Language . . . . . . . * Enter "/" to select option / First occurrence only Hierarchy search information: Architecture Control . . 3 1. In Scope . . 3 1. Normal 2. Out 2. Subunit 3. Not used 3. Extended Architecture Group . . . Architecture Type . . . Architecture Member . .

Menu ________________________________________________________________ SCLM Database Contents - Customization Parameters Command ===> Report name . . . . . . STATISTICS REPORT Report line format . . . @@FLMMBR @@FLM$CC Enter "/" to select option / Page headers / Show totals


96

Output from DBUTIL - Messages Output from DBUTIL – Database Contents Report

FLM69010 - INVOKING DATABASE CONTENTS UTILITY FLM69025 - THE TAILORED OUTPUT WILL APPEAR IN RSFORD.DBUTIL.CMDS45 FLM61007 - DATABASE CONTENTS UTILITY INITIATED - 13:04:18 ON 2001/08/31

**************************************************************************** PAGE 2 DATABASE CONTENTS REPORT ******************************* TYPE: ARCHDEF ************************** MEMBER GROUP 1 GROUP 2 GROUP 3 GROUP 4 GROUP 5 GROUP 6 ------- ------- ------- -------- ------- ------- ------- IBM02 DEVA ******************************* TYPE: PACKAGE ************************** IBM002 DEVA ******************************* TYPE: SOURCE ************************** IBM02 DEVA


97

Audit and Version Utility (SCLM option 3.8)

� View audit information

� Recover an old version of: source, copybook, etc.

� Retrieve to a sequential dataset or back into an SCLM PDS

� Delete Version Audit information

� Compare 2 prior version of a member

� View a member

� View history of a member

� Number of versions kept (20) controlled by project definition

� See page 16 for a list of types and groups that have versions

Menu SCLM Utilities Help ------------------------------------------------------------------------------ SCLM Audit and Version Utility - Entry Panel Command ===> More: + Option . . 1 1. Versioning and Audit Tracking 2. Versioning only SCLM Library: Project . : SCLMTFS Alternate - SCLMTFS Group . . . DEVA Type . . . . SOURCE Member . . . (Member name or blank for member list) Selection date range: Date from . . (Blank or start date for member list) Date to . . . (Blank or end date for member list) Non-SCLM controlled retrieve and compare output data sets: Retrieve/New . . 'RF30.TEST.SOURCE' Retrieve/Old . . Listing . . . . SCLM retrieve group and type: To Group . . . Authorization code . . To Type . . . (Defaults to auth code from audited member)


98

Output Audit and Version Utility

This panel shows all the audit information for a particular member within SCLM. You can select to display the audit information (A), retrieve a prior version of a member (R), compare 2 members (C), delete a audit and version member (D), view the history changes for a member (H), or view a particular version member (V).

Menu SCLM Utilities Help ------------------------------------------------------------------------------- SCLM - Version Selection Row 1 to 7 of 14 Option ===> Scroll ===> PAGE Project . . . : SCLMTFS Alternate - SCLMTFS Type . . . . . : SOURCE Retrieve/New . : RF30.TEST.SOURCE Retrieve/Old . : Listing . . . : Line Commands: A Audit Information C Compare D Delete H History R Retrieve V View Action Action Action Action S Member Group Reason Date Time Userid Result V Status - -------- -------- -------- ---------- -------- -------- -------- - -------- RENETEST DEVA STORE 2003/01/30 04:40:08 RF30 COMPLETE * RENETEST DEVA STORE 2003/01/28 20:43:04 TESTI1 COMPLETE * RENETEST DEVA LOCK 2003/01/28 20:42:52 TESTI1 COMPLETE TESTACF2 DEVA STORE 2003/01/30 23:14:31 RF30 COMPLETE * TESTACF2 DEVA LOCK 2003/01/30 23:14:22 RF30 COMPLETE TESTACF2 DEVA DELETE 2003/01/30 23:14:18 RF30 COMPLETE TESTACF2 DEVA STORE 2003/01/30 23:13:20 RF30 COMPLETE *


99

Version History Report Results

VIEW QAG096.D730759.T74443.VERTEMP Columns 00001 00072 Command ===> Scroll ===> CSR ****** ***************************** Top of Data ****************************** 000001 Version History 000002 Changes since, but not including Version 1 000003 000004 CURRENT 0 01/10/02 20:37:06.90 QAG096 000005 VERSION 1 01/10/02 20:07:54.58 QAG096 000006 000007 |--Key--| |----------Description----------| 000008 Ixxx Inserted into Version xxx 000009 Dxxx Deleted from Version xxx 000010 (blank) Unchanged since selected version 000011 000012 |--Key--| |------------------------------------Source------------------- 000013 000100 IDENTIFICATION DIVISION. 000014 000200*------- ------- ----- --- - - - - - - --- ----- ------- 000015 000300* XXXXXXX DEMO 000016 000400*------- ------- ----- --- - - - - - - --- ----- ------- 000017 000500 PROGRAM-ID. IBM001. 000018 000600 AUTHOR. DOUG BROWN. ............................................................................... 000219 020100 DISPLAY ERROR-LINE-BLANK. 000220 020200 DISPLAY ERROR-LINE2. 000221 020300 DISPLAY ERROR-LINE-BLANK. 000222 020400 DISPLAY ERROR-LINE3. 000223 020500 DISPLAY ERROR-LINE4. 000224 020600 DISPLAY ERROR-LINE-DASHES. 000225 020700 DISPLAY ERROR-LINE-BLANK. 000226 I0 019800 DISPLAY ERROR-LINE-DASHES. 000227 I0 019900 DISPLAY ERROR-LINE-BLANK. 000228 I0 020000 DISPLAY ERROR-LINE1. 000229 I0 020100 DISPLAY ERROR-LINE-BLANK. 000230 I0 020200 DISPLAY ERROR-LINE2. 000231 I0 020300 DISPLAY ERROR-LINE-BLANK. 000232 I0 020400 DISPLAY ERROR-LINE3. 000233 I0 020500 DISPLAY ERROR-LINE4. 000234 I0 020600 DISPLAY ERROR-LINE-DASHES. 000235 I0 020700 DISPLAY ERROR-LINE-BLANK. 000236 020800 STOP RUN. ****** **************************** Bottom of Data ****************************


100

Delete Group Utility (SCLM option 3.9)

� Delete multiple components from an SCLM group.

� Determined by ACF2 authority.

� Pattern may not be used for member

� Can not use Delete Group screen in FREEZE or PRD groups.

� Always use report mode for a dry run before actually deleting.

� Delete Flag:

1. Build Map – Deletes only the build map for a member.

2. Account – Deletes both the account record and the build map for a member.

3. Text – Deletes the member from SCLM PDS, Build Map, and Account record.

4. Output – Deletes only the output created from an SCLM member.

Menu SCLM Utilities Jobcard Help ______________________________________________________________________________ SCLM Delete Group Utility - Entry Panel Command ===> Delete Group Input: Project . : SCLMBNK Group . . . HOLDA Type . . . . * (Pattern may be used) Member . . . IBM01 (Pattern may be used) Delete Flag . . 3 1. Build map Delete Mode . . 1 1. Execute 2. Account 2. Report 3. Text 4. Output Output control: Ex Sub Process . . . . 1 1. Execute Messages . . 1 2 1. Terminal 2. Submit Report . . . 1 2 2. Printer Listings . . 1 2 3. Data set Printer . . . . * 4. None Volume . . . .


101

DELGROUP.MSG

FLM32504 - INVOKING DELETE GROUP UTILITY FLM85000 - DELETE GROUP UTILITY INITIATED - 11:02:32 ON 2001/08/31. FLM85107 - 4 ACCOUNTING RECORDS WERE DELETED. FLM85109 - 2 BUILD MAP RECORDS WERE DELETED. FLM85110 - 0 INTERMEDIATE RECORDS WERE DELETED. *************************************************************************

*********************************************************************** ** SOFTWARE CONFIGURATION AND LIBRARY MANAGER (SCLM) ** DELETE GROUP REPORT ** 2001/08/31 11:02:33 ** ** PROJECT: SCLM ** ALTERNATE: SCLM ** GROUP: HOLDA ** TYPE: * ** MEMBER: IBM* ** FLAG: TEXT ** MODE: EXECUTE ** ************************************************************************* MEMBERS: PAGE: 1 VERIFY COMPLETION GROUP TYPE MEMBER STATUS STATUS -------- -------- -------- ------ ------------- HOLDA ARCHDEF IBM01 PASSED PASSED *HOLDA LINKLIB IBM01 PASSED PASSED *HOLDA OBJ IBM01 PASSED PASSED HOLDA SOURCE IBM01 PASSED PASSED BUILD MAPS: PAGE: 2 VERIFY COMPLETION GROUP TYPE MEMBER STATUS STATUS -------- -------- -------- ------ ------------- HOLDA ARCHDEF IBM01 PASSED PASSED HOLDA SOURCE IBM01 PASSED PASSED ADA INTERMEDIATE CODE: PAGE: 3 VERIFY COMPLETION GROUP CU QUAL CU NAME CU TYPE STATUS STATUS -------- -------- ---------------------------- ------- ------ ------------- ********************* NO RECORDS PROCESSED ************************************ FLM85299 - DELETE GROUP UTILITY COMPLETED - 11:02:33 ON 2001/08/31. FLM09008 - RETURN CODE = 0


102

Topic 8. SCLM Customized Tools for Northern Trust

SCLM Productivity Tools (SCLM option 3.T)

SCLM Productivity Tools Option ===> 1 Copybook Search Search for copybooks in programs 2 Subroutine Search Search for subroutines in archdefs

Menu Utilities Help ---------------------------------------------------------------------------- SCLM Utilities Menu Option ===> 1 Library View, browse, edit, delete, build or promote SCLM controlled members and update member authorization codes 2 Sublib Mgmt Browse or delete intermediate records and forms 3 Migration Register the contents of a library with SCLM 4 Database Contents Create reports and tailored data sets against SCLM database 5 Architecture Report Create architecture report 6 Export Extract SCLM accounting information 7 Import Incorporate exported data into the hierarchy 8 Audit and Version Display Audit and Version members 9 Delete Group Delete members, accounting records, build maps, intermediate code and records from a group 10 Package Functions View, delete and restore backed-up packages B Breeze SCLM Approval Functions T Tools Productivity Tools


103

Copybook Search Utility (SCLM option 3.T.1)

� Searches up hierarchy from specified group, or just that group.

� Returns list of all source that reference a given copybook.

� Can create High Level archdef which will include all members referenced by the copybook. This archdef can be used to re-build and promote all members related to the copybook change.

� Works in foreground or background.

Copybook Search Results

Groups to be searched: DEVA, HOLDA, UAT, PRD Request is being processed... Please Wait... FLM87115 - DBUTIL SUCCEEDED AT 16:53:59, CODE: 0 FLM87115 - DBUTIL SUCCEEDED AT 17:02:07, CODE: 0 Copybook VICWGSSP is in the following programs: CLASS00 CLASS01 CLASS02 CLASS03 Elapsed time: 3213.955040

Search for Copybooks in Programs Command ===> Selection Criteria: Project . . . SCLMBNK Group . . . . DEVA Copybook . . VICWGSSP Enter "/" to select search option / Search up the Hierarchy To create high level archdef fill in the fields below: High Level Archdef . . . . SCLM Dev Group . . . . . . Output Control: Process 1 1. Execute 2. Submit


104

Subroutine Search Utility (SCLM option 3.T.2)

� Search in source code archdefs for a specific subroutine

� Optionally create an HL archdef referencing all source code archdefs containing that subroutine

Search For Subroutine in Archdefs Command ===> Selection Criteria: Project . . . SCLMBNK Group . . . . DEVA Subroutine . IBM01 Enter "/" to select search option / Search up the Hierarchy To create high level archdef fill in the fields below: High Level Archdef . . . . SCLM Dev Group . . . . . . Output Control: Process 1 1. Execute 2. Submit


105

Breeze Approval Functions (SCLM option 3.B) The Breeze Approval Functions main menu is used for selecting options for maintenance, reporting, and voting on package approval.

Breeze Approval Functions Option ===> Setup Utilities 1 Approvers Add, Delete, Update or Show Approvers 2 Approver Groups Add, Delete or Show Approver Groups and Update Quorum of Approver Groups 3 Approver Group Approvers Add, Delete or Show Approvers of Approver Groups 4 Junction Records Tie SCLM Members to Approver Groups 5 Watch Records Tie SCLM Members to Approver Watch Groups Package Utilities 6 Package Report Report on package contents 7 Cross Reference Report Display a cross reference list of users, packages and approver groups 8 Package Status Clear or Reset the status of a package and Delete (purge) packages 9 Package Approval Display packages for your approval 10 Package Voting Utility Approve or Veto a package


106

Approver Maintenance (SCLM option 3.B.1)

The Breeze Approver Maintenance panel is used by the SCLM Administrators to add, update, and delete, the userid information for an approver. All users can perform a list or report on the information for one or more approvers.

For a list, fill in the user's TSO ID, enter L in the action field and press Enter. The fields on the screen will be filled in.

For a report, fill in the user's TSO ID, enter R in the action field and press Enter. (To report all user IDs, enter * in the userid field). The report will be displayed.

For an update, perform a list first. Then change the fields you want, enter U in the action field and press Enter. A log file will be displayed indicating the results of the update.

For an add, fill in the user's TSO ID, name, phone number, etc. as needed, enter A in the action field and press Enter. A log file will be displayed indicting the results of the add.

For a delete, fill in the user's TSO ID and press Enter. A log file will be displayed indicting the results of the delete.

Approver Maintenance Command ===> Perform Process = A (Add) U (Update) D (Delete) L (List) R (Report) Approver's User ID = RF30 Name = Phone = ( ) - Email address 1 = Email address 2 = Email address 3 = TSOSend = Y Y/N Default 'Y' Output report will be generated to 'RF30.CIGRPT'


107

Approver Group Maintenance (SCLM option 3.B.2)

The Approver Group Maintenance panel will display the approver groups as stored in the Breeze database. This panel will allow an administrator to add an approver group with an associated quorum (total number of users needed to vote on a package). Fill in the approver group, quorum number (maximum 99), enter A in the action field, and press Enter. A log file will be displayed indicating the results of the add.

This panel can also be used to List and Update the quorum for an existing approver group and to delete and report on an approver group.

To List a quorum, enter an approver group and L in the action field. When you press Enter the quorum will be displayed.

To update a quorum, perform a List first to retrieve the quorum. Change the quorum as needed, enter U in the action field and press Enter. A log file will display the results of the add.

To report on an approver group, enter the approver group and R in the action field. When you press Enter the report will be displayed. To report on all approver groups, enter * in the approver group field and R in the action field.

Approver Group Maintenance Command ===> Perform Process = A (Add) U (Update) D (Delete) L (List) R (Report) Approver Group = Quorum = 1 Default = 1 ... Output report will be generated to 'RF30.CIGRPT'


108

Approver Group Approver Maintenance (SCLM option 3.B.3)

The Approver Group Approver Maintenance panel will allow an administrator to add, update, and delete approvers for an existing approver group. Anyone can also List or Report on the information for an approver group.

For an add, enter all needed information on the screen, enter A in the action field, and press Enter. A log file will display the results of the add.

For a list, enter an approver group and an approver. After pressing Enter, the screen will be filled in for a list.

For a report, enter a approver group and approver. Enter * in either field to report all records.

For a report, the report will be displayed after pressing Enter.

For an update perform a List first. Then change the fields as needed, enter U in the action field and press Enter. A log file will be displayed indicating the results of the update.

For a delete, enter the approver group and approver, D in the action field, and press Enter. A log file will be displayed with the results of the update.

Approver Group Approver Maintenance Command ===> Perform Process = A (Add) U (Update) D (Delete) L (List) R(Report) Approver Group = Approver = RF30 Required = N Y/N Package Approval Required Approve Only Once = N Y/N Retain Approval at all Groups Notify Only = N Y/N Notification Only ... Output report will be generated to 'RF30.CIGRPT'


109

Inventory Junction Record Maintenance (SCLM option 3.B.4)

The Inventory Junction Record Maintenance panel will allow an administrator to manually add, delete, or report inventory junction records. These records tie an approver group to an inventory (SCLM) member. After filling in a process (A, D, or R), the Approver Group, Member and the other fields if the default values need to be changed, press Enter. A log file will be displayed indicating the results of the add or delete. If a report was requested the report will be displayed.

For a report only the approver group is used as input. Except for the approver group and member, the input fields have default values, but can be changed. You can specify wildcards (*) for all fields, except that approver group must be specified for an add. You can specify * on its own or you can specify a partial value followed by * (for example, DEV* to match all development groups).

Caution: When using wildcards with the delete function be careful not to delete more records than you want.

Inventory Junction Record Maintenance Command ===> Perform Process = A (Add) D (Delete) R(Report) Approver Group = Member = Project = SCLMBNK Alt Project = SCLMBNK Group = FREEZE Type = PACKAGE Language = ARCHDEF ... Output will be generated to 'RF30.CIGRPT'


110

Inventory Watch Record Maintenance (SCLM option 3.B.5)

The Inventory Watch Record Maintenance panel will allow an administrator to manually add, delete, update or report inventory watch records. These records tie an approver group to a inventory (SCLM) member for "watching". After filling in the process (A, D, U, or R), the Approver Group, Member and the other fields, if the default values need to be changed, press ENTER. A log file will be displayed indicating the results of the add, delete, or update. If a report was requested, the report will be displayed. For a report only use the member as input.

Except for the approver group and member, the input fields have default values, but can be changed. You can specify wildcards (*) for all fields, except that approver group must be specified for an add. You can specify * on its own or you can specify a partial value followed by * (for example, DEV* to match all development groups).

Caution: When using wildcards with the delete function be careful not to delete more records than you want.

Inventory Watch Record Maintenance Command ===> Perform Process = A (Add) D (Delete) U (Update) R(Report) (Update: change the Approver Group of an existing record) Approver Group = Member = Project = SCLMBNK Alt Project = SCLMBNK Group = DEVA Type = PACKAGE Language = ARCHDEF ... Output will be generated to 'RF30.CIGRPT'


111

Package Report (SCLM option 3.B.6)

The Package Report panel will allow anyone to view the file information for a Breeze Package ID. After filling in the Package ID, and if desired a specific Status, Approver, or Option. Press Enter to get a display of the report file (dataset name referenced at the bottom of this panel) created by the reporting process which was just executed.

After reviewing the report file, press PF3 to return to the report panel where you can enter another Package ID or press PF3 to return to the previous menu.

Package Report Command ===> Package ID = * * For All Packages The following can be entered or left blank to default to all... Status = Approved,Pending,Vetoed,Promoted,Updated Approver = Project = SCLMBNK Group = Options = ALL Contents,Status,Notes,Votes,Log,All ... Output report will be generated to 'RF30.CIGRPT'


112

Cross Reference Report (SCLM option 3.B.7)

The Cross Reference Report panel will allow anyone to view a cross reference list of approver user ids, package ids, and approver groups. After optionally filling in the User ID and Package ID (leaving a field blank defaults to all), press Enter and get a display of the report file (dataset name referenced at the bottom of this panel) created by the reporting process which was just executed.

After reviewing the report file, press PF3 to return to the panel where you can enter the next User ID and/or Package ID, or press PF3 to return to the previous menu.

Cross Reference Report Option ===> The following can be entered or left blank to default to all... User ID = RF30 Package ID = ... Output report will be generated to 'RF30.CIGRPT'


113

Package Status (SCLM option 3.B.8)

Three actions can be performed on a package by an administrator:

� Clear: Removes all approval and collision data for a package and clears the package status. Used to either restart the approval process for a package or allow it to be overlaid during a promote.

� Reset: Restores a package status to its previous value of either pending or approved. Can be used to change a package status from "Incomplete" to "Approved" following a promote failure.

� Purge: Removes all information associated with a package from the Breeze database.

After filling in the Process (C, P, or R), Package ID and optionally the Project, Alt Project and Group, press Enter. A log file will be displayed indicating the result of the process.

Package Status Command ===> Perform Process = C (Clear) P (Purge) R (Reset) Package ID = Project = SCLMBNK Alt Project = SCLMBNK Group = UAT Type = PACKAGE Clear : Removes all approval and collision data for a package and clears the package status. Used to either restart the approval process for a package or allow it to be overlaid during a promote. Reset : Restores a package status to its previous value of either pending or approved. Can be used to change a package status from "INCOMPLETE" to "APPROVED" following a promote failure. Purge : Removes all information associated with a package from the Breeze database


114

Package Approval (SCLM option 3.B.9)

The Package Approval panel presents a list of packages requiring your approval. Enter V in the action area to select a package to vote on. Press Enter to be transferred to the package voting utility where the fields will be filled in based upon the entries of the package in the list that you selected. Press PF3 to return to the previous menu.

Package Approval Command ===> SCROLL ===> PAGE Line Commands : V - Vote Package Project Alternat Group To Group Type Decision -------- -------- -------- -------- -------- -------- -------- ******************************* Bottom of data ********************************


115

Package Voting Utility (SCLM option 3.B.10)

The Package Voting Utility panel will allow authorized approver user ids to cast a ballot associated with a Breeze package ID. After filling in the Package ID and Vote option (a veto requires notes to be entered), press ENTER to get a display of the log file created by the voting process which was just executed.

After reviewing the log file, press PF3 to return to the cast ballot panel where you can enter the next package ID or press PF3 to return to the previous menu.

Package Voting Utility Option ===> Package ID = Project = SCLMBNK Alt Project = SCLMBNK Group = UAT Type = PACKAGE Perform Vote = A (Approve) V (Veto) Note 1 = Note 2 = Note 3 = Note 4 = Note 5 =


116

Topic 9. Viewing and Voting on Packages Using the

Breeze Web Interface

An email will be sent to all potential Approvers of a package. The email contains a link to the Web page that displays the Breeze interface. To start using the Breeze Web interface, you can either click on the link in the e-mail, or ask your Breeze Administrator for the Web address (URL) of the interface, and enter the address in your Web browser. The Web address of the Breeze Web interface has the following format:

http://IBM3.NTRS.com:2002/brsclm.html

This Web page downloads a Java applet that displays inside your Web browser window. When the Breeze Web interface has loaded, it displays a login prompt:

To login, type your host TSO user ID and password, then click on OK.


117

Breeze Main Panel After you login, the Breeze Web interface displays the main panel:

The main panel is divided into several areas: In-box Lets you determine which packages are displayed in the list,

according to package status and whether you are an approver for the package.

Filter Limits the packages displayed in the list to those that meet the criteria you specify.

List Displays a list of packages, determined by the in-box and any filter that you have set. To view or vote on a package, you select the package from this list.

Information Displays information about the package that you select from the list.

Status Describes communication between the Breeze Web interface and the Breeze host.


118

Selecting a Package for Viewing or Voting Before you can view or vote on a package, you need to select it by clicking on the package ID or its description in the list on the main panel. Before you can do this, you need to display the package in the list. To determine which packages are displayed in the list, click an in-box item (at the top left of the main panel):

Requiring my approval Displays packages that require your approval; that is, the packages in PENDING status for which you are an Approver. When you login, this is the default.

Emergency Packages Displays only the emergency packages that require your approval.

Standard Packages Displays only the standard packages that require your approval.

Packages by status Displays all packages, regardless of their status or approvers.

Pending Displays packages that require approval, and for which voting is still in progress.

Vetoed Displays packages that have been voted on and vetoed.

Approved Displays packages that have been voted on and approved.

Promoted Displays packages that have been successfully promoted.

Promotion failed Displays packages that were approved but, for some reason (such as a problem in SCLM), have not been promoted.

When the list displays the package you want, select the package by clicking on the list.


119

To vote on a package for which you are an Approver, you must select the package from the list displayed when you click on Requiring my approval or one of its sub-items. This activates the Approve and Veto buttons, allowing you to cast a vote. If you select the same package from the “Packages by status” list, then these buttons remain disabled.

Filtering Packages from the List

You can limit the list to display packages that meet certain criteria:

Criteria Value Package ID 1 to 16 character SCLM package ID

Promotion Window The timeframe in which the package can be promoted

Build User ID User ID of the person who built the package

Promote User ID User ID of the person who promoted the package

Promote Date Date package was promoted

Last Update User ID User ID of the person who made the last update to the package

Last Update Date Date the package was last updated

Voting on a Package

You can vote on a package if all of these conditions are true:

� You are an Approver for the package. Before you can be an approver, your Breeze Administrator must define the necessary Breeze records on the host. For information about defining these records, see the Breeze Planning and Administration Guide.

� The package is still in pending status. That is, when you click “Requiring my approval” in the in-box, the package appears in the package list.

� You have not already voted on the package.

� You have selected “Requiring my approval” (or one of its sub-items, “Standard Packages” or “Emergency Packages”) in the in-box.


120

To vote on a package:

1. Click on the package in the list that you want to vote on.

2. To cast a vote for approval, click the Approve button. To cast a vote against approval, click the Veto button. (If any of the conditions listed above are not true, then these buttons are disabled, and you will not be able to cast a vote.)

3. A voting dialog appears, similar to the one shown below (depending on whether you clicked on Approve or Veto).

This is the first in a sequence of voting dialogs. Each of these panels has a Prior button and a Cancel button. To step back through the sequence, click on Prior. To return to the main panel without voting, click on Cancel. (On the first dialog in the sequence, shown above, both Prior and Cancel return you to the main panel without voting.)

To leave a note explaining your vote to other users, select Add Notes to the Package.

To proceed, click Next.

4. If you chose not to add notes, go to the next step. If you chose to add notes, then a dialog is displayed with a text box where you can enter your notes.

You can enter up to 480 characters. To insert a line break in your notes, press Enter.

When you have finished entering your notes, click on Next to proceed.


121

5. The final voting dialog is displayed. To cast you vote, click on Submit.

How Voting Results in Approved or Vetoed Status

Here is how a package in pending status reaches either approved status or vetoed status:

Approved status

Every approver group for the package approves the package. That is, in every approver group:

� Every required approver has voted (either “for” or “against”; a package can be approved even if one or more required approvers vote against it).

� The number of votes is equal to or greater than the quorum (minimum number of votes required for the approver group).

� There are a majority of “for” votes.

The package can now be promoted.


122

Vetoed status

One approver group for the package vetoes the package. That is, in one of the approver groups:

� Every required approver has voted (either “for” or “against”; a package can be vetoed even if one or more required approvers vote for it).

� The number of votes is equal to or greater than the quorum (minimum number of votes required for the approver group).

� There are at least as many “against” votes as “for” votes.

If one approver group vetoes a package, then Breeze immediately sets the package to vetoed status, even if required approvers in other approver groups have not yet voted.

It is easier for a package to be vetoed than approved: an equal number of “for” and “against” votes in one approver group is enough to veto a package For example, if there are five approver groups for a package, and four of the approver groups approve the package, but in the fifth approver group, there is an equal number of “for” and “against” votes, then the package is vetoed.


123

Viewing Package Information

To view detailed information about a package:

1. Select the package you want from the package list.

2. Click one of the tabs in the information area of the main panel. These tabs are described under the headings that follow.

Summary

The Summary tab displays various information about the selected package.


124

Description If a developer used the SCLM promote function in foreground

to request promotion for this package, then this is the description that the developer entered on the Breeze pop-up window. Otherwise, if the developer used the SCLM promote service in a batch job, then this is the default description supplied by Breeze.

Type Package type: standard or emergency.

Status Current package status.

Last cast/pverify User ID, time and date of the most recent invocation of the Breeze “promote verify” user exit for this package. (That is, who last used the SCLM promote function for this package, and when they used it.)

Last promote User ID, time and date of the most recent successful promotion of this package (as recorded by the Breeze “promote purge” user exit).

Next promote date start/end

If the package reaches approved status between these two dates, then the package can be promoted. Otherwise, the package cannot be promoted, even if it is approved.

Package member Package member details. The “to” group is the SCLM project group to which the package will be promoted.

Collisions Indicates whether or not the current package is in collision with any other packages.


125

Contents

The Contents tab lists the names and inventory locations of the members in the selected package. The tab lists each member at its source inventory location (the SCLM project group where the member is to be promoted from) and also at its target inventory location (the SCLM project group where the member will be promoted to).

To view more detailed information about a member, click the entry for the member in the Contents tab. A dialog displays with the following choices, each of which opens a new browser window displaying the selected information: Browse: Displays the contents of the member.

Changes: Displays a line-by-line comparison of the new (source) and old (target) members.

Audit: Displays audit information for the member.


126

Log

The Log tab displays a history of the actions performed on a package.

For each action, the log displays the date and time, the return code, and the user ID that performed the action. If a package has previously been promoted, then the package inherits the existing log, and the log accumulates as the package is promoted up the hierarchy.


127

Collisions

The Collisions tab contains detailed collision information about the current package, including which members are causing the collision. The collision may be current or historic, depending on the status and location of the package.


128

Ballot Box

The Ballot Box tab shows the details of the current voting status:

� Which approver groups are responsible for voting on the selected package.

� Which approvers are in each approver group.

� Who has voted.

� How and when those approvers voted.

� Whether or not a quorum has been reached.


129

Notes

The Notes tab displays any notes that have been added by Approvers who have voted on the package.


130

END OF DOCUMENT

This is the last page of this document.

Documents

SCLM Education Manual