PL/I (continued)

 

 

 

 

 

storage management

345

subprograms 331

 

 

 

VSAM support

131

 

 

PL/I and CICS

346

 

 

 

calling DUMP

346

 

 

CICS transaction backout

347

compatibility

346

 

 

 

execution options

346

 

file support

346

 

 

 

return from ON-units

347

 

statements not supported

346

transaction ABEND codes

346

PL/I calling SORT

 

 

 

 

interfaces offered

340

 

parameters to be passed

 

DDNAME PREFIXES

341

E15 EXIT PROCEDURE

341

EXIT E35

341

 

 

 

RECORD

341

 

 

 

RETURN CODE

341

 

SORT FIELDS

341

 

 

SORT MESSAGES

341

SORT TECHNIQUES

342

STORAGE

 

341

 

 

 

PL/I compiler options

 

 

 

EXEC & PROCESS cards

338

execution options

 

 

 

COUNT FLOW

337

 

 

ISASIZE

337

 

 

 

REPORT

337

 

 

 

SPIE STAE

338

 

 

options specific to DOS compiler

CATALOG

 

335

 

 

 

DYNBUF

336

 

 

 

LIMSCONV

336

 

 

LINK

336

 

 

 

 

NAME

336

 

 

 

 

WORKFILE

336

 

 

options specific to MVS compiler

GONUMBER

336

 

 

IMPRECISE

337

 

 

INTERRUPT

337

 

 

NUMBER

336

 

 

 

SEQUENCE

336

 

 

SMESSAGE or LMESSAGE 337

STATEMENT

336

 

 

TERMINAL

337

 

 

PL/I forcing an ABEND

 

 

automatic restart

345

 

 

usage of DISP in the JCL

344

PL/I overlay structures

 

 

conversion

345

 

 

 

overlay in MVS

345

 

 

plan components

 

 

 

 

assumptions

45

 

 

 

education

49

 

 

 

 

milestone events

48

 

 

plan components (continued) tasks 47

team

applications programmers 47 operations 47

project manager 46 systems programmers 46

plan development overview 41 recommendations

conversion method 42 conversion tools & automation 42 librarian 43

migration assignments 44

migration plan - guide and outline 42 migration responsibilities 43 project management 41

project staffing 43

two phase approach 42 references 41

plan examples project plan example

details 58 summary 56

project schedule 54 PLICANC 343 PLICKPT 342

PLINE mapping to JES2 LINE parms for RJE & NJE 227

PLIREST 342

POINTS macro 300, 308 POINTW/POINTR macros 299, 308 Poly-JES 225

portability 175

POWER

command equivalences 231 defaults 79

detailed comparisons with JES2 225 equivalent JES2 parameters 225 functional comparison with JES2 211 JES2 command equivalences 231 JES2 JECL comparison 89

JES2 parameter mapping 225 major POWER-JES2 differences 207 other differences POWER-JES2 209

POWER/JES2 command equivalences 231 POWER/JES2 detailed comparisons 225

exit comparisons

JES2 patching facility 231 source code modifications 231

mapping POWER parameters to JES2 init parms define BSC remotes 228

define compaction tables 230 define NJE nodes 230

define SNA remote workstations 229 equivalent JES2 parms for POWER macro 225 PLINE mapping to JES2 LINE parms for RJE &

NJE 227

Index 611

Page 635
Image 635
IBM OS/390 manual Pl/I

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.