IBM OS/390 User Manual

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

Table 21. PNODE MACRO to JES2 Parameter Mapping

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

V T A M Appl-ID

APPL(name)

N O D E =

Defaults to node name. (Use
LOGONn for local node)

A U T H

Command authorization level

NODE

A U T H =

BUFSIZE

Transmission buffer size

TPDEF

x x x B U F =
( S I Z E =

BELOWBUF for BSC or CTC
EXTBUF for SNA

M A X B U F

Number of buffers for
transmitters & Receivers

TPDEF

x x x B U F =
( L I M I T =

(shared between RJE & NJE)

PWD

Send or Receive signon
p a s s w o r d

NODE

PASSWORD

S e n d = p w d   f o r   l o c a l   n o d e
V e r i f y = p w d   f o r   o t h e r   n o d e s

ROUTE1

Indirect link if using
store-and-forward (BSC, CTC
only)

NODE

S U B N E T =

-or-

CONNECT

(use dynamic path
management, or CONNECT
statements and operator
cmds)

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

n a m e

Name of the Compaction
Table

NAME

Compaction tables can be
referenced by name or
number.

MASTER

3 to 16 master characters

C H A R =

(nm,m1,m2,

...mn,

Number of master chars and
n master chars

N O M A S T n

Non-master characters

C H A R =

(...nm1,

...nmx)

Remainder are non-master
c h a r s

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.

VSE to OS/390 Migration Workbook