10.4.1.5 Define NJE Nodes

This table shows the conversion of POWER PNODE parameters to JES2 parameters.

Table 21.

PNODE MACRO to JES2 Parameter Mapping

 

 

 

 

 

 

PNODE

 

Description

JES2 Parm

Comment

Parm

 

 

 

 

 

 

 

 

 

N O D E =

 

Name of the NJE node

NODE

 

 

 

 

N A M E =

 

 

 

 

 

 

LOCAL

 

This is the local node.

NJEDEF

 

 

 

 

O W N N O D E =

 

 

 

 

 

 

APPLID

 

VTAM Appl-ID

APPL(name)

Defaults to node name. (Use

 

 

 

N O D E =

LOGONn for local node)

 

 

 

 

 

AUTH

 

Command authorization level

NODE

 

 

 

 

A U T H =

 

 

 

 

 

 

BUFSIZE

 

Transmission buffer size

TPDEF

BELOWBUF for BSC or CTC

 

 

 

x x x B U F =

EXTBUF for SNA

 

 

 

( S I Z E =

 

 

 

 

 

 

MAXBUF

 

Number of buffers for

TPDEF

(shared between RJE & NJE)

 

 

transmitters & Receivers

x x x B U F =

 

 

 

 

( L I M I T =

 

 

 

 

 

 

PWD

 

Send or Receive signon

NODE

Send=pwd for local node

 

 

password

PASSWORD

Verify=pwd for other nodes

 

 

 

 

 

ROUTE1

 

Indirect link if using

NODE

(use dynamic path

 

 

store-and-forward (BSC, CTC

S U B N E T =

management, or CONNECT

 

 

only)

-or-

statements and operator

 

 

 

CONNECT

cmds)

 

 

 

 

 

10.4.1.6 Define Compaction Tables

Up to 99 different compaction tables can be defined in JES2. They can be used by SNA RJE or NJE. For RJE, these can be referenced by individual OUTPUT JCL statement, specified on an individual Remote or Remote Printer or Punch statement. For NJE, they can only be specified on a NODE or APPL basis. (Use these with caution; they may take more cycles than they are worth.)

Table 22.

PCPTAB MACRO to JES2 Parameter Mapping

 

 

 

 

 

 

PCPTAB

 

Description

JES2

Comment

Parameter

 

 

COMPACT

 

 

 

 

Parameter

 

 

 

 

 

 

name

 

Name of the Compaction

NAME

Compaction tables can be

 

 

Table

 

referenced by name or

 

 

 

 

number.

 

 

 

 

 

MASTER

 

3 to 16 master characters

C H A R =

Number of master chars and

 

 

 

(nm,m1,m2,

n master chars

 

 

 

...mn,

 

 

 

 

 

 

NOMASTn

 

Non-master characters

C H A R =

Remainder are non-master

 

 

 

(...nm1,

chars

 

 

 

...nmx)

 

 

 

 

 

 

10.4.2 Exit Comparisons

Here are the VSE/POWER exits and their equivalent exits in JES2. The major difference between the two subsystems, is that POWER allows you to scan and alter the source data, whereas JES2 only gives you access to the header information.

230VSE to OS/390 Migration Workbook

Page 253 Page 255
Page 254
Image 254
IBM OS/390 manual Exit Comparisons, Define NJE Nodes, Define Compaction Tables, Pnode Macro to JES2 Parameter Mapping
Page 253 Page 255

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.
Top Page Image Contents