11.2.5 FSS Procedure and PRINTDEV Statements

Below is the sample FSS proc shown in the PSF/MVS Systems Programming

Guide.

//SAMPPROC PROC

 

 

 

 

 

//STEP01

EXEC PGM=APSPPIEP,REGION=4096K,TIME=1440

 

//STEPLIB DD DSN=PSF.LINKLIB,DISP=SHR

 

 

 

 

//JOBHDR

OUTPUT PAGEDEF=V06483,

 

/* JOB HEADER PAGE

*/

//

FORMDEF=A10120,CHARS=GT12

 

/*

FORMDEF: ALTERNATIVE BIN*/

//JOBTLR

OUTPUT PAGEDEF=V06483,

 

/* JOB TRAILER PAGE

*/

//

FORMDEF=A10110,CHARS=GT12

 

/*

FORMDEF: MAIN BIN

*/

//DSHDR

OUTPUT PAGEDEF=V06483,

 

/* DATA SET SEPARATOR

*/

//

FORMDEF=A10110,CHARS=GT12

 

/*

FORMDEF: MAIN BIN

*/

//MSGDS

OUTPUT PAGEDEF=A08682,

 

/* MESSAGE DATA SET

*/

//

FORMDEF=A10110,CHARS=GT15

 

/*

 

 

*/

//FONT01 DD DSN=SYS1.FONTLIB,DISP=SHR

/* SYSTEM FONTS

*/

//

DD DSN=INST.FONTLIB,DISP=SHR

/* INSTALLATION USER FONTS

*/

//PSEG01 DD DSN=INST.PSEGLIB,DISP=SHR

/* INSTALLATION PAGE SEGMENTS*/

//

DD DSN=SPEC.PSEGLIB,DISP=SHR

/* SPECIAL PAGE SEGMENTS

*/

//PSEG02 DD DSN=INST.PSEGLIB,DISP=SHR

/* INSTALLATION PAGE SEGMENTS*/

//OLAY01 DD DSN=INST.OVERLIB,DISP=SHR

/* INSTALLATION OVERLAYS

*/

//PDEF01 DD DSN=SYS1.PDEFLIB,DISP=SHR

/* SYSTEM PAGE DEFINITIONS

*/

//

DD DSN=INST.PDEFLIB,DISP=SHR

/* INSTALLATION PAGE DEFS

*/

//FDEF01 DD DSN=SYS1.FDEFLIB,DISP=SHR

/* SYSTEM FORM DEFINITIONS

*/

//

DD DSN=INST.FDEFLIB,DISP=SHR

/* INSTALLATION FORM DEFS

*/

//PRT1

CNTL

 

 

 

 

 

//PRT1

PRINTDEV FONTDD=*.FONT01, /* FONT

 

LIBRARY DD

*/

//

OVLYDD=*.OLAY01,

/* OVERLAY

LIBRARY DD

*/

//

PSEGDD=*.PSEG01,

/* SEGMENT

LIBRARY DD

*/

//

PDEFDD=*.PDEF01,

/* PAGEDEF

LIBRARY DD

*/

//

FDEFDD=*.FDEF01,

/* FORMDEF

LIBRARY DD

*/

//

JOBHDR=*.JOBHDR,

/* JOB HEADER SEPARATOR OUTPUT

*/

//

JOBTRLR=*.JOBTLR,

/* JOB TRAILER SEPARATOR OUTPUT */

//

DSHDR=*.DSHDR,

/* DATA SET HEADER SEPARATOR

*/

//

MESSAGE=*.MSGDS,

/* MESSAGE DATA SET OUTPUT

*/

//

BUFNO=5,

/* NUMBER OF WRITE DATA BUFFERS */

//

PAGEDEF=A08682,

/* DEVICE PAGEDEF DEFAULT

*/

//

FORMDEF=A10110,

/* DEVICE FORMDEF DEFAULT

*/

//

CHARS=GT12,

/* DEFAULT FONT

*/

//

PIMSG=(YES,16),

/* ACCUMULATE DATA SET MESSAGES */

//

DATACK=UNBLOCK,

/* UNBLOCK DATA CHECKS

*/

//

TRACE=NO,

/* BUILD INTERNAL TRACE

*/

//

SETUP=FORMS

/* SETUP MESSAGE

*/

//PRT1

ENDCNTL

 

 

 

 

 

 

 

 

 

 

 

 

11.2.5.1 Comparison of PRINTDEV Statement Parameters

In PSF/VSE and PSF/MVS, the PRINTDEV statement is part of the PSF startup job which defines the AFP printing environment and default print attributes. (In OS/390, the PRINTDEV statement is actually a JCL statement with ²//² in columns 1 and 2.) Many of these parameters can also be specified or overridden on the JES2 PRT(nnnnn) initialization statement or on the user¢s // OUTPUT statement.

Most PRINTDEV parameters are supported identically between PSF/VSE and

PSF/MVS. Exceptions are listed in the table below.

238VSE to OS/390 Migration Workbook

Page 262
Image 262
IBM OS/390 manual FSS Procedure and Printdev Statements, Comparison of Printdev Statement Parameters

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.