Manuals / IBM / Computer Equipment / Server

IBM OS/390 manual Other Differences Performance, Installation Exits

Models: OS/390

1 673
Download 673 pages 53.75 Kb
Page 267
Image 267

Table 31 (Page 2 of 2). VSE - OS/390 Command Comparison

VSE or POWER Command

JES2 Command

Comment

 

 

 

 

PSTOP devname

 

 

Drain the printer

[,EOJ

$P

PRTnnnn

- wait for current job to finish

RESTART

$I

PRTnnnn

- interrupt current job, restart from ckpt

FORCE. ]

F FSSx,FORCE,PRTnnnn

- Only use if nothing else works

 

 

 

 

PXMIT devname

$T

PRTnnnn

Change printer selection criteria

[, C L A S S = ]

[, C L a s s = ]

- SYSOUT Classes

[,LOGDEST= . ]

[,Routecde= ]

- Route codes (Logical destinations)

 

 

 

PFLUSH devname

$C PRTnnnn

Cancel output on printer

[,HOLD ]

$E

PRTnnnn

- Restart output on printer

 

 

 

 

PRESTART devname

$B

PRTnnnn,pages

Backspace printer

[,count ]

$F

PRTnnnn,pages

Forward-space printer

 

 

 

 

PGO devname

$S

PRTnnnn

Restart printer after setup or interruption

 

 

 

 

VSE Partition Command

 

 

 

 

 

 

 

TRACE devname

$T

PRTnnnn,TRace=Y

Enable printer for tracing

 

$S

TRACE(nn)

Activate tracing: nn = 11, 12, 14 & 15

 

 

 

TERM devname

$P PRTnnnn

Drain printer and then

 

$C

PRTnnnn

Cancel output on printer

 

 

 

 

TRAP devname

 

 

(Use MVS SLIP)

 

 

 

IGNORE devname

$T PRTnnnn,TRace=N

Turn off tracing.

 

 

 

 

SET F O R M D E F =

-

 

Use PSF Exit APSUX07

P A G E D E F =

 

 

 

 

 

 

 

SET J S E P S =

$T

PRTnnnn,SEP=

(must restart FSA after $T)

 

 

 

or use PSF Exit APSUX01, -02, -03

 

 

 

 

11.5 Other Differences

11.5.1 Performance

The same factors affecting performance in VSE also apply in OS/390. The speed of the printer, complexity of the output stream, transmission speeds, VTAM and NCP parameters, host and printer resources all figure into the performance of the printing.

11.5.2 Installation Exits

PSF/VSE has no installation exits. PSF/MVS provides installation exits for your use in coding and installing modifications to PSF functions. For example, with these exits, you can:

∙Create your own separator pages, or modify separator-page formats supplied by PSF

∙

∙

∙

∙

Modify, add, or suppress output records

Modify system management facilities (SMF) type 6 records

Inspect, redirect, or suppress PSF messages

Manage resources

See Chapter 17 ²Using Installation Exits² in the PSF/MVS Systems Programmers Guide, especially the section ªDo¢s and Don¢tsº at the front of that chapter.

Chapter 11. Advanced Function Printing and Print Services Facility/MVS 243

Page 266 Page 268
Page 267
Image 267
IBM manual Other Differences Performance, Installation Exits, 2 of 2. VSE OS/390 Command Comparison
Page 266 Page 268

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.