Edit in DEV1

This section provides information about how to perform Edit. 

Edit Module

Once the module is checked out to the DEV1 level, it can be updated.

Type S to invoke Edit. You don’t need to remember the file/dataset names associated with components because the necessary logistics or infrastructure information is already contained in the ISPW repository. In this example, the bottom (update) level is a PDS called TRNG.PLAY.DEV1.CLIST, as shown in the following figure. ISPW uses that dataset automatically, so users don’t need to know its name.

Edit Module

Task List Stats are Updated

The module’s last operation is updated to S, and the UserID and date and time fields are all updated.

Update operations change the statistics. However, operations such as Print and Compare (to be discussed later), do not update the statistics, because there is no real state change in the module.

Support for Various Editors

Different editors may be attached to different types of modules. For example:

• QMF types (forms, procs, and queries), invoke the QMF environment.
• Telon types invoke TDF (Telon’s development environment).
• SDF II types invoke IBM’s SDF (screen definition facility) interface.
• HFS files invoke OEDIT on Unix Systems Services.
• And so on.

Support for Various File and Data Types

Modules may be in PDS members, Adabas files, VSAM files, HFS files, or basically any type of file.