setting up AFP resources (continued)

SNA Network Interconnection (SNI) 189

migrating print applications (continued)

SNAP macro 279

OS/390 dynamic allocation & output descriptor

softcopy books

412

macros 242

softcopy library

412

PL/I 242

software configuration library manager (SCLM) 391,

printing from TSO

241

 

440

 

 

 

 

 

REXX

242

 

 

 

 

software partitioning

 

423

 

VSE printer PARM macro

241

Software Project Office

539

migrating resources from VSE to OS/390

SoftwareXcel SystemPac/MVS 406

defining resources

240

 

SORT

 

 

 

 

 

migration without the source 240

control statements

377

remote-resident resources

240

DFSORT/VSE control statements 379

transferring print streams

241

DFSORT/VSE migration considerations 379

setup JES2 resources

209

 

FIELDS

341

 

 

 

 

shared

 

 

 

 

 

ICETOOL

380

 

 

 

application code

50

 

 

JCL statements

375

 

DASD 404, 425

 

 

 

 

MESSAGES

341

 

 

 

DASD between OS/390 test systems 432

multiple data sets

 

132

 

DASD between VSE and OS/390 (vs. cloned

programming support

131

DASD)

433

 

 

 

 

suicide

131

 

 

 

 

DASD vs. cloned DASD

432

TECHNIQUES

342

 

 

volume ownership

 

120

 

VSAM considerations

131

shareoptions

125

 

 

 

 

source code modifications

231

SHAREOPTIONS (X 3)

130

 

source program inventory

14

SHAREOPTIONS (X 4)

130

 

space classes

125

 

 

 

SHOWCB macro 292

 

 

 

space management

100

 

shutdown statistics

137

 

 

SPIE STAE

338

 

 

 

 

SIE 405

 

 

 

 

 

spool

 

 

 

 

 

single

CPU cross-region sharing

126

CICS interface 151

single

region data set sharing

128

interface restrictions 151

single switchover 28

 

interfaces 221

 

SIS option (Sequential Insert Strategy) 340

interfaces - other

222

SISIPT data 73

 

space allocation

221

SISRO - CORTEX-Migration System

volumes JES2

210

 

(CORTEX-MS)

524

 

spooling

73

 

 

sizing migration effort

18

SPUFI

179

 

 

areas of VSE & OS/390 differences

SQL/DS to DB2

 

 

batch & online program conversion 14

descriptions of users

 

files 15

 

 

application developers

179

Job Control Language 15

database administrators (DBAS) 180

operations

16

 

end users

178

 

source program inventory 14

security administrators

181

source programs

14

system administrators

180

basic VSE vs. OS/390 functions & components 16

ISQL and SPUFI 179

 

introduction

13

 

other comparison areas

 

project objectives definition

13

data replication and data access

182

sliding window definition

579

 

DRDA considerations

182

 

SLIP

475

 

 

 

other product areas

182

 

 

SMESSAGE or LMESSAGE

337

 

transaction management

182

 

SMF

22, 395

 

 

year 2000

181

 

 

 

SMP/E

23

 

 

 

summary of migration Task

182

 

SMP/E zone maintenance

431

 

SQL/DS to DB2 for OS/390 migration

178

SMPO (Software Project Office)

539

SRM 22

 

 

 

 

SNA

 

 

 

 

STACKER 339

 

 

 

 

attached printers 236

 

 

staff availability

12

 

 

 

migration

485

 

 

staffing strategies

29

 

 

 

network

191

 

 

stand-alone Fast Copy 397

 

 

remote workstation definition

229

 

 

 

 

 

Index 615

Page 639
Image 639
IBM OS/390 manual Rexx, Sort, Fields, Icetool, Messages, Techniques, Shareoptions X, Spufi, Slip, Smf, Smp/E, SNA Stacker

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.