loading a DAM File (Fixed-Length Records without keys) 323

loading a DAM File (Undefined or Variable-Length Records) 323

LOCK & UNLOCK macros 281 log manager 145

logical library structure 389 logical partitioning 422 LOGON procedures 157 LOGREC 475

LPAR systems 421 LTM subparameter 105

M

macro level programs 137, 148

Macro Resource Definition Table changes 140 macros

call 272

data management 292 Define The File (DFT) 98 ICCF 167

linkage 271 multitasking 283 system 268 virtual storage 289 VSAM 290

main program parameter passing 335 maintaining your OS/390 libraries and SMP/E

zones 431

maintenance environment 431 major POWER-JES2 differences 207 managed SAM files 122 managed storage 100 management criteria 548 management disciplines 25 managing

change 411

display consoles 444 problems 411 projects 440

managing remote operations 452 JES2 RJE operations

command authority for remote operators 453 host operations 452

remote workstation operations 452 remotes without consoles 453 using SDSF panels for RJE 453

NJE operations

command authority for remote operators 454 using SDSF panels for NJE 454

manipulating data 159

manual OS/390 conversion 502 mapping

ISV products and functions 539 options 354

PLINE to LINE 227

POWER parameters to JES2 init parms 225

mass conversion - background, benefits & method 486

automated conversion process 490

CORTEX MS

Assembler conversion tools 492 COBOL conversion tools 492 file transfer 492

inventory validation 492 JCL conversion tools 492 translate languages/programs 492

IBM MVS-MS - background 486 mass conversion tools 489 overview/benefits

automated conversion 488 automation limits 489

mass conversion (switchover) 489 repetitive conversion 488

mass conversion overview/benefits 487 mass conversion phase overview 493 mass conversion tools 489

mass migration 27, 52 master catalog 114 math services 365 MCS consoles 445 MEDIUM 339 MERGECAT option 119 mergers/acquisitions 5 message facilities 157 message formats 446 message replies 446

methodology accounting management 472 methodology of change management 461 methodology of systems management 457 migrating

AFP resources 240

interlanguage communications applications 358 object code 251

print applications 241 reasons 3

run-time environments 354 support material 134

VSE to OS/390 250 migrating from LE/VSE 359

callable services & math services CEETDLI 366

LE/VSE 1.4 locales 366 run-time options

recommended settings for options 363 run-time options & LE/VSE 1.4 and later

releases 362

run-time options and LE/VSE 1.1 361 user exits & abnormal termination exits

abnormal termination exits 365

abnormal termination exits & LE/VSE 1.4 and later releases 365

Assembler user exits 364 high-level language exits 364

606VSE to OS/390 Migration Workbook

Page 630
Image 630
IBM OS/390 manual Cortex MS

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.