Table 18.

PLINE MACRO to JES2 Parameter Mapping

 

 

 

 

 

PLINE

Description

JES2 LINE

Comment

Parameter

 

Parameter

 

 

 

 

 

A D D R =

Unit address of the BSC

U N I T =

²SNA² or unit address

 

emulator port or CTC adapter

 

(4-digit addresses

 

 

 

supported)

 

 

 

 

CODE

EBCDIC is the only value

L I N E C C H R =

EBCDIC or USASCII

 

allowed. (ASCII is not supported)

 

supported

 

 

 

 

INTRPT

Selector channel mode

N/A

Option not in JES2

 

 

 

 

MODSET

BSC (2701) Adaptor

INTERFACE=

BSC adapter interface &

 

characteristics

C O D E =

code

 

 

 

 

PSWRD

Line password

P A S S W O R D =

BSC or dedicated SNA line

 

 

 

 

SWITCH

Switched line or leased

N/A

Don¢t specify LINE= on RMT

 

 

 

statement for switched lines

 

 

 

 

TIMEOUT

Number of idle minutes before

(not on LINE

Specify DISCINTV= on the

 

forced off

parm)

RMT(nnnn) statement.

 

 

 

 

TRNSP

Transparency feature

T R A N S P A R =

Text transparency required

 

 

 

for NJE

 

 

 

 

10.4.1.3 Define BSC Remotes

This table shows the conversion of POWER PRMT parameters to JES2 RMT remotes.

Table 19

(Page 1 of 2). PRMT MACRO to JES2 Parameter Mapping

 

 

 

 

 

PRMT

 

Description

JES2 R M T

Comment

Parameter

 

 

Parameter

 

 

 

 

 

 

REMOTE

 

remote ID number

RMT(nnn)

¢nnn¢ is the remote ID

 

 

 

 

number

 

 

 

 

 

TYPE

 

2770, 2780, 3741, or 3780 for

TYPE

2770, 2780, or 3780/3781 for

 

 

BSC

 

BSC (3741 not supported)

 

 

 

 

 

ABE

 

Additional buffer expansion

B U F E X P A N = 2

(3741 not supported)

 

 

on 2770 and 3741

 

 

 

 

 

 

 

BE

 

Buffer expansion on 2770

B U F E X P A N = 1

 

 

 

 

 

 

CS

 

Component selection

TYPE=3781

 

 

 

 

or 2770

 

 

 

 

 

 

CSALST

 

Component select for LST

N/A

Not specified at this level -

 

 

output

 

based on device type (2770,

 

 

 

 

3781)

 

 

 

 

 

CSAMSG

 

Component selection for

N/A

Use MSGPRT=Y to route

 

 

messages sent to remote

 

messages to a printer

 

 

 

 

 

CSAPUN

 

Component select for punch

N/A

Not specified at this level -

 

 

output.

 

based on device type (2770,

 

 

 

 

3781)

 

 

 

 

 

HFC

 

Horizontal Tabs

HTABS

 

 

 

 

 

 

LIST

 

Number of characters in

N/A

(not nec.)

 

 

print line

 

 

 

 

 

 

 

LSTROUT

 

Default print routing

ROUTECDE

Same for LST and PUN

 

 

 

 

 

MRF

 

2780 multi-record feature

MRF2780

 

 

 

 

 

 

MSG

 

width of message lines

N/A

(not nec.)

 

 

 

 

 

MSEEJCT

 

Suppress skip-to-1 after

N/A

 

 

 

output before messages

 

 

 

 

 

 

 

228VSE to OS/390 Migration Workbook

Page 252
Image 252
IBM OS/390 manual Define BSC Remotes, Pline Macro to JES2 Parameter Mapping, 1 of 2. Prmt Macro to JES2 Parameter Mapping

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.