11.3 Setting up AFP Resources

PSF/MVS supports resources in the system libraries defined in the PRINTDEV statement, and dynamically on a per-job basis via the USERLIB JCL statement.

11.3.1 Migrating Resources from VSE to OS/390

11.3.1.1 Defining Resources

If you have the source definition files for these resources, you can use the same process to define them on OS/390.

The same utilities are used on OS/390 as on VSE to define resources: PPFA for PAGEDEFs and FORMDEFs, and OGL for Overlays. Page Segments (PSEGs) can be created by GDDM or other licensed programs. See AFP Application Programming Interface: Programming Guide and Reference, S544-3872 for more information.

DCF (Script) is also supported in both environments.

11.3.1.2 Without the Source

If you don¢t have the source definition files (and can¢t recreate them) then you will have to use a tool to migrate them (²Mass Migration²).

There are some tools available from the IBM Printing Systems on their FTP site to help you convert VSE resources to MVS:

VSERES REXX exec to convert multiple VSE LIBR PUNCH phases to AFP resources

RESPUNCH Assembly program to extract an AFP resource from VSE and create an input file and JCL for RESMAKE

RESMAKE Assembly program to create an AFP resource in the MVS system from RESPUNCH

VSEREBLK PC and VSE tools for editing/creating resources on workstations and transferring them to VSE

APTRCONV Convert MVS resource back to VSE (shipped as part of PSF/MVS)

All of the resources for a specific print job can be extracted into a sequential (RECFM=VBM) Resource Object file using ACIF in VSE. ACIF will also create a printable MO:DCA (LIST3820) file from linedata using a PAGEDEF, exactly as PSF would do.

The Resource Object can also be concatenated to the front of a print job for any PSF or converted to a PDS (or sequential files in VM) using the FLAT2PDS exec. See 11.6.5, ªToolsº on page 244 for the Internet location.

11.3.2 Remote-Resident Resources

APTRMARK (VSE) and APSRMARK (MVS) differ in a subtle, but important way: Resources such as fonts that are shipped with PSF/VSE are ²marked² with an

²object origin identifier triplet² for VSE. Use the APSRMARK utility to mark resources that will be printer-resident.

If you move resources marked with the VSE program APTRMARK to an MVS system, PSF/MVS will not accept them for printer-residency. You must run the

240VSE to OS/390 Migration Workbook

Page 264
Image 264
IBM Setting up AFP Resources, Migrating Resources from VSE to OS/390, Remote-Resident Resources, Defining Resources

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.