Standard Dictionary Reports—DREPORTS › Teleprocessing Entity Reports › Task Reports (DREPORTs 011, 061, 081) › Task Detail and Key Reports (DREPORTs 011 and 081)

Task Detail and Key Reports (DREPORTs 011 and 081)

Contents

The task detail report provides detailed information about all task occurrences; the task key report provides similar information about selected task occurrences. The fields and format of these two reports are the same.

The report below shows sample output for DREPORT 081. The DREPORT and KEY parameters used to create this sample report are:

DREPORT=081
 KEY TASK-NAME-025 'TESTBYE'

Sample DREPORT 081:

 REPORT NO. 81                                   DATA DICTIONARY REPORTER  REL nn.n                       mm/dd/yy        PAGE   1
 DREPORT 081                                                TASK REPORT


 *********************************************************************************************************************************
                                                                                                               ---- D A T E ----
 TASK                                                                                                          UPDATED   CREATED
 *********************************************************************************************************************************


 TESTBYE  VER     1                                                                                            mm/dd/yy   mm/dd/yy
     PREPARED BY LHN
     REVISED BY  LHN
     DESCRIPTION TEST TASK
     PUBLIC ACCESS ALLOWED FOR ALL AUTHORITY
   USER LHN                               RESPONSIBLE FOR CREATION AND UPDATE AND DELETION
     WITHIN SYSTEM LHNSYSTEM                        VER     1
         INVOKES PROGRAM RHDCBYE  VER     1
     DIVISION             DOCUMENT
                     COMMENT
                      00000100  THIS IS A TEST TASK OCCURRENCE

Field Descriptions

The format of DREPORTs 011 and 081 depends on the order in which information was defined to the dictionary. A description of the fields on the sample report follows:

TASK

Identifies the name and version number of the task occurrence being described.

DATE UPDATED/CREATED

Identifies the date the task occurrence was last updated (if updated) and the date the task occurrence was defined to the dictionary. Task occurrences that are defined through the DC/UCF system generation compiler do not have these dates associated with them.

PREPARED BY/REVISED BY

Identifies the user who defined the task occurrence to the dictionary and the user who last updated it.

DESCRIPTION

Identifies text associated with the task occurrence.

PUBLIC ACCESS

Identifies the level of access allowed for unregistered users.

USER

Identifies a user who is registered to access the task occurrence and identifies any responsibility codes and associated text defined for the user. If no users are registered for the task, the USER literal does not appear; if no responsibility codes are associated with a user, the RESPONSIBLE FOR literal does not appear.

WITHIN SYSTEM...INVOKES PROGRAM

Identifies a system associated with the task occurrence and the initial program invoked by the task.

Class/attribute associations

Identifies class/attribute associations that have been defined for the task. In this sample report, the attribute DOCUMENT within class DIVISION is associated with TESTBYE.

COMMENT

Identifies commentary text associated with the task through the COMMENTS clause of the DDDL TASK statement.

User-defined comments

Identifies user-defined comments that were defined through the DEFINITION/comment-key clause of the DDDL TASK statement.