6 2 2 Task Tracking Settings

LANSA for i

previous page next page

6.2.2 Task Tracking Settings

To display the Work with Task Tracking Settings screen, select Administration from the Main System Menu (Advanced), choose Review system settings from the Administration Menu and then select Task tracking from the Review of System Settings menu.

 

  DC@P8117        Work with Task Settings 

  

  System wide settings      

  Product level task tracking

           prefix . . . . . . . : *T   check in unlocking  . . . : Y

  Developer task tracking

           prefix . . . . . . . : *U   check in unlocking  . . . : Y

  Minimum task tracking

           prefix . . . . . . . : *N   check in unlocking  . . . : Y 

  Retain task history on REORG . . . . . . . . . . . . . . . . . : Y  

  Lock functions to same task as process . . . . . . . . . . . . : N 

 

  Partition XXX settings 

    Task tracking active . . . . . . . . . . . . . . . . . . . : Y

            User require task to work. . . . . . . . . . . . . : Y 

            Prompt/Confirm task id . . . . . . . . . . . . . . : Y  

            Allow user to change task  . . . . . . . . . . . . : N  

            Disable special task security . . . . . .  . . . . : N  

            Task tracking for imports    . . . . . . . . . . . : N   

 

  Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages Fnn=Change            

 

 

 

The settings on the Work with Task Settings screen are retrieved from the data areas and the partition details. Authority to change these values will be available if you have IBM i change authority to the data areas, LANSA authority to the partition maintenance and task tracking menus and LANSA authority to change the current partition values.

Setting

DC@A01

DC@A07

DC@OSVEROP

Prefix and Unlocking

 

640 – 648

 

History

 

639

 

Lock functions

 

 

*TTG6FUNCLOCKING

Task tracking flags retrieved for the current partition.

 

 

Product level task tracking prefix and check in unlocking

Positions 644-645 and 648 in data area DC@A07.

These are optional settings. The prefix is a two character value and is associated with an Unlock Object after Check In flag.  When this flag is set to "Y", an object is unlocked from the task both on the IBM i and on the workstation when it is checked in. At the same time, it is changed to read-only on the workstation. To change an object again on the workstation, you must check it out for update.

This may be used if you wish to use Task identifiers assigned to products. It is suitable for small teams which have little cross-over between products. It is recommended product-oriented task identifiers use "*T" as the first two characters. If you follow this recommendation, you could, for example, create task identifiers *T00000A and *T00000B for a Product A and Product B. Users need to be authorized to product-oriented tasks as is usual.

Developer level task tracking prefix and check in unlocking

Positions 642-643 and 647 in data area DC@A07.

These are optional settings. The prefix is a two character value and is associated with an Unlock Object after Check In flag.  When this flag is set to "Y", an object is unlocked from the task both on the IBM i and on the workstation when it is checked in. At the same time, it is changed to read-only on the workstation. To change an object again on the workstation, you must check it out for update.

This option may be used if you wish to have Task identifiers assigned to individual developers. It is suitable for small teams where there is little cross-over between developers. It is recommended developer-oriented task identifiers use "*U" as the first two characters. It is strongly suggested that an appropriate naming convention be used to identify tasks with users. If you use the recommended prefix, you could, for example, create task identifiers such as *U000BOB or *U00MARY. Only one user can be authorized to a developer-oriented task.

Minimum level task tracking prefix and check in unlocking

Positions 640-641 and 646 in data area DC@A07.

These are optional settings. The prefix is a two character value and is associated with an Unlock Object after Check In flag.  When this flag is set to "Y", an object is unlocked from the task both on the IBM i and on the workstation when it is checked in. At the same time, it is changed to read-only on the workstation. To change an object again on the workstation, you must check it out for update.

This level of task tracking is suitable for small teams with trusted developers. It uses one task for the entire system. Only system internal task tracking activities are performed. There is no locking out of objects and you cannot export by task or inquire on task history. The recommended prefix for the single permanent task is "*N". A suggested name for this task is "*NONE". All users can use this task and they do not need to be authorized to it.

Retain task history on REORG

Position 639 of data area DC@A07.

"Y" indicates that task history is to be retained. "N" indicates that the next Request Submit LANSA Re-org job will have Purge Task History starting from date pre-filled with today's date.

Lock functions to same task as process

Setting *TTG6FUNCLOCKING in data area DC@OSVEROP.

If this value is "Y", then all functions are required to be locked with the same Task ID as the parent process. This flag only applies when the Allow user to change tasks partition configuration flag is set to "N". If an inconsistency between these settings exists, a warning message will result. You may Enter to accept the setting despite the warnings or cancel to abandon the changes.

Partition settings

Refer to Configure Task Tracking in Partition Definitions - Create, Change or Delete.

previous page start next page