10.3.7.1 NJE Definitions

Use the following JES2 initialization statements to define your NJE network and networking options:

TPDEF BSC & SNA Buffer Sizes, and Number of SNA Sessions

NJEDEF Number of Nodes, Transmitters, Receivers, and other NJE options

NODE Individual NJE node definitions

APPLID VTAM Applid of NJE nodes (if not the same as Node Name)

LOGON VTAM Applids of this node

LINE BSC, CTC, and SNA communication lines. These are defined in the same way RJE lines are defined. Lines can be used interchangeably between RJE and NJE. See the comparison of PLINE macro parameters and JES2 parameters in Table 18 on page 228.

CONNECT Predefined NJE Node Connections

See Table 21 on page 230 for a comparison of PNODE macros to JES2 NODE parameters.

In addition to the JES2 Init & Tuning Guide (Chapter 5), also see NJE Installation, Operation and Use with JES2 and Other Systems, GG22-9339.

10.3.7.2 NJE Operations

See 28.6.2, ªNJE Operationsº on page453 and JES2 Commands for a description of NJE commands.

10.3.7.3 NJE Exits

JES2 exits 46 and 47 can be used to scan NJE headers when being sent or received, and the contents of the headers can be changed. JES2 does not have any exit to examine the spooled data records being sent with NJE. See Table 23 on page 231 for a comparison of POWER exits and JES2 exits.

10.3.7.4 NJE Management

See 10.3.7.1, ªNJE Definitionsº for detailed parameter comparisons.

10.3.8Application Interfaces

10.3.8.1Spool Space Allocation

POWER allocates spool space for jobs and spool files in units of DBLK groups which is usually about 4000 bytes. JES2 allocates space in units of track groups which are usually about three tracks each, as determined by the SPOOLDEF TGSIZE parameter.

10.3.8.2 Programmable Spool Interfaces

VSE/POWER supports macros to access spool data from user partitions:

CTLSPOOL, GETSPOOL, PUTSPOOL, PWRSPL, MAPXPCCB, and XPCC.

There is not a one-for-one mapping of these macros, but the following APIs are useful for accessing JES2 spooled jobs.

Chapter 10. POWER and JES2 221

Page 244 Page 246
Page 245
Image 245
IBM OS/390 manual Application Interfaces
Page 244 Page 246

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