Professional Documents
Culture Documents
User Guide
User Guide
User Guide
User Guide
Publication number
Copyright notice
Documentation set
The documentation relating to this product includes:
Getting Started with TURNOVER for iSeries v100 Client
Getting Started with TURNOVER for iSeries v100
TURNOVER for iSeries v100 User Guide
TURNOVER for iSeries v100 Developers Guide
Application Planning Guide
Managing IFS Objects with TURNOVER for iSeries v100
TURNOVER for iSeries v100 PWM Quick Reference
Trademark acknowledgements
The following are trademarks or registered trademarks of IBM
Corporation: APPC, APPN, iSeries, System i, OfficeVision,
OS/400, and SNA.
Product and company names mentioned herein may be the
trademarks or registered trademarks of their respective owners.
TABLE OF CONTENTS
PREFACE .......................................................................................................................................................................... IX
WHO SHOULD USE THIS GUIDE .........................................................................................................................................IX
UNICOM SYSTEMS, INC. RECOMMENDATIONS .................................................................................................................IX
UNICOM SYSTEMS, INC. CAUTIONS ..................................................................................................................................X
WHAT'S NEW IN TURNOVER FOR ISERIES V100? .........................................................................................................XI
THE TURNOVER FOR ISERIES V100 INFORMATION LIBRARY ..................................................................................... XII
CHAPTER 1: WORKING WITH APPLICATION DEFINITIONS ...........................................................................1-1
GETTING STARTED...........................................................................................................................................................1-2
WORK WITH APPLICATION DEFINITIONS PANEL ..............................................................................................................1-3
WORK WITH APPLICATION DEFINITION PANEL ................................................................................................................1-7
DEFINE THE APPLICATION PANEL ....................................................................................................................................1-9
Application Description ........................................................................................................................................... 1-12
Application Defaults and Rules ................................................................................................................................ 1-13
Project Defaults........................................................................................................................................................ 1-15
Library Defaults ....................................................................................................................................................... 1-18
Form Defaults .......................................................................................................................................................... 1-21
Line Defaults ............................................................................................................................................................ 1-29
Type Codes ............................................................................................................................................................... 1-37
Authorized Users ...................................................................................................................................................... 1-43
Distribution Defaults ................................................................................................................................................ 1-44
Approval Lists .......................................................................................................................................................... 1-45
Form Completion Messages ..................................................................................................................................... 1-48
Application Relationships......................................................................................................................................... 1-49
Version and Object Stamping Defaults .................................................................................................................... 1-51
CHAPTER 2: SETTING UP PROGRAMMER PROFILES........................................................................................2-1
ENROLLING PROGRAMMERS IN TURNOVER FOR ISERIES V100 .................................................................................2-2
Step 1: Sign-on as User TURNOVER ........................................................................................................................2-2
Step 2: Enter Programmer Information ....................................................................................................................2-3
CHAPTER 3: AUTHORIZING USERS TO TURNOVER FOR ISERIES V100 ...................................................3-1
SIGN ON AS USER TURNOVER .......................................................................................................................................3-1
ENTERING USERS AND AUTHORITIES ...............................................................................................................................3-2
SOURCE Authority ....................................................................................................................................................3-3
FORMS Authority .......................................................................................................................................................3-3
SYSTEM Authority......................................................................................................................................................3-3
PROJECTS Authority .................................................................................................................................................3-4
AUTHORIZING USERS TO APPLICATIONS, PROJECTS, OR WISEDESK TREES ......................................................................3-5
DELETING A USER FROM TURNOVER FOR ISERIES V100 ............................................................................................3-7
CHAPTER 4: WORKING WITH OBJECT HISTORY...............................................................................................4-1
THE WORK WITH OBJECT HISTORY PANEL ......................................................................................................................4-2
WORKING WITH NAMED FILTERS ....................................................................................................................................4-8
Adding and maintaining named filters .......................................................................................................................4-9
Filtering objects ....................................................................................................................................................... 4-13
VIEWING ARCHIVED INFORMATION ............................................................................................................................... 4-23
Restoring archived source members ........................................................................................................................ 4-24
How archiving works ............................................................................................................................................... 4-25
CHAPTER 5: CHECKING OUT/CHECKING IN SOURCE ......................................................................................5-1
THE CHECKOUT MENU ....................................................................................................................................................5-2
Page iii
Page iv
Page v
Page vi
Page vii
Page viii
PREFACE
This guide is intended to help you use the TURNOVER for iSeries v100 user interface on the
iSeries. It contains chapters that describe the panel interface of the TURNOVER for iSeries v100
product. The chapter numbers correspond directly to the options on the TURNOVER for iSeries
v100 Main Menu.
1 The iSeries context-sensitive Help is a useful reference for CL. You can position the cursor on a command prompt display to get Help about the
command, and you can position the cursor on a field to get Help about parameters for that field. Also, for information about every aspect of your system
hardware and software, refer to the many fine publications that come with your IBM iSeries computer.
Page ix
Page x
Enhanced form filtering in the Work with Forms 5250 interface. A new function key (F17) on
the Work with Forms panel provides access to sorting and filtering functions that make working with
forms on that panel MUCH easier.
New CHGPWLPGMR and TARAFORM commands. The CHGPWLPGMR command (Change
Programmer Worklist Programmer) is useful when you need to reassign the programmer
associated with a given worklist. Depending on the parameters you pass, the changes made might
include: Worklist programmer, Worklist item programmer for all lines on the worklist, and checkout
records.
The TARAFORM command (TURNOVER for iSeries Add Related Application Form) is useful
when you need to create related application forms once the base form has been created.
Page xi
The TURNOVER for iSeries v100 iSeries information library, consisting of (in addition to this
TURNOVER for iSeries v100 User Guide) a getting started guide and a tutorial:
o The Getting Started with TURNOVER for iSeries v100 guide provides instructions for
installing TURNOVER for iSeries v100 on your iSeries computer (for the first time),
upgrading to TURNOVER for iSeries v100, and applying changes to an existing
TURNOVER for iSeries v100 release.
o The TURNOVER for iSeries v100 Tutorial presents an example of a TURNOVER for
iSeries v100 application, and walks you through the steps you would typically perform in your
actual working environments.
o The TURNOVER for iSeries v100 Developers Guide contains topics of specific interest to
software developers. It also serves as an effective introduction to TURNOVER for iSeries
v100.
o The Synchronizer User Guide describes all of the features of the Synchronizer system,
including the source compare and merge programs.
The TURNOVER for iSeries v100 Application Planning Guide provides information to help
you understand TURNOVER for iSeries v100 and TURNOVER for iSeries v100 application
definitions. (This information is user interface independent.)
The TURNOVER for iSeries v100 Supplements and Technical Bulletins are articles on
specialized or advanced topics.
The TURNOVER for iSeries v100 Interface Guides describe how to use TURNOVER for
iSeries v100 to manage objects created by other products. 2
The TURNOVER for iSeries v100 Client/Server information library remains available on the
CD for customers who have not transitioned to the new TURNOVER for iSeries v100 Client.
The Getting Started with the TURNOVER for iSeries v100 Client guide provides installation
and configuration instructions for using the Eclipse-based TURNOVER for iSeries v100 plugins, either in the standalone TURNOVER for iSeries v100 Client or within your WebSphere
IDE.
2 For a complete list of products with which TURNOVER for iSeries v100 interfaces, visit our Web site or contact your UNICOM Systems, Inc. Sales
Representative.
Page xii
TURNOVER for iSeries v100 Supplement #66: Implementing TURNOVER for SVN v100
provides complete information for installing and configuring the TURNOVER for iSeries v100
version control product for your Web/PC/Java development projects. This product integrates
seamlessly with the Eclipse-based TURNOVER for iSeries v100 plug-ins running either in the
TURNOVER for iSeries v100 Client or another Eclipse-based IDE such as IBMs Rational
Application Developer (RAD) or WebSphere Development Studio Client (WDSC) products.
In addition, Help text (both field sensitive and extended help) is available for every display. Position
the cursor to any field, or to the panel title, and press the F1/Help key.
All TURNOVER for iSeries v100 documentation is available as Adobe Acrobat PDF files on
your TURNOVER for iSeries v100 product CD. Using the Acrobat Reader with Search (also
provided), you can search, view, and print TURNOVER for iSeries v100 information.
Page xiii
Page xiv
Page 1-1
GETTING STARTED
To work with application definitions, sign on as TURNOVER or use a profile that is authorized to
work with application definitions.
1/29/10
11:16:26
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F24=More keys
From the TURNOVER for iSeries v100 Main Menu, select option 1 (Work with application
definitions) and press Enter. (Alternatively, you can type the WRKAPPDFN command on a
TURNOVER for iSeries v100 command line.) The Work with Application Definitions panel
appears.
Page 1-2
(Home) Rel:
Ver:
Position to . . . Application:
Fltr:
Type options (and Application), press Enter.
1=Create 2=Change 3=Copy 4=Delete 5=View 6=Print 7=Rename
14=Create missing items 19=Application relations . . .
Opt
Appl
AP
VNDF
VNDR
YCAP
01M
02M
03M
04M
05M
Rel Ver
Description
System-Wide Defaults
Accounts Payable - TurnOver Tutorial
Vendor Base with Fixes and Mods
Vendor Base with Mods
Your Company's Software Application
Model 1
Model 2
Model 3
Model 4
Model 5
Emer.
N
N
N
N
N
N
N
N
N
N
N
Relations
More...
F3=Exit F5=Refresh F6=Create application definition
F14=WRKSBMJOB F21=Command line F23=More options
F12=Cancel
Additional Options:
21=Change level 1 22=Change level 2 . . . 299=Change level 99
51=View level 1 52=View level 2 . . . 599=View level 99 . . .
From this panel, you can work with both system-wide and application definition defaults. You can
use the system-wide defaults as a base from which to create a new application entry when you use
option 1=Create.
What you can do:
Position to
Type the application, release, or version code associated with the application definition with
which you want to work, and press Enter. TURNOVER for iSeries v100 positions the
cursor at that application. You can then select that application definition with the options
described below. If your list of applications is filtered, the cursor is positioned within the filter
if applicable. (See the description of the Fltr field, below.)
Fltr
Type an entry in one or more filter fields to filter the list of application definitions by
application code, release, version, description, emergency setting, or application relationship.
If you type a value in more than one field, you will see only those definitions that meet all
criteria specified. Use an asterisk (*) as a wildcard prefix or suffix with a partial value (for
example, *A or A*) to see all definitions with values that either contain or end with the
designated value, respectively.
Page 1-3
3 If data area TGAEONLY is set to *YES, then you cannot edit on the iSeries any applications that have been edited using the Application Designer.
Page 1-4
21=Change level 1
Define the defaults for the first level of your application. TURNOVER for iSeries v100
displays the Define the Application panel, from which you can work with the application
defaults for that level. See Define the Application Panel on page 1-9.
22=Change level 2
Define the defaults for the second level of your application. TURNOVER for iSeries v100
displays the Define the Application panel, from which you can work with the defaults for that
level. See Define the Application Panel on page 1-9.
2n=Change level n
Define the defaults for additional levels of your application, where n is the application level.
If the level already exists, TURNOVER for iSeries v100 displays the Define the Application
panel, from which you can work with the defaults for that level. If the level doesnt exist,
TURNOVER for iSeries v100 displays the Work with Application Definition panel, from
which you can work with existing levels or create a new level.
51=View level 1
View the defaults for the first level of your application. TURNOVER for iSeries v100
displays the Define the Application panel, from which you can view (but not change) the
defaults for that level.
52=View level 2
View the defaults for the second level of your application. TURNOVER for iSeries v100
displays the Define the Application panel, from which you can view (but not change) the
defaults for that level.
Page 1-5
Page 1-6
Bottom
F3=Exit F5=Refresh F6=Create level F12=Cancel F14=WRKSBMJOB
F16=User options F21=Command line F23=More options
More options:
8=Description 9=Application defaults and rules 10=Project defaults
11=Library defaults 12=Form defaults 13=Line defaults 14=Type codes . . .
More options:
15=Authorized users 16=Distribution defaults 17=Approval list
18=Form completion messages 19=Application relations 24=Version Dfts . . .
This panel displays the levels for the selected application definition. You can work with the defaults
for these levels, and create new levels. Also, if you have authority to update the highest unlocked
level (Production) of the application, you can update the application description and emergency
application flag shown at the top of this panel.
What you can do:
20=Sbm Xref
Submit a job to generate a cross-reference file for the application level. Before selecting this
option, you should first specify *TURNOVER as the applications X-Ref method on the
Application Defaults and Rules panel. You only need to perform this operation once. (You
do not need to do this if your application is using libraries that are already built into the crossreference table.) This job is submitted on hold and you can release it when you want it to run.
Page 1-7
Page 1-8
Application . . AP
QA
Release . . . .
Lock . . . . . No
Version . . . .
XRef . . . . . *TURNOVER
Level . . . . . 1
Emergency. . . No
Type options, press Enter. Press F21 to select all.
1=Select
Description
Application defaults and rules
Project defaults
Library defaults
Form defaults
Line defaults
Type codes
Authorized users
Distribution defaults
Approval list
Form completion messages
Application relations
Version and stamping defaults
F3=Exit
F12=Cancel
F18=Next level
F21=Select all
This panel lists all the categories of application defaults. TURNOVER for iSeries v100 uses
application defaults when building a programmer worklist, during checkout, and when building a
TURNOVER for iSeries v100 form.
Notice that you can press F17 and F18 on this panel to quickly jump to higher or lower levels of the
application definition. F17 and F18 appear here only if there are higher or lower levels defined.
Taken together, these defaults are referred to as an application definition. Some of these defaults,
such as Application Distribution Defaults and Approval List, are optional. Any defaults youve
previously specified are marked with a > sign.
Use option 1 (Select) to selectively choose from the list of default categories, or press F21 to work
with all parts of the application definition. If you use F21 to select all the default categories,
TURNOVER for iSeries v100 presents each defaults panel in succession. When youve finished
with a panel, press Enter to advance to the next panel. Each application defaults panel is shown and
described in this section.
Note: Changes made to these defaults are not applied to any existing form or programmer worklist
items unless you re-edit the item or recreate the TURNOVER for iSeries v100 form.
Page 1-9
Page 1-10
Page 1-11
Application Description
1/29/10
9:23:41
Application Description
code . . .
description
. . . . . .
. . . . . .
. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. AP
. Test Application
.
.
. 1
Audit application . . . . . . . . . . .
Use reference object for owner . . . .
Application default owner . . . . . . .
Application administrator . . . . . . .
Allow only administrator to submit form
Pre-run/Post-run command authority . .
Application level permanently locked .
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
W
N
QSECOFR
QSECOFR
N
QSECOFR
N
W,E,N
Y,N
Usrprf
Usrprf
Y,N
Usrprf
Y,N
F12=Cancel
Whether youre working with entries for the system-wide definition or an application definition, this
panel looks the same.
If a user other than QSECOFR is the owner of production objects for this application, change the
Application default owner field.
If you have one person who will usually be designated as the Application Administrator, enter
that users profile name.
Pre-run/Post-run command authority indicates the user profile under whose authority pre- and
post-run commands (commands that can be added to a TURNOVER for iSeries v100 form) will
be run.
Page 1-12
Lev:
. . . . . . *TURNOVER
F12=Cancel
*YES
DEFAULT
05/01/05
05/05/05
. . . .
. . . .
. . . .
. . . .
. . . .
command
. . . .
. . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*DEFAULT
N
Y,N
L
*DEFAULT
*MAP *DROP
*YES
*YES,*NO
*YES
*YES,*NO,*NATIVE
E
W,E
With TURNOVER for iSeries v100, you can manage the contents of your on line source archive
files and store files off line. If you choose to archive off line, youll need to periodically save source
off line to tape. 4 Archived source can be retrieved any time and restored if necessary from the Work
with Object History panel (see Main Menu option 4). The Archive information topic in Chapter 4
contains a complete description of the archiving process. Also, the TURNOVER for iSeries v100
Application Planning Guide contains tips and examples for setting up your source archiving strategy.
You can also archive objects. Objects that are being deleted or replaced can be retained in a library
associated with the TURNOVER for iSeries v100 job (identifiable by its form number). You can
run a regular job to save these objects off line to tape, or you can purge them on a regular basis. If
you save the objects using TURNOVER for iSeries v100s save procedure, 5 you can view, retrieve,
and restore them later, if necessary.
You can use the Field attributes parameter to lock in the default value. L=Lock the field. The value
you provide cannot be overridden when entering a TURNOVER for iSeries v100 form. R=Restrict
the field. The value you provide here can be changed when entering a form. Blank=the value you
provide will be presented as a default, but you can change it when entering a form.
4 See Main Menu option 8, then option 2, and then select, with option 3=Save, the source archive file you want to save off line.
5 See the SAVARCO command or Main Menu option 8, then option 9 and 10 and also the SAVARSBM command
Page 1-13
Page 1-14
Project Defaults
With TURNOVER for iSeries v100, you can require that all changes be associated with a project
task in the TURNOVER for iSeries v100 Project database by setting the Require Project entry
parameter to Y. If you do, TURNOVER for iSeries v100 will require that a developer identify a
valid project task any time s/he checks out or turns over source and objects. For more information,
see Chapter 9: Working with Projects and Tasks.
If you choose to link events that occur during object management to TURNOVER for iSeries
v100s project system, then you can also specify the value to which the task status code should be
updated when key events, such as checkout or form completion, occur. (You can also define
escalation processing for your project, to automatically generate e-mail notices or run commands, for
any of the status codes you choose here.) For example, assuming a two-level application, your task
status might progress this way:
1. When you check out of Production for the first time, you can have TURNOVER for iSeries
v100 update your task to Started.
2. When you build any form and require approval to run it, you can have TURNOVER for iSeries
v100 update the task status to Approve.
3. When you run a level 1 form to promote to test libraries, you can have TURNOVER for iSeries
v100 update your task to In Testing.
4. If you check out of level 1 to do revisions, you can have TURNOVER for iSeries v100 update
your task to In Revision.
5. When you run a level 2 form to promote to production, TURNOVER for iSeries v100 can
update the form status to Completed.
Note: Status changes linked to the completion of a form occur only if the form completes with a
status of xxx-OK.
Page 1-15
Project Defaults
Application: AP
Rel:
Ver:
Lev:
Y/N
Y/N
When
When
When
When
When
checked out . . . . .
form requires approval
form completes . . . .
form distributes . . .
remote confirms . . .
.
.
.
.
.
.
.
.
.
.
New
. S
. 2
. T
.
.
Task Status
STARTED
APPROVE
TESTING
F4=List
F4=List
F4=List
F4=List
F4=List
Project Task Status field will be updated to these values when the related
event has occurred.
F3=Exit
Page 1-16
F4=List
F12=Cancel
6 You can define your own status code values to be used by TURNOVER for iSeries v100.
Projects and Tasks.
Page 1-17
Library Defaults
From and Target libraries are specified for each application and level.
1/29/10
10:11:04
Library Defaults
Application: AP
Rel:
Ver:
Lev:
F12=Cancel
L
L
L
(Y,N)
F3=Exit
Field Attributes
R=Restrict, L=Lock
L
L
L
L
L
Note: This panel shows the Target and From libraries for this application level.
The Target libraries are the libraries into which source is copied and to which objects are moved or
created when a promotion occurs. These libraries can also be specified by object type (see
TURNOVER for iSeries v100 Type Defaults on page 1-39).
The From libraries are the libraries from which source or objects (or both) should be moved, and
where test objects should be found. (Read the online Help for the values you can type here.) These
can also be specified differently by object type (see TURNOVER for iSeries v100 Type Defaults on
page 1-39).
If any of the libraries dont exist, TURNOVER for iSeries v100 displays a message and lets you
create the libraries. TURNOVER for iSeries v100 creates the libraries using the profile and
authority of the application owner, with PUBLIC(*CHANGE) authority. You can also elect to
create these outside of TURNOVER for iSeries v100 with different ownership and authority.
You can specify name masks to check new object names when you enter a TURNOVER for iSeries
v100 form. You can also specify name masks for each object type within the application (see
TURNOVER for iSeries v100 Type Defaults on page 1-39).
Maintaining IFS path defaults
Use option F8 (IFS Path defaults) on the Library Defaults panel to display or maintain path defaults
for Integrated File System (IFS) object types. When you select this option, TURNOVER for iSeries
v100 displays the Path Defaults panel. For more information, see the IFS guide, Managing
Integrated File System (IFS) Objects Using TURNOVER for iSeries.
Page 1-18
4=Delete
Library
TSTDTABAS
F3=Exit
Allow
Override
N
F5=View 2
F6=Add library
F12=Cancel
If reference objects exist in the explode library, theyll be used to set creation parameters and object
authority, where applicable, otherwise the regular reference objects in the primary data library of the
application are used. For more information, see the discussion about Reference objects on page 1-38.
If you have a pre- or post-run command that you want to run for an object that resides in all explode
libraries, you can use the &ALLTGT value (including the quotes shown) in the Library parameter
of your pre- or post-run command string. For more information, see the TURNOVER for iSeries
v100 Supplement entitled The TURNOVER for iSeries v100 Change Process (#14).
If you specify Allow override = Y, a user is allowed to decide when creating a form whether or not to
explode data objects to that library. If you specify Allow override = N, data object changes are
7 You can either duplicate an existing data library or create a library and duplicate each file object from an existing library into the new one.
Page 1-19
Form Defaults
Form defaults govern the running of the TURNOVER for iSeries v100 promotion job (the job that
promotes the source and objects to the next test level or to Production). When you create a
TURNOVER for iSeries v100 form, these defaults comprise the form header. Form defaults control
such things as what job description and library list TURNOVER for iSeries v100 should use when
running the TURNOVER for iSeries v100 form, where output should be placed, and which recovery
option should be used.
1/29/10
12:05:59
Form Defaults
Application: 01M Rel:
Ver:
Lev:
F4=List
.
.
.
.
.
.
.
.
Name, *PGMR
Name
Name, F4=List
1=Recover
2=Recover
3=Attempt
4=Process
*BATCH
*CURRENT
*SBMRLS
Y
N
N
*USRPRF
Field Attributes
R=Restrict, L=Lock
L
L
L
F12=Cancel
The Library list name field identifies the library list TURNOVER for iSeries v100 should use when
compiling objects into the target library. The library list must contain libraries identified for this
application level and for higher levels. It may also include libraries for other applications, as when
you have a joint logical file over files in this and other applications.
To create or work with library lists, position the cursor to the Library list name field and press F4.
TURNOVER for iSeries v100 constructs a library list for you which you can then edit, if none
exists. (For an illustration of the Library list name panels, see Working with an applications library
list, beginning on page 1-23.)
Error check, job submission, and form scheduling fields let you specify default values for controlling
local form jobs. If necessary, you can override these values when you submit the form to run.
A Y in the Submit Finalization field defers certain steps of the promotion process to a separate job,
called a finalization job, making the objects youre promoting more quickly available. For more
about this parameter, see page 1-28.
Page 1-21
8 The Override Form Job Description Defaults panel is also audited for application changes.
Page 1-22
9 There are other areas, besides in the applications form defaults, where you can specify a library list. You can also specify library lists for explode data
libraries (in the applications library defaults) and in a forms header. However, those library list fields have not been expanded to accommodate 250
library names.
Page 1-23
Form Defaults
Application: AP
Rel:
Ver:
Lev:
Field Attributes
R=Restrict, L=Lock
L
L
L
Name, *PGMR
Name
Name, F4=List
and press F4=List. The panel you see next depends on if your system is configured for a maximum
of 25 or 250 libraries in the library list:
1/29/10
10:38:16
1/29/10
13:48:26
Library list
Name, F4=List
. . . . . . LIBRARY001
LIBRARY002
Recommended . . . . . . . LIBRARY001
LIBRARY002
Name, F4=List
Recommended . . . . . . . LIBRARY001
LIBRARY002
If you left the Library list name field blank on the Form Defaults panel, then the first time you
view this panel, TURNOVER for iSeries v100 constructs a library list for you based on the
libraries identified in the current application definition and gives it the same name as the job
description. For this reason, we recommend that you define all the levels of your application first,
and then build a library list for each level. If the Library list name already exists, TURNOVER
for iSeries v100 appends 01, 02, and so on, to the name to make it unique.
If you position to the Library list name field and press F4=List, you will see a window (not
shown here) containing a list of the named library lists you may have created earlier from which
you can select or view.
To create a new library list based on an existing library list name, position to the Library list
name field, press F4 and then select another list name. Then, back on this panel, over-type the
Library list name field. You can then edit your new list, if you want.
Page 1-24
Description
Test Application- Test Level 1
Test Application- Test Level 1
Test Application- Test Level 1
Test
Bottom
F3=Exit
F12=Cancel
Changing the library list affects all applications that use the same library list name. If you do
not have authority to change all of the application definitions on the list, you will not be able
to change the library list and F5 and F7 are disallowed.
If you change the library list name to a new name, you will see the message, Library list does
not exist. Press Enter to add it.
TURNOVER for iSeries v100 displays warning messages if one or more libraries in your list
do not exist on the current system.
Press F5=Reset for Appl to adopt the Recommended library list and then, if necessary, modify
that list. Be sure to press F3 to update the list afterwards.
Page 1-25
If you position to the Library list name field and press F7=EDTLIBL, you will see the current
library list:
Edit Library List
YOURSYS
System:
Library
LIBRARY001
LIBRARY002
Sequence
Number
150
160
170
180
190
200
210
220
230
240
250
Sequence
Number
Library
Library
Sequence
Number
0
10
20
30
40
50
60
70
80
90
100
110
120
130
140
LIBRARY001
LIBRARY002
LIBRARY003
LIBRARY004
LIBRARY005
LIBRARY006
LIBRARY007
LIBRARY008
LIBRARY009
LIBRARY010
LIBRARY011
LIBRARY012
LIBRARY013
LIBRARY014
F3=Exit
F5=Refresh
Library
Sequence
Number
150
160
170
180
190
200
210
220
230
240
250
260
270
280
290
Library
LIBRARY015
LIBRARY016
LIBRARY017
LIBRARY018
LIBRARY019
LIBRARY020
LIBRARY021
LIBRARY022
LIBRARY023
LIBRARY024
LIBRARY025
LIBRARY026
LIBRARY027
LIBRARY028
LIBRARY029
Bottom
F3=Exit
F5=Refresh
YOURSYS
F12=Cancel
Sequence
Number
300
310
320
330
340
350
360
370
380
390
400
410
420
430
440
Library
LIBRARY030
LIBRARY031
LIBRARY032
LIBRARY033
LIBRARY034
LIBRARY035
LIBRARY036
LIBRARY037
LIBRARY038
LIBRARY039
LIBRARY040
LIBRARY041
LIBRARY042
LIBRARY043
LIBRARY044
More...
F12=Cancel
Edit the library list by typing new or changed information on this panel. This is useful for
defining and maintaining library lists for a remote system. When you are finished, press Enter.
TURNOVER for iSeries v100 displays the list in the format shown at the beginning of this
section.
Press F11=Display recommended library list to display a complete list of the recommended
libraries, including the library name, library type (PROD or TEST), and a text description:
Display Library List
System:
YOURSYS
Library
LIBRARY001
LIBRARY002
Type
PROD
PROD
Text
Production Library One
Production Library Two
Bottom
F3=Exit
F12=Cancel
F17=Top
F18=Bottom
On this panel, select a library with option 5 to view the objects in that library.
Page 1-26
LIBRARY001
PROD
*SYSVAL
Object
CLP98
CLP99
RPG01
EVFEVENT
PF001
PF002
PR00F
PR00FL1
PR01F
QCBLSRC
QCLSRC
F3=Exit
Type
*PGM
*PGM
*PGM
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
F12=Cancel
Number of objects . :
ASP of library . . . :
18
1
F17=Top
Size
45056
45056
81920
208896
49152
49152
65536
12288
49152
8192
49152
Text
F18=Bottom
Two additional options let you display full attributes and service attributes for any object
you select on this list.
UNICOM Systems, Inc. Recommends
When defining your library list, keep these suggestions in mind:
DO include target libraries from the current level and higher levels. These should appear AFTER
all target libraries from the current level.
Page 1-27
10 For more about running groups of forms, see Chapter 7: Submitting a TURNOVER for iSeries v100 Form to Run.
11 See TURNOVER for iSeries v100 Main Menu option 8, then option 5.
Page 1-28
Line Defaults
Line defaults are used when TURNOVER for iSeries v100 adds a line to a form or when you
manually add an item to a TURNOVER for iSeries v100 form. One line corresponds to one object
or source member to be promoted. This information is used during promotion processing to dictate
how the object is processed.
When you copy a form to the same level of the same application, TURNOVER for iSeries v100
doesnt alter the form lines. However, if you copy a form to a different level of the application, or to
a different application, then all values come from the application to which youre copying the form.
1/29/10
15:28:46
Line Defaults
Application: AP
Rel:
Ver:
Lev:
Your Company
SYSTEM: YOURSYS
Method
. . . . . . . . . CSCO
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Y
N
P
REF*
.
.
.
.
Y
Y
*CHECKOUT
*FORM
F3=Exit
ACPTTEST
P
REF*
ACPTTEST
Field Attributes
R=Restrict, L=Lock
CSCO, MO, CD, COPR,
L
CSMO, CSCD, CS, *NULL
Y, N
Y, N
P, T, S, R, C
Name, REF*
L
Name
L
P, T, S, R
L
Name, REF*
L
Name
L
Y, N
Y, N
*USRPRF, *FORM, *CHECKOUT
Code, *FORM
R
R
L
R
F12=Cancel
Page 1-29
Page 1-30
Message files
How does TURNOVER for iSeries v100 handle message IDs and files? When you check out a
message file, TURNOVER for iSeries v100 marks it as checked out, but does not move or duplicate
it from your production library. You should create it in test, code the messages you need to add or
change, and then turn it over. TURNOVER for iSeries v100 automatically merges the messages
you changed or added into the message file in the target library. If you need to delete several
messages, you can delete message IDs individually. For more about checking out and promoting
individual message IDs, see the TURNOVER for iSeries v100 Supplement entitled Handling
Message IDs in TURNOVER for iSeries v100 (#61).
If you need to manage more than one message file with one application, youll need to create a unique
type code for each message file. See Working with TURNOVER for iSeries v100 Type Code
Definitions on page 8-6.
Can it handle UIM panel groups? Yes. Can it handle SQL type programs? Yes. Virtually any object
type for which a create command exists or for which one can be created can be managed using
TURNOVER for iSeries v100.
Many vendor supplied applications have object types that are unique only to those vendors. For
example, PeopleSoft has a report writer called Dreamwriter. They also have special create
commands that can be used for creating PeopleSofts RPG programs. These can be defined to
TURNOVER for iSeries v100 as TURNOVER for iSeries v100 type codes and managed just like
your other program objects. If you have a vendor-supplied application package, ask us for more
information about these capabilities.
Level check
Set Check for Level-Check to N to have TURNOVER for iSeries v100 bypass the source level
check. During a source level check, TURNOVER for iSeries v100 checks to see that the Fromsource and object match; that is, that the From-object was created from the From-source. If they do
not match, TURNOVER for iSeries v100 prevents you from submitting a TURNOVER for iSeries
v100 form. Note: If your method is CSCO, this parameter is not relevant; however, we recommend
you set it to your preference anyhow.
Page 1-31
P
T
R
S
C
Page 1-32
Create parameters
If you set Create parameter to P and TURNOVER for iSeries v100 does not find the object in the
target library, then it looks forward through all intermediate libraries until it reaches the production
level. The first time the object is encountered, it is used as the reference object. If TURNOVER for
iSeries v100 fails to find the object in any of these libraries, then it uses the reference object. If you
have not specified a reference object , or if you have set Create parameters to S, TURNOVER for
iSeries v100 uses whatever system defaults are associated with the create command in the global type
code (including special type codes) for the object it is creating.
As stated previously, you specify, in the Create parameters field, the parameters you want
TURNOVER for iSeries v100 to use for objects it creates for the application upon a promotion. If
you do not specify create parameters in the application definition line and type code defaults,
TURNOVER for iSeries v100 uses the default parameter settings for the create command in the
global type code. Next, TURNOVER for iSeries v100 looks for any overrides that previous
developers have applied, shows them to the developer currently performing the change, and prompts
the current developer for his/her overrides.
You can restrict developers from overriding any parameter settings in the create command in the
global type code. You impose these restrictions using settings in the following data areas and file:
TKEYPRTF file
TURNOVER for iSeries v100 protects, or does not protect, create command parameters against user
modification based on the contents (Y or N value) of the one-character data areas, TPROTECT and
TALWKEYOVR, and whether or not the TKEYPRTF file contains a record (such as *ALL CMD)
for the create parameter.
Page 1-33
Results
Contains a Y
value.
TURNOVER for
iSeries v100
protects create
parameters.
TKEYPRTF file
Contains an
N value.
Contains a record
for the parameter.
Contains an
N value.
Contains no record
for the parameter.
TALWKEYOVR
data area
TURNOVER for
iSeries v100 does
not protect create
parameters.
Contains a Y
value.
Note: Your settings only control what developers can override at the development level.
Depending on the promotion methods (for example, CSCO) and create parameters (for
example, P) you have specified, these values could changes during the form run.
Results
Once a form is
copied to another
application or
application level, or
is received on
another computer,
TURNOVER for
iSeries v100 does
not reset nonprotected
parameters that are
explicitly specified in
the global type code.
Page 1-34
ALWLMTUSR
HLPPNLGRP
CURLIB
HLPID
PRDLIB
PMTOVRPGM
Display Files
DEV
DFRWRT
WAITFILE
ENHDSP
MAXDEV
CHRID
WAITRCD
LVLCHK
IGCDTA
DTAQ
RSTDSP
IGCEXNCHR
SHARE
Modules
OPTIMIZE
Physical files
MAXMBRS
SIZE
WAITFILE
REUSEDLT
MAINT
ALLOCATE
WAITRCD
RECOVER
UNIT
DLTPCT
FRCACCPTH
FRCRATION
LVLCHK
Programs
USRPRF
OPTIMIZE
USEADPAUT
FRCCRT
Printer Files
SPOOL
DEV
CPI
JUSTIFY
CTLCHAR
FONT
SCHEDULE
HOLD
MULTIUP
PAGERANGE
FRONTMGN
IGCDTA
IGCSOSI
OUTBIN
WAITFILE
DEVTYPE
OVRFLW
RPLUNPRT
PRTQLTY
CHRID
COPIES
SAVE
DUPLEX
FRONTOVL
BACKMGN
IGCEXNCHR
IGCCDEFNT
SHARE
PAGESIZE
FOLD
PRTTXT
FORMFEED
OUTQ
FORMTYPE
OUTPTY
DFRWRT
BACKOVL
FNTCHRSET
IGCCHRRTT
CHLVAL
LVLCHK
LPI
PAGRTT
ALIGN
DRAWER
MAXRCDS
FILESEP
USRDTA
UOM
FIDELITY
ODEFNT
IGCCPI
REDUCE
Service Programs
USRPRF
User-defined objects
Page 1-35
12 To void this rule, you can set the Global default parameter Use delete test object rule to N. See Main Menu option 8, then option 5.
Page 1-36
Type Codes
The Type Codes panel displays the valid TURNOVER for iSeries v100 object types for your
application. The type of objects valid for one application may vary from those of another.
TURNOVER for iSeries v100 lets you set those by application. The TURNOVER for iSeries
v100 type codes you use should be consistent from one application level to another.
1/29/10
11:07:43
Type Codes
Application: AP
Rel:
2=Maintain definition
Type
CBL
CBLLE
CLP
CMD
DOC
DSPF
DTAARA
LF
LFDUP
MSGF
PF
PFDUP
PFREF
Ver:
Lev:
Data
Description
Obj.
Cobol/400 program
N
ILE CBL Program
N
CL Program
N
Command
N
Documents
N
AS/400 Display File
N
Data Area
Y
AS/400 Logical File
Y
SYNON Condition values LF N
Message File
Y
AS/400 Physical File
Y
SYNON Condition values PF N
PF-Field Reference
N
Source
File
QLBLSRC
QCBLLESRC
QCLSRC
QCMDSRC
Creation
Reference
QDDSSRC
QDDSSRC
QDDSSRC
QDDSSRC
More...
F3=Exit
F4=Add/Delete types
F8=User-defined parameters
Press F4 (panel not shown) to work with the list of all the available TURNOVER for iSeries
v100 type codes and to select or deselect the object types appropriate for this application.
Afterwards, this panel contains just the types that are appropriate for this application.
Select the type codes by entering a 1 next to the appropriate object types, or deselect types by
removing the 1. If the application includes additional levels, then another panel is displayed,
prompting you to add or remove the same type codes from all levels to which youre authorized.
Press Enter. This panel reappears, containing just the subset of types you selected.
Press F6 to view a list of missing libraries, source files, and reference objects for this application
level, with options to create these missing items.
Press F8 to view and specify defaults for User-defined parameters. (For more about user-defined
parameters, see page 1-41.)
Page 1-37
14:40:18
Application: AP
1=Run command
1
1
1
1
1
1
1
Ver:
Lev:
Create command
CRTSRCPF FILE(DEVTEST/QLBLSRC) TEXT('CBL source file')
CRTSRCPF FILE(ACPTTEST/QLBLSRC) TEXT('CBL source file')
CRTSRCPF FILE(ACPTTEST/QCBLLESRC) TEXT('CBLLE source file')
CRTSRCPF FILE(ACPTTEST/UDDSSRC) TEXT('PFASI source file')
CRTSRCPF FILE(PRODTEST/UDDSSRC) TEXT('PFASI source file')
CRTSRCPF FILE(ACPTTEST/QRPGLESRC) TEXT('RPGMOX source file')
CRTSRCPF FILE(PRODTEST/QRPGLESRC) TEXT('RPGMOX source file')
Type
SRC-PF
SRC-PF
SRC-PF
SRC-PF
SRC-PF
SRC-PF
SRC-PF
Bottom
F3=Exit
Page 1-38
F12=Cancel
F21=Command line
CLP
Application: AP
Defaults
Rel:
Ver:
Lev:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. QCLSRC
.
DEVTEST
. QCLSRC
.
ACPTTEST
Name
Name, *PGMR
Name
Name
Field Attributes
R=Restrict, L=Lock
L
L
L
L
Name, *PGMR
Name
. . . . . . . . .
Y, N
Y, N
Method . . . . . . . . . . . .
F3=Exit
L
L
F12=Cancel
More...
13 The recommended record length of the ILE RPG source file is 112 bytes rather than the previous standard default of 92 bytes. For more information,
see the TURNOVER for iSeries v100 Supplement entitled Managing ILE Programs (#60).
14 Defaults for IFS objects look different than those shown in these panels. For detailed information, see the IFS guide, Managing Integrated File
System (IFS) Objects Using TURNOVER for iSeries v100.
Page 1-39
1/29/10
11:20:46
CLP
Application: AP
Defaults
Rel:
Ver:
Lev:
P, T, S, R, C
Name, REF*
Authority . . . . . . . . . . P
Authority reference object . .
Library . . . . . . . .
P, T, S, R
Name, REF*
Distribute . . . . . . . . . .
F3=Exit
F12=Cancel
Bottom
The [type code] Defaults panel identifies the From Source file and Target Source file (usually
QxxxSRC) and their respective libraries to be used by TURNOVER for iSeries v100. It also
identifies other information such as the From object library and Target object library for this object
type. These can be specified globally for your application level (see Library Defaults on page 1-18),
but you may want to set up one or more object types differently here. Test source for level one might
be in a programmer library or a common development library; production might share one library or
many application libraries. Read the online Help to see what values you can type here.
Notice that many of the defaults that can be specified on the type entry were also specified for the
application and level on the Library Defaults and Line Defaults panels. These remain in effect
unless you specify some other value for an object type default. Leave these blank or unchanged
unless you want the object type to be treated differently. Entries you make at this level take
precedence.
UNICOM Systems, Inc. Recommends
If you have non-standard source file names that cannot be set as defaults here, you may want to use an
exit program to set the source file name programmatically using some other criteria. For example,
maybe your source files are named differently for different parts of your application, having names
such as APSRC, ARSRC, and so on, and can be determined based on how the object itself is named.
TURNOVER for iSeries v100 provides many exit points and exit program samples. 15 For more
about defining Exit programs, see Chapter 8: Utility Menu.
Specialized type codes
You might have certain data objects that you want to store in a library other than the data object
library specified for your application. You can do this by creating a specialized type code, such as
15 Read about Exit 5 in the online Help text for the Work with Exits panel (option 7 on the Utility Menu) or see the TURNOVER for iSeries v100
Supplement entitled TURNOVER for iSeries v100 Exits and APIs (#30).
Page 1-40
Descr iptio n
Targe t rel ease
Gener ation opti ons
Debug ging views
Optim izati on le vel
Targe t Rel ease
no ra nge c hecki ng
Bindi ng Di recto ry
Unass igned
Unass igned
Unass igned
Unass igned
F 3=Exi t
Keyw ord
TGTR LS
GENO PT
DBGV IEW
OPTI MIZE
TGTR LS
GENO PT
BNDD IR
Def ault
V5R 1M0
*NO OPTIM IZE
*ST MT
*NO NE
F 12=Ca ncel
You can only assign values to those user-defined options that have been defined globally for your
organization. See Main Menu option 8, then option 4 to change type code entries and maintain the list
of these user-defined parameters. You must have special authority to change these parameters.
Page 1-41
Page 1-42
Authorized Users
You can specify which users should be authorized to work with each application. See also Main
Menu option 3 (Maintain TURNOVER for iSeries authority).
1/29/10
13:45:10
Authorized Users
Application: AP
Test Application
Rel:
Ver:
Lev: 1
1=Authorize User
2=Reset User to default authority
1
1
1
1
1
User
*NONE
AUSER
BENNETT
BIKER
COWLES
ELSINORE
FRENCH
GROVES
HAMMON
JONES
LAWSON
MATHEWS
F3=Exit
F11=Authority
+
F12=Cancel
Type 1 next to each profile who can work with this application. An Application Authority
Maintenance panel appears.
Press F11 to view or update a more detailed view of specific application level authorities. For
more information, see Chapter 3: Authorizing Users To TURNOVER for iSeries v100.
You can work with and view only those applications to which you have been granted authority.
Page 1-43
Distribution Defaults
When changes are successfully promoted to the production level 16 of your application on your
development computer, the changes can be distributed to your remote computer. These changes can
be distributed automatically or manually. For more information, see Chapter 11: Distributing
Changes to Production Computers.
1/29/10
14:13:16
Application
Rel
Ver
Lev
Description
.
.
.
.
.
.
.
.
.
.
. AP
Position to system . . .
.
.
. 1
. Test Application- Prod Level 1
System
JM
SLSWEB
S1014706
S1014706
S1014707
SLSTRAIN
*V45011
*V45012
Device
*SNADS
*SNADS
*SNADS
*SNADS
*SNADS
*SNADS
*SNADS
*SNADS
2=Change distribution
System description
Non existent, to test failure
SLS Web Server
200 QA Environment
4.2 to 4.1 Distribution
4.2 to 4.2 Designed to fail
SLS Training box
Virtual system
Virtual
For the application and level with which you are working, you can select those systems to which you
want to distribute changes. For example, you may have several computers, but your application runs
on only a few of them. Select the systems by typing 1 next to those that are appropriate.
You can also indicate that, for this application and level, objects and/or source should be included in
the distribution. In fact, you can choose whether objects and/or source should be sent by computer,
application, and object type. Object distribution parameters exist in the system definition, the
application definition and the type definition within the application defaults. An entry of *SYSTEM
here in the application definition tells TURNOVER for iSeries v100 to use the distribution Send
defaults as they appear in the system definition. (For more about distribution defaults, see Chapter
11: Distributing Changes to Production Computers.)
16 Some companies distribute changes when they are promoted to a test level for user testing and again when changes are promoted to production. You
Page 1-44
Approval Lists
Approval lists can be defined for any application and level; however, they are not required.
TURNOVER for iSeries v100 forms may require approval by different people at different levels of
your application. For example, a programming manager may be required to approve a form before it
is promoted to level 1, while the MIS manager and a user department manager must approve the form
before it is promoted to level 2.
The Approval List panel lets you specify a named approval list object to associate with your
application definition.
1/29/10
13:40:23
Approval List
Application
Release . .
Version . .
Level . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. YCAP
. 1
. 0
. 10
*YES, *NO
F4=List
5=Display
User
BIKER
COWLES
MANAGER
SMITH
F3=Exit
Admin
N
N
F4=List
Notify
Y
Y
Y
Override
N
N
Y
N
Approve
Own Form
Y
Y
Y
Type
*USRPRF
*USRPRF
*GROUP
*USRPRF
MsgQ
BIKER
COWLES
MsgQ Lib
QUSRSYS
QUSRSYS
SMITH
QUSRSYS
F12=Cancel
An approval list object contains any combination of user profiles and/or Approval groups. You can
give any user authority to approve for other people on the list, in case of absence, by granting that
user Override authority. An Approval group is a list of users, any one of whom must approve
changes before a form is run. For example, you may have a Quality Assurance department. Anyone
within that departmental group can be responsible for reviewing approving your changes. In other
words, approval by any member of the group constitutes approval by the entire group.
If the approval user usually works on another production computer, you can instruct TURNOVER
for iSeries v100 to send a message to the persons profile on that computer. That user must either
pass-through to the development computer to view details and approve the form, or use the Eclipsebased TURNOVER for iSeries v100 Administrator module.
Named approval list objects make it easier to assign one list to other applications or application levels.
To select an approval list object, position your cursor to Approval list name and press F4.
Page 1-45
2=Change
List
MYAPPRVRS
PRODUCTION
4=Delete
5=Display
7=Usage
Description
My Application Approvers
Production approval list
Bottom
F3=Exit
F6=Add
F12=Cancel
From here, you can select from and/or maintain all available approval list objects.
To choose an existing approval list, select it option 1 and press Enter. To create a new approval list
object, use F6. To change an existing list, use option 2. To delete a list, use option 4. To view the
contents of a list, use option 5.
To see what applications use an approval list object, use option 7.
When creating a new approval list object, you must first name it. You can then add users or groups to
your approval list object.
If you use option 2 to change an approval list object, you can then add or remove users and groups.
Once youve selected or defined a list, you can exit and then select that new Approval list object to be
used for your application.
UNICOM Systems, Inc. Recommends
Approval list objects are named lists and consist of Approval Groups and/or individual user profiles.
Approval list objects can be reused for several applications, to avoid re-keying the same list of users
over and over again. Approval Groups themselves can be named and reused in several Approval lists.
So, to avoid confusion:
1) If you intend to use Approval Groups, create your Approval Groups first. (Use this dialog, or use
the WRKAPPGRP command.)
2) Create your Approval list objects. (Use this dialog, or use the WRKAPPLST command.)
3) Assign the Approval list object to your applications. (Use this dialog.)
Its easier to understand what you see on the various approval list panels, if you do it in this order.
Page 1-46
Page 1-47
Application: AP
Rel: 00 Ver: 00
Description: Test Application
Lev: 01
Message:
Message Queue
Library .
or
User ID . . .
Address. .
F3=Exit
Page 1-48
. . . . . .
. . . . . .
Name
Name, *LIBL
. . . . . .
. . . . . .
Character Value
Character Value
F12=Cancel
Application Relationships
Application definitions can be interrelated so that changes in one application prompt you to check to
see if a similar change is required for a related application.
The Work with Application Relationships panel shows all existing application relationships for your
current (or selected) application. You can also display this panel by selecting the application
definition with option 19=Application relations on either the Work with Application Definitions
panel or the Work with Application Definition panel.
1/29/10
Selected application
Release . . . . .
Version . . . . .
Parent application .
Release . . . . .
Version . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
. AP
Test Application
.
.
. *NONE F7=Select parent
.
.
Appl
ACAM
ADIS
AMER
AP3
2=Change rule
Rel Ver
New Obj.
Rule
*NONE
*NONE
*NONE
*NONE
*NONE
Description
ACAM application
Distribution Application
American Software
Application3
Bottom
F3=Exit
F4=Select child
F7=Select parent
F12=Cancel
The names of the selected application and its parent application appear at the top of this panel. The
names of any applications that have child relationships with the selected application are listed on the
panels lower half. Options let you add and remove relationships between the selected application
and its child applications, and set new object rules for these relationships.
UNICOM Systems, Inc. Caution
Interrelating applications is a specialized function that may or may not apply to your company. We
recommend that you thoroughly understand it and build test cases of your own before you apply it in
your production environment. For more about related applications and managing versions of
software, see the TURNOVER for iSeries v100 Supplement entitled Managing Multiple Versions
(#63).
What you can do:
1=Add child
Add a new child relationship to the selected application. Select the topmost blank line with
this option, then type the application code, release, version, and new object rule. Press F4 to
display a list of applications from which you can select the child application.
Page 1-49
Page 1-50
Help you quickly identify the version of a specific object, especially, by differentiating it from its
predecessors and successors;
Tell exactly how an object was changed, who changed it, why it was changed, and so on, every time it
was changed, throughout the objects life.
The Version and Object Stamping Defaults panel lets you control whether or not the object
description of the object TURNOVER for iSeries v100 promotes is to be updated by
TURNOVER for iSeries v100. 17
1/29/10
13:30:19
Y, N
Values to stamp:
Object version number
Form number . . . . .
Project/task reference
TurnOver type code . .
Y,
Y,
Y,
Y,
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Y
Y
Y
Y
N
N
N
N
F12=Cancel
17 For a more in-depth discussion of object stamping, see the TURNOVER for iSeries v100 Supplement entitled Managing Multiple Versions (#63).
Page 1-51
Page 1-52
18 Each chapter in this User Guide corresponds with a TURNOVER for iSeries v100 Main Menu option.
Page 2-1
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F24=More keys
Page 2-2
2=Change
_
_
_
_
4=Delete
Programmer
BERNARDI
ELSINOR
PHILLIPS
PSHIFTY
Data
Library
BERNARDI
ELSINORE
PHILLIPS
TESTLIB
Programmer Name
Irvin Bernard
Steve Elsinore
Ed Phillips
Peter Shifty
Other
Object
Library
BERNARDI
ELSINORE
PHILLIPS
TESTLIB
F3=Exit
F12=Cancel
F10=Additional parameters
F4=Add from List
F5=Fold/Unfold
F6=Add Programmer
Source
Library
BERNARDI
ELSINORE
PHILLIPS
TESTLIB
Rate
20.00
60.00
45.00
25.00
F21=System command
Use F10 to define up to four 10-character user-defined fields. These fields are primarily used for
CASE interfaces; otherwise they are not used by TURNOVER for iSeries v100. Once youve
defined one, you can enter a value as an additional parameter on either the Add or the Change a
Programmer Profile panel.
.
.
.
.
.
.
.
.
.
.
.
.
__________
__________
__________
__________
__________
__________
Name
Name
Name
Name
Name
Name
F12=Cancel
F10=Additional parameters
Type the User profile name and press Enter. TURNOVER for iSeries v100 will retrieve and
display the rest of the information on the panel. Complete or change the information. If user-defined
fields are available for this programmer, then F10 appears, and you can use it to provide additional
information as necessary.
Page 2-3
Page 2-4
Wo rk wi th ob ject histor y
Ch eck-o ut/ch eck-i n sour ce
Wo rk wi th fo rms
Su bmit a for m to run
Ut ility menu
Wo rk wi th Pr oject s and Tasks
Re porti ng me nu
Di strib ution menu
Pr ogram mer W orkli st Man ager
F6 =DSPM SG
F12= Cance l
F24=Mo re ke ys
Page 3-1
2=Project authority
3=Wisedesk
4=Delete user
Source -------- FORMS --------- -- SYSTEM -- ----- PROJECTS ----Out In View Add Chg Run Dst Prg Dft Aut Pgmr Use Add Code Rsc Rqs
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
More...
F4=Add from List F6=Add User F12=Cancel F21=System command
User
BENNETT
BLAKE
DONNA
DUMMY
ELMSMIKE
GILLIGAN
GUEST
KING
MORKPHIL
MILLER
MARYLYN
QPGMR
F3=Exit
Press F6 to enter a new user profile name to the list. (To add multiple users, press F4 and select
them from the list.)
Page 3-2
SOURCE Authority
Source authority options permit a user to checkout and/or check-in source code using TURNOVER
for iSeries v100.
Note: TURNOVER for iSeries v100 automatically checks in source when a TURNOVER for
iSeries v100 form is run. Manual check-in only needs to be done if you decide not to change an
object after checking out source, or if a task was canceled. Production source is not affected by
source check-in. Manual check-in frees a lock on the source so it is available for someone else to
check out. It also lets you delete test source and objects from your development library.
FORMS Authority
View -
Chg
Add
Allows a user to enter a new TURNOVER for iSeries v100 form into the system.
Run
Allows a user to submit a TURNOVER for iSeries v100 form for processing and to
distribute TURNOVER for iSeries v100 to remote computers (if applicable).
Dst
Allows a user to change distribution defaults and to manually distribute and receive
TURNOVER for iSeries v100 forms.
Prg
Allows a user to purge old forms for those applications on which he/she is authorized to
work.
Note: A user may be authorized generally to run TURNOVER for iSeries v100 forms, but an
application Administrator may be the only one allowed to run TURNOVER for iSeries v100 forms
for a particular application.
SYSTEM Authority
Dft
Aut
Pgmr - Indicates that the user can maintain TURNOVER for iSeries v100 programmer
information.
Note: In a multi-level application, if you want to allow programmers to have run authority to a lower
level application, you can use application approval-lists as an alternative. For more information, see
Approval Lists on page 1-45.
Page 3-3
PROJECTS Authority
These columns appear only if you have elected to use the TURNOVER for iSeries v100 Projects
system.
Use
Add
Code -
Lets the user maintain user-defined code tables within the project system, such as the
status code table or other user-defined fields.
Rsc
Rqs
You must have authority to the project system to grant others access. You also need access to a
specific project in order to work on that project. This should be done when you or others define
projects to TURNOVER for iSeries v100. If projects are already defined, select a user in the
authority list with option 2=Project Authorities to grant authority to a specific project. If Wisedesk
help trees are defined, select option 3=Wisedesk to grant authority to specific decision trees. For
more information, see Chapter 9: Working with Projects and Tasks.
The Administrator(s) is usually given authority to all project system functions except Requester
Maintenance. (The requester file contains all of your departments or companys clients or contacts.)
Page 3-4
User: BENNETT
1=Authorize User
Fltr:
Appl
1
1
1
1
1
1
1
1
1
1
1
1
AKM
AKM
AKM
AP
AP
APE
APP
APP
APPO
APTS
APTS
F3=Exit
Bob Bennett
2=Reset User to default authority
F12=Cancel
F13=Authorize all
SYSTEM
Dfts
X
X
X
X
X
X
X
X
X
X
X
F21=Command Line
Use the Fltr: fields to specify criteria with which to further limit the list of applications that
appears. All filter values you specify are combined, so the results show only those applications
that meet all the filter values you typed. Enter or F3 on this panel saves the current filter settings
for use during the next session; F12 neither saves filter values upon exit, nor replaces existing
saved filters. Filter fields you can specify also toggle when you use F11, but filters that have been
toggled out of view remain in effect. Read the online help for more detailed information about
filters.
Press F13 to toggle authority for all currently-selected records. Pressing once grants authority;
pressing again removes authority.
Page 3-5
Field-Exit (blank) the 1s next to any application to which you do not want the user to have
authority.
Page 3-6
If you also need to delete the user from the list of requesters, then:
This procedure does not deactivate the user profile or remove the user profile from the iSeries. If
appropriate, be sure to do these steps as well.
Page 3-7
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F24=More keys
Select option 4 to work with TURNOVER for iSeries v100 object history.
You can also access the Work with Object History panel by typing the command TURNOVER 4 on
a command line and as a user option from the Programmers Worklist panel.
For field definitions press F1/Help.
Page 4-1
Apply filters . . N
Filter name: *DEFAULT
1=Browse current source 2=Browse archived source 3=Copy archived source
5=View form 6=Data explosion
7=Checkout
8=Archive information ...
Exists
Chk
Object
Library
Type
Run Date Appl Rl Vr Lv
Cd Obj Src Arc
Out
MENCACTU
T54PRDS
PF
3/02/06
A
N
N
N
N
MENCADDU
T54PRDS
PF
3/04/06
TO
5 4 2
N
N
N
N
MENCADDU
T54PRDS
PF
3/04/06
TO
5 4 2
N
N
N
N
MENCADSA
T54PRDS
PF
6/28/06
TO
5 4 2
N
N
N
N
MENCATST
T54PRDS
PF
6/28/06
TO
5 4 2
N
N
N
N
MENCATTN
T54PRDS
PF
7/04/06
TO
5 4 2
N
N
N
N
MENCATTY
T54PRDS
PF
7/18/06
TO
5 4 2
N
N
N
N
MENCBADS
T54PRDS
PF
7/27/06
TO
5 4 2
A
Y
N
N
N
MENCBADS
T54PRDS
PF
7/29/06
TO
5 4 2
A
N
N
N
N
MENCCACT
T54PRDS
PF
8/01/06
TO
5 4 2
Y
N
N
N
MENCCAND
T54PRDS
PF
8/02/06
TO
5 4 2
N
N
N
N
MENCDATU
T54PRDS
PF
8/09/06 TO
5 4 2
N
N
N
N
More...
F3=Exit F5=Refresh F8=IFS history F11=Alt. view F12=Cancel F24=More keys
F23=More options:
9=View task 10=Checkout history
16=Dist History
F24=More keys:
F16=User options
F17=Filters
11=Line details
F21=Cmd. line
This panel offers a variety of options, including view, browse, copy, and checkout options; and it
displays object-related information. The Exists Arc column indicates whether or not archived source
exists. The Chk Out column indicates whether or not the source for this object is currently checked
out.
Select option 11 (Line details) for more details about any of the objects displayed here. (See
description is later in this chapter.)
Select option 12 (Compare source) to invoke the source compare function. (See description later in
this chapter.)
You can use TURNOVER for iSeries v100 user-defined options to define other functions you may
want to do. Press F16 to see the user-defined options already available, if there are any.
You can specify criteria to have TURNOVER for iSeries v100 list the most recent record for each
object, or to list all objects, on the Work with Object History panel. You can view objects associated
with applications with which you are authorized to work.
To position the subfile to an object, type the object name at the top of the display. TURNOVER for
iSeries v100 sequences objects by object name and sorts them alphabetically or by date.
Page 4-2
Page 4-3
Object: AAITVAL
Attr: DTAARA
Library: QGPL
Pgmr:
Form: 5103356 Initial Application Load
Action:
11/20/98 18:34:15
Src archived: N
Obj archived: N
Line: 378 Sts: Initial
Version: 001 000
+ Number of checkout records: 2
Line Comments
The line comment, if it exists, is displayed here with a +
Following if additional comment lines exist.
Task Details
Details for the project or task are displayed here if they exist.
F3=Exit
F17=Previous change
Page 4-4
F10=View form
F11=View line
F12=Cancel
F24=More keys
Member
TURCADDL
Bottom
F3=Exit
F12=Cancel
F4=Prompt
F14=WRKSBMJOB
Page 4-5
Appl:
This panel lists the most recent TURNOVER for iSeries v100 record for each IFS object.
Only objects that are associated with applications to which youre authorized are displayed.
See the online Help for a description of the fields displayed for each object. For detailed
information, see the IFS guide, Managing Integrated File System (IFS) Objects Using
TURNOVER for iSeries.
Page 4-6
Library
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
T100PRDS
F5=Refresh
Type
PF
PF
PF
PF
PF
PF
PF
PF
PF
PF
PF
PF
Run Date
1/02/10
1/04/10
1/04/10
1/28/10
1/28/10
1/04/10
1/18/10
1/27/10
1/29/10
1/01/10
1/02/10
1/09/10
F8=IFS history
Programmer
SAMK
SAMK
SAMK
SAMK
SAMK
SAMK
SAMK
SAMK
SAMK
SAMK
SAMK
SAMK
F11=Alt. view
F16=User options
Enter your own user-defined options.
F17=Filters
Press F17 to see the Filtering panel on which you can define filtering criteria for objects you
want listed on the Work with Object History panel. Once you define your criteria, you can
press F17 (again) on the Filtering panel to save your settings. For more information, see
Filtering objects on page 4-13.
F21=System Command
Press F21 to work on a command line.
F23=More options
Press F23 to view additional options.
F24=More keys
Press F24 to view additional keys.
Page 4-7
Apply filters . . Y
Filter name: *DEFAULT
L
D
D
D
D
D
D
D
D
D
D
D
D
Bottom
F2=Maintain Filters
F5=Refresh
F8=IFS history
F3=Exit
F12=Cancel
F11=Alt. view
More...
F12=Cancel F24=More keys
The Select Named Filter panel lists the existing named filters. You can select a filter name with
option 1 and press Enter to apply that filters criteria to the list of objects on the Work with Object
History panel. On that panel, TURNOVER for iSeries v100 sets the Apply filters flag to Y (if it is
not already set to that) to indicate that you have applied filtering criteria, it replaces the value in the
Filter name field with the name of the filter you are have selected, and it removes the popup panel. If
you now pressed F17 (if you do not see F17 at the bottom of the panel, press F24 to see more keys), a
Filtering popup panel will appear. This panel shows the filtering criteria associated with the named
filter you have selected (see Filtering objects on page 4-13).
Page 4-8
1=Add
2=Change
3=Copy
4=Delete
5=View
Name
Description
*DEFAULT
KING_OBJ
RANOK_WRN
RECOVER
Bottom
F3=Exit
F5=Refresh
F11=Show Shared
F12=Cancel
F21=System Command
The Named Filter Maintenance panel lists the existing named filters and provides options for
working with them. If your filter names list becomes lengthy, you can press the Home key to position
your cursor on the Position to field. In that field, you can type a filter name (and press Enter) to
quickly position your cursor on that filter name in the list.
Page 4-9
1=Add
2=Change
Name
READYOBJS
*DEFAULT
KING_OBJ
RANOK_WRN
RECOVER
3=Copy
4=Delete
5=View
Description
Bottom
F3=Exit
F5=Refresh
F11=Show Shared
F12=Cancel
F21=System Command
Press Enter.
TURNOVER for iSeries v100 displays the new filter name at the top of the Filtering panel. You
can now type a filter description (of up to 40 characters) in the field to the right of the filter name and
supply the filtering criteria beneath that:
1/29/10
12:
Named
Filter name
Filter Maintenance
Your Company,
Type a description
here.
Inc.
Filtering
1=A
F3=
Page 4-10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Test Value
List values
. . .
. . .
. . .
Specify
your filtering criteria here.
. . .
. . .
. . .
. . .
. . .
. . .
and
. . .
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Named filter READYOBJS does not exist. Press ENTER to create.
1=A
F3=
Filtering
Filter name: READYOBJS Objects with a Ready status
Select one or more filters:
Field
Object . . . . . . .
Library. . . . . . .
Type code. . . . . .
Object type. . . . .
Programmer . . . . .
Reference. . . . . .
Line status. . . . .
Action code (A/R/D).
Run date . . . . . .
Form . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Test
Value
EQ
READY
.
.
.
.
.
.
.
.
.
.
List values
and
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Named filter READYOBJS does not exist. Press ENTER to create.
Press F17 to save your criteria settings (and then press Enter to create the filter) or press Enter twice
to save your criteria and create the filter. (For detailed information about defining your filtering
criteria, see Filtering objects on page 4-13.)
Maintaining named filters
You can change, copy, delete, and view named filters listed on the Named Filter Maintenance panel.
You do so by selecting a named filter set with the desired option (2=Change, 3=Copy, 4=Delete,
5=View) and pressing Enter. When you select a filter set with options 2 or 5, TURNOVER for
iSeries v100 displays the filter name, description, and criteria on the Filtering panel. You can change
the filter description and criteria (option 2) or just view the filter information (option 5). While
viewing the criteria for a named filter, you can press F19 (Previous) or F20 (Next) to scan the criteria
settings for the other named filter sets, one by one.
When you select a filter set with option 4 (Delete), TURNOVER for iSeries v100 asks you to
confirm your choice. Press Enter delete the filter set. TURNOVER for iSeries v100 deletes it and
removes its name from the named filters list.
You can duplicate an existing filter set to create a new named set, and change the new filter sets
name, description, and criteria as you want. Also, if you want to make a filter set available to other
users, you can copy it to a shared filter set.
Page 4-11
Copy Filter
1=A
To Filter: READYOBJS
Type: *USER
F3=Exit
F12=Cancel
Bottom
F3=Exit
F5=Refresh
F11=Show Shared
F12=Cancel
F21=System Command
Use this Copy Filter panel to supply the name and description of the new filter set. You can also
specify the type of filter youre creating (*USER or *SHARED). Descriptions of the filter types
follow:
*USER filter sets are private that is, they are specific to your user profile. Only you have
access to these filter sets.
*SHARED filter sets are a pool of named filter sets that are shared among users. Only users
with System Aut authority can delete shared filter sets.
You can interchange user and shared filter sets when copying:
*USER to *USER Copy a private filter set to and provide a new name to modify the filter
set name or type, while retaining the original criteria settings.
*USER to *SHARED Copy a private filter set to a shared filter set to make it available to
others to copy to their own private filters. Any changes you and others subsequently make to
the private filter will not affect the shared filter set. If a shared filter set with that name
already exists, you must supply a new name.
*SHARED to *USER Copy shared filter sets to user filter sets to create your own private
versions. Any changes you subsequently make to the resulting private filter set will not affect
the originating shared filter set. If you already have a user filter with the same name, you must
supply a new name.
*SHARED to *SHARED You cannot modify shared filters. Therefore, this copy function
is not permitted.
Page 4-12
Filtering objects
You see the Filtering popup panel when you add and maintain filter names (as described on the
previous pages) or when you press F17=Filters on the Work with Object History panel. 19 The
Filtering panel follows:
1/29/10
12:
Filtering
To
1=B
5=V
Field
Object . . . . . . .
Library. . . . . . .
Type code. . . . . .
Object type. . . . .
Programmer . . . . .
Reference. . . . . .
Line status. . . . .
Action code (A/R/D).
Run date . . . . . .
Form . . . . . . . .
F3=Exit
F4=Prompt
Test
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Value
.
.
.
.
.
.
.
.
.
.
List values
and
F5=Refresh F11=List
F12=Cancel
More...
F17=Save Filters
F16
Page down
1/29/10
12:
Filtering
To
1=B
5=V
Test
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Object exists. . . . .
Source exists. . . . .
Archived source exists
Checked out. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F3=Exit
F4=Prompt
F5=Refresh F11=List
Value
List values
days. . . N
F12=Cancel
More...
F17=Save Filters
F3=
19 You will initially see the Filtering panel upon entering object history if you have set the Prompt for filters when entering object history field to Y.
Page 4-13
Description
Equals
Not equals
Greater than
Less than
Greater
than
or
Equal to
Less than or Equal
to
Contains
Between
In the defined list
Not in the defined
list
Do not test
Notes:
1.
Use CT to see information for specific characters. For CT, you must specify a value that
begins with a percent sign (%), ends with a percent sign, or both. Also, with CT, you can use an
underscore in the value to indicate that any single character must occupy that position. For example,
if you wanted to see information for programmer TJEFFERSON, you could specify %JEFF% in the
Programmer field. However, you would also see information for programmer TJEFFERSON if you
specified %ERS_N (this has one underscore) or __EFF% (this has two underscores).
2.
Use LI to see information for multiple values. For example, you might want to see a list of
forms run by a programmer who has multiple User IDs. Specify LI as the test and press F11 to define
the list of User IDs. Your results will only include information for User IDs in your list.
3.
Use NL to exclude information for multiple values. For example, you might want to see a list
of forms run by all programmers except AUSER and SMITH. Specify NL as the test and press F11 to
define the list of User IDs (AUSER and SMITH) you want excluded. Your results will include
information for all User IDs except AUSER and SMITH.
4.
Use XX to retain a value that you often, but do not always, test. Specify XX with a value
when you want TURNOVER for iSeries v100 to ignore that value.
Page 4-14
The default
Test value
becomes
a
CT
LI
BT
Another field appears at the bottom of the Filtering panel. A description follows:
Include only objects run in the past 0 days
Specify for how many days you want TURNOVER for iSeries v100 to display objects that
have been promoted. TURNOVER for iSeries v100 will only display objects promoted
within the number of days that you specify. For example, if you use the default value of 0
days, TURNOVER for iSeries v100 will only show objects promoted today (the current
day). If you specify a value of 1 day, TURNOVER for iSeries v100 will show objects
promoted yesterday and today. If you specify a value of 2 days, TURNOVER for iSeries
v100 will show objects promoted the day before yesterday, yesterday, and today. You can
specify up to 999 days.
Note: You might have a particular number of days that you repeatedly reuse. If you specify
that number in this field, you can use the field (Y/N) to the right to toggle this criteria setting
on and off.
Page 4-15
Additional Options
To
User specific settings:
1=B
5=V
F3=Exit
F4=Prompt
F5=Refresh
F12=Cancel
Y
Y
name, *LAST
Y
Y
Bottom
F17=Save Filters
F3=
If you type Y,
TURNOVER for iSeries v100 sorts in this
order
Field
Description
Field
Description
Object
Run Date
Type
Code
Object
Type
Code
Library
Run Date
Library
Run Time
Form
Run
Time
Line
Form
Line
Page 4-16
F3 - When you press F3 to exit the Filtering panel, TURNOVER for iSeries v100 does
not save any filtering changes you have made and does not show you the Work with
Object History panel.
F12 When you press F12 to exit the Filtering panel, TURNOVER for iSeries v100
does not save any filtering changes you have made but does show you the Work with
Object History panel.
Enter When you press Enter to exit the Filtering panel, TURNOVER for iSeries
v100 saves any filtering changes you have made and shows you the Work with Object
History panel.
20 TURNOVER for iSeries v100 only recognizes the value you specify for this Prompt for filters when entering object history field when you access
object history from the TURNOVER for iSeries v100 Main Menu. When you access object history for a particular object (for example, if you use the
TDSPOBJD command) or for a particular reference (for example, if you select a task on the Work with Tasks panel with option 18=Object history),
TURNOVER for iSeries v100 will automatically apply filters based on that object or reference.
Page 4-17
If you type Y here but have set Prompt for filters when entering object history to N,
TURNOVER for iSeries v100 will automatically apply any filtering criteria you
previously saved.
If you type N here and have set Prompt for filters when entering object history to N,
TURNOVER for iSeries v100 will not automatically apply any filtering criteria you
previously saved. However, you can instruct TURNOVER for iSeries v100 to apply
those criteria by setting the Apply filters flag (on the Work with Object History panel) to
Y. 21
21 When you access object history for a particular object (for example, if you use the TDSPOBJD command) or for a particular reference (for example,
if you select a task on the Work with Tasks panel with option 18=Object history), TURNOVER for iSeries v100 will automatically apply filters based
on that object or reference.
Page 4-18
1=A
Filtering
Filter name: LAST30DAYS Appl BFFJ & Objects Promoted this month
Select one or more filters:
Field
Application.
Release. .
Version. .
Level. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Object exists. . . . .
Source exists. . . . .
Archived source exists
Checked out. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Test
EQ
F3=
F3=Exit
F4=Prompt
F5=Refresh F11=List
Value
BFFJ
30
List values
days. . . Y
F12=Cancel
More...
F17=Save Filters
Page 4-19
Library
J73SLSOBJ
J73TSTOBJ
J73SLSOBJ
J73TSTOBJ
J73SLSOBJ
J73TSTOBJ
J73SLSOBJ
J73TSTOBJ
J73SLSOBJ
J73TSTOBJ
Type
Run Date
CLPJDE 8/02/09
CLPJDE 8/02/09
RPGJDE 8/02/09
RPGJDE 8/02/09
RPGJDE 8/02/09
RPGJDE 8/02/09
PRTJD3 8/02/09
PRTJD3 8/02/09
DSPJDE 8/02/09
DSPJDE 8/02/09
Appl Rl
BFFJ 7
BFFJ 7
BFFJ 7
BFFJ 7
BFFJ 7
BFFJ 7
BFFJ 7
BFFJ 7
BFFJ 7
BFFJ 7
Apply filters . . Y
Filter name: LAST30DAYS
3=Copy archived source
8=Archive information ...
Exists
Chk
Vr Lv
Cd Obj Src Arc
Out
3 2
R
Y
Y
Y
N
3 1
R
N
N
Y
N
3 2
R
Y
Y
N
N
3 1
R
N
N
N
N
3 2
R
Y
Y
Y
N
3 1
R
N
N
Y
N
3 2
R
Y
Y
Y
N
3 1
R
N
N
Y
N
3 2
R
Y
Y
Y
N
3 1
R
N
N
Y
N
F11=Alt. view
Bottom
F12=Cancel F24=More keys
Here, all objects that have been promoted under application BFFJ within the past 30 days (see
the dates under Run Date) are shown.
Example 2: Filter by objects modified for a particular task reference and application level
This example shows how you can filter objects to only see those that have been modified for a
particular task reference and application level. The information provided by these settings
could help you determine what objects you need to work with to make additional changes for a
task.
1/29/10
12:
1=A
F3=
Page 4-20
Test
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Filtering
Production objects modified for REGT0136
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
EQ
Value
List values
REGT0136
and
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Named filter REGT0136 does not exist. Press ENTER to create.
1=A
Filtering
Filter name: REGT0136
Production objects modified for REGT0136
Select one or more filters:
Field
Application.
Release. .
Version. .
Level. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Object exists. . . . .
Source exists. . . . .
Archived source exists
Checked out. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Test
EQ
EQ
EQ
EQ
F3=
F3=Exit
F4=Prompt
F5=Refresh F11=List
Value
REGT
List values
20
days. . . N
F12=Cancel
More...
F17=Save Filters
As shown here, for the Reference field (see topmost panel), you type EQ (Equals) in the Test
field and supply the task reference in the Value field. (You can press F4 to see a list of
reference codes.) On the bottom panel, you specify that you only want to see the production
objects (Level 20) that have been modified for application REGT.
When you press Enter twice (the second time to confirm your settings), your results will look
something like this:
1/29/10
12:25:59
Apply filters . . Y
Filter name: REGT0136
1=Browse current source 2=Browse archived source 3=Copy archived source
5=View form 6=Data explosion
7=Checkout
8=Archive information ...
Exists
Chk
Object
Library
Type
Run Date Appl Rl Vr Lv
Cd Obj Src Arc
Out
CLP001
REGT100PRD CLP
6/05/09 REGT
20
R
Y
Y
N
N
CMD01
REGT100PRD CLP
6/05/09 REGT
20
R
Y
Y
N
N
CMD01
REGT100PRD CMD
6/05/09 REGT
20
R
Y
Y
N
N
DTAARA01
REGT100PRD DTAARA 6/05/09 REGT
20
R
Y
N
N
N
DTAQ01
REGT100PRD DTAQ
6/05/09 REGT
20
R
Y
N
N
N
DXLF1
REGT100PRD LF
6/05/09 REGT
20
R
Y
Y
N
N
DXPF1
REGT100PRD PF
6/05/09 REGT
20
R
Y
Y
N
N
DXPF2
REGT100PRD PF
6/05/09 REGT
20
R
Y
Y
N
N
FILE01
REGT100PRD PF
6/05/09 REGT
20
R
Y
Y
N
N
FILE02
REGT100PRD PF
6/05/09 REGT
20
R
Y
Y
N
N
FILE03
REGT100PRD PF
6/05/09 REGT
20
R
Y
Y
N
N
FILE04
REGT100PRD PF
6/05/09 REGT
20
R
Y
Y
N
N
More...
F3=Exit F5=Refresh F8=IFS history F11=Alt. view F12=Cancel F24=More keys
NOTE: This is a subsetted list.
Page 4-21
Apply filters . . Y
Filter name: REGT0136
1=Browse current source 2=Browse archived source 3=Copy archived source
5=View form 6=Data explosion
7=Checkout
8=Archive information ...
Version
Object
Library
Type
Run Date Form
Status
Reference Maj Min
CLP001
REGT54PRD CLP
6/05/06 6402618 Ran-OK
REGT0136
CMD01
REGT54PRD CLP
6/05/06 6402618 Ran-OK
REGT0136
CMD01
REGT54PRD CMD
6/05/06 6402618 Ran-OK
REGT0136
DTAARA01
REGT54PRD DTAARA 6/05/06 6402618 Ran-OK
REGT0136
DTAQ01
REGT54PRD DTAQ
6/05/06 6402618 Ran-OK
REGT0136
DXLF1
REGT54PRD LF
6/05/06 6402618 Ran-OK
REGT0136
DXPF1
REGT54PRD PF
6/05/06 6402618 Ran-OK
REGT0136
DXPF2
REGT54PRD PF
6/05/06 6402618 Ran-OK
REGT0136
FILE01
REGT54PRD PF
6/05/06 6402618 Ran-OK
REGT0136
FILE02
REGT54PRD PF
6/05/06 6402618 Ran-OK
REGT0136
FILE03
REGT54PRD PF
6/05/06 6402618 Ran-OK
REGT0136
FILE04
REGT54PRD PF
6/05/06 6402618 Ran-OK
REGT0136
More...
F3=Exit F5=Refresh F8=IFS history F11=Alt. view F12=Cancel F24=More keys
NOTE: This is a subsetted list.
1=A
F3=
Page 4-22
Filtering
Filter name: RPGSRV
RPG Service Programs
Select one or more filters:
Field
Object . . . . . . .
Library. . . . . . .
Type code. . . . . .
Object type. . . . .
Programmer . . . . .
Reference. . . . . .
Line status. . . . .
Action code (A/R/D).
Run date . . . . . .
Form . . . . . . . .
Test
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
EQ
Value
List values
RPGSRV
and
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Named filter RPGSRV does not exist. Press ENTER to create.
Apply filters . . Y
Filter name: RPGSRV
1=Browse current source 2=Browse archived source 3=Copy archived source
5=View form 6=Data explosion
7=Checkout
8=Archive information ...
Version
Object
Library
Type
Run Date Form
Status
Reference Maj Min
RPG009
SKPROD
RPGSRV 2/12/08 6308180 Ran-OK
SAKP0008
003.000
RPG009
SKTEST
RPGSRV 2/12/08 6307922 Ran-OK
SAKP0004
000.001
T3ADDCHGSV A2PROD
RPGSRV 2/20/09 6312174 Ran-OK
JM520059
000.000
T3ADDCHGSV A2TEST
RPGSRV 2/20/09 6312134 Ran-OK
JM520059
006.000
T3MSG
A2PROD
RPGSRV 2/20/09 6312174 Ran-OK
JM520059
006.000
T3MSG
A2TEST
RPGSRV 2/20/09 6312134 Ran-OK
JM520059
006.000
To reposition screen, enter Object:
F11=Alt. view
Bottom
F12=Cancel F24=More keys
Object . . . . . APPF001
Library . . . PRODTEST
Type . . . . . . *FILE
1=Restore
Form
2=Browse
Archive
Line Date
103214
100621
100301
100027
005
006
001
003
F3=Exit
Archive
File
01/21/98 APARCHIVE
06/30/98 APARCHIVE
04/11/98
03/21/98
Archive
Library
Archive
Member
Save
Date
ARCLIB
ARCLIB
M000043912
M000003249
M000000911
M000000312
00/00/00
09/18/98
09/18/98
Save
Volume
SLS210
SLS210
F12=Cancel
Page 4-23
Page 4-24
22 As a rule of thumb, the record length of your archive files should be the widest of the record lengths used by your source files.
Page 4-25
First, TURNOVER for iSeries v100 attempts to check out source for a production object by
referring to the object description to locate the source that created it, and then checking out and
copying that source to your development library. If it cannot find the source based on the object
description, TURNOVER for iSeries v100 looks at the application definition to find the source
and check it out from there.
If you specify a source member name to be checked out and no object exists, TURNOVER for
iSeries v100 will check out the source member from a source file, without referring to the
production object.
When you check out source, you do not need to know the source file name and library. You can
reference the application name and TURNOVER for iSeries v100 uses the application definition
to determine these variables. Also, depending on how TURNOVER for iSeries v100 is set up
on your system, you do not need to tell TURNOVER for iSeries v100 the name of your
development library. TURNOVER for iSeries v100 also determines this from the application
definition or your programmer profile.
Page 5-1
When you check out an object, we recommend that you specify a Project task reference. This
makes it easier to build a form later, by typing the Reference field and having TURNOVER for
iSeries v100 complete the form with the object names that were checked out or reserved here.
Your company may have made the Project task reference field a required field. If you use the
Programmers Worklist, TURNOVER for iSeries v100 will use the Project task reference
associated with the worklist, by default.
You can manually perform source check-in if you check out source and then decide not to change
it. In this case, checking in the source only resets the lock in the checkout file. The only time
production source is changed is during the TURNOVER for iSeries v100 run, when it is copied
to production. TURNOVER for iSeries v100 automatically checks in the source at that time.
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F24=More keys
23 For normal operations, you will perform most of these functions from your Programmers Worklist (PWM) rather than from this menu. For more
about PWM, see Chapter 9: Working with Projects and Tasks in this guide, and see the TURNOVER for iSeries v100 Developers Guide.
Page 5-2
Checkout/Check-in Menu
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F20=PDM Menu
F21=System command
24 See the TURNOVER for iSeries v100 Supplements entitled TURNOVER for iSeries v100 Commands (#28), as well as the TURNOVER for
Page 5-3
__________
Type
RPGLE
CLLE
LF
__________
Programmer
AUSER
JSMITH
JSMITH
__________
Reference
YCWP0004
YCWP0001
YCWP0001
________
Status
NEW
NEW
NEW
Bottom
F3=Exit F4=Select
F16=User options
F5=Refresh F11=View2
F21=Command
F12=Cancel
Page 5-4
Object . . . . . . . .
Library . . . . . .
Type . . . . . . . . .
Production source file
Library . . . . . .
Member . . . . . . . .
Type code . . . . . .
Test source file . . .
Library . . . . . .
Member . . . . . . . .
Programmer . . . . . .
Reference . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ACTPYBMSTF
MSPRDDTA
*FILE
QDDSSRC
MSPRDSRC
ACTPYBMSTF
PF
QDDSSRC
MARYSDEV
ACTPYBMSTF
ELMESMIKE
PROJ0002
Y,N
Y,N
Page 5-5
Page 5-6
Select the object for which you want to check in source. You can select options to delete the test
source member, or to delete both the source member and test object from your development library.
You must have Check-in authority for the application and level you select.
26 Normally, you will check in using option 22 on the Programmers Worklist (PWM). We recommend that method. (While this option predates PWM,
we still support it.) For more about PWM, see Chapter 9: Working with Projects and Tasks in this guide, and see the TURNOVER for iSeries v100
Developers Guide.
Page 5-7
Position to member:
Filter by Programmer:
Reference:
Appl/Rel/Ver/Lev:
test member/object
Test Lib
Reference
ELMEMIKE
T99M0203
ELMSMIKE
JFC
ELMSMIKE
ETEVMIK +
Select the member for which you want to check in source. You can select options to delete the source
member from your development library, or to delete both the source member and test object from
your development library.
You must have Check-in authority for the application and level you select.
27 Normally, you will check in using option 22 on the Programmers Worklist (PWM). We recommend that method. (While this option predates PWM,
we still support it.) For more about PWM, see Chapter 9: Working with Projects and Tasks in this guide, and see the TURNOVER for iSeries v100
Developers Guide.
Page 5-8
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Name
AAUDIT, ABPGM, ADMDL, ADPGM...
CHAR
Number
Char
.
.
.
.
.
Additional Parameters
Library . . . . . . . .
Source Member . . . . .
Source File . . . . . .
Source Library . . . . .
Source copy option . . .
Duplicate non-src object
Release . . . . . . . .
Version . . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
*APPL
*OBJ
*APPL
*APPL
*NONE
*YES
F12=Cancel
*APPL, name
Name, *OBJ, *OBJD
Name, *APPL
Name, *APPL
*NONE, *ADD, *REPLACE
*YES, *NO
Number
Number
More...
F13=How to use this display
To check out source by object or source member, you must satisfy all TURNOVER for iSeries v100
rules pertaining to checkout. You must be a user of the application you specify and have Checkout
authority to that application. You must specify valid libraries for the object or member you are
checking out. You cannot check out an object or member that is already checked out (unless group
checkout is allowed).
Page 5-9
Position to object:
Filter by Programmer:
Reference:
Appl/Rel/Ver/Lev:
F3=Exit
F4=Reference selection
F12=Cancel
Reference
WEB 0001
WEB 0001
WEB 0001
PROJ0003
+
F22=Full path/object
For more information, see the IFS guide, Managing Integrated File System (IFS) Objects Using
TURNOVER for iSeries v100.
Page 5-10
Position to object:
Filter by Programmer:
Reference:
Appl/Rel/Ver/Lev:
This panel shows all the IFS objects that are currently checked out. For more information, see the IFS
guide, Managing Integrated File System (IFS) Objects Using TURNOVER for iSeries v100.
Page 5-11
Type code . . . . . . . . . . .
Application . . . . . . . . . .
Reference . . . . . . . . . . .
F3=Exit
F4=Prompt
F5=Refresh
F13=How to use this display
F10=Additional parameters
F24=More keys
Bottom
F12=Cancel
For detailed information, see the IFS guide, Managing Integrated File System (IFS) Objects Using
TURNOVER for iSeries.
Page 5-12
.
.
.
.
.
.
.
.
.
.
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
TLINEF
SOFTTURND
PF
DEFAULT
*
F12=Cancel
Name
Name
AAUDIT, ABPGM, ADMDL, ADPGM...
APDEMO, DEFAULT, J52XREF, L..
*, *PRINT
Bottom
F13=How to use this display
Type the Object Name, Library Name, Object Type, and X-Ref Table name in which the crossreference information is to be found and press Enter. If you position to the X-Ref Table parameter
and press F4, you will see a list of all of the cross-reference (X-Ref) tables defined on your system.
(Note that those you see here are only examples.)
Note that you can also see cross-reference usage information by selecting option 15 on the
Programmers Worklist and Work with Object History panels.
If you have Pathfinder, Abstract/Probe+, or some other cross-reference package, you can create a
user-defined option while viewing the Work with Object History or Work with TURNOVER for
iSeries v100 Forms panels to get into your cross-reference files quickly.
Page 5-13
Data set
11:12:52
. . . . DEFAULT
Apply filters . . . Y
5=View checkout
Object
ADDCHKITMR
ADDCMDR
ADDCMDXR
CHGFORMPRR
CVTLINCMTR
DISTDATAR
TCRTPGM
TCRTSRVPGM
TLINEH
TLINEL
TLINEN
(F17=Filters)
8=Browse member
Library
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTRUN
SOFTTURN
SOFTTURN
SOFTTURND
SOFTTURND
SOFTTRUND
Attr
RPG
RPG
RPG
RPG
RPG
RPG
CLP
CLP
LF
LF
LF
F12=Cancel
Chk
How Used Out U/B
Input
N
B
Input
N
B
Input
N
B
Update
N
B
Input
N
B
Input
N
B
Not given N
B
Not given N
B
PF->LF
N
B
PF->LF
N
B
PF->LF
N
B
More
F13=Repeat
F22=Print
You will see all of the objects that refer to the object you specified (TLINEF in our example). You
can also see how the reference object is used. Values for the How Used column are:
Input
Output
Out/Upd
Update
Pgm-Call
PF->LF
Pgm-module
Pgm-SRVPGM
DTAARA
Cmd-VLDCKR
Cmd-CPP
Another example: If you started with a physical file, you could then see all of the related logical files
built over that physical, and then see all of the programs that used one of the logicals, and then a
program that called one of those programs, and so on.
Page 5-14
2=Change
4=Delete
Object
_ TURSLINA
_ TURSLIND
_ TURSFORS
F3=Exit
Library
SOFTTURN
SOFTTURN
SOFTTURN
F6=Add X-Ref
Type
*FILE
*FILE
*FILE
F12=Cancel
Attr
DSPF
DSPF
DSPF
Reference --------------------------Object
Library
Type
Attr
TURHLINA
SOFTTURNE *PNLGRP PNLGRP
TURHLIND
SOFTTURNE *PNLGRP PNLGRP
TURHFORS
SOFTTURNE *PNLGRP PNLGRP
F21=System command
Of course, the X-Ref table you specify will be one you defined when you set up your application
definitions. You could add additional relationships by pressing F6.
While these relationships can be added and updated from this panel, you could also write a program
that uses the Add a user-defined reference API program to add these entries more efficiently.
Page 5-15
Position to Worklist . . . .
Filter by Programmer . . . .
Filter by Appl rel ver . . .
F3=Exit
F4=List
F6=Add
F7=Previous Worklists
task
Status
Done
Started
Started
F12=Cancel
F21=Command line
For detailed information, see Programmer Worklist Manager (PWM), beginning on page 9-116 in
this guide, and see the TURNOVER for iSeries Developers Guide.
Page 5-16
1=Checkout 2=Change definition 4=Delete defn 5=View file 9=Update test file
File
ARNOLDPF
GGSTRDTA
GGSTRDTA
PRDATA03
PRDATA03
SIXFIELD
SIXFIELD
F3=Exit
Library
HENRY
AAXPRD
AAXQA
PRTEST
RICHARDS
AAXPRD
AAXQA
Member
ARNOLDPF
GGSTRDTA
GGSTRDTA
PRDATA
PRDATA
SIXFIELD
SIXFIELD
F6=Add definition
F11=Alternate view
Rpl
Y
N
N
Y
N
N
N
Test lib
C.O. File
AAXDEVX
AAXDEVX
TD00005F
TD00004F
AAXDEVX
AAXDEVX
TD00001F
TD00003F
TD00006F
F12=Cancel
F14=WRKSBMJOB
While the *DATA object type serves its purpose, it is somewhat cumbersome to use and has some
limitations. For example, *DATA object types:
Do not let you define how others should edit the source for the object or how TURNOVER for
iSeries v100 should move, delete, and archive the object.
Do not readily support file and record format names that are greater than eight characters.
Only manage records in a single file. They do not handle records in a group of related files, such
as menu header and menu option files.
With TURNOVER Release 5.3, support for managing data at the record level was significantly
expanded over that provided by the *DATA object type. As of Release 5.3, you can use change
management schemes to selectively override, for a user-defined object type, almost any change
management method that you would execute for an object. You can use the sample change
management schemes that ship with TURNOVER for iSeries v100 as examples, or create your own
schemes. For detailed information, see the TURNOVER for iSeries v100 Supplement entitled
Managing User-Defined Object Types (#59).
Page 5-17
iSeries
v100
product
CD
Page 5-18
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*APPL
*USRPRF
*APPL
Name
Name, *APPL, *LIBL
Name, *USRPRF, *SELECT
Name, *PGMR, *APPL
Name
Number
Number
Number
Char, *SELECT
Additional Parameters
Bypass Prompt
Y,N
. . . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Bottom
F13=How to use this display
For more about S/36 menus, see the TURNOVER for iSeries v100 Supplement entitled Menus,
DFUs, and Queries (#58).
Page 5-19
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*APPL
*USRPRF
*APPL
Name
Name, *APPL, *LIBL
Name, *USRPRF, *SELECT
Name, *PGMR, *APPL
Name
Number
Number
Number
Char, *SELECT
Additional Parameters
Y,N
Include Source . . . . . . . . .
F3=Exit
F4=Prompt
F24=More keys
F12=Cancel
F5=Refresh
Bottom
F13=How to use this display
Specify Include Source = Y if you want to check out the source, N if you just want the DFU object.
For more about S/36 menus, see the TURNOVER for iSeries v100 Supplement entitled Menus,
DFUs, and Queries (#58).
Page 5-20
APPL
Level 2
(CSCO)
PRODDTA
PRODOBJ
PRODSRC
ACCEPTANCE
TEST
*PGMR
CSCO
CSCO
Checkout
When you check out source for an object, you specify the object name, object type, and application
code. TURNOVER for iSeries v100 looks for the source by referring to the highest-level
application description; in the example above, APPL level 2. If the source is checked out already,
TURNOVER for iSeries v100 will tell you that the source is checked out from the highest level
(production) and, if it has been promoted to another level (Acceptance Test, in the example above),
you will have the opportunity to check it out from there.
If you have more than two levels defined, TURNOVER for iSeries v100 will search them all.
If you want to specify from which level you are checking out the source, you can still specify the
level.
Page 5-21
APPL
Level 1
(CSCO)
MOD DTA
MOD OBJ
MOD SRC
APPL
Level 3
(CSCO)
Perm Locked
BASE DTA
BASE OBJ
BASE SRC
ACCEPTANCE
TEST
*PGMR
CSCO
CSCO
Checkout
Note also that the Base level does not have to contain software from a vendor, but might be the
previous release of an application you have developed. The modification level might represent work
in progress on a later release.
Page 5-22
Page 5-23
The objects listed below have been turned over by other programmers while
checked out to JIMCLARK.
Changes made by those programmers must be
included in changes made by JIMCLARK.
Position to object . . . .
Filter by programmer . . .
Filter by reference . . .
Type options, press Enter.
1=Approve 4=Cancel approval 5=View form 7=Project details
Object
SLSF001
F3=Exit
Library
SLSLIB
F5=Refresh
Type
RPG
Programmer
ABFORTIS
F12=Cancel
Form
10431
Run
Date
04/30/93
Reference
SLPR0321
Approved
PSMITH
F14=Display all
By selecting option 1=Approve, you confirm that the changes made by the other programmer have
been made to your version of the object.
A variant of this command also runs when you exit a TURNOVER for iSeries v100 form, and again
during the Pre-run error-check. When the multiple checkout feature is enabled, TURNOVER for
iSeries v100 will not run a form containing objects that you have not confirmed.
If you try to promote an object to an intermediate level while another programmers work is in
process (at the same target level), TURNOVER for iSeries v100 prevents you from doing so.
However, you can check out an object from an intermediate level. Keep in mind that the multiple
checkout rules apply to any level.
Page 5-24
OVERVIEW
Whats a TURNOVER for iSeries v100 form?
In TURNOVER for iSeries v100, we use form as short hand for promotion request. A
TURNOVER for iSeries v100 form is the vehicle for promoting source and object from a test
environment to a higher-level test environment, or to production.
When you visualize the application schematic, think of a form as all the information TURNOVER
for iSeries v100 needs to promote objects and source from left to right. Checkout occurs right to left
and is done when you start a programming project-task. A form is created when you are done
programming and are ready to have your work certified and put back into production.
A TURNOVER for iSeries v100 form consists of:
1. Job control information (the form header)
2. Object information (the lines on the form)
A form can also contain:
3. Commands (Pre-run or Post-run commands). Commands like override database file necessary
for creating some objects can be included as Pre-run commands. Commands can be associated
with particular objects on the form. When you do so, TURNOVER for iSeries v100 will
remember this association for you next time you or someone else changes that object.
4. Create command overrides. You can override the default create command TURNOVER for
iSeries v100 uses to create this object. This command override is associated with a particular
object on the form. When you do so, TURNOVER for iSeries v100 will remember this
command override for you next time you or someone else changes that object.
Page 6-1
Page 6-2
A few important things you should know about TURNOVER for iSeries
v100 forms
A few important things you should know about TURNOVER for iSeries v100 forms are the
following:
Each form is numbered with a unique seven-digit number, similar in concept to a job number,
with two digits being a form prefix number and five digits a sequence number that is assigned by
TURNOVER for iSeries v100.
Note: Previously, the first three digits of the form number referred to the system on which the
form was created. As of Release 5.2, TURNOVER for iSeries stores system information in the
form header. You no longer have to set a form rollover threshold or change your form number
prefix when your form sequence number approaches 9999; TURNOVER for iSeries v100 now
handles this situation automatically.
Any time a form is created, if the number of lines on the form exceeds a number set by the
XREFOVRFLW data area (shipped set to 900), then the remaining lines are automatically added
to one or more new forms, such that a form group of dependent forms is created.
Each form contains a reference to your project task (subject to how your environment is set up).
This field is called Reference or Project task reference, where space allows.
Each form is run once. If a form needs to be rerun, it is copied to create a new form, and the new
form is run. In this way a complete audit trail is maintained by TURNOVER for iSeries v100.
The objects on a form are sequenced such that objects are created in the correct logical order (PF
first, then LF, then DSPF, and so on).
Logical files are added to the form automatically for physical files in a target library. You only
need to identify explicitly those logical files that you have changed.
Your TURNOVER for iSeries v100 Administrator can purge (remove) forms from
TURNOVER for iSeries v100. When you purge forms, you should be careful not to remove
valuable change history.
Form status determines whether a form can be run. Only forms that are READY or RECVD
status can be run. (Note: RECVD is only valid on remote production systems where
TURNOVER for iSeries v100 changes have been received.)
If Form status is APL-PN (Approval Pending), the form must be approved before being run.
When distributed to another system, a form will retain its original form number.
Forms can be grouped together and run as a group or run independently. They can also be linked
such that one form must complete successfully before another form can start.
Page 6-3
Page 6-4
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F24=More keys
Page 6-5
Press F6 and enter the application-level with which you are working; i.e. AP level 1. You will be
prompted for the last one you used; you can change this or press F4=List to select another.
On the Add a Form panel, you enter your project task code or press F19 to select from a list.
Confirm the information on the form header.
Confirm the list of objects you checked out or reserved under that Project task code.
View and confirm the TURNOVER for iSeries v100 form on the Form Maintenance panel.
See TURNOVER for iSeries v100 Form Maintenance in this chapter for detail about other
things to do.
Once youve returned to Work with Forms, you can request to have your form approved or run, or
submit it yourself (depending on form status and your TURNOVER for iSeries v100 authority).
The remainder of this chapter steps you through the process illustrated on the preceding page in
greater detail and describes the function of each panel.
28 For an alternative method, see Chapter 9: Working with Projects and Tasks in this guide as well as the topic Programmers Worklist Manager
(PWM) in the TURNOVER for iSeries v100 Developers Guide.
Page 6-6
2=Update form
6=Print form
Form
5300189
5300188
5300187
5300186
5300185
5300184
5300183
5300182
5300181
5300180
5300178
Description
Add eCM presentation
Add eCM presentation
Add press releases t
Add press releases t
Add press releases t
Add sales targets to
Add eCM presentation
Add eCM presentation
Promote all web file
Promote all web file
Add development cont
4=Cancel form
8=Work w/ job
Run
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
Programmer
MARTIN
MARTIN
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
MARTIN
MARTIN
MARTIN
Status
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RECOVER
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
More...
F6=Add form F7=DSPMSG F11=Alternate view
F16=User options F24=More keys
F23=More options:
1=Perform error check on form
17=Run turnover without error checking
11=Distribution status
12=Create recovery form
F24=More.keys:
F17=Filters F21=System Command
F23=More options
F24=More keys
The Work with Forms panel lists all the TURNOVER for iSeries v100 forms that have been
entered. By default, TURNOVER for iSeries v100 lists the forms in descending order by form
number. (This means that the most recent form appears at the top of the list.)
You will only be able to see forms for applications that are unlocked and to which you have Forms
authority.
If you are creating forms and receiving distributions on the same computer, this panel will position to
the range of forms created on your computer. Roll or page up to see forms distributed to you from
other systems.
Page 6-7
Apply filters . . Y
Here, you can type the name of a specific programmer (or if a programmer name is already
filled in, you can type over that name) and press Enter to have TURNOVER for iSeries
v100 display that programmers forms at the top of the list. In the then form field, you can
type a specific form number for that programmer and press Enter to have that forms
information appear topmost in the list. Note: If you type a form number to which you are not
authorized, TURNOVER for iSeries v100 will position the panel to the next form matching
your criteria.
For details about sorting and filtering TURNOVER for iSeries v100 forms, see Sorting and
filtering forms, beginning on page 6-17.
29 In this field, TURNOVER for iSeries v100 displays the name of the programmer whose forms are now topmost in the list. Depending on your
sorting and filtering criteria, this name might change as you scroll down through the forms list.
Page 6-8
Page 6-9
DISTRIB if all distributions for a form distributed but not all have been confirmed yet.
5=Display form
Type a 5 next to a form to view the details of the form.
6=Print form
Type a 6 next to a form to print the form. You will see a command prompt for printing the
form.
7=Run turnover
Type a 7 next to a form to submit it to be run. TURNOVER for iSeries v100 will perform
an edit check on the form and then display the Submit TURNOVER for iSeries v100 Job
Prompt panel. Forms may be submitted on hold, depending on the application default.
8=Work w/ job
Type an 8 next to a form to view the job if it has been submitted or run.
9=Release job
Type a 9 next to a form to release the form from the job queue. When a form is submitted, it
may be submitted on hold. This is an application default.
Page 6-10
Page 6-11
2=Update form
6=Print form
Form
5300189
5300188
5300187
5300186
5300185
5300184
5300183
5300182
5300181
5300180
5300179
5300178
4=Cancel form
8=Work w/ job
Description
Add eCM presentation to website
Add eCM presentation to website
Add press releases to Marketing page
Add press releases to Marketing page
Add press releases to Marketing page
Add sales targets to site
Add eCM presentation to Sales site
Add eCM presentation to Sales site
Promote all web files
Promote all web files
Add development content
Add development content
Entered
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
7/09/09
Reference
WEB 0007
WEB 0007
WEB 0005
WEB 0005
WEB 0005
WEB 0004
WEB 0003
WEB 0003
WEB 0002
WEB 0002
WEB 0001
WEB 0001
Status
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RECOVER
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
More...
F6=Add form F7=DSPMSG F11=Alternate view
F16=User options F24=More keys
F14=WRKSBMJOB
Press F14 to display the Work with Submitted Jobs panel. This lets you view and work with
the status of jobs that youve submitted.
F16=User options
Press F16 to select user defined options.
PP - Use option PP to flag a form to be purged. Status will be PURGEPND.
SC - Use option SC to call your source compare program. (See Setting Source Compare
Utility Defaults on page 8-28.)
F17=Filters
Press F17 to see the Sorting and Filtering panel on which you can define sorting and filtering
criteria for the forms you want listed on the Work with Forms panel. Once you define your
criteria, you can press F17 (again) on the Sorting and Filtering panel to save your settings.
For more information, see Sorting and filtering forms on page 6-17.
F21=System Command
Press F21 to work on a command line.
F23=More options
Press F23 to view additional options.
F24=More keys
Press F24 to view additional keys.
Page 6-12
2=Update form
6=Print form
Form
5300189
5300188
5300187
5300186
5300185
5300184
5300183
5300182
5300181
5300180
5300179
5300178
Desc
Add
Add
Add
Add
Add
Add
Add
Add
Promo
Promo
Add
Add
Bottom
F2=Maintain Filters
F3=Exit
F12=Cancel
More...
F6=Add form F7=DSPMSG F11=Alternate view
F16=User options F24=More keys
The Select Named Filter panel lists the existing named filters. You can select a filter name with
option 1 and press Enter to apply that filters criteria to the list of forms on the Work with Forms
panel. On that panel, TURNOVER for iSeries v100 sets the Apply filters flag to Y (if it is not
already set to that) in reverse image to indicate that you have applied filtering criteria, it replaces the
value in the Filter name field with the name of the filter you are have selected, and it removes the
popup panel. If you now pressed F17 (if you do not see F17 at the bottom of the panel, press F24 to
see more keys), a Sorting and Filtering popup panel will appear. This panel shows the filtering
criteria associated with the named filter you have selected (see Sorting and filtering forms on page 617).
Page 6-13
1=Add
Name
2=Change
3=Copy
4=Delete
5=View
Description
*DEFAULT
KING_FORMS King's Forms that need approval
RANOK_WRN Forms that RAN-OK or RAN-WRN
RECOVER
Recovered forms
Bottom
F3=Exit
F5=Refresh
F11=Show Shared
F12=Cancel
F21=System Command
The Named Filter Maintenance panel lists the existing named filters and provides options for
working with them. If your filter names list becomes lengthy, you can press the Home key to position
your cursor on the Position to field. In that field, you can type a filter name (and press Enter) to
quickly position your cursor on that filter name in the list.
Page 6-14
1=Add
2=Change
Name
READYFRMS
*DEFAULT
KING_FORMS
RANOK_WRN
RECOVER
3=Copy
4=Delete
5=View
Description
Bottom
F3=Exit
F5=Refresh
F11=Show Shared
F12=Cancel
F21=System Command
Press Enter.
TURNOVER for iSeries v100 displays the new filter name at the top of the Sorting and Filtering
panel. You can now type a filter description (of up to 40 characters) in the field to the right of the
filter name and supply the filtering criteria beneath that:
1/29/10
12:
1=A
Your Company,
Type a description
here.
Filter name
Inc.
0 days:
0 days:
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Named filter READYFRMS does not exist. Press ENTER to create.
Page 6-15
1=A
Filtering
with a Ready status
Select one or more filters:
Test Value
List values
EQ
READY
and
and
0 days:
0 days:
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Named filter READYFRMS does not exist. Press ENTER to create.
Press F17 to save your criteria settings (and then press Enter to create the filter) or press Enter twice
to save your criteria and create the filter. (For detailed information about defining your sorting and
filtering criteria, see Sorting and filtering forms on page 6-17.)
Maintaining named filters
You can change, copy, delete, and view named filters listed on the Named Filter Maintenance panel.
You do so by typing an option number (2=Change, 3=Copy, 4=Delete, 5=View) next to a filter name
and pressing Enter. When you select a filter name with options 2 or 5, TURNOVER for iSeries
v100 displays the filter name, description, and criteria in the Sorting and Filtering panel. You can
change the filter description and criteria (option 2) or just view the filter information (option 5).
While viewing the criteria for a named filter, you can press F19 (Previous) and F20 (Next) to scan
the criteria settings for the other named filters, one by one.
When you select a filter name with option 4 (Delete), TURNOVER for iSeries v100 presents a
Delete Filter popup panel. Press Enter to confirm that you want to delete the filter. TURNOVER
for iSeries v100 deletes it and removes its name from the named filters list.
You can duplicate an existing filter to create a new filter. You can change the new filters name,
description, and criteria as you want. Also, if you want to make a filter available to other users, you
can copy it to a shared filter.
Page 6-16
Copy Filter
1=A
To Filter: READYFRMS
Type: *USER
F3=Exit
F12=Cancel
Bottom
F3=Exit
F5=Refresh
F11=Show Shared
F12=Cancel
F21=System Command
On this Copy Filter popup panel (in the To Filter fields), you type the name and description of the
new filter. You also specify the type of filter (*USER or *SHARED) you are creating. Descriptions
of the filter types follow:
User filters are specific to your user profile. Only you have access to these filters.
Shared filters are a pool of named filters that are shared among users. Only users with
System Aut authority can delete shared filters.
The ways you can interchange user and shared filter types as follows:
*USER to *USER Copy a user filter to a user filter with a new name to modify the filter yet
retain the original criteria settings.
*USER to *SHARED Copy a user filter to a shared filter to make it available to others to
copy to their own user filters. Any changes you and others subsequently make to the user
filter will not affect the shared filter. If a shared filter already has the user filter name, you
must supply a new shared filter name.
*SHARED to *USER Copy shared filters to your user filters. Any changes you
subsequently make to the user filters will not affect the shared filters. If you already have a
user filter with a shared filter name, you must supply a new user filter name.
*SHARED to *SHARED You can not modified shared files. Therefore, this copy function
is not permitted.
Once you supply a new filter name and description, and specify the filter type, press Enter.
TURNOVER for iSeries v100 creates the new filter and adds it to the named filters list. On the
Named Filter Maintenance panel, you can press F11 to toggle between lists of user and shared
filters.
TURNOVER for iSeries v100 2005-2010 UNICOM Systems, Inc.
Jul-10
Page 6-17
2=U
6=P
0 days: N
0 days: N
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
You use the Sorting and Filtering panel to define sorting and filtering criteria for the forms listed on
the Work with Forms panel. On the Sorting and Filtering panel, the fields that you use for sorting
are listed on the left; the fields that you use for defining filtering criteria are on the right. See pages 618 through 6-23 for details about these fields and their possible values; see pages 6-24 through 6-27
for several examples.
Sorting fields
You can sort by the fields on the Work with Forms panel. You can choose only ONE sorting field,
and you choose the field with A (sort in Ascending order) or D (sort in Descending order) to specify
in what order you want TURNOVER for iSeries v100 to list the information. Alternatively, you can
leave all the sorting fields blank to have TURNOVER for iSeries v100 list the forms on the Work
with Forms panel in descending order by form number. When you choose to sort by one of these
fields rather than by the default of descending form numbers, the form numbers sort becomes the
secondary sort. For example, if you have TURNOVER for iSeries v100 sort by application in
ascending order, it then lists the forms in descending order within each application group.
Note: When you choose to sort by application, TURNOVER for iSeries v100 treats the four fields
that comprise the application (Application, Release, Version, and Level) as one field.
Page 6-18
Description
Equals
Not equals
Greater than
Less than
Greater than or Equal to
Less than or Equal to
Contains
Between
In the defined list
Not in the defined list
Do not test
Notes:
1. Use CT to see information for specific characters. For CT, you must specify a value that
begins with a percent sign (%), ends with a percent sign, or both. Also, with CT, you can use
an underscore in the value to indicate that a character (any character) must occupy that
position. For example, if you wanted to see information for programmer TJEFFERSON, you
could specify %JEFF% in the Programmer field. However, you would also see information
for programmer TJEFFERSON if you specified %ERS_N (this has one underscore) or
__EFF% (this has two underscores).
2. Use LI to see information for multiple values. For example, you might want to see a list of
forms run by a programmer who has multiple User IDs. Specify LI as the test and press F11
to define the list of User IDs. Your results will only include information for User IDs in your
list.
3. Use NL to exclude information for multiple values. For example, you might want to see a list
of forms run by all programmers except AUSER and SMITH. Specify NL as the test and
press F11 to define the list of User IDs (AUSER and SMITH) you want excluded. Your
results will include information for all User IDs except AUSER and SMITH.
31 To see which of these values are valid, position your cursor on the Test field and press F1 for the online Help.
Page 6-19
CT
LI
Page 6-20
2=U
6=P
F3=
F12
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Press ENTER to confirm.
In the Include only approval pending for your user ID field, indicate whether or not you want
TURNOVER for iSeries v100 to only show forms with a status of APL-PN (Approval
Pending) for which you are on the approval list. Type Y to have TURNOVER for iSeries
v100 only show forms with a status of APL-PN for which you are on the approval list. Type
N to have TURNOVER for iSeries v100 show all forms with a status of APL-PN, including
those for which you are not on the approval list.
Include only forms entered in the past 0 days
Specify for how many days you want TURNOVER for iSeries v100 to display forms that
have been entered. TURNOVER for iSeries v100 will only display forms entered within the
number of days that you specify. For example, if you use the default value of 0 days,
TURNOVER for iSeries v100 will only show forms entered today (the current day). If you
specify a value of 1 day, TURNOVER for iSeries v100 will show forms entered yesterday
and today. If you specify a value of 2 days, TURNOVER for iSeries v100 will show forms
entered the day before yesterday, yesterday, and today. You can specify up to 999 days.
Note: You might have a particular number of days that you repeatedly reuse. If you specify
that number in this field, you can use the field (Y/N) to the right to toggle this criteria setting
on and off. This works the same way for the following field, Include only forms run in the
past 0 days.
Page 6-21
Page 6-22
Additional Options
2=U
6=P
F3=
F12
N
*DEFAULT
N
Y
F3=Exit
F4=Prompt
F5=Refresh
F12=Cancel
name, *LAST
Bottom
F17=Save Filters
\
Page 6-23
*LAST
Use the named filter you used the last time you exited the Work
with Forms panel.
Name
Page 6-24
2=U
6=P
0 days: N
0 days: N
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
As shown here, all you need to do is type D (Descending) in the Reference field. When you
press Enter twice (the second time to confirm your settings), your results will look something
like this: 32
1/29/10
Work with Forms
Your Company, Inc.
12:29:58
YOURSYS
Apply filters . . Y
To reposition, enter Reference. . .: WEB0007
then form. . . . . .:
Filter name: *DEFAULT
2=Update form
3=Copy to new form
4=Cancel form
5=Display form
6=Print form
7=Run turnover
8=Work w/ job
9=Release job
Sorted Descending by Reference
Form
Description
Entered Reference Status
5300189 Add eCM FAQ to support site
8/09/09 WEB0007
RAN-OK
5300188 Add instructions to "Download fixes" pa 8/09/09 WEB0006
RAN-OK
5300191 Add instructions to "Download fixes" pa 8/09/09 WEB0006
RAN-OK
5300190 Add auth code generation and logging
7/03/09 WEB0005
RAN-OK
5300187 Add auth code generation and logging
7/03/09 WEB0005
RAN-OK
5300186 Add auth code generation and logging
7/03/09 WEB0005
RAN-OK
5300185 Add auth code generation and logging
6/19/09 WEB0005
RECOVER
5300201 Post new version of docs
6/13/09 WEB0004
RAN-OK
5300184 Post new version of docs
6/12/09 WEB0004
RAN-OK
5300183 Integration with iSeries Projects
4/16/09 WEB0003
RAN-OK
5300182 Integration with iSeries Projects
4/16/09 WEB0003
RAN-OK
5300181 Integration with iSeries Projects
4/16/09 WEB0003
RAN-OK
More...
F3=Exit F4=Prompt F5=Refresh F6=Add form F7=DSPMSG F11=Alternate view
F12=Cancel
F14=WRKSBMJOB
F16=User options F24=More keys
Here, the reference codes (WEB0007 through WEB0003) are in descending order. The form
numbers are in descending order within each reference code group. Therefore, although
5300201 is the highest form number shown, because it belongs to WEB0004, it is listed
under that reference code. Notice that the Apply filters flag is set to Y, but is not in reverse
image. This indicates that you have not defined any filtering criteria. Finally, the line Sorted
32 To see the form references, as shown here, you must press F11 (Alternate view) from your initial view of the Work with TURNOVER for iSeries
Page 6-25
2=U
6=P
0 days: N
0 days: N
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Press ENTER to confirm.
As shown here, you type BT (Between) in the Test field and your dates in the Value field. If
you type your dates as 41606 and 80106, TURNOVER for iSeries v100 will insert the
slashes (/) when you press Enter.
When you press Enter again, your results will look something like this:
1/29/10
12:53:42
2=Update form
6=Print form
Form
6402836
6402835
6402834
6402833
6402832
6402831
6402830
6402829
6402828
6402827
6402826
6402825
4=Cancel form
8=Work w/ job
Description
Error when processing new claims
pre/post run command authority
pre/post run command authority
pre/post run command authority
pre/post run command authority
prepost
prepost
prepost
prepost
prepost
prepost
Recover Form 6402824
Entered
8/01/09
7/31/09
7/31/09
7/31/09
7/31/09
7/27/09
7/27/09
7/27/09
7/27/09
7/27/09
7/27/09
7/27/09
Reference
SAKP0003
PRPR0135
PRPR0135
PRPR0135
PRPR0135
REGT0542
REGT0542
REGT0542
REGT0542
REGT0542
REGT0542
JPWP0104
Status
READY
RAN-OK
RAN-OK
RAN-OK
RAN-OK
READY
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
More...
F6=Add form F7=DSPMSG F11=Alternate view
F16=User options F24=More keys
Here, all forms entered between April 16, 2009 and August 1, 2009 (inclusive) are shown.
The Apply filters flag is set to Y, and is in reverse image to indicate that you have defined
Page 6-26
Example 3: Sort by reference in ascending order and filter for level 20 forms with a status
of APL-PN
This example shows you how to combine sorting and filtering. For example, if you wanted to
sort forms by reference code in ascending order, as well as only include level 20 forms for
which you (the signed on user) are on the approval list, you would do so as follows:
1/29/10
13:
2=U
6=P
F3=
F12
More...
F3=Exit F4=Prompt F5=Refresh F11=List F12=Cancel F17=Save Filters
Press ENTER to confirm.
As shown here, you type A (Ascending) in the Reference field to define how you want
TURNOVER for iSeries v100 to sort the forms. For the Application/Level field, type EQ
(Equals) in the Test field and 20 in the Value field to have TURNOVER for iSeries v100
only include forms that are level 20. For the Status field, type EQ (Equals) in the Test field
and APL-PN in the Value field to have TURNOVER for iSeries v100 only include forms
for which you are on the approval list.
Page 6-27
Here, TURNOVER for iSeries v100 only displays forms that match your filtering criteria,
and it lists them in ascending within each reference code group. (Only the last two forms
belong to the same reference code, and form number 6312277 precedes form number
6312219.) The Apply filters flag is set to Y, and is in reverse image to indicate that you have
defined filtering criteria. The line Sorted Ascending by Reference indicates how
TURNOVER for iSeries v100 has sorted the forms.
33 To see the form references, as shown here, you must press F11 (Alternate view) from your initial view of the Work with TURNOVER for iSeries
Page 6-28
Application . .
Form
Release . . . .
1423
Version . . . .
1423
Level . . . . .
1423
1423
1423
1423
1423
F4=List F12=Cancel
1423
1423
1423
1423540 Test Threshold on fo
1423539 Test Threshold on fo
F3=Exit
F12=Cancel
. AP
.
.
. 1
F4=List
AP
AP
1
1
8/27/09
8/27/09
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
atus
ADY
N-OK
ADY
ADY
STRIB
RTIAL
R-OK
COVER
N-OK
ADY
RECOVER
RECOVER
More...
PHILLIPS
PHILLIPS
F11=Alternate view
F24=More keys
The application will default to the last application and level you had selected. If you press F4=List,
you will then see the entire list of applications from which you can choose.
1/29/10
Application Selection
A/P
A/P
FDA
FDA
MENU
PROB
PROB
SECR
SECR
SECU
SECU
SLS
F3=Exit
Position to . . . Application:
Application Description
Rel
System-Wide
Accounts Payable Level 1
Accounts Payable Level 2
File Design Aid Release 2
2
File Design Aid Release 3
3
CENTRAL for iMenu v100
Problem Tracking Release 1
1
Problem Tracking Release 1.2
1
Secret Application
1
Secret Application release 2
2
Security Management Release 1
1
Security Management Release 2
2
SoftLanding Prospect/Order System
Rel:
Ver
Ver:
Lev:
Lev
1
2
100
2
1
1
1
1
2
F12=Cancel
Youll see the Application Selection panel. Select the appropriate application.
Page 6-29
Add a TurnOver
Application: A/P Rel:
Ver:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Library list:*AP01____________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
________________________________ *JOBD, *CURRENT, *library list name, Lib List
More...
F3=Exit
F4=List Proj
F11=Unprotect fields
F12=Cancel
F19=List Refs
Enter your project task and complete or confirm the form header information.
Page down to see additional parameters that are less frequently used.
1/29/10
12:22:12
Add a TurnOver
Application: A/P Rel:
Ver:
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F4=List Proj
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Y
4
0
___________
APOQ
QGPL
F11=Unprotect fields
Y/N
0-4
0-99
Name, *JOBD, *PGMR, *USRPRF
Name, *LIBL
F12=Cancel
F19=List Refs
34 A developer will perform this function by selecting option 46 on the Programmers Worklist (PWM) rather than from this menu. For more about
PWM, see the TURNOVER for iSeries v100 Developers Guide and Chapter 9: Working with Projects and Tasks in this guide.
Page 6-30
Page 6-31
Page 6-32
200008
APPR0123
Filter by level . . . . .
Filter by programmer . . .
The objects listed below have been checked out using the above
reference number but have not yet been included on the above form.
1=Include on form
1
1
1
1
1
1
Obj/Mbr
APFILEF
APFILE1
APFILE2
APS0001
APCL0323
APRPG026
F3=Exit
Library
APDATALIB
APDATALIB
APDATALIB
APPGMLIB
APPGMLIB
APPGMLIB
F12=Cancel
Type
*FILE
*FILE
*FILE
*PGM
*PGM
*PGM
Attribute
PF
LF
LF
CLP
CLP
RPG
Programmer
ELMSMIKE
ELMSMIKE
ELMSMIKE
ELMSMIKE
ELMSMIKE
ELMSMIKE
Reference
APPR0123
APPR0123
APPR0123
APPR0123
APPR0123
APPR0123
F21=Select all
TURNOVER for iSeries v100 builds and displays the new TURNOVER for iSeries v100 form.
Page 6-33
F3=Exit
F4=Comments
F5=Resequence
F6=Add line
F7=Locks
Bottom
F24=More keys
More keys:
F8=IFS objects F9=Insert line F11=Header F12=Cancel F24=More keys
F13=Other pgmr chgs F14=Comp. messages F15=Review commands F24=More keys
F16=User options F17=X-Ref F18=Add cmd F19=Checkout F20=PDM F24=More keys
F21=Command line F23=More options F24=More keys
Normally, once you build the TURNOVER for iSeries v100 form, you can exit and your form is
ready to run. However, you may want to do one or more of the following:
Enter commands to be run at the beginning or end of the TURNOVER for iSeries v100 form
run.
Enter lock checks to ensure you will have exclusive access to objects being changed.
Select objects from the applications cross-reference file to include in the form.
Each of these choices is described in greater detail below. Press F24 to see more function keys.
What you can do:
2=Change
Type 2 to change the line.
4=Delete
Page 6-34
Form:
Line:
40567
2
F3=Exit
. . . . .
F12=Cancel
The fields on the of this panel (Form, Description, Line, Object, Code, and Library) display
the form number of the current form as well as information about the line you have chosen.
The Code field shows the action code (ADD, REPLACE, or DELETE) for the current line.
Page 6-35
Description
Programmer
The user profile name of the programmer whose time you are
recording.
Rate
Analysis time
Programming time
Testing time
Description
Page 6-36
Page 6-37
Page 6-38
Page 6-39
Type: PF
CSCO
CD, COPR, MO, CSCO, CSMO, CSCD, CS, *NULL
Copy Source, Compile Object
Lib: APDATALIB
Lib: APDATATST
Lib: APRPGSRC
Lib: REFLIB
Lib: REFLIB
F7=Change top
F11=Unprotect fields
F12=Cancel
File copy FMTOPT only appears when type is a physical file type (PF).
Supply the object name, type code, and action code and press Enter. The remaining fields are
filled in from the application definition defaults.
As with the form level entries, field defaults and rules defining which fields are locked and
which can be changed are determined from the application definition. For more information,
see Chapter 1: Working with Application Definitions.
For edit rules for the panel, see the TURNOVER for iSeries v100 Supplement entitled The
TURNOVER for iSeries v100 Change Process (#14).
For field definitions, see F1 Help text.
To jump ahead, go to the next panel ...
Page 6-40
Page 6-41
Exiting from the TURNOVER for iSeries v100 Form Maintenance panel
Once you have reviewed and updated your form, press F3 or Enter to exit from the Form
Maintenance panel.
Youll see the Form Maintenance Options panel:
1/29/10
14:46:19
To run Form Maintenance exit options, type choices and press Enter. To return
to Form Maintenance without running options, press F12. To exit without
running options, press F3.
Form . . . . . . . . . 40567
Description . . . . . Chg credit-term verify program
Resequence the form . . . . . . . . . . . . . . . .
Y, N
Y, N
. .
Y, N
. .
Y, N
Y, N
F3=Exit
F12=Cancel
Normally youll take the defaults set by TURNOVER for iSeries v100 and press Enter. If youve
already performed the operations listed here, you can press F3 to exit without running them. F12
returns you to form maintenance.
Page 6-42
Page 6-43
0 Level:
1=Send message
1
_
_
5=Display Group
User Name
Approved
PSHIFTY
Paul Shifty
N
TURNOVER TURNOVER System Admin.
Y
QAGROUP
Quality Assurance Group
N
Date
Time
00/00/00
01/08/10 13:21:01
00/00/00
By
TURNOVER
Enter message text and press F10 to send message to selected Users.
F3=Exit F9=View Prj/Tsk
F10=Send message F11=View form
F21=Select all
35 A developer will perform this function by selecting option 48 on your Programmers Worklist (PWM) rather than from this menu. For more about
PWM, see the TURNOVER for iSeries v100 Developers Guide and Chapter 9: Working with Projects and Tasks in this guide.
36 See Chapter 1: Working with Application Definitions.
Page 6-44
Page 6-45
Form
1423554
1423553
1423551
1423547
1423546
1423545
1423544
F3=Exit
F12=Cancel
Description
Contact cmmnt changes
1st top secret T.O.
Change check writing
Chg. alloc. method 3
Enhance budget format
Submenu call chg MENU
Prtfile paint enhance
4=Cancel form
8=Work w/ job
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
Apply filters . . N
5=Display form
9=Release job
Run
2/04/09
1/29/09
1/22/09
1/18/09
1/18/09
Programmer
DELANEY
ELMSMIKE
ELMSMIKE
ELMSMIKE
PHILLIPS
ELMSMIKE
PHILLIPS
Status
READY
RAN-OK
READY
DISTRIB
PARTIAL
EMER-OK
RECOVER
F11=Alternate view
F24=More keys
Type 6 next to the TURNOVER for iSeries v100 form you have entered to print it. You are
prompted for print instructions. An example of the printed TURNOVER for iSeries v100 form
appears below.
1/ 29/1 0
17: 08:0 0
Fo rm List ing
A P R O V A L S
** *** **** **** *** **** **** *** **** **** *** **** **** ***
* ___ ____ ____ ___ ____ ____ __
____ /__ __/_ ___
*
* ___ ____ ____ ___ ____ ____ __
____ /__ __/_ ___
*
* ___ ____ ____ ___ ____ ____ __
____ /__ __/_ ___
*
** *** **** **** *** **** **** *** **** **** *** **** **** ***
*** **** *** **** **** *** **** **** *** **** **** *** **** **** ****
*
APP LIC ATIO N: A /P Acco unts Pa yabl e
*
*
REL EASE -#:
*
*
V ERSI ON-# :
*
*** **** *** **** **** *** **** **** *** **** **** *** **** **** ****
*** **** *** **** **** *** **** **** *** **** **** *** **** **** **** *** **** **** *** **** **** *** **** **** *** **** **** *** **** **** ***
*
Form :
20 0008
Desc ript ion : Ch ange ch eck writ ing pgm
St atu s: R eady
*
*
Run dat e:
2/0 8/09
J ob d esc ript ion:
AP 1
R efer enc e#:
*
*
Run tim e:
21: 41:3 7
Libr ary:
PR OD
P rogr amm er:
ELM SMI KE
*
*
Jo b n umbe r:
Jo b ac cou ntin g:
*
*
Libr ary lis t:
*JO BD
*
*** **** *** **** **** *** **** **** *** **** **** *** **** **** **** *** **** **** *** **** **** *** **** **** *** **** **** *** **** **** ***
Lin e:
Lin e:
Lin e:
1
2
3
Ty pe: PF
Ty pe: LF
Ty pe: LF
If your form has commands, comments or approvals, they appear on the printed version as well (not
shown in sample).
If you want the approval box to be printed on the form, answer the Print for approval prompt with
Yes. If you want to see full line-level details on the form, type *FULL in the details prompt. If you
want to print several forms, refer to the TURNOVER for iSeries v100 Reporting Menu. To print
the details of the task referenced on the form, enter *LINE or *FULL in the task details parameter.
Page 6-46
F3=Exit
F12=Cancel
Description
Contact cmmnt changes
1st top secret T.O.
Change check writing
Chg. alloc. method 3
Enhance budget format
Submenu call chg MENU
Prtfile paint enhance
4=Cancel form
8=Work w/ job
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
Apply filters . . N
5=Display form
9=Release job
Run
2/04/09
1/29/09
1/22/09
1/18/09
1/18/09
Programmer
DELANEY
ELMSMIKE
ELMSMIKE
ELMSMIKE
PHILLIPS
ELMSMIKE
PHILLIPS
Status
READY
RAN-OK
READY
DISTRIB
PARTIAL
EMER-OK
RECOVER
F11=Alternate view
F24=More keys
More options:
1=Perform error check on form
17=Run turnover without error checking
10=Form approval
11=Distribution status
12=Create recovery form
More.keys:
F17=Filters
F21=System Command
F23=More options
Page 6-47
F3=Exit
F4=Comments
F5=Resequence
F6=Add line
F7=Locks
Bottom
F24=More keys
As described previously (see page 6-34), the options on this panel enable you to perform a number of
operations associated with the lines on a form. One such operation you can perform is to override the
create command parameters for a form line, providing the command parameters are not protected.
(Conditions under which TURNOVER for iSeries v100 protects create command parameters against
user modification are described below.)
TURNOVER for iSeries v100 protects, or does not protect, create command parameters against
user modification based on the contents (Y or N value) of the one-character data areas, TPROTECT
and TALWKEYOVR, and whether or not the TKEYPRTF file contains a record (such as *ALL
CMD) for the create parameter.
The conditions you can set with the TPROTECT and TALWKEYOVR data areas and the
TKEYPRTF file are summarized here:
Page 6-48
Results
Contains a Y
value.
TURNOVER for
iSeries v100
protects create
parameters.
TKEYPRTF file
Contains an
N value.
Contains a record
for the parameter.
Contains an
N value.
Contains no record
for the parameter.
TALWKEYOVR
data area
TURNOVER for
iSeries v100 does
not protect create
parameters.
Contains a Y
value.
Note: Your settings only control what developers can override at the development level.
Depending on the promotion methods (for example, CSCO) and create parameters (for
example, P) you have specified, these values could changes during the form run.
Results
Once a form is
copied to another
application or
application level, or
is received on
another computer,
TURNOVER for
iSeries v100 does
not reset nonprotected
parameters that are
explicitly specified in
the global type code.
On the Form Maintenance panel, to override the create command parameters for the form line, select
the line with option 10 (CreateParms) and press Enter.
Page 6-49
Change a Line
Form:
Type choices, press Enter.
Object: APLF991A
Library: PRODLIB
Method:
Type: LF
CSCO
CD, COPR, MO, CSCO, CSMO, CSCD, CS, *NULL
Copy Source, Compile Object
Lib: ACPTTEST
Lib: ACPTTESTT
Lib: PRODLIB
Lib: REFLIB
Lib: REFLIB
Page 6-50
Method
Field Attributes
R=Restrict, L=Lock
L
. . . . . . . . . CSCO
Compile parameters . . . P
Reference object . . . .
Library . . . . . . .
L
L
L
Authority . . . . . . . . P
Reference object . . . .
Library . . . . . . .
L
L
L
R
R
.
.
.
.
.
.
.
.
Y
Y
*CHECKOUT
*FORM
More...
You can remove the Rs, which indicate that a field is restricted. This enables you to change the
associated field when you return to the previous panel.
If the field you need to change is Locked, then you should see your System Administrator to
determine if the field needs to be unlocked within the application definition or whether the reasons for
the changes you are trying to make are sound.
Press Enter when youre done to confirm the changes.
When youve completed changing the line, you will be returned to the Form Maintenance panel.
Page 6-51
F3=Exit
F4=Comments
F5=Resequence
F6=Add line
F7=Locks
Bottom
F24=More keys
Page 6-52
Form Comments
Form:
2=Change
13
4=Delete
Date
Time
Added
Added
Added-by
8/23/09 15:31:14 PHILLIPS
2
F3=Exit
F6=Add comment
Comment Text
This is a sample of a comment about the entire+
This is another comment.
F12=Cancel
Select a comment to change by typing a 2 next to the comment line, or press F6 to add a new
comment.
1/29/10
15:28:54
Form:
13
F3=Exit
F12=Cancel
Page 6-53
Line Comments
Form:
Line:
2=Change
4=Delete
Date
Added
8/23/09
8/23/09
F3=Exit
13
1
Time
Added
Added-by
15:38:46 PHILLIPS
15:38:55 PHILLIPS
F6=Add comment
Comment Text
This is a sample comment about this line of th+
This is a 2nd, shorter comment about this line.
F12=Cancel
To add a line comment, press F6; to change an existing comment, select it with option 2. (The Add
and Change panels are similar.)
1/29/10
15:52:17
Form:
Line:
13
3
F3=Exit
F12=Cancel
Page 6-54
37 Another method is to code your post-run command to access the copy data from the old file in TURNOVER for iSeries v100s archive object library
using your conversion program called in a post-run command.
38 If you have commands you want to be executed every time you run a form, you might prefer to code a pre- or post-run exit program.
Page 6-55
F3=Exit
F4=Comments
F5=Resequence
F6=Add line
F7=Locks
Bottom
F24=More keys
To enter a pre-run command, position the cursor to the point above which you want to insert a
command, and press F18. The command line will be inserted after the cursor position.
You can insert a pre-run command into an existing form by positioning the cursor on the line above
the first line and pressing F18.
OR ... Select an object with option 11 and press Enter.
To enter a post-run command, position the cursor at the last line on the form and press F18. If preor post-run commands already exist on the form, position the cursor on the line after which you want
the new command inserted, and press F18.
OR ... Select an object with an option 12 and press Enter.
UNICOM Systems, Inc. Recommends
Always use option 11 or 12 if the pre- or post-run command should be associated with a particular
line on the form especially if you want TURNOVER for iSeries v100 to use that same item again
the next time the object promoted. Otherwise, use F18 to enter a command as described above.
Page 6-56
Add a Command
Form . . . . . . .
40667
Command type . . . Post-Run
Sequence . . . . .
2
Type command, press Enter.
Command to execute: CHGPGM
Error recovery: C
Link to line:
1
F10=Select
When to execute . . . *PREFORM
Library list . . . . *CURRENT
Run on system . . . . *ALL
F3=Exit
F4=Prompt command
Object: PF1
Lib: DEVELOP
Type: PF
*PREFORM, *PRELINE
*APPL, *CURRENT
*ALL, *LOCAL, *REMOTE, Name
F9=Retrieve
F10=Select line
F12=Cancel
You can prompt commands by typing the command and pressing F4. (Note: Prompting the
command allows you to change the case of the keywords and values in the command string.)
Supply up to 999 pre-run or post-run commands.
If the command fails, Error recovery tells TURNOVER for iSeries v100 whether or not to proceed.
There is a difference between the implications of errors for pre- and post-run commands.
Error recovery:
G
C
R
Error recovery:
G
C
Pre-run commands
Continue with the next step of the
TURNOVER for iSeries v100 form.
Cancel the TURNOVER for iSeries v100
form. No objects are promoted.
Roll back all installed objects and end the job.
Post-run commands
Continue with the next step of the
TURNOVER for iSeries v100 form.
End the TURNOVER for iSeries v100 job.
All objects have already been successfully
promoted. The TURNOVER for iSeries
v100 Log Report indicates that the command
was in error. The form is not rolled back.
Roll back all installed objects and end the job.
You can link your command to a specific line on the form if you so desire. To select the line, press
F10 (unless you selected options 11 or 12 described above). TURNOVER for iSeries v100 will
scroll the lines of the form through one by one. Stop scrolling when the line you want appears.
TURNOVER for iSeries v100 also brings the object name, library and object type with the line, so
you do not have to enter any information in those fields.
TURNOVER for iSeries v100 2005-2010 UNICOM Systems, Inc.
Jul-10
Page 6-57
Error recovery
When to execute
Library list .
Run on system .
PostRun: Error recovery
When to execute
Library list .
Run on system .
Linked: Command type .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
C
*PRELINE
*CURRENT
*ALL
C
*POSTFORM
*CURRENT
*ALL
*PRERUN
F12=Cancel
Bottom
F13=How to use this display
This panel shows the defaults you can specify for pre- and post-run commands. These are described
on pages 6-61 through 6-64. The TURNOVER for iSeries v100 panels on which these defaults will
appear are shown on pages 6-59 and 6-60.
Page 6-58
Add a Command
Form . . . . . . .
40667
Command type . . . Post-Run
Sequence . . . . .
2
Type command, press Enter.
Command to execute: CHGPGM
Error recovery: C
Link to line:
1
F10=Select
When to execute . . . *PREFORM
Library list . . . . *CURRENT
Run on system . . . . *ALL
F3=Exit
F4=Prompt command
Object: PF1
Lib: DEVELOP
Type: PF
*PREFORM, *PRELINE
*APPL, *CURRENT
*ALL, *LOCAL, *REMOTE, Name
F9=Retrieve
F10=Select line
F12=Cancel
Page 6-59
Form . . . . . . .
40668
Command type . . . Post-Run
Sequence . . . . .
1
Type command, press Enter.
Command to execute:
Error recovery: C
Link to line:
1
F10=Select
Object: PF1
Path: /SMITH/QA
Type: PF
Library list . . . . *CURRENT *APPL, *CURRENT
Run on system . . . . *ALL
*ALL, *LOCAL, *REMOTE, Name
F3=Exit
F4=Prompt
F9=Retrieve
F10=Select
F12=Cancel
1/29/10
17:01:30
Command type . . .
Sequence . . . . .
Error recovery . .
When to execute . .
Library list . . .
Run on system . . .
F3=Exit
F4=Prompt
. *PRERUN
*PRERUN, *POSTRUN
.
1
0-999
C=Cancel, G=Go
. C
. *PRELINE *PREFORM, *PRELINE
. *CURRENT *APPL, *CURRENT
. *ALL
*ALL, *LOCAL, *REMOTE, Name
command
F12=Cancel
Page 6-60
. . . . IFSOBJ
*PRERUN, *POSTRUN
&TY=Type code
&TP=Target path
&OB=Target object
&FP=From path
&FO=From object
&ME=Method
&PG=Programmer
&RF=Reference
&AL=Authority list
&PO=Path/Object
&UO-&U9=User defined
&TR=Target release
F4=Prompt
F12=Cancel
Descriptions of the defaults you can specify using the TSETPPCDFT (Set Pre/Post Command
Defaults) command are the following:
PreRun: Error recovery
Specify how you want TURNOVER for iSeries v100 to handle the form job if it encounters
an error while running the pre-run command. Your choices are:
C (Cancel)
G (Go)
R (Recover)
*PRELINE
Page 6-61
*APPL
*LOCAL
*REMOTE
Name
Page 6-62
G (Go)
R (Recover)
*POSTLINE
*APPL
*LOCAL
*REMOTE
Name
Page 6-63
*POSTRUN
F3=Exit
F4=Comments
F5=Resequence
F6=Add line
F7=Locks
Bottom
F24=More keys
Application:
F3=Exit
Page 6-64
F4=List
F11=Unprotect fields
Page 6-65
Page 6-66
Form:
40567
F3=Exit
Library
APDATATST
Type
*FILE
Allocate
Y
F12=Cancel
(If no lock checks exist on the form when you press F7 from Form Maintenance, the Add Lock
Checks panel shown next appears instead.)
You can remove a lock check from your form, whether it was added manually or automatically, at any
time using option 4.
Press F6 to add more lock checks.
1/29/10
17:04:19
Form . . . . . . .
Name, *ALL
Name, *ALL
*FILE, *DTAOBJ, *DTAARA, . . .
Allocate . . . . . Y
Y,N
F3=Exit
F12=Cancel
Type the name of the object that should be checked for locks.
If you want to allocate this object for the duration of the TURNOVER for iSeries v100 form run, set
Allocate to Y.
Page 6-67
Select the form with which you want to work on the Work with Forms panel with
option 2=Change.
If, when you defined your application, you set up default messages, you can view and modify them
here. You can also define completion messages as an application default.
If messages already exist, youll see this panel:
1/29/10
13:41:22
Form:
2=Change message
Comp.
Code
Normal
F3=Exit
40667
4=Delete message
Message Text
Your form has completed normally.
F6=Add message
F12=Cancel
Page 6-68
Form:
40667
Message Queue
Library .
or
User ID . . .
Address. .
F3=Exit
. . . . . . PRESIDENT
. . . . . . QUSRSYS
Name
Name, *LIBL
. . . . . .
. . . . . .
Character Value
Character Value
F12=Cancel
Enter the termination code, the message and message queue to which the message should be
delivered. The message queue can be either a personal message queue or a device message queue.
Page 6-69
Copying forms
If your applications are defined with more than one level (i.e. development to quality-assurance to
production), then after running forms for level one, you copy the form(s) to prepare a form to run to
the next level.
Also, if a form fails and recovers (form status is RECOVER), then you need to copy it to create a
new form to run. For audit control reasons on the development computer, you cannot rerun a form
that has already run.
You may have entered a form, canceled it, and decided later that you want to do the same set of
changes after all. (You cannot reactivate a form once it has been canceled or run.)
There are two types of form copies. One is a simple copy of one form to create a new form. On the
Work with Forms panel, select the form you want to copy with option 3=Copy (or use option
43=Copy form on the Programmer Worklist panel).
Copy Form
Copy From
Form . . . .
Description
Form status
Application
Release . .
Version . .
Level . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 104859
. Corrections to Install program
. RAN-OK
. TO
. 4
.
. 1
Copy to
Application . . . . . . .
Release . . . . . . . . .
Version . . . . . . . . .
Level . . . . . . . . . .
New form description . . .
*Drop COPR lines . . . . .
*Copy commands. . . . . . .
*Copy comments . . . . . .
*Check cross-reference. . .
*Check related applications
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
TO F4=Select
4
2
Corrections to Install Program
Y, N
N
Y
Y, N
Y
Y
Y
F3=Exit
F4=Select application
F12=Cancel
F19=Submit to batch
Press Enter or F19 to copy form, or press F3 or F12 to cancel form copy.
Accept the defaults or type another target application and description and press Enter.
TURNOVER for iSeries v100 creates the new form.
Page 6-70
3
3
Form
104555
104554
104553
104552
104551
104550
104549
104548
104547
104546
F3=Exit
F12=Cancel
Description
LF member not added
LF member not added
Checkout/promote Dre
Checkout/promote Dre
Testing delete of LF
Incorrect text durin
Removal of pre-run c
Correct requester fi
HD420009 CPF0001 i
HD420009 CPF0001 i
4=Cancel form
8=Work w/ job
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
Apply filters . . N
5=Display form
9=Release job
Run
5/16/09
5/15/09
5/13/09
5/13/09
Programmer
BRADLEY
ELMSMIKE
BRADLEY
DAVIS
DAVIS
BRADLEY
DAVIS
ELMSMIKE
ELMSMIKE
ELMSMIKE
Status
READY
READY
APL-PND
INITIAL
READY
PURGEPND
PURGEPND
READY
PURGEPND
PURGEPND
F11=Alternate view
F24=More keys
Page 6-71
TURNOVER for iSeries v100 eliminates any duplicate objects when it merges two or more
forms.
If more than 999 total lines are involved, TURNOVER for iSeries v100 splits the result into
multiple, correctly-sequenced, dependent forms.
If you request a cross-reference check, we check the table identified in the application definition.
This can be particularly useful if applications other than that on the consolidated form share the
same cross-reference table.
The consolidation job always submits to batch as job CPYFORMS. This job produces a log
report showing you
o
Which, if any, lines were dropped during the copy, the associated reason codes, and footnotes
explaining the reason codes; and
To consolidate several forms, select them all with option 3 on the Work with Forms panel. 39 This
panel appears:
01/29/10
12:42:33
This panel appears only if you have selected multiple forms for copying.
39 You can also do this from the Programmer Worklist using option 43.
Page 6-72
Page 6-73
................................................................
:
Select Application for New Form
:
:
:
F4=List
:
:
Application . . . XX
:
:
Release . . . . . 2
:
:
Version . . . . .
:
:
Level . . . . . . 3
:
:
:
:
:
:
:
:
: F4=List F12=Cancel
:
:
:
:
:
:..............................................................:
New form description . . . Installation programs
Review sequencing of commands before running form.
TURNOVER for iSeries v100 defaults to the application for the last form you selected. Press F4 to
see a list of applications from which to choose. Press Enter to copy. Allow a minute for the copy to
complete. (If you are consolidating forms, the job is submitted to batch.)
Youll see the Form Maintenance panel next. Verify the new form and then exit.
Setting a cross-reference threshold
If a form is large, its possible to approach or exceed the maximum number of lines allowed on a
form. To reserve space for the objects added during the cross-reference check, you can set an
overflow threshold in the XREFOVRFLW data area. This threshold controls the number of lines that
TURNOVER for iSeries v100 can add to a form before it begins adding cross-reference items to the
form. The default number of lines that TURNOVER for iSeries v100 can add to a form before
cross-referencing is 900.
Page 6-74
The test and production source file names and libraries will be determined by the target
application.
The from library (from which objects may be duplicated or moved) is determined by the default
entry for the target application.
The object library name will be determined by the default entry for the target application.
The object name must conform to the naming convention defined in the default entries for the
target application.
Field protection (Lock or Restrict specifications) will be determined by the default entries of the
Target application.
The TURNOVER for iSeries v100 Method will be determined by the target application.
The P/T/S/R/C rules for Create Parms and the P/T/S/R rules for Authority will be determined by
the target application. (For a Create Parm of C, see next page)
If an object appears on more than one form being copied, it will appear only once on the new
form. A unique object is one with a unique name, type, action, attribute and library.
The Action code (Add or Replace) will automatically be set appropriately, depending on whether
the object exists in the target library.
The user doing the copy must have authority for both the existing form and target application.
Pre-run or post-run commands will be copied, unless you answer the prompt N. TURNOVER
for iSeries v100 will look for library references related to one level and convert them to
comparable library names appropriate for the next level. Note: If the library in the command is
not referred to in the from application, TURNOVER for iSeries v100 will not convert these
library names.
Completion messages will be copied unless you answer the prompt No.
Line or form comments will be copied unless you answer the prompt N.
40 These rules also apply to forms distributed to other computers; the form is copied to conform with the local application definition.
Page 6-75
If you copy an LF line that was added automatically by TURNOVER for iSeries v100 on the
from form, then TURNOVER for iSeries v100 will delete those lines from the new form.
Logical file entries appropriate for the target level will be added to the form later, before it is run.
If a create command has been customized for a form line (Create Parm: C), the command will be
copied forward and library references will be converted appropriately to match test and production
libraries of the target application. (See next rule for exception.)
This rule applies when copying a line from one application to another application with different
object types. For example, you may want the create RPG program command set to
*NOOPTIMIZE when you compile the program for acceptance testing and to *OPTIMIZE
when you compile it into production. In this case TURNOVER for iSeries v100 allows you to
define two type codes (such as RPG and RPG2), each one set up to use different versions of the
CRTRPGPGM command.
If the type codes for the source and target applications match, TURNOVER for iSeries v100
will copy the object type code to the same type code (for example, RPG to RPG). The same
create command will be used on the new form that was used on the old one.
If the type codes for the source and target applications do not match, TURNOVER for iSeries
v100 will pick the first type code of the target application that matches the first two positions of
the type code. For example, CLP might be changed to CLP2; PF1 to PFX; RPG to RPG2. Note
that form lines with customized commands (Create parm: C) will not be copied forward in this
instance.
If the source application has no equivalent type code, TURNOVER for iSeries v100 will copy
the line as it is, using the same type code, even though that type code may not be valid for the
target application. In that case you will get an error when you try to submit the form to run.
For information regarding copying forms for interrelated applications, see the TURNOVER for
iSeries v100 Supplement entitled Managing Multiple Versions (#63).
Page 6-76
F3=Exit
F12=Cancel
Description
LF member not added
LF member not added
Checkout/promote Dre
Checkout/promote Dre
Testing delete of LF
Incorrect text durin
Removal of pre-run c
Correct requester fi
HD420009 CPF0001 i
HD420009 CPF0001 i
4=Cancel form
8=Work w/ job
Apply filters . . N
5=Display form
9=Release job
Run
5/16/09
5/15/09
5/13/09
5/13/09
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
Programmer
BRADLEY
ELMSMIKE
BRADLEY
DAVIS
DAVIS
BRADLEY
DAVIS
ELMSMIKE
ELMSMIKE
ELMSMIKE
Status
READY
READY
APL-PND
INITIAL
READY
PURGEPND
PURGEPND
READY
PURGEPND
PURGEPND
F11=Alternate view
F24=More keys
16:49:51
YOURSYS
Form to be recovered . . . 1422905 Add field to Payroll, GL, and Accts Paya
Select the objects to be recovered and press Enter to create recovery form.
Press F21 to select all objects and create recovery form.
1=Select
Line
001
Object
ACTPYBMSTF
Library
MSQADTA
Type
PF
Line
Status
RAN-OK
Action
ADD
Recovery
Action
DELETE
Page 6-77
17:14:10
YOURSYS
Reference: PROJ0002
1=Select
Object
ACTPYBMSTF
Library
MSQADTA
Type
PF
Method
MO
Bottom
F3=Exit
F9=Change task
F21=Select all
If you want to check items out at the same time, select them on this panel and press Enter.
3. Once youve created the recovery form, submit it to be run.
UNICOM Systems, Inc. Caution!
Use extreme caution if you are reversing a physical file. TURNOVER for iSeries v100 will copy
the data from the new version of the file to the old version, using the copy command Record format
field mapping parameter *MAP *DROP. Normally this is exactly what you would want it to do, but
you should consider whether or not you want the file changes since the TURNOVER for iSeries
v100 form that you are recovering was run. The original data is contained in the TURNOVER for
iSeries v100s Archive library. You may want to avoid the copy and have the data restored as well.
The recovery form reverses changes. The recovery TURNOVER for iSeries v100 form uses the
TURNOVER for iSeries v100 Archive library as the from library and the production library(s) as
the target library. The method of the recovery form will be MO (Move Object). Deleted objects
are moved back into the production library, and replaced objects will replace the newer versions.
If you only want to undo (recover) some of the objects, you can do so by editing the recovery forms
and deleting lines you do not want to undo.
Note: If multiple ASPs (Auxiliary Storage Pools) are being used, up to sixteen TURNOVER for
iSeries v100 temporary libraries may exist at the end of a TURNOVER for iSeries v100 run (if you
are archiving objects); one for each of your ASPs. All of these must exist on-line when the recovery
TURNOVER for iSeries v100 form runs. The temporary library names are TnnnnnnnDx, where
nnnnnnn=form number and x=ASP, 0 through F representing from one to sixteen ASPs.
Page 6-78
1=Send message
User
PSHIFTY
GIBBONSED
QAGROUP
Name
Paul Shifty
Ed Gibbons
Quality Assurance Group
Approved Date
Y
02/08/09
N
0/00/00
N
0/00/00
Time
13:21:05
By
PSHIFTY
F3=Exit
F7=Message programmer
F11=View form
F9=View Prj/Tsk
F12=Cancel
F21=Select all
Enter message text and press F10 to send message to selected users.
View the project task details or the form details. If you approve the changes, type Y in the approval
column next to your profile name. You can also cancel your approval by changing the Y to N.
When you define the approval list, you can create approval groups such as Quality Assurance group.
You can include all of the people in QA in that group such that, if any one within that group approves
the form it may fall to any one of several people it is approved for the group.
If the user has override authority for the application, s/he can enter an approval for all or some of the
other users on the list. This may be a useful feature if only one of several people needs to approve the
form before it can be submitted to run.
Once the form has been approved, the form status will be advanced to READY. Later, if changes are
made to the form, or if test objects or source members referenced on the form have changed, the
status will revert to APL-PN and it will need to be approved again.
UNICOM Systems, Inc. Recommends
We recommend that you use an approval list rather than rely on printing and approving hard copies of
the TURNOVER for iSeries v100 form. The online approval history remains with the form and can
be printed or reviewed at any time.
Page 6-79
Page 6-80
Page 7-1
Page 7-2
Form
103340
103339
103338
103337
103336
103330
103327
103326
103325
103324
103321
103320
F3=Exit
F12=Cancel
Description
Added by KLINE
Change worklist Prob
Create worklist Prob
Fixes to update pgm
Session or device er
Recursive call in app
Error checking not go
Error checking not go
Added by KLINE
Added by KLINE
Added by ELMSMIKE
Added by ELMSMIKE
4=Cancel form
8=Work w/ job
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
Apply filters . . N
5=Display form
9=Release job
Run
6/17/09
6/17/09
6/14/09
6/10/09
6/10/09
6/14/09
6/14/09
6/09/09
6/08/09
Programmer
KLINE
KLINE
KLINE
PHILLIPS
MARKSSUE
MILLER
ELMSMIKE
ELMSMIKE
KLINE
KLINE
ELMSMIKE
ELMSMIKE
Status
READY
READY
READY
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
More...
F11=Alternate view
F24=More keys
More options:
1=Perform error check on form
17=Run turnover without error checking
10=Form approval
11=Distribution status
12=Create recovery form
More.keys:
F3=Exit
F17=Filters
F5=Refresh
F6=Add form
F7=DSPMSG
F21=System Command F23=More options
F11=Alternate view
F24=More keys
Note: The person running the TURNOVER for iSeries v100 may be someone other than the
programmer. You must be authorized to run a TURNOVER for iSeries v100 form.
If you are unable to submit a form and you have run authority, your application might be set up to
allow only an Administrator to submit forms. See your Administrator if this is the case.
Form status
The form status must be READY or RECVD on a remote computer for the form to be eligible for
processing.
If the form status is APL-PN, people on the approval list must approve it. Type 10 next to the form.
(If you are using the Programmer Worklist, use option 48 to see the approval list.) To see a list of
forms pending your approval, press F10.
Page 7-3
Page 7-4
Submit Form
Form . . . . . . . . . 1000131
Application . . . . . .
AP
Status . . . . . . . .
READY
Level: 1
F3=Exit
F5=Refresh
F10=Form approval
F12=Cancel
F15=Scheduling
Note that you would also see this panel if you selected option 7 from the TURNOVER for iSeries
v100 Main Menu and entered a form number on the Submit Form panel (or used option 48 on the
Programmer Worklist). Some of the Form Submit Options are already selected for you; you can
change or accept the selections.
What you can do:
Form schedule date
Type the date on which the form should run, or type *CURRENT to use todays date.
Form schedule time
Type the time at which the form should run, or type *CURRENT to use the current time.
Submit on hold
Type Y or N to indicate whether you want the form processing job to be submitted on hold,
such that it must be released manually to run.
Error-check ...
Error-checking a form refers to the process of checking the form for potential errors before
running it. The error-checking option default is determined by the application definition. You
can do error checking interactively if you have a short form. Any errors detected will be
displayed in a window on this panel. Errors and warnings will be reported; if you only have
warnings and they are acceptable, then you can submit the form by pressing F6. See
Submitting a TURNOVER for iSeries v100 Error-Check Job on page 7-15.
Page 7-5
If you have TURNOVER for iSeries v100 submit the error-check to batch, the error-check job
will be called SBMnnnnnnn 41 (where nnnnnnn is the TURNOVER for iSeries v100 form
number). If no errors are found, TURNOVER for iSeries v100 will submit the form job to be
run. If errors are found, TURNOVER for iSeries v100 will send a message to the programmer
and print an error log. TURNOVER for iSeries v100 will not submit the form to be run.
If you selected option 1=Error check on Work with Forms or 41=Error check form from the
Programmers Worklist, then only Error check in batch option will be selected when the Submit
Form panel is displayed next, but you may select Error-check interactively if you prefer.
If any warnings are detected, F6=Run with warnings will appear in the error-check messages
window. You must press F6 to submit the form.
If you select option 17=Run form without error-checking on Work with Forms, error check
options will not be selected.
Submit ...
The submit of the form can be done immediately, on hold or as a timed-job.
You must have authority to submit a form. If you dont have authority, you will not be able to
select the submit options.
The job name of the submitted job is TOnnnnnnnG where nnnnnnn is the TURNOVER for
iSeries v100 form number.
Check for checked out objects not on form
Select this option to check for objects that have been checked out using the form reference, but
are not included on the form. If any such objects are selected and there is an approval list
associated with the application, the form status becomes APL-PN and any submit options that
were selected will be canceled.
Work with form
Select this to view or update the TURNOVER for iSeries v100 form. 42
Work with form distribution defaults
If you have authority to maintain distribution defaults, and if distribution is specified in the
application level definition, then this option will be available. Use it to override the
distribution defaults for this application level.
41 If you submit an error check only job to batch, the job name will begin with CHK.
42 For more information, see Chapter 6: Working with TURNOVER for iSeries v100 Forms.
Page 7-6
Form . . . . . . 1000133
Description . . . Demo form II
Distribution job schedule date
Distribution job schedule time
Schedule elapsed action . . .
Automatic remote rollback . .
Position to system
2=Change 4=Remove
System
Name
Description
S1014444
SLS Product4
S1014445
SLS Product5
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*CURRENT
*CURRENT
*SBMRLS
*NO
*CURRENT, date
*CURRENT, hhmmss
*NEXTDAY, *SBMHLD, *SBMRLS,...
*NO, *RMT, *ALL
Device
*SNADS
TAP01
Receive
Logs
Back
*RMTDFTS
*RMTDFTS
Receive
Confirmation
Back
Y
Y
F15=Scheduling
The system or systems that appear highlighted in the list are on the distribution list for the application
to which this form applies. The columns describe some of the distribution settings.
What you can do:
Press Enter to accept the distribution defaults and continue processing your other form submit
options, or
Override the distribution defaults by selecting a system with option 2; press Enter.
Press F13 to repeat the last option specified, beginning with the selected system and ending with
the last system listed.
Press F15 to adjust the form, distribution, or remote form job schedule. (Read Scheduling Form
Jobs on page 7-10.)
If you accept the distribution settings and continue, the form is submitted for processing according to
your selections on the Submit Form panel.
Page 7-7
If you decide to override the distribution defaults, you see the Change Distribution Defaults for
Form panel after you press Enter.
1/29/10
11:01:12
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1000133
Demo form II
S1014706
UNICOM D4
Distribute . . . . . . . . . . . .
Target user id and address . . . .
Distribution device . . . . . . . .
Distribute source . . . . . . . . .
Distribute objects . . . . . . . .
Remote form schedule date . . . . .
Remote form schedule time . . . . .
Schedule elapsed action . . . . .
Submit received forms automatically
Receive logs back . . . . . . . . .
Receive confirmations back . . . .
Receive forms method . . . . . . .
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Y
Y, N
TURNOVER S1014444 UserId-Address
*SNADS
Device, *SNADS, *NONE
Y
Y, N
Y
Y, N
*CURRENT
*CURRENT, date
*RMTDFTS
*RMTDFTS, *CURRENT, hhmmss
*RMTDFTS
*RMTDFTS, *NEXTDAY,...
*RMTDFTS
*RMTDFTS, Y, N
*RMTDFTS
*RMTDFTS, Y, N
*RMTDFTS, Y, N
Y
*AUTOSTART *AUTOSTART, *PASSTHRU
F12=Cancel
Use this panel to override the distribution default settings for this form. 43
What you can do:
Page 7-8
Page 7-9
Form Scheduling
.
.
.
.
.
.
Form
Schedule
System
Date
S1014706 200 *CURRENT
Schedule
Elapsed
Action
*RMTDFTS
Form
Schedule
Time
*RMTDFTS
.
.
.
.
.
.
.
.
.
.
.
.
*CURRENT
*CURRENT
*NO
*CURRENT
*CURRENT
*SBMRLS
*CURRENT,
*CURRENT,
*NEXTDAY,
*CURRENT,
*CURRENT,
*NEXTDAY,
date
hhmmss
*SBMHLD, *SBMRLS,...
date
hhmmss
*SBMHLD, *SBMRLS,...
Bottom
F3=Exit
F12=Cancel
Using this panel, you control the date and time that your form can be run locally, distributed to a
remote computer, and submitted on the remote computer. The distribution and remote job fields
appear only if the form is for a distributed application. The elapsed action parameters let you tell
TURNOVER for iSeries v100 what to do if the job could not start on time.
You can access this panel using F15=Scheduling on any of the following panels: 45
Type information in the local form scheduling fields to indicate when the local form job should
run.
Type information in the distribution job scheduling fields to indicate when the form should be
distributed.
Type information in the fields next to the remote systems listed at the panel bottom, to control the
timing of the form-processing job on each remote computer where it will be distributed.
Page 7-10
Use F11 to adjust the schedule and distribution information for forms in a form group.
The remaining fields control the processing of the jobs on their respective systems. Local
form jobs are processed on a development computer; distribution jobs are processed on a
sending computer (which could be a development or a production computer); and remote form
jobs are processed on a receiving computer (which also could be either development or
production).
Schedule date fields
In the date fields for the local form and distribution jobs, you can type a specific date on which
the job should run, or use *CURRENT to retrieve and use the current system date.
For the remote form job schedule date, you can also type *RMTDFTS to retrieve and use the
date in the remote computers local form schedule defaults.
Schedule time fields
In the time fields for the local form and distribution jobs, you can type a specific time at which
the job should run, or use *CURRENT to retrieve and use the current system time.
For the remote form job schedule time, you can also type *RMTDFTS to retrieve and use the
time in the remote computers local form schedule defaults.
Schedule elapsed action fields
The Schedule elapsed action fields let you tell TURNOVER for iSeries v100 what to do
with the job if the schedule date or time you set has passed by the time the job processor
begins to run the job.
In the elapsed action fields for the local form and distribution jobs, you can type one of these
choices:
*NEXTDAY
*SBMHLD
*SBMRLS
*NOSBM
In the elapsed action field for the remote form job, you can type one of the above choices, or
you can type *RMTDFTS to retrieve and use the remote computers default elapsed action
information.
Page 7-11
7
7
7
Form
103340
103339
103338
103337
103336
103330
103327
103326
103325
103324
103321
103320
F3=Exit
F12=Cancel
Description
Added by KLINE
Change worklist Prob
Create worklist Prob
Fixes to update pgm
Session or device er
Recursive call in app
Error checking not go
Error checking not go
Added by KLINE
Added by KLINE
Added by ELMSMIKE
Added by ELMSMIKE
4=Cancel form
8=Work w/ job
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
Apply filters . . N
5=Display form
9=Release job
Run
6/17/09
6/17/09
6/14/09
6/10/09
6/10/09
6/14/09
6/14/09
6/09/09
6/08/09
Programmer
KLINE
KLINE
KLINE
PHILLIPS
MARKSSUE
MILLER
ELMSMIKE
ELMSMIKE
KLINE
KLINE
ELMSMIKE
ELMSMIKE
Status
READY
READY
READY
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
More...
F11=Alternate view
F24=More keys
Apply filters . . N
5=Display form
9=Release job
Page 7-12
Y, N
F12=Cancel
Fixes to update pgm
Session or device er
Recursive call in app
Error checking not go
Error checking not go
Added by KLINE
Added by KLINE
Added by ELMSMIKE
Added by ELMSMIKE
SLS
TO
TO
TO
TO
T1
T1
T1
T1
3
3
3
3
1
1
1
1
2
2
2
2
2
1
1
1
1
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
6/17/09
6/17/09
6/14/09
6/10/09
6/10/09
6/14/09
6/14/09
6/09/09
6/08/09
Status
READY
READY
READY
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
More...
F11=Alternate view
F24=More keys
Programmer
KLINE
KLINE
KLINE
PHILLIPS
MARKSSUE
MILLER
ELMSMIKE
ELMSMIKE
KLINE
KLINE
ELMSMIKE
ELMSMIKE
If your answer to the Link submitted forms prompt is Yes, youll see this panel:
1/29/10
Work with Forms
Your Company, Inc.
14:28:32
YOURSYS
...............................................................................
:
Work with Form Group
:
:
:
:
Form group schedule date . . . *CURRENT *CURRENT, date
:
:
:
Form group schedule time . . . *CURRENT *CURRENT, hhmmss
:
Schedule elapsed action . . . *SBMRLS
*NEXTDAY, *SBMHLD,...
:
:
Submit on hold . . . . . . . . N
:
:
Submit form finalization . . . N
:
:
Error Distribution :
:
Form Description
Seq Check
Defaults
:
: 103338 Create worklist Prob
10
Y
N
:
: 103339 Change worklist Prob
20
Y
N
:
Y
N
:
: 103340 Added by KLINE
30
:
:
:
:
:
Bottom :
: F3=Exit
F12=Cancel
F15=Scheduling
:
:
:
:
:
:.............................................................................:
F12=Cancel
F14=WRKSBMJOB
F16=User options F24=More keys
You can change the sequence in which the forms should be run, set the Error Check indicator on or
off (if you are authorized to run without doing the pre-run error checking), and you can view or
change the Distribution Defaults (if you have Distribution authority).
If this form group will be distributed, you can use F15 to control the timing of the local form job, the
distribution job, and the remote form job.
If your answer to the Link submitted forms prompt is No, youll see the normal Submit Form panel
for each form you selected.
Page 7-13
When you select more than one form to be run in a group, all forms will be run under the control
of one job.
The name of that job is TOnnnnnnnG, where nnnnnnn is the form number of the first form in the
group.
As soon as you select the forms to be included in the group, the form status for all of these forms
is set to IN-USE.
If you select the option to do error checking, all forms are checked and the job will continue only
if no errors are detected; otherwise, an error report will be printed.
Once the form group is submitted, status is set to SUBMIT for all forms in the group.
When the group form job starts to run, all forms are set to IN-USE. The form that is actually
running is set to status RUNNING.
Form status will remain at RUNNING status until all form processing has completed.
Once the finalization phase of the final form has started, the form status of all forms will be set to
FINAL. At this point, your completion messages will be sent and your users are free to use the
objects.
Page 7-14
Are there any logical files related to any physical file on the form that have not been included
on the form (TURNOVER for iSeries v100 adds them to the form)?
Have any source members or test objects been changed since the form was approved (if you
use the on-line approval feature)?
Are all of the files that are referenced by the programs on the form found in the library list of
the job description under which the form will be running? You will see warning messages if
necessary files are not found.
Do the source and object members match, if youre using TURNOVER for iSeries v100
methods CSMO or CSCD?
Have any objects or source been checked out under the same reference code since the form
was created? This might have been an oversight. Youll be prompted to add these to the form
if you forgot to earlier.
Are all of the objects and members on the form reserved or checked out to this programmer
and for the application and level indicated (depends on application settings), or for a higher
level of the same application?
Does any object on the form being submitted appear on another form that has not run to
completion? If so, if the other form status is not RAN-OK, FIN-OK, RAN-WRN, FINWRN, EMER-OK, EMER-WRN (if the application is not being distributed) or is not
CONFIRMED 46 (if the application level is being distributed) then, TURNOVER for iSeries
v100 will issue a warning message in your error-check log.
46 Confirmation requirement can be suppressed, if you want. Call our Support line for assistance.
Page 7-15
All of these checks help ensure that the form will run successfully.
Description
Added by KLINE
Change worklist Prob
Create worklist Prob
Fixes to update pgm
Session or device er
Recursive call in app
Error checking not go
Error checking not go
Added by KLINE
Added by KLINE
Added by ELMSMIKE
Added by ELMSMIKE
4=Cancel form
8=Work w/ job
F5=Refresh
F6=Add form
F7=DSPMSG
F14=WRKSBMJOB
F16=User options
Apply filters . . N
5=Display form
9=Release job
Run
6/17/09
6/17/09
6/14/09
6/10/09
6/10/09
6/14/09
6/14/09
6/09/09
6/08/09
Programmer
KLINE
KLINE
KLINE
PHILLIPS
MARKSSUE
MILLER
ELMSMIKE
ELMSMIKE
KLINE
KLINE
ELMSMIKE
ELMSMIKE
Status
READY
READY
READY
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
More...
F11=Alternate view
F24=More keys
create process (Checkout Items to be Recovered panel). Note: Compile-only objects from the
original form are not included in the list of objects you can select for checkout.
Note: To create a recovery form, the application default entry Archive objects must be set to Y. The
Archive object library must be available on your system when the recovery form runs.
F3=Exit
F5=Refresh
F10=Forms
F12=Cancel
by job
Last
Form
3004868
F14=WRKSBMJOB
Last
Line
2
Page 7-17
Depending upon what phase the form group is in (if the form group job is currently active), whether
you chose to have the form group finalization phase run in-line or as a submitted job, and whether or
not the form group is being distributed to other computers, the Work with Form Group Jobs panel
will list one, two, or three jobs.
Job TOnnnnnnnG (nnnnnnn = the form number of the first form in the form group) will be the first
job listed. This is the main form group-processing job.
Job TOnnnnnnnF (nnnnnnn = the form number of the first form in the form group) is the form group
finalization job and performs cleanup functions such as archiving source, deleting test source and
objects, refreshing the cross-reference database, and deleting temporary objects used during the form
group process. If finalization was not submitted, then these functions will be performed by job
TOnnnnnnnG.
Job DISddddddd (ddddddd = the distribution job number) is the distribution job that sends the form
group and associated objects to remote computers. This job will only be listed if the form group is
being distributed to other computers.
The status of each of these jobs will be indicated in the Status column. The group job status may be
*ACTIVE, *JOBQ, *OUTQ, or *FIN (the job has completed and all associated spooled files have
been either printed or deleted).
The last action completed by jobs TOnnnnnnnG and TOnnnnnnnF is indicated by the Last Phase,
Last Function, Last Form, and Last Line columns. The form group phases and functions are listed
in the table below.
Phase
*ERRORCHK
Function
*EXITPRE
*FORMPROC
*DEPEND
*DATETIME
*LOCK
*SYNONPRE
*PRERUNX
*CMDPRE
*LANSAPRE
Page 7-18
Description
Error-checking (performed for all forms in group before
proceeding to next phase).
Pre-form group exit (TURNOVER for iSeries v100
Exit19).
Form pre/main processing (performed for all forms in
group before proceeding).
Form dependency checks.
Form time range checks.
Form lock checks.
OVER/2E pre-run processing (if youre using
TURNOVER for iSeries v100s Synon interface).
Form pre-run exit (TURNOVER for iSeries v100 Exit
8).
Form pre-run commands.
LAN/TURN pre-run processing (if youre using
TURNOVER for iSeries v100s Lansa interface).
Function
*CRTARCLIB
*MOVARCLIB
*NEWSRCOBJ
*CRTPARMS
*MEMBERS
*DATACOPY
*DOCUMENTS
*POSTRUN
*AUTHORITY
*JOURNAL
*EXPLODE
(*POSTRUN)
*LANSAPOST
*SYNONPOST
*POSTRUNX
*CMDPOST
*FINAL
*ARCHIVE
*DELETETST
*XREF
*DLTARCLIB
(*FINAL)
*CHECKIN
*LOGS
*CONFIRM
*MESSAGES
*DISTRIB
*EXITPOST
Description
Create temporary TnnnnnnnD archive libraries.
Move source and object to archive libraries.
Copy source, compile object, and so forth.
Set creation parameters for object.
Add members to PFs and LFs.
Copy PF data.
Copy Documents.
Form post-run processing (performed for all forms in
group before proceeding to next phase).
Set authorities.
Restart journaling.
Explode data objects.
Page 7-19
Note that the Last Phase and Last Function columns indicate the last step of the form group process
that has completed. Even if a form group does not happen to make use of a particular phase or
function, all phases and functions are processed when the form group runs. For example, it is
possible that the Work with Form Group Jobs will indicate that the last function completed was
*CMDPRE (pre-run commands) even though the form group does not include any forms which have
pre-run commands.
What you can do:
Function Keys
Press F3 or F12 to exit from the Work with Form Group Jobs panel.
Press F5 to refresh the panel. The most recent status, last phase, last function, last form, and last line
will be displayed for each job.
Press F10 to display all TURNOVER for iSeries v100 forms that are part of the form group.
Press F14 to work with your submitted jobs.
Options
You can work with or display any job that has a status of *JOBQ, *OUTQ, or *ACTIVE using
options 2 and 5.
If the job is currently held then the status will be *JOBQ. You can release the job using option 6.
For an explanation of option 7, see Restarting a Failed TURNOVER for iSeries v100 Job on page
7-21.
Use option 8 to access the spooled files for any job listed here.
Use option 9 for any job listed here to see a list of jobs it in turn submitted, and access those jobs
spooled files.
Page 7-20
5=Display job
Job name
Description
7 TO3004868G Run form group
F3=Exit
F5=Refresh
6=Release job
7=Resume job
Last
Last
Last
Last
Status
Phase
Function
Form
Line
*OUTQ
*FORMPROC *NEWSRCOBJ 3004868 2
F10=Forms
F12=Cancel
F14=WRKSBMJOB
If job TOnnnnnnnG has a status of *OUTQ or *FIN, then the last phase should be *EXITPOST.
Any other phase would indicate that the form group job terminated abnormally (system failure,
subsystem ended, and so on).
If job TOnnnnnnnF has a status of *OUTQ or *FIN, then the last phase should be *FINAL and the
last function should be *DLTARCLIB. Any other phase or function would indicate that the form
group finalization job terminated abnormally.
If the form group job or form group finalization job terminated abnormally, and you have authority to
run forms for all forms in the form group, then you can resume the form group or form group
finalization job using option 7. This will cause job TOnnnnnnnG or TOnnnnnnnF to be resubmitted.
Form group processing will be resumed starting at the phase, form, line and function where the failed
job left off.
For more about this panel and a description of the various status values, see Work with Form Group
Jobs on page 7-17 in this chapter.
Page 7-21
When a form group is resumed, the new job makes use of temporary libraries and objects that were
created by the failed job. It is assumed that all source, objects, checkout records, and so forth, are
exactly as they were at the time that the original job failed. If, after the original form group job failed,
source and objects related to the form group have been moved, changed, or deleted, then the resumed
form group job may not run predictably.
The resume form group capability should be considered a valuable safety net to be used in the event
of an actual failure, and not used as part your day-to-day TURNOVER for iSeries v100 procedures.
You should make every possible effort to schedule TURNOVER for iSeries v100 form group jobs
to run at a time when you can guarantee that there will be sufficient time for them to reach successful
completion.
Page 7-22
Utility Menu
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F21=System command
Page 8-1
.
.
.
.
.
.
.
.
+
. .
. .
. .
. .
for
. . . . . .
. . . . . .
. . . . . .
. . . . . .
more values
00
00
00
Name, *ALL
00-99
00-99
00-99
00
00
00
Purge Date . . . . . .
From Form-# . . . . .
To Form-# . . . . . .
Form Status . . . . .
Retain Object History
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
1
9999999
C
Y
F12=Cancel
Date
Number
Number
C=Cncl, R=Run, P=Pend, A=C/R/P
Y,N
Bottom
F13=How to use this display
The PRGFOR command submits a job to run in batch. The user submitting the purge job must have
TURNOVER for iSeries v100 purge authority. A Purge Report lists all forms that were purged.
Only forms that have a Form Status of RAN-xx, CANCEL, or PURGEPND are eligible to be
purged. To purge a recovered form, cancel it first. You may select any of the codes or A to purge
forms with all three codes.
Page 8-2
Forms can be set to Purge Pending on Work with Forms by selecting forms with option PP.
Forms that are READY or RECOVER status can be set to CANCEL on Work with Forms by
selecting forms with option 4.
UNICOM Systems, Inc. Caution!
Make sure that the TURNOVER for iSeries v100 data library, SOFTTURND, has been backed
up recently prior to running this purge procedure! We also suggest that you print forms you are
purging (detail=*FORM) before you purge the forms. See List Forms (option 20) on the
TURNOVER for iSeries Reporting Menu (option 10 on the TURNOVER for iSeries Main
Menu.)
Type Y to Retain object history. The forms will be flagged as purged, but will not be deleted from
the system. Forms flagged as purged will not be displayed on the Work with Forms panel. The
object history will still be available when you view the Work with Object History panel. Type N (are
you sure!) to remove all records from all TURNOVER for iSeries files for the forms selected.
UNICOM Systems, Inc. Recommends
Use the form status and form number range if you want to purge a specific group of forms. If you
run a purge for an overlapping range, and do not retain the object history, all records from all files
will be deleted for form numbers that meet the purge criteria.
Page 8-3
When you select option 2 on the Utility Menu, the Work with Source Archive Files panel appears:
1/29/10 13:24:53
File
ARCHIVE
ARCHIVE
ARCHIVE
3=Save
Library
APP199
APP299
MLARCHIVE
4=Delete
5=Usage
Members
8
22
9
Size
16384
24576
16384
First
Used
9/17/99
9/17/99
9/17/99
Last
In
Save
Used
Use Date
9/17/99 N 10/05/99
9/17/99 Y 10/05/99
9/17/99 N 0/00/00
Save
Volume
991005
991005
991005
Bottom
F3=Exit
F5=Refresh
F12=Cancel
F14=WRKSBMJOB
F21=System command
Use this panel to manage the contents, usage, and existence of the TURNOVER for iSeries source
archive files on your system. 48 This list includes only source archive files that still reside on the
system. TURNOVER for iSeries v100 Object History is the best place to find information about
source members that have been saved off line. The save date and volume information you see on this
panel are likely to reflect either backup procedures or manual saves done from this panel.
47 For a description of how the TURNOVER for iSeries v100 archiving process works, read How archiving works in Chapter 4: Working with Object
History.
48 If you restore to your system a source archive file that has been saved off line, it does not show up in this list unless an application has since archived
source to it.
Page 8-4
You can move members from one file, or from several files at once. You can add conditional
processing, moving only those archived before a certain date or version. (You can specify
*ALL for the member and/or file parameters without adding conditional processing.)
Once members are copied to the target file, they are deleted from their original location. You
can then store the target file off line using option 3, and your applications will continue
archiving to the original file.
3=Save
This option runs the TSAVARCF API to store an archive file to an offline storage medium,
then updates the object history records for all objects saved with appropriate save volume and
date information.
A file is not deleted automatically during a save. You must do this using option 4 if you want
to remove it from your system.
5=Usage
Use this option to determine which files are in use, and which TURNOVER for iSeries v100
applications are using them.
4=Delete
Use this option to remove unused archive files. (You cannot remove an archive file if a
TURNOVER for iSeries v100 application is still using it.)
Page 8-5
You can control default command parameters such as Target release and Replace *YES/*NO that
TURNOVER for iSeries v100 uses when it creates an object in Production.
You can create your own object type, as when you need to create an object using a vendorsupplied create command.
You can create your own command to use in place of the system-supplied commands, if you have
some special requirements, such as collating source members before compiling an object. This
section explains how to go about changing and adding type entries.
To see a list of available type codes, select option 4 on the Utility Menu:
1/29/10
13:32:13
2=Change
Type
AAUDIT
ABPGM
ADMDL
ADPGM
AFILE
AFLD
ARPGM
ASHLP
ASUBR
BAS
BASCPY
BKPDF
BMP
BND
BNDDIR
F3=Exit
3=Copy
4=Delete
Description
ASSET Audit Trail
ASSET Batch Program
ASSET Data Model
ASSET Display Program
ASSET File
ASSET Field
ASSET Report Program
ASSET Help Text
ASSET Action Subroutine
Basic/400 program
/COPY BAS Member
Manage PDF'd book files
Windows Bitmap
ILE Binder Language
ILE Binding Directory
F6=Add Type
Object Type
*AAUDIT
*ABPGM
*ADMDL
*ADPGM
*AFILE
*AFLD
*ARPGM
*ASHLP
*ASUBR
*PGM
*SRC
*IFSOBJ
*IFSOBJ
*SRC
*BNDDIR
Data
Object
N
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
Seq
250
350
300
350
200
100
350
350
250
500
100
20
100
100
480
F8=User-defined parms
Create CMD
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
SRCFILE("&SL"/"&S
CRTBASPGM PGM("&L
More...
F24=More Keys
TURNOVER for iSeries v100 is shipped with most object types already predefined. We recommend that you consult with our support staff before changing them.
All of the valid type codes available on your system are listed on this panel.
Type 3 to copy a type code in order to create a new one. All related commands will be copied too.
Press F8 to add and update user-defined parameters that can apply to any type.
Page 8-6
You should be extremely careful when you change, delete, or create object type code entries. These
entries affect all applications on your system. You need to coordinate changes with all
TURNOVER for iSeries v100 users, and to test new object types thoroughly. Be sure you
understand how TURNOVER for iSeries v100 uses these entries before changing them. If you do
not, you may have unexpected results.
Page 8-7
Type code . .
Description .
Object type .
Sequence . . .
Create command
"&OB" =
"&LI" =
"&TY" =
"&SM" =
"&SF" =
"&SL" =
"&U0" =
"&U2" =
"&U4" =
"&U6" =
"&U8" =
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CM scheme . . .
Attribute . . .
Source file name
Data object . .
Object name
Library name
Type code
Source member name
Source file name
Source library name
Generation options
Optimization level
Source listing options
Unassigned
Binding directory
F4=Prompt/select
F8=Add IFS
.
.
.
.
. *TURNOVER
.
.
. N
"&RF" = Reference
"&X0"-"&X9" = Exit
"&TO" = Test object name
"&TL" = Test object library name
"&TR" = Target release
"&FM" = From source member name
"&FF" = From source file name
"&FL" = From source library name
"&U1" = Debugging views
"&U3" = Compiler options
"&U5" = Unassigned
"&U7" = Service program source file
"&U9" = Module source file
type code F12=Cancel F22=Long command
After you supply information for the type code you want to add, the Add a Type Code panel looks
something like this:
1/29/10
13:59:03
"&OB" =
"&LI" =
"&TY" =
"&SM" =
"&SF" =
"&SL" =
"&U0" =
"&U2" =
"&U4" =
"&U6" =
"&U8" =
F3=Exit
Object name
Library name
Type code
Source member name
Source file name
Source library name
Generation options
Optimization level
Source listing options
Unassigned
Binding directory
F4=Prompt/select
F8=Add IFS
CM scheme . . . . .
Attribute . . . . .
Source file name . .
Data object . . . .
SRCFILE("&SL"/"&SF")
*TURNOVER
CLP
QCLSRC
N
"&RF" = Reference
"&X0"-"&X9" = Exit
"&TO" = Test object name
"&TL" = Test object library name
"&TR" = Target release
"&FM" = From source member name
"&FF" = From source file name
"&FL" = From source library name
"&U1" = Debugging views
"&U3" = Compiler options
"&U5" = Unassigned
"&U7" = Service program source file
"&U9" = Module source file
type code F12=Cancel F22=Long command
Press Enter to add the type code. (Note: TURNOVER for iSeries v100 is shipped with object
types already defined.)
The information on the following pages describes how you add new types or change existing ones.
Page 8-8
With TURNOVER Release 5.3, support for user-defined object types was significantly expanded.
Release 5.3 introduced change management schemes that you can use to selectively override, for a
user-defined object type, almost any change management method (such as moving an object, copying
an object, deleting an object, and so forth) that you would execute for an object. After you create a
CM scheme and override CM methods, you must create new type codes, or change existing ones, to
use the new scheme. (Several sample schemes, with their type codes already created, are shipped
with TURNOVER for iSeries v100.) To do so, press F6 as you would to add any other type code.
1/29/10
15:10:06
Type code . .
Description .
Object type .
Sequence . . .
Create command
"&OB" =
"&LI" =
"&TY" =
"&SM" =
"&SF" =
"&SL" =
"&U0" =
"&U2" =
"&U4" =
"&U6" =
"&U8" =
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Object name
Library name
Type code
Source member name
Source file name
Source library name
Generation options
Optimization level
Source listing options
Unassigned
Binding directory
F4=Prompt/select
F8=Add IFS
.
.
.
.
. *TURNOVER
.
.
. N
"&RF" = Reference
"&X0"-"&X9" = Exit
"&TO" = Test object name
"&TL" = Test object library name
"&TR" = Target release
"&FM" = From source member name
"&FF" = From source file name
"&FL" = From source library name
"&U1" = Debugging views
"&U3" = Compiler options
"&U5" = Unassigned
"&U7" = Service program source file
"&U9" = Module source file
type code F12=Cancel F22=Long command
On this panel, in the CM scheme field, type the name of the CM scheme for which you are creating a
type code (or press F4 to select the name from a list of CM schemes). When you press F4, you see a
list of existing CM schemes:
1/29/10
15:15:35
Type code . . . . .
CM scheme . . . . . *TURNOVER
Des
Obj
Select Change Management Scheme
Seq
1=Select
Cre
Scheme
Description
UTBIO
Employee Biography Scheme
UTDDG
JD Edwards Data Dictionary Glossary Text
"&O
1 UTMENU
Menu System Scheme
"&L
"&T
"&S
"&S
"&S
"&U
Bottom
"&U
F2=Work with schemes
F3=Exit
F12=Cancel
"&U
"&U6" = Unassigned
"&U7" = Service program source file
"&U8" = Binding directory
"&U9" = Module source file
F3=Exit F4=Prompt/select
F8=Add IFS type code F12=Cancel F22=Long command
Page 8-9
TURNOVER for iSeries v100 fills the name you selected in the CM scheme field:
1/29/10
15:21:06
Type code . .
Description .
Object type .
Sequence . . .
Create command
"&OB" =
"&LI" =
"&TY" =
"&SM" =
"&SF" =
"&SL" =
"&U0" =
"&U2" =
"&U4" =
"&U6" =
"&U8" =
F3=Exit
.
.
.
.
.
.
.
.
.
.
CM scheme . . .
Attribute . . .
Source file name
Data object . .
.
.
.
.
.
Object name
Library name
Type code
Source member name
Source file name
Source library name
Generation options
Optimization level
Source listing options
Unassigned
Binding directory
F4=Prompt/select
F8=Add IFS
.
.
.
.
. UTMENU
.
.
. N
"&RF" = Reference
"&X0"-"&X9" = Exit
"&TO" = Test object name
"&TL" = Test object library name
"&TR" = Target release
"&FM" = From source member name
"&FF" = From source file name
"&FL" = From source library name
"&U1" = Debugging views
"&U3" = Compiler options
"&U5" = Unassigned
"&U7" = Service program source file
"&U9" = Module source file
type code F12=Cancel F22=Long command
After you supply information for the type code you want to add, the Add a Type Code panel looks
something like this:
1/29/10
15:25:09
Type code . .
Description .
Object type .
Sequence . . .
Create command
SM")
"&OB" =
"&LI" =
"&TY" =
"&SM" =
"&SF" =
"&SL" =
"&U0" =
"&U2" =
"&U4" =
"&U6" =
"&U8" =
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
UTMENU
CM scheme . . . . . UTMENU
My Menu
Attribute . . . . .
*UTMENU
Source file name . . UTMENSRC
Data object . . . . N
100
UTCRTMENU MENU("&LI"/"&OB") SRCFILE("&SL"/"&SF") SRCMBR("&
Object name
Library name
Type code
Source member name
Source file name
Source library name
Generation options
Optimization level
Source listing options
Unassigned
Binding directory
F4=Prompt/select
F8=Add IFS
"&RF" = Reference
"&X0"-"&X9" = Exit
"&TO" = Test object name
"&TL" = Test object library name
"&TR" = Target release
"&FM" = From source member name
"&FF" = From source file name
"&FL" = From source library name
"&U1" = Debugging views
"&U3" = Compiler options
"&U5" = Unassigned
"&U7" = Service program source file
"&U9" = Module source file
type code F12=Cancel F22=Long command
Press Enter to add the type code. TURNOVER for iSeries v100 adds the type code and displays it
on the Work with Type Codes panel.
Page 8-10
To change a type code for a CM scheme, select the type code with option 2=Change as you would
any other type code:
1/29/10
16:03:02
2=Change
Type
TBL
TXT
T3
UIMMNU
UTBIO
2 UTMENU
WORD
YINT
YUFC
YUFR
YYCLP
YYCMD
YYDSPF
YYLF
YYPF
3=Copy
4=Delete
Description
Translation Table
Copy Text Member
AS/400 Physical File
UIM Menu
User-defined Biography
My Menu
Word Documents
Synon/2E Non-source type
User Source (COBOL)
User source
CL Program
Command
AS/400 Display File
AS/400 Logical File
AS/400 Physical File
F3=Exit
F6=Add Type
Object Type
*TBL
*SRC
*FILE
*MENU
*UTBIO
*UTMENU
*IFSOBJ
*SGT
*SRC
*SRC
*PGM
*CMD
*FILE
*FILE
*FILE
Data
Object
N
N
Y
N
N
N
Y
N
N
N
N
N
N
Y
Y
Seq
400
100
410
200
100
100
900
100
100
500
400
450
425
410
F8=User-defined parms
Create CMD
CRTTBL TBL("&LI"/
CRTPF FILE("&LI"/
CRTMNU MENU("&LI"
UTCRTMENU MENU("&
&PRDLIB/TCRTOBJY
&PRDLIB/TCRTOBJY
&PRDLIB/TCRTOBJY
&PRDLIB/TCRTOBJY
&PRDLIB/TCRTOBJY
More...
F24=More Keys
Press Enter.
TURNOVER for iSeries v100 displays the type code information:
1/29/10
16:05:04
Type code . .
Description .
Object type .
Sequence . . .
Create command
SM")
"&OB" =
"&LI" =
"&TY" =
"&SM" =
"&SF" =
"&SL" =
"&U0" =
"&U2" =
"&U4" =
"&U6" =
"&U8" =
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
UTMENU
CM scheme . . . . . UTMENU
My Menu
Attribute . . . . .
*UTMENU
Source file name . . UTMENSRC
Data object . . . . N
100
UTCRTMENU MENU("&LI"/"&OB") SRCFILE("&SL"/"&SF") SRCMBR("&
"&RF"
Object name
"&TO"
Library name
"&TL"
Type code
"&TR"
Source member name
"&FM"
Source file name
"&FF"
Source library name
"&FL"
Generation options
"&U1"
Optimization level
"&U3"
Source listing options
"&U5"
Unassigned
"&U7"
Binding directory
"&U9"
F4=Prompt/select
F7=Applications
= Reference
"&X0"-"&X9" = Exit
= Test object name
= Test object library name
= Target release
= From source member name
= From source file name
= From source library name
= Debugging views
= Compiler options
= Unassigned
= Service program source file
= Module source file
F12=Cancel F22=Long command
Change the type code information as you want and press Enter.
For detailed information about creating and using CM schemes, see the TURNOVER for iSeries
v100 Supplement entitled Managing User-Defined Object Types (#59).
Page 8-11
TURNOVER for iSeries v100 allows you to create your own TURNOVER for iSeries v100 type
codes so you can create variations of standard types. When naming a new type code, begin the name
with a recognizable iSeries type code.
For example, you may want to create a second CLP type code, CLPNO, that uses a different version
of the create CL program command from the command associated with CLP. For example, you
might want to set the default to RTVSRC *NO (Allow Retrieve Source=No). You can create types
and then use them in one or more of your application default definitions. TURNOVER for iSeries
v100 will use the command you specify, even a command you yourself may have written.
Substitution variables provide a way for TURNOVER for iSeries v100 to know what fields the
command expects to be passed during the TURNOVER for iSeries v100 run.
To enter a command string longer than 256 characters (often necessary with use of substitution
variables or when binding multiple ILE programs), press F22.
Another example of a type we have defined for you is PFREF. This can be used exclusively for
creating a field reference file. It is defined with MEMBER(*NONE) and LVLCHK(*NO) and
assigned a form sequence code that ensures that it will always be listed first on the TURNOVER for
iSeries v100 form (it needs to be created before physical and logical files are created).
If you define your own type entry, use the Attribute field to tell TURNOVER for iSeries v100 what
the real attribute is. TURNOVER for iSeries v100 will use this code in Programmers Worklist
Manager (PWM) when you edit source so the right editor is used. For example, the PFREF type
referred to above should be defined with an attribute of PF.
You can create types and then use them in some or all of your application definitions. TURNOVER
for iSeries v100 will use the command you specify, even a command you yourself may have written.
Substitution variables provide a way for TURNOVER for iSeries v100 to know what fields the
command expects to be passed during the TURNOVER for iSeries v100 run.
It is useful to consider that three categories of type codes are possible:
Source-only types such as text source members and copy books (see TXT type).
Object-only types which will always be duplicated or moved into production. For these types, the
associated command has no source reference (see DTAARA type). Object-only types without
a command specified can only be moved or duplicated from test to production.
Source-created object types
Any object created using a create command, or moved or duplicated into production along
with the source member from which the object was created (see RPG type).
Page 8-12
TURNOVER for iSeries v100 also recognizes special types related to some case tools.
Supplemental documentation that describes when these apply is available.
Some restrictions apply to the TURNOVER for iSeries v100 methods permitted to each of the
above.
TURNOVER for iSeries v100 Method
Source
Only
CS Copy Source
Source
Compiled
Object
Only
MO Move Object
NULL No action
For more information about how each object type is promoted by TURNOVER for iSeries v100, see
the TURNOVER for iSeries v100 Supplement entitled The TURNOVER for iSeries v100
Change Process (#14).
The Sequence field is used when sorting objects on a form into the correct logical order. For
example, all PFs precede LFs that precede DSPFs... and so on. If you enter objects on a form out of
order, TURNOVER for iSeries v100 will give you a warning message. You can resequence them
quickly with a command key.
The Create command and default parameters entered here will be used when creating an object or
transferring this object type to production. Similar to the way you can code user defined options in
PDM, the substitution parameters appearing below the command line can be used wherever
appropriate in the command.
Page 8-13
An example is:
CRTCBLPGM PGM(&LI/&OB) SRCFILE(&SL/&SF) SRCMBR(&SM)
Where &LI
&OB
&TY
= Type code
&SL
&SF
&SM
&TO
&TL
&TR
= Target release
&FM
&FF
&FL
If the command line is blank and the object type (above) is not *SRC, only TURNOVER for
iSeries v100 methods MO or CD will be allowed for this object type.
(See How does TURNOVER for iSeries v100 resolve the create command? on page 8-16.)
F4=Prompt
Enter a command name and press F4 to prompt the command. When entering the & variables,
surround each one with a double quote.
Page 8-14
In this instance, &U3 is a user-defined parameter. It can be anything you define it to be; in this case,
the ALWRTVSRC parameter with value of *YES or *NO, depending on the default setting on the
user-defined parameter panel, as illustrated below.
1/29/10
19:34:27
User-defined Parameters
2=Change
_
_
_
_
_
_
_
_
_
_
User
parm
&U0
&U1
&U2
&U3
&U4
&U5
&U6
&U7
&U8
&U9
F3=Exit
4=Delete
Description
________________________________
Generation options______________
Replace program ________________
Allow retrieve source___________
User profile____________________
________________________________
________________________________
________________________________
________________________________
________________________________
Keyword
Default
__________ ________________________
GENOPT____ ________________________
REPLACE___ *NO_____________________
ALWRTVSRC_ *NO_____________________
USRPRF____ *USER___________________
__________ ________________________
__________ ________________________
__________ ________________________
__________ ________________________
__________ ________________________
F12=Cancel
In this example, weve defined four user-defined parameters. As you can see, you can assign any
parameter you want to each of the ten user variables. Also, its not necessary to use all of them and
you can leave gaps. Notice that we left &U0 unassigned.
Page 8-15
Assume, you are running a two level application, one with a QA library and one with a Production
library. When you promote to level one, you may want objects to be created with the ALWRTVSRC
parameter set to *YES. Later, when you promote to production, you may want to set it to *NO.
Once you define a user-defined parameter, you can set it differently for each application and level.
For more about using these user-defined parameters, see Chapter 1: Working with Application
Definitions.
How does TURNOVER for iSeries v100 resolve the create command?
When TURNOVER for iSeries v100 promotes an object, the resolution of the create command
substitution parameters proceeds as illustrated below.
TURNOVER for iSeries
v100 Program
Get
command
1. Retrieve command
CRTRPGPGM PGM(&OB)
GENOPT(&U3)
Page 8-16
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
Y
N
*CURRENT
*JOBD
*LIBL
*JOBD
*LIBL
V5R1M0
*NONE
*LIBL
TURRNSTD
*LIBL
Y
Y
Y
N
F12=Cancel
*SAME, Y, N
*SAME, Y, N
Name, *SBMJOB, *CURRENT...
Name, *SAME, *JOBD
Name, *LIBL
Name, *SAME, *JOBD
Name, *LIBL
Character value
Name, *SAME, *NONE
Name, *LIBL
Name, *SAME, *NONE
Name, *LIBL
*SAME, Y, N
*SAME, Y, N
*SAME, Y, N
*SAME, Y, N
More...
F13=How to use this display
Page down...
Set Global Defaults (SETGLOBE)
Type choices, press Enter.
Use Delete Test Object rule .
Company name . . . . . . . . .
Specify method of distribution
IFS Adopted authority user . .
QNTC Adopted authority user .
IFS Archive subdirectory . . .
Source archive file . . . . .
Library name . . . . . . . .
Automatic form lock checking .
Allocate form locks . . . . .
Reference objects library . .
F3=Exit
F4=Prompt
F24=More keys
*SAME, Y, N
. > Y
. > 'Your Company'
*SAME, *FORM, *DISTRIB
> *DISTRIB
Name, *SAME, *CURRENT
. > TURNIFS
Name, *SAME, *CURRENT
. > TURNIFS
Character value
. > ARCHIVEABC
Name, *SAME
. > ARCHIVE
. >
ARCHIVELIB Name
*SAME, *NONE, *FILE, *DTAOBJ
. > *FILE
*SAME, Y, N
. > Y
Name, *SAME, *TURNOVER
. > *TURNOVER
F5=Refresh
F12=Cancel
Bottom
F13=How to use this display
This option gives you access to global parameters that control how TURNOVER for iSeries v100
runs on your computer.
Page 8-17
Page 8-18
49 See the topic Form Copy and Object Delete Rules in the TURNOVER for iSeries v100 Supplement entitled The TURNOVER for iSeries v100
Change Process (#14).
Page 8-19
If you are managing IFS objects using TURNOVER for iSeries v100, you must supply the
name of a specifically configured user profile to be used for creating objects in IFS directories
during promotion. For information about this parameter and about the requirements for the
user profile, see the Managing IFS Objects using TURNOVER for iSeries v100 guide.
QNTC Adopted authority user (QNTCUSER)
The user profile whose authority you want TURNOVER for iSeries v100 to use when
checking out or promoting IFS objects from the /QNTC file system. You must create this
profile or use an existing one. The profile must have enough authority to copy, move, or
delete any IFS objects being managed by TURNOVER for iSeries v100.
IFS Archive subdirectory (IFSARCHIVE)
The subdirectory name you supply here is used as the default archive subdirectory for IFS
objects, if *DEFAULT is specified at the application level. For more information about IFS
archiving, see the Managing IFS Objects Using TURNOVER for iSeries v100 guide.
Source archive file / Library name (SRCARCFIL)
The values you supply for this parameter identify an archive file and library name to be used
for archiving files. TURNOVER for iSeries v100 can archive all applications to one file
specified here, or you can specify different archive files and libraries for different applications
(or application levels).
Automatic form lock checking (AUTOLOCK)
Use this parameter to have TURNOVER for iSeries v100 check for locks, either on files
only (*FILES) or on all data objects (Data object field is set to Y in the type code definition),
before replacing such objects during a form run. Use *NONE to disable automatic lock
checking. This default setting applies to each individual form. You can manually override
this setting before running the form.
Allocate form locks (ALLOCATE)
If Y, TURNOVER for iSeries v100 will keep the allocation on the object for the entire form
run. If N, TURNOVER for iSeries v100 will only keep the lock on the object at the very
beginning of the form job; just long enough to determine that no one is using the object at that
moment. Once TURNOVER for iSeries v100 determines that no one is using the object, it
releases all locks on the object and the form processing begins. This default setting applies to
each individual form. You can manually override this setting before running the form.
Reference objects library (REFOBJLIB)
The name of the library that contains the reference objects that TURNOVER for iSeries
v100 duplicates when creating missing objects for an application. If you specify
*TURNOVER, TURNOVER for iSeries v100 duplicates the reference objects from the
TURNOVER for iSeries v100 product library.
Page 8-20
Version/Install History
F12=Cancel
Installation
What was
Applied
Changes
Ver 100
Changes
Changes
Changes
Changes
Changes
Changes
Changes
Changes
Changes
Changes
-------------------Type
D
D
D
D
D
D
D
D
D
D
D
D
OS/400
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
5 3.0
More...
F21=System command
Before calling for technical support, know your TURNOVER for iSeries v100 Cumulative Change
Date. This will help us assist you more quickly.
50 Obtain the same information from the TURNOVER for iSeries v100 Client or plug-ins using Administration > Utilities ` TURNOVER for
iSeries v100 Version/Install History.
Page 8-21
1
2
3
4
5
8
9
10
11
12
13
14
15
16
19
F3=Exit
Description
Active
Form Finalization Processing
N
Pre-Distribution Form Exit
Y
Pre-Distribution Library Exit
Y
Receive of Distribution
Y
Determining Source file names
Y
Form Initialization phase
Y
Post-Checkout Exit
Y
Manual check-in
N
Form Completion Processing
N
Add a line to TurnOver form
N
Pre-run Error check Exit
N
Pre-Checkout Processing
N
Add PWL Item
N
Form Approval
Y
Pre-Form Group Exit
Y
F8=IFS Exits
F12=Cancel
Library
TOEXIT2UDR DXDDG
TOEXIT3UDR DXDDG
TOEXIT4UDR DXDDG
*LIBL
TOEXIT8RAY SMITH
TPDWX9
SMITH
SNDEXIT12
RICHARDS
TOEXIT15AC FRPROD
TOEXIT16
SMITH
LGEXIT19
RICHARDS
Library
List
*APPL
*CURRENT
*APPL
*CURRENT
More...
F21=Command line
Page down
1/29/10
11:27:38
Description
Active Program
Post Form Group Exit
N
Post-Receive Exit
Y
Post Add-Line Exit
Y
TPDWX22
Create Change Impact File
N
EXIT23
Related Forms Creation
N
Pre-Save - Rmt Cfg Wizard
Y
Post-Receive - Rmt Cfg Wizard
N
Form confirmation
N
Conflict resolution
N
Lock Check Exit
Y
Change Checkout Exit
N
Application Pre-Checkin Exit
N
Create Command Replacement Var N
Timesheet Exit
N
Escalation Blackout Date/Time
Y
Library
Library
List
*CURRENT
SMITH
PHILLIPS
*CURRENT
More...
F3=Exit
Page 8-22
F8=IFS Exits
F12=Cancel
F21=Command line
Page down
1/29/10
11:27:39
_
_
_
_
Exit
PROJ
PROJ
PROJ
XREF
03
04
05
01
Description
Escalation Blackout Item
Task Authorization
Task Validation
X-Ref Exit 1 - RPG Source Scan
Active Program
Y
___________
N
___________
N
___________
N
___________
Library
___________
___________
___________
___________
Library
List
Bottom
F3=Exit F8=IFS Exits F12=Cancel F21=Command line
You can select option 5=Browse exit program to see the source for that program exit.
TURNOVER for iSeries v100 looks at the object description to find the source member used to
create the program object.
If you want to see the sample program supplied by UNICOM Systems, Inc., you can select option
7=Work with sample exits to see the source for that exit program.
Complete Help text describes each exit; read this by selecting 8=Help. The help describes when the
exit is used, the required parameters, and in most cases provides an example of how it might be used.
Press F8 to display the TURNOVER for iSeries v100 IFS exit programs. For more information, see
the Managing IFS Objects Using TURNOVER for iSeries v100 guide.
F1 from any field shows you broader information about exits in general.
UNICOM Systems, Inc. Caution!
Keep in mind that, once an exit is defined, it is called for all applications. The program will be called
immediately after you make the change on this panel. Therefore, if the exit applies only to one or a
few applications, it must be coded to bypass processing for applications for which it does not apply.
Page 8-23
Page 8-24
1. You can set up a scheduled job to perform this function. If you want to do so, we recommend
using the SAVARSBM command described in the TURNOVER for iSeries v100 Supplement
entitled TURNOVER for iSeries v100 Commands (#28).
2. The SAVARCO command does NOT save archived explode libraries. To do this, use
SAVARSBM.
The SAVARCO (Save Archive Object) command can be run from the Utility Menu (option 9 or
from a command line).
Submit Object Archive Save (SAVARCO)
Type choices, press Enter.
Form . . .
From date
To date .
Volume . .
Device . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
0_____
000000
999999
______
__________
F5=Refresh
F12=Cancel
number, 0=Select
Date, 000000
Date, 999999
Character value
Character value
Bottom
F13=How to use this display
Type the device name and (first) volume serial number you intend to use to save the archived objects,
and press Enter.
Page 8-25
You can select a specific form number or a date-range of form run dates, such as all forms that ran
between 01/01/09 and 01/31/09.
1/29/10
16:35:26
Form selected
Date range selected
Save device/volume
0/00/00 to 99/99/99
TAP01
SLS533
4=Delete
_
_
5=Display 9=Save
Archive Run
Form
Library Date
200005
T0200005D
200008
T0200008D
F3=Exit
Save
Date
Save
Volume
1/28/09
12/01/09
F12=Cancel
Type 9 next to those object archive libraries that you want to save off-line and press Enter.
TURNOVER for iSeries v100 will submit a job.
Type 5 next to a form number to display the contents of the object archive library.
Type 4 next to a form number to delete the object archive library. Make sure you save it first!
Page 8-26
__
__
__
__
200001
200004
200005
200008
Form
Description
Changes to check-writer
Revise TO purge program
Fix program SMASOLDA
Emergency Change TURSONFF
Saved
Library Date
T0200001D
T0200004D
T0200005D
T0200008D
Save
Save
Volume
1/02/91 VOL3
1/02/91 VOL1
1/02/91 VOL3
1/02/91 VOL3
F3=Exit F12=Cancel
This panel provides a list of all of the object archive libraries that have been saved and deleted from
your system using the SAVARCO or SAVARSBM commands. It provides you with a directory of
volume serial numbers on which the archive libraries were saved, in case you have to restore these at
any time in the future. To restore any of these object libraries select option 1=Restore.
Page 8-27
Source
Source
Source
Source
Source
Source
File
Library
Member
File
Library
Member
F3=Exit
F4=Prompt command
F12=Cancel
TURNOVER for iSeries v100 is shipped with this command set to TURNOVER for iSeries
v100s own source compare command, CMPSRCMBR. You may use any other source compare
product, if you prefer one you have already been using. Note that this command is also used by the
TURNOVER for iSeries v100 Synchronizer system.
Type the source compare command and substitution variables just as they are displayed on this panel.
Once established, the command parameter enables the source compare option SC on Form
Maintenance, Work with Forms, and other panels as a user-defined option.
Emergency change applications use the source compare utility defined here to print a source compare
of the emergency change against the checked out source and the production source.
Page 8-28
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Y
*USRPRF
*JOBD
*JOBD
*APP
N
*BATCH, *INTER
*SYSAUTH, *DEVELOP,
*CHECKOUT
Y, N
*USRPRF, name
Library name
*JOBD, name
Library name
*PGMR, *JOBD, name
Library name
*APP, *CURRENT
Y, N
Lock (Y/N)
N
N
N
N
N
N
N
N
N
N
N
More...
F3=Exit
F12=Cancel
Page down
1/29/10
14:19:54
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
TUSROPTF
*LIBL
*TOP
N
*OBJECT, *LIBRARY,
*TYPE, *CRTSEQ
File name
Library name
*TOP, *ITEM
Y, N
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
N
Y
*ALL
N
Y
Y, N
Y, N
*SELECTED, *ALL
Y, N
Y, N
.
.
.
.
.
.
.
.
.
.
.
.
Lock (Y/N)
N
N
N
N
N
N
N
N
N
N
Bottom
F3=Exit
F12=Cancel
Page 8-29
3=Copy
Convert
From Type
RPG
RPG
4=Delete
Convert
To Type
RPGLE
RPGMOD
5=Display
Delete
Type
RPGCPY
RPGCPY
Check
Out
Copy
Y
N
Y
N
Conversion Command
CVTRPGSRC FROMFILE("&PL"/ . . .
CVTRPGSRC FROMFILE("&PL"/ . . .
Bottom
F3=Exit
F6=Add
F12=Cancel
F21=System command
As shown here, the conversion table comes with two initial entries:
This section describes the actions you can perform on entries in the Type Code Conversion Table.
Descriptions of the fields in the Type Code Conversion Table Entry panels are provided; also refer to
the online Help.
Page 8-30
Page 8-31
Adding an entry
To create an entry in the Type Code Conversion Table, press F6 on the Work with Type Code
Conversion Table panel. The Add Type Code Conversion Table Entry panel appears:
1/29/10
13:31:23
.
.
.
.
.
.
.
.
.
.
.
.
. Y
. N
.
Conversion command . . .
F4=Prompt
The following substitution parameters may be used in the conversion command:
"&PF" = Production source file
"&PL" = Production source library
"&PM" = Production source member
F3=Exit
F4=Prompt
F12=Cancel
F21=System command
The fields in the Add Type Code Conversion Table Entry panel are the same fields that appear in the
panels for changing, copying, and displaying an entry. In those three panels, however, the fields are
filled in.
To add a new conversion table entry, enter values for the following fields:
What you see:
Convert or supply from type
Type the TURNOVER for iSeries v100 type code that is to be converted (for example,
RPG). This type code must exist at the global level and at each level of the application
definition (including permanently locked levels).
Convert or supply to type
Type the new TURNOVER for iSeries v100 type code to which the object will be converted
(for example, RPGLE). This type code must exist at the global level and at each level of the
application definition (including permanently locked levels).
Checkout
Indicate whether the object should be checked out when the TCVTOBJTYP utility is run. Y
checks out the object; N does not check out the object.
Page 8-32
Use N if the conversion command will create the source member in development. In this case,
it may not be necessary to copy the source during checkout.
Use Y if you have a conversion utility that converts source in place, rather than converting
source from one source member into another source member. For example, if your company
has a policy that every time an RPG member is checked out it will be converted to RPGLE,
you would make QRPGLESRC the development source file for the RPG type code. The
TCVTOBJTYP utility would then copy from QRPGSRC in production to QRPGLESRC in
development when the object is checked out, and the conversion command would convert the
copied source in place.
Type code to delete
Type the type code that will be used to delete the obsolete source member once the object has
been converted (for example, the RPG member that was converted). In most cases, you will
have defined RPGCPY as the type code to delete, but your company may use some other
RPXXXX type code to designate a source-only type for RPG members.
If you type a type code here, a D delete line is added to the highest unlocked level
(Production) TURNOVER for iSeries v100 form to delete the old source.
If you leave this field blank, a line is NOT added to the form for the highest unlocked level
(Production).
If you type a type code, it must be a *SRC (source-only) type code, and the type code
must be defined to each level of the application definition.
If for some reason the highest unlocked level (Production) form, once it is created, is
cancelled and re-created, the D delete line is not automatically added to the new form.
Youll have to manually create the D delete line.
Conversion command
Type the command that should be executed to convert the source from one type to another (for
example, CVTRPGSRC). You can include the substitution parameters that appear on the
panel in the command string.
Page 8-33
Changing an entry
You can change an entry in the Type Code Conversion Table. In the Work with Type Code
Conversion Table panel, select the entry you want to change with option 2. The Change Type Code
Conversion Table Entry panel appears:
1/29/10
13:46:56
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
RPG
RPGLE
Y
N
RPGCPY
Y, N
Y, N
TurnOver/iSeries type code
F4=Prompt
F12=Cancel
F21=System command
Copying an entry
You can duplicate an entry in the Type Code Conversion Table to create a new entry. In the Work
with Type Code Conversion Table panel, select the entry you want to copy with option 3. The Add
Type Code Conversion Table Entry panel appears, with all the fields filled in for the entry you
selected. You can then modify the field contents as you want.
Deleting an entry
You can delete an entry from the Type Code Conversion Table. In the Work with Type Code
Conversion Table panel, select the entry you want to delete with option 4. The Work with Type Code
Conversion Table panel reappears, with the entry you selected removed. A message appears at the
bottom of the panel, notifying you that the entry was deleted.
Displaying an entry
You can display an entry in the Type Code Conversion Table. In the Work with Type Code
Conversion Table panel, select the option you want to display with option 5. The Display Type Code
Conversion Table Entry panel appears, with all the fields filled in for the entry you selected.
Page 8-34
Enter a value for the Type code to delete parameter in the conversion table entry. As long as the
highest unlocked level of the application being used is set to archive source on line, TURNOVER
for iSeries v100 will archive the old source member.
Page 8-35
Utility Menu
Select
Save IFS Archive Directory
Type choices, press Enter.
Volume . . . . . . .
Device . . . . . . .
Archive subdirectory
Clear subdirectory .
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
F4=List
Y, N
F4=Select subdirectory
F12=Cancel
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F21=System command
After you enter the command parameters, TURNOVER for iSeries v100 submits your archive save
job to batch. For more information, see the Managing IFS Objects Using TURNOVER for iSeries
v100 guide.
Page 8-36
Page 8-37
AN
Wisedesk
Work with
Requesters
Enter
Problem
(FASTTASK)
Review
Assign
Problem
(WORKTASK)
Work with
Projects
Reporting
Work with
Tasks
Timesheet
Work w/
Escalation
Queue
Search
Change
Tasks
Add Tasks
Other Change
Mgmt
functions...
Programmers
Worklist
Task
Details
Figure 1
This panel map summarizes the main elements and flow of the Helpdesk and project subsystems of
TURNOVER for iSeries v100 Projects. Reading from top left to bottom right, you can see that the
entire change process is addressed, from identifying the person making a request, entering a request or
problem through programming and promotion, as supported by the Programmers Worklist function.
TURNOVER for iSeries v100 2005-2010 UNICOM Systems, Inc.
Jul-10
Page 9-1
With TURNOVER for iSeries v100 Projects, authorized users or Helpdesk personnel can enter
requests and problems directly, and track them as they make their way through your system. At the
same time, you can limit user access to only those capabilities and projects you want them to see.
Automatic escalation and messaging, based on rules you define, ensure that a project coordinator and
programmer are informed of high-priority problems as soon as they enter the system. Text masks that
you can define help you collect descriptive details you need in order to respond to the request or
problem. Help trees, which you can use from several points of view, let you answer user questions
about your product; identify duplicate requests and problems; and locate related, pre-existing tasks in
any of your projects. Once assigned a task, your programmer can work from one panel (the
Programmers Worklist) to complete all phases of testing and development.
A request or problem in fact any task can be entered at any stage, by a Helpdesk person, by an
authorized end-user, and by information system personnel.
Another way to look at TURNOVER for iSeries v100 Projects is to consider the different user
interfaces that have been provided to support these different user perspectives, as illustrated in Figure
2.
Page 9-2
Wisedesk
HELPDESK==>
Helpdesk View
Work with
Requesters
Problem
Details
Add
Problem or
Request
FASTTASK:
Work with
Projects
FASTTASK==>
WRKESCQ==>
WORKTASK==>
TURNOVER 9==>
Manage a
user base
User Entry
View
Coordinators View
Work with
Escalation
Queue
WORKTASK:
Work with
Projects
Work with
Projects
Work with Tasks
----------------------
STRPWM==>
STRPWM Listname==>
Work with
Programmer
Worklists
Developers View
Programmer
Worklist
---------------
Figure 2
Page 9-3
Project Views
Figure 2 shows the various views or perspectives supported by TURNOVER for iSeries v100
Projects.
Helpdesk personnel normally work from the perspective of the requester (or customer). Using
TURNOVER for iSeries v100 Projects, this person can look up a requester by first name, last
name, company name, and phone number; check the status of outstanding requests for a requester
or his/her company or department; search for answers using Wisedesk; and enter new problems or
requests quickly using the FASTTASK command.
Authorized Users can enter problems directly into the system using the FASTTASK command
(or an equivalent menu option). They can also look up previously entered requests to learn their
current status.
A project coordinator can review all pending requests (entered since the last time requests were
reviewed) or review pending requests and problems, using the escalation queue.
Project leaders and programmers can manage their own Working projects that is, those
projects to which the Coordinator assigns requests and problems as Working tasks.
Assigned programmers can then use the Programmer Worklist to complete their assignments.
51 For more information, see the TURNOVER for iSeries v100 Application Planning Guide.
Page 9-4
Filters--
View Task
Add/Change
Requesters
----------------------
F6/2
F2
View Related
Tasks
Work with Tasks
for Requester
12
----------------------
Wisedesk:
Filters--
Work with
Help Trees
FASTTASK:
Enter Requests
or Problems
Work with
Escalation Queue
----------------------
Figure 3
Identifying a requester
On a Helpdesk, responding to a problem or request starts with knowing to whom you are talking. In
TURNOVER for iSeries v100 Projects, you the Helpdesk staff member can use the
HELPDESK command to look up a requester by name, company name, location, or phone number.
(For example, you may want to see all of the people at a certain company or department.) There are
also several user-defined fields for special use in the requester file that you can use to filter the list. If
authorized, you can add new requesters to the file or update requester information.
Page 9-5
Before entering a new request or problem, you might want to see if someone has already requested or
reported something identical or related. Using Wisedesk, you can search all the projects on your
system for existing tasks that describe the problem or request you want to report. Sometimes, youll
be able to add information to existing tasks without creating a new task. And if its a problem thats
been fixed, youll be able to tell the requester how to correct it.
Entering requests or problems
Once youve determined that a problem or request is not a duplicate, you can create a new task in the
appropriate Helpdesk project. When problems are entered by, or on behalf of, a person in the
Requester file, a list of Helpdesk Projects appears, defaulting to the last project for which the
Requester reported a problem or made a request.
Handling inquiries about previously reported problems
Besides being able to look-up and review problems that were reported earlier on the requesters
behalf, you (the Helpdesk person) can view all of the Working tasks related to the FASTTASK
request. For example, suppose a user reported a problem that impacts both the AR and AP projects.
As a result, the Project Coordinator created and assigned two Working tasks. You can then view the
status of both of these assigned tasks and review the details for each, if necessary.
If no action took place, you can look up on the escalation queue all of the tasks for that requester to
determine when action is scheduled to take place. If necessary, and assuming you are authorized to
change the queue, you might change the wake-up date and time of the queue entry.
Helpdesk Projects and Working Projects
When you create a project entry, you tell TURNOVER for iSeries v100 whether the project you are
defining is to be a Helpdesk project or a Working project. All projects share the same database, but a
Helpdesk project includes additional default values used to manage a Helpdesk. For example, the
project definition designates the Project coordinator that is, the person who reviews requests and
problems and assigns them to Working project teams or programmers.
Page 9-6
View Assigned
Tasks
Details
Add a Request
or Problem F5
Work with
Requests
or Problems Filters-F6
F5=Details
F2
Wisedesk:
25
2/5
Work with
Categories for
Task
Escalation
Queue
View or Change
Requests and
Problems
Text Search
Figure 4
Entering problems
An authorized user or a Helpdesk person can directly enter problems and tasks into TURNOVER
for iSeries v100 Projects by selecting the appropriate Helpdesk project and then completing the Enter
a Problem/Request panels. If the Helpdesk person is authorized, s/he can also review and assign the
request (see Working with WORKTASK on page 9-54).
Page 9-7
If an authorized user is entering a problem or request on your system, the user is prompted first for
data about the request, and then to describe the request further on a text panel. This text panel can be
set up as a mask, to prompt the user for specific information or to supply instructions. More than one
mask can be associated with a project. For example, if your Helpdesk project is Hardware
Problems, then you can have a mask for printer problems, PC problems, display problems, and so
forth. The user selects the appropriate mask and then describes the problem. If the user is authorized
to do so, s/he can review and assign the task immediately by pressing F2=Assign.
Looking up problems/requests
After a problem has been entered, the user or Helpdesk person can look it up and view the current
status of the original problem or the assigned task(s) on line. Filtering and text searches can be done
to quickly find previously entered problems. Wisedesk can be checked to see and work with how a
task fits into the categories defined there. Users can change or delete a request they entered any time
before the Project Coordinator reviews it.
Escalation queue
Each time a request is entered or changed, TURNOVER for iSeries v100 checks the project
escalation rules and values changed (such as due date) to determine whether or not to add or change
an escalation queue entry. When the wake-up time is reached, the escalation queue triggers
processing, such as automatically advancing the task status or priority. See Task escalation
processing on page 9-77.
Tracking and Working with Tasks
Once a request or problem (referred to here generally as a task) is entered, an authorized Requester,
Helpdesk person, or authorized systems person can track the request at each stage of the process,
without calling you. S/he can also view text details that have been entered and see the current task
status.
TURNOVER for iSeries v100 Projects provides messaging, work-with panels and reports to help
keep everyone informed. You can generate reports of project and task information in several different
useful formats. Each standard report is initiated using report commands that allow you to specify
what information you want to see, and whether you want information summarized or in detail. With
the task report generator the Report Masks feature you can generate a fax (if you have a machine
connected to your iSeries) or other output format easily. With TURNOVER for iSeries v100
Projects, you can produce a fax document to send to your customers or users, when a problem is
solved or a task completed.
Page 9-8
Coordinators View
WORKTASK:
Work with
Requests and
Problems
Change or View
a Task
Work with
Escalation
Queue
Work with
Pending
Requests and Filters-Problems
F2
1
Task Details
11
Escalation
Queue
12
Review
Requests
Work with
Assigned
Tasks
Filters--
1=Append Request or
Problem
F2
F16
Assign to
Working
Projects
23,
24
Work with
Category Tasks
Work with
Categories
WISEDESK:
Work with
Help Trees
Send Messages
To:
Requester
Assigned Resource
Edit Details
Assign
Resource
Figure 5
Page 9-9
You, or someone in your organization, will be designated the Project Coordinator for any Helpdesk
project you define. To review new problems and requests, the coordinator uses the WORKTASK
command (or equivalent menu option). As a Coordinator, you would periodically review all pending
problems and requests to assign, defer or reject them. You can either process all pending requests,
one by one (option 2), or do so selectively, either by referring to the escalation queue (option 1) or the
list of requests and problems (option 5) and assigning particular items in the list.
Using the escalation queue
As the Project Coordinator, you can set up the escalation queue to sequence pending requests by
priority or some other relevant criterion. This way, you can assign the most important requests first.
Escalation Rules
When you define a project, you can specify escalation rules. These rules are based on the value of
priority and status codes for a task. For example, you can establish a rule that a request with a status
of New and a high priority be reviewed within four hours. The escalation rules define a Wake-up
interval a time at which some action is to occur and Actions, such as send a reminder message or
change the task status. In fact, you can even write your own program to be called under conditions
defined in the escalation table.
Escalation Queue
Each time a problem or request is entered into the system for a project for which escalation rules are
defined, an entry is made in the escalation queue. The escalation queue entry contains a wake-up
time, which is a specific time at which some predefined action is to be taken. The queue entry is
changed or removed, depending on the requirements defined in the projects escalation rules.
Page 9-10
Before assigning a request or problem, you might want to see if a similar task has been reported and
assigned. If help trees have been created across the projects on your system, then you can use them to
check for a similar, identical, or related task that already exists in your projects, and either append the
task you are reviewing to the existing task, or assign it as a subtask to the existing task.
If you append the new request to that previously assigned task (or add it as a subtask), you establish a
link between the assigned task and the request or problem under review. You might also want to
update the assigned task details at that time. Later, when that assigned task is completed, all
originating requests can be viewed and, if appropriate, each of the requesters notified that the request
has been completed.
Searching for a Task
There are two ways to search your projects for duplicate or related tasks: manually, or using help
trees within Wisedesk. These are just the kind of features that make a Helpdesk person effective.
When you search manually, you can view the list of tasks by project, after youve started to assign the
task, using F4. You can filter the list by requester, resource, status or any number of other filter
values, including up to ten user-defined fields. Then you can search task text details using a powerful
text search capability (option 25). For example, one project may be Accounts Payable Problem
Reports with a task that describes a fix to a check-writing program. You can interactively search all
tasks for the word check and then print or view the resulting list. Once you locate a task, you can
view the task details. You can also view the list of program objects changed when the problem was
resolved.
Using Wisedesk, you can accomplish the same work, but more efficiently. To use Wisedesk, you
must have help trees set up on your system. Help trees are structures consisting of reasonable
categories and subcategories, into which the tasks from all the projects on your system are
sorted using specific search requirements that you supply. If you are using Wisedesk, problems
or requests reported by your users would be sorted and displayed using these logical categories,
making it easy to spot duplicate or related tasks during a search. And, if you do find a match,
its easy to handle the task youre reviewing whether you need to add it as a new task, link it
to an existing one, or explain to the requester how the problem or request has already been
dealt with.
Page 9-11
If your search reveals that the request is a new problem, you can then assign it to a Working project;
in fact, you can assign it to more than one project or task. For example, a request may impact both the
AP and the AR projects. The projects to which a particular problem or request can be assigned is
determined by F10=Valid projects within the *HELPDESK project-specific options parameter of
the Helpdesk Project definition. If you select more than one assignment project, TURNOVER for
iSeries v100 performs the assignment cycle once for each project.
You can update the assigned task to include the resource, time-estimates, start time, and so on. After
you complete the review, messages can be sent to the requester and assigned resource. You can set
these to be sent automatically, or you can have TURNOVER for iSeries v100 prompt you to edit
and send the message.
Requests are accepted and assigned, conditionally accepted, or rejected. Requests that are assigned
are copied to a Working project and assigned to a resource. The original request is preserved as the
user entered it. The assigned task is given to the programmer or other resource to be completed. That
programmers view of Projects is illustrated on the next page.
Page 9-12
F2
Change/View
Tasks
Work with
Tasks
Work with
Escalation
Queue
Filter s--
F20
F16
20
Search or View
Assigned Tasks
25
Escalation
Queue
15
Wisedesk:
View
Originating
Requests
Work with
Worklists
Work with
Help Trees
Filters--
Categories
1
Cat. Tasks
Programmer
Worklist
20
Filters-32
PDM
F2 0
F15 /
15
X-Ref DB
Pathfinder
Abstract/Probe
TURNO VER X-ref
SEU/SDA
CODE/400
FLEX/EDIT
Figure 6
Page 9-13
Once the Helpdesk project coordinator has reviewed and assigned a task to a Working project,
TURNOVER for iSeries v100 informs the project leader or developer to whom the task was
assigned.
As a developer, you then go to the Work with Tasks panel, select the assigned task, and build a
Programmer Worklist. A worklist is a list of the objects and source needed to complete the task.
You can access cross-reference files and view objects and source in PDM to add items to the list.
Once the list is complete, youll do all of your work from this Programmer Worklist Manager
(PWM) panel including things like checking out objects and source, building TURNOVER for
iSeries v100 forms, and running the forms to promote your work into the next application level.
Time reporting
If you are required to account for time spent on your project tasks, you can use the on-line timesheet
to enter and track your time. You can also create administrative projects to track time spent in
meetings, or sick time and holidays, and so on.
You can view the accumulated time reported for any project or task, no matter how many people have
reported time.
Page 9-14
Of course, at any time, you can view the list of objects and source members, and other important
information associated with a completed task or one in process.
Develop
QA
Prod
Promote
Promote
Distribute
Checkout
Figure 7
Analyze
Assign
Task
Check
out
Build
Worklist
Promote
to QA
Program
& Test
Promote
to Prod.
Distribute
Test in
QA
2
53 For more information, see the TURNOVER for iSeries v100 Application Planning Guide.
Page 9-15
Position to user . . .:
1=Application authority
2=Project authority
3=Wisedesk
4=Delete user
Source -------- FORMS --------- -- SYSTEM -- ----- PROJECTS ----Out In View Add Chg Run Dst Prg Dft Aut Pgmr Use Add Code Rsc Rqs
X
X
X X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
More...
F4=Add from List F6=Add User F12=Cancel F21=System command
User
*NONE
BARCLAY
COMPARDI
BIANCHA
BLAINE
ELMSMORE
GILBERT
RONNY
HOLMESBY
JSCHMIDT
2 KLINE
LELAND
F3=Exit
Use the set of columns labeled PROJECTS to specify for each user generic authorities for the project
management component of your TURNOVER for iSeries v100 system. An X in the Use column
gives the user basic authority to use the project system. The remaining columns are used to define
additional levels of project system authority; read the online help for more about these settings.
Assigning authority to groups of users
There are two ways to assign project authority to groups of TURNOVER for iSeries v100 users. If
you use group user profiles, you can assign project authority to the group profiles to avoid entering
each individual member of the group into TURNOVER for iSeries v100s authority list.
Assigning authority to individual users
If you dont use group profiles (the group profile parameter in the iSeries user profile is *NONE),
you can add a user called *NONE to the TURNOVER for iSeries v100 Authority List, assigning to
that user the project system authorities you want your individual users to have. Use caution though
this means that any user without a group profile will adopt the authority of the *NONE user upon
entering the project system.
Page 9-16
To work with user authority settings for a specific project, select one or more users with option 2.
When you press Enter, this panel appears:
1/29/10
11:24:02
Project
APPR
LANT
MKTG
MKTP
OVER
OEPR
F3=Exit
View
X
X
X
X
X
X
Add
Chg
Dlt
Rvw
X
X
X
X
X
X
X
X
F12=Cancel
This panel contains a list of all the projects defined to your TURNOVER for iSeries v100 projects
system. The list is arranged in alphabetical order by project ID. The user you selected on the
previous panel appears at the top of the panel. To work with this users authority for a project, use the
Page Up/Page down keys to position the panel to the desired project and type an X in the fields that
represent the kind of access you want the user to have for that project.
What you see:
Project
The four-character identifier assigned to the project.
Description
Text that explains the project ID.
definition.
View
The user can look at the information in the project definition, tasks or subtasks for the selected
project.
Add
The user can change information in the project definition, or in tasks and subtasks, for the
selected project.
Dlt
The user can delete the project definition for, or tasks and subtasks from, the selected project.
Rvw
If the selected project is a HELPDESK project, this user can review tasks for approval and
assign them to any WORKING project for which s/he has authority.
TURNOVER for iSeries v100 2005-2010 UNICOM Systems, Inc.
Jul-10
Page 9-17
Project . .
Task . .
Subtask .
Description
User
DELANEY
BERNARD
COMPARDI
BIANCHA
BLAIRE
ELSINORE
GILBERT
HOLMESBY
JSCHMIDT
F3=Exit
.
.
.
.
. DOC.
.
. Documentation projects
Name
Jim Delaney
Andrew Bernard
Joe Compardi
Biancha Paterson
Blair Edwards
Steve Elsinore
Gordon Gilbert
Bruce Holmesby
Jeanne Schmidt
F12=Cancel
View
X
X
X
X
X
X
X
X
Add
X
Chg
X
Dlt
X
Rvw
X
X
X
X
X
X
X
X
X
X
F21=Authorize all
Note: You can achieve the same results using option 2=Change next to the project and selecting
Authorized users on the Define the Project panel.
Type X in the appropriate columns and rows, or press F21 to authorize all users; type a space to
remove authorities.
Press F1/Help for a description of authority settings.
Page 9-18
11:04:12
Position to project . . . .
Filter by Administrator . .
Status
F4=List
1=Add task 2=Change 3=Copy 4=Delete 5=View 6=Print 7=Rename 9=View time
12=Work with tasks
14=Authority
16=Forms
17=Checkout 18=History
__
__
__
__
__
__
__
__
__
__
__
Proj
CENH
CMPR
PET
PHPT
PLOG
SE50
SLSO
SMI
SM5
SNEN
SP50
Description
CENTRAL for iMenu Enhancement Request
CENTRAL for iMenu Problem Reports
Product Evaluation
Physical plant changes
SLS Phone Log
SoftMenu 5.0 Enhancements
SLS Order System
SoftMenu Release 5.0 Installation Programs
SoftMenu Release 5.0
Serial Number Enhancements
SoftMenu 5.0 Problem Fixes
Administrator
TURNERJIM
ANDREWS
TURNERJIM
THOMASMA
TURNERJIM
TURNERJIM
TURNERJIM
ANDREWS
ANDREWS
ANDREWS
ANDREWS
Status
ASSIGNED
ONGOING
STARTED
ONGOING
ONGOING
ONGOING
ONGOING
ONGOING
ONGOING
ONGOING
ONGOING
More...
F7=Control files
Page 9-19
Page 9-20
17=Checkout
Type 17 to work with checkout history related to this project. This is equivalent to filtering by
project code on the View Checkout panel. (From there, press F11 to see checked out IFS
objects for this task.)
18=History
Type 18 next to a project to view object change history related for this project. This is
equivalent to filtering by the project code on the Work with Object History panel.
F2=Esc. queue
Press F2 to view the task escalation queue. See page 9-87 for more about the escalation
queue.
F4=List
Position to a Filter by ... field and press F4 to see list of acceptable values.
F7=Control Files
Press F7 to go to the Project Control Files Menu. For more information, see Working with
TURNOVER for iSeries v100 Projects Control Files on page 9-88.
F9=Actual time update
Press F9 to submit a job that updates (rolls-up) all the time reported by each resource into
subtask, task, and project records and changes the Actual duration of all tasks to this total.
TURNOVER for iSeries v100 automatically updates the time when you submit the Project
Report. However, if you have not recently run the Project Report, you must update the time
using F9 for all time to be reflected in the task and project records.
Note: By default, the Time Update function assumes an 8-hour work day, 40-hour work
week. Previously, you could override this default with the TDFTDAY and TDFTWEEK data
areas.
Your companys schedule might be a non-standard 7.5-hour work day, 37.5-hour work week.
TURNOVER for iSeries v100 provides two new data areas (TDFTDAYM and
TDFTWEEKM) to supersede the old data areas. These data areas let you specify the time
worked as a whole number in minutes, instead of having to round to the nearest hour.
Descriptions of these data areas follow:
TDFTDAYM
TDFTWEEKM
*DEC 7.0
*DEC 7.0
You must manually create these data areas in the SOFTTURND library. In these data areas,
for a 7.5-hour work day, you would specify 450 as the value for TDFTDAYM; for a 37.5-hour
work week, you would specify 2250 as the value for TDFTWEEKM. If none of the four data
areas exists, TURNOVER for iSeries v100 uses the default 8-hour work day, 40-hour work
week.
Page 9-21
F16=Wisedesk
Press F16 to start Wisedesk and go to the Work with Help Trees panel. You can use help
trees to search for information about problems, requests, or tasks and to add new tasks in
projects to which you are authorized.
F18=Timesheet
To enter time on the daily timesheet report. You will be prompted for a profile name and date
(default is your profile). Press Enter to report time for yourself for the current day. Alternate
path: use the TIMESHEET command.
F20=PWM
To work with your Programmer worklists.
F21=System command
To view and work with a command line.
Page 9-22
Your Company,Inc
SYSTEM: YOURSYS
ACTION: ADD
Project . . . . . TP40
Description . . . TURNOVER for iSeries v100 Problems Release 4.0
1=Select
Opt
1
1
1
1
1
1
1
1
1
1
F3=Exit
F12=Cancel
F21=System command
Each option represents a panel on which you supply information, guidelines and rules for your
project.
Type 1 next to each line and press Enter to view each of the definition panels.
The project definition panels are summarized here, and illustrated with additional detail on the
following pages.
Page 9-23
Page 9-24
The Project description panel contains fields, such as project description and Administrator name,
which describe the nature of the project youre defining. Refer to the online Help for a definition of
each field.
1/29/10 10:46:12
Project Description
Project . . . . . . . . .
Description . . . . . . .
________________
Status . . . . . . . . .
Priority range . . . . .
Project administrator . .
Auto assign task numbers
Audit project changes . .
Requester validation . .
Personality . . . . . . .
Escalation table . . . .
Details editor . . . . .
F1=Help F3=Exit
F4=List
. . . TP40
. . . TURNOVER for iSeries v100 Problems Release 4.0
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
O ONGOING
1 to 3
TURNOVER
Y
Y
*FILE
*WORKING
WORKPROJ
*TURNOVER
F12=Cancel
F4=List
name
Y=Yes, N=No, A=Aggressive
Y, N
name, *FILE, *USRPRF, *BOTH, *NONE
*WORKING, *HELPDESK
F4=List
*TURNOVER, *OFFICE, *SEU
F21=System command
On the Project Description panel, you can specify such things as the project name, valid priority
range for the project, whether or not task codes should be sequentially assigned automatically and
whether to audit changes to the project (record all changes in a project journal).
UNICOM Systems, Inc. Note
When naming a project, the only special characters you can use are: # $ @. Also, you cannot include
embedded blanks in project names.
The Project Administrator must either have a valid iSeries user ID, or exist in the Resource file.
The Requester validation field identifies the rules TURNOVER for iSeries v100 should use to
check the Requester field in a project task, problem report, or enhancement request. If your users
have profiles on your computer, the Requester validation can be set to *USRPRF or *BOTH. In the
first case, the requester must have a profile on the system; in the latter, s/he must have a profile and an
entry in TURNOVER for iSeries v100 Projects requester database. If you use the value *FILE,
TURNOVER for iSeries v100 Projects requires that the requester exist in the Requester file, but
does not require that requester ID to be a user profile on your system.
The Auto assign task numbers field determines if the task names are to be generated by
TURNOVER for iSeries v100 or keyed by you. If you type Y, then TURNOVER for iSeries v100
will generate sequential task numbers automatically, ranging from 0000 to 9999. If you type A, task
numbers are generated automatically AND they can range from 0000 to ZZZZ.
Page 9-25
You can associate an escalation table with the project. Escalation tables contain rules that control
when some automatic action should be triggered for a task, and they define that action that should
occur.
When you position to the Escalation table parameter and press F4=List, you will see the following
panel:
1/29/10 10:46:12
Project Description
Project . . . . . . . . . . . . TP40
Description . . . . . . . . . . TURNOVER for iSeries Problems Release 4.0____
_________________________________
Status . . . . . . . . . . . . O ONGOING
F4=List
Priority range . . . . . . . . 1 to 3
Project admin ................................................................
Auto assign t :
Select Escalation Table
:
Audit project : 1=Select
:
Requester val :
:
Personality . :
Table
Description
:
Escalation ta : _ FTPR
Queue created for project: FTPR
:
Details edito : _ HELP-PS
Test Helpdesk table
:
: _ HELPDESK
Escalation Table for Helpdesk Projects
:
: _ PAULHELP
Test queue for HELPDESK project
:
: _ WORK1
Test queue for WORKING project
:
: _ SLS
SoftLanding Internal Escalation Table
:
: _ TEST
Escalation Table for Testing
:
: _ TESTHELP
Test queue for HELPDESK project
:
:
More... :
F3=Exit F4=L : F2=Maintain tables
F3=Exit
F12=Cancel
:
:..............................................................:
Type 1 to select the escalation table you want to be applied to this project. Type F2 to work with the
escalation table.
For more information, see The escalation table on page 9-80.
Page 9-26
You can define several text detail masks and report masks to format task information in any number
of ways. Detail masks are used when entering text that describes the task (if the Details editor is set
to *TURNOVER). If you require detail masks, then you will see the mask or a list of masks from
which to choose, after entering the task data. You will fill in the text description according to the
format provided by the mask, and then exit. Report masks can be defined as well. Report masks can
be best thought of as text merge documents; virtually any data contained in the requester file or the
project and task files can be included on the report mask. For example, you could create a report
mask to create a fax of the task to be sent to a user, or a format to be handed to a programmer that
contains space for recording time spent on the task that would later be keyed using TURNOVER for
iSeries v100s TIMESHEET command.
Details editor
The Details editor parameter lets you choose between TURNOVER for iSeries v100s editor
(*TURNOVER), SEU (*SEU), or OfficeVision (*OFFICE) to edit task details. This field defaults
to *TURNOVER. Detail masks cannot be used if you use SEU or OfficeVision editor options. If
you choose *OFFICE, you will be prompted to specify a folder to be used for task descriptions. If
you specify *SEU, you will be prompted to specify a source physical file name to be used to store
project descriptions. For *OFFICE and *SEU, TURNOVER for iSeries v100 will generate
document or member names based on the project/task/subtask, unless a document or member name is
specified by the user.
The Initial status field determines the beginning status of new task and subtasks.
Project details
The Details option lets you provide a text description for your project.
1/29 /10 11:56:37
This is a sample p roject for assi gning HELPDESK request. It is a good ide a
to s et up special projects for as signing HELPDE SK requests.
You can, thus,
ensu re that User d efined fields a re the same fo r each project . When you ass ign
a HE LPDESK request the user defi ned fields sim ply map into t he same positi on,
assu ming they are defined in the project. So it's possible t o have nonsens ical
info rmation in the se fields, if y ou do not take the time to s ee that they
matc h.
Ther e are two repo rt masks set u p for this pro ject. One nor mal mask, and one
FAX mask. The FAX mask will auto matically fax a message to t he person in t he
requ ester field.
This of course assumes that you have an in tegrated FAX o n
your 400. The con trol instructio ns in this mas k are for FAX* STAR. If you h ave
a di fferent fax sy stem simply cha nge the contro l variables.
HINT: You must
ente r the fax numb er in the requ ester file EXA CTLY as the fa x system needs
to r eceive it. i. e. 1-603-924-85 08 or 9,1-603- 924-8508 etc..
******
EN D OF DOCUMENT
******
Bot tom
F3=E xit
F4=Delete line
F6=Inser t line
F12=C ancel
Page 9-27
You can specify up to ten user-defined fields for your project. The fields characteristics (alpha,
numeric, number of decimal places, valid values) are predefined in the Project Control File for Userdefined Fields (F7 from the Work with Projects panel). When you create or change your project, you
identify the predefined fields you want to associate with it and specify default values for them.
1/29/10 10:39:36
User-defined Fields
Project . . . . . . . . . . . . TP40
Default Value
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
F3=Exit
field
field
field
field
field
field
field
field
field
field
F4=List
1
2
3
4
5
6
7
8
9
10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F11=View 2
.
.
.
.
.
.
.
.
.
.
. SUBSYSTEM
. USR013
.
.
.
.
.
.
.
.
F12=Cancel
F4=List
F4=List
F4=List
F4=List
F4=List
F4=List
F4=List
F4=List
F4=List
F4=List
0
0
.00
.00
F21=System command
Only those fields you associate with your project here will appear on the Add a request, Add a task,
and Change a task panels, discussed starting on page 9-68. If you provide a default value, it appears
in the field when a new task is added to the project.
Page 9-28
When setting up user-defined fields, keep in mind how the tasks in your organization will flow. For
example, if you will be assigning tasks from a help desk project to a working project, then it makes
sense to keep the user-defined fields defined for both projects parallel. This is because any
information in a user-defined field of the help desk project is carried into the equivalent user-defined
field of the working task. If no equivalent user-defined field is defined there, the information is
dropped.
To select a value from a list of user-defined fields, position the cursor to a field with the desired
characteristics and press F4=List. A pop-up panel appears:
1/29/10 11:16:41
User-defined Fields
Project . . . . . . . . . . . . TP40
Default Value
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
field 1
field
field
field
field
field
field
field
field
field
. . . . .
F4=List
Select User-Defined Field
(Type *CHAR, Length 10)
1=Select
Field name
SUBSYSTEM
RESPONSE
ACCT
DOCCHG
DIV
METHOD
DOCUMENT
Description
Application subsystem
Method of response--Fax?
Account number
Doc. Change required?
Division
Method
Which document impacted?
More...
F2=Maintain
F3=Exit
F4=List
F11=View 2
F3=Exit
F12=Cancel
F12=Cancel
F21=System command
A list appears of all of the pre-defined fields that have the same characteristics as the field that you
chose (such as 10-character decimal).
To add a new field, press F2=Maintain (see Work with user-defined fields on page 9-95).
You then see a panel (not illustrated here) on which you can add new fields, specify a table of valid
values, create a field dependency, 55 or specify a user-written program with which TURNOVER for
iSeries v100 should validate the field contents. Using this approach you can define fields once and
use them in any number of your projects, ensuring consistency across all of your projects.
The field description is the field label that will actually appear on the Add and Change a Task panels.
Page 9-29
The second parameter varies depending on the type of the user-defined field you are
defining. It will either be a 10-character field, 25-character, 7,0 decimal, or 7,2
decimal, depending on the field type. Obviously, you couldnt have a single program
that handles all types of fields.
Your program will always be called by a CL program named TURCCUDP. If you
need to send back messages for some reason, send them to the *PRV program queue
of this program.
Generally your program should bring up some kind of list panel where the user can
select a valid value for the field, and should return that selection to the task.
2. Create your validation program. This program lets you verify that the user has
entered a valid value in the field. A validation program is called with the following
four parameters:
The 10-character name you have assigned to the field. (This is the name of the
validation program.)
The value for the user-defined field. Again, this varies depending on the field
type. (See the text for the F4 program, above.)
A 10-character value, which is the name of the program to which you want your
validation program (named in the first parameter above) to send error messages.
TurnOver passes this name to the validation program.
Note: TurnOver does not automatically send error messages. To have TurnOver
display a message on the screen during the validation process, you must issue a
SNDPGMMSG command to the program identified by this third parameter.
Page 9-30
Define one or more user-defined fields as keyword fields that must be entered when adding a request.
Then you will be able to filter on a field value when looking up tasks, or supply it as a search criterion
in Wisedesk when categorizing tasks in help trees. This greatly improves your ability to find
information without relying on text searches later on. For example, on our system at UNICOM
Systems, Inc., TURNOVER for iSeries v100 problems are categorized by Subsystem that is a userdefined field with a table of valid values that we defined in our own Helpdesk project. For example,
if we are looking for a problem and know that it had to do with Application definitions, we can filter
on the word Application and narrow the search to just a few tasks. This filter is available on all
Work with Tasks panels.
Valid applications
Use this panel to specify one or more valid applications for the project. You can specify more than
one application, but when you supply task defaults, youll have to choose one to specify as a default
application. For example, in the following panel, we have selected three valid applications for this
project; however, the entry TO 4 will be used as the default unless overridden wherever it applies.
1/29/10 11:08:47
Valid Applications
_
_
_
_
_
_
_
_
_
_
_
1
1
1
Appl
*ALL
*NONE
AP
AR
GL
HR
INV
SM
SM
SM
SM
TO
TO
TO
Rel
3
3
4
5
3
3
4
Ver
1
2
Description
All applications are valid
No application
Accounts payable
Accounts receivable
General ledger
Human resources application
Inventory application
SoftMenu Release 3.0
SoftMenu Release 3.5
SoftMenu Release 4.0
SoftMenu Release 5.0
TurnOver Release 3.1
TurnOver Release 3.2
TurnOver Release 4.0
More...
F3=Exit
F12=Cancel
F21=System command
Page 9-31
The object and source management subsystems of TURNOVER for iSeries v100 are closely
integrated with TURNOVER for iSeries v100 Projects. By specifying which applications can be
changed under the control of a project, you limit the chance of a programmer specifying the wrong
application during checkout or promotion. Think of it this way: When you get a problem or request,
what applications need to be changed to service the request? In our example, the project
TURNOVER for iSeries Problems Release 4.0 is very specific. We wouldnt include a SoftMenu
problem in this project (there would be another project for that product). However, previous releases
of TURNOVER for iSeries v100 might be affected; therefore they are included in our list as valid
applications.
Note that *ALL will include any new applications that might be created in the future. *NONE would
be appropriate if the project is to be used to track hardware problems or other non-software
applications.
If you are defining a *HELPDESK project, then you may decide not to specify *NONE. The
Helpdesk project is intended as a collection point for problems and requests. The application is not
assigned until the Project Coordinator reviews the request and assigns it to a *WORKING project
that has one or more valid applications associated with it.
UNICOM Systems, Inc. Recommends
In most organizations, it is appropriate and reasonable to select only one application for a project. It
is possible that you will have more than one application under the control of one project, but you will
find it easier to specify only one. If a task affects more than one application, copy the task and assign
it to the person most knowledgeable about that application.
Note that *NONE is also valid and might apply to a Helpdesk project or a Working project that is set
up for working on hardware problems.
Valid resources
1/29/10 11:16:18
Valid Resources
Resource
*ALL
BILL
CHRISTINE
CLARA
DAVIS
JON
JULIETTE
KERRI
LISA
RICH
ROB
SANDY
TINA
Description
All resources are valid
Bill C.
Christine P.
Clara G.
Davis B.
Jon S.
Juliette W.
Kerri C.
Lisa E.
Rich C.
Rob T.
Sandy L.
Tina T.
Bottom
F3=Exit
Page 9-32
F12=Cancel
F21=System command
When assigning a problem or request to a Working project, the project coordinator can assign it to a
specific resource. You may list those resources assigned to the project, if appropriate at your
company.
If you are defining a Helpdesk project, then you may decide not to specify any resource. The
Helpdesk project is intended to be a collection point for problems and requests. The resource is not
assigned until the Project coordinator reviews the request and assigns it to a *WORKING project, for
which valid resources are specified.
Valid status codes
1/29/10 15:00:55
1
1
1
Code
*ALL
A ASSIGNED
B DISTRIB
C CANCEL
D DONE
F FINISHED
H HOLD
K DUPLICAT
M CONFIRM
N NEW
O ONGOING
P IN-PROD
Q IN-QA
F3=Exit
Description
All status codes are valid
Request/Task has been assigned.
Task has been distributed
Has been canceled
The task has been completed
Task has been completed
On hold. Awaiting instructions.
The task is a duplicate of another
Task has been confirmed
A new request.
Project/task is on-going
Task has reached production
Task has reached QA
F12=Cancel
Allow as
Reference
Y
Y
N
N
N
Y
N
N
Y
Y
Y
Y
Update
Start
Date
N
N
N
N
N
N
N
N
N
N
N
N
Update
End
Date
N
N
N
Y
Y
N
N
Y
N
N
N
N
More...
F21=System command
The Status code table is defined once and applies to all your projects. However, for a particular
project, a subset of these valid status codes may be appropriate. For example, a *HELPDESK
project used to collect requests and problems might have these valid status codes assigned:
NEW
REVIEWED
ASSIGNED
HELD
REJECTED
CANCELLED
DONE
The *WORKING project to which problems can be assigned might have these valid status codes
assigned:
NEW
HELD
CANCELLED
CLOSED
STARTED
DONE
IN-QA
IN-PROD
Page 9-33
The Update start date and Update end date determine whether to automatically set the task start and
end dates when the task status is set to that value. For example, when you checkout an object, the
application you are working on can be set such that the task status is automatically set to S (Started).
The Update start date field for S Started is set to Y, so the Task start date will be set to todays date.
Task defaults
This panel defines the values that you want to appear automatically (that is, by default) in the fields of
new tasks or subtasks that users add to this project.
1/29/10 12:02:37
Task Defaults
Project . . . . . . . . . . . . TE40
Application . . . . . .
Release . . . . . . .
Version . . . . . . .
Resource . . . . . . .
Requestor . . . . . . .
Status . . . . . . . .
Status Transition Rules
Priority . . . . . . .
Task type . . . . . . .
Time units . . . . . .
Billable time . . . . .
Test data library . . .
Test object library . .
Test source library . .
F3=Exit
F4=List
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F12=Cancel
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
TO
4
0
*USRPRF
*USRPRF
N NEW
*NONE
1
A ASAP
H
Y
F4=List
F21=System command
You can override these defaults when you add or change the task.
If you are defining a *HELPDESK project, you might want to supply default values for Resource,
Requester, Priority, and Task type. (The other fields are for tracking change work, and are less
applicable to the problem reporting function of a Helpdesk project.) These fields carry information
forward to any *WORKING task to which the Helpdesk task is assigned.
For *WORKING projects, you might want to specify defaults for the Application fields, Status,
Time units, Billable time, and the Test library fields; this kind of information is more pertinent to
tracking the changes made to satisfy a request.
UNICOM Systems, Inc. Note
When you add or change a project, you can specify blanks as the defaults for the Priority and Task
type fields. Also, unless you use the Status Transition Rules field to associate a status transition rules
table with the project, you can specify a blank as the default for the Status field. (If you associate a
status transition rules table with the project, you must specify a default status code.) However, when
you add a task to the project, TURNOVER for iSeries v100 requires entries for the Status, Priority,
and Task type fields.
Page 9-34
If you decide to specify default test libraries, TURNOVER for iSeries v100 uses these library names
as defaults in the test library fields of new tasks. You can use specific library names; you can use
*PGMR, to use the library names from the TURNOVER for iSeries v100 programmer profile
(Main Menu option 2); or you can use *TASK, to build the library name from the project and
task/subtask IDs (for example, TE40011801). If the library does not exist, TURNOVER for iSeries
v100 creates it.
UNICOM Systems, Inc. Note
If your application definition is NOT set up to get the From library name from the Project record,
then TURNOVER for iSeries v100 will NOT check the Project task for the test library name.
However, TURNOVER for iSeries v100 will populate a new tasks test library fields with default
values specified on this panel, and will create libraries if they dont exist. But these libraries wont be
used when checking out and promoting objects for this task; the application libraries will be used
instead.
Authorized users
All users who have been enrolled in TURNOVER for iSeries v100 and have Work with Projects
level of authority will appear in this list.
1/29/10 11:57:24
Authorized Users
Name
View
Bill C.
X
Christine P.
X
Clara G.
X
Davis B.
X
Jon S.
X
Juliette W.
X
Kerri C.
X
Lisa E.
X
Security officer
X
Rich C.
X
Rob T.
X
Sandy L.
X
Tina T.
X
TURNOVER for iSeries Admin X
Add
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Chg
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Dlt
_
_
_
_
_
_
_
_
X
_
_
_
_
X
Rvw
_
_
_
_
_
_
_
_
X
_
_
_
_
X
Bottom
F3=Exit
F12=Cancel
F21=Authorize all
For more about authorization to TURNOVER for iSeries v100 Projects, see Authorizing users to
TURNOVER for iSeries v100 Projects topic on page 9-18.
View
View authority lets the user look at project, task, or subtask information for this project.
Add
Add authority lets the user create tasks or subtasks for this project.
Page 9-35
Change (Chg)
Change authority lets the user update task or subtask information for this project.
Delete (Dlt)
Delete authority lets the user remove a project, task, or subtask from the system.
Review (Rvw)
Review authority lets the user examine a Helpdesk task using WORKTASK, and assign it to a
*WORKING project (to which the person is authorized).
Personality defaults
The fields displayed here depend upon the value of the Personality parameter on the Project
Description panel. This example applies to a Personality of *WORKING.
1/29/10 10:59:16
Personality Defaults
Project . . . . . . . . . . . . TP40
Personality . . . . . . . . . . *WORKING
Details mask required . . . . . Y
Report mask required . . . . . Y
F3=Exit
Page 9-36
F4=List
F12=Cancel
Masks defined
Masks defined
1
3
F4=List
F4=List
F21=System command
The following example applies to a Personality of *HELPDESK. (See Creating a Helpdesk project
on page 9-38.)
1/29/10 11:02:14
Personality Defaults
Project . . . . . . . . . . . . FTRQ
Personality . . . . . . . . . . *HELPDESK
Details mask required . . . . . Y
Report mask required . . . . . Y
Task synonym
Accept status
Reject status
Review status
Coordinator .
F3=Exit
.
.
.
.
.
F4=List
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F12=Cancel
.
.
.
.
.
.
.
.
.
.
Masks defined
Masks defined
Request
X ACCEPTED
R REJECTED
V REVIEWED
BERMANJIM
F10=Valid Projects
1
3
F4=List
F4=List
F4=List
F4=List
F4=List
USRPRF
F21=System command
Page 9-37
Personality Defaults
Project . . . . . . . . . . . . FTRQ
Personality . . . . . . . . . . *HELPDESK
Details mask required . . . . . Y
Report mask required . . . . . Y
Task synonym
Accept status
Reject status
Review status
Coordinator .
F3=Exit
Page 9-38
.
.
.
.
.
F4=List
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F12=Cancel
.
.
.
.
.
.
.
.
.
.
Masks defined
Masks defined
Request
X ACCEPTED
R REJECTED
V REVIEWED
BERMANJIM
F10=Valid projects
1
3
F4=List
F4=List
F4=List
F4=List
F4=List
USRPRF
F21=System command
The information you type on this panel controls the problem entry and messaging functions. For
example, you can specify the profile name of the Project Coordinator. This might be a manager or
project leader who is responsible for reviewing and assigning (or rejecting) the problems and requests.
This person must either have a valid iSeries user ID or exist in the Requester file.
When assigned, the Helpdesk request displays the status of the task to which it has been assigned. If
conditionally accepted, the status is determined by the Accept status parameter. If it is rejected or
reviewed, then the Reject status and Review status parameters determine the setting of the task status.
When a problem or request is first entered, the coordinator can receive a message. Similarly, once the
coordinator has assigned the request, the requester and/or the assigned resource (usually the
programmer) can be sent a message automatically. Escalation table processing programs manage all
such messaging.
All projects have available the task escalation features that provide for automatic messaging and
updating of a task, upon entry and after a specified time-interval. For more information, see the Task
Escalation Processing topic on page 9-77.
Page 9-39
When you type FASTTASK on a command line or select the Add Problem/Request option on the
Work with Requesters panel, you will only see those projects that have been defined as HELPDESK
projects. Further, only those projects to which you are authorized will appear.
If you select a HELPDESK type project on the Work with Projects panel, you will then see the View
Request/Problems panel rather than the Work with Tasks panel. The Work with Tasks panel only
applies to Working projects, not Helpdesk projects.
Also, the functions controlled by the HELPDESK Personality defaults on the previous page are
available only for Helpdesk projects.
Press F1 for more about each of the fields on the panel.
Wisedesk dynamic update options
This panel is for specifying whether you want your Wisedesk categories to be updated whenever a
new task is entered into the project system.
1/29/10 11:43:39
F3=Exit
F12=Cancel
Y, N
F21=System command
To update your Wisedesk help trees each time a new task is created, type Y and press Enter.
For more about Wisedesk, read the Wisedesk topic on page 9-136. For specific information about
dynamic updating for Wisedesk, read the Setting up dynamic category updating topic on page 9-151.
Page 9-40
As Figure 3 shows, a Helpdesk person usually starts with a list of customers or requesters (see the
Working with Requesters panel).
Figure 4 shows how an authorized end-user can enter problems and requests directly into the
system using the FASTTASK view. S/he will find this to be a quick and efficient way of entering
a request or notify you of a problem (see Working with FASTTASK on page 9-46). Similarly,
once the Helpdesk person decides to enter a problem or request on behalf of a user, s/he will use
this same FASTTASK facility that the end-user could be allowed to use.
As shown in Figure 5, the Project Coordinator must review pending problems and requests
quickly. S/he needs an efficient means of reviewing previously entered requests and appending a
new request to an old one, or assigning the new one to a Working project (see Working with
WORKTASK on page 9-54).
And finally, as pictured in Figure 6, a Project Manager needs direct access to all of the Working
projects for which s/he is responsible. A Programmer needs direct access to Working projects and
tasks for which s/he is responsible.
Page 9-41
Filters--
View Task
Add/Change
Requesters
----------------------
F6/2
F2
View Related
Tasks
Work with Tasks
for Requester
12
----------------------
Wisedesk:
Filters--
Work with
Help Trees
FASTTASK:
Enter Requests
or Problems
Work with
Escalation Queue
----------------------
Figure 3
(See the TURNOVER for iSeries v100 Projects Overview section for an explanation of this
diagram.)
Page 9-42
The HELPDESK command, which can be placed on a menu or typed directly on a command line,
displays this panel:
1/29/10
13:07:41
_
_
_
_
_
_
_
_
_
_
Requester
BURBANK
BUSHNEIL
CAMPBELL
ELSINORE
ESPNBERM
HAYES
NEWTON
PHILLIPS
SCHWARZC
STANLEY
2=Change
First name
Karen
Neil
David
Steve
Chris
Bernard
Jane
Ed
Norman
Stephen
Last name .
Company . .
Apply filters .
4=Delete 7=Comments
Last name
Burbank
Bush
Campbell
Elsinore
Berman
Hayes
Newton
Phillips
Schwarzcopf
Stanley
Your Company,Inc.
YOURSYS
. ____________________
. _____________________________
. Y
9=View time 12=Tasks
Company
Quaker Publishing
BCCI
Merril-Lynch
UNICOM Systems
ESPN
Northeast Mutual
Parade Systems
UNICOM Systems
General Motors
FedReserve
F8=User fields
F17=Filters
Phone number
703-463-8590
803-524-5540
413-848-2175
203-924-8818
503-438-6744
913-441-9989
218-945-0412
103-924-8818
213-483-8619
603-418-8821
Ext.
23
25
2
More...
F12=Cancel
F2=Escalation queue
F18=Timesheets F21=System command
Typically, this is the view that a systems or Helpdesk person would prefer to use. Starting with a list
of your users or customers, you can filter by company, locations or any of a number of fields
including up to four user fields that you can define yourself. For example, you could filter by
department ACCT* and then type 12 next to each person in the list to view all of the requests entered
on behalf of each person in that department.
When you search by last name, company or any of the other fields provided, the list will be presented
in the order of that search field.
From the Work with Requesters panel, you can look up all of the requests for a requester or enter a
new one. You can also include comments to log conversations you have had with your requesters. Of
course, you can also enter a new request for the requester.
When you enter a new request, you will then see the HELPDESK Work with Projects panel
(identical to FASTTASK Work with Projects except that when entered from HELPDESK, it
remembers the requester you selected and defaults to that requesters ID when adding a request). See
Working with FASTTASK on page 9-46 for more information.
Page 9-43
You can also press F17 and filter the list by one or more of several other criteria:
1/29/10
13:07:41
Your Company,Inc.
YOURSYS
F8=User fields
F17=Filters
Ext
213
021
25
2
More...
F12=Cancel
F2=Escalation queue
F18=Timesheets F21=System command
When you type a value in a filter field and press Enter, the requester list is sub-setted by that filter
parameter. A message appears to remind you that you are viewing a sub-setted list.
You can type a partial name followed by an *, as in a Company of SOFTLAND*, to see a partial list
of all people that have a company that matches.
What you can do:
1=Add request
Add a request or problem on behalf of the requester. Equivalent to typing the FASTTASK
command on a command line, this will display the FASTTASK: Work with
Requests/Problems panel. See the next section for more on the FASTTASK function.
2=Change
Change requester record.
3=Copy
Copy an existing requester to create a new requester record for the same company/department.
4=Delete
Delete a requester.
7=Comments
Enter comments about interactions with the requester.
9=View time
See how much time has been spent on this requesters tasks.
Page 9-44
12=Tasks
See all of the requests related to a particular requester. See also F2 and F14.
F2=Work Escalation Queue
Work with the escalation queue. If you use the automatic escalation features of
TURNOVER for iSeries v100 Projects, you can look up the status of pending requests in the
queue. If filters are set on, then you will see only those escalation queue entries related to the
requesters that match the filter criteria. See the Working with the escalation queue topic on
page 9-87.
F6=Add requester
Add a new record to the Requester file.
F8=User fields
Review and change the user field definitions. Up to four Requester-related user fields can be
defined for your company.
1/29/10
13:07:41
F2=Work
F17=Filters
EscQueue
F4=List
F6=Add Requester
F11=View2
F10/F11=View3/View2
See additional requester data (including any user-defined fields) on alternate display panels.
F17=Filters
See a window from which you can set panel filters (selection criteria), including user fields, to
control what you see on Work with Requesters.
F18=Timesheet
Enter time in your timesheet.
Page 9-45
View Assigned
Tasks
Details
Add a Request
or Problem F5
Work with
Requests
or Problems Filters-F6
F5=Details
F2
Wisedesk:
25
2/5
Work with
Categories for
Task
Escalation
Queue
View or Change
Requests and
Problems
Text Search
Figure 4
(Figure repeated from TURNOVER for iSeries v100 Projects Overview section for clarity.)
UNICOM Systems, Inc. Recommends
We recommend that all project information about office procedures, status codes, priority range, and
the user-defined fields be written in the project description so that all users can easily refer to it,
without having to tie up the coordinators time with repetitive questions.
We also recommend that you put the FASTTASK command on the menu for each of your
FASTTASK users, using SoftMenu or other menu software.
Page 9-46
Throughout this section, youll see a few generic references on some panels. This is because
FASTTASK contains many features that are tailored for your companys specific needs. These
references are:
REQUEST
This appears in the title of some of the panels and in the description for some of
the function keys. Request might become Problem Report, Change
Request, or anything else that your company may want. You can set the
actual title in the project definition.
FIELD #
TURNOVER for iSeries v100 provides up to ten user-defined fields for each
project. You might see up to ten of these fields in the project in which you are
working, depending on how many fields your coordinator decided to use. The
names of the fields will also vary from project to project, depending on how the
coordinator set them up.
Your Company -
This is a global parameter that can be set to contain your companys name.
To begin the FASTTASK function, type the command FASTTASK on a command line. (We suggest
that you see your System Administrator about having FASTTASK put on your menu, and to confirm
that you have been authorized to all necessary functions.) You should see the main FASTTASK Work with Projects panel:
1/29/10
10:21:20
_
_
_
_
Proj
FCRQ
FHPR
FSPR
MISC
F3=Exit
2=Lookup a task
Description
Change Requests
Hardware Problem Reports
Software Problem Reports
Miscellaneous
F12=Cancel
Coordinator
JONESMIKE
JONESMIKE
RAYMOND
RYLAND
F21=System commands
Before entering a problem or request for the first time, it is a good idea to select option 5 (View
Project Description) for the Project with which youll be working. The project coordinator may
have entered some comments that will further explain how this specific project is set up.
Page 9-47
To enter a request, type a 1 next to the appropriate project on FASTTASK - Work with Projects. You
will see this panel:
1/29/10 14:20:20
Add a Request
Your Company, Inc.
Project: FPPR FASTTASK/ SLS Products Problem Reports
Description . . . . . . . . . . _____________________________________________
_________________________________
*Resource . . . . . . . . . . . PSCHMIDT
F4=List Phip Schmidt
*Status . . . . . . . . . . . . N NEW
F4=List
Requester . . . . . . . . . . . __________ F4=List
Priority . . . . . . . . . . . _
1 to 3 Sequence . . . ___
Date needed . . . . . . . . . . _______
Task type . . A ASAP
F4=List
User-defined field1 . . . . . __________ F4=List1
User-defined field2 . . . . . __________ F4=List
User-defined field3 . . . . . __________ F4=List
User-defined field4 . . . . . __________ F4=List
User-defined field5 . . . . . _________________________ F4=List
User-defined field6 . . . . . _________________________ F4=List
User-defined field7 . . . . . ________
F4=List
User-defined field8 . . . . . ________
F4=List
User-defined field9 . . . . . ________
F4=List
User-defined field10. . . . . ________
F4=List
F3=Exit
F4=List
F10=Additional parameters
F12=Cancel
F21=System command
* Status and Resource appear only when adding a request from HELPDESK.
Entering a request is a two-part process; the first is to complete this panel, the second is to enter a
detailed text description of your request. You should fill in the details for every parameter, if
possible, and enter a complete and accurate description of your problem or request when the Details
panel appears. When you viewed the project description, there may have been information about the
significance of the Status and Priority codes, and about the User-defined fields for this project. (If
you havent checked the project description yet, press F12=Cancel, and type a 5 next to the project
when you return to the original panel.)
Page 9-48
Once youve completed these fields, press Enter. If a details mask has been defined for this project,
you will see the Project Details Entry panel. On this panel you will enter a detailed description of
your request. You will probably see some information or directions on the entry mask on this
panel. Do not type over the information in the mask. Press the F1/Help key (Scroll Lock on a PC)
for information about how to enter details.
Page 9-49
When you finish entering a detailed description, you must press Enter to exit. You should see a
message at the bottom of your panel confirming that the request or problem has been entered. You
might also see a message saying that a message has been sent to the coordinator. This is pre-defined
by the coordinator, depending on the priority of the task you entered.
Youll return to the Add a Task panel. If you want to enter more requests or problems for this project,
do so. If youre finished, or want to enter a request for a different project, press F3. If you want to
cancel your text changes, press F12. Youll return to the FASTTASK - Work with Projects panel.
Looking up a previously entered request
Select option 2 on the FASTTASK - Work with Projects panel to lookup all tasks that have been
entered for a user entry project. You might do this to check on the status of prior requests; to make
changes to a request; to delete a request; to view other requests; to search requests or to send a
message(s) to the coordinator or person (resource) assigned to perform the task. You can also add a
new task by pressing F6 and following the procedure outlined on the previous pages.
1/29/10
10:22:44
Project:
FHPR
Apply filters. . . Y
2=Change 4=Delete
25=Search
10=Send message
_
_
_
_
Rqst
0001
0002
0003
0004
5=View
6=Print
Description
Laser printer jammed
Terminal flickers
FAX not receiving--Comm. Error
Laser printer--'fuzzy' output
F17=filters
Assigned
Task
PRTP0024
FAXP0005 +
Status
DONE
CANCELED
STARTED
NEW
The Assigned Task column shows the Working task to which your request or problem was assigned
(if applicable). If this column is followed by a + sign, the request resulted in more than one Working
task. Your original request is just as you entered it. The assigned Working task(s) was copied from
it. You can view both your original request and the assigned task(s). If more than one task was
created to service a particular request, then you will see a list of the assigned tasks. If this field is
blank then the task has not been assigned.
The Status is the status of the assigned task unless the assigned task field is blank; then it is the
original status. Your Project Administrator controls the actual status. These may have been changed
on your system since TURNOVER for iSeries v100 was installed. For each user entry project, each
company can decide what the initial status, accept status, assigned status and completed status should
be.
Page 9-50
Page 9-51
10=Message
Type 10 next to a task to send a message relating to that task. Youll see the Send Project
Messages panel that is discussed in greater detail later in this section.
11=Move
Type an 11 next to a task to move it either within this project or into another project.
25=Find text
Type 25 next to one or more tasks to do a search based on the context of the task and text
description. You can press F13 to repeat the 25 selection throughout the remaining tasks in
the list (that is, from that point forward).
F2=Escalation queue
Press F2 to work with the escalation queue. See page 9-87 for more information.
F6=Add Problem Report
Press F6 to add requests to this project. This works the same as option 1 of the main panel.
F17=Filters
Press F17 to view and set filters (selection criteria) to only see those requests you need to see
on this list. For example, you can set a Status filters to see only NEW requests or a priority
filter to see only priority 1 requests.
F18=Timesheet
Press F18 to make a time entry on your timesheet.
F21=System command
Press F21 to bring up a system command line.
Page 9-52
Type 10 next to a task on the Work with Requests panel to send a message relating to that request.
1/29/10 10:31:06
Task: FTPR0016
Send Message
A new task
Profile
Resource: ELSEMIKE
Requester: PHILLIPS
Coordinator: GIBSONGUI
User ID
ELMS
PHILLIPS
GIBSON
Address
MIKE
ED
GUITAR
__________
Message . . . . . . . . . __________________________________________________
______________________________________________________________________________
______________________________________________________________________________
_______________________________________
Key in message text and recipient and press F10 to send message.
F3=Exit
F10=Send
F12=Cancel
F21=System command
Page 9-53
Change or View
a Task
Work with
Escalation
Queue
Work with
Pending
Requests and Filters-Problems
F2
1
Task Details
11
Escalation
Queue
12
Review
Requests
Work with
Assigned
Tasks
Filters--
1=Append Request or
Problem
F2
F16
Assign to
Working
Projects
23,
24
Work with
Category Tasks
Work with
Categories
WISEDESK:
Work with
Help Trees
Send Messages
To:
Requester
Assigned Resource
Edit Details
Assign
Resource
Page 9-54
We recommend that you read through this section before setting up your Helpdesk projects, so that
youll have a better idea about what additional information your users will need.
We also recommend that you use the expanded project text description to convey information about
the project that the FASTTASK users may need. This information might include a description of
status codes set for this project; the priority code range, and its significance; the user-defined fields,
the entry and report masks you may be using, and how theyre to be used, and the priority codes that
will result in messages being sent.
Page 9-55
On a command line enter the command WORKTASK, or select it from your menu. 56
9/20/94
10:21:20
_
_
_
_
Proj
FCRQ
FHPR
FSPR
MISC
2=Lookup tasks
5=View description
Description
FASTTASK/Change Requests
FASTTASK/Hardware Problem Reports
FASTTASK/Software Problem Reports
Miscellaneous
F3=Exit
F12=Cancel
Coordinator
PSHIFTY
ELSINORE
PSHIFTY
PSHIFTY
F21=System command
The initial panel is WORKTASK - Work with Projects. This panel shows you all of the projects that
have been defined as user entry projects along with the profile names of their respective coordinators.
There are three ways that you can review tasks.
Press F2 to Work with Escalation Queue and view pending requests or problems in order by
priority, as they are presented to you on that queue. (See the section entitled Working with the
escalation queue on page 9-87.)
Select option 1 to cycle through and review all of the requests and problems for the project that
have not been reviewed yet.
Select option 2 to see a list of all tasks for a project. There you can choose from various options
on that panel.
Regardless of which method you choose, the process works the same, so we will only discuss
option 2=Lookup task.
Page 9-56
11:22:44
Project:
_
_
_
_
Task
0001
0002
0003
0004
Description
Laser printer jammed
Terminal flickers
FAX not receiving--Comm. Error
Laser printer--'fuzzy' output
Assigned
Task
PRTP0024
FAXP0005
Status
DONE
CANCELED
STARTED
NEW
57 You can set Requests to any literal value you want it to be when you define your project.
Page 9-57
3=Copy
Type a 3 to copy the request from one project to another. Copy rules are:
*WORKING to *HELPDESK project Task created looks new. It is given the initial
tasks status for that project, and escalation entries are processed if defined. Task will
appear if Review All is selected.
4=Delete
Type a 4 next to a task to delete it.
5=View
Type a 5 next to a task to view it. Once there, press F5 to view the details.
6=Print
Type a 6 next to a task to print out a report. Youll be prompted to select a report mask if
more than one has been assigned to this project.
7=Categories
Type 7 next to a task to see a list of Wisedesk categories in which it belongs. You can change
the list by excluding the task from some categories and including it in others.
10=Send message
Type a 10 next to a task to send a message relating to that task. See below for a more.
11=Move
Type a 11 next to a task to move that task. (For Copy rules, see 3=Copy above.)
12=Assigned task
Type a 15 next to a task to view the assigned task. Once there press F5 to view the details.
25=Find text
Type a 25 next to a task to search the task description and detail test for a particular character
string. You will be prompted for the search string.
F2=Escalation queue
Press F2 to view requests or problems pending on the escalation queue in order by priority, as
they are presented to you on that queue. (See the Working with the escalation queue topic on
page 9-87.)
Page 9-58
F18=Timesheet
Press F18 to enter time in your timesheet.
F21=System command
Press F21 to work with a command line.
Page 9-59
Review a Request
Your Company, Inc.
Project: FHPR FASTTASK/Hardware Problem Reports
Task . . . . . . . . . . . . . 0019
Status . . . NEW
Description . . . . . . . . . . A test request delete it.
Resource . .
Status . . .
Requester . .
Priority . .
Date needed .
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
User-defined
. . . .
. . . .
. . . .
. . . .
. . . .
field1
field2
field3
field4
field5
field6
field7
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
PSCHMIDT
V Reviewed
MARSSTELLA
1 to 3
3
0/00/00
F4=List
More...
F2=Assign F11=Reject F13=Accept F9=Print F10=Addl. Parms F16=Wisedesk
F3=Exit F5=Edit details F7=Requester comments F12=Cancel F21=System command
The Review a Request 58 is the same panel as the Add a Request panel on which the user entered the
task, with two notable exceptions. A Task identifier and the task Status now appear on this panel.
The coordinator can do one of the following:
Press F7 to view any requester comments that may have been entered by the Helpdesk person.
Press F11 to reject the request. You will be prompted to send a message to the requester.
Press F12 to cancel any changes you may have made to the request, and either proceed to the
next one or return to the Work with Projects panel.
Press F13 to accept the request without assigning it (the status changes to ACCEPT but no
other changes are made automatically).
Press F16 to start Wisedesk and search for related duplicate tasks.
58 You can set Request to be any literal value you want it to be.
Page 9-60
Initially the Resource field is set to *NONE. You can enter a valid resource name before proceeding,
if you like, or you can wait until you assign the task to a new project. Some people assign the
resource to a project manager who will reassign it later to a programmer in his/her group.
The initial Status assigned to the task is specified in the project definition. The status automatically
changes when you take some action. You do not have to set the Status manually unless you want to
override the automatic change of value. Parameters in the project definition determine the values. If
you take no action, the status will be set to the Initial review status. If you accept the task, the status
is set to the Accept status. If you reject the task, the task is set to the Reject status. If you assign the
request to a Working project, the status becomes Assigned. [This field is input capable, however, and
if you manually set the status yourself before taking any action, the status will not be changed
automatically. This feature was included so that you could have more than one Reject status to
provide more information about why you rejected a task to soften the blow. For example, your
normal Reject status might be Rejected. In some cases a request may have already been solved for
someone else and you may want to return a status of Duplicate along with a note in the details as to
which task to see for the solution.]
Note that, once a request is assigned, subsequent changes will be made to the assigned task(s), not the
original request. Look at the assigned task(s) to view current status and details. Look at the original
request if there are questions about the original request.
In the project definition, you can define up to ten User-defined fields. These will appear only if they
are defined for the project.
For more about what happens when a request or task is updated, see the Task escalation processing
topic on page 9-77.
What you can do:
Enter
If no action is to be taken, press Enter to update and exit from the panel. The Status is set to
the Initial review status. If youre Reviewing All you see the next request.
F2=Assign
Press F2 to assign the request to one or more Working projects. Any changes you have made
before pressing F2 will be updated. You have several options to choose from when assigning
tasks. The process is outlined in detail on page 9-63.
UNICOM Systems, Inc. Caution!
Any data entered in the user-defined fields in the Helpdesk task is copied into the user-defined fields
for the newly assigned Working task, if the same fields are defined for that project. Therefore, you
should consider carefully how you name and use these fields. They should be used consistently
between your Helpdesk projects and Working projects.
Page 9-61
F3=Exit
Press F3 to exit without update. The Status will be set to Initial review status. If you are
Reviewing All, you will exit and return to the initial WORKTASK panel.
F5=Edit Details
Press F5 to view or edit the text details that the requester entered. We recommend that you
attach a brief statement to the end of the details to explain the actions youve taken to the
requester. If youre assigning the request, you may also want to include additional instructions
for the person (resource) to whom you have assigned the request. When you exit from the
Edit Details panel, you will return to this panel.
F6=Print
Press F6 to print out a copy of the details. You may be prompted to select a report mask, if
more than one is assigned to this project.
F11=Reject request
Press F11 to reject the request. Any changes you have made will be updated. The status will
be set to the Reject status defined for the Project unless you manually set a status before
rejecting.
F12=Cancel
Press F12 to proceed without update. Works the same as Enter, except if youve entered
some changes, such as Resource, those changes will not be saved. In Review All, you will
proceed to the next task. The request status will be set to Reviewed status.
F13=Accept only
Press F13 to conditionally accept a request. Any changes you have made will be updated. To
conditionally accept a request means that you have accepted the request, but have not yet
decided where and/or to whom to assign the request. The status will be set to the Accept
status defined for the Project unless you manually set it before accepting the request.
Page 9-62
When you assign a request to a Working project, you have several choices:
1. You can assign the request to one task of a Working project. One Working task is created in the
project you selected.
2. You can assign the request as a subtask of another Working task. A subtask is created is created
under the project task you selected.
3. You can append the request to an existing Working task or subtask, as in the case where more
than one person reports a particular problem and the Working task has already been assigned.
4. You can assign the request to more than one Working task in more than one project, as in the case
where a problem impacts more than one project. For example, a problem requires that
programming fixes be done in the AP project and the AR project.
5. Any combination of these conditions.
To assign a task, use F2 while you review requests within WORKTASK, as described on page 9-56.
This pop-up panel appears:
1/29/10 11:21:30
Task . . . . . . . . . . . . . 0019
Status . . . NEW
Descrip ......................................................
:
Assign Task
:
Request :
: rs
Priorit : To project . . . . . . APPR
F4=Select
:
Priorit :
:
Date ne :
:
Task ty :
:
TurnOve :
: List
:
:
: F4=Select project F12=Cancel F16=Wisedesk
:
:
:
:....................................................:
You can either accept the default project, type in another one, or press F4 to select from a list, as
shown on the next panel. (Notice that you can also press F16 to start Wisedesk and search for related
tasks. For more information, see the Wisedesk topic on page 9-136.)
Page 9-63
Using the list, you can now select one or more projects to which to add the request; or you can work
with tasks in any one of the Working projects and either assign the request to an existing Working
task, create one or more Working subtasks, or assign the request as a new Working task to the project.
1/29/10
14:49:01
Position to project . . . .
1=Add task
Proj
12 APPR
__ OFC
__ TP40
Description
Demo Project sample problem reports
Project with *OFFICE editor
TURNOVER for iSeries Release 4.0 Problems
F3=Exit
F12=Cancel
Bottom
F21=System command
If you select one of the Working projects with option 12, then youll see this panel:
1/29/10
15:01:45
Project . . . APPR
*TOP, *BOT
F17=Select
_
_
_
_
_
_
_
_
_
_
_
Task
0001
0002
0003
0004
0005
0006
0012
0013
0014
0015
0016
Description
Fix check-writing program: This is a sam
Add status field to Vendor File
Test task 3
Test task 4
Test task 5
Test task 6
Add status field to Vendor File
Test task 13
Update sales tax tables
This is a big problem
This is a trivial problem
F3=Exit
F5=Refresh
F10=View 3 F11=View 2
Page 9-64
Resource
ELMSMIKE
TURNOVER
MARKPHIL
MARKPHIL
MARKPHIL
MARKPHIL
TURNOVER
MARKPHIL
MARKPHIL
PSCHMIDT
PSCHMIDT
Status
ASSIGNED
ASSIGNED
IN-QA
ASSIGNED
ASSIGNED
ASSIGNED
CANCEL
DONE
ASSIGNED
ASSIGNED
ASSIGNED
More...
F6=Add task F7=Control files F8=Assign to project
F12=Cancel F13=Repeat F21=Command line F24=More keys
Pty
1
1
2
1
1
1
1
1
1
3
1
Select a task with option 1 to assign the request to an existing task as a subtask.
Select a task with option 25=Find text to search the Working tasks for a task that is similar or
identical to the request you are reviewing. If you find one, then you can append the request to that
Working task with option 2.
If you do not find a related task, or the task status indicates that the one you were looking for is
closed or completed, then press F6 to add a new Working task based on the request being
reviewed.
If the choice you make results in adding a new Working task, youll see this panel:
1/29/10 16:18:50
Assign a Task
Your Company, Inc.
Project: APPR Demo Project sample problem reports
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
PSCHMIDT
A ASSIGNED
ASPINMAY
AP
__
__
2
Planned:
Planned:
Planned:
0/00/00
0/00/00
A ASAP
F4=List
F4=List
F4=List
F4=List
Pat Schmidt
May Aspin
1 to 3
0/00/00
0/00/00
Actual:
Actual:
Actual:
Units: H
0/00/00
0/00/00
F4=List
More...
F3=Exit
F4=List
F7=Requester comments
F10=Additional parameters
F12=Cancel
F21=System command
When you press Enter you can edit the task details. When you return to Work with Requests, you
will see that the task status is now assigned and the Assigned Task field contains the Working task
ID.
At any time, you can see all of the assigned tasks associated with a Helpdesk request and vice versa.
Read more about task relationships on the next page.
Page 9-65
A user enters request RQST0001 on September 4th. It requires action by two project teams. As
project coordinator, Bill reviews the request and assigns it to the two appropriate WORKING
projects, APPR and OEPR, as tasks APPR0043 and OEPR0068. If you now looked up HELPDESK
task RQST0001 using option 2 from WORKTASK, 59 you would see by the plus (+) sign next to the
task that it is assigned to more than one WORKING task. If you select the task with option 12, you
can see a list of all the WORKING tasks associated with this request in this case, you would see
APPR0043 and OEPR0068.
Helpdesk Task
Working Tasks
Request
RQST0001
Task
APPR0043
Task
OEPR0068
Now, suppose request RQST0012 is entered on September 6th. It is reported by another user and is a
duplicate of request RQST0001.
When Bill reviews the request, he recognizes it as a duplicate, and selects F16=Wisedesk to search
for the request hes already reviewed. (Wisedesk in turn remembers which task Bill is reviewing
now.) When he finds it, he selects it with option 12 to remind himself which task(s) he assigned it to.
Still within Wisedesk, Bill looks up the two assigned tasks, and selects both with Wisedesk option 24
to append to each the task he was reviewing.
Now you can select either WORKING task with Wisedesk option 12 and see that it now has two
originating HELPDESK tasks: RQST0001 and RQST0012.
Helpdesk Task
Working Tasks
Request
RQST0001
Task
APPR0043
Request
RQST0002
Task
OEPR0068
59 You can also view task relationships from Work with Tasks option 15, or from Wisedesks Work with Tasks in Category option 12.
Page 9-66
If you press F10 to send a message, or later if you select the send message option on Work with
Requests panel, youll see this panel:
1/29/10 16:31:03
Task: FTPR0009
Send Message
New task
Profile
Resource: MARKPHIL
Requester: MARKPHIL
Coordinator: GIBSON
User ID
Address
MARKPHIL S1014706
MARKPHIL S1014706
GIBSON S1014706
__________
Message . . . . . . . . . __________________________________________________
______________________________________________________________________________
______________________________________________________________________________
____________________________
Key in message text and recipient and press F10 to send message.
F3=Exit
F10=Send
F12=Cancel
F21=System command
The panel displays the requesters, resources, and coordinators user profiles and directory addresses,
for your reference. You can send messages to anyone who has a user profile on your system or a
directory address on your network.
Type a profile or directory address and a message; then press F10 to send the message.
You can repeat this step to send messages to as many users as you want.
Press F3 or F12 to exit. When you return to the Work with Requests panel, the status of the
original Helpdesk request is set to the status of the assigned task.
Page 9-67
F2
Change/View
Tasks
Work with
Tasks
Work with
Escalation
Queue
Filters--
F20
F16
20
Search or View
Assigned Tasks
25
Escalation
Queue
15
Wisedesk:
View
Originating
Requests
Work with
Worklists
Work with
Help Trees
Filters--
Categories
1
Cat. Tasks
Programmer
Worklist
20
Filters-32
PDM
F20
F15 /
15
X-Ref DB
Pathfinder
Abstract/Probe
TURNO VER X-ref
SEU/SDA
CODE/400
FLEX/EDIT
60 The data and rules for adding or changing tasks also apply to subtasks. Only tasks are discussed here.
Page 9-68
17:48:13
Project . . . APPR
F4=List
Task
0001
0002
0003
0004
0005
0010
0011
0014
0015
0018
0020
Description
Application distribution fails if applic
Nickname field in Requester file is shor
XREF did not grab a pgm to be COPR'd bec
Reserve Object Name allowed invalid name
CHKINOBJ does not recognize if source ha
Form Reapproval Error
FASTTASK tasks statuses are not being se
Source Checkout Problem
Upgrade bombs if SOFTTURN is not in ASP
Can't apply TO Changes to Remote systems
Received error MCH0603 when printing a p
Resource
BERNARDS
ELMSMIKE
SANDSAMY
ELMSMIKE
BERNARDS
*NONE
SANDSAMY
ELMSMIKE
SANDSAMY
BERNARDS
*NONE
Pty
2
2
2
3
2
2
2
3
3
3
3
More options
16=Forms 17=Checkout 18=Object history
7=Categories 19=Test plan
22=Audit history
...
More Keys
F3=Exit F9=View project
F17=Filters F18=Timesheet F20=PWM F21=Command line
F10=View 4 F11=View 2 F12=Cancel
F2=Esc. Queue F16=Wisedesk F24=More keys
You can jump to another project by typing the project code in the Project parameter or by pressing
F8=All projects or entering *ALL in the project code to see all tasks for all projects.
Besides selecting a particular task to view or update, this panel has some powerful filtering and search
capabilities that enable you to look up a task quickly, as might be the case when you need to find a
previously resolved problem that you want to review.
Page 9-69
If you press F17=Filters, you see the Filter Selections dialog box. Here you can specify selection
criteria so you see just those tasks you need to see at any given time.
............................................................................
:
Filter Selections
:
:
:
: Filters:
:
:
Resource ............. *ALL
Status ............... *ALL
:
Appl/Rel/Ver ......... *ALL
:
:
Requester ............ *ALL
:
Priority ............. _
1 to 3
:
:
Start date ........... 0/00/00 to 99/99/99 A A=Actual, P=Planned
:
:
:
End date ............. 0/00/00 to 99/99/99 A A=Actual, P=Planned
:
:
Date entered ......... 0/00/00 to 99/99/99
:
:
:
:
:
:
:
:
:
:
Application function .
:
:
:
:
Date Reported ........
:
:
Entered by ...........
1=Task, 2=Resource, 3=Priority
:
: Sort by:
2
:
:
: F4=List F12=Cancel
:
:
:
:..........................................................................:
For example:
1. Suppose you want to see all of the tasks added this month that are assigned to you. You can set
the Resource filter to your profile name and set the Date entered range to this month. Press
Enter.
2. Suppose you want to see the status of only the high-priority tasks. Set the Priority filter
appropriately. Press Enter.
3. Suppose you wanted to see all of the tasks completed this year on behalf of a particular customer
or user (requester). Set the Requester filter to the customers Requester ID (press F4 to see a list
if you dont know the ID) and set the End date range to this year followed by an A for Actual
time. Press Enter.
4. You can quickly change back to the unfiltered state, without clearing the filters, by setting the
Apply filters parameter on the Work with Tasks panel to N.
5. Suppose you want to see all of the tasks that are completed and have to do with the order entry
customer address maintenance process. If you often need to search for such a category, we
recommend setting up a User-defined field for your projects. In this example, you might call the
field Application function, as our panel shows (previous page). You could set up a table of
acceptable values that could be used to verify the field during data entry. If you had done so, then
you would see this user field in the Filters dialog box and be able to filter on a keyword such as
Address updates. You could set the Status filter to D for done (or the equivalent status code on
your system.) Then you would see all tasks that meet those criteria.
Page 9-70
If the task you are printing is associated with more than one requester, a list of related
requesters appears so you can choose those for whom you want to print copies. You can
include copies for any unrelated requesters you want to notify. If you dont select any
requesters, a single copy prints. If your report mask includes requester information, the copies
will be personalized.
7=Categories
Type 7 next to a task to see a list of Wisedesk categories in which it belongs. You can change
the list by excluding the task from some categories and including it in others.
9=View time
Type 9 next to a task or subtask to view time reported against that task. See the section
entitled Entering Time Using the On-Line Timesheet on page 9-112.
11=Move
Type 11 next to a task or subtask to move it to another project or task (respectively).
13=Details
Type 13 next to a task or subtask to edit the text detail description for that task or subtask.
14=Authority
Type 14 next to a task to edit the task authority. Unless specifically changed by you, the
authority settings for the task are identical to those for the project. (See the section entitled
TURNOVER for iSeries v100 Projects Authority on page 9-18.)
Page 9-71
15=Original task
Type 15 next to a task to view original Helpdesk requests. When a request or problem is
entered into TURNOVER for iSeries v100 from the HELPDESK or the FASTTASK
Helpdesk function, it remains in the Helpdesk project after it is assigned to a Working project.
One request can result in one or more Working tasks. Also, several users may have reported
one Working task; therefore, one Working task will fix more than one request. Option 15 lets
you view all of those original requests. If the task did not derive from a Helpdesk request,
then youll see a message This task not derived from a Helpdesk request. (See More about
Associating Request and Working Tasks on page 9-66.)
16=Forms
Type 16 next to a task or subtask entry to view all of the TURNOVER for iSeries v100
forms (promotion jobs) related to that task.
17=Checkout
Type 17 to view any system objects currently checked out with work in process that are
related to the task. (From there, press F11 to see checked out IFS objects for this task.)
18=Object history
Type 18 adjacent to a project or task to view all object change history for the task selected.
19=Test plan
Type 19 next to a task to view the TURNOVER for iSeries v100 test plan associated with
that task. 61 The test plan lists the TestBench tests that will need to be run to test the changes
for the task.
20=PWM
Type 20 to create or work with a Programmers Worklist associated with the task. A worklist
is a list of objects that are to be changed or created to complete the task. (For more
information about PWM, see Programmer Worklist Manager (PWM) on page 9-116.)
22=Audit history
Type 22 to view all project change history for the task selected. The projects Audit project
changes parameter (in the Project Description) must have been set to Y.
25=Find text
Type 25 next to several tasks or subtasks to search the task descriptions and text details for a
specific text string. Youll be prompted for the search string. To limit your search time, we
recommend that you set filters first, and then search only the tasks that meet the filter criteria.
F6=Add task
Press F6 to add a new task (see the next section for illustration of add/change a task panels).
61 To work with a TURNOVER for iSeries v100 test plan, you must have the TestBench product installed on your system. If you do not have
TestBench installed on your system, when you attempt to access a test plan, you will see the message TestBench files not found. For detailed
information about the TURNOVER for iSeries v100 TestBench interface, see the TURNOVER for iSeries v100 Interface guide entitled Using the
TURNOVER for iSeries v100 TestBench Interface.
Page 9-72
F7=Control Files
Press F7 to access a menu to view or change certain control file information in TURNOVER
for iSeries v100. You must have specific authority to do so. (See Working with
TURNOVER for iSeries v100 Projects Control Files on page 9-88.)
F8=All projects
Press F8 to view all tasks for all projects.
F10/F11=View 2/View3
Press F10 or F11 to see alternate task views that include, among other things, user-defined
task fields.
F13=Repeat
If you type an option and then press F13, the option will be replicated for every task/sub-task
in that project from that position on. If you have filters applied, it will only repeat the option
for the filtered tasks and subtasks.
F16=Wisedesk
Press F16 to start Wisedesk and go to the Work with Help Trees panel. You can use help
trees to search for information about problems, requests, or tasks and to add new tasks in
projects to which you are authorized.
F18=Timesheet
Press F18 to enter timesheet information. See the section entitled Entering Time Using the
On-Line Timesheet on page 9-113. (Alternate path: TIMESHEET command.)
F20=PWM
Press F20 to view and work with your list of Programmer Worklists. Youll then see the
Work with Programmer Worklists panel. For more about PWM, see Programmer Worklist
Manager (PWM) on page 9-116. (Alternate path: STRPWM command.)
Page 9-73
Task . . . . . .
Description . . .
is not active
Resource . . . .
Status . . . . .
Requestor . . . .
Application . . .
Release . . .
Version . . .
Priority . . . .
Priority sequence
Duration . . . .
Start date . . .
End date . . . .
Date needed . . .
Date promised . .
Task type . . . .
Add a Task
Project: APPR Accounts Payable Project
. . . . . . . 0001
. . . . . . . Application distribution fails if Remote system
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
SCHMIDTP
V REVIEWED
SLAWSONJIM
AP
F4=List
F4=List
F4=List
F4=List
1 to 3
Phil Schmidt
Jim Slawson
Planned:
12.00 Actual:
13.00
Planned: 12/01/02 Actual: 12/04/02
Planned: 12/31/02 Actual: 0/00/00
1/02/03
12/31/02
F4=List
A ASAP
Units: H
More...
F3=Exit
F4=List
F7=Requester comments
F10=Additional parameters
F12=Cancel
F21=System command
Note: Notice that the function keys at the bottom of the Add a Task panel are different from
those on the Change a Task panel. For a description of these function keys, see the online
Help.
1/29/10 13:12:26
Task . . . . . .
Description . . .
is not active
Resource . . . .
Status . . . . .
Requestor . . . .
Application . . .
Release . . .
Version . . .
Priority . . . .
Priority sequence
Duration . . . .
Start date . . .
End date . . . .
Date needed . . .
Date promised . .
Task type . . . .
Change a Task
Project: APPR Accounts Payable Project
. . . . . . . 0001
. . . . . . . Application distribution fails if Remote system
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
SCHMIDTP
V REVIEWED
SLAWSONJIM
AP
F4=List
F4=List
F4=List
F4=List
1 to 3
Phil Schmidt
Jim Slawson
Planned:
12.00 Actual:
13.00
Planned: 12/01/02 Actual: 12/04/02
Planned: 12/31/02 Actual: 0/00/00
1/02/03
12/31/02
F4=List
A ASAP
Units: H
More...
F3=Exit
F4=List
F5=Edit details
F6=Add subtask
F7=Requester comments
F8=View time F9=Print F10=Additional parms. F12=Cancel F24=More keys
More Keys
F3=Exit
F4=List
F5=Edit details
F6=Add subtask
F7=Requester comments
F8=View time F9=Print F19=Test Plan F21=System Command F24=More keys
Page 9-74
Most of the defaults that you see and rules governing what information you can enter here are
supplied by the project definition.
For example:
1. The Resource name might default to a particular profile name, but in our example, it is set to
*NONE with the assumption that you will assign it appropriately.
2. The rules for entering a requester are determined by the Project definition. They can be set to
require that it be a user profile; a Requester ID selected from the Requester file, or both a profile
and a Requester ID.
3. The Application, Release, and Version fields are also determined by the Project definition.
Normally, each project or task will relate to only one application. See UNICOM Systems, Inc.
Recommends on the next page.
4. If User-defined fields have been included, then these must be entered according to the edit rules or
tables specified when they were defined in the project definition.
5. Test libraries might default to specific names, but in our example, they are blank with the
assumption that you are supplying test library names in your application definition. If the
application definition test libraries were set to *PROJECT, TURNOVER for iSeries v100
would look to these fields for the names of the appropriate test libraries. (If you ARE supplying
this information in your application definition, then you should leave these fields blank.)
Refer to the online Help for more about each of these examples.
What you can do:
F4=List
Press F4 where appropriate to see a list of valid entries for the corresponding field.
F5=Edit details (Change only)
Press F5 to view, edit, or enter text details about the task. 62
F6=Add subtask (Change only)
Press F6 to add a subtask entry subordinate to the current task entry.
F7=Requester comments
Press F7 to read any comments the requester included when the task was created.
F8=View time (Change only)
Press F8 to view the time logged for this task.
62 When entering task details, you can press F2 to stamp your entry with a comment header containing a date and time. You can customize this
comment header by renaming program object SOFTTURN/TURRBRCH to TURRBRCHX (or some such), then copying our sample comment header
program SOFTTURN/ARPGLESRC(TURRBRCH2) into a location in your system library list. Rename it to TURRBRCH, modify it as desired (our
sample adds a prefix of dashes to the comment header), and compile it. As long as your version resides in your system library list, it will not get replaced
when you upgrade or apply changes.
Page 9-75
When you finish creating or changing the task details, press Enter. You must press Enter
again to finish adding the task. If adding a task, you will then go to the Details Entry panel, if
these are required for your project (as determined by the project definition).
UNICOM Systems, Inc. Recommends
If you need more than one person assigned to a task, consider dividing it into two or more tasks or
adding subtasks. For best accountability, we recommend that only one person be responsible for a
task. You can copy a task (option 3 on the Work with Projects panel) to create a new task or subtask.
Similarly, if a task relates to more than one application, we suggest that you divide it into two or more
subtasks, each of which relates to a single application. These may or may not be assigned to the same
resource (developer).
Page 9-76
Page 9-77
An escalation queue (ESCQ) is used to monitor all of the tasks for which escalation-monitoring rules
apply. Only tasks that meet certain criteria, as defined in the projects escalation table, are included in
the escalation queue.
Heres how it works:
1. A task or subtask is created or updated.
The fields in the task file that are monitored for change include:
Status
Priority
Date promised
Duration
Projected completion date
2. TURNOVER for iSeries v100 checks for an entry in the escalation table
(see The escalation table on page 9-80, keyed by Priority and Task status)
3. TURNOVER for iSeries v100 calculates the wake-up date and time
4. Is there a matching escalation table entry?
Yes. Did the task priority and/or status change?
No.
Calculate the wake-up date and time.
Update the wake-up date, time.
Yes. Delete the queue entry for this task.
Update the wake-up date and time.
Add a new queue entry for this task.
No.
Is there already an entry on the escalation queue for this task?
Yes. Delete the task escalation queue entry.
If the task status and/or priority has changed and there is no matching entry in the escalation
table, the task is removed from the escalation queue and will no longer be monitored.
Page 9-78
The calculation of the wake-up date and time depends one of these variables:
Escalation Interval (from escalation table)
Alarm Interval (from the escalation table)
Due date from task record
Estimated completion date
Estimated Duration from the task record
If Due date is blank and Estimated completion date is blank
Wake-up date/time = Todate + Escalation-time-interval - Alarm-days/hrs - Duration-days/hrs
Else
If Estimated completion date is not blank,
Wake-up date/time equals Due date/time - Alarm-days/hrs - Duration days/hrs
Example 1: (time of day on due date assumed to be 0800hrs or .333)
Todays date
94100.333 (julian)
Escalation interval
+10.000 (days)
Duration 16 hrs (default=7/day)
-2.183 (days)
Alarm interval (24 hrs)
-1.000 (days)
Wake up date/time
94107.150 (or 4/17/94 at 03:36)
Example 2: (time of day on due date assumed to be 0800hrs or .333)
Due date
94100.333 (julian)
Est. Duration 16 hrs (default=7/day)
-2.183 (days)
Alarm interval (24 hrs)
-1.000 (days)
Wake up date/time
94097.150 (or 4/07/94 at 03:36)
A task is added to a project and, after checking the escalation table, an entry is made on the escalation
queue. At periodic intervals, the escalation processing program which is set to run as an autostart
job 64 wakes up and checks the escalation queue, as follows:
Is any tasks Wake-up date-time >= (greater than or equal) current date-time?
Yes. Look up action in escalation table. Do the defined action(s).
When an escalation queue entry is added or updated on the escalation queue, it is set to indicate
whether the next wake-up date-time is to send an Alarm or to Escalate the entry.
63 The actual date calculations are based on days since January 1, 0000. Julian dates used here are for illustration only.
64 See the TURNOVER for iSeries v100 Supplement entitled Setting Up TURNOVER for iSeries v100 Autostart Jobs (#25) for information about
how to set up an autostart job to run the Start Escalation queue command: TSTRESCQ.
Page 9-79
Table: HELPDESK
2=Change
_
_
_
_
_
_
_
_
_
_
_
_
3=Copy
Pty Status
A ASSIGNED
1 N NEW
2 N NEW
3 N NEW
4 N NEW
R REJECTED
1 U URGENT
2 U URGENT
1 V REVIEWED
2 V REVIEWED
3 V REVIEWED
4 V REVIEWED
F2=Print listing
4=Delete
Aging
Rpt
N
N
Y
Y
Y
N
N
Y
N
Y
Y
Y
F3=Exit
6=Command
Alarm
Interval
48
24
2
4
Hrs
Hrs
Hrs
Hrs
24
4
7
2
1
4
Hrs
Hrs
Days
Days
Days
Hrs
7=Messages
Repeat
Alarm
N
N
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
F12=Cancel
Bottom
F21=System command
If an escalation table has not been associated with the project66 or no matching entries are included, no
automatic escalation will occur for this project.
How the escalation table works
A task is added
The escalation table is checked for a matching Priority and Status entry. If found:
If one or more messages exist (Msg=Y) with Action code of N (New),
send the message(s).
If one or more commands exist (Cmd=Y) with Action code of N (New), run the
command(s).
Calculate the Alarm wake-up time based on the Alarm interval.
Calculate the Escalation wake-up time based on the Escalation interval.
Calculate the Task wake-up time based on the Due dates and duration.
Write an escalation queue entry for the task for the Alarm, Escalation, or Task wake-up
time, which ever is sooner.
Page 9-80
When you set up your escalation table, be sure to consider whether the project is to be a user entry
project, a Helpdesk project, a Working project, or is to be used for some other purpose. If the project
is a Helpdesk project, the escalation table would be set up similarly to the table shown on page 9-80.
However, a Working project (one used by your programmers) would most likely contain entries for
status values of Assigned, Started, Held (or equivalent codes at your company) to track progress after
a task is assigned. The next panel shows an escalation table for a typical Working project.
Page 9-81
We provide model Helpdesk and Working tables that you can use or copy as the basis for your own
tables. The sample on page 9-104 is the Helpdesk table.
The following escalation table might govern a Working project to which tasks are assigned:
1/29/10 15:13:31
Table: WORKING
2=Change
_
_
_
_
_
_
_
_
_
_
_
_
Pty
*
1
2
3
4
1
2
3
4
*
*
*
3=Copy
Status
A ASSIGNED
A ASSIGNED
A ASSIGNED
A ASSIGNED
A ASSIGNED
D DONE
D DONE
D DONE
D DONE
H HOLD
S STARTED
W WAITING
F2=Print listing
4=Delete
Aging
Rpt
N
Y
Y
Y
Y
N
N
N
N
N
N
N
F3=Exit
6=Command
Alarm
Interval
14 Days
12 Hrs
6 Hrs
7=Messages
Repeat
Alarm
N
N
Y
Y
Y
N
N
N
N
N
N
N
F12=Cancel
Bottom
F21=System command
Page 9-82
Repeat Alarm
If set to Y, continue to send an alarm message for a task whenever the Alarm interval time
limit passes. If set to N, alarm messages will be sent only once.
Escalation interval
In days, hours or minutes, the time interval after which an escalation action will occur.
Esc Priority
This is the new priority code value to which a task is changed after the task Escalation time
interval has been exceeded. The task Priority will not be changed automatically if this field is
left blank.
Esc Status
This is the new status code to which a task is changed after the Escalation time interval has
been exceeded. The task Status will not be changed automatically if this field is left blank.
Msg
This is Y if messages have been defined that are to be sent when a task is added or an Alarm
interval or Escalation interval expires; otherwise N. More than one user can be a recipient of
a message. Select option 7 to view recipients and messages. You can set default recipients to
a user profile name or *RSRC (task Resource), *RQST (Task Requester) or *COORD
(project Coordinator for Helpdesk projects; Administrator for Working projects).
Cmd
This is Y if commands have been defined that are to be run when an Alarm interval or
Escalation interval expires, otherwise N. Select the entry with option 6 to view the
command(s) to be run.
Refer to the section about defining escalation tables on page 9-104 for more about creating a table.
Escalation table definitions can be accessed using option 10 on the TURNOVER for iSeries v100
Project Control File Menu (F7 on the Work with Projects panel).
Page 9-83
Priority 4 (highest); most severe problem, must be reviewed within 2 hours and must be
addressed and fixed as soon as possible. Task takes precedence over all other tasks. May require
advisory be sent to all customers.
Priority 3; urgent, must be reviewed within 4 hours and will be addressed immediately and fixed
or resolved with a work-around within two working days. If a satisfactory work-around is
devised, it will be down-graded to priority code 2.
Priority 2; must be reviewed within 48 hours. It will be addressed in the next release of the
product. If it has a due date assigned, then the task will be completed by that due date.
Priority 1; must be reviewed with 7 days. It will be addressed the next time the related function
is revised or replaced, not necessarily in the next release, but will remain open no longer than 365
days.
Imagine two projects, one Helpdesk project (PROB) and one Working project (APPR).
Page 9-84
Page 9-85
Page 9-86
Filter by:
Project: ____ Status: __ Priority: _
Soft by: _
1=Wake-up 1=Priority
2=Status
4=Project
You can filter and change the sequence of the items in the queue. Only tasks with a priority/status
combination that appear in the projects escalation table will be listed.
To make a change to the queue, you must have full authority to the associated project.
You can override the Wake-up date and time manually. When you do, the Chgd by column will be
set to the profile ID of the user who changed it. Other values for Chgd by are *ESCQ (by the
escalation processing program) and *UPDT (by the Task update program) as a result of a task being
added or significant data being updated.
Select option 5 to view the complete queue entry.
Select option 12 to work with the task and option 15 to view the task.
Select option 11 to start WORKTASK and review a task that was entered using HELPDESK or
FASTTASK, and process the request if you are authorized to do so. Some project managers may
prefer to work with this escalation queue rather than with WORKTASK.
TURNOVER for iSeries v100 checks the escalation queue at a frequency you define (default is 30
minutes) and processes all entries that have a wake-up date and time that has expired. To change the
wake-up interval, use the command TSTRESCQ. The parameter is wake-up interval, in seconds.
This command starts the escalation queue monitor if it is not running and resets the time interval.
(3600 seconds equals one hour.) The TSTRESCQ command must be submitted to run in batch.
Page 9-87
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
with
with
with
with
with
with
with
with
with
with
with
Status codes
Task type codes
Timesheet categories
Resources
Requesters
User-defined fields
Entry masks
Report masks
Messages
Escalation tables
Conflict resolution codes
Select option: __
F3=Exit
F6=DSPMSG
F14=WRKSBMJOB
F12=Cancel
F21=System command
From this panel, you can maintain all of TURNOVER for iSeries v100s project control files. Any
user can get to this panel, but s/he must have the appropriate authority to access each option. Code
maintenance authority (the Code column on the Maintain Users Authority List panel) allows the user
access to options 1, 2, 5, 6, 7, 8, 9, and 10. Resource maintenance authority (the Rsc column on the
Authority List panel) allows the user to access option 4, and Requester maintenance authority (Rqs
column on the Authority List panel) allows the user to access option 5.
Page 9-88
4=Delete
Short
Code Desc.
_ A ASSIGNED
_ B DISTRIB
_ C CANCEL
_ D DONE
_ F FINISHED
_ H HOLD
_ K DUPLICAT
_ M CONFIRM
_ N NEW
_ O ONGOING
_ P IN-PROD
_ Q IN-QA
_ R REJECTED
_ S STARTED
_ V REVIEWED
F3=Exit
Long
Description
Request/Task has been assigned
Task has been distributed
Has been canceled
The task has been completed
Task has been completed
On hold. Awaiting instruction
The task is a duplicate of ano
Task has been confirmed
A new request.
Project/task is on-going
Task has reached production
Task has reached QA
Request was not accepted.
Project or Task has been start
Request has been reviewed
F6=Add code
F12=Cancel
Show
Y
Y
Y
N
N
Y
N
Y
Y
Y
Y
Y
N
Y
Y
Update Update
Allow as Start End
Reference Date
Date
Y
N
N
Y
N
N
N
N
N
N
N
Y
N
N
Y
Y
N
N
N
N
N
N
N
Y
Y
N
N
Y
N
N
Y
N
N
Y
N
N
N
N
N
Y
Y
N
Y
N
N
More...
F21=System command
You can change the status codes or add new ones. You must have code maintenance authority to
maintain this status code list. Remember that this is the master control file and that changes will
impact all applications and projects.
The Show field determines whether or not tasks with this status will be displayed on panels that
youve filtered with a status code value of *LIMIT. Y means that tasks with this status are always
shown.
The Allow as Reference column indicates whether any task assigned the related status value can be
used as a reference when checking out or promoting objects in TURNOVER for iSeries v100.
The Update start date and Update end date determine whether to automatically set the task start and
end dates when the task status is set to that value. For example, when you check out an object, the
application you are working can be set such that the task status is automatically set to S (Started).
The Update start date field for S Started is set to Y, so the Task start date will be set to todays date.
Page 9-89
4=Delete
Type code
A ASAP
C CNVNENCE
F FIXED
L ALAP
M MILESTON
Description
As soon as possible
At your convenience
Fixed
As late as possible
Milestone
Bottom
F3=Exit
F12=Cancel
F21=System command
You can change or add codes to this table but be aware that future releases of TURNOVER for
iSeries v100 may lock its use to the values below.
A=ASAP (Schedule As Soon As Possible)
L=ALAP (Schedule As Late As Possible)
M=MILESTON (Milestone task duration must be zero).
F=FIXED (Fixed date task must be done on date specified)
Page 9-90
4=Delete
Description
Administration
Consulting
Design
Marketing
Programming
Quality Assurance
Problem Resolution
Testing
Writing User Documentation, Etc.
Bottom
F3=Exit
F6=Add category
F12=Cancel
F21=System command
If you do not need to report specific categories of time, then you might delete all of the category codes
except one, and use that code when reporting all of your time.
Page 9-91
4=Delete
Resource
*NONE
DELANEY
ELSINORE
PHILLIPS
PSHIFTY
QSECOFR
_
_
_
_
_
_
F3=Exit
Description
no resource is assigned
Jim Delaney
Steve Elsinore
Ed Phillips
Paul Shifty
Security Officer
F6=Add resource
F12=Cancel
Dept./Category
Training
Dev
QA
QA
F21=System command
Press F6 to add a resource name. Youll be prompted for a Resource, Name, and
Department/Category. The Resource is usually a User profile name. The Department/Category can
be used for anything you want to use it for.
Type a 4 next to a resource you would like to delete; type a 2 next to any resource you would like to
change.
Names on the resource list can be included on the authority list for a project. You can specify which
users should have access to specific project or task at that time. Only users authorized to a
TURNOVER for iSeries v100 project can be authorized to a subordinate task or subtask within the
project. (For more information, see TURNOVER for iSeries v100 PROJE, beginning on page 916.)
Page 9-92
__
__
__
__
__
__
__
__
__
__
Requester
ANDERSOALB
ANDERSODAV
ANDERSOJOE
ANDERSOLIZ
ANGLEMAMAR
APPLEWORAY
ARCSON KRO
ARCELMALOU
ARGDENNIL
ASHERMIK
First name
Albert
Dave
Joel
Liza
Margo
Ray
Kronen
Lou
Niles
Michael
Last name
Anderson
Anderson
Anderson
Anderson
Angleman
Appleworks
Arcson
Arcelman
Argden
Asher
Company
Meyers Co
Warren Distributi
Margrove Ind.
Yorkey Publishing
American Nutritio
The Bowles Group
UCC Industries
Cyruss Corp.
Busch Research
Connector Box Co.
Phone number
Ext.
1-804-555-9172 2232
1-402-555-9397 0021
1-515-555-8845
(603) 555-8111
1-409-555-6654
44-53-555-4661
1-607-444-2841 0112
1-702-555-3515
1-314-555-7470
1-404-555-7182
More...
F2=Escalation queue
F21=System command
To enter a new requester, press F6 and enter all of the appropriate information on the form provided.
To update requester information, place a 2 next to a requester name.
The Requester identifier must be unique.
You can also define up to four user-defined requester fields. To do so, press F8=User fields. Keep in
mind that changes affect all project system requester records.
Requester information might be useful for generating reports using a project Report Mask. For
example, you can produce letters or even faxes to users informing them of the latest status of their
requests. For more information on this procedure, see page 9-97, or press the F1/Help for details on
the mask entry panel.
You can quickly search through your requester file to find a specific client by entering the last name,
first name, company/dept. or requester code in the appropriate fields at the top of the panel.
Press F10 or F11 to see alternate view panels.
Page 9-93
Press F17 to see the filters. Youll see this pop-up panel:
1/29/10 10:59:57
Note that the last four filter fields are user-defined fields that you or your Administrator may have
defined in some other way.
You may type a generic search field such as SOFT* in the filter fields. Once you set a filter, press
Enter to view the Work with Requester panel subsetted by your filter settings.
UNICOM Systems, Inc. Recommends
If you plan to use the Helpdesk system then, in order to take full advantage of TURNOVER for
iSeries v100 Projects messaging features, you should take time to complete the User ID and directory
address information on the requester panel. Also, you will find that things will work smoothly if you
enter all of your users in the Requester file and make their requester code name the same as their user
profile.
Page 9-94
_
_
_
_
_
_
_
_
4=Delete
Field
NUMERIC
SUBSYSTEM
TESTFIELD
USERNAME
USR0000001
USR0000002
USR0000003
USR0000004
Panel description
Test numeric field
TURNOVER subsystem
Test field
User Name
Department ID/Location
Product/Version
Module -- AP, AR, GL etc.
Accounting Module
F4 Pgm
*NONE
*DEFAULT
*NONE
*DEFAULT
*NONE
*NONE
*NONE
*NONE
Valid. Pgm
*NONE
*DEFAULT
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
Type
*DEC (7,2)
*CHAR (10)
*DEC (7,0)
*CHAR (25)
*CHAR (25)
*CHAR (25)
*CHAR (10)
*CHAR (10)
Bottom
F3=Exit
F6=Add field
F12=Cancel
F21=System command
You can press F6 to add a field, or select an existing field with option 2 to change it.
This panel appears when you press F6. (Option 2 produces virtually the same panel.)
1/29/10 15:44:21
Bottom
F3=Exit
F6=Add field
F12=Cancel
F21=System command
Page 9-95
The Field name you assign must start with an alphabetic character and be no longer than 10
characters.
The Field type designates its length and content characteristics. Choose from four combinations of
field length and type.
The Panel description is the field label that will appear on task panels.
The F4 program field either identifies a program that will prompt users to view and select field
values when adding or changing a task, OR it defines a relationship dependency between this fields
values and those of a parent field.
If set to *NONE, the F4=List option is not available to users who are typing information into
a task panel field.
If set to *DEFAULT, users can define a table of values by pressing F4=List and then creating
acceptable values for the field.
If set to a program name, you must provide an exit program for TURNOVER for iSeries
v100 to call. Your program must display a list of valid values from which users can select.
Note: Custom programs specified here run only when processing tasks from the 5250
interface. The TURNOVER for iSeries v100 Client cannot call custom programs. For
prompting that works in all interfaces, use *DEFAULT.
If set to *CHILD, the Validation program field must identify the parent field on which this
fields valid values should depend.
If set to *NONE, no validation will be performed when entering information in the field.
If set to *DEFAULT, the values will be validated against the list of valid values defined for
the field.
If set to a program name, you must provide an exit program that TURNOVER for iSeries
v100 will call and that must validate a value passed to it, returning a status flag back to
TURNOVER for iSeries v100s calling program.
Note: Custom programs specified here run only when processing tasks from the 5250
interface. The TURNOVER for iSeries v100 Client cannot call custom programs. For field
validation that works in all interfaces, use the Task Validation exit point (PROJ 05).
And, if set to a parent field name, the values of the child field depend on the value chosen for
the parent field during task maintenance.
Page 9-96
Nesting is limited only by the number of fields you can specify for any given project (10), but
dependencies themselves can be only one layer deep. In other words, using the diagram
below, UDF2 dependencies apply only to UDF1 values, and UDF3 dependencies apply only
to UDF2 values. The value chosen for UDF1 has no effect on the valid values for UDF3.
Custom programs for prompting and validation are not supported when you are using field
dependencies.
TURNOVER for iSeries v100 does not try to make sure that you have added all related
fields to your project.
UDF1
Hardware
UDF2
Display
Software
Modem
JDE
Printer
OE
Payroll
UDF3
Ink
Jam
For instance, suppose you have a help desk project for end users to enter problems.
UDF1 might be called TYPE of ISSUE with valid values of hardware or software.
UDF2 might be called CATEGORY and have valid values defined that depend on UDF1.
UDF3 might be called PROBLEM and have valid values defined that depend on UDF2.
Page 9-97
_
_
_
_
_
_
_
F3=Exit
F12=Cancel
If you choose to add or change a project mask, you will go directly to the Project Masks panel.
To add a mask, fill out the name and description at the top of the panel and press Enter.
To change a mask, type a 2 next to the mask you want to change and press Enter.
To delete a mask, type a 4 next to the mask you want to delete and press Enter.
Before creating an entry mask, try to anticipate all of the information that you might want to gather.
Then create a form-like mask that prompts for the information you need.
Page 9-98
Project Mask
Mask Name: PROBRPTS
-----------------------------------------------------------------------------Resolution:
(To be filled out by the programmer)
------------------------------------------------------------------------------
******
END OF DOCUMENT
******
F6=Insert Lines
When the task details from an entry mask are printed using a report mask, it operates like a mail
merge for one task or request; everything (including the mask) is printed. The text will print starting
with column one, so if you want a left margin, youll have to leave spaces for a margin.
One more tip: If youre going to be printing the task details using a report mask, dont put headings
such as Problem Report on the entry masks. Put these on the report mask otherwise when you
print it out, you will have two headings in two places.
Page 9-99
Your company can define its own report masks using option 8 on the TURNOVER for iSeries v100
Project Control Files Menu.
1/29/10
13:08:03
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
_
_
_
_
_
_
_
Mask
Name
CMPR
CMPR-FAX
FAX
PR
PR-FAX
TOPR
TOPR-FAX
F3=Exit
__________
_________________________
__________
*CURRENT, Name
__________
*LIBL, Name
4=Delete
Mask
Description
CENTRAL for iMenu Prob. Rpt
CENTRAL for iMenu Fax Form
Fax Form Mask
Problem Report
Problem Report Fax Form
TURNOVER for iSeries Prob. Rpt
TURNOVER for iSeries Fax Form
Output
Queue
*CURRENT
FAXOQ
FAXOQ
QPRINT
FAXOQ
*CURRENT
FAXOQ
Outq
Library
*LIBL_____
QGPL______
QGPL______
QGPL______
QGPL______
*LIBL_____
QGPL______
F12=Cancel
If you choose to add or change a project report mask, you will go directly to the Report Masks panel.
To add a mask, fill out the name, description, output queue and library at the top of the panel and
press Enter.
Page 9-100
To change a mask, type a 2 next to the mask you want to change and press Enter. Heres an example
of a Report Mask we have defined.
1/29/10
17:22:35
Report Mask
Mask Name: PROBRPT
P R O B L E M
Resource:.&RSRN Status:.&STSD
Actual
.&SDTA
.&EDTA
.&DURA
.&DTLS
******
END OF DOCUMENT
******
F6=Insert Lines
F9=Substitution parms
You can position to wherever you want a substitution parameter and press F9=Substitution parms.
You will see a list (not included here) from which you can select the substitution parameters you want
to use in your report mask.
You can use the substitution variables to merge information relating to the task you are working on
from the project, task and requester files. This might include dates, durations, names, phone numbers,
fax numbers, and so on. The variables must be preceded with .&. For example, to print the text
details, you would use the variable name .&DTLS. Press the Help key (Scroll lock on a PC) on any
of TURNOVER for iSeries v100s Word processing panels for more information, and to see a list
of all the available substitution parameters.
If your company has one of the many iSeries fax systems on the market, you can create a report mask
that merges all of the necessary information for a fax (Name, address, fax #, details, your name, and
so on). Also, by including the control statements for your fax system in the mask (on our system it is
**FAX .&FAX#), you can send the output directly to your fax queue and it will be sent automatically.
Page 9-101
1=Select
_
_
_
_
_
_
_
_
MSGID
ABC0001
ABC0002
ABC0004
ABC0005
ABC0007
ABC0010
ABC0101
ABC0111
ABC9999
F3=Exit
2=Change message
4=Delete message
Message text
Hey &RS. Deal with this problem (&PJ &TK &SK) now!
A priority &PY change request, &2, has been entered.
A priority &PY hardware problem, &2, requires your immediate atten+
A priority &PY hardware problem, &2,has been entered please look +
A priority &PY hardware problem, &2, has been entered.
A priority &PY software problem requires your immediate attention.
A priority &PY problem has been entered. Please review ASAP!
Task &PJ &TK &SK has been completed by &RS with aplomb!
No entry found in message table for task &PJ &TK &SK.
F6=Add message
F12=Cancel
This message file contains messages by project and priority to be sent to the project coordinator when
a task is entered, or to others during escalation processing.
From this panel you can view, add, change, and delete all of the messages in the message file.
You can also refer to and use messages when setting up the projects escalation rules. For more
information, see The escalation table on page 9-80.
These messages are similar to iSeries messages, but are not stored in standard message files.
Press F6 to add a message, or type 2 next to a message you want to change.
Page 9-102
Add a Message
Message ID . . . . . . ABC0001
Message text . . . . . Hey &RS. Deal with this problem (&PJ &TK &SK) now!_____
________________________________________________________________________________
________________________________________________________________________________
__________________________________
Substitution parameters:
&PJ = Project
&TK = Task
&SK = Subtask
&RS = Resource
&RQ = Requester
&PY = Priority
&ST = Status
&RF = Project/Task/Subtask (Reference)
&DN = Date needed
&DP = Date promised
F3=Exit
F12=Cancel
&U1
&U2
&U3
&U4
&U5
&U6
&U7
&U8
&U9
&U0
=
=
=
=
=
=
=
=
=
=
User
User
User
User
User
User
User
User
User
User
field
field
field
field
field
field
field
field
field
field
1
2
3
4
5
6
7
8
9
10
F21=System command
You can include any of the substitution parameters shown in the message text, as shown in the
example.
Page 9-103
3=Copy
Table
FTPR
HELPDESK
SLS
TEST
WORKING
6=Print
12=Work with
Description
Queue created for project: FTPR
Escalation Table for Helpdesk Projects
SoftLanding Internal Escalation Table
Escalation Table for Testing
Escalation Table for Working Projects
Bottom
F3=Exit
F12=Cancel
F21=System command
Escalation tables can be defined globally using this panel, and then applied to one or more projects.
For example, you might have two escalation tables defined, one to be used for Helpdesk project, the
other for Working projects. If you used task status and priorities consistently for all of your projects,
two definitions would work best.
Select a table with option 2 to change its title. Select it with option 12 to work with the rules in the
table.
1/29/10 16:56:46
Table: HELPDESK
2=Change
_
_
_
_
_
_
_
_
_
_
_
_
3=Copy
Pty Status
A ASSIGNED
1 N NEW
2 N NEW
3 N NEW
4 N NEW
R REJECTED
1 U URGENT
2 U URGENT
1 V REVIEWED
2 V REVIEWED
3 V REVIEWED
4 V REVIEWED
F2=Print listing
Page 9-104
4=Delete
Aging
Rpt
N
N
Y
Y
Y
N
N
Y
N
Y
Y
Y
F3=Exit
6=Command
Alarm
Interval
48
24
2
4
Hrs
Hrs
Hrs
Hrs
24
4
7
2
1
4
Hrs
Hrs
Days
Days
Days
Hrs
7=Messages
Repeat
Alarm
N
N
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
F12=Cancel
Bottom
F21=System command
For a discussion about how this escalation table works, see the Task escalation processing section on
page 9-77.
Each table entry is keyed by Task status and Priority.
Type 3 next to an entry to copy it into a new entry. Press F6 to add a new table entry.
Actions can be defined to change (escalate), the task by changing the Task status or Priority, send
messages to one or more individuals or groups and/or run a command.
Select an entry with option 6 to define a command that should run when the escalation Alarm [time]
interval has passed.
Page 9-105
To work with commands that associate actions with task status, select a table entry with option 6.
This panel appears:
1/29/ 10 13 :01:5 5
Des cript ion: Escal ation Table for Helpd esk Pr oject s
2 =Chan ge
Se q
10
4 =Dele te
Cm d Ac t
En v Co de
I
N
Comman d to execu te
TPRTTS K TAS K("&R F") M ASK(*S ELECT ) FAX (*YES )
Bo ttom
F 3=Exi t
F6 =Add messa ge
F1 2=Can cel
Sequence . . . . . . . . . . . . . . . . .
Restrict command to escalation action:
N
Restrict command to execution environment: I
20
N=New, A=Alarm, E=Escalation
I=Interactive, B=Batch, A=All
F4=Prompt command
Substitution parameters:
"&RF" = Project/Task/Sub (Reference)
"&PJ" = Project
"&TK" = Task
"&SK" = Subtask
"&PT" = Priority
"&RS" = Resource
"&RQ" = Requester
"&Un" = User field 1-10 n=1-0
F3=Exit
F4=Prompt command
F12=Cancel
F21=System command
Commands can include any of the substitution parameters listed on the Add and Change panels.
Press F4 to prompt the command.
Page 9-106
If N (New), the command runs only when a task that matches the Task status and Priority defined
for the associated escalation table entry is added to the project.
If A (Alarm), the command runs when a task has been on the escalation queue beyond the Alarm
interval.
If E (Escalate), the command runs when a task has been on the escalation queue beyond the
Escalation interval.
Restrict command to execution environment controls whether the command can be run only in batch,
only interactively or both. For example, if the escalation-processing program that runs in batch was
processing an escalation queue entry, it would bypass any command that was set to I (interactive
only). However, if the command were being run when the task was being interactively added to the
project, then the command would run. In the example above, the TPRTTSK command is a
TURNOVER for iSeries v100 Projects command that will prompt the user (interactively) to select a
task report format from a list of predefined report masks. This is a real example of how you might
use this command feature. The command is run when a new Helpdesk task is added to a Helpdesk
project. At UNICOM Systems, Inc., the report we run generates a confirmation fax that we send to
the customer who reported a problem or entered a request on our system. This is one example of the
many ways you could use this command feature.
The TUPDHLPTSK command is another command that youll typically use in an escalation table.
This command enables you to update the Helpdesk tasks that are associated with a Working task.
With this command, you can synchronize the information for a Helpdesk task with the values of its
associated Working task. For example, when the status of the Working task changes to ASSIGNED
or DONE, TURNOVER for iSeries v100 will update the basic Helpdesk task information so it
matches the Working task information. You can optionally have TURNOVER for iSeries v100
update the task details also.
When using this command in an escalation table, you should use the &RF substitution parameter to
specify the Working task. The entry for this command looks like this:
Page 9-107
Sequence . . . . . . . . . . . . . . . . .
Restrict command to escalation action:
N
Restrict command to execution environment: I
20
N=New, A=Alarm, E=Escalation
I=Interactive, B=Batch, A=All
Page 9-108
F4=Prompt command
F12=Cancel
F21=System command
One Action that can occur when a task is added to a project, or when the Alarm or Escalation interval
has passed is to send a message to one or more users or groups. You accomplish this by associating
messages youve defined in the Project Message Control File with specific escalation table entries.
To do this, select an escalation table entry (see the panel on page 9-104) with option 7. When you
press Enter, this panel appears:
1/29/10 10:34:00
Table: HELPDESK
Priority:
Status: A ASSIGNED
2=Change
3=Copy
4=Delete
USRPRF
Seq MSGID
or Method
10 PRJ0001 *MAPI
20 PRJ0002 PSCHMIDT
User-ID/Address
or E-mail Address
Marylyn Schoop
Pablo Schmidt
Act.
Code Message text
A
Task &RF has been entered,
A
Task &RF has been entered,
Bottom
F3=Exit
F6=Add message
F12=Cancel
F21=System command
In this example, two different alarm messages will be sent when the Alarm interval has passed. You
can also have messages sent as soon as the task is added to the project or later, after the Escalation
interval has passed. Press F6 to add a new message entry.
Each message has specific delivery options that identify the recipient.
1/29/10 10:41:38
Message ID . . . . . . . PRJ0001
Sequence . . . . . . . .
20
Message text . . . . . .
. . . . . .
User ID . . . . . . . . .
Address . . . . . . . . .
Action code . . . . . . . N
N=New
A=Alarm
E=Escalation
F3=Exit
F4=List
F12=Cancel
Page 9-109
Note that you can press F4 to see a list of messages and, if necessary, maintain that list from that
panel (not shown).
You can choose one of these delivery methods:
*STD
The remaining fields on the panel vary according to which method you choose. When you press
Enter after typing a method, fields appear that apply to the method you chose. For more information,
read the online Help.
Rather than type a specific user profile name in the User profile and User ID fields, we recommend
that you use one of the variables, *RSRC, *RQST, or *COORD. This will substitute the Task
Resource, Task Requester, or the Project Coordinator or Administrator (respectively) to be the
recipient of the message.
The Action code controls when the message should be delivered: at the moment the task is added to
the project (N); when the Alarm interval has passed (A); or when the Escalation interval has passed
(E). If the same person is to be notified at more that one of these events, you need more than one
message entry.
Page 9-110
You can define *MAPI escalation messages to use a report mask for determining their message
content. This technique lets you include the task details in your message, as well as any other task,
requester, resource, or utility information.
Suppose, for example, that you want the notification message you receive from TURNOVER for
iSeries v100 each time a programming task is entered to contain the task details of the new task.
Instructions for doing this follow:
1. Create or copy a report mask, giving it a name like PRGNEW, which contains information such as
the task reference number and task details.
2. Create a new message in the escalation message file that uses the new report mask as its message
text. For example, you could create a message PRG0001 and give it a message text of
*PRGNEW. By doing this, you refer to the new report mask described in the previous step.
3. Add the new message to the appropriate escalation table entry for your project. Continuing with
our example, you could add the PRG0001 message to an escalation table entry called PRGTABLE
that controls what happens when a programming task has an A (Assigned) status. You could
specify *MAPI for the delivery method, press Enter, and then use the *RSRC variable for the
email address.
The result of this escalation table entry is that, when you or someone else assigns a new
programming task to a resource, TURNOVER for iSeries v100 sends an Internet email message
to the resource. The message contains the task details that the resource needs to promptly begin
the task.
Page 9-111
4=Delete
Description
Do later
Obsolete code
Normal resolution
Bottom
F3=Exit
F6=Add code
F12=Cancel
F21=System command
All reason codes are valid for all projects and applications.
To delete a code, select it with option 4. A confirmation panel appears; press Enter to delete.
Page 9-112
Resource . . . PShultz
Date . . . . . 9/08/06
Phil Shultz
Friday September 8, 2006
Sub Cat.
Project Task Task Code
_
_
_
_
TE31
TE31
TE31
TE31
0001
0001
0001
0001
01
02
03
03
P
P
P
R
-------Time------From - To Total
08:0012:0013:0015:00-
12:00
13:00
15:00
17:00
Comment
4:00
1:00
2:00
2:00
Bottom
Total time for day . . . . . . . 9:00
F3=Exit
F4=List
F12=Cancel
F17=Previous day
F18=Next day
To add an entry, type 1 and type the information for the underlined fields or press F6 to use the Add
Time Sheet Entry window. (This panel is the same as Change Time Sheet Entry; see samples on
next page.)
To change an entry, select a time entry with option 2.
You can position to the Project, Task, or Subtask field, and press F4 and view the lists of projects
tasks from which to select. A window appears containing this information.
You can position to the Cat. Code field and press F4 to view the list of valid Category codes.
Note that either the From or To times or the Total time should be entered. If the From and To times
are entered, the Total time is calculated for you.
Page 9-113
Select option 2 and view this window to change the time entry:
1/29/10
10:52:24
Resource . . . PSHULTZ
Date .
Phil Shultz
Change Time Sheet Entry
1=Add T
Resource . . . SHULTZ
Proj
TE31
TE31
Date . .
Project
Category
Comment
.
.
.
.
.
.
.
.
.
.
.
.
From time . .
To time . . .
--or-Total time . .
F3=Exit
F4=List
Phil Shultz
12 : 00
14 : 00
02 : 00
HH:MM
F12=Cancel
F3=Exit
Page 9-114
Press Enter to change the entry; press F3 or F12 to exit back to the Work with Time Sheets panel.
00:00:00
Task/
Subtask Date
Comment
3/30/93
0032
4/13/93
0105
2/11/93
0105
2/11/93
0105
2/12/93
0105
2/12/93
0105
2/12/93
0129
3/15/93
-------Time------Resource
From
EDELLIS12:00 14:00
PSCMIDT8: 00 10:00
SUEMRKS
3:00
SUEMRKS
30
SUEMRKS
40
SUEMRKS10:10 10:20
SUEMRKS12:00 13:00
SUEMRKS
30 P
Total time
F3=Exit
Resource : __________
To
Cat: _
Total
F4=List
Cat
2:00
T
Test
2:00
A
PChanged USRTOOL Pgms
P
TTesting
10
T
Testing
1:00
P
Testing DDS
Chg'd TURRFAPS
10:55
F4=List
F12=Cancel
Several reports also include time information. Time can be reported by project on the Project
Timesheet Report and by resource on the Project Resource Time Report. If youve included Rate in
your Programmer Profile records (see Chapter 2: Setting Up Programmer Profiles), you can also
see projected and reported costs in the Project Cost Report (see Chapter 10: TURNOVER for
iSeries v100 Reports).
Page 9-115
68 For a complete discussion of PWM, see the TURNOVER for iSeries v100 Developers Guide.
Page 9-116
Position to Worklist . . . .
Filter by Programmer . . . . PSCHMIDT
Filter by Appl rel ver . . .
F3=Exit
F4=List
F5=Refresh
F6=Add
F7=Previous Worklists
F24=More keys
You can type 1 to select a worklist, or press F7 to view the four most recent worklists and then press
Enter to transfer to the last one you worked on.
Note that the STRPWM command also has a LIST parameter that defaults to *SELECT. You can
type a specific worklist name or *PRV to select the last worklist you used, in which case youll
bypass this panel and go directly to the next one.
Page 9-117
8:53:31
Worklist. . . . . APPR0003
Position to . . .
The + after the checkout flag indicates that the item is checked out to more than one person.
Page 9-118
The key to using the worklist panel effectively is to use the filter fields; youll find the next option,
level (*DEV, *PROD, or the target application level code) and item status filters especially useful.
To set filters or change subfile sequence, press F17=Filters. Youll see this pop-up panel:
1/29/10 20:20:29
Work with Programmer Worklist
Your Company, Inc.
...............................................................................
:
:
:
Type filter value and Press Enter.
:
:
:
: Next option . . . __
F4=List
:
: Library . . . . . ___________
Library name, generic*
:
: Level . . . . . . _____
number, *DEV, *PROD
:
: Appl rel ver . . . ____ __ __
F4=List
:
: Programmer . . . . ___________________
F4=List
:
: Item status . . . _______
:
: Object type . . . ______
:
: TurnOver Type. . . ______
F4=list
:
: Checked out . . . ___
Y, N, blank
:
:
:
:
F3=Exit F4=List
F12=Cancel
:
:
:
:
:
...............................................................................
Parameters or command
===> _________________________________________________________________________
F2=Forms
F3=Exit
F4=Prompt
F5=Refresh
F6=Add item
F9=Retrieve
F10=Command entry
F11=View2 F19=Batch 21/46 F23=More options F24=More keys
If youre viewing the PWM on line, experiment by adding items to the list, using the filter-by fields
and looking at the alternate views (F11). Press F1/Help for more information. (You wont be able to
do anything that youre not authorized to do on your system.)
Session defaults let you set your Programmer Worklist options the way that works best for you.
Press F18=Defaults to view and set other personal session preferences. Youll see this pop-up panel:
1/29/10 11:08:36
Work with Programmer Worklist
Your Company, Inc.
...............................................................................
:
Change Session Defaults
:
:
:
: Save session defaults . . . . . . . Y
Y, N
:
*BATCH, *INTER
:
: Default option 21/46 mode . . . . . *INTER
: Edit/compile authority . . . . . . *DEVELOP
*SYSAUTH,*DEVELOP,*CHECKOUT :
:
:
: Test object creation parameters
:
:
Link option 36 compiles . . . . . Y
Y, N
:
:
Job description . . . . . . . . . *USRPRF
*USRPRF, name
:
:
Library . . . . . . . . . . . .
Library name
:
:
Job queue . . . . . . . . . . . . *JOBD
*JOBD, name
:
:
Library . . . . . . . . . . . .
Library name
:
:
Output queue . . . . . . . . . . *JOBD
*PGMR, *JOBD, name
:
:
Library . . . . . . . . . . . .
Library name
:
:
Library list . . . . . . . . . . *APP
*APP, *CURRENT
:
:
Replace object . . . . . . . . . N
Y, N
:
:
More...
:
: F3=Exit
F12=Cancel
:
:
:
:
:
:.............................................................................:
Page 9-119
Page down...
1/29/10 11:08:36
Work with Programmer Worklist
Your Company, Inc.
...............................................................................
:
Change Session Defaults
:
:
:
: Save session defaults . . . . . . . Y
Y, N
:
:
:
: List sequence . . . . . . . . . . . *OBJECT
*OBJECT, *LIBRARY, *TYPE... :
: User option file . . . . . . . . . TUSROPTF
File name
:
:
Library . . . . . . . . . . . . . T51QAD
Library name
:
: Position-to default . . . . . . . . *ITEM
*TOP, *ITEM
:
: Show perm-lock levels . . . . . . . N
Y, N
:
:
:
: Require X-Ref check . . . . . . . . N
Y, N
:
: X-Ref automatic . . . . . . . . . . Y
Y, N
:
: Option 15 library to X-Ref . . . . *ALL
*SELECTED, *ALL
:
: Require Related apps check . . . . N
Y, N
:
: Related apps check automatic . . . Y
Y, N
:
:
:
:
More...
:
: F3=Exit
F12=Cancel
:
:
:
:
:
:.............................................................................:
Page down...
1/29/10 11:08:36
Work with Programmer Worklist
Your Company, Inc.
...............................................................................
:
Change Session Defaults
:
:
:
: Editor defaults
:
:
Edit source . . . . . . . . . . .
*SEU, *CODE400
:
:
Browse source . . . . . . . . . .
*SEU, *CODE400
:
:
Designer . . . . . . . . . . . .
*SDA, *CODE400
:
:
Debugger . . . . . . . . . . . .
*OS400, *CODE400
:
:
:
:
Code communications library . . .
*USRPRF, Name
:
:
Code server name . . . . . . . .
*DFT, Name
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Bottom
:
: F3=Exit
F12=Cancel
:
:
:
:
:
:.............................................................................:
If you sequence by *LIBRARY, the sort key will be library, object, and type.
If you sequence by *OBJECT, the sort key will be object, type, and level.
If you sequence by *CRTSEQ, the sort key will be create sequence, object, type, and level.
If you sequence by *TYPE, the sort key will be type, object, library, and level.
When you press Enter, youll see the worklist again with objects displayed in the sequence you
chose.
Page 9-120
You can specify how your test objects are to be created, including whether or not TURNOVER for
iSeries v100 should use the application library list, what job description it should use, where it should
be submitted, and where compile output should be placed.
These session defaults are saved for each user. When you create a new worklist, the last settings are
applied to the new worklist.
When you press F11=View2, youll see this alternate view:
1/29/10
20:20:29
Worklist . . . . APPR0003
Position to . . .
Chk Chk
Lv Xrf Rel
01 Y
02 Y
N
01 N
N
02
01
Y
N
N
N
02
01
N
N
N
N
More...
Parameters or command
===> _________________________________________________________________________
F2=Forms
F3=Exit
F4=Prompt
F5=Refresh
F6=Add item
F9=Retrieve
F10=Command entry
F11=View3 F19=Batch 21/46 F23=More options F24=More keys
The fields Chk Xrf and Chk Rel tell you whether you have checked the cross-reference file for
dependent objects and whether youve checked for related objects in related applications,
respectively. Both of these are explained more completely later in this section. Press F11=View3 to
see the third worklist display format:
1/29/10
20:20:29
Worklist. . . . . APPR0003
Position to . . .
__
__
__
__
__
__
__
__
__
Object
APCLP001
APCLP001
APCLP001
APDSPF01
APDSPF01
APDSPF01
APRPG001
APRPG001
APRPG001
Attr
CLP
CLP
CLP
DSPF
DSPF
DSPF
RPG
RPG
RPG
12=Compare source
24=Checkin 25=Task details
Item
Description
Programmer
Test item 1 desc
PSCHMIDT
Test item 1 desc
PSCHMIDT
Test item 1 desc
PSCHMIDT
Test display file desc
PSCHMIDT
Test display file desc
PSCHMIDT
Test display file desc
PSCHMIDT
Test RPG program desc
PSCHMIDT
Test RPG program desc
PSCHMIDT
Test RPG program desc
PSCHMIDT
ProjRef
APPR0212
APPR0212
APPR0212
APPR0212
APPR0212
APPR0212
APPR0212
APPR0212
APPR0212
More...
Parameters or command
===> _________________________________________________________________________
F2=Forms
F3=Exit
F4=Prompt
F5=Refresh
F6=Add item
F9=Retrieve
F10=Command entry
F11=View1 F19=Batch 21/46 F23=More options F24=More keys
Page 9-121
Why show objects that do not exist? By showing all objects at each level, you can see the progress
of your work from development through to production. You can tell exactly where your objects are,
no matter how many levels you use for your application.
Referring to the PWM panel, you can press F6 to add additional items to your worklist; or you can
select other options to scan and select items to include on your worklist. For information about
setting up user-defined options to use in PDM, or other documentation or cross-reference tools, see
Using TURNOVER for iSeries v100 with PDM in the Advanced Topics section of the
TURNOVER for iSeries v100 Developers Guide
For example, you can press F20 to start PDM. Then, in PDM you can use option AW (Add to
Worklist; as defined in TURNOVER for iSeries v100s user option file
SOFTTURND/QAUOOPT) to add items to your list. As you browse objects and source files, you
can continue to add items to the list by selecting them with the AW PDM option. As with PDM,
you can also do the same with TURNOVER for iSeries v100s view cross-reference, with
Pathfinder and with Abstract/Probe+.
When you return to PWM, each of the items you selected will appear. You can continue to build
your list by pressing F6=Add to add new objects (those you intend to create) or by removing others
after you analyze them further.
For example, you may have included all items that referred to the Vendor file. Then, after analyzing
the programs, you may have removed from the list those that did not refer to the vendor payment
terms field.
Incidentally, notice that the PWM panel tells you if the object and source actually exist in any of the
libraries associated with the application with which you are working.
As the sample shows, the PWM panel lets you position, filter by, and perform many development and
change management functions. For a complete explanation of all of these functions, see Working
with PWM in the Advanced Topics section of the TURNOVER for iSeries v100 Developers
Guide. Now read the following section, where youll find a wealth of other useful features.
Page 9-122
1=Compare interactive
_
_
Member
__________
APCLP001
Member . . . . APCLP001
File . . . . QCLSRC
Library . . . . PRODTEST
2=Compare in batch
File
__________
QCLSRC
Library
__________
DEVTEST
You can select one of the items on the list or type in another member and its file and library names.
Press F1/Help for more about other things you can do on this panel.
Page 9-123
09:16:50
Worklist . . . . APPR0003
Position to . . .
(F17=Filters)
15=Check X-Ref
32=Edit source
Now you type option 15=Check X-Ref next to the items you want to check and press Enter.
69 If you use TURNOVER for iSeries v100s cross-reference, you will see the cross-reference panels displayed below; otherwise you will see your
vendors cross-reference panels. In that case, you can use user-defined options to add related items to your Programmer Worklist.
Page 9-124
Youll then see the Work with Cross-Reference panel, which includes all of the objects related each
of the items you selected:
1/29/10
Worklist
Data set
09:46:14
. . . . APPR0003
. . . . ACCTGSYS
In this example, we selected a logical file, a physical file and a program from the worklist.
1. The logical file is used by six programs.
2. The physical file is used by the logical file and two programs.
3. The program calls three programs.
You can press F17=Filters (not shown here) to display a panel on which to set filters on these
conditions:
Show only items that use or items that are used by the reference items;
If you want to add objects to your worklist, type 1 next to each one and press Enter or use option 2 to
add them to the Programmer Worklist and also check them out. If you want to compile related
objects objects that you dont need to change but need to test into your development library, select
it with option 4. The object(s) will be created in the development library identified for that
applications first level. If *PGMR is specified, then into your own development library. Options 1
and 2 can be submitted to batch by pressing F19. Option 4 is always submitted. You can prompt
options 1, 2, and 4 by pressing F4.
Page 9-125
You can determine if an item listed uses other items, or is used by other items, by selecting it with
option 6. For example, suppose you were researching a physical file that you had placed on your
worklist. When you reach this panel, you might then see related logical files and programs that refer
directly to the physical file. If you type 6 next to one of the related logical files, you would see all of
the programs that refer to that logical file. If you type 6 next to one of the programs, you might see
another program that calls that program. This way you can drill-down to see all of the objects that
might be affected by the pending file change. Each time you see a dependent object, you can add it to
the list. This way, you can be sure that your analysis provides you with a complete picture.
Each time you use option 6, the X-Ref depth field advances to indicate how far you have drilled
down.
If you select option 6 again on the X-Ref depth 02 panel, the X-Ref depth becomes 03, and so
on.
Once you go beyond the first depth of dependencies, F12 will return to the previous depth; F3 will
return to your Programmer Worklist.
The cross-reference check will also show any logical files that are built over any physical files on the
form. You can add these logical files to the form so that they will be recompiled in the test
environment. Be aware, though, that any programs that use a logical file you add from the crossreference selection panel are not added automatically. You must edit the form and recheck the crossreference file for programs related to the additional logical files.
A logical file is automatically added to the form if it exists in the target library for the form you are
creating. In that case, any programs that use the logical file will be found by the cross-reference
check because the additional logical file will be added to the form before the cross-reference check
occurs.
If an object you need to change is currently checked out to someone else, then you can read the
checkout information to find out more about when, and by whom, it was checked out. Depending on
whether the multiple-checkout feature is enabled, you might then decide to check it out. Otherwise,
you might want to coordinate your changes with the programmer who already has it checked out.
Note that you can add an item to your Programmer Worklist, whether it is checked out or not.
You should only add items to the worklist that you intend to change. If you intend only to have the
item recompile when you promote it, as in the case where you change a file and want only to
recompile dependent programs to avoid level checks, TURNOVER for iSeries v100 will prompt
you to recompile these objects later, when you add the items to your TURNOVER for iSeries v100
form.
Page 9-126
When you add an item to your programmer worklist from the Work with Cross-reference panel, it
will set the X-Ref checked indicator for that item to Y. (See What happens if you forget to check
cross-reference? on page 9-127.)
What happens if you forget to check cross-reference?
TURNOVER for iSeries v100 maintains a field for each worklist item that is set on when you select
option 15=Check X-Ref on the Programmer Worklist.
If cross-reference information exists in the cross-reference database for any item on your worklist,
and you forget to check the cross-reference file during development using option 15, then
TURNOVER for iSeries v100 will remind you to check when you add the item to the
TURNOVER for iSeries v100 form using option 46. After you check, TURNOVER for iSeries
v100 will set the Cross-reference checked indicator to Y. TURNOVER for iSeries v100 will not
allow you to add an item to a TURNOVER for iSeries v100 form, interactively or in batch, if the
Cross-reference checked flag is N.
You can set this Cross-reference checked flag manually with the Change Worklist Item
(CHGPWLITM) command (option 2 on the worklist), if you want.
Recompiling related items that did NOT change
Suppose you checked the cross-reference database earlier and decided that no other related items
needed to be changed. (That is, you didnt add these items to your Programmer Worklist at that
time). Now you are ready to promote your changed objects. When you add the worklist items to a
TURNOVER for iSeries v100 form, TURNOVER for iSeries v100 will let you add the unchanged
related objects to your TURNOVER for iSeries v100 form to be recompiled. They will be
recompiled from source in the applications target library or a library at a higher level.
As explained below, the process of adding items works differently when done interactively or in
batch.
Adding items to the form in batch
If cross-reference information exists in the cross-reference database for any item on your worklist,
and you forget to do a cross-reference check (using option 15), then TURNOVER for iSeries v100
will add the item to the TURNOVER for iSeries v100 form when you select it with option 46=Add
to form and press F19=Batch 21/46 to build the form in batch (as you would do if you had several
items on the form). To avoid having cross-reference items added automatically in this fashion, add
the items to your form interactively. An alternative is to delete some of the reference items from the
form afterwards.
Page 9-127
If cross-reference information exists in the cross-reference database for any item on your worklist,
and you forget to do a cross-reference check (using option 15), then TURNOVER for iSeries v100
will remind you to do so at the time you add the item to the TURNOVER for iSeries v100 form
when you select it with option 46=Add to form (interactively).
If cross-reference information exists and has not been checked, then you will not be able to add the
item to a TURNOVER for iSeries v100 form until you either select the item with option 15 to check
cross-reference information, or set the Cross-reference checked indicator to Yes.
1/29/10
Worklist
Data set
09:46:14
. . . . APPR0003
. . . . ACCTGSYS
You can avoid a recompile of these related objects by de-selecting them. If added to the form, the
items will be recompiled in the target libraries using the source found in the target source library. If
an item had been added to the worklist, but never checked out, it will also be recompiled from target
source.
Only physical-to-logical file, file-to-program and program-to-module relations 70 will be included on
the Work with Object Cross-Reference panel. If a logical file is selected, then that files relatives (that
is, programs that use the logical file) are also displayed so you can include those items on the
TURNOVER for iSeries v100 form.
70 The cross-reference method table contains an indicator that determines what type of relationships are to be automatically added to a form and in what
order they are to be added (LF first, then modules, then programs).
Page 9-128
If you or TURNOVER for iSeries v100 need to add a related cross-reference item to a form for a
different application than the primary worklist application, then TURNOVER for iSeries v100 will
create a new form and add the related item to that form (see the Caution! that follows). If this is done
interactively, then you will see a message informing you that a related form has been created. If done
in batch, the log report will indicate that TURNOVER for iSeries v100 has done this. The related
application forms will be dependent on your primary form and cannot run unless the primary form has
run successfully. If you run all of the forms as a group, then the rules that apply to running group
forms apply. 71
If an item is already on your Worklist, then TURNOVER for iSeries v100 assumes you have added
it or will be adding it to a form in the standard manner. You will not be able to select it here.
If you add items to the TURNOVER for iSeries v100 form in batch, then TURNOVER for iSeries
v100 will add items to the form automatically. If, for some exceptional reason (see the Caution! that
follows), you do not want the cross-reference items on the form, you can delete them from the form
after it is created. If you do not want the cross-reference items on the form, we suggest that you add
items to the form interactively rather than in batch.
UNICOM Systems, Inc. Caution!
Do you use one production library for more than one application? When TURNOVER for iSeries
v100 detects a related object in the cross-reference, it adds it to the same TURNOVER for iSeries
v100 form or, if it is in another application, to a new form. Which application to use is not always
clear when more than one application uses the same target library. TURNOVER for iSeries v100
first looks at its own history database to determine the correct application. If TURNOVER for
iSeries v100 cannot determine the application in this way, TURNOVER for iSeries v100 assumes
that it is part of the first application it encounters for which a matching target library was found. In
some cases, it wont really matter and the object will be recreated correctly. However, if it does
matter, we recommend that you build a form interactively so that you will see a panel that lets you
determine the correct application interactively.
71 For more about running group forms, see the section entitled Submitting a Group of Forms to Run Together in Chapter 7.
Page 9-129
We recommend that you use the Programmers Worklist; however, if you do not use it, then
TURNOVER for iSeries v100 will prompt you to check the cross-reference database when you
checkout an item and again when you edit your TURNOVER for iSeries v100 form, to ensure that
you do not overlook anything.
Editing your TURNOVER for iSeries v100 form
If you build a TURNOVER for iSeries v100 form from a Programmers Worklist, then the Check
cross-reference file for related objects prompt on the Form Maintenance Exit options panel will
default to N. If you do not use the Programmer Worklist and there are files on the TURNOVER for
iSeries v100 form, then this will default to Y. However, if you chose to edit a form, the exit options
will work the same, no matter how the form was created.
If you set Check cross-reference file for related objects to Y, then youll see the Work with Object
Cross-reference panel, as described earlier.
Page 9-130
15:39:12
. . . . TP400060
1=Add to Worklist
Member
_ SDRWRKLU
_ SDRWRKLU
_ SDRWRKLU
F3=Exit
Attr
RPG
RPG
RPG
F4=Prompt
2=Add to Worklist/Checkout
--------Base-------Appl Rel Ver Lev
SDU
2
SDU
2
SDU
2
F11=Alt. view
8=Browse base
9=Browse related
F12=Cancel
F19=Submit 1/2
Bottom
F21=Commands
If you want to add objects to your worklist, type 1 next to each one and press Enter or use option 2 to
add them to the Programmer Worklist and also check them out. Options 1 and 2 can be submitted to
batch by pressing F19. Options 1 and 2 can be prompted by pressing F4.
Press F11 to see an alternate view that contains source file names, library names and checkout
programmer name.
Page 9-131
If you add an item to your worklist using option 1 or 2, and if you have nested related applications,
then TURNOVER for iSeries v100 will display related items in the nested application(s). The
Depth indicator at the top of the panel reflects how many nested levels you have. For example,
suppose you are managing two releases of your software and have defined them as APPL Release 1
and APPL Release 2. You can relate these applications. You would probably related APPL Release
2 to APPL Release 1, referred to as the Base. If you maintain custom modifications for each of these
one set of modifications for Release 1 and two for Release 2 then you can relate these
modification applications to whichever Release they apply. Then you will see any object of the same
name that resides in any of the related application libraries as you drill down through the nested
applications.
APPL Rel 1
(Base)
APPL Rel 2
(Related and
Base)
MOD1 Rel 1
(Related)
MOD2 Rel 2
MOD3 Rel 2
(Related)
If you do use the related applications feature, then we recommend that you check for related
application objects (option 16) and add them to your worklist (if necessary), before you check the
cross-reference database (option 15).
Note that, because the related object is associated with another application (related to the base
application), each item you add to your Programmer Worklist will be associated with a separate
application. The project definition associated with the worklist must have all of the applications in its
related application list. Later, when TURNOVER for iSeries v100 forms are created using option
46, one TURNOVER for iSeries v100 form will be created for each application represented on the
Programmer Worklist.
Page 9-132
TURNOVER for iSeries v100 maintains an indicator for each worklist item that is turned on when
you select option 16=Related object on your Programmer Worklist. You can set this Related
application checked indicator with the Change Worklist Item (CHGPWLITM) command
(Programmer Worklist option 2).
If related applications exist for any item on your Programmer Worklist (as determined by the item
application) and you forget to check for related objects, then TURNOVER for iSeries v100 will
prevent you from adding the item to a TURNOVER for iSeries v100 form with option 46=Add to
form until you check for related applications or turn on the Related application checked indicator.
Adding items to the form in batch
If objects exist in a related application for any item on your worklist, then TURNOVER for iSeries
v100 will create a form automatically when you select the object with option 46=Add to form and
press F19=Batch 21/46 to build the form in batch (as you would do if you had several items on the
form). To avoid having forms created for related applications, add the items to your form
interactively. Youll then see a panel on which you can void the creation of forms for one or more of
the related applications. An alternative is to delete the related items from the forms afterwards.
Page 9-133
The objects listed below have been turned over by other programmers while
checked out to PSCHMIDT
Changes made by those programmers must be
included in changes made by PSCHMIDT
Position to object . . . . __________
Filter by programmer . . . __________
Filter by reference . . . __________
Type options, press Enter.
1=Approve 4=Cancel approval 5=View form 7=Project details
Run
Object
Library
Type
Programmer
Form
Date
Reference Approved
_ APRPG001
PRODTEST
RPG
SMITHRAY
100021 042194 APPF0002
F3=Exit
F5=Refresh
F12=Cancel
F14=Display all
This panel will not appear if no items where promoted while you were working on the item.
If one or more items were changed and promoted while you were working on them, then you must
merge those changes with your own, or using TURNOVER for iSeries v100s source merge
command, test them and then certify that you have done so by selecting option 1=Approved on the
this panel.
Page 9-134
PROJECT REPORTS
There are many reporting options you can use to retrieve and report all of the project and task data in
a variety of ways. Each report option includes a command prompt to help you specify the breadth and
depth of information you need. Each report, described briefly below, is illustrated with an example in
Chapter 10: TURNOVER for iSeries v100 Reports.
Task Aging Reports
Provided in detail and summary formats, this report contains information about how long any
task has been on your system.
Project Description Report
Provides a listing of the project definition information.
Escalation Table Listing
Shows the contents of the escalation table, along with associated commands and messages.
Project Task Report
Provided in detail and summary formats, this report contains information about how long a
request, problem (any task) has been on your system.
Project Time Resource Report
Summarizes the time reported for any resource or for all resources, within date ranges for all
or some projects. Sequence is resource within project.
Projects and tasks by priority
Lists tasks in priority order, by resource or for all resources. You can also specify priority,
status, and task ranges.
Project Time Report
Summarizes the time reported for tasks or projects, within any date range. Sequence is project
and task.
Project Cost Report
Lets you report project costs, based on time reported and programmers rate, of task within
project. Reporting can be limited to specific date ranges, resources, and requesters.
Programmer Worklist listing
Lists the contents of your programmer worklist.
Other Reports
Most reports, such as the Object History Report let you select by project task reference to see
objects changed to complete a particular task or request.
For more about reports, see Chapter 10: TURNOVER for iSeries v100 Reports.
Page 9-135
WISEDESK
The Wisedesk feature lets Helpdesk personnel interview TURNOVER for iSeries v100s project
system to find out whether a working task, problem report, or change request already exists for an
issue that someone is describing to them. It can also help users gather information from the project
tasks defined on your system to see how your projects affect each other.
Overview
Wisedesk lets you define logical views over your existing projects without creating a special
question and answer database. Although you can build a special project for this purpose and build a
Wisedesk decision tree over it, youll probably prefer to build decision trees over your existing
projects especially if you are already using TURNOVER for iSeries v100 Projects. The beauty of
Wisedesk is that you can build a decision tree over several projects, ensuring that every relevant task
is represented in the tree. Also, if one task matches the criteria of two or more categories, it will show
up in each related tree branch, even though it only exists once in the project database.
To use Wisedesk, you must build one or more help trees. A help tree is a group of related tasks that
are organized in a common-sense, level-oriented structure that you define. The levels in the tree
structure are called categories. The first level of categories in a tree are called root categories. Any
category can have one or more levels of its own, called subcategories. For example, you might have
a tree called Trees, with categories and subcategories like these:
Cortland
Trees
Fruit Trees
Apple Trees
Pear Trees
Plum Trees
MacIntosh
Granny Smith
The avenue of access through the layers of a tree into a specific category is called a path. The dotted
line in the diagram shows the path into the Cortland category. (Notice that the help tree name
Trees is not included in the path.) If you wanted to specify this path on a Wisedesk panel, you
would type:
/fruit trees/apple trees/cortland/
You tell TURNOVER for iSeries v100 how to group tasks into categories by supplying a set of
requirements, called selection criteria. During a build process, TURNOVER for iSeries v100
compares these criteria to values in the task definition, description and details, selecting for the
category those tasks that satisfy them and ignoring those that dont. Once youve built your trees, you
can view task lists by category to find out what work is under way for a given project, problem, or
change request.
Grouping tasks like this helps you find relevant information fast, so you can see if somethings
already been reported, determine whether a fix is available, or clear up confusion about how a product
feature is designed to work.
Page 9-136
You can access Wisedesk help trees from these key areas of the Helpdesk process:
1. Independently, by typing WRKHLPTREE on a command line.
2. From option 16 on the HELPDESK Work with Requesters panel, so you can select a requester
and search for answers to his or her questions and, if necessary, enter a request on the users
behalf.
3. Using F16 on Work with Tasks or Work with Projects panels within TURNOVER for iSeries
v100 Projects.
4. Using F16 from the task review panel or the Assign Task pop-up panel within WORKTASK, so
the reviewer can search for and locate existing duplicate tasks.
To create a tree, type WRKHLPTREE on a TURNOVER for iSeries v100 command line. Press
Enter. The Work with Help Trees panel appears:
1/29/10 14:40:07
F3=Exit
6=Print
7=Authorities
F5=Refresh
F12=Cancel
F21=System command
Page 9-137
Type option 1 and a tree name in the selection fields on the first row of the panel:
1/29/10 14:44:07
F3=Exit
F5=Refresh
F12=Cancel
F21=System command
Press Enter.
The Add Help Tree panel appears:
Add Help Tree (ADDHLPTREE)
Type choices, press Enter.
Help tree . . . . . . . . . . . > NEWTREE
Name
Description . . . . . . . . . .
New Help Tree
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Bottom
F13=How to use this display
This panel is the prompt for the Add a Help Tree (ADDHLPTREE) command. Type a description
for your new help tree and press Enter. The tree is created and the Work with Help Trees panel
reappears.
UNICOM Systems, Inc. Note
Another way to create a help tree is to use option 3=Copy to duplicate an existing tree. You can then
change the tree by giving it a different name and description, reassigning users authorities to it,
working with its categories, and so forth, as described in the remainder of this section.
Continue with the next step.
Page 9-138
On the Work with Help Trees panel, select the new tree with option 7=Authorities and press Enter.
The Wisedesk Authorities panel appears:
1/29/10 10:07:02
Tree: NEWTREE
User
*NONE
BERNEY
COMPARDI
BIANCHA
BLAIRE
ELLISMAN
GIBBONS
HOLMER
JSCHMIDT
KLINE
LEBLANC
MIKEPHIL
F3=Exit
Wisedesk Authorities
Name
Unassigned
Berney Fern
Roy Compardi
Biancha Jefferson
Blaire Peterson
Stephen Ellisman
Greg Gibbons
Denise Holmesby
Joan Schmidt
Sandy Kline
Louie LeBlanc
Mike Phillips
F12=Cancel
View
X
X
X
X
X
X
X
X
X
X
X
Work
with
X
X
X
X
X
X
X
X
X
X
X
Bld
X
X
X
X
X
X
X
X
X
X
X
Dlt
X
X
X
X
X
X
X
X
X
X
X
Match
Tasks
X
X
X
X
X
X
X
X
X
X
X
Exclude
Tasks
X
X
X
X
X
X
X
X
X
X
X
F21=Authorize all
The tree for which youre assigning authority is identified at the top of the panel.
People who will be repeatedly searching for information in the help trees on your system should have,
at a minimum, View and Match authority. People who will update the trees should have all
authorities.
For each user in the list, type an X in the column(s) representing the kind of authority the user
should have for this tree. Press Enter.
Review the results, and correct them if necessary. Press Enter, then F3 to return to the Work
with Help Trees panel.
Once the help tree is created and populated with task lists, your help desk users can begin using it to
locate information. Users can see task information only from projects that they are authorized to,
regardless of their authority to the tree.
(To learn how to use Wisedesk from a Helpdesk users point of view, read Finding information in a
help tree on page 9-146.)
Continue with the next step.
Page 9-139
Select your tree with option 12. The Work with Categories panel appears:
1/29/10 12:16:19
Bottom
F12=Cancel
F14=WRKSBMJOB
F20=Expand all F21=Command
Here you create your tree categories and supply criteria for selecting related tasks to include in the
categories task lists. At any time, you can add or change categories or subcategories, and then
rebuild them.
Press F6 to add a root category to your tree. The Add Category pop-up panel appears.
The Tree and Path fields at the top of the pop-up are informational, and show you where in the tree
the category will be added.
Type a category name and description, and press Enter. The Change Help Tree Category panel
appears:
1/29/10 14:44:45
Tree . . NEWTREE
Path . . /ROOT1/
2=Remove criteria
Page 9-140
F4=List
F10=Change description
F12=Cancel
Selection
Criteria
Defined
y
N
N
N
N
N
N
N
N
N
More...
F21=System command
*OR, *AND
Tree . . NEWTREE
Path . . /ROOT1/
2=Remove criteria
*OR, *AND
Selection
Criteria
Defined
N
N
N
N
N
N
N
Bottom
F3=Exit
F4=List
F10=Change description
F12=Cancel
F21=System command
Page 9-141
Use this panel to supply a set of requirements called selection criteria. TURNOVER for iSeries
v100 uses this information to choose from the database any tasks that relate to this category. There
are three kinds of selection criteria:
1. Project criteria identify to which projects a task must belong to be included in a category list.
2. Task criteria identify values that a task must match to be included in a category list.
3. Search strings identify specific words or portions of words, acronyms, or other character strings
that the task description or details must contain to be included in a category list.
If the category you are working with is a root category that is, a category in the first level of the tree
then TURNOVER for iSeries v100 applies the criteria to all projects and tasks. If the category is
a subcategory, then TURNOVER for iSeries v100 applies the criteria only to the parent categorys
task set.
What you see:
Logical relationship between criteria and strings
You can assign a logical relationship between the task selection criteria (project, resources,
requesters, and so on) and the search string selection criteria. The values you can type here
are:
*OR
Any task that either meets all the task selection criteria OR matches one
search string criterion is included in the category during a build.
*AND
Any task that both meets all of the task selection criteria AND matches one
search string criterion is included in the category.
Project criteria
Type the IDs for up to ten specific projects that might contain tasks for issues related to this
category, or use one of the following:
*ALL
*HLP
*WRK
Generic*
Specifies a group of projects that have some portion of their IDs in common.
A task must match one of the Projects you specify; otherwise, TURNOVER for iSeries v100
will not select it. A task that meets the Projects requirements must also meet at least one
requirement from either the task criteria or the search strings. If not, TURNOVER for
iSeries v100 will not select it.
Page 9-142
Task criteria
Select any of the task criteria listed here with option 1 to supply information TURNOVER
for iSeries v100 can use to identify tasks relating to this category. You can supply up to ten
specific values for each of these task fields:
Resources
Requesters
Status codes
Priority codes
In addition to specific values, you can also supply one of the following (exceptions apply as
noted):
*ALL
Specifies all possible values for a task field. *ALL can be used for any of
the task fields shown above.
Generic*
Specifies values for a task field that have one or more characters in common.
Generic* applies only to Resources, Requesters, and user-defined fields.
TURNOVER for iSeries v100 compares these values to the contents of the corresponding
task fields. If any one matches, TURNOVER for iSeries v100 includes it in the categorys
task list.
72 Wisedesk is just one more reason to define and use these fields when you specify user-defined fields, the usefulness of this decision tree increases
dramatically.
Page 9-143
Search strings
Select Search strings with option 1 to supply an unlimited number of text strings. Search strings are
automatically treated as Generic* values. To add a string, type a 1 in the selection field on the first
line. Tab past the Seq field, position the cursor in the Search string column, and type a text string
that you think is most likely to appear in the description or details of a task relating to this category.
When you press Enter, the Add Category Search String (ADDCATSTR) prompt appears with your
information filled in. Additional parameters appear so you can tell TURNOVER for iSeries v100
where to look for these strings in the task description or the task details, or both. You can also make
the search case-sensitive, if necessary.
If you enter your strings in order from most to least common, you can let TURNOVER for iSeries
v100 sequence your strings for you. If necessary, you can change the order later by selecting the
string with option 2 and typing in a different sequence number.
Make your strings as all-inclusive as you can, such that you supply as few strings as possible. Also,
use strings sparingly at the root category level, where the list of tasks to choose from is large. These
measures save time during the category build, when tasks are selected.
Read the online help for additional information about specifying and sequencing search strings.
Press F3. A pop-up prompt appears asking if you want to build the category youve just
created. You can either build category-by-category as you go along, or build the entire tree
later when you finish defining categories. Well build our tree later.
Answer N and press Enter. The Work with Categories panel reappears.
To define more root categories, return to the beginning of Step 2 and proceed as before.
If youve finished adding root categories, you can now begin branching out using
subcategories. Continue with Step 5.
This is where the true branching of your tree takes place. You can add subcategories to root
categories, or to other subcategories.
The panels presented are the same ones you saw when adding root categories. Proceed as you did
before, again skipping the build after each subcategory is defined.
When you finish supplying the selection criteria for the last subcategory, press F3. The build
prompt appears.
Page 9-144
Answer N to the build prompt and press Enter. Then use F3 to return to the Work with Help
Trees panel.
Select your help tree with option 14=Build and press Enter. The Build Help Tree Category
panel appears.
Answer Y to the build prompt and press Enter. The Build Help Tree Category panel
appears.
Position the cursor at the Path field. What you see here represents the subcategory you
just defined. You want to build the entire tree not just the last subcategory you created.
To build the entire tree, type *ALL in the Path field, and blank out any remaining path
information. Press Enter. The build job is submitted.
Either way, a build job called BLDHLPCAT is submitted to the job queue. When the job completes,
a spool file called BLDHLPP will be in your default output queue. This spool file contains the Help
Tree Category Build Summary report, which describes all the categories and subcategories you
created, and lists the tasks that were selected for each.
Review the task list for each category you created. Look for information that can help you
refine your search strings or other selection criteria. Then make any changes to the categories
that are necessary, rebuilding each category as you finish changing it.
Our own usage of Wisedesk suggests that you might want to create a Question and Answer project
to compliment your existing project database. This complimentary project contains answers to users
questions that are not requests or problems. Once the answers are entered, they can be shared by your
entire support staff.
For example, at UNICOM Systems, Inc., our TURNOVER for iSeries v100 decision tree includes a
problems project and an enhancements project for each TURNOVER for iSeries v100 release, and a
general TURNOVER for iSeries v100 Question and Answer project. This ensures that all relevant
TURNOVER for iSeries v100 issues are documented and represented in the decision tree.
Page 9-145
From within the HELPDESK command, by selecting a requester with option 16=Wisedesk;
From the task review panel within the WORKTASK command, using F16=Wisedesk;
From the Work with Tasks or Work with Projects panels within TURNOVER for iSeries
v100 Projects, using F16=Wisedesk; or
From a command line within TURNOVER for iSeries v100 using the WRKHLPTREE
command.
These locations are strategically located within common TURNOVER for iSeries v100 work
pathways; explore them at your leisure to see how they fit into the procedures you use.
Regardless of how you start Wisedesk, the Work with Help Trees panel appears:
Page 9-146
F3=Exit
F5=Refresh
F12=Cancel
F21=System command
A list of the help trees that have been constructed on your system appears. See the next step.
Step 2: Choose a tree
Select a tree with option 12 to view its categories, and press Enter. The Work with Categories panel
appears:
1/29/10
9:25:25
Tree . . TURNOVER
12
Category
API
APPL
|-APPROVAL
|-AUDIT
|-AUTHORITY
|-AUTHUSERS
|-COMPMSGS
|-DEFAULTS
|-DESC
|-DISTRIB
|-FASTTURN
|-FORM
7=Strings
8=Subcategories
Last
Build
Chg
1/24/96 N
1/24/96 N
1/10/96 N
1/24/96 N
0/00/00 Y
0/00/00 Y
1/10/96 N
0/00/00 Y
0/00/00 Y
0/00/00 Y
0/00/00 Y
0/00/00 Y
More...
F12=Cancel
F14=WRKSBMJOB
F20=Expand all F21=Command
Tasks
29
39
25
10
15
7
3
8
5
42
30
27
This panel shows the categories and subcategories that are part of the help tree you selected. Theyre
presented in a visually layered structure so you can go directly to the task list for any layer, without
having to dig through each preceding layer. (Option 8 provides an alternative style of viewing
subcategories for a category.) The number of tasks that meet each categorys selection criteria are
shown.
Note: The number of tasks shown for a category can disagree with the number you actually see,
because what you see depends on what projects youre authorized to look at.
Page 9-147
Select a category or subcategory with option 12 to see its task list. Press Enter. The Work with
Tasks for Category panel appears:
1/29/10 12:17:08
Position to task . .
*TOP, *BOT
Apply filters . . Y
Many of the options on this panel are similar, if not identical to, options you use when working with
tasks using Main Menu option 9; these are explained earlier in this chapter. When you press F23, you
see these additional options:
14=Authority
19=Test plan
16=Forms
17=Checkout
18=History
20=PWM
22=Audit
25=Search
The options specific to Wisedesk are described on the next couple of pages.
UNICOM Systems, Inc. Note
The tasks listed may not match the number of tasks shown for that category on the Work with
Categories panel. TURNOVER for iSeries v100 does not display tasks belonging to projects that
youre not authorized to use.
Page 9-148
Select a task with option 7 to exclude it from this category and/or (optionally) include it in another
related category. Use this option when you notice that a task has been included in a category
where it doesnt belong, and recategorize it properly.
Select a task with option 10 to indicate that the task contains the information you need. Use this
option any time you locate a match. Using this option helps you get results from later searches
more quickly by rippling tasks with useful information to the top of the task list subfile.
Select a task with option 21 to append a requester to the task. (This option is available only when
you enter a help tree from HELPDESK, and uses requester information carried forward from
there.) When you press Enter, TURNOVER for iSeries v100 prompts you to select a
*HELPDESK project in which a new task is created on the requesters behalf. The new task is
assigned to this task.
Select a task with option 23 to assign a *HELPDESK task the one you were reviewing when
you started Wisedesk as a subtask to the task you located within Wisedesk. This option is
available only when you start Wisedesk from within WORKTASK using F16. If you use this
option next to a subtask, the *HELPDESK task will be assigned to the subtasks main task.
Select a task with option 24 to attach a *HELPDESK task the one you were reviewing when
you started Wisedesk to a task or subtask you located within Wisedesk. This option is available
only when you start Wisedesk from within WORKTASK using F16. It is especially useful when
several people have made the same request, and you want them all notified when you complete it.
The name of a specific project to which any tasks added within HELPDESK
should be added.
*ALL
Presents a selection panel containing all projects to which you have access, so
you can choose where to add the task.
Page 9-149
*WORKING
4. If you reached this panel while reviewing tasks in WORKTASK (F16), then F6=Asg. new
shows you a list of the valid *WORKING projects for the task, so you can choose where to
assign it.
Press F10 to type another tree or path name, to transfer quickly to another tree or to another
category within this tree.
Press F11 to see different information about the tasks in the list, including who entered them and
to whom theyre assigned.
Press F16 to toggle the order of the list between match sequence and task ID sequence. Match
sequence means the tasks appear in order from most often matched to least often matched. This
capability relies on users to faithfully update a tasks match counter using option 10 each time a
search completes successfully.
Page 9-150
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
WDDYNUPD
*LIBL
F12=Cancel
Bottom
F13=How to use this display
To start a monitoring job, type *START in the Action code field. Leave the other fields as is, or type
the name of a data queue that you want TURNOVER for iSeries v100 to create, and the name of the
library where you want it to reside. Press Enter.
TURNOVER for iSeries v100 creates the data queue, and creates and starts the monitoring job. The
monitoring job is controlled by the WDDYNUPD job description in the TURNOVER for iSeries
v100 product library.
Continue with the next step.
Page 9-151
TURNOVER for iSeries v100 needs to know which projects should dynamically update your help
trees. To provide this information, do the following:
Select Main Menu option 9. From the resulting list of projects, select a project with
option 2=Change, and press Enter. The Define the Project panel appears:
1/29/10 12:01:18
Project . . . . . APPR
Description . . . Your Project
1=Select
Opt
F3=Exit
F12=Cancel
F21=System command
Select Wisedesk dynamic update options with option 1 and press Enter. The Wisedesk Dynamic
Update Options panel appears:
1/29/10 12:09:58
F3=Exit
F12=Cancel
Y, N
F21=System command
Type Y in the Dynamically update decision trees field and press Enter.
Page 9-152
Y, N
queue name
library
Description
Update all trees
CENTRAL for iMenu Items
Tasks that affect TurnOver Documents
Hardware Related Items
New tree to test steps
TURNOVER for iSeries Related Items
UNICOM Systems, Inc. Internal Items
Bottom
F3=Exit
F12=Cancel
F21=System command
Select with option 1 the trees that you want this project to update. Press Enter.
By selecting the trees a project can update, you limit the CPU cycle time spent processing project
tasks for trees that arent related. For example, you probably wont want your software project
updating the HARDWARE tree.
Repeat this step for each project that should update your help trees. When youve finished,
press F3 until you return to the TURNOVER for iSeries v100 Main Menu.
Now read the next topic to learn more about dynamic updating.
Page 9-153
To optimize performance for a high-volume or high priority project, you can create a dedicated data
queue for it, to which none of the other projects are defined. Updates for the project will go only to
that data queue, while updates for all others will be processed using the other data queue.
You can set up the monitoring job as an autostart job, if you want. (Or you can include the
WDDYNUPD command in your systems startup program.)
If one does not already exist, set up a dynamic updating autostart job.
This is done for you in subsystem TSERVER during a typical install; but if an autostart job called
WISEDESK does not exist on your system, you might have to create it manually. For instructions,
see the TURNOVER for iSeries v100 Supplement entitled Setting Up TURNOVER for iSeries
v100 Autostart Jobs (#25).
Page 9-154
Page 9-155
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F24=More keys
Page 10-1
Reporting Menu
1.
2.
3.
4.
10.
11.
12.
13.
14.
15.
16.
Application Reports
Print application definition
Check application definition
Audit report
Audit adjustments and report
Project Reports
Projects and tasks
Resource time report
Project timesheet report
Projects and tasks by priority
Project cost report
Task aging report
Project definition report
20.
21.
22.
23.
24.
25.
History Reports
List Forms
Object history
Programmer history
Source checkout history
Reference activity report
Related application conflict report
Distribution Reports
30. Form distribution report
31. Object distribution report
Miscellaneous
40. List authorized users
41. Programmer profile information
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F21=System command
The remainder of the chapter follows in the same order as options on the TURNOVER for iSeries
v100 Reporting Menu.
Page 10-2
APPLICATION REPORTS
Print Application Definition
List Default Values (LISTDFTS)
Type choices, press Enter.
Application code . .
Release . . . . . .
Version . . . . . .
Level . . . . . . .
Defaults to list . .
Suppress underlines
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*ALL
*ALL
*YES
F5=Refresh
F12=Cancel
Bottom
F13=How to use this display
This option prints the system-wide and/or application definitions on your system. Report sequence is
by application, release and version.
Enter the selection parameters and press Enter.
Page 10-3
Page:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
W
N
AUSER
AUSER
N
*USER
N
N
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*DEFAUL T
W, E,N
Y, N
US RPRF
US RPRF
Y, N
US RPRF, *PGMR, *USER
Y, N
Y, N
Y
*DEFAUL T
*MAP *D ROP
*YES
Y
E
*NONE
Y, N
U nlocked
U nlocked
Y, N
W, E, blank
*T URNOVER, *HAWKEYE, *ABSTRACT, *NON E
PROJECT DEFAULT S
Require project entry . . . . . . .
Project entry v erification program
Libr ary . . . . . . . . . . . .
Update p roject task status . . . .
Status w hen che cked out . . . . . .
Status w hen for m requires approval
Status w hen com pletes . . . . . . .
Status w hen dis tributes . . . . . .
Status w hen rem ote confirms
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Y
Y, N
TURRPRJ F
Na me
SOFTTUR N
Na me, *LIBL
Y
Y, N
S
(ST ARTED)
2
(AP PROVE)
D
(DO NE)
B
(DI STRIB)
M
(CO NFIRM)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
PRODDTA
PRODOBJ
PRODSRC
*PGMR
*PGMR
*PGMR
N
LIBRARY DEFAULT S
Na me
Na me
Na me
Na me, *PGMR, *PROJECT
Na me, *PGMR, *PROJECT
Na me, *PGMR, *PROJECT
Y, N
Ma sk
Ma sk
L ocked
L ocked
L ocked
L ocked
L ocked
L ocked
U nlocked
U nlocked
U nlocked
EXPLODE LIBRARI ES
Library
DATALIB
DATALIB2
Ove rride
Y
N
Library List
LIB1 LIB2 LIB3
LIB1 LIB2 LIB3
LIB4
LIB4
Sample continues
Page 10-4
1/29/10
Page:
I FS PATH DEFAULTS
Target path . . . ( Unlocke d) /ACCOUNTS//PAYAB LE/CLOSED
From path . . . . ( Unlocke d) /ACCOUNTS/PAYABL E/OPEN
IFS EXPLODE PATHS
Path
FORM DEFAULTS
Job description . . . .
Library . . . . . .
Library list name . . .
Library list . . . . .
Error Recovery . . . .
Threshold . . . . .
Error check form. . . .
Form schedule time. . .
Schedule elapsed ac tion
Submit Form on hold . .
Submit Finalization . .
Form Level Programm er .
Produce Listings . . .
Logging Level . . . . .
Logging Severity . . .
Output Queue . . . . .
Library . . . . . .
Job Accounting Code . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
QBATCH
QGPL
APA1
QBATCH
3
0
*BATCH
Method . . . . . . . . .
Check for Level-Che ck . .
Update Object Descr iption
Create parameters . . . .
Reference object . . . .
Library . . . . . . .
Authority . . . . . . . .
Reference object . . . .
Library . . . . . . .
Delete test object . . .
Delete test source . . .
Programmer . . . . . . .
Reference . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
CSCO
Y
N
P
*SBMRLS
Y
N
*USRPRF
Y
4
0
*JOBD
*JOBD
Name, *PGMR
Name
Name
Restricted
Restricted
Restricted
1-3
0-99
*BATCH, *INTER
*CURRENT, hhmmss
*NEXTDAY, *SBMHLD , *SBMRLS, *NOSBM
Y, N
Y, N
Name, *USRPRF
Y, N
Blank, 0-4
0-99
Name, *PGMR, *USR PRF, *JOBD
Name, *LIBL
Code, *JOBD
Restricted
Restricted
Restricted
Restricted
Restricted
Restricted
Restricted
Restricted
Restricted
Restricted
LINE DEFAULTS
P
N
Y
*CHECKO UT
*FORM
Unlocked
Unlocked
Unlocked
Unlocked
Unlocked
Unlocked
Unlocked
Unlocked
Restricted
Locked
Restricted
.
.
.
.
.
.
.
.
.
.
.
.
(Unlocked) A CCOUNTS
ACCOUNTS
(Unlocked) M OV
(Unlocked) N
Sample continues
Page 10-5
1/29 /10
TYPE COD ES
TYPE
ABPG M
CBL
CLP
CMD
FROM SRC
*PGMR
QLBLSRC
*PGMR
QCLSRC
*PGMR
QCMDSRC
*PGMR
PR ODSR C
QLB LSRC
PR ODSR C
QCL SRC
PR ODSR C
QCM DSRC
PR ODSR C
*PGMR
QDDSSRC
*PGMR
QDDSSRC
*PGMR
PR ODSR C
QDD SSRC
PR ODSR C
QDD SSRC
PR ODSR C
DTAA RA
LF
PF
PFDA TA
*PGMR
QDDSSRC
*PGMR
QPNLSRC
*PGMR
QDDSSRC
*PGMR
QRPG SRC
*PGMR
PFRE F
PNLG RP
PRTF
RPG
PR ODSR C
QDD SSRC
PR ODSR C
QPN LSRC
PR ODSR C
QDD SSRC
PR ODSR C
QRP GSRC
PR ODSR C
T GT OBJ LIB
P RODO BJ
CR EAT E RE F PARM
P
AUT H RE F PA RM
P
* PGMR
P RODO BJ
* PGMR
P RODO BJ
* PGMR
P RODO BJ
* PGMR
P RODD TA
* PGMR
P RODD TA
* PGMR
P RODD TA
* PGMR
P RODD TA
* PGMR
P RODO BJ
* PGMR
P RODO BJ
* PGMR
P RODO BJ
* PGMR
P RODO BJ
NAME MASK
D LT DLT
M ETHO D O BJ SRC D IST
C SCO
N
Y
Y
User
AUSE R
BIKE R
COWL ES
HOLM ES
JBRO WN
JSMI TH
TURN OVER
---- ---- --- --- Form -- ---- ---- --- --View Ad d Upda te Run Di str Pu rge
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Sample continues
Page 10-6
1/29/10
YOUR COMPANY, IN C.
YOURS YS
Page:
DISTRIBUTION DEFAULTS
----System---No.
Name
300 NEWBOX
0 S1014705
200 S1014706
0 S1014707
--------Us er-------ID
Addr
TURNOVER
NEWBOX
TURNOVER
S1014705
TURNOVER
S1014706
TURNOVER
S1014707
Device
*SNADS
*SNADS
*SNADS
*SNADS
Auto
Dist
N
N
Y
N
Schd
Time
*CURRENT
*CURRENT
*CURRENT
*CURRENT
Elapsed
Action
*SBMRLS
*SBMRLS
*SBMRLS
*SBMRLS
Sb m Rcv
F orms
N
N
Y
N
APPROVAL LIST
Notify Programmer Upon Form Approval
Approval list name
ACCTSPAY
User/Group
AUSER
BILLDEPT
COWLES
SLICK
Type
*USRPRF
*GROUP
*USRPRF
*USRPRF
Admin
Y
N
N
N
Notify
Y
N
Y
Y
*NO
*YES, *N O
Override
Y
N
N
Approve
Own Form
Y
N
Y
Y
MsgQ
AUSER
MsgQ Lib
QUSRSYS
UserID
AUSER
COWLES
SLICK
QUSRSYS
QUSRSYS
COWLES
SLICK
Address
APPROVAL GROUPS
Group
BILLDEPT
Description
Billing Department
Override
Users
Admin
No tify
Appr ove
Own Form
AUSER
JBROWN
JSMITH
Y
N
N
Y
Y
Y
Y
Y
Y
MsgQ
MsgQ L ib
User ID
AUSER
JBROWN
JSMITH
QUSRSY S
QUSRSY S
QUSRSY S
JBROW N
Addres s
RELATED APPLICATIONS
Appl
ARA
Rel
0
Ver
0
Y, N
Page 10-7
.
.
.
.
.
.
.
.
.
.
+
. .
. .
. .
. .
. .
for
F3=Exit
F4=Prompt
F24=More keys
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
more values
F5=Refresh
*LAST
*LAST
*PROD
*ALL
F12=Cancel
Character value
*LAST, Release Number
Number, *LAST
Number, *PROD
*ALL, *OBJNAMSTD, *JOBD...
Bottom
F13=How to use this display
If you leave the Detail default to *ALL, TURNOVER for iSeries v100 will print nine reports, each
corresponding to the categories listed below:
*OBJNAMSTD Lists objects that do not match the object naming standards in the application type
code.
*JOBD
TURNOVER for iSeries v100 checks the library list in the job description to
make sure that it is correct for the application. From libraries, or libraries
referenced at lower levels, should not be contained in the library list.
*APPLLIBL
Lists, for the application level, the recommended application library list as well as
the libraries that have been defined to the application library list name.
*OBJNOSRC
Lists objects for which TURNOVER for iSeries v100 could find no source in the
target libraries.
*LVLCHK
Lists objects for which source was found in the correct library, but for which the
change date does not match the object description.
*REFOBJ
Lists all missing reference objects (objects which are used by TURNOVER for
iSeries v100 when creating new objects and granting authority to objects).
*SRCNOOBJ
*OBJOWNER
Lists all objects with owners that are different than TURNOVER for iSeries v100
expects, given the application settings.
Page 10-8
Lists any objects of a type not included in the list of valid type codes for the
application.
Page 10-9
TURNOVER for iSeries v100 will produce a list similar to this for each category described above;
or the message No Errors Found .
1/29/10
17:47:03
******************************************************************
* APPLICATION: AP
Test Application- Prod Level 2
* RELEASE-#:
* VERSION-#:
LEVEL-#:
2
******************************************************************
SLS-US Division
Page:
1
*
*
*
Page 10-10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
+ for more
Starting Date . . . . . . .
Include past number of days
Outfile . . . . . . . . . .
Library name . . . . . . .
Add or replace outfile . . .
F3=Exit
F4=Prompt
F24=More keys
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
values
. . . .
. . . .
. . . .
. . . .
. . . .
F5=Refresh
*ALL
0
0
*PROD
*ALL
*ALL
*ALL
000000
000000
Date, 000000
Number of days, 0000
Name
Name
*YES, *NO
*ADD
F12=Cancel
Bottom
F13=How to use this display
With this command, you can run a reporting option to produce an Application Audit Report to
identify any application objects or source members that might have been changed, added or deleted
outside of TURNOVER for iSeries v100 (including objects in explode libraries). Once youve
resolved any discrepancies, you can run another reporting option to adjust TURNOVER for iSeries
v100s audit control file so that it matches the applications object and source. If you run the initial
application build job (Work with Application Definitions, option 23), or the Audit Adjustment
Report, TURNOVER for iSeries v100 builds an audit control file (TOBJRPTF) that contains
information about each of the objects and source members for the application you select.
If any levels of your application definition have no issues to report, a separate No Variances report
is generated listing all levels to which that condition applies.
TURNOVER for iSeries v100 updates the audit control file every time you run a TURNOVER for
iSeries v100 form. The flow chart on the next page illustrates the procedure followed during the
AUDITRPT job.
Supply an output file name if desired, to create a file for special reporting. This file contains records
of discrepancies identified during the verification run. You can have TURNOVER for iSeries v100
replace the output file if it already exists.
The following diagram illustrates the steps that are performed when you run the initial build job,
when you run TURNOVER for iSeries v100 forms and by this audit job.
Page 10-11
TURNOVER
for iSeries v100
Jobs
Appl/Rel/Ver/Lvl
Initial Build
SOFTTURN/TOBJRPTF
SOFTTURN/TMBRRPTF
SRCLIB
OBJLIB
DTALIB
EXPLODE
DSPFD
DSPOBJD
Check
for
Variance
QTEMP/MBNOW
QTEMP/OBNOW
exceptions
QTEMP/TOBJWRKF
Or
USER-s pecified outfile
Report
Variance
Application
Audit Report
Page 10-12
Date:
Time:
1/29/10
12:18:17
Audit Report
SLS-US Division
Page
1
Application: AAX
Release:
2
Version:
Level:
1
Objects: *ALL
Object Type: *ALL
Library: *ALL
Starting From:
0/00/00
Object: "&A"
Library: AAXPRD
Type: *PGM
TURNOVER Values
--------------OBJATR
OWNER
ASP
CRTDATE
CHGDATE
RSTDATE
CRTUSER
CRTSYSTEM
SRCF
SRCFLIB
SRCMBR
SRCDATE
00/00/00-00:00:00
00/00/00-00:00:00
00/00/00-00:00:00
00/00/00-00:00:00
Actual Values
------------CLLE
QPGMR
01
04/07/29-15:05:05
04/08/21-22:09:16
04/08/21-22:09:15
BIKER
YOURSYS
QCLSRC
BIKER
"&A"
04/07/29-15:04:57
Object: ACME01
Library: AAXPRD
Type: *PGM
TURNOVER Values
---------------
Actual Values
-------------
Member: SOMECLPGM
LibFile: QCLSRC
Library: AAXPRD
SRCCHGDATE
Page 10-13
When all objects in an application level meet audit expectations, a No Variance report is generated
along with other report output:
Date:
1/29/10
Audit Report
Time: 10:29:23
Objects:
*ALL
Object Type:
*ALL
Library:
*ALL
Starting From:
System: YOURSYS
Page
0/00/00
Page 10-14
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
*ALL
*ALL
*ALL
*PROD
*ALL______
*ALL______
*ALL
000000__
Date, 000000
000000
Number of days, 0000
________________________________
F12=Cancel
Bottom
F13=How to use this display
The application adjustment procedure lets you correct the TURNOVER for iSeries v100 audit
control file so that it matches the objects and source members for your application. Run this report
only after you thoroughly understand the reasons for any discrepancies and have corrected the source
of these discrepancies. The flow is the same as for the Audit Report except that TURNOVER for
iSeries v100 updates the audit control file (TOBJRPTF) and writes records to the Audit adjustment
history file (TAUDHSTF), making a permanent record of any changes.
Use the Library parameter to include all application libraries (including explode libraries), or identify
up to 10 specific libraries to include.
Use the Starting date parameter to select only objects promoted or created since the date you specify.
A 32-character Comment field is available to enter the reason this adjustment is being done. This
comment appears in the report should you decide to print and file it for auditing purposes (however,
the comment information is not retained).
Page 10-15
Page 10-16
Adjustment Report
System: YOURSYS
AAX
1
*ALL
*ALL
*ALL
0/00/00
Object
---------QCLLESRC
QCLSRC
QCLSRCGPG
QCLS36SRC
QCMDSRC
QCSRC
QCUMBER
QDDSSRC
QDDSSRCGPG
QLBLSRC
QMNUSRC
QRPGLESRC
QRPGSRC
Type
---------*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
*FILE
Form-# Line-#
------- -----6311001
104
6311001
105
6311001
6311001
6311001
6311001
6311001
6311001
6311001
6311001
6311001
6311001
107
108
109
110
111
112
113
114
115
116
Run Date
-------0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
Message
-----------------Chg-d TO Audit Obj
Chg-d TO Audit Obj
Added TO Audit Obj
Chg-d TO Audit Obj
Chg-d TO Audit Obj
Chg-d TO Audit Obj
Rmv-d TO Audit Frm
Chg-d TO Audit Obj
Rmv-d TO Audit Frm
Chg-d TO Audit Obj
Chg-d TO Audit Obj
Chg-d TO Audit Obj
Chg-d TO Audit Obj
PROJECT REPORTS
If you use TURNOVER for iSeries v100s project system, you can print project and task
information with this report. A variety of selection criteria can be specified to limit the detail or
define the breadth of information reported. You can run this report from the TURNOVER for
iSeries v100 Reporting menu or by typing the command PRJTSKRPT. Three versions are available.
The first is the *SUMMARY version, the second is the *DETAIL version and the last is the *MASK
version. They are presented in that order on the following pages.
*SUMMARY
Y Y,N
Project...................
*ALL
____
____
____
____
____
____
____
____
____
Task......................
*ALL
____
____
____
____
____
____
____
____
____
Subtask...................
*ALL
__ __ __ __ __ __ __ __ __
Resource..................
*ALL
__________
__________
__________
__________
__________
__________
__________
__________
__________
More...
F3=Exit
F4=Prompt
F10=Additional parameters
F12=Cancel
Page down
Page 10-17
*ALL
__________
__________
__________
__________
__________
__________
__________
__________
__________
Status.................... *ALL _ _ _ _ _ _ _ _ _ _
Priority.................. *ALL _ _ _ _ _ _ _ _ _ _
Task type................. *ALL _ _ _ _ _ _ _ _ _ _
Search string............. _______________________________________
Search description........ Y Y,N
Search details............ Y Y,N
Case-sensitive search..... N Y,N
Additional Parameters
User-defined field #01.. *ALL
__________ __________ __________
__________ __________ __________
__________ __________
More...
F3=Exit
F4=Prompt
F10=Additional Parameters
F12=Cancel
You can also search the task description and/or task details for a character string value to further limit
your search. This search, also available interactively on the Work with Task panel, is a very effective
way to focus in on previously entered requests.
1/29/10
17:30:07
Page:
Selection criteria
Report option . . . . . .
Project . . . . . . . . .
Task . . . . . . . . . .
Subtask . . . . . . . . .
Resource . . . . . . . .
Status . . . . . . . . .
Requester . . . . . . . .
Priority . . . . . . . .
Task type . . . . . . . .
User-defined field #1 . .
:
:
:
:
User-defined field #10 .
Date needed . . . . . . .
Date promised . . . . . .
Actual Start Date . . . .
Actual End Date . . . . .
Date entered . . . . . .
Search string . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*SUMMARY
*ALL
*ALL
*ALL
*ALL
*ALL
*ALL
*ALL
*ALL
*ALL
:
:
*ALL
0/00/00
0/00/00
0/00/00
0/00/00
0/00/00
to
to
to
to
to
99/99/99
99/99/99
99/99/99
99/99/99
99/99/99
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
1/29/10
Project Task Report
Your Company, Inc.
17:30:07
Proj/Task
APPR0001
APPR0002
APPR0003
APPR0012
Page:
Status
Pty Resource
ASSIGNED 1 ELMSMIKE
ASSIGNED 1 ELMSMIKE
IN-QA
2 ELMSMIKE
CANCEL
1 TURNERIV
Requester
MERKMD
CARPENTER
MARKPHIP
MERKEMD
Description
Fix check-writing program: This is a high priority
Add status field to Vendor File
Update sales tax tables
Add priority field to Vendor File
Etc.
Page 10-18
*DETAIL
Y Y,N
Print related tasks.......
Y Y,N
Print timesheet entries...
N Y,N
Print object history......
R Y=Yes, N=No, R=Results
*ALL
Task......................
*ALL
Subtask...................
*ALL
Resource..................
*ALL
Y
N
N
Y,N
Y,N
Y,N
More...
F3=Exit
F4=Prompt
F10=Additional Parameters
F12=Cancel
The parameters, Print related tasks, Print task details, etc. correspond to sections of the report (see
detail report sample on page 10-20 which you can exclude, if you want).
Page 10-19
Page Down...
1/29/10 13:47:13
*ALL
__________
__________
__________
__________
__________
__________
__________
__________
__________
Status..................... *ALL _ _ _ _ _ _ _ _ _ _
Priority................... *ALL _ _ _ _ _ _ _ _ _ _
Task type.................. *ALL _ _ _ _ _ _ _ _ _ _
Search string.............. _______________________________________
Search description......... Y Y,N
Search details............. Y Y,N
Case-sensitive search...... N Y,N
Additional Parameters
User-defined field #01.. *ALL
__________ __________ __________
__________ __________ __________
__________ __________
More...
F3=Exit
F4=Prompt
F10=Additional Parameters
F12=Cancel
As was the case with the summary version, you can print all of the tasks or requests entered on behalf
of a particular Requester or for a particular Resource. You can print all of the text details available
for the tasks you select.
Page 10-20
For more about TURNOVER for iSeries v100 Projects, see Chapter 9: Working with Projects and
Tasks.
The Selection Criteria can be printed and would appear is it does on page 10-18.
1/29/10
9:54:45
Task . . . . . . . . . . . . . TP320383
Fix TOMSGRCV for NLS -enabling
Resource . . . . . . . . . . . ELMSMIKE
Mike Elms
Status . . . . . . . . . . . . DONE
Requester . . . . . . . . . . . MERKEMD
M.D. MERKE
Priority . . . . . . . . . . . 1
1 to 3
Priority sequence . . . . . . .
Task type . . . . . . . . . . . ASAP
Application . . . . . . . . . . TO
3 2
Date needed . . . . . . . . . . 0/00/00
Date promised . . . . . . . . . 3/02/62
Planned
Actual
Duration . . . . . . . . . . .
1.00 H
1.00 H
Start date . . . . . . . . . . 10/26/95
10/26/95
End date . . . . . . . . . . . 10/26/95
10/26/95
Dependency . . . . . . . . . .
Billable time . . . . . . . . . N
Subsystem . . . . . . . . . . . Distrib [User defined field example]
Entered Changed
User profile . . . . . . . . . PHILLIPSMA PHILLIPSMA
Date . . . . . . . . . . . . . 10/26/93
12/07/94
Time . . . . . . . . . . . . . 9:23:32
17:09:32
Task details:
Problem:
------------------------------------------------------------------------Fix TOMSGRCV for NLS -enabling. It is not recognizing the correct environment
when it sends back confirmations, and confirms to the wrong environment.
------------------------------------------------------------------------Resolution:
------------------------------------------------------------------------Program TURCAUTR fixed on 10/26/93. This program was sending back the wrong
environment ID on confirmations.
Originating Tasks:
Task
Requester
FTPR0221 CARLSONRA
FTPR2554 CLARKKENT
Date entered
2/12/61
2/12/94
Timesheet entries:
------ Time ------Resource
Date
ELMSMIKE
3/17/95
Checked out objects:
Object
Library
CLP1
SOFTTURN
CLP2
SOFTTURN
Type
CLP
CLP
Entered by
TAGERTMIKE
TAGERTMIKE
From To
8:00
10:00
Total:
Programmer
ELMSMIKE
ELMSMIKE
Total
2:00
2:00
Appl
TO
TO
Cat Comment
P All done
Date
2/14/95
2/14/95
Time
11:56:50
11:56:50
Reference
TP320383
TP320383
Object History:
Object
CLP1
CLP2
Library
SOFTTURN
SOFTTURN
Type
CLP
CLP
Programmer
ELMSMIKE
ELMSMIKE
Appl
TO
TO
Reference
TP3203883
TP3203883
Page 10-21
To maintain report masks, select Main Menu 9 and then press F7. You can then select option 8 to
work with report masks.
73 For more about Report Masks, see Chapter 9: Working with Projects and Tasks.
Page 10-22
Heres what the resolved mask document looks like after the merge program replaces the substitution
variables.
TO:
Rachael Carlson
Environmental/Analyst
Silent Spring Publishing, Inc.
1-700-924-8818
Project ID: TP32 0383
Priority: 1
Planned start date: 10/26/96
End date: 10/26/96
T U R N O V E R
P R O B L E M
A C K N O W L E D G E M E N T
==========================================================================================
March 17, 1996
Problem:
-----------------------------------------------------------------------------Fix TOMSGRCV for NLS -enabling. It is not recognizing the correct environment
when it send back confirmations, and confirms to the wrong environment.
-----------------------------------------------------------------------------Resolution:
-----------------------------------------------------------------------------Program TURCAUTR fixed on 10/26/96. This program was sending back the wrong
environment ID on confirmations.
You can design virtually any output format for reporting a task. Any of the variables in the Project,
Task, or Requester file, including user-defined fields, can be used as substitution variables.
Page 10-23
F3=Exit
F4=Prompt
F24=More keys
. . *ALL
Usrprf, *ALL
.
.
.
.
.
.
.
.
*ALL
*ALL
*ALL
*ALL
Char,
Char,
Char,
Code,
.
.
.
.
.
.
.
.
.
.
000000
999999
Y
N
N
Date, 000000
Date, 999999
Y, N
Y, N
Y, N
F5=Refresh
F12=Cancel
*ALL
*ALL
*ALL
*ALL
Bottom
F13=How to use this display
The Resource time report is designed to report time entered by one or more resources. The report
sequence is Resource, Date, Project, Task, Subtask. The Page break on resource field controls
whether or not each resource prints on a separate page.
Resource Time Report Sample
For more information, see Chapter 9: Working with Projects and Tasks.
1/29/10
13:11:05
Resource
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
Page:
Sub
Project Task Task Description
APPR
0001
Fix check-writing program
APPR
0001
Fix check-writing program
APPR
0001
Fix check-writing program
APPR
0002
Change Trial Balance
APPR
0002
Change Trial Balance
APPR
0002
Change Trial Balance
APPR
0047
Change PWM tasking
APPR
0047
Add postal codes to checks
APPR
0053
Demonstrate PWM
APPR
0059
Change FPC position on label
FPPR
0012
TURNOVER issuing CHECKOUT
1/29/10
13:11:05
Resource
PALANO
PALANO
SLS-US Division
---Time--Date From - To
Total
Cat
2/10/95
2:00
P
2/12/95
2:00
P
2/16/95
2:00
T
9/24/95 6:30
3:30 9:00
C
10/27/95
1:00
P
12/17/95
2:00
P
4/28/95
2:00
P
6/08/95
2:00
P
5/25/95 3:00
5:00 2:00
R
3/09/95
2:00
P
4/21/95
2:00
P
PHILLIPS
Subtotal:88:30
Comment
Found a shortcut
***
Date
7/07/95
4/13/95
PALANO
From - To
Total
Cat
4:20
A
8:00
10:00 2:00
A
Subtotal: 6:20
Total:
Page 10-24
184:00
---Time--Comment
***
****
.
.
.
.
.
.
.
.
.
.
.
.
. . .
. . .
. . .
. . .
+ for
Resource (User-Id).
+ for
From date . . . . .
To date . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
more values
. . . . . .
more values
. . . . . .
. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*ALL
*ALL
*ALL
*ALL
_____
*ALL_____
__________
000000__
999999__
Char,
Char,
Char,
Code,
*ALL
*ALL
*ALL
*ALL
Usrprf, *ALL
Date, 000000
Date, 000000
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Previous
The Timesheet Report can be run for just one Resource for any span of time, or for multiple users.
For more information, see Chapter 9: Working with Projects and Tasks.
1/29/10
17:50:23
Selection parameters
Project:
Task:
Subtask:
Status codes:
Resources:
From date:
To date:
TE31
*ALL
*ALL
*ALL
EMERSON
04/01/95
04/01/95
--------------------------------------------------------------------------------------------------------------------1/29/10
Project Timesheet Report
Your Company, Inc.
17:50:23
Page:
2
Sub
Project Task Task
Description
Date
TE21
TE21
TE21
040195 EMERSON
040195 EMERSON
040195 EMERSON
0001
0001
0001
01
02
01
Resource
From -
To
-----------Time--------Total Cat
11:00
11:00
11:00
3:00
3:00
3:00
4:00
4:00
4:00
P
P
T
Total:
12:00
Page 10-25
*ALL______
__________
*START_
*PRJEND
1
9
_
_
Y
N
Y
Name, *ALL
ProjTaskSb, *START
ProjTaskSb, *PRJEND, *END
Priority Range
Priority Range
Status, Blank for All
Y, N
Y, N
Y, N
Bottom
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
F12=Cancel
Priority Report
Selection parameters:
Resource: PHILLIPS
From Project: *START
From Priority: 1 to 9
Status:
Summary: Y
Page Break: N
to *END
--------------------------------------------------------------------------------------------------------------------1/29/10
Priority Report
Your Company Inc.
17:42:57
Page 2
Pty
1
1
1
1
2
Resource
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
Prj/Tst/SubTsk
APPR0047
APPR0059
CMA 0001
CWI 0001
FTRQ0107
Status
STARTED
NEW
NEW
NEW
REVIEWED
PHILLIPS
FTRQ0120
REVIEWED
2
2
3
3
3
3
3
3
3
3
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PHILLIPS
PET 0001
PET 0002
PET 0003
PET 0004
PET 0005
PET 0006
PET 0007
SLSO0002
SLSO0003
SLSO0008
STARTED
STARTED
STARTED
ASSIGNED
STARTED
STARTED
STARTED
DONE
DONE
DONE
Page 10-26
Description
Sample PWM task
Sample programmer Worklist
First Customer MO
First change to Rel 8
Change Timesheet to allow accuracy down
to the second
Application audit report doesnt accept
*ALL
Add new fields to database
Fix bugs in existing programs
Add UIM Help
Recover print check list source
Create menu with authorization check
Recompile for V2R2M0
Create a non-rating mode
Update Tape Dates from Packing list pram
Send Fax from Contact Scan & Select Scen
Cant delete contact
.
.
.
.
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
+ for more values
Resource . . . . . . . . . .
+ for more values
Requestor . . . . . . . . . .
+ for more values
From date . . . . . . . . . .
To date . . . . . . . . . . .
Calculation method . . . . .
Print selection criteria . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*ALL
*ALL
*ALL
*ALL
_____
*ALL_____
__________
*ALL_____
__________
000000__
999999__
*TIMESHEET
Y
Char,
Char,
Char,
Code,
*ALL
*ALL
*ALL
*ALL
Bottom
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
F12=Previous
Note: You must be authorized to Programmer Defaults to be able to run this report. For more
information, see Chapter 3: Authorizing Users to .
Project Cost Report Sample
1/29/10
16:45:45
-----Planned-------------Actual--------Proj Task
Sub
Description
Status
TE31 0038
Partial Distributions
DONE
TE31 0095
Archive compile listings
ASSIGNED
TE31 0117
Fields on form that are
ASSIGNED
TE31 0121
Time Sheet Report
DONE
TE31 0123
Allow Create Parms
ASSIGNED
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Total:
12,143 121:00
6,058
Page:
Requestor
SULLIVAN
SULLIVAN
DURANELI
KANEPAT
KLINEM
:
:
:
:
:
:
Resource
SUEMRKS
EDDOYLE
ELSINOR
SUEMRKS
ELSINOR
:
:
:
:
:
:
Rate
15.00
5.00
75.00
15.00
75.00
:
:
:
:
:
:
Time
8:00
24:00
8:00
4:00
8:00
:
:
:
:
:
:
Cost Time
120.00
3:00
120.00
.00
600.00
60.00
600.00
.00
:
:
:
:
:
:
:
:
:
:
:
:
Cost
45.00
.00
12:36 189.15
:
:
:
:
:
:
324:00
Subtotals by project, and totals, are shown for the entire selection.
Page 10-27
F3=Exit
F4=Prompt
F24=More keys
. . .
. . .
. . .
. . .
. . .
. . .
date
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
F5=Refresh
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*ALL
*ALL, *HELPDESK, *WORKING ...
7
days
*PRV
days, *PRV
15
days, *PRV
30
days, *PRV
60
days, *PRV
Y
Y, N
*ALL
Character value, *ALL
*ALL
Name, generic*, *ALL
*ALL____________________________
*ALL
Character value, *ALL
*ALL
Character value, *ALL
*TODAY
Date, *TODAY
*DETAIL
*DETAIL, *SUMMARY
*TABLE
*TABLE, *DATE
Y
Y, N
F12=Cancel
Bottom
F13=How to use this display
You can generate an Aging Report for a single project, for all *HELPDESK projects, for all
*WORKING projects or for *ALL projects.
Set Only tasks exceeding due date to Y to have only tasks reported whose Planned end date or Date
promised are beyond the Report date.
Set Only tasks exceeding due date to N to have all tasks reported. Tasks will be grouped by Priority
and Time thresholds, according to the length of time the task has been on file as compared to the
Report date.
If Aging report criteria is *TABLE, then only those tasks whose task status and priority are included
in the Escalation Table for the project and whose Aging Report parameter is set to Y are shown. If
you use the Escalation feature, then this provides a means to limit the report only to the most
important requests and tasks. If Aging report criteria is *DATE, all tasks will be reported where the
Actual End Date is zero.
Page 10-28
The summary version provides summary statistics (counts) of tasks within each time threshold. For
example, between 1 day and 7 days old, 8 and 15 days, 16 and 30, and so on, including up to five time
ranges.
1/29/10
10:22:02
Selection criteria:
Project . . . . . . . .
Time interval one . . .
Time interval two . . .
Time interval three. . .
Time interval four . . .
Time interval five . . .
Only tasks exceeding due
Resource . . . . . . . .
Requesters . . . . . . .
Requester company . . .
Include status . . . . .
Include priority . . . .
Report date. . . . . . .
Report type. . . . . . .
Aging report criteria .
. . .
. . .
. . .
. . .
. . .
. . .
date
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*ALL
7
7
15
30
60
*YES
*ALL
*ALL
*ALL
*ALL
*ALL
*TODAY
*SUMMARY
*DATE
Group
1 to 7 Days
1 tasks
2 tasks
3 tasks
4 tasks
1
8 to 14 days
3
3
4
3
91+
10
43
14
ARPR AR Project
Page 10-29
Each task for which action is due is reported on the Task Aging Report. This version provides you
with a list of the highest priority problems and total duration of tasks within each aging threshold.
1/29/10
10:22:02
Selection criteria:
Project . . . . . . . .
Time interval one . . .
Time interval two . . .
Time interval three. . .
Time interval four . . .
Time interval five . . .
Only tasks exceeding due
Resource . . . . . . . .
Requester . . . . . . .
Requester company . . .
Status . . . . . . . . .
Priority . . . . . . . .
Report date. . . . . . .
Report type. . . . . . .
Aging report criteria .
. . .
. . .
. . .
. . .
. . .
. . .
date
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*ALL
7
7
15
30
60
Y
*ALL
*ALL
*ALL
*ALL
*ALL
*TODAY
*DETAIL
*DATE
Page 10-30
Resource
08/25/94
ADAMSANN
*NONE
08/25/94
TRANTEM
08/30/94
08/25/94
2 hrs
08/30/94
00/00/00
16 hrs00/00/00
Started
MERCHTO
08/10/94
08/30/94
DANIEL 08/11/94
6 hrs
08/30/94
00/00/00
6 hrs00/00/00
Started
MURPHYA
08/30/94
6 hrs00/00/00
SMITHJOE
08/09/94
Project Definition
problem reports
STARTED
1 to 3
TURNOVER
Y
N
*FILE
*WORKING
*TURNOVER
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. . . DEPT
. . . PRODUCT
.
.
.
.
Department ID/Location
Product/Version
Valid applications
Appl Rel Ver Description
AP
Test Application- Test Level 1
AR
Test ApplicationProd Level 2
Valid Resources
Resource
*ALL
Description
All resources are valid
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
AP
*USRPRF
*USRPRF
ASSIGNED
1
ASAP
H
Y
Authorized users
User
Description
*NONE
Unassigned
ELMSMIKE
Mike Elms
QSECOFR
Security officer
TURNOVER
TURNOVER for iSeries v100 Administrator
Personality defaults
Details mask required . . . . . . Y Masks defined . . . .
Report mask required . . . . . . . Y Masks defined . . . .
Page 10-31
HISTORY REPORTS
List Forms
List Forms (LISTFORMS)
Type choices, press Enter.
Application . . . . . . . .
Release . . . . . . . . . .
Version . . . . . . . . . .
Level . . . . . . . . . . .
Reference . . . . . . . . .
From form . . . . . . . . .
To form . . . . . . . . . .
Programmer. . . . . . . . .
+ for more values
Job accounting code . . . .
+ for more values
Form status . . . . . . . .
+ for more values
Form Detail Level . . . . .
Task Detail Level . . . . .
Print Selection Criteria .
Print Form for approval . .
List all forms in Group . .
F3=Exit
F4=Prompt
F24=More keys
*ALL
0
0
0
*ALL______
1_______
999999__
*ALL______
Appl, *ALL
Rel
Ver
Lev
Char, *ALL, generic* From form
number
number
USRPRF, *ALL
*ALL
*ALL___
*LINE
*NONE
Y
N
Y
F5=Refresh
F12=Cancel
This report will print a hard copy of one or more TURNOVER for iSeries v100 forms. You can
select forms by application, by form number or range of form numbers, level of detail and other
selection criteria. Report sequence is by form number.
Page 10-32
This sample includes a form comment, a pre-run command, and a post-run command.
1/29/10
18:57:35
Form Listing
Page
****************************************************
* APPLICATION: AP Test Application- Test Level 1 *
* RELEASE-#:
*
* VERSION-#:
LEVEL-#:
*
****************************************************
A P P R O V A L S
********************************************
* __ ____________________ ____/____/____ *
* __ ____________________ ____/____/____ *
* __ ____________________ ____/____/____ *
********************************************
************************************************************************************************************************
* Form: 0100331
Description: Fix check-writing program
Status: READY
*
*
Run date: 00/00/00
Job description: AP1
Reference: APPR0001
*
*
Run time:
Library: ACPTTEST
Programmer: PSCMIDT
*
*
Job number:
Job accounting:
*
*
From date: 0/00/00
From time:
*
*
To date: 0/00/00
To time:
*
*
Library list: *JOBD
*
*
Submit Finalization: *YES
*
*
Forms in run Group: 0100331
*
************************************************************************************************************************
Description: Fix check-writing program: This is a sample task description from the project task file
FORM COMMENTS: PSCMIDT 6/09/95 This is a Form comment. This form must complete by 12 midnight, 6/10/95
LOCK CHECKS:
Object: TLINEF
Library: SLSPROD
Type: *FILE
Allocate: Y
PRE-RUN COMMANDS:
CPYF
FROMFILE(SLS/TOINVF)
TOFILE(QTEMP/TOINVF)
CRTFILE(*YES)
Line: 1 Object: APCLP991 Library: ACPTTEST Type: CLP Code: Add Method: CSCO
TEST
source file: QCLSRC
Library:
DEVT EST
TEST object name: APCLP991
Library:
DEVT EST
PROD source file:
QCLSRC
Library:
ACPT TEST
Compile parms: C
Reference object: APCL P991
Library: PRODTEST
Ref: APPR0001
Status: READY
Member:
APCLP991
Member:
APCLP991
Create command:
Type: RPG
Code: Add
Library:
Library:
Library:
Method: CSCO
DEVT EST
DEVT EST
ACPT TEST
Ref: APPR0001
Status: READY
Member:
APR00991
Member:
APR00991
POST-RUN COMMANDS:
CALL SLSCVTF
Page 10-33
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
more values
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Object type
From date .
To date . .
Detail . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F3=Exit F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
*ALL
0
0_
0
*ALL
*ALL
Appl,
Rel
Ver
Lev
Char,
Name,
Name,
*ALL
*ALL
000000
999999
*BASIC
F12=Previous
*ALL
*ALL, generic*
*ALL
*ALL
Bottom
F13=How to use this display
This report will print the change history of one or more promoted by TURNOVER for iSeries v100.
You can select objects by application, by object type, by change date range, by programmer and by
reference code. Also see the Programmer History Report. The report is sequenced by object name
within promotion date.
Page 10-34
The Object History Report lists objects changed or about to be changed; in this example programmer
profile EDELLIS. The report sample was produced with the default of Detail *BASIC. It contains
one line for each object listed. If we had selected Detail *FULL, you would see all of the data
associated with TURNOVER for iSeries v100 form line when it was promoted to production (as
illustrated on the TURNOVER for iSeries v100 Form Listing sample on page 10-33). For an
explanation of fields on this report, see Chapter 4: Working with Object History.
1/29/10
14:26:00
Selection parameters
Application: *ALL
Release-#:
Version-#:
Level-#:
Reference:
Object:
Library:
Type:
From date:
Detail:
0
0
0
*ALL
*ALL
*ALL
*ALL
*FIRST
*BASIC
to date: *LAST
Object
Library
Type
Form
APCLP99
APRPG01
TURASIP
ADCALT
ADCBRO
ADCCKD
ADCCMP
ADCL022
ADCL024
ADCL043
ADCL044
ADCL046
ADCL066
ADCL067
ADCL088
ADCL089
ACPTTEST
ACPTTEST
ASILIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
ADLIB
CLP
RPG
RPG
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
101808
100971
100712
101669
101669
101734
101674
101669
101669
101669
101669
101669
101669
101669
101669
101669
Line
1
1
1
8
9
2
2
10
11
12
13
14
15
16
17
18
Date
Time
0/00/00
0/00/00
9/23/95
4/28/95
4/28/95
5/19/95
4/29/95
4/28/95
4/28/95
4/28/95
4/28/95
4/28/95
4/28/95
4/28/95
4/28/95
4/28/95
00:00
00:00
16:45
11:50
11:12
15:41
9:530
11:22
11:26
11:33
11:44
11:47
11:48
11:55
12:01
12:04
Job#
Code
Status
043123
043127
043127
043127
043127
043127
043127
043127
043127
043127
043127
043127
043127
043127
A-CSCO
R-CSCO
R-CSCO
A-CSCO
A-CSCO
A-CSCO
R-CSCO
R-CSCO
A-CSCO
A-CSCO
R-CSCO
A-CSCO
R-CSCO
A-CSCO
R-CSCO
R-CSCO
READY
READY
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
DEVTEST
DEVTEST
SUEMRK
EDELLIS
EDELLIS
PHILLIP
PHILLIP
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
DEVTEST
DEVTEST
SUEMRK
EDELLIS
EDELLIS
PHILLIP
PHILLIP
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
Programmer
PSCMIDT
PHILLIP
SUEMRK
EDELLIS
EDELLIS
PHILLIP
PHILLIP
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
EDELLIS
Reference
APPR0001
APPR0001
TPR30198
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ADID0001
ETC . . .
Page 10-35
. .
for
. .
. .
. .
for
. . . . . .
more values
. . . . . .
. . . . . .
. . . . . .
more values
Object type . . . . . .
From date . . . . . . .
To date . . . . . . . .
Detail . . . . . . . . .
Print Selection Criteria
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
*ALL
Usrprf, *ALL
*ALL
*ALL
*ALL
*ALL
*ALL
*ALL
000000
999999
*BASIC
Y
F12=Cancel
Bottom
F13=How to use this display
Similar in content to the Object History Report, the Programmer History Report provides a
chronological history of changes made by one or more programmers. Report sequence is change date
within object name within programmer name.
Page 10-36
The Programmer History Report lists objects changed by a selected programmer; in this example
programmer profile EDELLIS. The report sample was produced with the default of Detail *BASIC.
It contains one line for each object listed. If we had selected Detail *FULL, you would see all of the
data associated with TURNOVER for iSeries v100 form line when it was promoted to production
(as illustrated on the TURNOVER for iSeries v100 Form Listing sample earlier in this chapter).
For an explanation of fields on this report, see Chapter 4: Working with Object History.
1/29/10
20:03:16
Selection Parameters
Programmer: EDELLIS
Reference: *ALL
Object:
*ALL
Library: *ALL
Type:
*ALL
From date: 5/15/95 to date: *LAST
Detail: *BASIC
--------------------------------------------------------------------------------------------------------------------6/09/96
TURNOVER for iSeries v100 Programmer History Report
Your Company, Inc.
20:03:16
Page 2
Appl Rel Ver Lev
SM
SM
SM
TO
TO
TO
TO
TO
TO
TO
TO
TO
TO
TO
TO
TO
TO
TO
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
Object
Library
Type
Form
MENRCMD
MENXCMD
UPGRADE
CHCKOUTR
DISTDATA
DISTDATA
DISTDATA
DISTDATAR
TURCCCLO
TURCDDRS
TURCDDR2
TURCOAEP
TURCPGDF
TURCSRCH
TURRAUTO
TURRCCLO
TURRDDRS
TURRDESC
SFTMNU
SFTMNU
SFTMNU
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTO
SOFTTO
SOFTTO
SOFTTO
SOFTTO
SOFTTO
SOFTTO
SOFTTO
RPG
LF
CLP
RPG
CLP
CMD
PNLG
RPG
CLP
CLP
CLP
CLP
CLP
CLP
RPG
RPG
RPG
RPG
101784
101784
101785
101759
101774
101774
101774
101774
101732
101774
101774
101732
101762
101752
101764
101732
101774
101746
Line
2
1
1
1
3
2
1
4
2
5
6
3
1
1
1
4
7
1
Date
6/02/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
6/12/95
Code
R-CSCO
R-CSCO
A-CSCO
R-CSCO
R-CSCO
A-CSCO
A-CSCO
A-CSCO
A-CSCO
R-CSCO
A-CSCO
A-CSCO
A-CSCO
R-CSCO
R-CSCO
R-CSCO
R-CSCO
A-CSCO
Status
Ran-OK
Ran-OK
Ran-Wrn
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Ran-OK
Reference
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
SMPR0342
ETC. . .
Page 10-37
F3=Exit F4=Prompt
F24=More keys
F5=Refresh
Name, *ALL
Name, *ALL
Name, *ALL
F12=Previous
Bottom
F13=How to use this display
This report lists source and object checkout history for selected objects, source members or group of
members. Report sequence is library, source file and member. All non-source objects appear first,
then all source members.
Specify status to select source that is currently checked out, checked in, or both. Your choices are:
*IN
*OUT
*ALL
Page 10-38
For an explanation of fields on this report, see Chapter 5: Checking Out/Checking In Source.
1/29/10
20:05:18
Selection parameters
Source Mbr: *ALL
Source File: *ALL
Library:
*ALL
Type:
*ALL
Programmers: *ALL
From date: 5/15/95 to date: *LAST
Status: *ALL
Reference: *ALL
---------------------------------------------------------------------------------------------------------------------------------------1/29/10
Source Checkout History Report
Your Company, Inc.
20:05:18
Page 2
***-- P R O D U C T I O N -- ***
Library
Object
Type
DEVELOP
TESTMSG
MSGF
DEVELOP
JFCOUTQ1 *OUTQ
***--P R O D U C T I O N--***
Library
File
Member
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
SFTMNU40
QCMDSRC
ADDBAS
***----Library
SMTEST
SMTEST
SMTEST
SMTEST
SMTEST
SMTEST
SMTEST
SMTEST
SMTEST
SMTEST
SMTEST
Check-Out
Date Time
5/26/95 3:11
5/26/95 12:16
T E S T ------***
File
Member
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
QCMDSRC
ADDBAS
Check-In
Date Time
6/12/11 14:00
6/12/11 14:00
Checkout
Date Time
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
Form
Number
101721
101721
Check-In
Date Time
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
11/25/95 3:04
Programmer Reference
EDELLIS
JFPA0121
EDELLIS
JFPA0121
Form
Number
101751
101751
101751
101751
101751
101751
101751
101751
101751
101751
101751
Programmer
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
Reference
SENH0021
SENH0021
SENH0021
SENH0021
SENH0021
SENH0021
SENH0021
SENH0021
SENH0021
SENH0021
SENH0021
ETC. . .
Page 10-39
Checkout History
Object
TADDDAT
TADDTIM
TCLCTIM
TRTVDAT
TRTVDAT
TURCSBCJ
TURSWTSP
TURRWTRR
TURRWTRX
Library
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
SOFTTURN
Type
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
CLP
Programmer
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
SUEMRK
Appl
TO
TO
TO
TO
TO
TO
TO
TO
TO
Rel
3
3
3
3
3
3
3
3
3
Ver
1
1
1
1
1
1
1
1
1
Object
TURNMAIN
Library
SOFTTURN
Type
CLP
Programmer Appl
SUEMRKS
TO
Rel
3
Ver
1
Lev
1
1
1
1
1
1
1
1
1
---Checkout--Date
Time
95/04/01 8:54:42
95/04/01 8:55:22
95/04/01 9:06:14
95/04/01 9:07:42
95/04/01 9:13:12
95/04/01 9:13:32
95/04/01 8:14:42
95/04/01 8:14:44
95/04/01 8:16:49
---Checkin--Date Time
95/05/01 11:35:55
95/05/01 11:35:55
95/05/01 11:41:55
95/05/01 11:35:55
95/05/01 11:35:55
95/05/01 11:35:55
95/05/01 11:35:55
95/05/01 11:35:55
95/05/01 11:35:55
Form
101286
101286
101286
101286
101286
101286
101286
101286
101286
Reference
TP3101053
TP3101053
TP3101053
TP3101053
TP3101053
TP3101053
TP3101053
TP3101053
TP3101053
Form History
Lev
1
Date
Time
Date - Time
Form
94/04/01 10:12:12 94/04/02 10:43:01 Ran-ok
Reference
TE310312
Etc. . .
Page 10-40
. . . .
. . . .
. . . .
on form
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
*ALL
*ALL
*ALL
*NO
*ALL
*ALL
*ALL
*ALL
*ALL
000000
999999
*ALL
*ALL
*ALL
*ALL
*ALL
F12=Cancel
Name, *ALL
Name, *ALL
Character value
Number, *NO
Character value
Number, *ALL
Number, *ALL
Number, *ALL
*ALL, *CHKOUT, *FORM
Date, 000000
Date, 999999
Name, *ALL
Name, *ALL
Name, *ALL
Character value
Number, *ALL
More...
F13=How to use this display
Page down
Report Conflicts (TRPTCON)
Type choices, press Enter.
Related version . .
Related level . . .
Resolution from date
Resolution to date .
Resolved . . . . . .
Resolved by user . .
Reason code . . . .
Print audit history
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
*ALL
*ALL
000000
999999
*ALL
*ALL
*ALL
*NO
F12=Cancel
Number, *ALL
Number, *ALL
Date, 000000
Date, 999999
*ALL, *NO, *YES
Name, *ALL
Character value, *ALL
*NO, *YES
Bottom
F13=How to use this display
Page 10-41
Object
CLP07
Type
CLP
Object
COPY01
Type
RPGCPI
Object
COPY01
Type
RPGCPI
Object
COPY01
Type
RPGCPI
Page 10-42
YOURSYS
------Base------ ----Related----Appl Rel Ver Lev Appl Rel Ver Lev Type
Res
LS01
2
LS02
2
*CHKOUT
Y
Base programmer: SMITH
Base reference: PRPR0103
Base form:
Base library: LSMOD1
Related library: GH0190B
Conflict time stamp: 20001129082623 Related time stamp: 20010205112552
Resolved by user: SWAIN
Related reference: PRPR0102
Related form:
Resolution code: OK Comment:
------Base------ ----Related----Appl Rel Ver Lev Appl Rel Ver Lev Type
Res
GH
5
GH
1
5
*CHKOUT
Y
Base programmer: SMITH
Base reference: PRPR0117
Base form:
Base library:
Related library: GH0190B
Conflict time stamp: 20010205103433 Related time stamp: 20010205113407
Resolved by user: SMITH
Related reference: PRPR0102
Related form:
Resolution code: OK Comment:
------Base------ ----Related----Appl Rel Ver Lev Appl Rel Ver Lev Type
Res
GH
5
GH
1
5
*CHKOUT
Y
Base programmer: SMITH
Base reference: PRPR0117
Base form:
Base library:
Related library: GH0190B
Conflict time stamp: 20010205112612 Related time stamp: 20010205113536
Resolved by user: SMITH
Related reference: PRPR0102
Related form:
Resolution code: OK Comment:
------Base------ ----Related----Appl Rel Ver Lev Appl Rel Ver Lev Type
Res
GH
5
GH
1
5
*CHKOUT
Y
Base programmer: SMITH
Base reference: PRPR0117
Base form:
Base library:
Related library: GH0190B
Conflict time stamp: 20010205113417 Related time stamp: 20010206094300
Resolved by user: SMITH
Related reference: PRPR0102
Related form:
Resolution code: OK Comment:
DISTRIBUTION REPORTS
Form Distribution Report
Report Form Distribution (RPTFORMDST)
Type choices, press Enter.
Application .
Release . . .
Version . . .
Level . . . .
Target System
Reference . .
From form . .
To form . . .
Programmer .
+ for more
Detail Level.
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
values.
. . . .
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*ALL
0
0
0
*ALL___
*ALL______
1_______
9999999__
*ALL______
Appl, *ALL
Rel
Ver
Lev
System name, *ALL
Char, *ALL, generic*
number
number
Usrprf, *ALL
*BASIC
*BASIC, *FULL
F5=Refresh
F12=Cancel
Bottom
F13=How to use this display
Select this option to print a report of all forms that have been distributed to one or more systems.
Form Distribution Report Sample
1/29/10
20:41:13
Selection Parameters
Application: ANCB
Release-#: 0
Version-#: 0
Level-#: 0
System: *ALL
Reference: *ALL
From form: 1 to form: *LAST
Programmers: *ALL
Detail: *BASIC
---------------------------------------------------------------------------------------------------------------------------------------6/09/96
Form Distribution Report
Your Company, Inc.
20:41:13
Page
2
Form:
Form:
ETC. . .
Page 10-43
*ALL
0
0
0
*ALL___
*ALL______
__________
*ALL______
__________
*ALL______
Object type . . . . . . . . . . . *ALL___
From date . . . . . . . . . . . . 000000__
To date . . . . . . . . . . . . . 999999__
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
F12=Cancel
Appl, *ALL
Rel
Ver
Lev
System name, *ALL
Char, *ALL, generic*
Name, *ALL
Name, *ALL
Bottom
F13=How to use this display
This report provides you with a list of all objects distributed to one or more systems. A variety of
selection criteria are available.
Object Distribution Report Sample
1/29/10
20:41:13
Selection Parameters
Application: ANCB
Release-#:
Version-#:
Level-#:
System: *ALL
Reference: *ALL
Object: *ALL
Library: *ALL
Type: *ALL
From: *FIRST
0
0
0
To: *LAST
--------------------------------------------------------------------------------------------------------------------1/29/10
Object Distribution Report
Your Company, Inc.
20:41:13
Page
2
Object
JDATA
JDPF001
JDPF002
JDPF003
JDPF005
JDLF001A
JDLF001B
JDLF001C
JDLF003A
JDLF003B
JDCL001
JDCL004
JDCL006
Library Type
JALIB
DTAA
JALIB
PF
JALIB
PF
JALIB
PF
JALIB
PF
JALIB
LF
JALIB
LF
JALIB
LF
JALIB
LF
JALIB
LF
JALIB
CLP
JALIB
CLP
JALIB
CLP
Form Line
101107 1
101107 2
101107 3
101107 4
101107 5
101107 6
101107 7
101107 8
101107 9
101107 10
101107 11
101107 12
101107 13
Ref#
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
JAPR0001
Confirmed
N
N
N
N
N
N
N
N
N
N
N
N
N
ETC. . .
Page 10-44
MISCELLANEOUS REPORTS
Authorized TURNOVER for iSeries v100 Users Report
This report prints a list of users who are authorized to perform TURNOVER for iSeries v100
functions. To see user application authority, print the System default reports, detail *SYSTEM or
*ALL.
There are no command parameters for this report. Report sequence is User Profile.
Authorized Users Report Sample
User
DOYLE
EDELLIS
JOMOOR
JSCMIDT
PSCMIDT
QSECOFR
SUEMRKS
TURNOVER
Authorized Users
----------- Form
View Add Update
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
----- System
Dfts
Auth
----Pgmr
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Page 10-45
F3=Exit
F4=Prompt
F24=More keys
F5=Refresh
Usrprf, *ALL
F12=Cancel
Bottom
F13=How to use this display
This report sample lists the programmers defined to TURNOVER for iSeries v100 along with
programmer profile information. Report sequence is user profile name.
1/29/10
20:06:51
Programmer
------------------------ELMSMIKE
Steve Elsemore
Folder:
DOLLAR
John Dollar
Folder:
FORDMAN
Bill Fordman
Folder:
JobD
----------ELMSMIKE
ELMSMIKE
OutQ
----------ELMSMIKEOQ
ELMSMIKE
MsgQ
----------ELMSMIKE
QUSRSYS
Data Lib
---------ELMSMIKE
Pgm Lib
---------ELMSMIKE
Source Lib
---------ELMSMIKE
DOLLAR
DOLLAR
DOLLAROQ
DOLLAR
DOLLAR
QUSRSYS
DOLLAR
DOLLAR
DOLLAR
85.00
FORDBILL
QUSRSYS
FORDBILL
FORDBILL
FORDBILL
65.00
FORDBILL
QGPL
Rate
-----85.00
ETC. . .
Page 10-46
User Data
TURRLOGR
TURRLOG2
TO4200751G
TURRLOGR
TURRLOG2
TO4200751F
Status
RDY
RDY
RDY
RDY
RDY
RDY
Total
Pages
1
1
3
1
1
2
215092
Current
Page
Copies
1
1
1
1
1
1
Bottom
F3=Exit
F10=View 3
F11=View 2
F12=Cancel
F24=More keys
Note: The top circle indicates log reports for the form group job. The bottom circle indicates
log reports for the form group finalization job, if it was run separately.
Youll see several spool files; the log reports are in TURRLOGR (the chronological version) and
TURRLOG2 (the version sequenced by object). Note that the version sequenced by form line does
not contain information about pre- and post-run commands.
In addition to the log report, TURNOVER for iSeries v100 always prints a joblog for all form runs.
Page 10-47
If you have any questions about what happened during a TURNOVER for iSeries v100 run, you
should refer to its associated TURNOVER for iSeries v100 Log Report(s) and joblog(s).
1/29/10
Type
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Info
Page 10-48
Time
11:36:15
11:36:16
11:36:19
11:36:22
11:36:29
11:36:31
11:36:34
11:36:36
11:36:41
11:36:44
11:36:46
11:36:47
11:36:47
11:36:48
11:36:48
11:36:48
11:36:48
11:36:56
11:36:56
11:36:57
11:37:01
11:37:04
11:37:05
11:37:09
11:37:09
Page:
System: YOURSYS
Message
Temporary library T0110111D created.
Temporary data area T0110111DA created.
Member APPF001 in file JBDEVTEST/QDDSSRC copied to library JBACPTTEST.
Object APPF001 type PF created in library JBACPTTEST.
Member APLF001A in file JBDEVTEST/QDDSSRC copied to library JBACPTTEST.
Object APLF001A type LF created in library JBACPTTEST.
Object APLF001B type LF created in library JBACPTTEST.
Member APRPG001 in file JBDEVTEST/QRPGSRC copied to library JBACPTTEST.
Object APRPG001 type RPG created in library JBACPTTEST.
Object APRPG002 type RPG created in library JBACPTTEST.
Object APRPG003 type RPG created in library JBACPTTEST.
Owner changed to ELSINORE for object APPF001.
Owner changed to ELSINORE for object APLF001A.
Owner changed to ELSINORE for object APLF001B.
Owner changed to ELSINORE for object APRPG001.
Owner changed to ELSINORE for object APRPG002.
Owner changed to ELSINORE for object APRPG003.
Test object JBDEVTEST/APLF001A deleted.
Test object JBDEVTEST/APPF001 deleted.
Test source member APPF001 removed from file JBDEVTEST/QDDSSRC.
Test source member APLF001A removed from file JBDEVTEST/QDDSSRC.
Test object JBDEVTEST/APRPG001 deleted.
Test source member APRPG001 removed from file JBDEVTEST/QRPGSRC.
Temporary data area T0110111DA deleted.
Temporary library T0110111D deleted.
Page 10-49
Before defining your computers and applications to TURNOVER for iSeries v100, we recommend
that you draw a change and distribution schematic diagram (see Setting Up Your Systems for
Distribution on page 11-13).
DISTRIBUTION OVERVIEW 74
In the following explanation, development computer refers to the source computer, where software
changes originate; and production computer refers to the target computer(s), to which changes are
sent for installation. Use of either term does not imply that the computer is used exclusively for either
development or production. Production can be run on your development and production computers;
development can be done on any of your production computers.
Distribution is a process consisting of three components:
Sending a TURNOVER for iSeries v100 form and its associated source and/or objects from
a development computer to a production computer;
Submitting the form on the production computer to process and install the changes.
Sending is the physical transfer of a TURNOVER for iSeries v100 form and its associated changed
items (objects only, source and objects, or source alone) from a development computer to one or more
remote computers. The development system has a file with system definitions for each remote
production system to which changes are distributed. The definition for each remote system contains
Send defaults that control how the local system packages and distributes changes to that remote
system.
Receiving involves accepting and storing the form and changed items onto the remote computer(s).
The receiving system has a file with system definitions for itself, and for any system that sends to it.
74 This chapter describes standard iSeries-to-iSeries distribution practices. TURNOVER for iSeries v100 can distribute IFS objects using FTP, to a
target computer outside your corporate firewall (or to other platforms that run FTP). For more information about this kind of TURNOVER for iSeries
v100 distribution, see the TURNOVER for iSeries v100 Supplement entitled Configuring TURNOVER for iSeries v100 for Direct FTP
Distribution (#26), which you can find on your TURNOVER for iSeries v100 product CD, or you can obtain a copy from our support Web site
(support.softlanding.com).
Page 11-1
The definition for the receiving system contains Receive defaults, which control how the system
accepts information and changes from the other systems in the network.
Submitting means processing the received form according to the instructions in the remote
computers Send defaults. (Remember, the remote systems Send defaults are stored on the computer
that is sending the information, so they are packaged and sent to the remote computer along with the
form and changed items.) Submitting can be either automatic or manual; this is controlled by a field
in the Receive defaults defined locally on the receiving system.
All three components can be handled either automatically or manually, depending on your system or
organizational requirements (read Combination distribution on page 11-4).
To distribute changes using TURNOVER for iSeries v100, you must have either the production or
development version of TURNOVER for iSeries v100 on each of your production computers. The
production version of TURNOVER for iSeries v100 has all of the functions necessary to receive
forms, run them, and track change history. It does not have facilities for source check-out/check-in,
TURNOVER for iSeries v100 forms creation, or distributing to other computers. For more
information, see the TURNOVER for iSeries v100 Supplement entitled Differences in
TURNOVER for iSeries v100 Production Version (#62).
TURNOVER for iSeries v100 can distribute source and/or objects to any number of remote computers using a network, or using a medium such as tape or diskette.
The names of libraries on the development and production computer can be different. Also,
TURNOVER for iSeries v100 can explode, or duplicate, data-type objects into multiple libraries
on each production computer.
Only forms that have a form status of RAN-xx, FIN-xx, EMER-xx, or PARTIAL (indicating that a
distribution has already been sent to some, but not all, production computers) are eligible for
distribution.
The following topics describe how to set up your computers to distribute changes.
Manual distribution
To distribute manually, you must perform each step in the send, receive, and submit processes
yourself. Using this setup, you would run a TURNOVER for iSeries v100 form on the development
computer and manually send it to the production computer. Then you would sign onto the production
computer using pass-through or a locally attached device, receive the distribution, and schedule the
TURNOVER for iSeries v100 form to be run.
You can distribute several forms concurrently, as long as they are all being distributed to the same
production computers.
Page 11-2
Regardless of how you set up distribution defaults, if the TURNOVER for iSeries v100 form
completes with a status other than RAN-OK, EMER-OK, or FIN-OK, you must check it and then
distribute it manually.
Automatic distribution
To distribute automatically, you must set up TURNOVER for iSeries v100 to send a form to the
production computer automatically, as soon as the TURNOVER for iSeries v100 form finishes
running on the development computer. Your production computer would also be set up to
automatically receive the form, schedule it to run, run it unattended and, optionally, send log spool
files and status back to the development computer to update the TURNOVER for iSeries v100 form
status there.
Also, with automatic distribution, you can override the distribution defaults at run-time for all or some
of the production computers. For example, today you might only want to distribute a TURNOVER
for iSeries v100 form automatically to one of several production computers when it completes, and
then manually distribute to the remaining computers tomorrow.
Automatic distribution is done one form or form group 75 at a time. If distribution is specified for an
application level, you will be presented with the list of production computers and distribution defaults
when you submit a TURNOVER for iSeries v100 form to run. At that time, you can accept these
options or, if you have distribution authority, change them. Distribution occurs immediately after the
form runs, unless you override distribution for all production computers; or the form status is xxxERR, xxx-WRN, xxx-ERR, or RECOVER. Form status must be RAN-OK, FIN-OK, or EMEROK for it to be distributed automatically. Otherwise, you must inspect the form and, if it is OK,
distribute it manually.
Automatically receiving changes
The automatic receive feature relies on a TURNOVER for iSeries v100 autostart job called
TURCRARE that must be running on each production system where you want to automatically
receive changes. This way, forms can be received even if the changes are distributed by SNADS
hours after the distribution job has ended on the development computer. If you want a production
system to automatically receive changes sent from other systems, you must first set up the
TURCRARE autostart job there.
UNICOM Systems, Inc. Recommends
Set up TURNOVER for iSeries v100 to automatically receive changes on your production
system(s). For instructions for setting up the autostart job TURCRARE, see the TURNOVER for
iSeries v100 Supplement entitled Setting Up TURNOVER for iSeries v100 Autostart Jobs (#25).
75 For more about how to submit more than one form at a time, see Chapter 7: Submitting a TURNOVER for iSeries v100 Form to Run.
Page 11-3
If you want TURNOVER for iSeries v100 to use the job queue specified in TURNOVER *JOBD,
then use the special value *JOBD in positions 1-10. If the TDSTJOBQ data area does not exist, or if
it contains invalid values, TURNOVER for iSeries v100 will use the value you have specified for
the Submit Form job queue parameter in the TURNOVER for iSeries v100 global defaults.76
Combination distribution
You can control how automatic the distribution process should be by using a combination
distribution. That is, you might have reasons for sending the form manually, but once sent you might
prefer to receive it automatically. On the other hand, you might want forms to be automatically sent
and received, but submitted manually. When you create your system definitions, you include default
values for your computers that control their sending and receiving activities.
Application definitions
Changes promoted to any application level can be distributed to all or some of your production
computers. Once you have identified all of your computers to TURNOVER for iSeries v100, 77 you
must specify to which computers you want changes to be distributed, for each application level
definition that is to be distributed. 78 For example, if you have ten computers, but application AR
only runs on six of them, then you must specify to which six computers to distribute AR changes.
Any level of an application for which forms are distributed requires equivalent application level
definition entries on each computer to which changes are sent that is, if you are distributing from
application AP level 1, you must have an application level definition called AP level 1 on each
remote computer that will receive changes.
76 To access the TURNOVER for iSeries v100 global defaults, select option 8 (Utility menu) on the TURNOVER for iSeries v100 Main Menu, and
the Maintain System Definitions panel, select a system with option 16 (Distributed Applications).
Page 11-4
You can copy application definition entries to remote computers. There are two ways of doing this:
1. Using remote application definition records This is the recommended approach because it
requires no physical connection between systems; it works with SNADS or with media. It is also
automated you dont have to remember to change the application definition on the remote
system before you can process a distributed form.
To use this method, you create and maintain remote application definition records for each
application you distribute in a file on the sending system. If this feature is in use, TURNOVER
for iSeries v100 checks to see if the definition has been changed since the last distribution. If it
has, TURNOVER for iSeries v100 sends the definition to the production system along with the
related form. The definition is applied when the form runs on the production computer, and then
the form is received.
You control use of this feature with the Distribute application definition (Y/N) field in this
systems Send distribution defaults on the development computer. Create entries in the remote
application definition file using Distribution Menu option 5.
2. Using the Remote Configuration Wizard For detailed information about this method, read
Step 7: Distribute application and system definitions to your remote computer, beginning on
page 11-27.
Page 11-5
If you tell TURNOVER for iSeries v100 that you will be distributing only source code, you can
specify which source to send by object type and application. The application determines if source
and/or objects are to be distributed. If only source is distributed, then the application definition on the
production computer where local promotions are controlled must specify TURNOVER for
iSeries v100 method of CS (Copy Source) or CSCO (Copy Source, Compile Object).
Objects-only distribution
If you tell TURNOVER for iSeries v100 that you will not be distributing source code, then only
objects and source-only objects, such as Help text, are distributed. If only objects are distributed, then
the application definition on the production computer must specify TURNOVER for iSeries v100
method of MO (Move Object) or CD (Create Duplicate).
UNICOM Systems, Inc. Note
If you plan to distribute objects for an application definition that uses MO (Move Object) or CD
(Create Duplicate) as its promotion method, you should make sure that object stamping is turned off
in the remote application definition. For more information, see Step 3: Create remote application
definitions for distributed applications, beginning on page 11-24. For more information about object
stamping, see the TURNOVER for iSeries v100 Supplement entitled Managing Multiple Versions
(#63); specifically the section entitled Object Versioning.
If necessary, you can set defaults to let you distribute source and object types differently for an
application. For example, you may want to send only objects for most object types (files, programs,
and so forth) but only source for a few object types such as an SQL logical view, which must be
compiled on the target system. Distribution of source or objects (or both) depends upon the defaults
settings in the application definition and in the TURNOVER for iSeries v100 type code entry. This
is summarized in the chart on page 11-7.
Page 11-6
System
definition
Application
definition 79
Distrib?
Distribute source?
Y or S or blank
Distribute source?
N or O
Distribute source?
Y or S
Distribute source?
N or O
Distribute source?
Y 80
Blank
Distribute object?
Y or O or blank
Distribute object?
N or S
Distribute object?
Y or O
Distribute object?
N or S
Distribute object?
Y 81
Blank
79 The application definition can also contain *SYSTEM in these fields, which refers back to the Y/N value in the system definition.
80 Alternatively, when blanks are entered for the type code, the source is distributed if the application definition is set to *SYSTEM and the system
definition is set to Y unless someone with the authority to do so, overrides the Distribute source parameter by changing it to N when the form is
submitted or when a manual distribution is submitted.
81 Alternatively, when blanks are entered for the type code, the object is distributed if the application definition is set to *SYSTEM and the system
definition is set to Y unless someone with the authority to do so, overrides the Distribute object parameter by changing it to N when the form is
submitted or when a manual distribution is submitted.
82 TURNOVER for iSeries v100s product library names may be different on your system.
Page 11-7
To distribute from your development computer without first promoting the data, use the DISTDATA
command as a post-run command. Like the CPYTSTDTA command, this has just one parameter,
file name.
*DATA and *SRC (source-only) object types will also cause TURNOVER for iSeries v100 to
distribute data. The *DATA object type lets you define a physical file so you can check out and
promote the contents of a file without changing the file format. The *SRC type lets you define a
TURNOVER for iSeries v100 type code to check out and promote and optionally distribute a
source or non-source file member. (For more information, see Working with TURNOVER for
iSeries v100 Type Code Definitions on page 8-6.)
When a TURNOVER for iSeries v100 form is distributed, the form status on the development
computer is changed to DISTRIB. If the form is partially distributed (distributed to some of the
production computers designated for the application, but not all), then the form becomes PARTIAL.
When the form is distributed to the remaining computers, then the form status becomes DISTRIB.
After the form has run successfully on the production computer and, if you have told TURNOVER
for iSeries v100 to send a confirmation back to the development computer, a network message is sent
to the development system from each production computer. When the message is received by the
development system, the distribution history record for the distribution is updated. When
confirmations have been received from all production systems to which the form was sent, the form
status changes from DISTRIB to CONFIRM. You can also view and update the distribution history
record manually for each form. (See Updating Form Distribution Status on page 11-44.)
Received forms
When a form is received on a production computer, the form status is RECVD. This is equivalent to
READY on the development computer. After the form is run, the form status is changed to RANOK or RAN-WRN, as when a form is run on a development computer. If the form fails and is
Page 11-8
recovered (status RECOVER) as when an object is in use when the form is running, for example
you can reset it by typing the command RESETFOR on a command line, and then pressing F4 to fill
in the form number. The form status will be reset to RECVD. (We suggest that you use the Lock
check feature to avoid this condition.)
Form status on the development computer must be xxx-OK for the form to be distributed automatically.
Form status may be xxx-OK, xxx-WRN, xxx-ERR, or PARTIAL to be eligible for manual
distribution. 83
Distributing from a development computer with multiple environments to production computers with
a single environment can produce duplicate form numbers on the receiving system. A form generated
in one environment on your development computer can have the same number as a form produced in
another environment on the same computer. If your production computer does not have multiple
environments, the result is duplicate form numbers. TURNOVER for iSeries v100 will not process
duplicate form numbers on a remote computer correctly. The simplest solution is to put
TURNOVER for iSeries v100s form number and distribution number files into TURNOVER for
iSeries v100s program library; this way, the same file is used regardless of environment.
If you must distribute from a multiple environment computer to a single environment computer, call
UNICOM Systems, Inc.s technical support line for guidance.
83 DID YOU KNOW? You can make RAN-WRN forms eligible for automatic distribution by creating a one-character data area called DSTRANWRN
in your TURNOVER for iSeries v100 product library. You need not initialize the data area; it should merely exist.
Page 11-9
Page 11-10
Distribution authority
You must have application default authority to maintain or distribute application definitions to
production computers.
You must have run authority to run and distribute forms automatically. You must have distribution
rights to change distribution options when you submit a form, or to distribute a form manually.
You must have forms run authority to distribute a form automatically, and forms distribution authority
to override or change distribution defaults.
84 See the TURNOVER for iSeries v100 Supplement entitled Setting Up TURNOVER for iSeries v100 Autostart Jobs (#25).
Page 11-11
Distribution user
You can specify which user is to receive a distribution at each production computer. The default user
name is user profile TURNOVER. We recommend that you use this profile.
When TURNOVER for iSeries v100 is loaded on your system, it creates a user profile called
TURNOVER and a directory entry for that user. TURNOVER is the user to whom distributions are
sent unless you substitute another name when you set the system distribution defaults. That user
profile must exist on the production computer.
If you do specify another user name for target user, TURNOVER for iSeries v100 will
automatically create a directory entry on the sending computer for that remote target user. If you
change the target user name, TURNOVER for iSeries v100 will change directory entries
appropriately.
For more about the form distribution process, see How Distribution Works on page 11-54.
Page 11-12
Your companys applications have already been defined. If this is not the case, for information
about setting up application definitions, see Chapter 1: Working with Application Definitions in
this guide and see the TURNOVER for iSeries v100 Application Planning Guide.
You plan to use SNADS for exchanging information between your development and production
computers. If this is not the case, you can use other network communications protocols.
Page 11-13
Production
APPGM
Program
Library
*PGMR
Test
Library
Production
APSRC
Source Library
APTEST
Test
Library
AP level 1
CSCO
Compile Objects
Production
APDATA
Database
Library
AP level 2
CSCD
O bjects Only*
* or Source-only, or Source and Objects
Sys tem D
System C
System B
AP
APPGMSG
Program
Library
TURNOVER
for iSeries
v100
Distribution
Library
TnnnnnnnS
Application default
AP Level 2
Method MO
Move Objects
Page 11-14
In this example, we have created two application level definitions on the development computer AP
level 1 and AP level 2. For each of the production computers, we intend to distribute objects from the
production libraries APPGM and APDATA located on the development computer to the production
libraries on each production computer.
Note the following:
All of the library names on the production computers can be different than on the development
computer.
We have set up application definition AP level 2 on the production computers. Also, this has been
defined to Explode data libraries that is, duplicate object changes from one production data
library into multiple data libraries, as might be the case if you were supporting multiple divisions
or companies.
The application definition on the production computers specifies TURNOVER for iSeries v100
method MO (Move Object). If we specified CSCO, CSCD, or CSMO, we would have to tell
TURNOVER for iSeries v100 to distribute source as well as objects.
Obviously, there are many possible variations. Your environment may be more or less complex.
And, each of your applications may be different.
Other information you might include in your schematic is:
The production system(s) on which the TURCRARE autostart job is needed for automatically
receiving changes.
The development system(s) on which the TOMSGRCV autostart job is needed for processing
incoming confirmation messages or distribution log entries from a receiving system.
Gathering this kind of information in advance makes the remaining steps easier to follow.
UNICOM Systems, Inc. Recommends
Set up your systems for automatic distribution. If you need to, you can override defaults to distribute
manually under exceptional circumstances.
Page 11-15
Step 2: Define your computers to TURNOVER for iSeries v100After youve decided how youre
going to manage and distribute changes, you can define your computers to TURNOVER for iSeries
v100.
Step 2.1: Sign onto the development computer and go to the Maintain System
Definitions panel
Sign onto your development computer. Define each of the computers in your network to
TURNOVER for iSeries v100 on this computer, as follows:
Select Main Menu option 11, then option 1. This panel appears:
1/29/10
11:13:35
F3=Exit
System
USI
UIUK
CDC
WASH
FLOR
ALAS
TORON
Device
TAP01
TAP01
TAP01
*SNADS
*SNADS
*SNADS
*SNADS
System Description
UNICOM Systems, Inc. Headquarters
UNICOM Systems, Inc. U.K.
Confederated Data Company
UNICOM Systems, Inc. Washington
Florida Fifty Group
UNICOM Systems, Inc. Alaska
UNICOM Systems, Inc. Toronto
F12=Cancel
All of the production computers in your network must be defined to TURNOVER for iSeries v100
on the development system. The development computer must be defined on each production system.
Each computer, whether its a development or production computer, must have a local definition for
itself.
Each system has a unique 3-digit system number. TURNOVER for iSeries v100 uses this number
as a prefix when it generates a form number.
The system definition record is where you define Send and Receive defaults to control how forms are
handled on your systems during a distribution. If you need to distribute manually, this is where you
tell TURNOVER for iSeries v100 what device to use for saving or restoring changes on tape.
Page 11-16
If your systems have been defined to TURNOVER for iSeries v100 already, they are listed here.
The entry for the system on which you are working (the development system) should be highlighted.
If it isnt, make sure the serial number specified in the system definition entry matches the system
value QSRLNBR. (Do not start it with an S.) In your development system entry, you can use
*LOCAL in the Serial number field; this retrieves the system value automatically.
What you can do:
2=Change
Select a system entry with option 2 to view or change its system information.
4=Delete
Select a system entry with option 4 to delete it from your system.
7=Application definitions
Select a system entry with option 7 to view and update its application definitions. If you select
a remote production system, an active network connection must exist for it.
TURNOVER for iSeries v100 uses DDM files to let you view and update the remote
production systems application entries. If you dont have a network connection between your
computers, you wont be able to select option 7. To get around this, you can pass-through to
the production computer and work with applications directly. Or you can use Distribution
Menu option 5 for another way of maintaining application definitions for your remote systems.
(Read about this on page 11-24.)
You must have system defaults authority to update application definition entries.
9=Distribution defaults
Select a system entry with option 9 to view and update its distribution default entry. If you
select a remote production system with this option, youll see its Send defaults. If you select
the local system, youll see its Receive defaults. These defaults are distributed with the forms.
They control the scheduling of the form on the development and production computers.
You must have forms distribution authority to update system definition entries.
12=Distribute system
Distribute the system definition to one or more production (remote) computers using the
Remote Configuration Wizard. You can also access the Wizard using option 7 on the
Distribution menu. For more information, see Accessing the Remote Configuration Wizard
on page 11-27.
13=Change DDMF definitions
Select a system with option 13 if youve changed any system definitions and need to rebuild
the DDM file connection to a remote computer.
Page 11-17
16=Distributed applications
Select a remote system with option 16 to see or update a list of applications that are distributed
by the chosen system to other systems in the network. By changing an application in the
resulting list, you can specify application Send defaults that would override the system Send
defaults.
Select the local system (highlighted) with option 16 to see a list of applications defined on that
system. By changing an application in the resulting list, you can specify application Receive
defaults that would override the system Receive defaults.
F6=Add system definition
Press F6 to add a new system definition to your system. (You must have authority to use this
option. See your TURNOVER for iSeries v100 Administrator.)
Page 11-18
Contact name .
Title . . . . .
Address Line 1
Address Line 2
City/State/Zip
Country/FPC . .
Phone . . . . .
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Char, *LOCAL
Neal Bush
Finance Manager
IRS Data Center
100 Pennsylvania Avenue
Washington
DC 20341
2023378899
F12=Cancel
All of the systems in your network, including the one youre on, must be defined to TURNOVER
for iSeries v100 before you can distribute TURNOVER for iSeries v100 forms to them. The
sending and receiving computers must be defined on each production computer.
The System number can be any number between 1-999; however, the System number assignments
must be consistent across all of your systems. In other words, if you define your Model F20 to be
System number 20 on your development computer, it must be defined as System number 20 on your
remote production computer as well. However, on a remote production computer, only the
development (source) and local production (target) system need to be defined. On your development
computer, all systems, including the development computer, need to be defined.
System name must match the Current system name parameter on the Display Network Attributes
panel on the system youre defining. (Use the DSPNETA command.)
Serial number must match the Serial number field on the Display System Value panel on the system
you are defining. You can type *LOCAL, or use the DSPSYSVAL QSRLNBR command on that
system to get the exact value.
Page 11-19
Once youve created entries for all your systems, return to the Maintain System Definitions panel
(see STEP 2.1).
Select your local system entry with option 9=Distribution defaults. This panel appears:
1/29/10
21:18:26
Distribution device . . . . . . . .
User profile to receive Snads files
Automatically submit received forms
Send logs back to host . . . . . .
Send confirmations back to host . .
Allow override from sending system
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*SNADS
TURNOVER
N Y, N
N Y, N
N Y, N
Y Y, N
F12=Cancel
System Receive distribution defaults apply to a system that will receive changes from other computers
in the network.
If you dont plan to use your local system the system youre working on now to receive changes,
press Enter to accept the defaults, and continue with the instructions for system Send distribution
defaults, on the next page.
The Automatically submit received forms field is where you control the automatic submit component
of the distribution process. If this field is Y, TURNOVER for iSeries v100 automatically submits
forms for processing as soon as they are received.
The Allow override from sending system field controls whether you can override the Receive
distribution defaults for a target system when you submit a form on the sending system. If this field is
Y, Receive default overrides that are sent with the form to the receiving system are accepted and
applied when the form is received there.
Page 11-20
Once youve supplied the system Receive distribution defaults for your local system, return to the
Maintain System Definitions panel. Select one of your remote production systems with option 9.
The System Send Distribution Defaults panel appears:
1/29/10
21:27:54
F3=Exit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F12=Cancel
System Send distribution defaults control how the local development system packages and sends
application changes to the remote production system you selected. These defaults are systemspecific, but you can override them for each application you distribute to the remote system. For
example, if most applications are to be distributed via SNADS, but, for whatever reason, your AP
application is to be distributed via tape, specify SNADS here at the system level, and then override
the Distribution device parameter for the AP application definition.
Automatic distribution can be fully or partially automatic. That is, you may not want the form sent
automatically, but when the form is sent, you may want it to be received and run automatically. Or,
you may want forms to be sent and received automatically, but submitted to be run manually. The
Send distribution defaults specify the degree of automation for each production computer.
If you have forms distribution authority, you can override the distribution defaults at run-time for all
or some of the production computers. For example, today you may only want to distribute a
TURNOVER for iSeries v100 form automatically to one of several production computers when it
completes, and then distribute to the remaining computers manually tomorrow.
Automatic distribution is done one form at a time. If automatic distribution is specified for any
production system to which an application would be distributed, TURNOVER for iSeries v100
presents the list of production computers and distribution defaults when you submit a form to run. At
that time, you can change or accept these options. Distribution occurs immediately after the form
runs, unless it has form status xxx-ERR, xxx-WRN, or RECOVER. (Form status must be RANOK, FIN-OK, or EMER-OK to be distributed automatically. Otherwise, you must inspect the form
and, if it is OK, distribute it manually.)
Page 11-21
You can control the receive process completely from your development computer, or locally on each
production computer.
If youre distributing to more than one computer, or if your communication lines are slow, or if your
connection is intermittent (switched-line), we recommend that you set up the automatic receive
autostart job, 85 TURCRARE, on each production system and control the receive process locally, at
each system.
If you use this method, then here in the Send distribution defaults for each remote computer, set the
Automatically distribute forms field to Y and the Receive forms method field to *AUTOSTART.
(Do not set Receive forms method to *PASSTHRU if the autostart job is running, because this will
cause conflicts.)
In each production computers Receive distribution defaults, set the Distribution device field to
*SNADS, supply a user profile (usually user TURNOVER) for receiving SNADS files, and indicate
whether TURNOVER for iSeries v100 should automatically submit received forms.
Fill out the panel and press Enter to accept the Send defaults for this system.
When you finish, use F3 to return to the Maintain System Definitions panel, then proceed with
the next step.
85 For more information, see the TURNOVER for iSeries v100 Supplement entitled Setting Up TURNOVER for iSeries v100 Autostart Jobs (#25).
Page 11-22
On the Maintain System Definitions panel, select a remote system with option 16. The System
Distributed Applications panel appears:
1/29/10
11:01:57
1
10
1
2
3
4
2=Change distribution
Description
System-Wide Defaults
Test Application- Test
Test Application- Prod
Test Application- Test
Test Application- Prod
Test Application- Test
Test Application- Prod
Level
Level
Level
Level
Level
Level
1
2
1
2
1
2
Distribute
Src
Obj
N
N
N
N
Y
Y
N
N
Y
Y
N
N
N
N
This panel lists all applications defined on the development system. Highlighting identifies any
applications that are distributed to the remote system shown at the top of the panel. If none are
highlighted, no applications are currently distributed to the remote system you selected.
To distribute an application to this remote system, select an application level entry from the list
with option 1.
If an application is already highlighted, you can select it with option 2 to supply application-level
Send defaults. These would override the systems Send defaults. When you use option 2 for an
application thats not highlighted, the application is automatically selected for distribution and
appears in the list when you return to the System Distributed Applications panel.
Use option 4 to remove undesired applications from the distribution list. (The application definition
itself is not deleted only removed from the distribution list for this system.)
When youve identified all the applications you want to distribute to the remote system shown,
press Enter; then press F3 to return to the Distribution Menu.
Page 11-23
We urge you to thoroughly test any changes you make to your application definitions. Take the
time to set up some sample objects. Then, when you do make a change, create a worklist, check them
out, promote them through all levels, distribute them, and install them on your production computers.
PLAY IT SAFE!
To create an entry in the Remote Application Definition file for an application that is defined to
TURNOVER for iSeries v100, select option 5 on the Distribution Menu. The Work with Remote
Application Definitions panel appears:
1/29/10
Position to . . . Application:
Rel:
Ver:
Lev:
Bottom
F3=Exit F12=Cancel F14=WRKSBMJOB F21=Command line F23=More options
Highlighted lines have remote application definitions defined.
This panel shows application level entries that have been identified in the system definition as
distributed applications. Highlighting identifies the applications that have remote definitions already.
To create a remote application definition for an application, select its unhighlighted entry with
option 1.
To change an existing entry, select it with option 2 or one of the other topic-specific options.
(These options are the same as those found on the Work with Application Definitions panel.) For
example, if youre not distributing source, you should change the TURNOVER for iSeries v100
promotion method to MO (Move Object) in your remote application definitions. Read the Note
and the recommendations on the following page.
Page 11-24
If you plan to distribute objects for an application definition that uses MO (Move Object) or CD
(Create Duplicate) as its promotion method, you should make sure that object stamping is turned off
in the remote application definition. For more information about object stamping, see the
TURNOVER for iSeries v100 Supplement entitled Managing Multiple Versions (#63); specifically
the section entitled Object Versioning.
UNICOM Systems, Inc. Recommends
Check these application default parameters for your production computers. Consider changing them
to these suggested settings:
Field
Setting
Location
Project defaults
blank
blank
Method
MO
blank
blank
Line programmer
blank
blank
Form defaults
Line defaults
Change any *PGMR values to some other value, or leave them blank.
Make sure that the libraries in the library list referenced in your application definition exist on
your production computer(s).
If you plan to use reference objects on the production system, make sure they exist and are set
up appropriately for each object type being distributed. (Use F6=Create missing items on the
application definition Type codes panel while signed on to your remote product computer to
create any missing items there.)
Page 11-25
Step 4: Check OS/400 release level and set TGTRLS parameter if needed
If you are distributing objects, check your diagram for the operating system release level of all
computers concerned. If your development computer is running a newer release of the operating
system than your production computer(s), you must do the following:
1. On your development computer, specify the remote computers target release value in the Target
Release global default (Utility Menu option 5). (If you are distributing to multiple computers with
different release levels, use the lowest release level.
2. Add the following TGTRLS parameter specification in the create command for all global type
codes that handle programs, modules, or service programs:
TGTRLS(&TR)
The &TR substitution variable is replaced with either the global default, or with an override specified
at the application level with a user-defined parameter value (F8 on the Type Codes panel of your
application definition).
Page 11-26
You can access the Remote Configuration Wizard in several ways, as described below:
If you want to distribute .
Either an application or a
system definition
(Or both)
An application definition
A system definition
86 An applications library list objects are included with the distributed definition, but they are NOT overlaid on the remote computer if they already
exist.
Page 11-27
When you access the Remote Configuration Wizard with option 7 on the Distribution Menu,
TURNOVER for iSeries v100 immediately starts the Wizard. If you access the Wizard with Main
Menu option 1 (for application definitions) or Distribution Menu option 1 (for system definitions), as
described above, the first panel you will see explains that the option you have selected has been
replaced by the Remote Configuration Wizard. Youll have to press Enter to start the Wizard.
TURNOVER for iSeries v100 then displays the first panel:
1/29/10
16:17:22
ENTER=Next Panel
F3=Exit Wizard
This panel provides an introduction to the Remote Configuration Wizard. After viewing this panel,
press Enter.
A second panel appears:
1/29/10
16:20:50
If you have selected options 1 or 2, then please specify where to get the
application data. Your two choices are: Remote definitions and Local
definitions. The remote definitions are configured using option 5 on the
Distribution menu. These give you the ability to setup locally, the way
the definition should appear on the remote. The local definitions are the
definitions you are actively using on this system (Main menu option 1).
This option would be useful if you are sending the data to another TURNOVER
Development system.
Specify the application data to send:
1=Remote Definitions
2=Local definitions
ENTER=Next Panel
F3=Exit Wizard
F12=Previous Panel
This second panel offers you three distribution options. The option you choose determines the
sequence of panels you see next, as is illustrated on the next page.
Page 11-28
System Definitions
Application Definitions
Panel 1
Introduction
Panel 2
Select Option
Panel 3
Select Applications
Panel 3
Select Applications
Panel 4
Select Systems
Panel 4
Select Systems
Panel 5
Final Specifications
Panel 5
Final Specifications
Panel 5
Final Specifications
Page 11-29
To distribute both application and system definitions, select option 1=Applications and systems on
the second panel. Because youre distributing application definitions, you need to indicate whether
the application definitions are remote or local definitions. (The panel displays text describing the
difference between remote and local definitions.) Specify this information and press Enter. The next
panel appears:
1/29/10
16:24:31
F3=Exit Wizard
F12=Previous Panel
F21=Select all
On this panel, select with option 1 the application definitions that you want to send to the remote
computer. Press F21 to select all the applications listed, including those displayed on subsequent
panels. Press Enter to confirm your choices and to display the next panel.
1/29/10
17:10:38
080
150
410
420
430
450
451
452
510
555
999
Serial
12345678
1000D6R
1038112
1038112
1038112
101314R
*V45111
*V45112
1048206
1048208
123456
Mdl
F10
150
200
200
200
150
150
150
400
999
620
System Description
Non-existent, to test failure
USI Web Server
QA Environment
100 to 5.4 Distribution
100 to 5.4 Designed to fail
USI Training box
Virtual system
Virtual
Development
Debs system
Pauls system
Bottom
ENTER=Next Panel
F3=Exit Wizard
F12=Previous Panel
F21=Select all
Next, select with option 1 the system definitions that you want to send to the remote computer. Press
F21 if you want to send all the system information shown.
Page 11-30
Press Enter to confirm your choices and to display the next panel:
1/29/10
17:25:40
Mdl
F10
150
200
200
200
150
150
Method
*SNADS
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
F3=Exit Wizard
*YES
System Description
Non-existence, to test failure
SLS Web Server
QA Environment
100 to 5.4 Distribution
100 to 5.4 Designed to fail
USI Training box
Virtual system
F5=Reset to Defaults
More...
F12=Previous Panel
Finally, specify such information as the lowest release level of the target systems and whether or not
you want to create only one tape for all the distributions that will result from your selections during
this procedure. Refer to the online Help for detailed information about this panel. When youre
finished, press Enter to confirm your entries and to start the distribution process. The series of
messages youll see during the distribution are listed and described on page 11-33.
Distributing application definitions only
To distribute application definitions only, select option 2=Applications only on the second panel.
Because youre distributing application definitions, you need to indicate whether the application
definitions are remote or local definitions. (The panel displays text describing the difference between
remote and local definitions.) Specify this information and press Enter.
1/29/10
16:24:31
F3=Exit Wizard
F12=Previous Panel
F21=Select all
On this panel, select with option 1 the applications that you want to send to the remote computer.
Press F21 to select all the applications listed, including those displayed on subsequent panels.
TURNOVER for iSeries v100 2005-2010 UNICOM Systems, Inc.
Jul-10
Page 11-31
Press Enter to confirm your choices and to display the next panel:
1/29/10
17:25:40
Mdl
F10
150
200
200
200
150
150
Method
*SNADS
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
F3=Exit Wizard
*YES
System Description
Non-existence, to test failure
USI Web Server
QA Environment
100 to 5.4 Distribution
100 to 5.4 Designed to fail
USI Training box
Virtual system
More...
F12=Previous Panel
F5=Reset to Defaults
Next, specify such information as the lowest release level of the target systems and whether or not
you want to create only one tape for all the distributions that will result from your selections during
this procedure. Refer to the online Help for detailed information about this panel. When youre
finished, press Enter to confirm your entries and to start the distribution process. The series of
messages youll see during the distribution are listed and described on page 11-33.
Distributing system definitions only
To distribute system definitions only, select option 3=Systems only on the second panel and press
Enter. The next panel appears:
1/29/10
17:10:38
080
150
410
420
430
450
451
452
510
555
999
Serial
12345678
1000D6R
1038112
1038112
1038112
101314R
*V45111
*V45112
1048206
1048208
123456
Mdl
F10
150
200
200
200
150
150
150
400
999
620
System Description
Non-existent, to test failure
USI Web Server
QA Environment
100 to 5.4 Distribution
100 to 5.4 Designed to fail
USI Training box
Virtual system
Virtual
Development
Debs system
Pauls system
Bottom
ENTER=Next Panel
F3=Exit Wizard
F12=Previous Panel
F21=Select all
On this panel, select with option 1 the system information you want to send to the remote computer.
Press F21 to select all the systems listed, including those displayed on subsequent panels.
Page 11-32
Then press Enter to confirm your choices and to display the next panel:
1/29/10
17:25:40
Mdl
F10
150
200
200
200
150
150
Method
*SNADS
*NONE
*NONE
*NONE
*NONE
*NONE
*NONE
F3=Exit Wizard
*YES
System Description
Non-existence, to test failure
USI Web Server
QA Environment
100 to 5.4 Distribution
100 to 5.4 Designed to fail
USI Training box
Virtual system
F5=Reset to Defaults
More...
F12=Previous Panel
Next, specify such information as the lowest release level of the target systems and whether or not
you want to create only one tape for all the distributions that will result from your selections during
this procedure. Refer to the online Help for detailed information about this panel. When youre
finished, press Enter to confirm your entries and to start the distribution process. The series of
messages youll see during the distribution are listed and described below.
Distribution messages
During the distribution process, TURNOVER for iSeries v100 displays a series of status messages
in the lower left corner of the panel. These messages are:
Message
Description
Page 11-33
As indicated by the messages, all of this information is packaged in a save file and sent to the remote
computer, in care of user TURNOVER (or whomever you configured in Step 2.3). Once that
network file arrives on the remote, a message is sent to the user profiles message queue. The remote
receive TURCRARE job monitors the message queue, and upon receipt of a file, triggers two jobs:
1. The RCVTONET job, which receives the network file.
2. The RCWAUTORCV job, which unpacks the save file and restores its contents on the remote
box.
If this process fails, check your remote system for the job logs associated with these two jobs, and
review them for clues.
When the local distribution process completes, TURNOVER for iSeries v100 displays a system
message telling you if the save file distributed successfully or not.
UNICOM Systems, Inc. Note
The save file thats created remains in QTEMP after the process completes.
Page 11-34
Receiving the TURNOVER for iSeries v100 forms on the remote system, and
This discussion assumes that you have already submitted the form for processing on the development
computer with satisfactory results. Then you send the form to a remote production computer. On the
production computer, you or someone local receives the distribution and then submits the form to be
run.
(See the section following this one for a description of the automatic distribution process.)
Distribution Menu
Select option:
F3=Exit
F6=DSPMSG
F12=Cancel
F14=WRKSBMJOB
F21=System command
Page 11-35
Distribute Forms
_
_
_
_
_
_
_
_
_
_
Form
200039
200038
200037
200011
200010
200009
200008
200005
200004
200003
F3=Exit
Filter by App/Rel/Ver/Lev:
Filter by Reference:
5=Browse
Description
Add extended cmd
Chg Submenu custom
Emergency change to
Chg to Upload Wt.
Chg UPS Tables
Delete XAR distr.
Installment billg
Invoice form chg
Invoice form chg
Statement format chg
F4=List
App/Rel/Ver/Lev
SFTM
1
SFTM
1
AGL
2
DIST
2
DIST
2
DIST
2
AR
1
AP
1
AP
1
AP
1
F10=Redistribute
Run
1/05/10
1/03/10
1/03/10
1/01/09
12/16/09
12/16/09
12/15/09
12/12/09
12/07/09
12/06/09
F12=Cancel
Programmer
ELSINORE
ELSINORE
PSHIFTY
PHILLIPS
PHILLIPS
PHILLIPS
PSHIFTY
DELANEY
DELANEY
DELANEY
Status
RAN-OK
RAN-WRN
EMER-Ok
RAN-OK
RAN-OK
RAN-WRN
RAN-OK
RECOVER
CANCEL
RAN-WRN
F21=Select all
The list contains all forms eligible for distribution. Forms must have status RAN-xx, EMER-xx,
FIN-xx, or PARTIAL to be eligible for distribution.
You can select more than one form at a time. All forms that you select must be destined for the
same group of computers.
To redistribute a form that was distributed earlier (not showing on this panel), go to Step 3 on
page 11-38.
Page 11-36
System
Device
1 USITRAIN 450 *SNADS
1 *V45011 451 *SNADS
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*CURRENT
*CURRENT
*SBMRLS
Y
*NO
*CURRENT, date
*CURRENT, hhmmss
*NEXTDAY, *SBMHLD, *SBMRLS,...
Y, N
*NO, *RMT, *ALL
Receive
Select
*AUTOSTART
*AUTOSTART
Submit
Received
Form
Y
N
Form
Schedule
Date
*CURRENT
*CURRENT
Form
Schedule
Time
*RMTDFTS
*RMTDFTS
Schedule
Elapsed
Action
*RMTDFTS
*RMTDFTS
Bottom
F3=Exit
F12=Cancel
(Consult the online Help to learn about the valid values for the fields on this panel.)
All systems to which the TURNOVER for iSeries v100 forms should be distributed appear, along
with form receive and scheduling information for each system. All systems in the list are pre-selected
with option 1.
If you distribute the forms to all of the computers listed, the form status for each form becomes
DISTRIB.
If you dont want to distribute to all systems now, blank out the 1 next to the systems you dont want
to include. When the distribution job runs, the form status will become PARTIAL. You can
distribute the forms to the remaining systems at a later time.
Page 11-37
You can omit one of the systems from the list by selecting option 4=Remove. If you never intend to
send a change to that system, then normally the form status would remain PARTIAL; meaning that
the change has been distributed to some of the systems, not all. If you remove a system, then, once
you have distributed to all remaining systems, TURNOVER for iSeries v100 will update the form
status to DISTRIB.
If you have distribution authority, you can override the form receive and scheduling information for
each system you are distributing to by typing over the information as it appears for each system in the
list. You can also override the distribution job scheduling information appearing at the top of the list
if necessary.
When you press Enter, the form is transmitted using SNADS from the development computer to each
production computer you selected. If the distribution queue depth is set to a high number, it might
take awhile for the actual transmission to occur.
Once the distribution is sent, then you or another authorized local user must receive it manually and
submit it to be run. (This discussion assumes the form was not received automatically.)
Filter by programmer:
Filter by reference:
F3=Exit
Form description
Test Distribution 113
A/P Chk writing fix
Emer. Chg TESTDIST
Invoice form chg
Statement format chg
F4=List
Sys
WASH
USI
CDC
USI
FLOR
40
10
30
10
50
System description
Washington
Headquarters
Confederated Data Com
Headquarters
Florida Fifty Group
Dist
N
Y
Y
Y
Y
Dist date
1/15/10
1/15/10
1/15/10
1/15/10
12/29/09
F12=Cancel
All forms that TURNOVER for iSeries v100 has distributed are listed here, with the most recent
forms appearing first.
If the form status on the production computer is status Recover, redistribute the form from the
development computer by changing the Dist field from Y to N and press Enter; then distribute the
Page 11-38
form again using the instructions under Step 1 of this procedure. TURNOVER for iSeries v100 will
replace the original form with the new one.
The automatic receive autostart job, TURCRARE, is not running on your target system.
If forms are being distributed by media, load the medium in the reader and proceed.
To receive a form, select option 11 on the TURNOVER for iSeries v100 Main Menu.
Receive Forms
F3=Exit
.
.
.
.
.
.
.
.
*SNADS
TURNOVER
*CURRENT
*CURRENT
Y
N
N
N
F12=Cancel
Change or confirm the prompts and press Enter. The Select Network File to Receive panel appears.
Page 11-39
1=Select
1
_
_
_
Net File
T162401675
T162521676
T174543733
T175500755
F3=Exit
User
QSECOFR
QSECOFR
QSECOFR
QSECOFR
Sending User ID
UK
DELANEY
TORON
ALAS
Date
Sent
1/21/10
1/21/10
1/21/10
1/21/10
Time
Sent
09:43
16:32
09:01
18:54
Date
Arrived
1/21/10
1/21/10
1/21/10
1/21/10
Time
Arrived
10:01
17:05
18:01
19:33
F12=Cancel
Page 11-40
Submit Form
Form . . . . . . . . .
Application . . . . . .
Status . . . . . . . .
108888
T1
READY
Test form
Release:
Version:
Level:
*CURRENT, date
*CURRENT, hhmmss
*YES, *NO
1=Select
Opt
Form Submit Option
1
Error-check in batch
Error-check interactively
1
Submit form
Check for checked-out objects not on form
Work with form
1
Work with form distribution defaults
F3=Exit
F5=Refresh
F10=Form approval
F12=Cancel
F15=Scheduling
Select the Work with form distribution defaults option. Press Enter.
Continue with the next step.
87 For more about this submission panel, see Chapter 7: Submitting a TURNOVER for iSeries v100 Form to Run.
Page 11-41
Form . . . . . . 4100114
Description . . . Test form
Distribution job schedule date
Distribution job schedule time
Schedule elapsed action . . .
Automatic remote rollback . .
Position to system
2=Change 4=Remove
System
Name
Description
UK
UNICOM Systems,
WASH
UNICOM Systems,
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
*CURRENT
*CURRENT
*SBMRLS
*NO
Inc. UK
Inc. Washingt
*CURRENT, date
*CURRENT, hhmmss
*NEXTDAY, *SBMHLD, *SBMRLS,...
*NO, *RMT, *ALL
Device
*SNADS
TAP01
Receive
Logs
Back
N
N
Receive
Confirmation
Back
*RMTDFTS
N
F15=Scheduling
The online Help contains details about the valid values for the job scheduling and rollback fields
on this panel. To accept distribution defaults as they were defined in the System Send
Distribution Defaults, press Enter. The form is submitted for processing, then distributed as
youve specified. When the form(s) reach the target computer, they are received and submitted
for processing automatically. The form log is updated with information during each processing
step on each computer.
To override the distribution defaults, type 2 next to any system; then go to Step 3.
If an application is defined as a distributed application, TURNOVER for iSeries v100 presents this
panel when you submit a form for that application.
Some or all of the production systems might be defined for distribution.
Page 11-42
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.5103437
.Test form
.WASH
.UNICOM Systems Inc, Washington Office
Distribute . . . . . . . . . . . . . . . . . Y
Target user id and address. . . . . . . . . .TURNOVER
Distribution device. . . . . . . . . . . . . *SNADS
Distribute source. . . . . . . . . . . . . . N
Distribute objects . . . . . . . . . . . . . Y
Remote form schedule date. . . . . . . . . . *CURRENT
Remote form schedule time. . . . . . . . . . 23:30
Schedule elapsed action. . . . . . . . . . *NEXTDAY
Submit received form automatically . . . . . *RMTDFTS
Receive logs back. . . . . . . . . . . . . . *RMTDFTS
Receive confirmations back . . . . . . . . . *RMTDFTS
Receive forms method . . . . . . . . . . . . *AUTOSTART
F3=Exit
Y, N
S1014706 UserId-Address
Device, *SNADS, *NONE
*CURRENT, date
*CURRENT, time
*NEXTDAY, *SBMHLD, . . .
Y, N, *RMTDFTS
Y, N, *RMTDFTS
Y, N, *RMTDFTS
*AUTOSTART, *PASSTHRU
F12=Cancel
If any of the target systems are to be sent a distribution after the TURNOVER for iSeries v100 form
is complete, the TURNOVER for iSeries v100 job will submit the distribution job when the form
has completed successfully. Form status must be RAN-OK, FIN-OK, or EMER-OK.
A Y in the Distribute field indicates that the form is to be distributed to the target system when the
form completes successfully. An N indicates that it should not be distributed.
When you have completed reviewing these defaults, press Enter to return to the Submit
TURNOVER for iSeries v100 Form panel and submit the TURNOVER for iSeries v100 form.
Page 11-43
Page 11-44
__
__
__
11
__
__
__
__
__
__
__
Form
103340
103339
103338
103337
103336
103330
103327
103326
103325
103324
103320
F3=Exit
Description
Added by KLINE
Change worklist Prob
Create worklist Prob
Fixes to update pgm
Session or device er
Recursive call in ap
Error checkine not g
Error checking not g
Added by KLINE
Added by KLINE
Added by ELMSMIKE
F4=List
Appl/Rel/Ver/Lev: ____ __ __ __
Reference: __________
F5=Refresh
4=Cancel form
8=Work w/ job
5=Display form
9=Release job
Run
0/00/00
0/00/00
0/00/00
6/17/09
6/17/09
6/14/09
6/10/09
6/10/09
6/14/09
6/14/09
6/08/09
Programmer
KLINE
KLINE
KLINE
PHILLIPS
MARKSSUE
MILLER
ELMSMIKE
ELMSMIKE
KLINE
KLINE
ELMSMIKE
F23=More options
Status
READY
READY
READY
PARTIAL
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
RAN-OK
F24=More keys
More keys:
F7=DSPMSG
F10=Show APL-PND
F11=Alt Vw
Page 11-45
Form . . . . . . .
Description . . . .
Status . . . . . .
100613
Test Distribution 113
PARTIAL
2=Change
System
_ UK
2 WASH
Description
20 USI UK Office
40 USI Wash Office
F3=Exit
Distribution
Job
Date
Dist
DIS0000377
2/11/09 Y
DIS0000377
2/11/09 N
Device
TAP01
TAP01
Confirmed
Y
N
F12=Cancel
Type 2 next to a system entry to change the distribution status. Youll then see the panel illustrated
on the next page.
If confirmations have been received from all systems, then the form status will be CONFIRM.
You can determine if a form has been distributed, to which computers it has been distributed and
whether or not it has been run on the production computer(s).
Update status
1/29/10
14:35:28
Form . . . . . . . . . . .
Description
. . . . . . .
Status . . . . . . . . . .
5100613
Test Distribution 113
PARTIAL
Target system
WASH
. . . . . .
40
DIS0000377
2/11/09
Date
Distribution device . . . .
TAP02
Distributed . . . . . . . .
Y, N
Confirmation received . . .
Y, N
F3=Exit
F12=Cancel
Page 11-46
Copied
Approved
Submitted
Running
Completed
Distributed
Received
If the Send distribution defaults for the remote system are set as described above, then TURNOVER
for iSeries v100 sends a message to a sending computers user TOMSGRCV to update the remote
form log whenever one of these same actions occur for a distributed form on the remote system.
If the distribution defaults are set as described but the TOMSGRCV autostart job is not running,
incoming log messages cannot be processed and no entries are made.
The diagram on the following page illustrates how form logging works.
Page 11-47
MSGS
USER
TOMSGRCV
2
3
4
FORM COMPLETES
DISTRIBUTE FORM TO 5
SYSTEM 20
Update
TFORLOGF
Development
TFORLOGF file
entries:
Sys
10
10
10
10
10
20
20
20
20
20
30
30
30
30
Function
*CREATE
*SUBMIT
*RUNNING
*RUN
*DISTRIB
*RECEIVE
*SUBMIT
*RUNNING
*RUN
*DISTRIB
*RECEIVE
*SUBMIT
*RUNNING
*RUN
System 20
RECEIVE FORM
SUBMIT FORM
RUN FORM
FORM COMPLETES
MSGS
USER
TOMSGRCV
7
8
9
DISTRIBUTE FORM TO
SYSTEM 30
10
Update
TFORLOGF
System 20
TFORLOGF file
entries:
Sys
20
20
20
20
20
30
30
30
30
Function
*RECEIVE
*SUBMIT
*RUNNING
*RUN
*DISTRIB
*RECEIVE
*SUBMIT
*RUNNING
*RUN
System 30
RECEIVE FORM
SUBMIT FORM
RUN FORM
11
12
MSGS
USER
TOMSGRCV
13
FORM COMPLETES
14
Update
TFORLOGF
System 30
TFORLOGF file
entries:
Sys
30
30
30
30
Page 11-48
Function
*RECEIVE
*SUBMIT
*RUNNING
*RUN
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *CREATE record in the log on the development
computer (system = development computer).
2.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *SUBMIT record in the log on the development
computer (system = development computer).
3.
TURNOVER for iSeries v100 sends a messages to user TOMSGRCV on the development
computer; TOMSGRCV then writes a *RUNNING record in the log on the development
system.
4.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *RUN record in the log on the development computer
(system = development computer, status = RAN-OK).
5.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *DISTRIB record in the log on the development
computer (system = development computer, target distribution system = System 20).
6.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *RECEIVE record in the log on the development
computer (system = System 20). TURNOVER for iSeries v100 also sends a message to
TOMSGRCV on System 20. TOMSGRCV writes a *RECEIVE record on System 20
(system = System 20).
7.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *SUBMIT record on the development computer
Page 11-49
(system = System 20). TURNOVER for iSeries v100 also sends a message to TOMSGRCV
on System 20. TOMSGRCV writes a *SUBMIT record on System 20 (system = System 20).
Page 11-50
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer; TOMSGRCV then writes a *RUNNING record in the log on the development
computer. TURNOVER for iSeries v100 also sends a message to TOMSGRCV on System
20. TOMSGRCV writes a *RUNNING record on System 20 (system = System 20).
9.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *RUN record on the development computer (system =
hub computer). A message is also sent to TOMSGRCV on System 20. TOMSGRCV writes a
*RUN record on System 20 (system = System 20).
10.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on the development
computer. TOMSGRCV then writes a *DISTRIB record on the development computer
(system = System 20, target distribution system = System 30). TURNOVER for iSeries
v100 also sends a message to TOMSGRCV on System 20. TOMSGRCV writes a *DISTRIB
record on System 20 (system = System 20).
11.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on System 20.
TOMSGRCV then writes a *RECEIVE record in the System 20 form log (system = System
30). TURNOVER for iSeries v100 also sends a message to System 30s user TOMSGRCV,
which then writes a *RECEIVE record in the System 30 form log (system = System 30).
12.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on System 20.
TOMSGRCV then writes a *SUBMIT record in the System 20 form log (system = System
30). A message is also sent to TOMSGRCV on System 30. TOMSGRCV then writes a
*SUBMIT record in the System 30 form log (system = System 30).
13.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on System 20.
TOMSGRCV then writes a *RUNNING record in the System 20 form log (system = System
30). TURNOVER for iSeries v100 also sends a message to user TOMSGRCV on System
30, which then writes a *RUNNING record in the System 30 form log (system = System 30).
14.
TURNOVER for iSeries v100 sends a message to user TOMSGRCV on System 20.
TOMSGRCV then writes a *RUN record in the System 20 form log (system = System 30).
Page 11-51
TURNOVER for iSeries v100 also sends a message to user TOMSGRCV on System 30.
TOMSGRCV then writes a *RUN record in the System 30 form log (system = System 30).
To view the records that user TOMSGRCV has logged in file TFORLOGF, select option 4 (Work
with form log) 88 on the Distribution Menu.
The following panel appears:
Work with Form Log (WRKFORMLOG)
Type choices, press Enter.
Form number .
System name .
System number
Function . . .
.
.
.
.
+
Time period:
Beginning time
Beginning date
Ending time .
Ending date .
. .
. .
. .
. .
for
. . . . . .
. . . . . .
. . . . . .
. . . . . .
more values
*LAST
*PRV
*PRV
*PRV
Number, *LAST
Name, *PRV, *ALL
Number, *PRV, *ALL
*PRV, *ALL, *CREATE, *COPY...
.
.
.
.
.
.
.
.
*PRV
*PRV
*PRV
*PRV
Time,
Date,
Time,
Date,
F3=Exit
F4=Prompt
F24=More keys
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
F5=Refresh
F12=Cancel
*PRV,
*PRV,
*PRV,
*PRV,
*AVAIL
*AVAIL
*AVAIL
*AVAIL
Bottom
F13=How to use this display
Use this panel to describe the information you want to see in the list on the Work with Form Log
panel. Type your choices and press Enter (use the online Help if you need it).
88 Alternate path: type the Work Form Log (WRKFORMLOG) command on a command line.
Page 11-52
The Work with Form Log panel appears, positioned at the latest form:
1/29/10
13:20:53
Position to form . . .
5=Display local form
_
_
_
_
_
_
_
_
_
_
Form
5303023
5303023
5303023
5303023
5303023
5303023
5303023
5303023
5303023
5303023
Form
Description
NL Enable all
NL Enable all
NL Enable all
NL Enable all
NL Enable all
NL Enable all
NL Enable all
NL Enable all
NL Enable all
NL Enable all
DSPFs
DSPFs
DSPFs
DSPFs
DSPFs
DSPFs
DSPFs
DSPFs
DSPFs
DSPFs
System
DEV
DEV
DEV
DEV
DEV
HUB
HUB
HUB
HUB
HUB
8=Work w/job
10
10
10
10
10
20
20
20
20
20
Function
*CREATE
*SUBMIT
*RUNNING
*RUN
*DISTRIB
*RECEIVE
*SUBMIT
*RUNNING
*RUN
*DISTRIB
11=Distribution status
Date/Time
10/05/09 11:30:24
10/05/09 12:45:20
10/05/09 12:45:30
10/05/09 12:47:02
10/05/09 17:30:00
10/05/09 17:45:19
10/07/09 9:33:33
10/07/09 9:33:37
10/07/09 10:12:57
10/07/09 10:29:05
F17=Filters F21=Commands
F11 shows you an alternate view, including form status, programmer, and details. Use F17 to
manipulate the contents of the list.
You can also access this panel from the Work with TURNOVER for iSeries v100 Forms panel
(Main Menu option 6).
Page 11-53
Target System 20
Tape
Manual receive
Manual submit
Target System 40
Source &Objects
Automatic receive
System 40
Production
Computer
WASH T
Target System 70
Objects only
Automatic receive
Automatic submit
System 70
Production
Computer
TORONTO T
Target System 30
Objects only
Automatic receive
Automatic submit
System 30
Production
Computer
T
CDC
System 20
Development
System
U.K.
T = TURCRARE autostart job running
Page 11-54
This flowchart and the notes that follow it describe the steps that occur on the development and
production computers when forms are distributed.
A
Development Computer
1
Manually
Distribute Form
Automatically
Distribute F orm
13
Network?
Y
14
15
Select
Forms
SAVLIB Thhmmssjjj
to SAVEF ILE
Thhmssjjj
SAVELIB TURNWORK
to Media (tape)
16
End
5
Submit
Distrubution Job
SENDNETF
Thhmmssjjj to
TARGET USER
Production Computer
6
Create T emp lib
T nnnnnnnS
17
Auto Receive?
7
Y
*AUTOSTART
Network?
N
Create savefile
and templib
Thhmmssjjj
Create templib
TURNWORK
*PASSTHRU
18
19
T URCRARE
Submit Remote
Job to Receive
Netfile
20
Receive F ail?
10
Duplicate
Objects into
T nnnnnnnS
21
Successful Retry?
11
Copy T urnOver Info
to Thhmmssjjj or
T URNWORK
23
Submit Remote
Job to Unbundle
Netfile
12
MoveObjects from
TnnnnnnnS to
Thhmmssjjj or
T URNWORK
22
Wait for
Receive-wait-limit
End
24
A
25
Update form status
End
Page 11-55
Manually distribute forms. After forms are run successfully, you must select forms from a list
of eligible forms. See Distributing Forms Manually on page 11-35.
2.
Select forms. One or more forms can be distributed at the same time. The forms you select
must all be destined for the same set of computers. You cannot mix network distribution and
media distribution in the same run.
Multiple network distributions can be run concurrently. Distributions using tape or diskette
must be run one at time.
3/4.
Automatically distribute forms. Automatic distribution is initiated at the time you submit a
form to be run. Automatic distribution includes one form at a time.
Multiple network distributions can be run concurrently. Media distributions must be run one
at a time.
5.
Submit distribution job. Manual distributions can be run interactively or can be submitted to
batch, either to be run immediately or as a timed job.
Automatic distributions are submitted when the TURNOVER for iSeries v100 form
completes successfully (RAN-OK) by the TURNOVER for iSeries v100 job itself. It can
run in batch immediately, or as a timed job.
Note: For information about specifying the job queue for the manual or automatic
distribution job, see Specifying the distribution job queue on page 11-4.
6.
Create Temporary Library TnnnnnnnnS (where nnnnnnn is the form number). TURNOVER
for iSeries v100 uses this library to stage objects being distributed. If multiple forms are being
distributed at the same time, then multiple TnnnnnnnnS libraries are created.
7.
8.
If distributing via network, create savefile and temporary library named Thhmmssjjj, where
hhmmss is time and jjj is the last three characters for the distribution job number.
9.
If using media distribution, create temporary library TURNWORK. All media distributions
are done through this temporary library.
10.
Duplicate objects in TnnnnnnnS library. All objects on the TURNOVER for iSeries v100
form being distributed are duplicated from the production library into TnnnnnnnS library. If a
form line for a PF specifies File Copy FMTOPT of *FROMFILE, then TURNOVER for
iSeries v100 will distribute the data from the file. This enables you to pass data through from
test to production, and then onto target systems.
Page 11-56
11.
Copy TURNOVER for iSeries v100 Info. Create duplicates of TURNOVER for iSeries
v100 files in the distribution library (Thhmmssjjj for network distribution and TURNWORK
for media distribution) and copy form data into that library. This data is necessary to run a
TURNOVER for iSeries v100 form on the target system.
12.
Move objects from TnnnnnnnS to Thhmmssjjj or TURNWORK. Objects are moved from the
distribution form library to the distribution library. Duplicate object names from different
libraries are given an alias, as in the case of distributing multiple forms concurrently.
13.
Network? Is distribution via network (SNADS) or a medium (tape, diskette)? Refer to the
flowchart.
14.
If distribution is on network, the distribution library is saved to a savefile of the same name.
SAVLIB Thhmmssjjj to SAVFILE Thhmmssjjj.
15.
If distribution is via media, save library TURNWORK to a medium. Update the form status to
DISTRIB or PARTIAL.
SNDNETF Thhmmssjjj to Target User. The distribution network file is sent to the user
identified as the target user on the system distribution default panel for the target system.
17.
18.
If the system/application Send defaults on the development system for the production system
specify a Receive forms method of *AUTOSTART and the autostart job, TURCRARE is
running locally, the distribution will be received automatically.
If the system/application Send distribution defaults on the development system for the
production (target) system specify a Receive forms method of *PASSTHRU, then
TURNOVER for iSeries v100 will call a program on the target system to receive the
network file using the SBMRMTCMD command from the development system.
19-22. Receive fail? (*PASSTHRU only). If the network file has not yet arrived at the target system,
TURNOVER for iSeries v100 will retry the receive command. First, TURNOVER for
iSeries v100 will automatically retry in 10 seconds. Then TURNOVER for iSeries v100
will retry after waiting the time specified in the system distribution default field Auto receive
delay time for the number of times specified in the Auto receive retries field. If the receive
fails after the specified delay and retries, TURNOVER for iSeries v100 will stop attempting
to receive the distribution. It will continue with the next target computer on the distribution
list. You or someone else will then have to receive the distribution manually on the Target
system.
Page 11-57
23.
Submit job to unbundle netfile. TURNOVER for iSeries v100 will call a program on the
target system from the production system, if *PASSTHRU; using TURCRARE if
*AUTOSTART that will unbundle the contents of the savefile. See below for more about
what happens on the production computer.
24.
Submit job to receive netfile. TURNOVER for iSeries v100 will call a program on the
target system from the production system, if *PASSTHRU; or using TURCRARE if
*AUTOSTART that will store the contents of the netfile onto the receiving system.
25.
Update form status on development computer. If a form is distributed to all of the intended
computers, the form status is DISTRIB; if only some computers on the list, the form status
will be set to PARTIAL. Once run confirmations have been received from all of the target
computers at the development computer, the form status is set to CONFIRM.
Page 11-58
This diagram and the notes that follow it describe what happens on the target system when a form is
received.
1
2
Automatic Rece ive
Networ k?
Restor e librar y
TURNWORK
6
Restore libr ary
Thhmmssjjj
7
Crea te library
T nnnnnnnS
8
Move objects from
T hhmmssjjj to
T nnnnnnnS
9
Copy TURNOVER for iSeries v100 data
to TURNOVER for iSeries v100 file s
10
Copy dist ribution defaults
to TURN OVER for iSeries v100 files
11
12
Automatic submit?
Submit form to r un
13
14
Se nd log to host?
Se nd networ k spoolfile to
deve lopment computer
15
Confir m status?
N
16
End
Se nd conf irmation
message to developme nt
computer
Page 11-59
Automatic Receive. Forms are received automatically by a job initiated from the development
computer (*PASSTHRU method) or, as recommended, by the autostart job, TURCRARE,
running on the production computer (*AUTOSTART method). The receive of the savefile,
the unbundling of the savefile and the running of the TURNOVER for iSeries v100 form can
be initiated by jobs submitted automatically by the development computer.
2.
Manual Receive. You can receive forms manually at the target computer, either as a network
file or on media. If more than one distribution has been received as a network file,
TURNOVER for iSeries v100 will display a list from which you select the file(s) you want
to receive.
3/4.
Network? If the manual distribution is on media, you will select an option to receive the
distribution; in this case, restoring to library TURNWORK. Only one distribution can be
received at a time (once a receive step has been run, another one can begin).
If the manual distribution is using a network file, you will select an option to receive the file.
5.
Receive Netfile Thhmmssjjj. TURNOVER for iSeries v100 will receive a savefile called
Thhmmssjjj where hhmmss is the time and jjj the last three characters of the job name of the
distribution job on the development computer. If more than one distribution is queued up to
be received, TURNOVER for iSeries v100 will present you with a list from which to select.
6.
Restore library Thhmmssjjj. The savefile is restored into a library name of Thhmmssjjj.
7.
Create library TnnnnnnnS. A temporary library for each form called TnnnnnnnS (where
nnnnnnn is the form number) is created on the production computer.
8.
Move objects from Thhmmssjjj or TURNWORK to TnnnnnnnS library. Each object in the
distribution library is moved to the appropriate form library.
9.
Copy TURNOVER for iSeries v100 data to TURNOVER for iSeries v100 files. Control
data for each form is copied to TURNOVER for iSeries v100 files. The TURNOVER for
iSeries v100 entries are changed to conform to the application definitions on the target
computer. For example, production library names on each form line are changed to the library
names in the application definition locally. There must be a matching application definition
for the application level entry that matches the application and level on the form.
10.
Copy the distribution defaults to TURNOVER for iSeries v100 file TDISTHF. (See 11/12.)
Page 11-60
11/12. Automatic submit? The distribution history record (in TDISTHF) and the system Receive
distribution default record on the target computer control the degree to which processing is
automatic. TURNOVER for iSeries v100 will look at the defaults in TDISTHF first. If they
say to submit the form(s) to run, the form will be submitted. Otherwise, TURNOVER for
iSeries v100 looks at the Automatically submit received forms field in the systems Receive
distribution default entry. If that says Y, TURNOVER for iSeries v100 will submit the
form(s) automatically; otherwise the form(s) must be submitted to run manually.
13/14. Send log to host? If either distribution control file is set to have the run logs returned to host,
the TURNOVER for iSeries v100 will send network spool files to the development
computer.
15/16. Confirm status? If either distribution control file is set to have a confirmation message sent
back to the development computer, then TURNOVER for iSeries v100 will send a network
message to user TOMSGRCV on the development computer. This message will be processed
by job TOMSGRCV to update the distribution history record and form status there.
UNICOM Systems, Inc. Caution
Page 11-61
Page 11-62
INDEX
type defaults ............................................................ 42
update object description ......................................... 34
using method ........................................................... 31
X-Ref method .......................................................... 14
application relationships
working with ........................................................... 52
application Send/Receive defaults .......................... 11-18
applications
checking for related application conflicts.............6-44
related application checked indicator ................. 9-134
approval lists
description of ........................................................... 48
using ..................................................................... 5-22
approving a TURNOVER for iSeries form (on line) .645, 6-81
archive files .................................................................8-4
archive object library ................................................ 7-18
archived member .........................................................4-6
archived objects......................................................... 7-18
looking up............................................................. 8-29
restoring................................................................ 8-29
archived source ...........................................................4-3
ASP
using multiple ASPs ................................................ 32
Audit Adjustments Report....................................... 10-15
authority
application ..............................................................3-5
application definition..............................................3-3
assigning
to groups of users............................................. 9-16
authorization ...........................................................3-3
check-in ..................................................................3-3
creating conversion table entries .......................... 8-32
distribution ................................................. 3-3, 11-11
for distributed objects ......................................... 11-11
form ........................................................................3-3
forms .................................................................. 11-11
programmer information ................................ 3-3, 3-4
project .....................................................................3-4
purge.......................................................................3-3
purging forms/history .............................................8-3
to TURNOVER for iSeries forms .......................6-7
Authorized TURNOVER for iSeries Users Report ..1045
authorized users
for an application ..................................................... 46
auto receive job
recommendation for setting up ................. 11-3, 11-22
automatic distribution
description ................................................ 11-3, 11-21
initiating ............................................................. 11-55
*
*DATA files
working with ........................................................ 5-16
*NONE user group profile (authority) ...................... 9-16
*PROJECT (specifying test library names) .............. 9-76
A
adding a TURNOVER for iSeries form 6-6, 6-12, 6-30,
6-31
Allow group checkout? (global parameter)............... 5-22
application
default authority ................................................. 11-11
exploding data libraries ...................................... 11-15
application definition
accessing the Remote Configuration Wizard ............ 8
approval lists ........................................................... 48
authorized users....................................................... 46
completion messages............................................... 51
components of ........................................................... 9
creating ...................................................................... 6
default owner .......................................................... 12
defaults and rules .................................................... 13
deleting ...................................................................... 4
description ............................................................... 12
distributing .......................................... 8, 11-30, 11-31
distributing to remote system ............................. 11-27
distribution defaults................................................. 47
error recovery .......................................................... 24
error recovery threshold .......................................... 24
explode data libraries .............................................. 20
form defaults ........................................................... 23
from libraries ........................................................... 18
level check .............................................................. 33
library defaults ........................................................ 18
library list name ................................................ 23, 28
library lists .............................................................. 26
line defaults ............................................................. 31
maintaining ............................................................... 3
object authority ....................................................... 34
object create parameters .......................................... 34
object ownership ..................................................... 38
path defaults ............................................................ 19
project defaults ........................................................ 15
reference objects ............................................... 38, 40
relationships ............................................................ 52
renaming ................................................................... 5
require project entry ................................................ 17
submit finalization................................................... 23
target libraries ................................................... 10, 18
type codes................................................................ 39
INDEX-63
C
canceling a TURNOVER for iSeries form............. 6-10
category
definition ............................................................ 9-137
root ..................................................................... 9-144
subcategory ........................................................ 9-137
cautions
maximum storage allowed ................................. 11-60
storage considerations ........................................ 11-60
change history ............................................................. 4-1
changed objects
checking for.................................................6-43, 6-44
changing a forms distribution defaults ...................... 7-7
changing a TURNOVER for iSeries form ......6-6, 6-35
changing distribution defaults ..........................7-6, 11-42
changing type codes for CM schemes....................... 8-11
Check Application Definition Report ....................... 10-8
checked out objects
viewing ................................................................... 5-4
checking changed objects (multiple-progrmmer
checkout) .............................................................. 5-23
checking for changed objects ...........................6-43, 6-44
checking in source ...................................................... 5-1
checking out S/36 DFUs ........................................... 5-19
checking out S/36 Menus .......................................... 5-18
checking out source .................................................... 5-1
checkout history .......................................................... 4-4
Checkout/Check-in menu............................................ 5-2
CM method
overriding ............................................................... 8-9
CM scheme
changing type codes for ....................................... 8-11
creating ................................................................... 8-9
creating type codes for ........................................... 8-9
commands
ADDHLPTREE (Add Help Tree) ...................... 9-140
adding to a TURNOVER for iSeries form ........ 6-40
ADDLIBLE (Add Library List Entry) .................... 21
AUDITRPT (Audit Report) ............................... 10-11
CHECKOUT (Add TURNOVER for iSeries
Checkout) .......................................................... 5-8
CHGLIBL (Change Library List) ........................... 21
CHGPWLITM (Change Worklist Item)..9-128, 9-134
CHGSYSLIBL (Change System Library List) ....... 21
CHKCHGOBJ (Check Changed Objects) ............ 5-23
CHKOUTDFU (Checkout DFU) ......................... 5-19
INDEX-64
D
data areas
QUSRSYS/QLILMTLIBL...................................... 25
TALWKEYOVR ........................................... 36, 6-50
TDFTDAYM (Time worked for day, in minutes) 9-21
TDFTWEEKM (Time worked for week, in minutes)
......................................................................... 9-21
TDSTJOBQ (Distribution Job Queue) ................. 11-4
TLIB#...................................................................... 25
TNO2100 ............................................................... 6-9
TPROTECT ................................................... 36, 6-50
XREFOVRFLW............................................6-3, 6-76
defaults
application-level Receive ................................... 11-18
application-level Send ........................................ 11-18
for pre- and post-run commands .......................... 6-59
deleting a user from TURNOVER for iSeries v100 3-7
development computer ................................. 11-54, 11-57
development library .............................................2-1, 2-4
DFUs
S/36 ...................................................................... 5-19
displaying your current release of TURNOVER for
iSeries................................................................... 8-23
distributed object authority ..................................... 11-11
distributing changes automatically..... 11-3, 11-21, 11-55
distributing changes manually ........... 11-9, 11-34, 11-55
distributing logical files ............................................ 11-8
distributing objects .................................................... 11-6
distributing physical file data .................................... 11-7
distributing source code ............................................ 11-6
distribution
adding a system definition ................................. 11-19
application definitions .......................................... 11-4
authority ............................................................. 11-11
automatic distribution ........................................ 11-40
automatic submit ................................................ 11-60
E
escalation queue
purpose ................................................................. 9-79
working with9-6, 9-8, 9-10, 9-45, 9-53, 9-57, 9-80, 988
escalation rules ........................................................ 9-103
working with ........................................................ 9-10
exclusive lock (checkout parameter) ......................... 5-22
exit points
INDEX-65
F
FASTTASK
working with ...............................................9-43, 9-46
files
*DATA ................................................................ 5-16
TKEYPRTF ................................................... 36, 6-50
filtering TURNOVER for iSeries forms . 6-8, 6-9, 6-19
filtering TURNOVER for iSeries objects .......4-3, 4-13
form......................... See TURNOVER for iSeries form
form approval
how it works ............................................................ 50
form defaults
purpose .................................................................... 23
form dependencies ...................................................... 7-4
form distribution defaults
changing ................................................................. 7-7
Form Distribution Report ........................................ 10-43
form group jobs
working with ........................................................ 7-18
form jobs
types of ................................................................. 7-18
form log, using ........................................................ 11-46
form status .................................................................. 7-8
purpose ................................................................... 6-3
forms ....................... See TURNOVER for iSeries form
H
help trees
description ..........................................................9-137
finding information in ........................................9-148
setting up ............................................................9-138
using ...................................................................9-148
Helpdesk access command ..9-32, 9-37, 9-38, 9-40, 9-42,
9-43, 9-73, 9-88
Helpdesk project
creating .................................................................9-38
hourly rate ...................................................................2-4
How Used column (cross-referencing)
values for ..............................................................5-13
I
IFS ......................................... See Integrated File System
ILE conversion utility ...............................................8-32
Integrated File System
archive subdirectory ....................................... 14, 8-38
archiving IFS objects ............................................... 14
checking in objects ...............................................5-10
checking out objects ............................ 5-9, 5-10, 5-11
line defaults ............................................................. 38
object history ..........................................................4-6
viewing checked out objects...................................5-9
G
global TURNOVER for iSeries defaults
allocate form locks ............................................... 8-22
allow checkout by object only.............................. 8-18
allow group checkout ........................................... 8-20
automatic form lock checking .............................. 8-22
company name ..................................................... 8-20
distribution method .............................................. 8-21
duplicate library warnings .................................... 8-18
for programmer worklist ...................................... 8-31
IFS adopted authority user ................................... 8-21
IFS archive subdirectory ...................................... 8-22
level checking on checkout .................................. 8-20
manage S/36 object types ..................................... 8-20
name checking program ....................................... 8-20
programmer check at check-in ............................. 8-20
QNTC adopted authority user .............................. 8-22
reference objects library ....................................... 8-22
setting ................................................................... 8-17
INDEX-66
J
jobs
restarting a failed TURNOVER for iSeries job .7-22
scheduling form jobs ........... See scheduling form jobs
L
library list
for form promotion ...............................................6-32
in application definitions ......................................... 26
including with distributed application ................11-27
maintaining for remote systems............................... 28
maximum allowable number of libraries ................. 25
line defaults
for IFS ..................................................................... 38
purpose .................................................................... 31
M
manual distribution
eligibility for ........................................................ 11-9
running ............................................................... 11-55
steps ................................................................... 11-34
masks
name ........................................................................ 18
media distribution ................................................... 11-10
menus
S/36 ...................................................................... 5-18
messages
confirmation ....................................................... 11-11
receiver ............................................................... 11-12
method
description ............................................................... 31
purpose .................................................................... 31
restrictions ............................................................ 8-13
multi-level environment
checking out in ..................................................... 5-20
multiple checkout feature.......................................... 5-23
multiple environment distribution
recommendation for ............................................. 11-9
multiple-programmer checkout feature ..................... 5-22
N
name masks .................................................................. 18
network distribution ................................................ 11-10
new object rule
setting ...................................................................... 52
O
Object Distribution Report...................................... 10-44
object history
working with .......................................................... 4-1
Object History Report ............................................. 10-34
object locks
checking on form ........................................6-57, 6-67
object name ............................................................... 5-12
object references
working with ........................................................ 5-12
object stamping
turning off when distributing ....................11-6, 11-25
object type................................................................. 5-12
*DATA ................................................................ 5-16
object types
INDEX-67
INDEX-68
S
S/36 object types
managing .............................................................. 8-20
saving archived source off line ................................... 8-4
scheduling form jobs ................................................. 7-10
setting source-compare default command ................. 8-30
sorting TURNOVER for iSeries forms ... 6-8, 6-9, 6-19
source archive ........................................................... 4-23
source archive files ..................................................... 8-4
working with .......................................................... 8-4
Source Checkout History Report ............................ 10-38
source compare ............................................ 4-1, 4-2, 4-5
source compare option in PWM ............................. 9-124
source-compare
setting default command ...................................... 8-30
starting Wisedesk .................................................... 9-148
STRPWM (Start Pgmrs Worklist Manager) command. 9118
subcategory ............................................................. 9-137
submit finalization
description of .......................................................... 30
submitting a group of TURNOVER for iSeries forms
............................................................................. 7-12
submitting a recovery (undo) form ........................... 7-17
submitting a TURNOVER for iSeries form 7-5, 7-7, 715
system definition ..................................................... 11-20
adding................................................................. 11-19
distributing .............................................. 11-30, 11-32
distributing to remote system ............................. 11-27
T
TALWKEYOVR data area
description ...................................................... 36, 6-50
target release
default .................................................................. 8-18
Task Aging Report ........................... 10-28, 10-29, 10-30
TDFTDAYM data area
description ............................................................ 9-21
TDFTWEEKM data area
description ............................................................ 9-21
INDEX-69
INDEX-70
escalation table . 9-26, 9-39, 9-79, 9-80, 9-81, 9-82, 983, 9-85, 9-86, 9-103, 9-105, 9-106, 9-108
overview of.............................................................9-2
project views ..........................................................9-4
time reporting .......................................................9-14
user entry views ......................................................9-7
views ....................................................................9-41
TURNOVER for iSeries test plan
accessing ..............................................................9-73
TURNOVER for iSeries type codes
changing for CM schemes ....................................8-11
create command....................................................8-14
creating for CM schemes ........................................8-9
definitions ..................................................... 8-6, 8-12
description ............................................................... 39
object-only types ........................................ 8-12, 8-13
Sequence field ............................................ 6-39, 8-13
source-created object types...................................8-12
source-only ................................................. 8-12, 8-13
TURNOVER for iSeries v100
deleting a user from ................................................3-7
Type Code Conversion Table
working with ........................................................8-32
U
updating form distribution status.............................11-43
user profile ..................................................................2-3
user request/problem entry command ... 9-4, 9-7, 9-40, 941, 9-43, 9-44, 9-46, 9-47, 9-48, 9-49, 9-50, 9-51, 956, 9-73, 9-88
user requests/problems
working with .. 9-7, 9-10, 9-41, 9-46, 9-57, 9-63, 9-64
user-defined fields .....................................................9-28
user-defined options ....................................................4-7
for a TURNOVER for iSeries form...................6-40
user-defined parameters
defining ...................................................... 8-14, 8-15
using .....................................................................8-16
user-defined references
working with ........................................................5-14
using *PROJECT to specify test library names ........9-76
V
vendor environment
checking out in .....................................................5-21
viewing a TURNOVER for iSeries form ...............6-10
W
Wisedesk
overview .............................................................9-137
starting ................................................................9-148
X
X-Ref method ............................................................5-12
INDEX-71