CICS (continued)

 

 

 

 

 

 

MRO

136

 

 

 

 

 

 

 

 

MVS management modules

142

 

PL/I

346

 

 

 

 

 

 

 

 

problem determination considerations

153

programs

252

 

 

 

 

 

 

run-time options

366

 

 

 

 

shutdown statistics 137

 

 

 

 

system

 

 

 

 

 

 

 

 

control blocks

138

 

 

 

 

data sets requirements

 

145

 

 

initialization parameters

 

140

 

 

program interface

147

 

 

 

 

programming commands

147

 

testing considerations

153

 

 

 

transaction

 

 

 

 

 

 

 

attributes

144

 

 

 

 

 

backout

 

347

 

 

 

 

 

 

security

 

149

 

 

 

 

 

 

server

133

 

 

 

 

 

 

translator option

252

 

 

 

 

unsupported products

136

 

 

 

UPSI

149

 

 

 

 

 

 

 

 

user exits & abnormal termination exits

367

vendor applications

154

 

 

 

 

virtual storage considerations for MVS

135

CISIZE

122

 

 

 

 

 

 

 

 

CLIST language 163

 

 

 

 

 

cloned DASD

 

432

 

 

 

 

 

 

CLOSE macro

 

298, 305, 314

 

 

 

 

CMDCHN 339

 

 

 

 

 

 

 

CMS usage

429

 

 

 

 

 

 

CNTRL macro

 

296, 298, 306, 314

 

 

COBOL

 

 

 

 

 

 

 

 

 

applications

242

 

 

 

 

 

CICS considerations

366

 

 

 

 

CICS programs

252, 366

 

 

 

 

COBOL for OS/390 and VM general

 

comments

249

 

 

 

 

 

 

COBOL for VSE/ESA

354

 

 

 

 

coding problems

253

 

 

 

 

comparison of IBM COBOL compilers

250

compiler comparison

250

 

 

 

 

compiler options

260

 

 

 

 

compiling converted programs

265

 

CONFIGURATION SECTION - SPECIAL-NAMES

paragraph

255

 

 

 

 

 

 

conversion tools

492

 

 

 

 

DATA DIVISION

256

 

 

 

 

 

DOS/VS COBOL

356

 

 

 

 

 

DOS/VS COBOL CICS programs

252

 

DOS/VS COBOL conversion

252

 

DOS/VS COBOL using REPORT WRITER

253

ENVIRONMENT DIVISION

255

 

 

file attribute mismatches

258

 

 

file handling

257

 

 

 

 

 

file status codes

257

 

 

 

 

from COBOL for VSE/ESA

 

259

 

 

COBOL (continued)

 

 

 

 

 

 

from VS COBOL II

258

 

 

 

 

general comments on COBOL for OS/390 and

VM

249

 

 

 

 

 

 

 

 

 

IBM COBOL & CICS CCCA

522

INPUT-OUTPUT SECTION

 

255

 

introduction

249

 

 

 

 

 

 

ISAM support

 

258

 

 

 

 

 

 

language differences DOS/VS COBOL and COBOL

for OS/390 and VM

 

253

 

 

migrating object code

251

 

migrating VSE to OS/390

 

250

 

migration considerations

 

250

 

OS/390

131

 

 

 

 

 

 

 

 

OS/VS

 

131

 

 

 

 

 

 

 

 

overall conversion

 

259

 

 

 

PL/I comparison

351

 

 

 

 

PROCEDURE DIVISION

 

256

 

program termination

257

 

 

recovery example

526

 

 

 

 

reserved words

263, 265

 

 

running converted programs

265

subprograms

331

 

 

 

 

 

 

subprograms called by RPG II

331

unavailable compiler options

260

useful publications

 

252

 

 

 

VM 131

 

 

 

 

 

 

 

 

 

VS COBOL II

355

 

 

 

 

 

 

VS COBOL II CICS programs

259

VS COBOL II compiler options

261

VSAM support

259

 

 

 

 

 

 

VSE compiler conversion

 

259

 

VSE/ESA

354

 

 

 

 

 

 

 

coding problems in COBOL

 

253

 

coexistence CICS/VSE & TS

 

153

 

COLBIN

 

339

 

 

 

 

 

 

 

 

 

command

 

 

 

 

 

 

 

 

 

 

 

authority for remote operators

453, 454

comparison

242

 

 

 

 

 

 

equivalences POWER-JES2

231

level coding (HLPI)

 

171

 

 

 

procedures

 

163

 

 

 

 

 

 

COMMAREA

152

 

 

 

 

 

 

 

common applications - naming conventions 549

DB2 naming conventions

 

550

 

generation data sets

551

 

 

TSO naming conventions

 

549

 

VSAM data set naming conventions 550

communication bytes

 

275

 

 

 

 

Communication Region

 

81, 274

 

communication region simulation

276

compaction tables

230

 

 

 

 

comparing

 

 

 

 

 

 

 

 

 

areas

 

181

 

 

 

 

 

 

 

 

IBM COBOL compilers

250

 

physical IOCS elements

 

328

 

POWER and JES2 JECL

 

89

 

PRINTDEV statement parameters 238

Index 595

Page 619
Image 619
IBM OS/390 manual Cics, Cobol

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.