also build lists of personal data sets. Personal data set lists are a good way to group (by project, for example) those data sets that you use frequently.

Ability to run foreground and batch processors such as Assembler H, VS COBOL, VS FORTRAN, PL/I optimizing compiler, Binder/Linkage editor, C/370, REXX/370, and C/C++ for MVS/ESA.

Ability to test individual dialog elements and complete dialogs using ISPFs Dialog Test option.

Ability to keep statistics about each data set member including which user updated it, date it was created, date and time it was changed.

Ability to see and work with the data sets which are allocated to your TSO user ID using the ISPF ISRDDN program. Although ISRDDN is considered a diagnostic tool, you may find it very useful in many situations, such as:

viewing allocations including data set characteristics,

editing, viewing, browsing allocated data sets,

freeing allocations,

compressing allocated partitioned data sets,

querying ENQs against a data set,

locating where a member exists in a concatenation.

For more information about these features and functions see the OS/390 ISPF

Users Guide and SDSF Guide and Reference.

For the latest ISPF release features, hints and tips, free software, ISPF newsletters, and information on how to access ISPF forums, visit the ISPF Web site http://booksrv2.raleigh.ibm.com/ispf/

27.1.1 Editing Data Sets

While TSO provides an editor, it is rarely used; most editing of data sets is done using the ISPF editor. The ISPF editor edits both sequential and partitioned data sets, with the majority of activities centered around partitioned data sets. The system programmer can easily edit system data sets such as SYS1.PARMLIB, while development programmers can edit program source. Production control personnel can edit job and PROCedure data sets. The ISPF editor has a program interface so that the edit function is available from any ISPF dialog with a custom look.

Edit provides functions such as:

locating a particular line in the data,

submitting edit data as a job stream for background execution,

setting RECOVERY mode on so that edit keeps track of any changes that you make while editing data and if a system crash occurs, you will be able to recover and continue editing from the last interaction,

saving the data without ending the edit session,

canceling edit without saving the data,

using the COMPARE command to compare, display, and merge differences between the data being edited and another file,

438VSE to OS/390 Migration Workbook

Page 462
Image 462
IBM OS/390 manual Editing Data Sets

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.