SDM-DesignTracker 5.0 User Guide - MKS

SDM-DesignTracker 5.0 

User Guide

From the MKS Software Development Management Library 

Manual SDM-DesignTracker 5.0 User Guide 

Document ID DTU5.0991015 

Software SDM-DesignTracker 5.0 

Notice 

The information in this manual is subject to change without notice. 

Mortice Kern Systems International SRL, its parent company and affiliates (MKS) make no warranty 

of any kind with regard to this material, including, but not limited to the implied warranties of 

merchant ability, performance, or fitness for a particular purpose. MKS shall not be liable for errors 

contained herein, or for any direct, incidental, or consequential damages resulting from the use of this 

material. 

Copyright 1999, Mortice Kern Systems International SRL. All rights reserved. No part of this 

publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated 

into any language in any form by any means, without written permission from Mortice Kern Systems 

International SRL. 

Printed in the Canada, October, 1999. 

All MKS products are trademarks or registered trademarks of one of the MKS group of companies. 

Other brand and product names are trademarks or registered trademarks of their respective holders. 

Corporate Headquarters 

Mortice Kern Systems Inc. 

185 Columbia St. W. 

Waterloo, Ontario 

Canada N2L 5Z5 

Tel: +1 519 884 2251 

Fax: +1 519 884 8861 

North American Sales: 1 800 265 2797 

E-mail: info@mks.com 

MKS/DataFocus 

12450 Fair Lakes Circle 

Suite 400 

Fairfax, Virginia 22033 

U.S.A. 

Tel: +1 703 803 3343 

Fax: +1 703 803 3344 

E-mail: nutcracker@mks.com 

MKS France 

11C Quai Conti 

78430 Louveciennes 

France 

Tel: +331 3082 2762 

Fax: +331 3082 7278 

E-mail: france@mks.com 

Mortice Kern Systems US Inc. 

2500 S. Highland Av. 

Suite 200 

Lombard, Illinois 60148 

U.S.A 

Tel: +1 630 495-2108 

Fax: +1 630 495-3591 

E-mail: sdminfo@mks.com 

MKS (UK) Ltd 

Third Floor, Duke’s Court 

Duke Street, Woking 

Surrey 

GU21 5BH United Kingdom 

Tel: +44 1483 733 900 

Fax: +44 1483 733 901 

E-mail: uk@mks.com 

Mortice Kern Systems US Inc. 

9020-I Capital of Texas Highway 

North 

Great Hills Corporate Center 

Suite 335 

Austin, Texas 78759 

U.S.A. 

Tel: +1 512 342-2220 

Fax: +1 512 342-2939 

E-mail: austin@mks.com 

MKS Germany 

Martinstraße 42-44 

D-73728 Esslingen 

Deutschland 

Tel: +49 711 351775 0 

Fax: +49 711 351775 11 

E-mail: info@mks.de 

MKS Japan 

Kounike Building 4F 

2-5-7 Minamisuna 

Koto-Ku, Tokyo 

Japan 

E-mail: japan@mks.com 

Please visit our web site at http://www.mks.com/ for up-to-date postal and telephone information.

Contents 

CHAPTER 1 BEFORE YOU BEGIN 1 

Who Should Read This Book.....................................................................................................1 

What to Know Before Using This Product.................................................................................1 

Document Conventions ..............................................................................................................2 

Installation Requirements...........................................................................................................2 

MKS Product Support................................................................................................................3 

Telephone ....................................................................................................................3 

MKS Online.................................................................................................................3 

Facsimile......................................................................................................................3 

How Does Product Support Work?..............................................................................4 

CHAPTER 2 GETTING STARTED 7 

What is SDM-DesignTracker? ...................................................................................................7 

What’s Inside .............................................................................................................................8 

Starting SDM-DesignTracker.....................................................................................................9 

What’s on the SDM-DesignTracker Main Menu .......................................................................9 

What’s New in This Release ....................................................................................................11 

New Options on the Main Menu................................................................................11 

New Options on the Setup Menu ...............................................................................13 

Work With Products Enhancements ..........................................................................14 

Integrated File System (IFS) Management Enhancements.........................................17 

CHAPTER 3 SETUP TASKS 19 

Overview..................................................................................................................................19 

Working With Service Request and Design Request Type Codes ...........................................21 

Working With Service Request and Design Request Status Codes..........................................22 

Working With Priority Codes...................................................................................................23 

Working With Project Creation Rules......................................................................................25 

Working With Systems.............................................................................................................26 

Working With Environment Status Code Settings ...................................................................28 

Working With Companies, Divisions, and Departments..........................................................29 

Working With Cost Centers .....................................................................................................32 

Working With Products and Components................................................................................34 

Working With Components .......................................................................................37 

Working With Product Versions ..............................................................................................39 

Working with Releases ..............................................................................................42 

Working With From Environments............................................................................45 

Working With Approval Users ..................................................................................48 

Working With Users.................................................................................................................49 

Work With Users Task Variations .............................................................................51 

CONTENTS • I

II • SDM-DESIGNTRACKER 5.0 USER GUIDE 

Working With Resources ........................................................................................................ 53 

Working With Approval Users................................................................................................ 54 

Changing System Control Settings .......................................................................................... 56 

Release Setup Options............................................................................................................. 57 

Working With Release Types ................................................................................... 57 

Working With Release Status Types......................................................................... 58 

Working With Media Types...................................................................................... 59 

Working With System Types .................................................................................... 60 

Working With Countries ........................................................................................... 61 

Working With Customers.......................................................................................... 62 

Working With Customer Types ................................................................................ 63 

CHAPTER 4 WORKING WITH SERVICE REQUESTS AND DESIGN REQUESTS 65 

Overview ................................................................................................................................. 65 

Subsetting Service Requests.................................................................................................... 65 

Subset Service Requests Task Variations.................................................................. 67 

Creating a Service Request......................................................................................................68 

Create Service Request Task Variations ................................................................... 69 

Approving Service Requests ................................................................................................... 70 

Attaching SDM-SupportCenter Calls to a Service Request..................................................... 72 

Subsetting Design Requests..................................................................................................... 73 

Subset Design Requests Task Variations .................................................................. 74 

Creating a Design Request ...................................................................................................... 75 

Create Design Request Task Variations.................................................................... 77 

Bulletin Board ......................................................................................................................... 78 

Attaching SDM-SupportCenter Calls to a Design Request ..................................................... 79 

Attaching Service Requests to Design Requests...................................................................... 80 

CHAPTER 5 SDM-IMPLEMENTER INTERFACE 81 

Overview ................................................................................................................................. 81 

Working With Entities - Check Out From SDM-DesignTracker ............................................ 82 

Building the Entity List in SDM-DesignTracker....................................................... 83 

Working With Entities - Creating an Entity List ..................................................................... 83 

SDM-DesignTracker to SDM-Implementer.............................................................. 85 

SDM-Implementer to SDM-DesignTracker.............................................................. 85 

Using Hawkeye/Pathfinder for Entity Selection........................................................ 86 

Working With Entities - Adding Related Entities ................................................................... 88 

Add Related Entities Task Variations ....................................................................... 88 

Working With Entities - Ready for Check Out........................................................................ 89 

Ready for Checkout Task Variations ........................................................................ 89 

Creating an SDM-Implementer Project in SDM-DesignTracker............................................. 90 

Work With Project Tasks Task Variations................................................................ 90 

Working With Design Request Entities................................................................................... 91 

Using Release Control............................................................................................................. 92 

Release Control Development Scenario.................................................................... 93 

Setting Up for Release Control ................................................................................. 94 

Working With Products and Versions....................................................................... 95 

Understanding the Software Release Process Configuration..................................... 96 

Working With Release Types ................................................................................... 96 

Working With the Release Status.............................................................................. 99

CHAPTER 6 SDM-DESIGNTRACKER COMMAND INTERFACE 105 

Overview................................................................................................................................105 

Creating Design Requests (DTCRTDR) ................................................................................106 

Changing Design Requests (DTCHGDR) ..............................................................................111 

Deleting Design Requests (DTDLTDR) ................................................................................116 

Approving Design Requests (DTAPRDR).............................................................................116 

Message Considerations.........................................................................................................117 

Controlling the Use of ADDERR and CHGERR Parameters.................................................118 

Creating Design Request and Approval Records ...................................................................118 

Retrieving the Design Request Number .................................................................................118 

CHAPTER 7 UTILITIES 119 

Overview................................................................................................................................119 

Printing the Service Request Standard Report .......................................................................119 

Printing the Design Request Standard Report ........................................................................121 

Updating Design Request Information in SDM-ProjectMaster..............................................122 

Printing the Service Request Summary Report ......................................................................123 

Printing the Design Request Summary Report .......................................................................125 

APPENDIX A GLOSSARY OF TERMS 129 

INDEX 135 

CONTENTS • III

Notes 

IV • SDM-DESIGNTRACKER 5.0 USER GUIDE

CHAPTER 1 BEFORE YOU BEGIN 

Who Should Read This Book 

The SDM-DesignTracker system is used to manage and track data processing 

services (service requests) and software development projects (design requests). It is 

also used for release management processing, including release control and release 

deployment. Typical users include members of product support, product 

maintenance, and project leaders. 

What to Know Before Using This Product 

The instructions for this product assume that you are familiar with the following 

AS/400 functions: 

AS/400 

OS/400 operating system 

command line 

AS/400 security 

software development policies and procedures for your organization 

CHAPTER 1 BEFORE YOU BEGIN • 1

Document Conventions 

Installation Requirements 

2 • SDM-DESIGNTRACKER 5.0 USER GUIDE 

The following text conventions are used: 

Manual Name Italics indicates MKS product manual names, references to 

other manuals, new terms, and variables. 

ENTER Capital letters indicate keys you press or programs, files, 

directory names, or drive letters. 

ADDLIBLE Courier font indicates code-based information, such as 

system messages, field syntax, macros, or commands. Courier 

font also indicates all other information that you type. 

[Note, Recommendation, Tip]: Notes containing important information are 

bordered by lines on the top and bottom. 

Caution: Caution messages are bold and enclosed in a box. 

Refer to the SDM Install Guide for instructions on installing or upgrading SDM- 

DesignTracker.

MKS Product Support 

When you have questions or need assistance, contact MKS Product Support. 

Telephone 

INTERNATIONAL 

UNITED STATES 

(800) 633-6298 

Available: Monday-Friday 

7:00 a.m. to 6:00 p.m. (CST) 

MKS in North America: (800) 265-2742 

MKS in the U.K.: 44 0 1483 733 910 

MKS Online 

E-MAIL 

USA: support.sdm@mks.com 

UK: support.sdm.uk@mks.com 

WORLD WIDE WEB SITE 

http://www.mks.com 

Facsimile 

MKS in the U.S.: (630) 495-3591 

MKS in the U.K.: 44 0 1483 733 901 



How Does Product Support Work? 

MKS Product Support is dedicated to... 

providing customers with the solutions they need to become successful 

at using MKS products 

providing solutions in a timely manner 

documenting any MKS product related issues and using the 

documentation as input to product development plans 

Availability 

MKS Product Support is available to customers with a current maintenance 

agreement or companies previewing an MKS product. If you have questions 

concerning your maintenance status, contact your MKS Account Manager at (800) 

633-1235. 

MKS Online 

Visit our We page to download presentations, demos, and/or white papers about 

MKS products. You can also use our Internet addresses to e-mail any questions, 

concerns or suggestions you may have about our products. When you send us an email, 

a return e-mail is sent to acknowledge that your correspondence has been 

received. If necessary, your correspondence will be followed up by a phone call or email 

from one of our Product Support Specialists. 

Before You Call 

Experience shows that the best way to resolve issues quickly is to assign one person 

for each MKS product as your contact with MKS Product Support. 

Before calling, make sure you have reviewed all available documentation, which may 

contain the answer you need. Document the issue, and be prepared to provide the 

Product Support Specialist with your documentation. 

When You Call 

Make sure you have the following information available: 

company and caller name 

customer number 

call number (if call concerns an existing issue) 

product in question 

current release level of your MKS software 

FAX number 

description of the question or issue 

supporting documentation (job logs, reports, and so forth)

What to Expect 

MKS Product Support uses a call routing system. When calling, use the MKS 

Product Support number (800) 633-6298 to access the call routing system directly. 

If you call the receptionist, you will be transferred into the call routing system so that 

you can speak to the first available Support Specialist. 

If you choose to send an e-mail to our Internet address, it is also logged and assigned 

a call number and routed to a Support Specialist. You will receive a return e-mail 

identifying the call number that has been assigned to your incoming mail. A Support 

Specialist will contact you to discuss your inquiry. 

A Support Specialist is normally able to answer any questions you have or determine 

the cause of any issues you are having with an MKS product. 

If the issue requires additional research or other MKS resources, you can expect a 

return call based on the priority of the issue (listed next). After speaking with a 

Support Specialist, your issue is logged and assigned a call number. If the issue is not 

resolved, the Support Specialist will give you the call number for future reference to 

the specific issue. 

If a Support Specialist is not available when you call, you can leave a message, in 

which case you will be contacted at a later time. 

When leaving a message, leave your name, company name, phone number and a brief 

description of the issue. If you are calling after hours from your site, be sure to leave 

a direct number or extension where you can be reached. 

Priority of Call 

Following are the priorities that can be assigned to your call. 

A = software unusable, need immediate response 

B = software usable but problem is causing high degree of 

dissatisfaction, need immediate response 

C = need a response within the business day 

D = need a response within two business days 

E = request for enhancement 

Note: MKS Product Support is not a substitute for proper education or 

implementation services. For more information about MKS Client Education and 

Implementation Services, contact your MKS Account Manager at (800) 633-1235. 


Notes 

6 • SDM-DESIGNTRACKER 5.0 USER GUIDE

CHAPTER 2 GETTING STARTED 

What is SDM-DesignTracker? 

SDM-DesignTracker is used to manage and track data processing services (service 

requests) and software development projects (design requests). 

With seamless integration to SDM-Implementer, this system also provides release 

management functionality. Release management consists of two feature sets, release 

control and release deployment. Release control provides software versioning and 

internal release facilities. Release deployment provides software vendors the facility 

to distribute software changes to their customers on the SDM-Implementer Receiver. 

For more information about release management, see the Release Management User 

Guide. 

SDM-DesignTracker can also be used with SDM-SupportCenter, and SDM- 

ProjectMaster. This provides for total integration of the MKS Software Development 

Management (SDM) family of products. 

For a demonstration of the SDM-DesignTracker features and functionality, see the 

SDM-Implementer Quickview. The QuickView introduces you to: 

signing on to SDM-DesignTracker (with a demonstration user profile) 

an overview of the SDM-DesignTracker setup functions 

displaying the SDM-DesignTracker Main menu and Setup menu 

creating a Service Request 

creating a Design Request from a Service Request 

working with approvals 

creating SDM-Implementer and SDM-ProjectMaster projects 

CHAPTER 2 GETTING STARTED • 7

What’s Inside 


The following is a basic outline of what is covered in this manual. 

Chapter 1 Before You Begin 

Explains the purpose and organization of this manual. 

Chapter 2 Getting Started 

Covers various ways to use this manual to become more 

familiar with the SDM-DesignTracker product. Explains what 

is new in the latest release. 

Chapter 3 Setup Tasks 

Identifies the setup of the programs used to establish userdefined 

processing parameters required for logging service 

requests and design requests in SDM-DesignTracker. Also 

provides a high level overview of the setup tasks related to 

release management. 

Chapter 4 Work With Service Requests and Design 

Requests 

Presents the tasks for logging and working with service 

requests and design requests. The tasks used to create entities 

and check out projects in SDM-Implementer are also covered. 

Chapter 5 SDM-Implementer Interface 

Provides a review of the tasks used to create entities and 

check out projects in SDM-Implementer. Also includes 

setting up and using the release control feature of release 

management. 

Chapter 6 SDM-DesignTracker Command Interface 

Chapter 7 Utilities 

Appendix A Glossary 

Explains how to use command interfaces to perform a single 

or repetitive task. Also explains how to create or change a 

design request in batch. 

Covers the reporting and update features in SDM- 

DesignTracker. 

Provides a description of the special terms and used in 

this manual.

Starting SDM-DesignTracker 

To start using SDM-DesignTracker, add the library SDMIM to your library list. Type 

STRDT on the AS/400 command line, and press ENTER. This prompts the first 

SDM-DesignTracker Menu panel. 

What’s on the SDM-DesignTracker Main Menu 

SDM-DesignTracker is organized into two main menu panels. Each menu is 

organized by the type of tasks you are performing. 

SDM-DesignTracker Menu 1 of 2 

The tasks performed on a daily basis are found on the SDM-DesignTracker Menu 

panel, which displays when you first access SDM-DesignTracker. 


On this menu… 

Options 1 - 4 allow you to access and work with design requests. 

Option 5 updates SDM-ProjectMaster information. 

Options 6 - 8 allows you to access and work with service requests. 

Options 9 - 10 allow you to work with packages and deliveries 

associated with release management. See the Release Management 

User Guide for detailed information about using these functions. 

Option 20 accesses the Setup Menu where you perform all 

administrative and setup functions. 

Option 50 provides direct access to SDM-Implementer. 




Access this menu through option 20, Setup Menu, from the first SDM- 

DesignTracker Menu panel. 


All administrative and setup functions can be performed from this panel. This menu 

is separated into four categories: 

General Setup options allow you to define the basic SDM- 

DesignTracker data elements. 

Service Request Setup options allow you to define the data elements 

associated with service requests. 

Design Request Setup options allow you to define the data elements 

associated with design requests. 

Release Setup options allow you to define the data elements associated 

with release management processing. An overview of these options is 

included in Chapter 4, Setup Tasks. See the Release Management User 

Guide for detailed information about using these options.

What’s New in This Release 

The user interface of SDM-DesignTracker is enhanced with menu changes and many 

new options and functions to support Integrated File System (IFS) management, 

object revision tracking, and release management processing. 

Release management functionality consists of two feature sets, release control and 

release deployment. Release control provides new and enhanced software versioning 

and release capabilities. Release deployment is a new feature that allows software 

vendors and those who develop software with version control, the facility to 

distribute software changes to remote customers. 

For information about using release control, see “Using Release Control” in Chapter 

5. For more information about the optional release deployment feature, see the 

Release Management User Guide, or contact your MKS Account Manager at (800) 

633-1235. 

New Options on the Main Menu 

New options on the main menu include software packaging and distribution facilities 

for release deployment. The new options include: 

Option 9, Work with Packages 

Option 10, Work with Deliveries 

9, Work with Packages 

A package is the physical software deliverable that is sent to a customer system. A 

package can contain a collection of software items, and optionally, associated reports 

and auto-executable installation instructions for a specific product, version, and 

release. 

Option 9, Work with Packages, displays the To product version and release, and the 

From product version and release for each package. It also identifies whether a 

package is a standard release or PTF release. 

Work with Packages Panel 



From Work with Packages you can create, edit, delete, and display software 

packages. You can also print package reports, view comments and package details, 

and work with special commands and package dependencies. In Work with Packages, 

you can prepare a package for distribution, close the package, and upgrade a package 

to the current SDM-Implementer host version. 

10, Work with Deliveries 

A delivery is the physical distribution of one or more software to a specified 

customer system(s). A delivery can contain any number of packages, supporting both 

STD and PTF releases. 

Option 10, Work with Deliveries, displays each delivery sent to a customer system, 

the delivery creation date, delivery date, and a variety of other information. 

Work with Deliveries Panel 

From Work with Deliveries you can create, delete, display, and deploy deliveries to 

customer systems. You can also print reports, view upgrade selections, and start a 

pass-through session to a customer system.

New Options on the Setup Menu 

The new Release Setup group of functions on the Setup menu allows you to define 

many of the additional data elements and tables that are required for configuring 

release management. 

SDM-DesignTracker Setup Menu 

35, Release Types 

Release types define the types of releases you manage. For ease of use, release types 

are user-defined so that the terminology you currently use for identifying standard 

and PTF releases can be reflected in the release control process. 

36, Release Status 

The software release process configuration links release types and categories to a 

release status. 

The release status defines the path a release must follow before it can be changed to 

the next available status. It also defines the functions that can or can not be 

performed to the release during each phase of the cycle. 

37, Media 

Media definitions allow you to define the media available for distribution to customer 

systems. Media types can be tape or electronic. 

Electronic media definitions contain all of the communication parameters needed to 

pass-through and/or process deliveries to a customer system. These definitions are then 

attached to the customer system and used to select the actual devices. 

38, System Types 

System types are associated with customer systems and define the kind of computer 

systems they have. 



39, Countries 

Country codes are associated with customer locations. They are for geographic 

informational purposes and are optional. 

40, Customers 

Work with Customers was previously accessible from Work with Products only. Now 

accessible as a separate menu option, the customer database is expanded with more 

functionality. 

This is the primary location for viewing current version information for customers 

and distributing new versions of software. 

41, Customer Types 

Customer types are associated with customers, and allow you to classify or group 

your customers (for example, by industry or business group). 

Work With Products Enhancements 

The product database is the core of release management processing, providing access 

to products, versions, environments, packages, deliveries, and more. The product 

version database is enhanced to support the infrastructure of the user interface for 

seamless integration to SDM-Implementer and release management processing. 

Work with Products Panel 

From Work with Products you can work with approval users, work with product 

components, work with product versions, and work with customers associated with 

specific products. This is also where you identify for each product the load sequence 

for installing software and controls whether source is shipped.

10, Work With Versions 

The version database is also a core part of the release management infrastructure. 

The version database defines the product version, default customer environment, 

whether a version is supported and available for delivery, if it is based on another 

product version and release, and the to and from operating systems supported. 

Work with Product Versions Panel 

12, Work with “From” Environments 

From Work with Versions, option 12=Work with From Environments, allows you to 

display and assign the SDM environments which provide objects that make up the 

product version. 

This area also controls whether the environments attached to the product version allow 

standard releases and/or PTF releases to be shipped. You can arrange the environments 

in a sequential order to control which version of an object to ship, in the event some 

objects exist in multiple environments and other objects do not. 

Work with Product Version Environments Panel 



10, Working With Releases 

From Work with Versions, option 10=Work with Releases displays the Work with 

Releases for a Product/Version panel. On this panel, product versions display at the 

release level and include a text description, the status of the release (based on the 

release status configuration), the type of release, and identifies if the release is open 

or closed. 

Work with Releases for a Product/Version Panel 

From Work with Releases for a Product/Version, you can use the following options 

to perform additional release management functions: 

9, Work with Release Objects 

To work with the objects in a release and view related promotion requests, view 

member/object detail, and display related design requests for open releases. 

10, Work with Release Packages 

To display the Work with Packages panel filtered by the selected product version and 

release. 

11, Work with Dependencies 

To add change, delete, and display dependencies which the selected product version 

and release may have on another product version and release. Dependencies are most 

common with PTF type releases, which require the PTF be installed over a specific 

product version and release. 

12, Change Status 

To change the release status to another status defined in the release status configuration. 

26, DR Report 

To generate the Design Request Summary Report for the selected product version 

and release. 

27, DR Display 

To display associated design requests for the selected product version and release.

Integrated File System (IFS) Management 

Enhancements 

Display Entity List Enhancement 

To support the Integrated File System (IFS) management and revision number 

enhancements in SDM-Implementer 5.0, you can now view the ‘Revision’ field in the 

Display Entity List Member panel in SDM-DesignTracker. 

Report Enhancements 

SDM-DesignTracker reports are enhanced to support IFS object management. The 

following reports now support the use of revision numbers and/or IFS file names. 

Design Request Report now includes the revision number. The ‘Revision #’ field 

prints after the disposition. 

Design Request Summary Report now includes the revision number. The ‘Revision 

#’ field prints after the disposition. 

Additionally, the IFS file name now prints below each entity that has an IFS file 

name defined. 

Note: For more information about managing IFS object management or using 

revisions, see the SDM-Implementer System Administrator Guide or the SDM- 

Implementer User Guide. 


Notes 


CHAPTER 3 SETUP TASKS 

Overview 

This chapter covers the tasks required to establish the user-defined processing 

parameters for SDM-DesignTracker. The setup tasks should be performed in the 

order found here. Each task description explains how to define system control 

settings, processing parameters, user profiles, and so forth. You must complete each 

of the tasks covered in this chapter in order to enter and process requests in SDM- 


The setup tasks should be entered and maintained by the person responsible for the 

administration of the SDM-DesignTracker system. 

Note: Some of the common tasks in this chapter, such as Working with Products and 

Working with Versions, are used for processing service and design requests, and are 

also used for release management. The extent to which you define these elements 

should be determined by your use of the product and individual business needs. 

Other tasks, such as Working with Releases Types and Working with Release Status, 

are used only with release management. A brief overview of these setup tasks is 

included at the end of this chapter (see the Release Management User Guide for 

detailed information). If you are interested in setting up release management in your 

shop, contact your MKS Account Manager at (800) 633-1235. 

The setup tasks that you need to perform are listed next along with a brief overview 

of the task. These tasks should be performed in the following order: 

Work with Service Request and Design Request Type Codes Tasks 

define the various types of requests that can be logged to the system. 

These request type codes can be specific to your processing 

requirements. 

Work with Service Request and Design Requests Status Codes 

Tasks define the status codes used to identify the current status of a 

request, and to identify other processing considerations based on the 

status of a request. 

Work with Priority Codes Task identifies the various priorities used 

to track the relative importance of a request. 

Chapter 3 Setup Tasks • 19

20 • SDM-DesignTracker 5.0 User Guide 

Work with Project Creation Rules Task creates the rules used to 

automate the creation of design request projects in SDM-ProjectMaster. 

Work with Systems Task allows you to categorize a company and 

break it down by a specific physical machine, application, division, and 

so forth. 

Work with Environments Status Codes Settings Tasks identify the 

individual environments that are used for projects in SDM- 

Implementer. The corresponding design request status setting 

automatically updates the design request associated with the project 

when all the entities in a design request entity list have been moved to 

that environment. 

Work with Companies, Divisions, and Departments Tasks define 

the companies and optionally divisions and departments associated with 

each company. 

Work with Cost Centers Task identifies charge back identifiers that 

can be used with your accounting system. 

Work with Products, Components, and Versions Tasks define the 

products, components, and versions that requests will be logged for. If 

you use the SDM-DesignTracker and SDM-Implementer release 

management features, customers, releases, and environments are 

integrated as well. 

Work with Users Task identifies the processing authorities for each 

user logging and processing requests on the SDM-DesignTracker 

system. 

Work with Resources Task identifies the project leaders and 

development resources available for processing requests in SDM- 

Implementer. 

Work with Approval Users Task allows for the assignment of 

approval administrators for design requests and service requests 

(someone who can approve at any level). 

Change System Control Setting Task establishes the system-wide 

defaults and control parameters used to process requests in SDM- 


Release Management Setup Tasks provides an overview of the 

Release Setup functions related to release management processing.

Working With Service Request and Design Request Type 

Codes 

The Work with Service Request Type Codes and Work with Design Request Type 

Codes functions allow you to create, change, copy, delete, and display service request 

and design request type codes. The process is the same for both service requests and 

design requests. 

You can filter the display of service and design requests and report data by using the 

service request and design request type codes. The codes also display when you 

attach a service request to a design request. 

Type codes are used to categorize service requests and design requests when creating 

requests, selecting subset criteria or editing (for example, hardware requests, product 

enhancements, and so forth). They are also used in updating information 

communicated to SDM-Implementer. 

To work with service request and design 

request codes: 

1. From the SDM-DesignTracker main menu, type option 20, Setup 

Menu, and press ENTER. The Setup Menu displays. 

2. From the Setup Menu, type option 28, Request Types, and press 

ENTER to display the Work with Service Request Type Codes panel. 

Or, type option 30 and press ENTER to display the Work with Design 

Request Type Codes panel. 

Type codes can also be accessed from a command line by entering the 

Service Request Type Codes command DTWRKSTC, or the Design 

Request Type Codes command DTWRKDTC. 

3. If creating a new type code, type 1 in the Opt field to display the Create 

Service Request Type panel or the Create Design Request Type panel. 

If you want to perform a different function, you can select 2=Change, 

3=Copy, 4=Delete or 5=Display. 

4. Enter the following information: 

a) Character ID code 

b) Short description (which displays on the selection panels) 

c) Longer description 

5. Press ENTER to process your entries. The panel remains displayed for 

additional entries. 

6. Press F12=Cancel to redisplay the Type Codes selection panel or 

F3=Exit to redisplay the Setup Menu. 


Working With Service Request and Design Request 

Status Codes 


The Work with Service Request Status Codes and Work with Design Request Status 

Codes functions allow you to create, change, copy, delete, and display service request 

and design request status codes, and to identify corresponding message flags and 

write protect fields. The process is basically the same for both service requests and 

design requests. You can filter the display of service and design requests and report 

data by using the service request and design request status codes. These codes also 

display when you attach a service request to a design request. 

Status codes are used to identify the current status of a service request or design 

request (for example, completed, denied, open, and so forth). They are also used to 

identify subset selection criteria, messaging, to update information communicated by 

SDM-Implementer and from entities made in Environment Status Code settings 

(option 34) default. 

This is a required function that is typically performed by the SDM-DesignTracker 

System Administrator at the beginning of setup. The type codes are used to set up the 

defaults for service requests and design requests in System Control. 

To work with service request and design 

request status codes: 



2. From the Setup Menu, type option 29 to display the Work with Service 

Request Status Codes panel or option 31 to display the Work with 

Design Request Status Codes panel, and press ENTER. 

Status codes can also be accessed from a command line by entering the 

Work with Service Request Status Codes command DTWRKSSC, or the 

Work with Design Request Status Codes command DTWRKDSC.. 

3. If creating a new status code, type 1 in the Opt field to display the 

Create Service Request Status panel or the Create Design Request 

Status panel. 


3=Copy, 4=Delete or 5=Display. 


a) Three character ID code 

b) Short description (displays on the selection panels). 

c) Determine if this specific status code represents a closed request or 

open request. 

d) Identify which users will receive messages based on the status of a 

request. 

e) Determine which fields in the Work with Service Request and 

Work With Design Request functions are write protected for the 

status code. 

f) Longer description

Note: Changing the Closed status from 0 to 1 for an existing status code 

automatically closes any outstanding service or design requests that are 

logged under that code. A message displays to warn you of this before the 

changed status code is accepted. 

5. Press PAGEDOWN to access the second panel of the Work with 

Service Requests and/or Work with Design Request Status Codes 

function and enter the following information: 

a) Continue to determine what fields in the Work with Service 

Request and Work With Design Request functions are write 

protected for the status code. 

b) Long description for service request status codes. 

6. If you are creating a design request status code, press PAGEDOWN to 

access the third and final panel for input. Enter the following: 

a) Continue to determine what fields in the Work With Design 

Request function are write protected for the status code. 

b) Longer description for the design request status code. 



8. Press F12=Cancel to redisplay the Work with Status Codes selection 

panel or for other status code tasks, or press F3=Exit to redisplay the 

Setup Menu. 

Common Question 

Working With Priority Codes 

Q. If I am interfacing SDM-SupportCenter calls with service requests and/or design 

requests, do the service requests and design request status codes need to be the same 

as the SDM-SupportCenter codes? 

A. Yes. This is especially important if you want to create service requests or design 

requests from an existing SDM-SupportCenter call. 

The Work with Priority Codes options allows you to create, change, copy, delete, and 

display the requester, benefit (service requests and design requests) and development 

priority (design requests only) codes. Up to 36 separate codes can be identified. You 

can filter the display of service and design requests and report data by the different 

priority codes. 

Both service requests and design requests have a default requester and benefits 

priority code that can be changed when creating or updating the request. Design 

requests have the added ability to have a development priority code. The code that 

displays can be any one of the available codes for that type of request. The codes also 

display when attaching a service request to a design request. Priority codes are used 

to identify the relative importance of a request (for example, major impact, cosmetic 

change, and so forth). 

This is a required function that is typically performed by the SDM-DesignTracker 

System Administrator at the beginning of setup. The priority codes are used to set up 

the default requester, benefit, and priority codes in System Control. 



To work with priority codes: 


Menu, to display the SDM-DesignTracker Setup Menu. 

2. From the Setup Menu, type option 24,Priority Codes, and press 

ENTER to display the Work with Priority Codes panel. 

Priority codes can also be accessed from the command line using the 

Work with Priority codes command DTWRKPC. 

To display a specific priority code at the top of the Priority Code List, 

type the priority code in the Prty field and press ENTER. 

3. If you are creating a priority code, type 1 in the Opt field to display the 

Create Priority Code panel. 


3=Copy, 4=Delete, or 5=Display. 

4. Enter the following: 

a) character ID code 

b) Short description (which is displayed on the selection panels) 

c) Longer description. 



6. Press F12=Cancel to redisplay the Work with Priority Codes panel, or 

press F3=Exit to redisplay the Setup Menu. 


Q. If I am using SDM-SupportCenter, do the request priority codes need to be 

equivalent to SDM-SupportCenter call priorities? 

A. Yes. This is especially important if you want to create service request or design 

requests from an existing SDM-SupportCenter call.

Working With Project Creation Rules 

The Work with Project Creation Rules function is used to create rules to automate the 

creation of design request projects in SDM-ProjectMaster. Each code is associated 

with a set of detailed rules that determine the task(s) to be created for each entity on 

the Design Request Entity List. 

The rules defined here can be simple (one task per project) or complex (multiple 

functions for each project and multiple tasks per entity) depending on your individual 

processing requirements. 

This is an optional function that requires SDM-ProjectMaster to be loaded. The 

SDM-DesignTracker System Administrator at the beginning of setup typically 

performs it. The priority codes are used to set up the default requester, benefit, and 

priority codes in System Control. 

To work with project creation rules: 

1. From the SDM-DesignTracker main menu, select option 20, Setup 

Menu, and press ENTER to display the Setup Menu. 

2. From the Setup Menu, select option 33 and press ENTER to display 

the Work with Project Creation Rules panel. 

This function can also be accessed from the command line using the 

Work with Project Creation Rules command DTWRKPCR. 

The Work With Project Creation Rules detail panel is used to identify 

the project creation rule code, description and the associated 

parameters. To display a specific creation rule at the top of the list, 

enter the creation rule in the Rule field and press ENTER. 

3. If creating a new creation rule, type 1 in the Opt field to display the 

Create Project Creation Rule panel. 




a) Character ID code - this is a required field. 

b) Short description (displays on selection panels) 

c) Domain - Name of the SDM-ProjectMaster domain the created 

project is assigned to. This is a required field. 

d) Group - Optional name of the SDM-ProjectMaster group the 

created project is assigned to. 

e) Default activity - Name of the SDM-ProjectMaster activity which 

will be applied to a task if creating a single task project. 

f) Default task name - Name of the SDM-ProjectMaster task to be 

assigned to a task if creating a single task project (defaults to 

*DRNBR) 

5. Press ENTER to accept the project creation rule. 

6. Press F12=Cancel to redisplay the Work with Project Creation Rules 

panel. The rule you just created displays on the list. 


Working With Systems 


7. Type 8 in the Opt field next to the newly created rule to display the 

Work with Project Rules Creation Detail panel. 

To work with project creation rule details: 

1. If creating a new rule detail, type 8 in the Opt field next to the rule you 

want to modify. 

The Project Creation Rules Detail function is used to create the specific 

details about rules defined in the Work with Project Creation Rules 

function. 



2. Type the following information: 

a) Object code - Valid SDM-Implementer object code for this 

creation rule. An existing object/activity cannot be renamed. This 

is a required field. 

b) Activity - Valid SDM-ProjectMaster activity code. 

c) Task name - Valid SDM-ProjectMaster task name. This is a 

required field. The default is *ENTNAM. 

d) Estimated effort/Estimated cost - These entries determine if a task 

is created in SDM-ProjectMaster for a particular entity list member 

if the estimated effort/cost for the entity is greater than or equal to 

this value. 



4. Press F12=Cancel to redisplay the Work with Project Creation Rule 

Details panel, or F3=Exit to redisplay the Setup Menu. 

The Work With Systems function is used to identify the computer system(s) that 

service requests or design requests are created for. These are the systems that you 

own. When you create a service or design request, you assign the system that the 

request is for. System ID’s can also be used to display service requests and design 

requests. Report data can also be filtered by the different system codes. 

Work with Systems aids in the categorization and breakdown of a company per 

physical machine, application, and division. 

This is an optional function. The SDM-DesignTracker System Administrator at the 

beginning of setup typically performs systems setup. 

To work with systems: 




the Work with Systems panel. 


Work with Systems command DTWRKSYS.

3. If creating a new system, type 1 in the Opt field to display the Work 

with Systems panel. The Work With Systems function is used to 

identify the computer system name the service request or design request 

is for. 



4. To display a specific system at the top of the list, type the name in the 

System field and press ENTER. 


a) System name 

b) Short description (displayed on selection panels) 



7. Press F12=Cancel to redisplay the Work with Systems panel, or 


Work With Systems Task Variations 

It will probably be necessary to edit the system definition once you have set up and 

identified users who are authorized to perform request approvals. The users identified 

as approval users for the system must approve or deny all requests that are logged for 

a specific system. 

1. From the Work with Systems panel, select the system with 7 in the Opt 

field and press ENTER to display the Work with System Approval 

Users panel. 

2. If creating a new approval user, type 1 in the Opt field to display the 

Create System Approval Users panel. 

To display a specific system approval user at the top of the list, type the 

user profile ID in the User prof field and press ENTER. 




a) User profile (or press F4 to display a list of valid user profiles to 

choose from). 

b) Determine if the user must approve service requests for this system. 

c) Determine if the user must approve design requests for entities to 

be checked out, for promotion of entities to a test or production 

environment, or for promotion of entities to a production 

environment. 

4. Press ENTER to process your entries. 

5. The panel remains displayed for additional entries. 

6. Press F12=Cancel to redisplay the Work with Systems Approval Users 

panel, or F3=Exit to redisplay the Setup Menu. 


Working With Environment Status Code Settings 


This function is used to create, change, copy, delete, and display design environment 

status settings associated with an SDM-Implementer environment. 

Environment status settings are used to update the design request status code when all 

the entities in a Design Request Entity List have been moved to that. 

This is an optional function requiring that the SDM-Implementer environments exist. 

The SDM-DesignTracker System Administrator during setup typically performs the 

setup of the environment status code settings. 

To work with environment task code settings: 




the Work with Environment Status Settings panel. 


Work with Environments command DTWRKENV. 

3. If creating a new environment status setting, type 1 in the Opt field to 

display the Create Environment Status Setting panel. 

To display a specific environment at the top of the list, enter the 

environment name in the Environment field and press ENTER. 




a) Environment name or type. Use F4 to display a list of valid SDM- 

Implementer environments to choose from. This is a required field. 

b) Short description (displays on selection panels). 

c) Design request status setting. 

Note: It is this setting that determines the status of a particular request. 

5. Set the message flags to determine who receives the message: 

a) Design request requester 

b) Design request approvers 

c) Design request project leader 

d) Service request requesters 

e) Service request approvers 

f) SDM-SupportCenter calls 



7. Press F12=Cancel to redisplay the Work with Environment Status 

Settings panel, or F3=Exit to redisplay the Setup Menu.

Working With Companies, Divisions, and Departments 

This function is used to establish specific identification for each company. The 

function allows you to create, change, copy, delete, and display SDM-DesignTracker 

company records. Optional divisions and departments can also be defined for each 

company. 

It is easier to manage a specific request when it can be tracked by a 

company/division/department. User profiles required for the approval of a service 

request and/or design request can be tied to the specific company, division, 

department, or any combination of each. It is possible to use the company, division, 

or department to display service requests and design requests, as a filter on the 

service requests and design request reports, and to filter the display of service 

requests and design requests by company. 

This is an optional function that is typically performed by the SDM-DesignTracker 

System Administrator at the beginning of setup. 

To work with companies, divisions, and 

departments: 

1. From the SDM-DesignTracker main menu, Type option 20, Setup 


2. From the Setup Menu, type option 25 and press ENTER to display the 

Work with Companies panel. 

This function can also be accessed using the Work with Companies 

command DTWRKCMP. 

3. If creating a new company, type 1 in the Opt field to display the Create 

Company panel. 

To display a specific company at the top of the list, enter the company 

name in the Company field and press ENTER. 




a) Company name - this is a required field. 


5. Press ENTER to process your entries. The panel remains displays for 


6. Press F12=Cancel to redisplay the Work with Companies selection 




Working With Companies, Divisions, and 

Departments Task Variations 

You may need to identify approval users for a specific company/division/department. 

The users entered as approval users for the company/division/department must approve 

or deny all requests that are logged for a specific company/division/department. 

To work with approval users: 

1. From the Work with Companies panel, select the specific company with 

7 in the Opt field to display the Work with Company Approval Users 

panel. 


Create Company Approval Users panel. 

To display a specific company approval user at the top of the list, type 

the user profile ID in the User prof field and press ENTER. 





choose from). 

b) Determine if the user must approve service requests for this 

company/division/department. 




environment. 



5. Press F12=Cancel to redisplay the Work with Company Approval Users 


You can use the same process to add approval users to divisions and/or 

departments if required.

To establish divisions and departments: 

If you are establishing divisions and departments in the company definition, perform 

the following tasks from the Work with Companies panel. 

1. Type 8 in the Opt field next to the newly created company and press 

ENTER to display the Work with Divisions panel. 

2. If creating a new division, type 1 in the Opt field to display the Create 

Division panel. 

To display a specific division at the top of the list type the division 

name in the Division field and press ENTER. 




a) Division name - this is a required field. 


4. Press ENTER to accept your entries. The panel remains displayed for 


5. Press F12=Cancel to redisplay the Work with divisions panel, or 


Note: Use the same process to create a department by typing option 8 in the 

Opt field next to the division to access the Work with Departments panel. 


Working With Cost Centers 


This function allows you to create, change, copy, delete, and display the cost centers 

information. 

This function is used to provide a charge-back identifier for a service or design 

request that can be used with your accounting system. Cost center can also be used to 

display service and design requests and as a filter for reports. 



To work with cost centers: 




Work with Cost Centers panel. 

This function can also be accessed using the Work with Cost Centers 

command DTWRKCC. 

3. If creating a new cost center, type 1 in the Opt field to display the 

Create Cost Centers panel. 

To display a specific cost center at the top of the list, type the cost 

center name in the Cost Center field and press ENTER. 




a) Cost center name - this is a required field. 


c) Manager associated with the cost center - this is an optional field. 



6. Press F12=Cancel to redisplay the Work with Cost Centers panel, or 

F3=Exit to redisplay the Setup Menu.

Working With Cost Centers Task Variations 

You may need to identify approval users for a specific cost center. The users entered 

as approval users for the cost center must approve or deny all requests that are logged 

for a specific cost center. 

1. From the Work with Cost Centers panel, select the specific cost center 

with 7 in the Opt field to display the Work with Cost Center Approval 



Create Cost Center Approval Users panel. 

To display a specific cost center approval user at the top of the list, type 

the user profile ID in the User prof field and press ENTER. 





choose from). 

b) Determine if the user must approve service requests for this cost 

center. 




environment. 



5. Press F12=Cancel to redisplay the Work with Cost Centers Approval 

Users panel, or F3=Exit to redisplay the Setup Menu. 


Working With Products and Components 


This function is used to identify the software products that service requests and 

design requests will be made for. Optional components and versions can also be 

defined. Components further define the software product. Products, components, and 

versions can also be used to display service request and design requests, and as a 

filter on reports. 

The product database is also used for release management (products, versions, and 

releases are used for both release control and release deployment). Work with 

Products also provides access to versions, software ‘from’ environments, packages, 

deliveries, and more. For more information see “Using Release Control” in Chapter 5 

of this manual, or the Release Management User Guide. 

This option allows you to create, change, copy, delete, and display product 

information. Users can also be tied to the approval list for a specific product and/or 

component. 



To work with products and components: 




Work with Products panel. 

Work with Products Panel 

This function can also be accessed using the Work with Products 

command DTWRKPRD.

Work With Products Panel Options 

The standard options on the Work with Products panel include 1=Create, 2=Change, 

3=Copy, 4=Delete (for products with components, you must delete related 

components prior to deleting the product), and 5=Display. Each of these options 

display the Product Maintenance window ⎯when using any of these options refer to 

the “Product Maintenance Field Descriptions” on page 36 for information about the 

fields. 

The additional options on this panel include: 

7=Approve User, to create, change, copy, delete, and display product 

approval users. Approval users are required to approve or deny all 

service requests and/or design requests that are logged for a specific 

product. For more information see “Working With Approval Users” on 

page 54. 

Note: Approval users are not required for release management. 

8=Work with Components, to work with components associated with 

a product. You can create, change, copy, delete, and display 

components, and work with approval users for the components. For 

more information see “Working With Components” on page 37. 

10=Work with Versions to work with the versions associated with a 

product. From Work with Product Versions, you can create, change, 

copy, delete, and display product versions. You can also work with 

releases for the product version, work with customers associated with 

the product version, and work with product version “from” 

environment(s). For more information see “Working With Product 

Versions” on page 39. 

11=Work with Customers to work with the customers associated with 

the product version. This is known as the customer product relationship. 

From Work with Customers for a Product, you can create and remove 

product/customer relationships. The product customer relationship 

establishes whether source is, by default, included in a package. For 

more information see “Working With Customers” on page 62. 



To create a product definition: 

1. From the SDM-DesignTracker Setup menu, select option 23, Products, 

and press ENTER. The Work with Products panel displays. 

2. Type 1=Create on the first option line and press ENTER. The Product 

Maintenance window displays. 

Product Maintenance Window 

3. Complete this panel as defined next in “Product Maintenance Field 

Descriptions”. 

4. When finished, press ENTER. 

Product Maintenance Field Descriptions 

Product 

Identify the product. This is a 10 character user-defined field. Input is required. 

Description 

Enter a description for the product. This is a 30 character field. Input is required. 

Manager 

Identify the product manager, if applicable. 

Load Sequence 

The load sequence controls the order that products are loaded on the tape, and the 

order in which they are installed from the tape on the customer system. For packages 

that contain multiple products, this determines the order that this product is installed 

in relation to the other products in the shipment. For example, if an Order Entry (OE) 

application requires that a General Ledger (GL) application be on the system prior to 

an install, GL would have a lower load sequence than OE. This is a five character 

numeric field. Input is optional.

Default Source 

Indicate whether source, by default, is shipped with the product. Valid options are Y 

(Yes) and N (No). The default value is N. 

Allow Default Source Override 

Indicate whether the default source flag can be overridden at time a package is 

created. Valid options are Y (Yes) and N (No). The default value is N. 

Working With Components 

Components provide a lower level of detail for a product definition by allowing you 

to define the modules that make up the product. This is useful for tracking and 

reporting changes, and for identifying which modules are impacted by software 

modifications. 

For example, components of an Accounts Receivable product could include customer 

maintenance, documentation, online help, reporting, and tutorials. You could also 

define a component of *ALL, to indicate for example, that a change to a master file 

impacts all modules of the product. 

Product components are created at the product level. If you intend to use product 

components, you will need to create them during your initial data setup (or ongoing 

as required). The use of product components is optional for release management 

processing. 

To work with components: 

1. From the SDM-DesignTracker Setup menu, select option 23, Products 


2. Select the product you want to work with components for with option 

8=Work with Components. The Work with Components panel displays. 

Work with Components Panel 



Work With Components Panel Options 

The standard options on the Work with Components panel include 1=Create, 

2=Change, 3=Copy, 4=Delete. Each of these options displays the Component 

Maintenance panel. When using any of these options refer to the “Create Component 

Field Descriptions” on page 38 for information about the fields. 

The additional option on this panel is: 

7=Appr users, to create, change, copy, delete, and display component 

approval users. Approval users are required to approve or deny all 

service requests and/or design requests that are logged for a specific 

product component. For more information “Working With Approval 

Users” on page 54. 

Note: Approval users are not required for release management. 

To create a component: 

1. Type 1=Create on the first option line and press ENTER. The Create 

Component panel displays. 

2. Complete this panel as defined next in “Create Component Field 

Descriptions”. 

3. When finished, press ENTER. The record is added and the Create 

Component panel remains displayed for entry of another record. 

Create Component Field Descriptions 

Component 

Enter the component name. This is a 10 character alphanumeric field. 

Description 

Provide a text description for the component. This is a 30 character field and input is 

optional.

Working With Product Versions 

A version is one of a sequence of copies of a product, with each version 

incorporating new modifications. A version is usually identified by a number, 

commonly in the form “X.Y”, where X is the major version number and Y is the 

release number. Typically an increment in X (with Y reset to zero) signifies a 

substantial increase in product functionality, or a partial or total re-implementation, 

whereas Y increases each time the product changes in any way and is re-released. 

Version numbers are useful for tracking program changes (bugs fixed or new 

functions added). This allows determination of whether a problem relates to the 

current version. (This makes it important to identify the version when reporting bugs. 

Statements about compatibility between different software components should always 

indicate which versions they apply to). 

To work with product versions: 

1. From the SDM-DesignTracker Setup menu, select option 23, Products 


2. Select the product you want to work with versions for with option 

10=Work with Versions. The Work with Product Versions panel 

displays. 

Work with Product Versions Panel 

Work with Product Versions Options 

The standard options on the Work with Product Versions panel include 1=Create, 

2=Change, 3=Copy, 4=Delete, and 5=Display. Each of these options displays the 

Product Version Maintenance panel. When using any of these options, see “Product 

Version Maintenance Field Descriptions” on page 41 for more information about this 

panel. 




10=Work with Releases, to work with releases that are associated with 

the specified product version. For more information about this option 

see “Working with Releases” on page 42. 

11=Work with Customers, to work with customer and customer 

systems associated with a product version. For more information see 

“Working With Customers” on page 62. 

12=Work with From Environments, to work with the environments 

associated with a product version. For more information about this 

option see “Working With From Environments” on page 45. 

To create a product version: 

1. From the SDM-DesignTracker Setup menu, select option 23, Products, 


2. Select the product you want to work with versions for with options 

10=Work with Versions. The Work with Product Versions panel 

displays. 

3. Type 1=Create on the first option line and press ENTER. The Product 

Version Maintenance window displays. 

Product Version Maintenance Window 

4. Complete these fields as defined next in “Product Version Maintenance 

Field Descriptions”. 

5. When finished, press ENTER.

Product Version Maintenance Field Descriptions 

Product 

The product defaults based on the product you selected to work with versions for. 

Version 

Specify the new version. This is a 10 character alphanumeric field. Input is required. 

Version Description 

Enter descriptive text to identify the version. This is a 30 character field. Input is 

required. 

Default Customer Environment 

Specify the environment associated with the product version. This is also the 

distribution environment⎯when a package is created this is the “To” environment 

that is sent to a customer system. You can use F4 to prompt and select from a list of 

defined environments. 

Available to Deliver 

This field is for informational purposes to indicate whether the version is currently 

available to send to a customer system. Valid values are Y (Yes) and N (No). The 

default value is N. 

Supported 

This field is for informational purposes to indicate whether the version is currently 

supported. Valid values are Y (Yes) and N (No). The default value is N. 

Version Date 

The field allows you to associate the version with a date. For example, this could be 

the date the version was created or a shipment availability date. 

Based on Product 

Specify the base product that this version was created from. This allows you to 

determine the level of modifications for a product that is used as the starting point of 

the new product version. 

When you use F4 to prompt and select from the list of valid product/version/release 

categories, the Based on Version and Based on Release default from the product 

definition. 



Based on Version 

Specify the base version that this version was created from. This allows you to 

determine the level of modifications for a product version that is used as the starting 

point of the new product version. This value defaults if you use the F4 prompt option 

for Based on Product. 

Based on Release 

Specify the base release that this version was created from. This allows you to 

determine the level of modifications for a product version and release that is used as 

the starting point of the new product version. This value defaults if you use the F4 

prompt option for Based on Product. 

From O/S Level 

Specify the operating system level this version was created from. You can specify an 

actual operating system value, *ANY or *NETCONFIG (which retrieves the value 

from system attribute). The default value is *NETCONFIG. 

To O/S Level 

Specify the operating system level the version will run on. The default value is *ANY. 

Working with Releases 

Releases are defined at the product version level. 

From the Work with Releases for a Product Version panel, you can create, change, 

delete, and display releases associated with a product version. 

The additional tasks performed in Work with Releases include: 

Option 9=Work with Release Objects, to work with the release 

objects that are in the product version. This provides information about 

promotion requests, member/object detail, and design requests. 

Option 10=Work with Release Packages, to work with packages and 

package dependencies associated with the release, or to create new 

packages for the product version.. 

Option 11=Work with Dependencies, to work with and add or delete 

release dependencies associated with the product version. 

Option 12=Change Status, to change the release status. See “Using 

Release Control” in Chapter 5 for information about the release status 

and valid values. 

Option 26=DR Report, to print the Design Request Summary Report 

for design requests associated with the release. 

Option 27=DR Display, to display design requests associated with the 

release.

To work with releases: 

1. From Work with Products, select a product with option 10=Work with 

Versions. The Work with Product Versions panel displays. 

2. Select a product version with option 10=Work with Releases. The 

Work with Releases for a Product/Version panel displays. 

3. Type 1 to create a new release definition, or use 2=Change, 4=Delete 

or 5=Display to perform another option. The Product Version Release 


Product Version Release Maintenance Panel 

The Product and Version fields default based on the product version 

you selected on the previous panel. 

4. Complete this panel as defined next in “Product Version Release 

Maintenance Field Descriptions”. 

5. When finished press ENTER. The Work with Releases for a Product/ 

Version panel redisplays. 



Product Version Release Maintenance Field 

Descriptions 

Release 

Define the release name. This a 10 character alphanumeric field and input is required. 

Release Description 

Provide a description of the release. This is a 40 character field and input is required. 

Release Type 

Define the type of release you are creating. Use F4 to prompt and select from a list of 

valid release types (if the release type does not exist, use F6 to create it). This is a 

required field. 

Release Status 

When creating a new release, the release status defaults to ENV-OPEN (environment 

open). To change the release to another status, use option 12 on the Work with 

Releases for a Product Version panel. 

Date Opened 

This is not an input-capable field. The date and time values default to the system date 

and time of when the release was opened. 

Date Closed 

This is not an input-capable field. The value defaults to *OPEN until the release is 

changed to ENV-CLOSE status. The date and time values default to the system date 

and time of when the release was closed.

Working With From Environments 

The release management function uses the ‘from’ environment(s) referenced for a 

product version to determine the location of software items that need to be packaged 

together. For release deployment the objects in these environments are sent to a 

customer (ensuring the customer is delivered a specific release within a product 

version). 

In addition, the SDM-Implementer promotion process checks to see if the ‘To’ 

environment of the promotion request is attached to a product version. SDM- 

Implementer will only allow a promotion request to be promoted into an environment 

attached to a product version if the product version has an ‘Open Release’. If the 

product version does not have an open release the promotion request will result in a 

‘Move-Fail’ status. This method ensures that the SDM-Environments that the product 

releases are created from can be frozen until the product manager decides to open a 

new release. 

There is no limit to the number of from environments you can associate with a 


Important: When defining ‘from’ environments for a product version, all 

environments that an object could possibly pass through on the path to the 

production environment must be defined for the product version. This includes any 

TST and QAC environments, as well as any environments that can be used for 

emergency checkout and/or emergency promotion. The reason for this is because if 

an object passes through an environment that is not defined, the audit trail 

information for that object will be lost, causing any design requests not to be attached 

to the releases or packages. In addition, any TST and QAC environments must be 

defined with the ‘Allow STD Release’ and ‘Allow PTF Release’ flags set to ‘N’. 



To work with ‘From’ environments: 

1. From Work with Products, select a product with option 10=Work with 

Versions. The Work with Product Versions panel displays. 

2. Select a product version with option 12=Work with From 

Environments. The Work with Product Version Environments panel 

displays. 

3. Type 1 to create a new product version environment definition, or use 

2=Change, 4=Delete or 5=Display to perform another option. The 

Product Version Environment Maintenance window displays. 

Product Version Environment Maintenance Window 

The Product and Version fields default based on the product version 

you selected on the previous panel. 

4. Complete this panel as defined next in “Product Version Environment 

Maintenance Field Descriptions”. 

5. When finished, press ENTER. The Work with Product Version 

Environments panel redisplays.

Product Version Environment Maintenance Field 

Descriptions 

Environment 

Specify the environment where the member/objects that make up this product version 

are coming from. This is used to determine the location of software items that need to 

be packaged and sent to a customer (ensuring the customer is delivered a specific 

release within a product version 

Sequence Number 

Defines the order that objects are pulled from the repository and included in the 

release. 

For example: If you have both MODS and a BASE production model in your 

environments, you will typically place MODS with a lower sequence number so that 

is the first place objects are pulled from. This is important in cases where you might 

have the same object name in multiple environments. 

Whether you have a MODS/BAS model described above or a model where two 

products share some of the same object names (but the objects are different in the 

two products). You would typically always want the primary product copied, so you 

would set that product’s environments to have a lower sequence number than the 

secondary products environments. 

Allows Standard Release 

Specify whether this environment allows standard releases. Valid values are Y or N. 

Allow PTF Release 

Specify whether this environment allows PTF releases. Valid values are Y or N. 



Working With Approval Users 

Approval users can be defined at the product level (for all components) or at the 

component level (which allows for components to have different approval users). The 

users entered as approval users for the product and/or component must approve or deny 

all requests that are logged for a specific product and/or component. 

To work with approval users: 

1. From the Work with Products panel, select the product with 7 in the 

Opt field to display the Work with Product Approval Users panel. 


Create Product Approval Users panel. 

To display a specific product approval user at the top of the list, type 

the user profile ID in the User prof field, and press ENTER. 




a) User profile (or press F4 to display a list of valid user profiles 

to choose from). 

b) Determine if the user must approve service requests for this 

product component. 

c) Determine if the user must approve design requests for entities 

to be checked out, for promotion of entities to a test or 

production environment, or for promotion of entities to a 

production environment. 



5. Press F12=Cancel to redisplay the Work with Product Approval Users 

panel or F3=Exit to redisplay the Setup Menu. 

Note: Use the same process to create approval users for components of a 

product, if required. 


Q. If I am using SDM-SupportCenter, do the SDM-DesignTracker request product 

and component codes need to be equivalent to the SDM-SupportCenter product and 

component codes? 

A. Yes. This is particularly important if you want to create service requests or design 

requests from an existing SDM-SupportCenter call.

Working With Users 

This option allows you to create, change, copy, delete, and display user information. 

This option is also used to identify the SDM-DesignTracker System Administrators 

and users with maintenance authority in Work with User Profiles. It further allows 

you to determine user subset authorities and corresponding subset defaults, and to 

identify users who have signing authority for other users on Approval Lists. 

It is necessary for users to be enrolled in SDM-DesignTracker in order to use the 

system. This is particularly true for identifying the System Administrator, user subset 

authorities and defaults, and to identify users who have signing authority for 

approvals. 

This is a required function typically performed by the SDM-DesignTracker System 

Administrator. You must have a valid AS/400 user profile. It is performed at the 

beginning of setup, or when subset or user default changes are required. 

To work with users: 




Work with Users Profiles panel. 

This option can also be accessed using the Work with User Profiles 

command DTWRKUSR. 

3. From the Work with Users Profiles panel, type 1 in the Opt field to 

display the Create User Profile panel to create a new user profile. 

To display a specific user at the top of the list, type the user name in the 

User field and press ENTER. 


3=Copy, 4=Delete, 5=Display, 6=DR subset defaults, 7=SR subset 

defaults, or 8=Sign for users. 

4. On the Create User Profile panel, enter the following: 

Notes: 

1. Default values entered here are initially used as the default selection 

criteria in the Subset Service Requests and Subset Design Requests 

functions. When a user initially creates a request, these values are used 

to start the request. 

2. Users identified as System Administrators can change the status of a 

service request or design request even if the Status field is write 

protected for a specific status code in the Work with Service Request 

Status Codes or Work with Design Request Status Codes functions. 



a) Basic information 

User Profile 

Description 

System Administrator 

b) Authorization information for service requests and design requests 

Display Requests 

Maintain Requests 

Approval Administrator 

Maintain Subset Values 

c) Basic defaults 

System 

Product 

Component 

Version 

d) Requester defaults 

Company 

Division 

Department 

Cost Center 

Contact 

e) Development defaults 

Production environment 

f) Project defaults 

Project creation rule 



6. Press F12=Cancel to redisplay the Work with Users Profiles panel, or 

F3=Exit to redisplay the Setup Menu.

Work With Users Task Variations 

If you are establishing service request and design request subset values for this user, 

perform the following tasks from the Work with Users Profiles panel. 

To establish subset criteria for the user: 

1. Type 6 in the Opt field next to the user and press ENTER to display the 

Subset Design Requests panel, or type 7 in the Opt field next to the user 

and press ENTER to display the Subset Service Requests panel. 

Note: The subset criteria established here is initially used when you run the 

Print Service Request Standard Reports (DTPRTSR), Print Design Request 

Standard Reports (DTPRTDR), Service Request Summary Reports 

(DTPRTSRM) and Design Request Summary Reports (DTPRTDRM) 

functions. The default criteria can be changed if the Maintain subset default 

field in the User Profile function is set to 1 (Yes). 

2. Specify the required subset criteria, or accept the default values 

(*ALL). Press PAGEDOWN to access the second subset panel. 

Note: The first time this panel is accessed, the values that display 

automatically default to the values entered for the individual user in the 

Work with User Profiles function. To change the defaults, clear the fields to 

set to *ALL, or enter another value. 

3. Specify additional subset criteria or accept the defaults. 

4. The Automatic prompt on subset field determines if the corresponding 

subset panel automatically displays each time the Work with Service 

Requests and Design Requests functions are accessed. Depending on 

how the Maintain subset values field in Change User Profile is set, the 

following can be true: 

Maintain subset Values = 1 (Yes) and Automatic prompt on subset 

= 1 (Yes): The subset panel automatically displays each time the 

user selects the Work with Service Requests and/or Design Request 

functions. User can select new subset criteria or accept the defaults. 

The F17=Subset function can also be selected from the Work with 

Service Requests or Work with Design Requests selection panels to 

display and maintain the corresponding subset panels. 

Maintain subset Values = 0 (No) and Automatic prompt on subset 

= 1 (Yes): The subset panel automatically displays each time the 


functions. The user can view but not maintain the displayed subset 

criteria. The F17=Subset function can also be selected from the 

Work with Service Requests or Work with Design Requests 

selection panels to display (but not maintain) the corresponding 

subset panels. 



Maintain subset Values = 1 (Yes) and Automatic prompt on subset = 

0 (No): The subset panel does not automatically display each time the 


functions. The F17=Subset function must be selected from the Work 

with Service Requests or Work with Design Requests selection 

panels to display and maintain the corresponding subset panels. 

Maintain subset Values = 0 (No) and Automatic prompt on subset = 

0 (No): The subset panel does not automatically display each time the 


functions. The F17=Subset function can be selected from the Work 

with Service Requests or Work with Design Requests selection 

panels to display (but not maintain) the corresponding subset panels. 



6. Press F12=Cancel to redisplay the Work with Users Profiles panel, or 


If you are establishing users who are able to approve requests for this user in their 

absence, perform the following tasks from the Work with Users Profiles panel. 

1. Type 8 in the Opt field next to the user profile ID and press ENTER to 

display the Work with Sign for Users panel. 

2. If creating a sign for user, type 1 in the Opt field to display the Add 

Sign for User panel. 

To display a specific user at the top of the list, type the user profile ID 

in the User Profile field and press ENTER. 

If you want to delete a user from this authority, select option 4=Delete. 

3. Type the ID of the user who can sign for the selected user, or press F4 

to display a list of valid user profiles to choose from. 



5. Press F12=Cancel to return to the Work with Sign for Users panel or 



Q. Is there any limit to the number of sign for users I can define per user profile? 

A. No.

Working With Resources 

This option allows you to create, change, copy, delete, and display resource initials 

used to identify project leaders and development resources assigned to design 

requests. It also allows you to identify project leaders and development resources 

assigned to design requests, and is used to display design requests and to filter report 

data. 

This is a required function typically performed by the SDM-DesignTracker System 

Administrator near the end of setup, or when a new resource needs to be defined. 

The users must be added using Work with Users. The resource initials entered here 

must be the same as those entered in SDM-ProjectMaster (if it is installed). 

To work with resources: 


Menu, and press ENTER. 


Work with Resources panel. 

This option can also be accessed using the Work with Resources 

command DTWRKRSR. 

3. If creating a resource, type 1 in the Opt field to display the Create 

Resource panel. 

To display a specific resource at the top of the list, type the resource 

name in the Resource field and press ENTER. 


3=Copy, 4=Delete, or 5=Display 


a) Resource initials 

b) Short description 

c) User profile (or press F4 to select from a list of valid user profiles) 



6. Press F12=Cancel to redisplay the Work with Resources panel, or 



Working With Approval Users 


Different aspects of the setup and request process need to have specific approvals. 

For most of the applications, it is best to set up the approvals at the end of the setup 

task. Work with Users allows for the assignment of approval administrators for 

design requests and service requests (someone who can approve at any level). 

If approvals will be used at different levels (companies, divisions, departments, 

systems, costs centers, products, and components), it is necessary to define who the 

approvers are. It is also necessary for the approvals to be set up if they want to get 

messages on the status of service requests and design requests through the 

Environment Status function. 

This is a required task. When a request is created it is set to a pending status and it 

must be approved. The approval could be set at the Work with User level of an 

approval administrator, or at any sub-level of company, product, system, or cost 

center. 

The SDM-DesignTracker System Administrator at setup, or whenever it is necessary 

to add or change an approval typically defines this. 

The user profiles must be setup in SDM-DesignTracker. 

To work with approval users 

The following steps describe how to set up an approval for a division approval user. 

The task assumes that a company with a division was created and that users are 

defined. The steps are similar for companies, departments, cost centers, systems, 

products, and components. It is important to remember, for companies and products 

with lower approval levels for certain users, approvals at higher levels may 

intentionally be disallowed (for example, a user allowed to approve at a department 

level may not be allowed to approve at a division or company level). 

1. From the SDM-DesignTracker main menu, type option 20 and press 

ENTER to display the Setup Menu. 


Work with Companies panel. 

This option can also be accessed by entering the Work with Approval 

Users command DTWRKCMP. 

To display a specific company at the top of the list, type the company 

name in the Company field and press ENTER.

3. Type 8 in the Opt field to display the Work with Divisions panel. 

To display a specific division at the top of the list type the division 

name in the Division field and press ENTER. 

4. Type 7 in the Opt field to display the Work with Division Approval 


5. If creating an approval user, type 1 in the Opt field to display the 

Create Division Approval User panel. 




a) User profile (or press F4 to select from a list). 

b) Specify if the particular user must approve service requests for that 

division. 

c) Specify if the particular user must approve design request entities 

for check out or promotion to a test or production environment in 

SDM-Implementer. 



8. Press F12=Cancel to redisplay the Work with Division Approval Users 



Changing System Control Settings 


The System Control Setting function allows you to establish system-wide defaults 

and control parameters best suited for your individual processing needs. 

The system control settings define to SDM-DesignTracker what applications are 

installed. This function also sets up the initial defaults, required entries, and 

validation rules for the entries. 

This is a required function typically performed by SDM-DesignTracker System 

Administrator at the end of setup. 

SDM-DesignTracker must be installed. If SDM-Implementer, SDM-SupportCenter, 

and SDM-ProjectMaster are to be used, they too must be installed. Type codes, status 

codes, and priority codes must also exist. 

To change system control settings: 

1. From the SDM-DesignTracker main menu, type option 20 to display 

the Setup Menu. 


Change System Control Settings panel. 

This option can also be accessed by using the Work with System 

Control Settings command DTMNTSC. 

3. System Control is divided into four sections: 

Applications installed: Select SDM-Implementer, SDM- 

SupportCenter, or SDM-ProjectMaster by typing 1. 

Initial settings: These settings determine defaults for service 

requests and design requests. The type, status, and priorities must 

exist before you can be select or use them. 

Validation rules: The validation rules determine what information 

is required for service requests and design requests, and also allows 

for validation of setup defaults. 

International information: This is used to determine the domestic 

currency for all cost fields (for example, USD - United States 

Dollars). 

4. Select the appropriate defaults. Major changes would be to set the 

correct flags for the installed applications, and to change the status set 

at approval to what your company requires. 

5. The defaults for the validation rules require validation for the specified 

entries, but not that the entries are required. Therefore, the only 

required entry for a service request or a design request is the request 

title. 

6. Press ENTER to process your entries. 

7. Press F3=Exit or F12=Cancel to redisplay the main menu without 

processing your changes.

Release Setup Options 

The Release Setup group of functions on the Setup menu is used to define many of 

the data elements that are required for configuring release management. 

While release management includes the use of products, versions, releases, 

environments, and many other data elements, this section is a high-level overview of 

the Release Setup group of functions. 

Note: Release management functionality consists of two feature sets, release control 

and release deployment. Release control provides software versioning and release 

capabilities. For more information about release control, see “Using Release Control” 

in Chapter 5 of this manual. Release deployment is an optional feature that allows 

software vendors and those who develop software using version control the facility to 

distribute software changes to remote customers. For more information about the 

release deployment features, contact your MKS Account Manager at (800) 633-1235. 

Working With Release Types 

Release types define the types of releases you manage. Release types are associated 

with release type categories (standard or PTF) and the release status. Together, these 

elements define the process that a release must follow and complete. It also 

determines the dependency that is automatically associated between a current release 

and a previous release. 

For ease of use, release types are user-defined so that the terminology you currently 

use to identify standard and PTF releases can be reflected in your release 

management process. 

Work with Release Types Panel 

From option 35, Release Types, you can create, change, copy, delete, and display 

release status types. 



Working With Release Status Types 

The release status is associated with release types and defines the process that both 

STD and PTF category release types must complete. The release status also defines 

what additional release management processes can or can not occur to the release at 

each stage in the process. These data elements establish the release status 

configuration. 

Work with Release Status Panel 

From option 36, Release Status, you can create, change, copy, delete, and display the 

data elements that make up the release status configuration. 

Caution: By incorrectly changing these values, it is possible to setup a meaningless 

process that can not be followed. If the release status is changed, be sure to test the 

complete release lifecycle before attempting to use in an “live” scenario.

Working With Media Types 

Media definitions allow you to define the distribution method (tape or electronic) for 

software deployment to a customer system. They include all of the communications 

parameters required to initiate a pass-through session to a specific customer system. 

These definitions are then attached to the customer system and used to select the 

actual devices on the remote system. This includes support for TCP/IP or SNA 

distribution. 

You can also define the parameters required for bulk transfer of data on tape. 

Work with Media Panel 

From Work with Media you can create, change, copy, delete, and display media 

definitions. 



Working With System Types 

System types are associated with customer systems and define the type of computer 

systems they have. 

Work with System Types Panel 

The standard options on the Work with System Types panel include 1=Create, 

3=Copy, and 4=Delete. 


10=Work with Models, displays the Work with System Models panel 

with options to create, copy, and delete system model definitions 

associated with the specified system type. Model definitions are created 

at the system type level. 

11=Work with Operating Systems, displays the Work with Operating 

Systems panel where you can create, change, copy, delete, and display 

operating system definitions associated with a selected system type. 

Operating system definitions are created at the system level and can 

include the system type, operating system and version, and the date the 

version was last supported.

Working With Countries 

Country codes are associated with customer locations. They are for geographic 

informational purposes and are optional. 

Work with Countries Panel 

From option 39, Countries, you can create, change, copy, delete, and display country 

code definitions. 



Working With Customers 

Work with Customers was previously a part of Work with Products. Now as a 

separate menu option, the customer database is expanded with more functionality for 

release management processing. 

This is the primary location for viewing current version information for customers 

and distributing new versions of software. 

Work with Customers Panel 

From option 40, Customers, you can create, change, copy, delete, and display 

customers. You can also work with customer systems, products, product versions, 

and customer contacts. 

Additional options on this panel include: 

10=Work with Systems, to work with the systems associated with the 

customer. It identifies information about their system(s), system 

location, and whether a receiver is installed. 

From work with systems you can work with products and product 

versions, and work with media associated with the customer system. 

You can also start a pass-through communications session for the 

purpose of electronic distribution of software. 

11=Work with Products, to work with the products associated with 

the customer. For more information see “Working With Products” on 

page 34.

Working With Customer Types 

Customer types are associated with customers, and allow you to classify or group 

your customers (for example, by industry or business group). 

Work with Customer Types Panel 

From option 41, Customer Types, you can create, change, copy, delete, and display 

customer types. 


Notes 

64 • SDM-DesignTracker 5.0 User Guide

CHAPTER 4 WORKING WITH SERVICE 

REQUESTS AND DESIGN REQUESTS 

Overview 

Subsetting Service Requests 

This chapter focuses on the tasks related to logging and working with service 

requests and design requests. 

The Subset Service Request panel can initially display when the Work with Service 

Requests function is accessed. Display of this function depends on how, or if, the 

System Administrator has previously determined your subset display capability. 

Depending on the your authority, this allows you to specify selection criteria to 

display only calls associated with specific criteria, or to view default selection criteria 

previously defined for you by the System Administrator. 


System Administrator or you (depending on your subset authority). 

Subset selection criteria can be determined by the System Administrator at the time 

your user profile is defined, or depending on your authority, determined when you 

access the Work with Service Requests function. 

When limiting the display of requests to specific selection criteria, subset criteria 

must be established you in Work with User Profiles, option 7=SR subset values. To 

display the Subset Service Requests panel automatically when Work with Service 

Requests is accessed, the Automatic prompt on subset field in Subset Service 

Requests must be set to 1. 

CHAPTER 4 WORKING WITH SERVICE REQUESTS AND DESIGN REQUESTS • 65


To subset service requests 

1. From the SDM-DesignTracker Menu, type option 6, Work with Service 

Requests, and press ENTER. The Subset Service Requests panel 

displays. 

This option can also be accessed by using the Work with Service 

Requests command DTWRKSR. 

Note: If the Work with Service Requests panel displays, the subset display 

was overridden. 

2. When the first Subset Service Request panel displays: 

Review the default selection criteria and press ENTER to continue 

to the Work with Service Requests panel. 

Or… 

Enter new selection criteria and press PAGE DOWN to continue to 

the second subset panel. 

3. Place the cursor at a field and press F4=Prompt to display a list of valid 

values to choose from. 

4. Press F5=Refresh to redisplay the selection criteria as it appeared when 

the panel was first accessed. 

5. When the second Subset Service Request panel displays: 


to the Work with Service Requests panel. 

Or… 

Enter new selection criteria. Press PAGEUP to redisplay the first 

subset panel if necessary. Prompt, Reset and Refresh functions are 

also available from this panel. 

6. You can choose to override or turn on the automatic display of the 

Subset Service Requests panel. 

7. Press ENTER to process subset information and continue to the Work 

with Service Requests panel. 

8. Press F3=Exit or F12=Cancel to redisplay the previous menu without 

accepting changes.

Subset Service Requests Task Variations 

Once you have accessed Work with Service Requests, you can change the current 

subset criteria or define a new subset using specific comparison criteria 

To change the current standard subset criteria: 

1. Press F17=Subset to display the Define Subset panel. 

2. Select Record Selection by typing a 1 in the Opt field and pressing 

ENTER. The Subset Service Request panel displays with the current 

standard default subset information. 

To define or change custom subset criteria: 

1. Press F17=Subset to display the Define Subset panel. 

2. Select Extended Record Selection by typing a 1 in the Opt field and 

pressing ENTER. The Select Records panel displays. 

3. Enter the subset comparison criteria required to display service 

requests. You can use F4=Prompt on any field to display a list of valid 

values for Fields, Tests, Values, or And/Or. 

Note: This function allows you to create subsets using a wide range of 

comparison values, as well as the and/or logic to create expressions that 

have more than one character string. 

4. Once you have created your subset criteria, press ENTER. The system 

validates the subset criteria and displays the Define Subset panel. 

5. Press ENTER again to display the service request list based on the 

custom subset selection criteria. 


Creating a Service Request 


This task is used to create service requests. It is used to manage and control service 

requests logged for enhancement requests, requests for services, and other internal or 

external requests that need to be tracked. 

This is a required task when using SDM-DesignTracker. It is a task typically 

performed by a programmer, project leader, or SDM-DesignTracker user. 

After the SDM-DesignTracker administrator and setup functions are established and 

service request and design request approval guidelines are determined, you can begin 

to process requests using the basic functions programs. 

To create a service request: 

1. From the SDM-DesignTracker Menu, type option 6 and press ENTER 

to display the Work with Service Requests panel. 

This task can also be accessed by using the Work with Service Requests 

command DTWRKSR. 

Note: If the Subset Service Requests panel displays, the subset display 

option is set to ‘1’ (Yes). See the Subset Service Requests task for further 

information about this function. 

2. On the Work with Service Request panel, type 1 in the Opt field to 

display the Create Service Request panel. 

3. In the Create Service Request panel, the title of the service request is 

the only required information. Other fields that are helpful are: priority, 

status, and the requester company (division or department), and contact. 

4. You can set up the following fields as required and/or needing 

validation in System Control. 

Company 

Division 

Department 

Cost Center 

Priority 

System 

Product 

Component 

Version 

5. You can set the initial values for the following fields in System Control: 

Type 

System 

Status set at approval

6. You can set the initial values for the following fields in the user profile: 

Product 

Component 

Version 


Company 

Divisions 

Department 

Cost center 

Contact 

7. Press ENTER when you complete your edits. The Work with Service 

Requests panel redisplays. 

Once a service request is created, it may be necessary to perform the tasks of 

Approvals and Attach SupportCenter calls. 

Create Service Request Task Variations 

You can also create a service request from an SDM-SupportCenter call. However, 

the call may not be used on more than one service request or design request. 

Note: This function is only available in create mode. 

To create a service request from a 

SupportCenter call: 


to display the Work with Service Requests panel. 

This function can also be accessed using the Work with Service 

Requests command DTWRKSR. 

2. Type 1 in the Opt field to display the Create Service Request panel. 

3. On the Create Service Request panel, press F6=Select Call to display 

the Select Call to Attach panel. 

4. Select a specific call by typing 1 in the Opt field and pressing ENTER. 

Any fields from the call overwrite identical fields on the service 

request. 

5. On the Confirmation Selection of Call to Attach panel, press ENTER. 

The Create Service Request panel redisplays. Notice the information 

from the SDM-SupportCenter call defaults on the corresponding service 

request fields. 

6. Press ENTER when you have complete your edits. The Work with 

Service Requests panel redisplays. 



To copy a service request record: 

Approving Service Requests 

You can also use the copy feature to copy the information from an existing request to 

create a new request. 


to display the Work with Service Requests panel, or type the Work with 

Service Request command DTWRKSR at the command line. 

2. Type 3 in the Opt field of the request to copy and press ENTER to 

display the Create Service Request panel. 

3. Change the title of the selected request to reflect the meaning of the new 

request. The remaining fields can be left to default to the values of the 

original request, or you can change the field values to better reflect the 

requirements of the new request. 

4. Press ENTER when you complete your changes to update the new 

request record. The Work with Service Requests panel redisplays. 

The approval process is the same for service requests and design requests. Both 

request types are referenced in this task. 

This task displays approval and disapproval information for a request. It is also used 

to approve or to disapprove selected service requests or design requests. 

Approvals are necessary for a request to be valid. If there is no Approval List tied to 

the selected request, the system bypasses the Service Request or Design Request 

Approval List panel and automatically displays the Approve/Disapprove panel for 

you to update. 

If approvals are to be used at different levels (companies, divisions, departments, 

systems, costs centers, products, and components), it is necessary to set up the 

approver. To be able to approve everything, you can be set up as an Approval 

Administrator. 

A service request or design request can be approved any time after the request is 

created. For a service request to be processed or a design request to be checked out in 

SDM-Implementer, it must be approved. 

You must be set up as an Approval Administrator or an Approval User in the 

appropriate area (companies, divisions, departments, systems, costs centers, products, 

and components). 

To approve requests: 


to display the Work with Service Requests panel, or type 1 to display 

the Work with Design Requests panel. 

You can also access these tasks by using the Work with Service 

Request command DTWRKSR or the Work with Design Requests 

command DTWRKDR.

Depending on your subset authorities, the Subset Service Request panel 

or Subset Design Request panel may display. Change the selection 

criteria or accept the defaults by pressing ENTER. The Work with 

Service Request panel or Work with Design Request panel displays. 

2. On the Work with Request panel, type 8 in the Opt field to display the 

Work with Approvals panel for the selected request. 

You can identify requests that need to be approved if the Approved for 

Dev, Tst, or Prod fields are set to 2 (Pending). 

Note: For a design request to be approved, three approvals must be obtained. 

In the event that there is no specific user for an approval, in order to bypass 

the approval set the Auto Approve flag to ‘Yes’. For example, if your 

company has an approval user for development and production, but not for 

testing, the Auto Approve function will automatically approve the testing 

approval. 

3. Approve the service/design request: 

You can only approve and/or deny requests that list you as an approval 

user or if you are set up as a sign for approval user for other user 

profiles. In some instances, before you can approve a request, the Add 

Approval panel displays, which allows you to add a new approval user. 

If Auto Approve is off, and you are an Approval Administrator, you can 

add yourself on this panel. Otherwise, only users identified as Approval 

Administrators in the Work with User Profiles function can enter a new 

approval record. 

a) To add an approval, press F6=Create to display the Add Approval 

panel. 

b) Type in or select the user profile. 

c) Complete the Approval type as follows: 

For service requests, the Approval Type will always be 1 

(Development). 

For design requests, the Approval Type identifies if the entities 

associated with a design request can be checked out or 

promoted to a test or production environment in SDM- 

Implementer. Set the approval to a 1 for yes or a 0 for no for 

checkout or promotion. 

d) Optionally type in a reason for the approval or denial of the 

request. 

e) Press ENTER to redisplay the Work with Service Request panel or 

the Work with Design Request panel. 



To change an approval (approve or deny it): 

On the Work with Service or Design Request panel, type 2 in the Opt 

field to display the Change Approval panel. If there are multiple 

approvals needed, repeat the following steps for each approval that is 

necessary: 

a) Set the approval to a 1 for yes (approved) or a 0 for no (not 

approved). 

b) Optionally type in a reason for the approval or denial of the 

request. 

c) Press ENTER to redisplay the Work with Service Request panel or 

Work with Design Request panel. 

Note: In order for a Design Request to be approved, there must be three 

approvals. This first approval is development in the Dev field, the next is 

testing in the Tst field, and the last is production in the Prd field. Each 

approval must be made sequentially. However, for example, if testing 

approves a design request before development, the Tst field still displays as 

2, or pending, even though it was approved. Once development approves the 

design request, the Tst field displays as approved also. 

Attaching SDM-SupportCenter Calls to a Service 

Request 

You can display a list of SDM-SupportCenter calls that have not been previously 

attached to a service request. SDM-SupportCenter calls can be attached to a service 

request for total integration of SDM-SupportCenter and SDM-DesignTracker. Using 

this function allows multiple calls to be attached to a service request at one time. 

This task is an optional task typically performed by a programmer, project leader, or 

end user anytime after a service request is created. 

SDM-SupportCenter and SDM-DesignTracker must be installed and integrated for 

this process to available. 

To attach an SDM-SupportCenter call: 


to display the Work with Service Requests panel or type the Work with 

Service Requests command DTWRKSR at the command line. 

2. Depending on your subset authorities, the Subset Service Request panel 

may display. Change the selection criteria or accept the defaults by 

pressing ENTER. The Work with Service Request panel displays. 

3. On the Work with Service Request panel, type 16 in the Opt field next 

to the request to display the Select Calls to Attach panel.

Subsetting Design Requests 

4. Attach the SDM-SupportCenter call(s) to the service request, by 

performing one of the following options: 

Type 1 in the option field next to the call(s) to attach to the service 

request, or search for specific calls by entering the full or partial 

value at the top of the corresponding column(s). The system 

searches for values that are equal to or greater than the entered 

value and displays the calls for selection. 

Type 5 in the option field next to the call(s) to display the 

corresponding call details. 

5. Press ENTER to accept the selected calls and redisplay the Work with 

Service Request panel. 

The Subset Design Request panel may initially display when the Work with Design 

Requests function is accessed. Display of this function depends on how, or if, the 

System Administrator has previously determined your subset display capability. 

Depending on your authority, subsetting allows you to specify selection criteria to 

display only requests associated with specific criteria or to view default selection 

criteria previously defined for you by the System Administrator. 

This is an optional task typically performed by the SDM-DesignTracker System 

Administrator or you (depending on your subset authority). 

Subset criteria can be determined by the System Administrator at the time your user 

profile is defined, or depending on your authority, determined when you access the 

Work with Design Requests function. 

When limiting display of requests to specific selection criteria, your subset criteria 

must be established in Work with User Profiles, option 6=DR subset values. To 

automatically display the Subset Design Requests panel when Work with Design 

Requests is accessed, the Automatic prompt on subset field in Subset Design 

Requests must be set to 1. 

To subset design requests: 

1. From the SDM-DesignTracker Menu, type option 1 for Work with 

Design Requests, or type DTWRKDR at the command line and press 

ENTER. The Subset Design Requests panel displays. 

Note: If the Work with Design Requests panel displays, the subset display 

was overridden. See the Work with Design Requests task for further 


2. When the first Subset Design Request panel displays: 


to the Work with Design Requests panel. 

Or… 

Enter new selection criteria and press PAGEDOWN to continue to 

the second subset panel. 



3. Place the cursor at a field and press F4=Prompt to display a list of valid 

values to choose from. 

4. Press F5=Refresh to redisplay the selection criteria as it appeared when 

the panel was first accessed. 

5. When the second Subset Design Request panel displays: 


to the Work with Design Requests panel. 

Or… 

Enter new selection criteria. Press PAGEUP to redisplay the first 

subset panel if necessary. Prompt, Reset, and Refresh functions are 

also available from this panel. 

6. You can choose to override or turn on the automatic display of the 

Subset Design Requests panel. 

7. Press ENTER to accept subset information and continue to the Work 

with Design Requests panel. Press F3=Exit or F12=Cancel to redisplay 

the main menu without accepting changes. 

Subset Design Requests Task Variations 

You can change the current subset criteria or define a new subset using specific 

comparison criteria once you have accessed Work with Design Requests. 

To change the current standard subset criteria: 

1. Press F17=Subset to access the Define Subset panel. 

2. Choose Record Selection by entering a 1 in the Opt field and press 

ENTER. The Subset Design Request panel displays the current standard 

default subset information. 

To define or change custom subset criteria: 

1. Press F17=Subset to access the Define Subset panel. 

2. Select Extended Record Selection by entering a 1 in the Opt field and 

pressing ENTER. The Select Records panel displays. 

3. Enter the subset comparison criteria required to display design requests. 

You can use F4=Prompe to display a list of valid values for Fields, 

Tests, Values, or And/Or. 

This function allows you to create subsets using a wide range of 

comparison values, as well as the and/or logic to create expressions that 

have more than one character string. 

4. Once you have created your subset criteria, press ENTER. The system 

validates the subset criteria and displays the Define Subset panel. 

5. Press ENTER again to display the design request list based on the 

custom subset selection criteria.

Creating a Design Request 

This task allows you to create a design request. A design request is a request that is 

used to manage and track software development projects and other types of projects 

(for example, error corrections for a product, enhancement requests, and so forth). 

Product errors are usually associated with SDM-SupportCenter calls, and product 

enhancements are usually associated with service requests. 

Design requests allow you to manage the complete development process. A design 

request brings control to the process of managing system changes for analyzing, 

prioritizing, and turning user requests into designed system changes. The design 

request can tie and copy pertinent information from multiple service requests or 

SDM-SupportCenter calls into a single design. 

This task is a required task when using SDM-DesignTracker, and is typically 

performed by a programmer or project leader. 

Once the SDM-DesignTracker administrator and setup functions have been 

established and service and design request approval guidelines have been determined, 

you can begin to process design requests using the basic functions programs. 

To create a design request: 


to display the Work with Design Requests panel, or type Work with 

Design Request command DTWRKDR at the command line. 

Note: If the Subset Design Requests panel displays, the subset display 

option is set to ‘1’ (Yes). See the Subset Design Requests task for further 


2. On the Work with Design Requests panel, type 1 in the opt field to 

display the Create Design Request panel. 

In the Create Design Request panel, the title of the design request is the 

only required information. Other fields which are helpful are: priority, 

status, development resource, project creation rule (if SDM- 

ProjectMaster is installed), and the requester company (division or 

department), and contact. 

a) You can define the following fields as required and/or needed for 

validation in System Control. 

Company/Division/Department 

Cost Center 

Priority 

System 

Product/Component/Version 

Production environment 

Resource initials. 



b) You can set the initial values for the following fields in System 

Control: 

Type 

System 

Status set at approval 

Requester priority 

Benefits priority 

Development priority 

c) You can set the initial values for the following fields in the user 

profile: 

Product 

Component 

Version 


Company 

Divisions 

Department 

Cost center 

Contact 

3. If SDM-ProjectMaster is installed, a project can be entered or you can 

specify the default value *DRNBR (design request number) which 

creates the project name as DTxxxxx (where xxxxx is the design 

request number). 

4. If using the project leader or development resource, they must be set up 

in the resource master file in SDM-ProjectMaster. 

5. Press ENTER when you complete your edits. The Work with Design 

Requests panel redisplays. 

Once a design request is created, you must, at a minimum, perform the following 

tasks: Approvals and Work with Entities (Create, Add Related, Ready for Check Out, 

and Check Out). You can also attach SDM-SupportCenter calls and/or service 

requests to the design request.

Create Design Request Task Variations 

You can also create a design request from either an SDM-SupportCenter call or an 

existing service request. Neither the call nor the service request can be used on more 

than one design request. The next task creates a design request from an existing 

service request. 

To create a design request from a 

SupportCenter call or service request: 



Design Requests command DTWRKDR at the command line. 

2. On the Work with Design Requests panel, type 1 in the Opt field to 

display the Create Design Request panel. 

3. On the Create Design Request panel, press F7=Select SR to display the 

Select Service Request to Attach panel. 

Note: The F7=Select SR function is only available in create mode. 

4. Select the request by typing 1 in the Opt field and pressing ENTER. 

Any fields from the service request overwrite identical fields on the 

design request. 

5. On the Confirmation Selection of Service Request to Attach panel, 

press ENTER. The Create Design Request panel redisplays with the 

information from the service request filled in on the design request. 

In the Create Design Request panel, the title of the design request is the 

only required information. Other fields which are helpful are: priority, 

status, development resource, project creation rule (if SDM- 

ProjectMaster is installed), and the requester company (division or 

department) and contact. 

6. Press ENTER once you have completed your edits. The Work with 

Design Requests panel redisplays. 

To copy a design request record: 

You can also use the copy feature to copy the information from an existing request to 

create a new request. 


to display the Work with Design Requests panel, or type the Work with 

Design Requests command DTWRKDR at the command line. 

2. Type 3 in the Opt field of the request you want to copy and press 

ENTER to display the Create Design Request panel. 

3. Change the title of the selected request to reflect the meaning of the new 

request. The remaining fields can be left to default to the values of the 

original request, or you can change the field values to better reflect the 

requirements of the new request. 

4. Press ENTER when you complete your changes to update the new 

request record. The Work with Design Requests panel redisplays. 


Bulletin Board 


This task displays a bulletin board that allows you to enter or respond to questions 

from SDM-SupportCenter personnel about the selected design request. This is 

particularly helpful when a call is attached to a design request to aid communication 

of information to the support personnel. 

This is an optional task typically performed by a project leader or programmer 

whenever a question arises or information needs to be updated. 

SDM-SupportCenter needs to be installed for this functionality. 

To use the bulletin board: 



Bulletin Board command DTWRKDR at the command line. 

2. On the Work with Design Requests panel, type 13 in the Opt field to 

display the Bulletin Board panel. 

3. Type in the necessary comments and press ENTER. 

This panel allows input of narrative information about or for a specific 

design request (maximum 999 lines of input). This multiple line entry 

text provides a place for SDM-SupportCenter personnel who have the 

correct authority to add (but not update) text associated with the design 

request. You must have update authority to maintain the text. 

Lines can be inserted or rearranged by selecting F8 and typing over the 

sequence numbers. If a + displays in the bottom right corner of the 

panel, additional text lines are available for viewing. Use the Roll keys 

to display additional lines of text.

Attaching SDM-SupportCenter Calls to a Design Request 

Displays a list of SDM-SupportCenter calls that have not been attached to a design 

request. SDM-SupportCenter calls can be attached to a design request for total 

integration of SDM-SupportCenter and SDM-DesignTracker. 

Using this function allows multiple calls to be attached to a design request at one 

time. Attaching an SDM-SupportCenter call to a design request allows the requester 

to track the current status of the request. 

This is an optional task typically performed by a programmer, project leader, or end 

user anytime after a design request is created. 

SDM-SupportCenter and SDM-DesignTracker must be installed and integrated for 

this functionality. 

To attach SDM-Support Center calls: 


to display the Work with Design Requests panel, or enter Work with 

Service Requests command DTWRKSR at the command line. 

Depending on your subset authorities, the Subset Design Request panel 


pressing ENTER. The Work with Design Request panel displays. 

2. On the Work with Design Request panel, type 16 in the Opt field next 

to the request to display the Select Calls to Attach panel. 

3. Attach the SDM-SupportCenter call(s) to the design request: 

Type 1 in the option field next to the call(s) to attach to the design 

request, or search for specific calls by entering the full or partial 

value at the top of the corresponding column(s). The system 

searches for values that are equal to or greater than the entered 

value and displays the calls for selection. 

Or… 

Type 5 in the option field next to the call(s) to view the 

corresponding call details. 

4. Press ENTER to accept the selected calls and redisplay the Work with 

Design Request panel. 

Note: You can use option 17=Display calls to display a list of SDM- 

SupportCenter calls that are attached to the selected design request. 


Q. Is there a limit to the number of SDM-SupportCenter calls that can be attached to 

a single design request? 

A. No. 


Attaching Service Requests to Design Requests 


This function displays a list of service requests that have not been previously attached 

to a design request. It allows multiple service requests relating to the same type of 

condition to be tied to a design request for processing. This allows the status of the 

request to be reviewed at any time during the design and implementation process. 

This is an optional task, typically performed by a programmer, project leader, or end 

user anytime after a design request is created. The service requests must be defined to 

SDM-DesignTracker. 

To attach a service request to a design 

request: 


to display the Work with Design Requests panel, or enter DTWRKSR at 

the command line. 

Depending on your subset authorities, the Subset Design Request panel 


pressing ENTER. The Work with Design Request panel displays. 

2. On the Work with Design Request panel, type 18 in the Opt field next 

to the design request to display the Select Service Requests to Attach 

panel. 

3. Attach the service request(s) to the design request. 

Type 1 in the option field next to the service request to attach to 

the design request, or search for specific service request by 

entering the full or partial value at the top of the corresponding 

column(s). The system searches for values that are equal to or 

greater than the entered value and displays the service requests for 

selection. 

Or… 

Type 5 in the option field next to the service request(s) to access 

the Display Service Request panel to review the corresponding 

service request details. 

4. Press ENTER to accept the selected service requests and redisplay the 

Work with Design Request panel. 

Note: You can use option 19=Display SRs to display a list of service 

request that are attached to the selected design request. 


Q. I requested option 18 to attach service requests to the design request, but received 

an error message stating “No items to display”. Why? 

A. One of two conditions may exist: All existing service requests have already been 

attached to design requests, or service requests have been logged but not approved.

CHAPTER 5 SDM-IMPLEMENTER 

INTERFACE 

Overview 

This chapter covers the tasks required to create an entity list and check out entities 

for a selected design request. Entities can be selected and checked out through SDM- 

Implementer or SDM-DesignTracker. Both options are explained here. The following 

tasks are covered in this chapter: 

Work with Entities - Check Out from SDM-DesignTracker explains 

how to select a design request, and create and check out the entity list 

directly through SDM-Implementer. This function automatically 

incorporates the following tasks. Therefore, if entities are created in this 

manner, the remaining tasks do not have to be completed. 

Work with Entities - Creating an Entity List describes how to create 

an entity list in SDM-DesignTracker. 

Work with Entities - Adding Related Entities describes how to select 

related objects for an entity. 

Work with Entities - Ready for Check Out explains how to identify 

entities that are ready for check out. 

Note: Design requests must be approved before entities can be checked out 

or promoted to a test or production environment in SDM-Implementer. 

Creating an SDM-Implementer Project in SDM-DesignTracker 

explains the various ways to create an SDM-Implementer project within 

SDM-DesignTracker. 

Using Release Control describes how to set up and use the release 

control features of SDM-Implementer’s release management for 

internal software configuration and control. 

CHAPTER 5 SDM-IMPLEMENTER INTERFACE • 81

Working With Entities - Check Out From SDM- 

DesignTracker 


This task allows you to add and check out entities through SDM-Implementer from 

within SDM-DesignTracker. 

When you check out using this task, the SDM-DesignTracker design request is linked 

with the SDM-Implementer check out information and promotion requests. It also 

allows the integration of SDM-DesignTracker for project creation and project 

tracking through SDM-ProjectMaster. 

This is a required task when using SDM-DesignTracker. A programmer or project 

leader typically performs the check out from SDM-DesignTracker after the design 

request is approved and programming is ready to begin. 

SDM-DesignTracker must be installed. The design request must be created and 

approved. The entity must be ready to check out with option 8 on the Work with 

Entity list panel in SDM-DesignTracker. 

Note: The term entity is used in SDM-DesignTracker for specified member/objects. 

To work with entities and check out from SDM- 

DesignTracker: 

1. Verify the design request is approved before checking out any entities. 

Also, the selected design request must be at a status that allows check 

out. 

2. On the Work with Design Requests panel, type 12 in the Opt field of 

the Design Request to display the Work with Entity List Member panel. 

The disposition field for a newly created Design Request defaults to 0. 

3. On the Work with Entity List Member panel, press F20=Create IM 

Project. The following message displays: 

“Implementer project DTxxxxx has been created.” 

The xxxxx represents the design request number you are currently 

working on. 

4. Type option 9 to display the SDM-Implementer Check Out main panel 

to check out the selected entity. The member/object and object type 

default from the design request. Enter the required member/objects 

using one of the following options: 

by pressing F4 or filter by object with F8 

using PathFinder 

using Abstract/Probe+ 

Note: The default production environment must be created in the SDM- 

DesignTracker function Work with User Profiles in order for the correct 

‘From’ environment to be available in the Check Out main panel.

5. On the Check Out main panel, press ENTER to verify the entries. The 

following message displays: 

“Press F9=Accept to check out.” 

6. Press F9=Accept to check out the entity and redisplay the Work with 

Entity List Members selection panel. 

Notice that the Disp field on the Work with Entity list panel is now set 

to 2, indicating that the entity is checked out. 

7. Press F3=Exit to redisplay the Basic Functions panel. 

Building the Entity List in SDM-DesignTracker 

You can create the entities by building the entity list in SDM-DesignTracker, then 

selecting any specific entity with option 9 to check out through SDM-Implementer. 

Building the Entity List Using Abstract/Probe 

From the Work with Entity List Members panel, press F17=Abstract/Probe+, and use 

option IS, IC, or IR. 

Building the Entity List Using Hawkeye 

From the Work with Entity List Members panel, press F18=Hawkeye/Pathfinder, and 

use option IS, IC, or IR. 

Working With Entities - Creating an Entity List 

This option is used by developers or project leaders to create a list of entities 

(programs, files, data areas, job descriptions, and so forth.) that are related to the 

implementation of the design request. 

Entity lists are used by SDM-DesignTracker to indicate the objects that will be 

changed. 

This is a required task if you are using SDM-DesignTracker for checking out objects. 

A Project leader or developer typically performs this task when a design request is 

created or needs to be changed. 

The following steps must be completed prior to using this option: 

Setup must be complete. 

If you are using SDM-Implementer for check out, you must create a 

project through SDM-Implementer. 

The design request must be approved before check out. 



To work with entities and create an entity list: 

This task assumes you are in the Work with Design Requests panel and the design 

request you want to work with exists. 

1. From the Work with Design Request panel, type option 12 to display 

the Work with Entity List Member panel. 

2. Type 1 in the Opt field on the Work with Entity list panel and press 

ENTER. 

3. In the Create Entity List Member, complete the following required 

fields: 

a) Entity 

b) Object code 

c) Action 

d) If you have SDM-Implementer and SDM-ProjectMaster installed, 

complete the Suffix for the PM function and SDM-Implementer 

project fields. Also, if you know the developer, or it differs from 

the resource defined on the design request, complete the 

development resource. 

4. Press ENTER to add the record. 

Note: At creation, the disposition of 0=Not ready is the default⎯you do not 

have to set the disposition. Before the disposition can be set to 1=Ready for 

check out, it must be approved. The following dispositions are set by SDM- 

Implementer: 2=In development, 3=In quality assurance, and 4=Completed. 

5. Specify the appropriate development text. 

6. Press ENTER to add the record. 

7. Press ENTER again to redisplay the Work with Entity list panel.

SDM-DesignTracker to SDM-Implementer 

You can also create the entities by first selecting the specific entity 

(members/objects) through SDM-Implementer. You can then change the entity with 

option 2=Change. 

To select the entity through SDM-Implementer 

for creation: 

1. Type 9 in the option action field at the top of the subfile list, and press 

ENTER to display the SDM-Implementer main Check Out panel. 

Note: If the entities are already selected, select each entity with option 9 

and press ENTER 

2. Enter the member/objects by using one of the following options: 

press F4, or filter by object with F8 

using PathFinder 

using Abstract/Probe+ 

3. Press ENTER to validate your selection and then press F9 to accept the 

member/objects. The Work with Entities panel redisplays. All of the 

member/objects selected are checked out and display on the panel with 

the disposition set to 2=In Development. 

SDM-Implementer to SDM-DesignTracker 

You can also create entities for an existing design request from SDM-Implementer, 

or choose entities on an existing design request for check out in SDM-Implementer 

using F10=Entities on the main Check Out panel. 

To create or choose entities for design 

requests through SDM-Implementer: 

1. On the SDM-Implementer main Check Out panel, position the cursor 

on the Design request number field and press F4 to display the Work 

with Design Requests panel to select an existing request. 

2. Select the request by typing 1 in the Opt field and press ENTER to 

redisplay the SDM-Implementer main Check Out panel. 

3. Press F10=Entities to display the Work with Entities panel in SDM- 

DesignTracker to select an entity. 

4. In the Work with Entities panel, select the entities and press ENTER to 

redisplay the SDM-Implementer main Check Out panel. 

5. Press ENTER to verify your entries, and press F9 to process the entities 

and complete the check out. 

Note: When selecting the design request in step 2, you can also use option 

15=Entities to add the entities to the design request at that time. 



Using Hawkeye/Pathfinder for Entity Selection 

You can also use Hawkeye’s PathFinder to select objects for the entity list. Two steps 

are necessary to use this function: 

1. Build a cross-reference listing of the appropriate libraries. 

2. Use F18=X-ref to perform the selection from within PathFinder. 

Building the Hawkeye Library 

It is necessary to build a view of the Hawkeye library for the cross-reference 

information to be available for selection. The following is a summary of this task. For 

a complete description, see the PathFinder manual. 

To select objects for the entity list using 

Hawkeye’s PathFinder: 

1. Access Hawkeye from the command line, or from the Work with Entity 

List panel, press F18=PathFinder. 

2. In the Hawkeye Overview menu (HAWKOVER) select option 53 to 

display the Hawkeye Setup menu (HAWKSETUP). 

3. Select option 1 to set up your library defaults in the DOCLIBL User 

Values panel. 

4. Type the names of your from environment libraries and press ENTER. 

A message displays stating “Without making changes, 

press ENTER to confirm”. 

5. Press ENTER again to redisplay the Hawkeye Setup menu. 

6. Type option 5 to display the User Defaults panel. In the Object X-Ref 

library field, type the name of the library where you want to store the 

cross-reference information. (You will type this library again when you 

execute the build for the cross-reference list.) 

7. Press ENTER. 

8. Press F3=Exit to redisplay the Hawkeye main menu. 

9. Select option 54, Object X-Ref, to display the Object X-Ref panel. 

10. Select option 1 to build the cross-references list. 

11. Press ENTER to display the Build/Refresh Object X-Ref panel. 

12. Type option 1 next to the libraries you inserted in DOCLIBL User 

Values panel and press ENTER to perform the build. 

13. Type *DOCLIBL and press ENTER. 

14. Type the name of the library you defined in step 6, to store the crossreference 

information, and press ENTER. 

15. Press ENTER again, with the defaults on the Submit panel.

To select objects: 

1. Type option 12 on Work with Design Request Panel to display the 

Work with Entity List Member panel. 

2. Press F18=X-ref to display the PathFinder Main Menu. 

3. At the PathFinder Main Menu, type option 54, Object X-ref, and press 

ENTER to display the PathFinder Object X-ref Menu. 

4. Type option 2=Object where used, and press ENTER to display the 

Object Where Used panel. 

5. Select the appropriate object type, (usually 1=*ALL), and press 

ENTER to display the second Object Where Used panel. 

6. Type the name, generic or *ALL (leave the rest of the defaults), and 

press ENTER to display the third Object Where Used panel. 

7. Type the ID option in the input field at the top (next to the object) and 

press ENTER. This option automatically adds the object to the entity 

list. 

You can use F16=User options to view all user-defined options. 

8. Press F3 twice to redisplay the Work with Entity list panel. The selected 

object displays on this panel. 


Working With Entities - Adding Related Entities 


This function allows you to select all objects or individual objects related to a single 

entity to include on the Check Out selection panel. This information is retrieved from 

either SDM-Implementer, or from PathFinder (using API calls) depending on what 

source of related object information is specified for the ‘From’ environment. 

Adding related objects to a request insures that an object is not promoted that would 

cause a level check in this environment. 

This is an optional function typically performed by a project leader or programmer 

when adding entities to the design request, either at initial creation or when changing 

the design request at a later time. 

If you are using SDM-Implementer this option can be specified only for an object of 

type *FILE. Programs are also available when using PathFinder. To determine the 

source of the related object information, set the required flag in the SDM- 

Implementer Work with Environments option. 

To work with environments and add related 

entities: 

This task assumes you are in the Work with Design Requests panel and the design 

request you want to work with exists. 

1. Select option 12 on Work with Design Request Panel to display the 


2. To add related objects, type 7=Add related, in the Opt field on the 

Work with Entity list panel, and press ENTER to display the Select 

Related Objects panel. All of the objects are pre-selected with 1. 

3. Press ENTER to accept. The Select Related Objects panel displays. 

4. Press ENTER again to confirm the objects and redisplay the Select 

Related Objects panel. 

5. Press ENTER again to redisplay the Work with Entity list panel. 

6. Press F3=Exit to redisplay the main menu. 

Add Related Entities Task Variations 

This task variation is carried out the same way, except that you must specifically 

select the objects from the Select Related Objects panel. 

1. Select option 12 on Work with Design Request Panel to display the 


2. To add related objects, type 6=Dsp related, in the Opt field on the 

Work with Entity list panel and press ENTER. The Select Related 

Objects panel displays. 

3. Select the objects by typing 1 in the option field, and press ENTER 

once to accept. The Select Related Objects panel displays. 

4. Press ENTER again to confirm the objects and redisplay the Select 

Related Objects panel. 

5. Press ENTER again to redisplay the Work with Entity list panel. 

6. Press F3=Exit to redisplay the main menu.

Working With Entities - Ready for Check Out 

This option is used by developers to ready a list of entities (programs, files, data 

areas, job descriptions, and so forth) for check out by setting the disposition to 1. 

This option allows you to create SDM-Implementer projects and to notify the 

programmer that the entities are available for check out, if you are going to use 

SDM-DesignTracker for checking out objects. 

A project leader or programmer typically performs this function when a design 

request is ready to be implemented. 

This task assumes you are in the Work with Design Requests panel, the design 

request you want to work with exists, an entity list is created with the disposition of 

0=Not ready, and the request is approved. 

To work with entities and be ready for 

checkout: 

1. Select option 12 on Work with Design Request panel to display the 


2. If an entity is ready to be checked out the disposition is set to 1. To 

ready a newly created entity, type 8 in the option field on the Work 

with Entity list panel for each entity and press ENTER. This readies the 

entity for check out and sets the disposition from 0 (zero) to 1. 

Note: Before the disposition can be set to 1=Ready for check out, it must be 

approved. This applies to design requests also. 

3. Press F3=Exit to redisplay the main menu. 

Ready for Checkout Task Variations 

You can ready the entity for check out at the time of creation in the second Create 

Entity List Member panel by typing disposition 1=Ready for check out. 


Creating an SDM-Implementer Project in 

SDM-DesignTracker 


This option creates a project in SDM-Implementer. The project number includes the 

design request number and the entity number. 

If you are using project tracking, projects must be created before you can check out 

or create promotion requests. This function creates the project; it does not assign the 

project (as a user default). An administrator must view Work with Projects to 

determine the project number and then assign the default project in Work with User 

Profiles. 

This task is only required if project tracking is implemented. A project leader or 

developer typically creates the project before check out is performed or a promotion 

request is created. 

To create an SDM-Implementer project in SDM- 

DesignTracker: 


to display the Work with Design Requests panel, or type the Work with 

Design Request command DTWRKDR at the command line. 

2. Select the design request with option 12=Work with Entity list and 

press ENTER to display the Work with Entity List panel. 

If an entity list does not exist and you need to create it, press 

F8=Crt/Upd PM Project on the Work with Entity List panel. A message 

displays stating 

“Implementer project DTxxxxx has been created” 

The xxxxx represents the design request number you are working on. 

3. Press F12=Cancel to redisplay to the Work with Design Requests panel. 

Work With Project Tasks Task Variations 

1. From the Work with Design Requests panel, select a design request 

with option 20 and press ENTER to display the SDM-Project Master 

Work with Tasks panel. 

For a complete description of this panel, see the “Working with Tasks” 

section of the SDM-ProjectMaster User Guide. 

Some of the tasks that can be performed are: create, change, copy, 

display, override, allocate, de-allocate, view history, view estimates, 

and view the calendar. 

2. Press F3=Exit to redisplay the Work with Design Requests panel.

Working With Design Request Entities 

This option displays design requests and their related entities that are created in the 

Work with Entity Members function. A single design request can be associated with 

multiple entities. 

Use this option to change or review an existing design request entity record, produce 

a hard copy report of a specific design requests entity, or to review the design request 

associated with an entity. 

This is an optional task. A project leader typically performs this task when required 

or when information is needed. 

A design request subset must be determined in Work with User Profiles (option 

6=DR subset values) for users who do not have subset authority. 

To work with design request entities: 


to display the Work with Design Request Entities panel, or type the 

Work with Design Request Entities command DTWRKDRE. 

2. From the Work with Design Request Entities panel, select the design 

request with the option number corresponding to the function you want 

to perform, as follows: 2=Change, 5=Display, 6=Print, 8=Design 

Request or 12=Entity List. 


Using Release Control 


Release control is a component of release management. Release management is a 

comprehensive SDM-Implementer change management solution that allows you to 

successfully manage and control your entire network of software, from in-house 

development to customer distribution. 

Release management functionality consists of two feature sets, release control and 

release deployment. 

Release Control provides additional management control and 

orientation by release name or number for managing internal production 

environments and reviewing release history. SDM-Implementer users 

can continue working in a continuous development model or a fixedversion 

development model which also supports PTFs for each version, 

optimizing developer time and productivity. The benefits of release 

control include software versioning at the product level, and knowledge 

of which products, versions, and releases are under change management 

control. 

Release Deployment is an optional feature that allows SDM- 

Implementer users to manage, track, and deploy software changes by 

client, installed system, licensed product, version number, or PTF, as 

well as check current release status and shipments. Internal and external 

clients have greater control and flexibility over installation of change 

packages, such as user-specified test libraries, scheduled installations 

and control over object owners and authorities. 

Note: This section addresses the release control feature of release management. For 

more information about the optional release deployment feature, see the Release 

Management User Guide, or contact your MKS Account Manager at (800) 633-1235.

Release Control Development Scenario 

A typical release control development scenario starts with setting up your products 

and versions, which includes attaching the SDM environments associated with each 

product at the version level. 

You then create an open release (this release should be at a status that allows 

software changes to occur, for example, ENV-OPEN). Any design requests which 

have at least one entity promoted to production while the release is open are attached 

to that release. 

Follow your normal change management procedures for checking out and promoting 

member/objects. 

When you are ready to close a release (for example, to go to system test or 

production) set the release to a status that does not allow software changes (for 

example, ENV-CLOSED). This will disallow any promotions from targeting the 

environments defined for the version which allow standard releases to be created 

from (this flag is set when you attach an environment to a version). Also, by changing 

the status from one that allows software changes to one that does not, you are able to 

capture an image of the SDM-Implementer repository so that you know exactly 

which objects were in the release when you closed it. 

When you are finished with this release, set it to a status where all four status flags 

(allow software change, allow packaging, allow controlled distribution, and allow 

distribute changes) are set to ‘N’ (for example, NOT SUPPORT). By changing the 

release status, you can control movement into production environments. 

You can now create a new open release to allow the standard change management 

cycle to begin again. 

Note: For more information about the release status, see “Working With the Release 

Status” on page 99 and the “Release Status Configuration, Table of Default Values” 

within that section. 

Change Management Scenario 

Development 

Promote 

Test 

Check Out 

Promote 

Production 

Example Releases 

Inventory 4.1 

Inventory 4.2 

Inventory 4.3 

Inventory 5.0 



Setting Up for Release Control 

Release control draws on the seamless integration of SDM-Implementer and SDM- 

DesignTracker. SDM-Implementer controls the environments and change 

management operations, with release control processing transparent to you. The 

SDM-DesignTracker user-interface includes working with products, versions, 

releases, release types, release status, and interactive processes. 

In most cases, the implementation of release control requires minimal setup to your 

existing configuration, allowing you to quickly apply release control to your change 

management operation. 

The additional data elements and tables required for release control processing 

include: 

Notes: 

SDM environments 

Products 

Versions 

Releases 

Release Types 


Follow the steps described in Chapter 3 of the SDM-Implementer System 

Administrator Guide for defining SDM environments. No special considerations 

are required when defining environments for release control. 

User profiles must have authority to work with products and versions. This is 

defined in SDM-Implementer, Work with Users. The ‘Maintain Products’ flag 

and the ‘Maintain Versions’ flag must be defined as ‘Y’ for each user who will 

maintain product versions. 

All other required data elements and tables are explained in this manual.

Working With Products and Versions 

Follow the steps described in “Working With Products, Components, and Versions” 

in Chapter 3 for setting up product versions and releases. 

Attaching SDM Environments to a Product Version 

Product version definitions refer to one or more SDM environments. When you set 

up product versions, you attach the SDM environment(s) associated with each 

product at the version level. 

The release management function uses the environment(s) referenced for a product 

version to determine the location of software items that need to be included in a 

specific release within a product version). 

In addition, the SDM-Implementer promotion process checks to see if the ‘To’ 

environment of the promotion request is attached to a product version. SDM- 

Implementer will only allow a promotion request to be promoted into an environment 

attached to a product version if the product version has an ‘Open Release’. If the 

product version does not have an open release, the promotion request will result in a 

‘Move-Fail’ status. This method ensures that the SDM environments that the product 

releases are created from can be frozen until the product manager decides to open a 

new release. 



Understanding the Software Release Process 

Configuration 

The software release process configuration determines the development path that 

each release must follow. 

The software release process configuration consists of: 

release types 

release status 

Working With Release Types 

Release types define the types of releases you manage. For ease of use, release types 

are user-defined so that the terminology you currently use for identifying releases can 

be reflected in the release control process. 

Release Categories 

Release types are in two different categories⎯standard (STD) and program 

temporary fix (PTF). The release category, along with the release status, determines 

the development path that a release must follow. It also determines the dependency 

that is automatically associated between a current release and a previous release. 

Both STD and PTF releases automatically default to being dependent on the previous 

STD release; however, STD releases are not dependent on previous PTF releases. 

This method of dependency allocation automatically insures that the software items 

in a STD release can not be installed without first installing the software items in the 

previous STD release. It also supports selective PTFs. For example, PTF releases can 

installed without other PTF releases (impacting different objects built over the same 

STD release) also being installed. However, if two PTFs impact a common object, a 

PTF dependency is automatically created to insure that dependent changes are never 

missed. 

Note: This is the default dependency configuration. You can create other userdefined 

dependencies if needed.

To create release types: 

1. From the SDM-DesignTracker menu select option 20, Setup Menu. 

2. From the Setup Menu, select option 35, Release Types. The Work with 

Release Types panel displays. 

3. Type 1 on the first option line and press ENTER. The Release Type 


Release Type Maintenance Window 

4. Complete this panel as defined next in “Release Types Maintenance 

Field Descriptions” and press ENTER. 



Release Types Maintenance Field Descriptions 

Release Type 

The release type is a user-defined variable that defines the types of releases you 

manage. This is a ten character alphanumeric field. 

Type Description 

Use this field to include a narrative about the release type. This is a 40 character 

alphanumeric field. 

Release Category 

The release category determines the path that a release must follow. It also 

determines the dependency that is automatically associated between a current release 

and a previous release of software. 

STD A STD release is typically created on a periodic basis (weekly, monthly, 

quarterly, or adhoc) by a product/development manager. This category is 

the standard deliverable that is provided by development over a period of 

time. It typically contains a collection of software changes and 

enhancements that have been promoted into the product version 

environment over the period of time that the release was built. The STD 

category represents a cumulative set of software changes. This is the 

default value. 

PTF A PTF category release contains software items for a specific change. 

This category is typically defined by a developer, and corresponds to a 

specific problem and/or enhancement. The PTF category represents a 

single software change.

Working With the Release Status 

The software release process configuration associates release types and categories to 

the release status. 

The release status defines the path a release must follow before it can be changed to 

the next available status. It also defines the functions that can or can not be 

performed to the release during each phase of the cycle. This stage progression is 

typically controlled by someone with software product management responsibility. 

The release status controls four functions: 

Allow Software Changes controls whether software can be promoted 

into the environments attached to the product version. 

Allow Create Package controls whether packages can be created. 

Allow Controlled Distribution controls whether the release is 

available for selection to distribute to a customer system, but does not 

become a default release. 

Allow Distribute Changes controls whether this release can be the 

default release to distribute to a customer system as the most current 

release available. 

The options and defaults associated with the release status are described in “Release 

Status Maintenance Field Descriptions” on page 102. 

The release status is associated with an ordered sequence, for example, 10, 20, 30, 

40, 50, and so forth. A release type is required to flow through each associated status 

to make it available for a delivery. (However, in release control you bypass 

sequences 30, 40, and 50 because package creation is not performed.) 

The next illustration defines the default release status configuration for STD and PTF 

releases. It defines the functions that can or can not occur during each phase of the 

cycle. For example, by changing the release status to PKG-CRT automatically closes 

the environment (thereby freezing it from subsequent promotions) and is the only 

status that allows a package to be created. 

Category Sequence Status Description Software 

Change 

Package 

Create 

Controlled 

Distribution 

General 

Distribution 

PTF 10 BETA Beta Release N N Y N 

PTF 20 GA General 

Availability 

N N N Y 

STD 10 ENV- 

OPEN 

STD 20 ENV- 

CLOSE 

STD 30 PCKG- 

CRT 

Environment 

Open 

Environment 

Closed 

Create 

Package 

Y N N N 

N N N N 

N Y N N 

STD 40 BETA Beta Release N N Y N 

STD 50 GA General 

Availability 

N N N Y 

STD 70 NOT 

SUPPORT 

Not 

Supported 

Release Status Configuration, Table of Default Values 

N N N N 



Release Management Development Cycle 

Unit of Time 

Creating 

Release 1 

1……….5…..….10 

Software 

Changes 

Allowed 

Release 1 Open 

Preparing 

to close 

Release 1 

…15… 

No 

Changes 

Allowed 

Release 1 Closed 

(Release and objects frozen 

Release 2 

Opened 

20………25……..30 

Software 

Changes 

Allowed 

Release 2 Opened 

Release 1 set to General Availability 

Note: This development cycle does not prevent starting new development, but 

controls when the objects are promoted back to production. Release management 

supports both single version and multiple version development models.

To work with the release status: 



2. Select option 36, Release Status, and press ENTER. The Work with 

Release Status panel displays. 

Work with Release Status Panel 

Work with Release Status Options 

The standard options on the Work With Release Status panel include 2=Change, 

3=Copy, 4=Delete (a release status can be deleted only if existing release 

dependencies are not associated with it), and 5=Display. 

Each of the options on this panel display the Release Status Maintenance window. 

When processing any of these options, refer to the “Release Status Maintenance Field 

Descriptions” beginning on page 102. 



Creating or Changing a Release Status 

The default release status configuration provided with release management is rarely 

modified except to change the status name. 

Warning: MKS does not recommend changing the default release status values 

without first discussing with an MKS Product Support Specialist. By 

incorrectly changing these values, it is possible to setup a meaningless process 

that can not be followed. If the release status must be changed, be sure to test 

the complete release lifecycle before attempting to use it in a “live” scenario. 

To create a release status: 

1. From the Work with Release Status panel, press F6=Add. The Release 

Status Maintenance window displays. 

Release Status Maintenance Window 

2. Complete this panel as defined next in “Release Status Maintenance 

Field Descriptions” and press ENTER. 

Release Status Maintenance Field Descriptions 

Release Category 

The release category determines the process that a release must follow and the 

dependency that is automatically associated between a current release and a previous 

release. For a description of release categories, see “Release Types Maintenance 

Field Descriptions” beginning on page 98. 

Release Category sequence 

Specify the next available sequence number that is automatically positioned to when 

a release status changes. A release is required to flow through each sequence 

associated with the release category to make it available for a delivery. This is a two 

character numeric field.


Specify the status associated with this release category and sequence. This is a ten 

character alphanumeric user-defined field. 

Status Description 

Use this field to include a narrative about the release status. This is a 30 character 

alphanumeric field. 

Allow Software Changes 

Controls whether software can be promoted into the environment attached to the 


Y The release is “Open” and software can be promoted into the environments 

attached to the product version. 

N The release is “Closed” and software is prevented from promotion into the 

environments attached to the product version. However, promotion requests 

can be created and promoted when a release is later opened. This is the 

default value. 

Allow Create Package 

Controls whether software packages can be created. A package contains the software 

items required to upgrade a product version from a prior release to the current 

release. 

Y Software packages can be created for this release category and sequence. 

N Software packages can not be created. This is the default value. 

Allow Controlled Distribution 

Controls whether the release is available for selection to send to a customer system. 

Y The release is available for selection and can be sent to a customer. 

N The release is not available for selection and currently can not be sent to a 

customer. This is the default value. 

Allow Distribute Changes 

Determines whether this release is the most current default release available that can 

be sent to a customer system. 

Y This is the most current release available to send to a customer. Also allows 

for distribution of changes to occur. 

N This is not the most current release to send to the customer and does not 

allow for distribution of changes. This is the default value. 


Notes 


CHAPTER 6 SDM-DESIGNTRACKER 

COMMAND INTERFACE 

Overview 

The SDM-DesignTracker command interfaces allow you to perform basic SDM- 

DesignTracker functions for one or both of the following situations: 

As a fast path command line interface to perform simple or repetitive 

tasks. For example, a project leader can reassign the development 

resource for a series of design requests to another person, or the system 

operator can create a design request when a batch job ends abnormally. 

As a programming interface to your in-house systems. Design requests 

can be created or changed in batch. For example, if a job runs that 

monitors messages on the QSYSOPR message queue, you can 

automatically create a design request each time an error occurs (such as 

line or device failures). 

The available command interfaces are: 

DTCRTDR - to create a new design request 

DTCHGDR - to change an existing design request 

DTDLTDR - to delete a design request 

DTAPRDR - to approve a design request 

CHAPTER 6 SDM-DESIGNTRACKER COMMAND INTERFACE • 105

Creating Design Requests (DTCRTDR) 


This command allows you to create design requests. The information that you define 

in the command depends on your individual processing requirements. However, if a 

field is identified as a required field in SDM-DesignTracker System Control, it must 

be passed. 

The design request date fields must be entered (or passed, if embedded in a program), 

in YYMMDD format. If the date fields are not currently in this format, they must be 

converted to the YYMMDD format before being passed to the command 

Create Design Request (DTCRTDR) Command 

Panel 1 of 3 

This is the first of three panels. 



Parameters, Panel 1 of 3 

Drnumber 

The number that SDM-DesignTracker assigns to design requests. 

Title 

Description of the design request. This information is used for easy identification of 

the design request in selection lists (maximum 30 alphanumeric characters). 

Type 

The type code is associated with the design request.

System 

Name of the computer system the design request is for. 

Product 

The product passed to the design request. 

Component 

Component of the specified product for the design request. 

Version 

This is the version of the specified product. 

Expdate 

Date the requester expects the design request to be completed. This must be in 

YYMMDD format. 

Reqpty 

Priority of the design request. 

Status 

Status code used to track the progress of the design requests. 

Projleader 

The project leader assigned to the design request. The project leader must exist in the 

SDM-DesignTracker Resource Master. 

Developer 

The development resource assigned to each entity in the entity list. The development 

resource must exist in the SDM-DesignTracker resource master. 

Projrule 

The rule used to create a project automatically in SDM-ProjectMaster using the 

entity list associated with the design request. 

Esteffort 

Additional area to store effort that is not entered into the individual members of the 

entity list. Maximum seven numeric characters (with one decimal position). If SDM- 

ProjectMaster is used, option 5, Update SDM-ProjectMaster information, from the 

SDM-DesignTracker main menu updates this field. 


Estcost 


Additional area to store costs that are not entered into the individual members of the 

entity list. Maximum 11 numeric characters (with two decimal positions). 

Estcmpldat 

The current projection for the completion of the design request. If a project is created 

for this design request in SDM-ProjectMaster, option 5, Update SDM-ProjectMaster 

information, from the SDM-DesignTracker main menu uses the latest estimated date 

of completion for all of the tasks associated with the project to update this field. If an 

unscheduled task exists in the project and the date of completion is not known this 

field will be blank. This date must be entered in YYMMDD format. 

Create Design Request (DTCRTDR) Panel 2of 3 

This is the second of three panels. 




Pmprojname 

This is the project name that will be created in SDM-ProjectMaster (maximum seven 

alphanumeric characters) for the design request. *DRNBR is the default. 

Improjref 

This is the project name that will be created in SDM-Implementer (maximum seven 

alphanumeric characters) for the design request. *DRNBR is the default. 

Company 

The name of the company associated with the design request. 

Division 

The division within the specified company the design request is for.

Dept 

The department of the division in the specified company the design request is for. 

Costcntr 

The cost center that will absorb the costs associated with the design request. 

Contact 

The user contact ID for the person at the customer site who is associated with the 


Dupdr 

This is the number of a design request that is similar to the request being passed. 

Reqdate 

Date the design request was requested. Must be entered in YYMMDD format. 

Clsdate 

Date the design request was closed. Must be entered in YYMMDD format. 

Userdef1 

User-defined field value for the design request. Each individual user can define the 

meaning of the user-defined field. 



meaning of the user-defined field. 

Adderr 

Define the action to be taken if edit errors are encountered. 

*YES 

Create a design request regardless of edit errors encountered. 

*NO 

Do not create a design request if edit errors are encountered. 

Benpty 

Assigned code for the priority of attained benefits by completing the design request. 

Devpty 

Assigned code for the priority of development. 

Prdenv 

Define the SDM-Implementer production environment. 



Create Design Request (DTCRTDR) Panel 3 of 3 

This is the third of three panels. 




Dtldesc 

Descriptive information about the design request. Up to 20 lines of information can 

be passed

Changing Design Requests (DTCHGDR) 

The Change Design Request command (DTCHGDR) is used to change existing 

information for a design request. For example, this command can be used to change 

the current status of a design request, the development resources initials, or the 

estimated completion date for a request. 

Change Design Request (DTCHGDR) Panel 1 of 3 

Change Design Request (DTCHGDR) Command 



Drnumber 

Specify the number of the design request to be changed. The maximum is five 

alphanumeric characters. 

Title 

Design request title. The maximum is 30 alphanumeric characters. Set this value to 

*SAME to use the existing field value for the design request. 

Type 

The design request type code. The maximum is two alphanumeric characters. Set to 

*SAME to use the existing field value for the design request. 

System 

Name of the system the design request is for. The maximum is eight alphanumeric 

characters. Set to *SAME to use the existing field value for the design request. 

Product 

The product associated with the design request. The maximum is 10 alphanumeric 




Component 

Component of associated product for the design request. The maximum is 10 

alphanumeric characters. Set to *SAME to use the existing field value for the design 

request. 

Version 

Specify the version of the product. The maximum is 10 alphanumeric characters. Set 

to *SAME to use the existing field value for the design request. 

Expdate 

Date the requester of the design request expects the request to be completed. Must be 

in YYMMDD format. Set to *SAME to use the existing field value for the design 

request. 

Reqpty 

Priority for the design request set by the person requesting it. The maximum is one 

alphanumeric character. Set to *SAME to use the existing field value for the design 

request. 

Status 

Status code used to track the progress of the design requests. The maximum is two 


request. 

Projleader 

The project leader assigned to the design request. The project leader must exist in the 

SDM-DesignTracker resource master. The maximum is three alphanumeric 


Developer 

The development resource assigned to each entity in the Entity List for the design 

request. The development resource must exist in the SDM-DesignTracker resource 

master. The maximum is three alphanumeric characters. 

Projrule 

The rule used to automatically create a project in SDM-ProjectMaster using the 

entity list associated with the design request. The maximum is seven alphanumeric 

characters. 

Esteffort 

Additional area to store effort that is not entered into the individual members of the 

entity list. If SDM-ProjectMaster is used, the batch function Update SDM- 

ProjectMaster information (option 5 from the SDM-DesignTracker main menu) 

updates this field. Maximum seven numeric characters (with one decimal position). 

Set to *SAME to use the existing field value for the design request.

Estcost 

Additional area to store costs that are not entered into the individual members of the 

entity list. If SDM-ProjectMaster is used, the batch function Update SDM- 

ProjectMaster information (option 5 from the SDM-DesignTracker main menu) 

updates this field. Maximum 11 numeric characters (with two decimal positions). 

Estcmpldat 

The current projection for the completion of the design request. If a project is created 

for this design request in SDM-ProjectMaster, specify the batch function. If SDM- 

ProjectMaster is used, the batch function Update SDM-ProjectMaster information 

(option 5 from the SDM-DesignTracker main menu) uses the latest estimated date of 

completion for all of the tasks associated with the project to update this field. If an 

unscheduled task exists in the project and the date of completion is not known this 

field will be blank. Maximum six numeric characters. Set to *SAME to use the 

existing field value for the design request. 


This is the second of three panels. 




Pmprojname 

The project name created in SDM-ProjectMaster for the design request. The 

maximum is seven alphanumeric characters. Set to *SAME to use the existing field 

value for the design request. 

Improjref 

The project name created in SDM-Implementer for the design request. The maximum 

is seven alphanumeric characters. Set to *SAME to use the existing field value for 

the design request. 


Company 


The name of the company associated with the design request. The maximum is 10 


request. 

Division 

The division within the specified company the design request is for. The maximum is 

10 alphanumeric characters. Set to *SAME to use the existing field value for the 


Dept 

The department of the division in the specified company the design request is for. 

The maximum is 10 alphanumeric characters. Set to *SAME to use the existing field 


Costcntr 

The cost center that will absorb the costs associated with the design request. The 

maximum is 15 alphanumeric characters. Set to *SAME to use the existing field 


Contact 

The user contact ID for the person at the customer site who is associated with the 

design request. The maximum is 25 alphanumeric characters. Set to *SAME to use 

the existing field value for the design request. 

Dupdr 

Specify the number of a design request that is similar to the request being passed. 

Maximum 5 numeric characters. Set to *SAME to use the existing field value for the 


Reqdate 

Date the design request was requested. Enter in YYMMDD format. Maximum six 

numeric characters. Set to *SAME to use the existing field value for the design 

request. 

Clsdate 

Date the design request was closed. Enter in YYMMDD format. Maximum six 

numeric characters. Set to *SAME to use the existing field value for the design 

request. 



meaning of the user-defined field. The maximum is 10 alphanumeric characters. Set 

to *SAME to use the existing field value for the design request.



meaning of the user-defined field. The maximum is 10 alphanumeric characters. Set 

to *SAME to use the existing field value for the design request. 

Chgerr 

Define the action to be taken if edit errors are encountered. Specify *YES to change 

the design request if edit errors are encountered. Specify *NO if you do not want to 

change the design request if edit errors are encountered. 

Benpty 

Assigned code for the priority of attained benefits by completing the design request. 

Devpty 

Assigned code for the priority of development. 

Prdenv 

Specify the SDM-Implementer production environment. 


This is the last panel of this command. 




Dtldesc 

Descriptive information to add to the current design request narrative. Narrative text 

is added at the bottom of the current narrative text. Up to 20 lines of information can 

be added. 


Deleting Design Requests (DTDLTDR) 


This command allows you to delete design requests. There is one panel to the 

command. 

Delete Design Request (DTDLTDR) Command 

Delete Design Request (DTDLTDR) Command 

Parameters 

Drnumber 

The number of the design request to be deleted. Maximum five numeric characters. 

Approving Design Requests (DTAPRDR) 

The Approve Design Request (DTAPRDR) command is used to set the approval for 

a design request. There is one panel to this command. 

Approve Design Request (DTAPRDR) Command

Approve Design Request (DTAPRDR) Command 

Parameters 

Drnumber 

Number of the design request to assign approval information. Maximum five numeric 

characters. 

Userid 

User profile ID of the approval user for the design request. The maximum is 10 

alphanumeric characters. 

Apprvltype 

Approval type for the design request. 

1=Dev Design request approved for entities to be checked out in SDM- 

Implementer. 

2=Tst Design request approved for entities to be promoted to a test 

environment in SDM-Implementer. 

3=Prd Design request approved for promotion to a production 

environment in SDM-Implementer. 

Approval 

Message Considerations 

Approval code for the design request. 

0=No User does not approve the design request. 

1=Yes User approves the design request. 

2=Pending Design request has not been approved or disapproved. 

The command interfaces to SDM-DesignTracker perform the same edit checks as the 

panel interfaces (for example, checking for required fields, valid values, and so 

forth). If an error is found, an error message is produced in the job log. (When 

executed from a command line, these error messages can also display on the error 

message sub-file on the bottom of the panel.) If no edit errors are encountered, a 

message displays indicating that the design request was created, changed, and so 

forth. 

If you request that the design request be created or changed regardless of the errors 

encountered (the ADDERR and CHGERR keywords), error messages still display in 

your job log. However, you also receive the message that the design request was 

created or changed. 

When using these commands within user-written programs, any edit error messages 

are returned to the program as diagnostic messages. If the design request is 

successfully created, changed, and so forth, an informational message is returned to 

your program. However, if the design request is not created, changed, and so forth, 

an escape message is sent back to your program. These escape messages are in the 

VDT3000 range. Be sure to monitor for these messages. 


Controlling the Use of ADDERR and CHGERR 

Parameters 


The ADDERR parameter on the Create Design Request command (DTCRTDR) and 

the CHGERR parameter on Change Design Request command (DTCHGDR) allow 

you to create or change the design request even if errors in the editing process are 

encountered. 

If this is required, the data area DTAPIERR must be changed to the value *ALLOW. 

The default value of this data area is *NOALLOW which disregards the specification 

on the commands. 

You must have authority to change the data area in the product library to control this 

feature. 

Creating Design Request and Approval Records 

Any created design request must have at least one approval record associated with it. 

Therefore, when the Create Design Request command (DTCRTDR) creates a new 

design request, it also writes an approval record pending approval status with the user 

ID of the person creating the design request. The design request itself is then in 

approval pending status. The approval status of the design request can be changed 

through the Approve Design Request command interface (DTAPRDR) or the panel 

interface. 

Retrieving the Design Request Number 

When the Create Design Request command (DTCRTDR) is used from a command 

line, the number of the newly created design requests displays as a message to you. 

When this command is used within a program, this message must be received from 

the program message queue after the command is issued and the design request 

number extracted from the message data field. 

To illustrate this: 

/* THE DR HAS BEEN CREATED OK; THE NUMBER OF THE DESIGN REQUEST */ 

/* CREATED IS CONTAINED WITHIN THE MSGDTA OF THE MSG VDT3000. */ 

RECV: RCVMSG MSGQ(*PGMQ) MSGTYPE(*LAST) RMV(*NO) + 

MSGDTA(&MSGDTA) MSGID(&MSGID) 

/* DR# MESSAGE FOUND; EXTRACT THE NUMBER ASSIGNED AND RETURN IT */ 

IF (&MSGID *EQ 'VDT3000') THEN(DO) 

CHGVAR &DRNUMBER %SST(&MSGDTA 5 5) 

ENDDO

CHAPTER 7 UTILITIES 

Overview 

This chapter describes the reporting capabilities and update procedures used to 

update SDM-DesignTracker information to SDM-ProjectMaster. 

Printing the Service Request Standard Report 

The standard report is used to create a service request report. The Print Service 

Requests selection criteria directly reflects your default subsetting information 

defined in the Work with User Profiles panel, option 7=SR subset values, or can be 

based on a custom subset defined in Select Records. 

Access to subset fields depends on your subset authority. If your subset authority in 

Work with User Profiles is set to 1, default subset information can be changed. If 

your subset authority is set to 0, you only have access to the fields not restricted by 

your subset defaults. 

Use this option to produce a hard copy report of selected service requests. Typically, 

a project leader generates this report when the information is needed. 

A service request subset must be determined in Work with User Profiles (option 

7=SR subset values) for users who do not have subset authority. 

To print a service request standard report: 

1. From the SDM-DesignTracker menu, type option 7 and press ENTER 

to display the Define Subset panel. 

The Define Subset panel allows you to select the type of subset to apply 

to run the report. There are two available subsets to select from: 

Record Selection accesses the Print Service Requests Standard 

Report subset panel. This subset allow you to change the standard 

subset selection criteria. Go to step 2 if you want to select this 

report subset. 

Extended Record Selection accesses the Select Records panel. 

This subset allows you to create customized subset selection 

criteria using a wider range of information. Go to step 3 if you 

want to customize the report subset. 

CHAPTER 7 UTILITIES • 119


Note: Whether you are using the Record Selection or Extended Record 

Selection subset to create your report, the system defaults to the values 

established the last time the report was submitted. If these are the parameter 

requirements needed for the report, you can press ENTER and submit the 

report without accessing and viewing each panel (you can press ENTER to 

submit the report from any of the Service Request Report panels). 

2. The Print Service Requests Standard Report function consists of two 

panels. Information on these panel include: 

a) The subset values established in Work with User Profiles panel 

option 7=SR subset values. Your ability to change the default 

values depends on your defined subset authority. 

b) Identify the report parameters. Accept the subset defaults, or if 

your authority permits, identify specific selection criteria for this 

report. Determine if the report is submitted to batch or run online 

(system default is 1 to submit to batch). 

c) After all report requirements are determined, press ENTER to 

submit the report and redisplay the SDM-DesignTracker main menu. 

3. The Select Records function allows you to create a report using specific 

selection criteria with “And/Or” comparison functionality. 

a) Enter the name of the field(s) you want to search. You can press F4 

on this field to choose from a list of valid field names. 

b) Select the Test parameters to compare the field with a specific 

value. You can press F4 on this field to choose from a list of valid 

Test parameters. 

c) Enter the value you want to search for in the selected field. You 

can enter a specific value or press F4 to select from a list of valid 

values for the selected field. 

d) Use the And/Or field to identify how the values are searched when 

the expression contains more than one character string. For 

example, if you want to search for all requests that have a status 

code of pending and an expected date of 950220, or you want to 

include all requests for customer ABC or that have a status code of 

AP (approved). 

There is no limit to the number of And/Or string comparisons that 

can be entered. However, use caution when selecting your 

comparisons⎯too many comparisons can create a blank report. 

e) Once all report requirements are determined, press ENTER to 

submit the report. The system first validates the selection criteria 

and redisplays the Define Subset panel. 

f) Press ENTER again to submit the report and redisplay the SDM- 

DesignTracker main menu.

Printing the Design Request Standard Report 

The standard report is used to create a design request report. The Print Design 

Requests selection criteria directly reflects the default subsetting information defined 

in you in the Work with User Profiles panel option 6=DR subset values, or can be 

based on a customer subset defined in Select Records. 

Access to subset fields depends on your subset authority. If your subset authority in 

Work with User Profiles is set to 1, default subset information can be changed. If 

your subset authority is set to 0, you only have access to the fields not restricted by 

your subset defaults. 

Use this option to produce a hard copy report of specific information about design 

requests. A project leader typically does this when the information is needed. 

A design request subset must be determined in Work with User Profiles option 6=DR 

subset values for users who do not have subset authority. 

To print a design request standard report: 


to display the Define Subset panel. 


to run the report. There are two available subsets to select from: 

Record Selection accesses the Print Design Requests Standard 

Report subset panel. This subset allows you to change the 

standard subset selection criteria. Go to step 2 if you want to 

select this report subset. 

Extended Record Selection accesses the Select Records 

panel. This subset allows you to create customized subset 

selection criteria using a wider range of information. Go to 

step 3 if you want to customize the report subset. 

Note: Whether using the Record Selection or Extended Record Selection 

subset to create your report, the system defaults to the values established the 

last time the report was submitted. If these are the parameter requirements 

needed for the report, you can press ENTER and submit the report without 

accessing and viewing each panel (you can press ENTER to submit the 

report from any of the Design Request Report panels. 

2. The Print Design Requests Standard Report function consists of two 

panels. Information on these panels include: 

a) The subset values established in Work with User Profiles panel 

option 7=SR subset values. Your ability to change the default 

values depends on your defined subset authority. 

b) Identify the report parameters. Accept the subset defaults, or if 




c) Once all report requirements are determined, press ENTER to 

submit the report and redisplay the SDM-DesignTracker main 

menu. 





















comparisons⎯too many can create a blank report. 

e) After all report requirements are determined, press ENTER to 




DesignTracker main menu. 

Updating Design Request Information in SDM- 

ProjectMaster 

This batch function is used to update the actual effort, actual cost, and estimated 

project completion date for all design requests associated with projects in SDM- 

ProjectMaster. The estimated date of completion is updated to all associated SDM- 

SupportCenter calls. The required information is retrieved from the SDM- 

ProjectMaster database. This advances communication within the project. 

This function is required if you want to update the information in SDM- 

ProjectMaster. A project leader typically performs it, whenever needed. 

The program will only process design requests that have an open status code. 

To update design request information in SDM- 

ProjectMaster: 

1. On the SDM-DesignTracker Menu, type option 5, Update SDM- 

ProjectMaster Information, and press ENTER. The Update DR 

ProjectMaster Info panel displays. Or, use Update ProjectMaster 

command DTUPDPM at the command line. 

2. Select if you want to run the update in batch. 

3. Press ENTER to run the update for all the information. The SDM- 

DesignTracker main menu redisplays.

Printing the Service Request Summary Report 

The Service Request Summary Report is used to create a service request report of 

user-defined selection, sort and format options. 

The Print Service Requests record selection criteria directly reflects the default 

subsetting information setup for you in the Work with User Profiles panel option 

7=SR subset values. Access to the subset fields depends on your subset authority. If 

your subset authority in your user profile is set to 1, default subset information can be 

changed. If your subset authority is set to 0, you only have access to the fields not 

restricted by your subset defaults. 

Use this option to produce a hard copy report of selected service requests using userdefined 

criteria. 

A project leader typically runs this report whenever the information is needed. 

A service request subset must be determined in Work with User Profiles (option 

7=SR subset values) for users who do not have subset authority. 

To print a service request summary report: 

1. On the SDM-DesignTracker Menu, type option 8, Print Service 

Requests Summary Report, and press ENTER to display the Define 

Subset panel. 


when running the report. There are five available subsets to select from: 

Record Selection accesses panels 1 and 2 of the Print Service 

Requests Summary Report subset panel. This subset allows 

you to change the standard subset selection criteria. Go to step 

2 if you want to select this report subset. 


panel. This subset allows you to create customized subset 


step 3 if you want to select this report subset. 

Select and Sequence Fields accesses the third panel of the 

Print Service Requests Summary Report subset panel. This 

subset allows you to select or change which fields are selected 

for the report, and in what order they display. Go to step 4 if 

you want to select this report subset. 

Select Sort Fields accesses the fourth panel of the Print 

Service Requests Summary Report subset panel. This subset 

allows you to select or change the sort priority and order 

(ascending or descending) for specific fields. Go to step 5 if 


Narratives, Sections, Limits and Title accesses the fifth and 

sixth panels of the Print Service Requests Summary Report 

subset panels. This subset allows you to select or change 

which narrative fields, sections, and request types to include 

on the final report, and/or to enter or change the title for the 

report. Go to step 6 if you want to select this report subset. 



Note: The system defaults to the values established the last time the report 

was submitted. If these are the parameter requirements needed for the 

report, you can press ENTER and submit the report without accessing and 

viewing each panel (you can press ENTER to submit the report from any of 

the Service Request Summary Report panels). 

2. The Print Service Requests Summary Report function consists of two 

panels. Both panels reflect the subset values established for you in 

Work with User Profiles option 7=SR subset values. Your ability to 

change the default values depends on your subset authority. 

a) Identify the report parameters. Accept the subset defaults, or if 




b) Once all report requirements are determined, press ENTER. The 

system validates your selections and redisplay the Define Subset 

panel. 

c) Select another subset option or press ENTER again to submit the 

report and redisplay the SDM-DesignTracker main menu. 


selection criteria with And/Or comparison functionality. 


















e) Once all report requirements are determined, press ENTER to 




DesignTracker main menu. 

4. The Select and Sequence Fields function allows you to specify which 

fields to include on the report and in what sequence they display. 

Enter the sequence subset and press ENTER. The system validates the 

sequence criteria and redisplays the Define Subset panel. Select another

subset option, or press ENTER again to submit the report and redisplay 

the main menu. 

5. The Select Sort Fields option allows you to specify in what order you 

want to see the request information sorted on the report. 

Enter the sort criteria for the report and press ENTER. The system 

validates the selected sort criteria and redisplays the Define Subset 

panel. Select another subset option or press ENTER again to submit the 

report and redisplay the main menu. 

6. The Narratives, Sections, Limits, and Title options allow you to identify 

the narrative fields to print on the report and the maximum number of 

lines per narrative to include. They also allow you to determine the 

specific sections to include for each service request, and if only requests 

that are attached to a design request or SDM-SupportCenter call are 

included in the report. 

a) Press PAGEDOWN to continue to the sixth panel of this option to 

specify or change the title of the report. Identify what narrative 

information, sections, and request types to include on the report. 

Press ENTER to validate the selected criteria, or press 

PAGEDOWN to display the sixth panel of the Print Service 

Requests Summary Report function to enter a descriptive title for 

the report. 

b) Press ENTER to validate the selected criteria and redisplay the 

Define Subset panel. 

7. Select another subset option or press ENTER again to submit the report 

and redisplay the main menu. 

Printing the Design Request Summary Report 

The Design Request Summary Report is used to create a design request report of 

user-defined selection, sort, and format options. The Print Design Requests record 

selection criteria directly reflects the default subsetting information defined for you in 

Work with User Profiles panel (option 6=DR subset values). Access to these fields 

depends on your subset authority. If your subset authority in your user profile is set to 

1, default subset information can be changed. If your subset authority is set to 0, you 

only have access to the fields not restricted by your subset defaults. 

A project leader typically runs this report when the information is needed. 

A design request subset must be determined in Work with User Profiles (option 

6=DR subset values for users who do not have subset authority. 

To print a design request summary report: 

1. On the SDM-DesignTracker Menu select option 4 and press ENTER to 

display the Define Subset panel. 


to the report. There are five available subsets to select from: 

Record Selection accesses panels 1 and 2 of the Print Design 

Requests Summary Report subset panel. This subset allows 

you to make changes to the standard subset selection criteria. 

Go to step 2 if you want to select this report subset. 




panel. This function allows you to create customized subset 


step 3 if you want to customize the report subset. 

Select and Sequence Fields accesses the third panel of the 

Print Design Requests Summary Report subset panel. This 

subset allows you to select or change which fields are selected 

for the report and in what order they display. Go to step 4 if 


Select Sort Fields accesses the fourth panel of the Print 

Design Requests Summary Report subset panel. This subset 

allows you to select or change the sort priority and order 

(ascending or descending) for specific fields. Go to step 5 if 


Narratives, Sections, Limits, and Title accesses the fifth and 

sixth panels of the Print Design Requests Summary Report 

subset panels. This subset allows you to select or change 

which narrative fields, sections, and request types to include 

on the final report, and to enter or change the title of the 

report. Go to step 6 if you want to select this report subset. 

Note: The system defaults to the values established the last time the report 

was submitted. If these are the parameter requirements needed for the 

report, you can press ENTER and submit the report without accessing and 

viewing each panel (you can press ENTER to submit the report from any of 

the Design Request Summary Report panels. 

2. The Print Design Requests Summary Report function consists of two 

panels. Both panels reflect your subset values that are established in 

Work with User Profiles option 7=SR subset values. Your ability to 

change the default values depends on your subset authority. 

a) Identify the report parameters. Accept the subset defaults, or if 




b) Once all report requirements are defined, press ENTER. The 

system validates your selections and redisplays the Define Subset 

panel. 

c) Select another subset option or press ENTER again to submit the 








Test parameters.










The number of And/Or string comparisons that can be entered has 

no limit. However, use caution when selecting your 


e) Once all report requirements are defined, press ENTER to submit 

the report. The system first validates the selection criteria and 

redisplays the Define Subset panel. 

f) Press ENTER again to submit the report and redisplay the main 

menu. 

4. The Select and Sequence Fields function allows you to specify which 

fields to include on the report and in what sequence they display. 

Enter the sequence subset and press ENTER. The system validates the 

sequence criteria and redisplays the Define Subset panel. Select another 

subset option or press ENTER again to submit the report and redisplay 

the main menu. 

5. The Select Sort Fields option allows you to specify in what order you 

want to see the request information sorted on the report. 

Enter the sort criteria for the report and press ENTER. The system 

validates the selected sort criteria and redisplays the Define Subset 

panel. Select another subset option or press ENTER again to submit the 


6. The Narratives, Sections, Limits, and Title options allow you to identify 

the narrative fields to print on the report, and the maximum number of 

lines per narrative to include. They also determine the specific sections 

to include for each design request, and if only requests that are attached 

to an entity list, service request, or SDM-SupportCenter call are 

included in the report. 

a) Press PAGEDOWN to continue to the sixth panel of this option to 

enter or change the title of the report. Identify what narrative 

information, sections, and request types to include on the report 

and press ENTER to validate the selected criteria, or press 

PAGEDOWN to go to the sixth panel of the Print Design Requests 

Summary Report function to enter a descriptive title for the report. 

b) Press ENTER to validate the selected criteria and title and return to 

the Define Subset panel. 

7. Select another subset option or press ENTER again to submit the report 

and redisplay the main menu. 


Notes 


APPENDIX A GLOSSARY OF TERMS 

administrator 

This is the person responsible for controlling the effective operation of the SDM- 

DesignTracker system. 

alternatives 

Entered for service and design requests to identify “work-arounds” or alternative 

solutions for a request. Useful for requests that are not currently viable or that need 

further review, and processing cannot be interrupted. 

approval users 

These are users who must approve or disapprove a service or design request. 

Requests cannot be processed and entities cannot be checked out or promoted in 

SDM-Implementer until they have been approved or disapproved by the approval 

user(s). 

authority 

Each user is granted specific authorities to use or access functions within SDM- 

DesignTracker. Authorities are defined and maintained by the Administrator. 

benefits priority 

Identifies the relative importance of a request based on the possible benefits of the 

request. 

bulletin board 

Function used to allow communication between the SDM-DesignTracker and SDM- 

SupportCenter users to track the progress, status, and standing of a request. 

APPENDIX A GLOSSARY OF TERMS • 129

call 


A problem reported by a customer in SDM-SupportCenter. 

call reference number 

The system allocated number used to uniquely identify a call in SDM-SupportCenter. 

company 

The entity (your company) that is using the SDM-DesignTracker system to submit 

service and design requests. 

cost center 

Code that can be used by the accounting department to track costs. 

department 

Used to further define each segment of a division within a company. For example, the 

development department may be broken down into separate groups by product (for 

example, SDM-DesignTracker Development, SDM-SupportCenter Development, 

and so forth). 

design request 

Request for software development projects and other types of projects (for example, 

error corrections for a product, enhancement requests). Product errors are usually 

associated with SDM-SupportCenter calls, and product enhancements are usually 

associated with service requests. 

development priority 

Identifies the development priority of a request. This can be used to identify requests 

that need to be considered for development. 

development resource 

Identifies the person responsible for the development of a logged design request. 

division 

This refers to each segment within a company (for example, Administration, Sales, 

Support, and so forth).

domain 

This is an SDM-ProjectMaster concept that allows projects to be grouped together. 

See the SDM-ProjectMaster User Guide for additional information. 

entity list 

The programs, files, data areas, job descriptions, and so forth, that are related to the 

implementation of a design request. 

environment 

Used in SDM-Implementer to identify a collection of AS/400 libraries where 

production, testing and quality assurance objects reside. See the SDM-Implementer 

System Administrator Guide for additional information. 

narrative 

Descriptive text describing additional considerations or processing guidelines for 

service and design requests. 

PTF release 

Program Temporary Fix. A category of a release that contains software items for a 

specific change. This category is typically defined by a developer, and corresponds 

to a specific problem and/or enhancement. The PTF category represents a single 

software change. 

priority 

The relative importance of a service or design request. 

product 

Detailed information describing the software products supported on your system. 

product component 

Defines the components that make up the total software product. 

project creation rule 

These are rules that enable you to create a project automatically in SDM- 

ProjectMaster in conjunction with a Design Request Entity List. 



project leader 

Person responsible for the development of a design request in SDM-ProjectMaster. 

project tasks 

Task created for a design request in SDM-ProjectMaster. 

release category 

Determines the path that a release must follow. It also determines the dependency 

that is automatically associated between a current release and a previous release of 

software. 

Release types are in two different categories⎯standard (STD) and program 

temporary fix (PTF). The release category, along with the release status, determines 

the development path that a release must follow. It also determines the dependency 

that is automatically associated between a current release and a previous release. 

release control 

Feature of release management that provides additional management control and 

orientation by release name or number for managing internal production 

environments and reviewing release history. SDM-Implementer users can continue 

working in a continuous development model or a fixed-version development model 

which also supports PTFs for each version, optimizing developer time and 

productivity. The benefits of release control include software versioning at the 

product level, and knowledge of which products, versions, and releases are under 

change management control. 

release deployment 

An optional feature of release management that allows SDM-Implementer users to 

manage, track, and deploy software changes by client, installed system, licensed 

product, version number, or PTF, as well as check current release status and 

shipments. Internal and external clients have greater control and flexibility over 

installation of change packages, such as user-specified test libraries, scheduled 

installations and control over object owners and authorities 

release status 

Defines the path a release must follow before it can be changed to the next available 

status. It also defines the functions that can or can not be performed to the release 

during each phase of the cycle.

elease type 

User-defined variable that defines the types of releases you manage 

requester 

Person or persons submitting the service or design request. 

requester priority 

Identifies the relative importance of a request based on the requester’s criteria. 

SDM-ProjectMaster 

MKS product used to interface with SDM-DesignTracker. SDM-ProjectMaster is 

used to create specific projects and tracking capability for a design request. 

service request 

This is a request for data processing services and other types of service (for example, 

software enhancements or a program fix). 

sign for user 

User who has the authority to approve or disapprove requests for another user profile 

ID. 

standard release (STD) 

A type of software release is typically created on a periodic basis (weekly, monthly, 

quarterly, or adhoc) by a product/development manager. This category is the 

standard deliverable that is provided by development over a period of time. It 

typically contains a collection of software changes and enhancements that have been 

promoted into the product version environment over the period of time that the 

release was built. The STD category represents a cumulative set of software 

changes. This is the default value. 

status 

Determines the current state of the service or design request. 


subset 


Used to identify specific selection criteria for displaying service and design requests, 

user profiles, and for selecting information to print on standard and summary service 

request and design request reports. 

system administrator 

See Administrator. 

type code 

Used to determine and track the reasons why a service or design request was 

submitted (for example, communication problem, documentation correction, and so 

forth). 

user profile 

Profile of the individual SDM-DesignTracker user. This information includes granted 

authorities defined by the System Administrator. 

version 

A version is major functional level of a product. It defines a specific set of features 

within the product and the corresponding software that provides those features. A 

product version is developed within change management environments.

INDEX 

A 

Abstract/Probe 

building the entity list with 83 

Administrator, defined 129 

Alternatives, defined 129 

Approval users 

working with 54 

Approval users, defined 129 

Approving requests 70 

Authorities 

signing authorties 49 

subsetting 49 

Authority, defined 129 

B 

Benefits 

priority codes 23 

Benefits priority, defined 129 

Bulletin board, defined 129 

C 

Call reference number, defined 130 

Call, defined 130 

Changing 

close status 22 

Closed status 

changing 22 

Commands 

DTAPRDR 116 

DTCHGDR 111 

DTCRTDR 106 

DTDLTDR 116 

DTMNTSC 56 

DTUPDPM 122 

DTWRKCC 32 

DTWRKCMP 29, 54 

DTWRKDR 70 

DTWRKDRE 91 

DTWRKDSC 22 

DTWRKDTC 21 

DTWRKENV 28 

DTWRKPC 24 

DTWRKPCR 25 

DTWRKPRD 34 

DTWRKRSR 53 

DTWRKSR 66, 68, 70 

DTWRKSSC 22 

DTWRKSTC 21 

DTWRKSYS 26 

DTWRKUSR 49 

Companies 

creating 30 


Company, defined 130 

Components 

interfacing with SDM-SupportCenter 48 


Components, see Product components 37 

Cost center, defined 130 

Cost centers 

creating 32 


Creating 

approval users 54 

companies 30 

cost centers 32 

departments 30 

design request priority codes 23 

design request status codes 22 

design request type codes 21 

divisions 30 

environment status codes 28 

product versions 40 

products 36 

project creation rules 25 

resources 53 

service request priority codes 23 

service request status codes 22 

service request type codes 21 

system ID's 26 

user profiles 49 

versions 40 

D 

Definition of 

administrator 129 

alternatives 129 


authority 129 

benefits priority 129 

bulletin board 129 

INDEX • 135

call 130 

call reference number 130 

company 130 

cost center 130 

department 130 

design request 130 

development priority 130 

development resource 130 

division 130 

domain 131 

entity list 131 

environment 131 

narrative 131 

priority 131 

product 131 

product component 131 

project creation rule 131 

project leader 132 

project tasks 132 

PTF 131 

release category 132 

release control 132 

release deployment 132 

release status 132 

release type 133 

requester 133 

requester priority 133 

SDM-ProjectMaster 133 

Service request 133 

sign for user 133 

standard release 133 

status 133 

subset 134 

system administrator 134 

type code 134 

user profile 134 

version 134 

Department, defined 130 

Departments 

creating 30 

work with 29 

Design request 

entity list, using project creation rules 25 

priority codes, working with 23 

status codes, working with 22 

type codes, working with 21 

Design Request Standard Report 121 

Design Request Summary Report 125 

Design request, defined 130 

Development 


Development priority, defined 130 

Development resource, defined 130 

Division, defined 130 

Divisions 


creating 30 


Domain, defined 131 

DTAPIERR data area 118 

DTAPRDR command 116 

DTCHGDR command 111 

DTCRTDT command 106 

DTDLTDR command 116 

DTMNTSC command 56 

DTUPDPM command 122 

DTWRKCC command 32 

DTWRKCMP command 29, 54 

DTWRKDR command 70 

DTWRKDRE command 91 

DTWRKDSC command 22 

DTWRKDTC command 21 

DTWRKENV command 28 

DTWRKPC command 24 

DTWRKPCR command 25 

DTWRKPRD command 34 

DTWRKRSR command 53 

DTWRKSR command 66, 68, 70 

DTWRKSSC command 22 

DTWRKSTC command 21 

DTWRKSYS command 26 

DTWRKUSR command 49 

E 

Entity list 

building 83 

defined 131 

Environment status code settings 


Environment, defined 131 

G 

Glossary 129 

H 

Hawkeye 

building the entity list with 83 

I 

Interface commands 

DTAPRDR 116 

M 

Media 

working with 59

N 

Narrative, defined 131 

O 

Object selection 

in PathFinder 87 

P 

Prerequisites to using this manual 1 

Priority codes 

benefits 23 


development 23 


requester 23 

service request 23 

Priority, defined 131 

Product component, defined 131 

Product versions 39 

Product, defined 131 

Products 



Project creation rule, defined 131 

Project creation rules 

creating 25 

Project leader, defined 132 

Project tasks, defined 132 

PTF, defined 131 

R 

Release category 

defined 132 


Release control 

defined 132 

development scenario 93 

release status, working with 99 

release types, working with 96 

set up requirements 94 

Release deployment 

defined 132 

Release management 

overview 7 

release control overview 92 

setup tasks overview 57 

Release management, see also Release control 

Release status 

defined 132 

field descriptions 102 

setting up for release control 101 


Release type 

defined 133 

Release types 

field descriptions 98 

setting up for release control 97 


Releases 

member/object detail 42 

release and package dependencies 42 



Reports 

Design Request Standard Report 121 

Design Request Summary Report 125 

Service Request Standard Report 119 

Service Request Summary Report 123 

Requester 


Requester priority, defined 133 

Requester, defined 133 

Resources 


S 

SDM-DesignTracker data areas 

DTAPIERR 118 

SDM-Implementer 

environments, creating status code settings 28 

SDM-ProjectMaster 

project creation rules, creating 25 

SDM-ProjectMaster, defined 133 

SDM-SupportCenter 

interfacing components 48 

interfacing products 48 

Service request 

priority codes, working with 23 

status codes, working with 22 

type codes, working with 21 

Service Request Standard Report 119 

Service Request Summary Report 123 

Service request, defined 133 

Sign for user, defined 133 

Signing authorities 

approval lists 49 

Software release process configuration 

defined 96 

Software release process configuration, see also Release 

types and Release status 

Standard release, defined 133 

Status codes 



service request 22 

INDEX • 137

Status, defined 133 

Subset, defined 134 

Subsets 

in work with service requests 65 

System 

authorities 49 

control settings 56 

default values, user profiles 49 

defaults, control settings 56 

System administrator, defined 134 

System authorities 49 

System control settings 

changing 56 

System ID's 

creating 26 

Systems 


T 

Type code, defined 134 

Type codes 

design requests 21 

service requests 21 

U 

User profile 

defined 134 


V 

Version, defined 134 

Versions 39 


W 

Working with 


companies 29 

components 34 

cost centers 32 

departments 29 

design request priority codes 23 

design request status codes 22 

design request type codes 21 

divisions 29 

environment status code settings 28 

media 59 

products 34 

project creation rules 25 


release types 57 


resources 53 

service request priority codes 23 

service request status codes 22 

service request type codes 21 

systems 26 

users 49 

versions 34 

Working with products 

creating product versions 40 

creating products 36 

product components 37 

product versions 39 

working with releases 42 

Working with releases 

creating packages 42 

from environments 45 

member/object detail 42 

package dependencies 42 

release dependencies 42 


Working with versions 39 

creating versions 40 

release 'from' environments 45

SDM-DesignTracker 5.0 User Guide - MKS

Create successful ePaper yourself

Delete template?

Save as template?