PSF/MVS utility APSRMARK against these ported VSE resources in order for PSF/MVS to consider these resources ¢marked¢ for printer residency. (Printer resident fonts shipped with PSF/MVS are already ¢marked¢ with the APSRMARK program.)

11.3.3 Transferring Print Streams - VSE and OS/390 Coexistence

You can use NJE to transmit AFPDS (also known as LIST3820 or MO:DCA) files from VSE to OS/390 or vice versa. Print files created on VSE should print on PSF/MVS, and vice versa. See some of above for exchanging files between VSE and MVS.

Sequential print files can also be downloaded to a workstation from POWER using the IND$FILE protocol. MO:DCA (AFP) files should be transferred as binary files. Mixed-mode and line data should usually be transferred BINARY CRLF because record lengths are not appended. Note that POWER will change ANSI carriage control to machine.

PSF/VSE, PSF/MVS and PSF/VM include the AFP Toolkit, an API used to create AFP documents. A more advanced version is available for OS/2, AIX and MVS called ²AFP ToolBox.²

11.3.4 Migrating Print Applications

In general, the OS/390 Application Programmer has an easier job defining and using AFP resources than his VSE counterpart. See the PSF/MVS: Application Programming Guide, S544-3673 for details.

11.3.4.1 JCL and JECL Differences

All the AFP parameters on the VSE * $$ LST statement are fully supported on the OS/390 // DD or // OUTPUT statements.

11.3.4.2 Printing from TSO

The OUTDES (TSO/E) statement also has all the parameters available on the VSE APTZPARM macro.

11.3.4.3 Assembler Programming Interfaces

In OS/390, it is a lot easier to specify AFP attributes. Much of the VSE coding for print file attributes, while easily done in MVS, is also unnecessary. JCL SYSOUT and OUTPUT statements provide all the functions. Features such as FREE and SPIN may eliminate much of the need for special coding.

VSE Printer PARM Macro

In VSE, the APTZPARM macro is used to create library members for a specific set of attributes. These members¢ names are referenced in the $$ LST statement. All parameters on the APTZPARM macro are available on the OUTDES macro in OS/390:

CHARS CKPTPAG

DATACK FORMDEF

FORMS PAGEDEF

PIMSG PRMODE

TRC

In OS/390, you can use the PSF writer procedure to provide the defaults.

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

Page 265
Image 265
IBM manual Transferring Print Streams VSE and OS/390 Coexistence, Migrating Print Applications, JCL and Jecl Differences

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.