OS/390OS/390OS/390OS/390

An OverviewAn OverviewAn OverviewAn Overview

Data Processing IRANSystems Engineering Department

Contents

• OS/390 Evolution • OS/390 : S/390 Server Operating System• IT requirement and challenges• Major solutions of OS/390 OS/390

services and managements• webServer on S/390 platform

introduction to joining S/390 to web

•

Evolution of S/390A bit of history

• 1964 : System/360 family of computers uniprocessor,single-user,24 bit addressing real memory 128KB

• 1970 : S/370,interactive time sharing• 1971 : OS/VS1, Virtual storage, Transaction

management & database management• 1974 : MVS/370,focus on integrity

performance and functionality

Evolution of S/390(Continued)

• 1979 : Performance enhancements for larger storage,large disks,more channels

• 1981 : MVS/XA, 31-bit addressing(2GB),

• 1983 : First 4-way SMP, DB2

• 1988 : MVS/ESA

• 1990 : ESCON

• 1994 : 9672, Technology change to CMOS

• Transformation in Hardware : S/390 parallel Server

• Transformation in software for S/390

• OS/390 is the S/390 server operating system

• Enterprise wide Client/Server infrastructure

• Fast,flexible deployment of new applications

IT Requirement and Challenges

• Availability / Reliability

• Application Technology Choice

• Service to End Users

• Enterprise wide Systems Management

• Network and Security integration

• Productivity

OS/390 : An Integrated Solution

• OS/390 builds on the strengths of MVS/ESA

• A complete network ready server environment

• Base OS functions of key products are tested and then integrated into the Operating System, this ensures quality and reliability of OS/390

• SAP R/3 , Lotus Domino

• OS/390 with DB2 as a Database server

• Support for huge number of users

Solutions for the following major areas : •System Services •Systems Management •Communication server •LAN Services •Distributed Computing •Application Enablement •UNIX Services •Softcopy Services

OS/390 System Services

• Availability,Reliability,Serviceability

• Data integrity by system managed storage,automatic backup,recovery

• Flexibility:Tailored to the needs

• Storage management : Automated

• Parallel sysplex

• Workload management

OS/390 Systems Management

• One of the top IT concerns• Provide support in maintaining computer

and communication systems• OS/390 : A window to Enterprise wide

management• Configuration changes,security

access,analysing performance and tracing system modifications

OS/390 Systems Management

• Security is an integral part of the os390

• Four primary security management facility : RACF

DCE security serverFirewall technologies

LDAP

• Both local and distributed security

OS/390 Application Enablement

• Support for Object oriented technology

• Simplified code sharing and reuse, data sharing among heterogeneous systems, reduced application development cycle

• New user interfaces to traditional applics

• ISPF panels as GUI windows on WSs

• CORBA Standard

OS/390 UNIX Services

• X/Open XPG4.2 UNIX 95 branded• Include Unix applications which can use

strength,capacity and flexibility of OS/390 large and fast DASD,high speed printers, computing power,availability and security and system management tools.

• Permanent UNIX services• C/C++ API , Shell, UUCP,Socket interface

LAN Services

• OS/390 as LAN Data server and print server

• Central management

• High capacity

• High performance

• LANRES/MVS

• LAN Server

9672-RX4 9672-RX4

ESCON

Dir

11 x RAMAC II Subsystems

6 x 39990-6 + RAMAC II

2 x 3990 + RAMAC I

2 x RAMAC I Subsystem

Coupling facility

DB2 TeraByte System

Sysplex

Timer

ESCON

Dir

ESCON

DirESCON

OS/390 HTTP Server

• Fully functional web server

• Retrieve documents from OS/390 and return them to browsers

• Trrigers an OS/390 application upon client request which can be a UNIX application by CGI, Java servlet or CICS & IMS as well as DB2 stored procedures through connectors

OS/390 HTTP …Cont.

• HTTP server functionality includes : Secure sessions to access & programs

Exploit WorkLoad ManagerExploit scalability,large

storage Exploit availability of OS/390 & S/390

Why OS/390?

• S/390 is a very scalable hardware platform

• Security has always been a strength of S/390

• Over 70% of the world business data resides on 390 type systems,so by HTTP server direct access to CICS,IMS and DB2 from web is provided

Connectors to legacy applications

HTTP Server

webASBrowser

Oracle

MQM

VSAM

DB2

IMS

CICS

Direct access from web to CICS transactions

Secure access to Data and transactions from WWW

• S/390 with OS/390 can provide you with one of the most secure platforms in the IT industry to run mission critical business applications

• Secure data access

• Secure web transactions

Infoprint Server

IBM has printing solutions in z/OS and OS/390 to meet all of your enterprise printing needs:

•Print Services Facility (PSF) provides industrial strength support for production printing and mission critical distributed printing.

•Infoprint Server supports distributed enterprise printing over TCP/IP, including a single printer inventory for all printers managed by the solution, and ability to "capture" VTAM application output and place it on the spool for printing with PSF or Infoprint Server.

•Infoprint Server Transforms lets you print AFP application output on PCL or PostScript printers, or LAN-based print files in PCL, PostScript or PDF on shared, reliable AFP printers. It also transforms SAP output for AFP printing, and supports the attachment of VTAM-controlled coax printers.

Infoprint® Server is an optional feature of OS/390 V2R8-V2R10 and z/OS V1R1.

Infoprint Server delivers improved efficiency and lower overall printing cost with the flexibility for high-volume, high-speed printing from anywhere in the network. Infoprint Server lets you reduce the overall cost of printing while balancing your print workload across all available printers.

Infoprint Server lets you consolidate your print workload from many servers to a central OS/390 print server. Consolidating onto a central print server lets you use the right printer for specific print jobs and more easily manage the inventory of printers.

No matter what type of data you want to print (payroll, invoices, Web documents, sales reports), you can use OS/390 batch applications, VTAM applications, applications running on remote workstations, and OS/390 UNIX® System Services applications to send print requests to Infoprint Server. Infoprint Server then sends the print requests to OS/390 printers, including local printers and remote printers in a TCP/IP network.

Infoprint Server lets you:

Access all defined printers

Infoprint Server lets you define all of your printers in a centralized repository, called the Printer Inventory, so that any user in the network can send print jobs from OS/390 and LAN clients to any printer that is defined to Infoprint Server. Because all components of Infoprint Server share the printer definitions, you only have to configure each printer in one place.

Handle print jobs effectively

Because print jobs are managed by the OS/390 JES spool, they are secure, recoverable, and have OS/390 accounting information logged automatically.

What does Infoprint Server do for you?

Detect and transform data streams

Infoprint Server automatically detects the data stream for jobs that LAN and OS/390 UNIX System Services clients submit. It can then ensure that the selected printer can print the data stream, thus saving paper and time.

If the Infoprint Server Transforms are installed, and if the printer definition specifies transformation, Infoprint Server automatically invokes the appropriate transform command to convert any of these data streams to AFPTM format for printing: PCL, PostScript, PDF, SAP ABAP, and SAP OTF.

Support common printer languages

Infoprint Server lets you print to printers that provide support for the most commonly used printer languages in the industry, including Postscript, PCL, and AFP or Mixed Object Document Content Architecture-Presentation (MO:DCA-P). With the optional Infoprint Server Transforms, Infoprint Server also supports PDF, SAP OTF, and SAP ABAP. Infoprint Server protects your investment in printer hardware, while providing you with printing enhancements.

Monitor printer status

The SNMP subagent provided with Infoprint Server reports printer status to a printer management program, such as the IBM Network Printer Manager (NPM), whose graphical user interface (GUI) lets the operator monitor any IBM AFP printer managed by PSF for OS/390. When something goes wrong, the operator can check for more details without leaving the workstation.

Query job status

With Infoprint Server, users in the LAN and UNIX System Services environments can query the status of their print jobs to find out if a job is processing or is complete, or local system users can simply wait for the server to notify them that the job is complete.

Create AFP output from Windows applications

Infoprint Server provides an AFP Printer Driver for Windows® 95/98 and an AFP Printer Driver for Windows NT®; therefore, you can print output from any Windows application, such as Lotus WordPro or Freelance, on any of IBM's AFP printers.

Browse AFP documents on the Web

Infoprint Server includes an AFP Viewer plug-in for the Netscape Navigator and Microsoft® Internet Explorer Web browsers so you can view AFP documents from your Web browser. You can also use Infoprint Server to print documents that you are viewing from a Web browser to any defined printer.

Specify printer configuration information for PSF for OS/390

PSF for OS/390 provides support for the administrator to specify printer configuration information in Infoprint Server. This eliminates the need to write a PSF exit routine to specify customization information or to restart multiple printers when you change one printer.

The following diagram shows how the components of Infoprint Server fit into your system. The Infoprint Server components are shaded in yellow. Components of Infoprint Server Transforms are shaded in blue.

Graphic of Infoprint Server Components

Printing ScenariosPrinting Scenarios

1. A sheet of paper gets caught in a PSF printer. Because the printer is defined in the Printer Inventory, PSF for OS/390 is able to report the paper jam to the SNMP subagent immediately.2. The SNMP subagent reports the paper jam to NPM.3. In the NPM GUI running in a Web browser on the key operator's Windows workstation, the printer icon turns red to show that something is wrong with the printer.4. The key operator clicks on the printer icon to view details about the problem and then goes to the printer and clears the paper jam.5. PSF for OS/390 reports to the SNMP subagent that the problem has been corrected. The SNMP subagent transmits this information to NPM.6. Meanwhile, a researcher compiles a report at a UNIX workstation. The researcher then starts a Web browser and checks the NPM GUI to see if the PSF printer is available. The printer icon is now normal.7. Satisfied that the printer is running, the researcher submits the report to print.

A university engineering department maintains a network of many different computers and printers for a variety of projects. To prevent damage to the printers, they are locked. Only authorized key operators can add toner or clear a paper jam.

Here is how this department can use Infoprint Server components (in yellow) and IBM Network Printer Manager for the Web (NPM) to monitor printer status:

IBM Network Printer Manager

A bank creates its loan applications in AFP format for printing on high-speed IBM AFP printers. The company also wants to print these documents at their branch offices; however, the printers at their branch offices can print only PCL data. For example, the printers might be IBM Network Printer 24s without the optional IPDS cards that let them print AFP data.

Here is how this company can use Infoprint Server components and the AFP to PCL feature of Infoprint Server Transforms (in yellow) to meet its requirements:

Printing AFP Data from Batch Applications to Network PCL Printers

1. A batch application running on OS/390 or z/OS submits an AFP document to the JES spool for printing on a PCL printer in the branch office.

2. The IP PrintWay component automatically determines that the AFP document must be transformed into PCL format. IP PrintWay uses Print Interface to call Infoprint Server Transforms.

3. The AFP to PCL feature of Infoprint Server Transforms uses AFP resources, such as a form definition and fonts from the AFP resource libraries, to convert the AFP data to PCL format.

4. IP PrintWay transmits the document in PCL format from the JES spool to the PCL printer.

An international manufacturing company recently configured a LAN and has purchased network printers to replace its coaxially-attached SNA printers. This company wants to print inventory control reports from its CICS® and IMSTM applications to the network printers, instead of to its usual set of SNA printers. The company wants to route the reports to one or more remote locations, such as warehouses, docks, and the plant floor, while taking advantage of the security, accounting, and recovery capabilities of OS/390 or z/OS. Here is how this company can use Infoprint Server components (in yellow) to meet its requirements:

Printing CICS or IMS Output Data on Network Printers

2. The NetSpool component intercepts the print requests and creates output data sets on the JES spool, using JES output parameters defined by the administrator. The JES output parameters specify routing information that IP PrintWay uses to transmit the output to a particular network printer. 3. The IP PrintWay component transmits the output data sets from the JES spool to one or more network printers on the TCP/IP LAN.

1. The CICS or IMS applications submit print requests using VTAM in the same way they submit print requests to SNA printers. No changes to the CICS or IMS applications are required.

A market research firm wants to print Web documents on LAN-based PostScript printers and local high-speed AFP printers such as the Infoprint 60. In order to improve performance and specify Infoprint Server job attributes, some users install the Infoprint Port Monitor on their Windows systems.

Here is how this company can use Infoprint Server components (in yellow) to meet its requirements:

1. From a Windows workstation, a user views a document from the Web using a browser, such as Netscape Navigator. If the document is in AFP format, the AFP Viewer plug-in displays the document. 2. The user submits the document for printing using the standard print-submission method provided with the browser or viewer. The user selects a printer defined to Infoprint Server, which might be a PostScript printer or an AFP printer, and specifies job attributes in the Infoprint Port Monitor dialog. The printer driver associated with the printer creates an output file in the required format. For example, the AFP Printer Driver creates an output file in AFP format for printing on AFP printers. 3. The Infoprint Port Monitor automatically transmits the output file across the TCP/IP LAN to the Print Interface component. 4. The Print Interface component creates an output data set on the JES spool, using JES output parameters defined by the administrator and the JES output parameters that correspond to the job attributes specified by the user. The JES output parameters specify routing information that PSF for OS/390 and IP PrintWay can use to transmit the output to a printer. These parameters can also specify how the job is printed. 5. If the selected printer is a remote PostScript printer, the IP PrintWay component transmits the output data set to the PostScript printer on the TCP/IP LAN. If the selected printer is an AFP printer, PSF for OS/390 prints the data set on the AFP printer.

Printing Documents from the Web with the Infoprint Port Monitor

1. From a Windows workstation, a user views a document from the Web using a browser, such as Netscape Navigator. If the document is in AFP format, the AFP Viewer plug-in displays the document. 2. The user submits the document for printing using the standard print-submission method provided with the browser or viewer. The user selects a printer defined to Infoprint Server, for example a PostScript printer or an AFP printer. The printer driver associated with the printer creates an output file in the required format. For example, the AFP Printer Driver creates an output file in AFP format for printing on AFP printers. 3. The Server Message Block (SMB) protocol included in Windows automatically transmits the output file across the TCP/IP LAN to the OS/390 or z/OS SMB server, which is part of the Distributed File Service base element of OS/390 and z/OS.4. The OS/390 or z/OS SMB server calls the Print Interface component to create an output data set on the JES spool.5. The Print Interface component creates an output data set on the JES spool, using JES output parameters defined by the administrator. The JES output parameters specify routing information that PSF for OS/390 and IP PrintWay can use to transmit the output to a printer. These parameters can also specify how the job is printed. 6. If the selected printer is a remote PostScript printer, the IP PrintWay component transmits the output data set to the PostScript printer on the TCP/IP LAN. If the selected printer is an AFP printer, PSF for OS/390 prints the data set on the AFP printer.

A market research firm wants to print Web documents on LAN-based PostScript printers and high-speed AFP printers such as the Infoprint 60.

Here is how this company can use Infoprint Server components (in yellow) to meet its requirements:

Printing Documents from the Web with the Windows SMB Protocol

A market research firm wants to print documents created by Windows applications over the Internet on LAN-based PostScript printers and on high-speed AFP printers such as the Infoprint 60. The company upgrades to Windows 2000 because Windows 2000 contains a client that can print over the Internet using the Internet Printing Protocol (IPP). It also installs a printer that contains an IPP server, such as the Infoprint 21. Here is how this company can use Infoprint Server components (in yellow) to meet its requirements:

Printing Documents over the Internet Using the Internet Printing Protocol

1. From a Windows 2000 workstation, a user submits the document for printing using the standard print-submission method provided with Windows. The user selects any printer defined to Infoprint Server, for example a PostScript printer or an AFP printer. The printer driver associated with the printer creates an output file in the required format. For example, the AFP Printer Driver creates an output file in AFP format for printing on AFP printers. 2. The IPP printing protocol included in Windows 2000 automatically transmits the output file across the TCP/IP LAN to the Print Interface component. 3. The Print Interface component creates an output data set on the JES spool, using JES output parameters defined by the administrator. The JES output parameters specify routing information that PSF for OS/390 and IP PrintWay can use to transmit the output to a printer. These parameters can also specify how the job is printed. 4. If the selected printer is a remote PostScript printer, the IP PrintWay component transmits the output data set to the PostScript printer on the TCP/IP LAN. If the printer supports IPP, IP PrintWay communicates with the printer's IPP server.

If the selected printer is an AFP printer, PSF for OS/390 prints the data set on the AFP printer.

A financial institution wants to use OS/390 or z/OS to develop all of its statements at one central location. It then wants to print bank statements and reports at each of its branch offices throughout the mid-Atlantic region.

Here is how this financial institution can use Infoprint Server components (in yellow) to meet its

Printing from Batch Applications to Network Printers

1. The financial institution uses an OS/390 or z/OS batch application to generate statements, segment the statements by branch office, and store them in separate files for printing. 2. The application uses job control language (JCL) to submit the print files directly to the JES spool. 3. The IP PrintWay component transmits the print files from the JES spool to branch office printers in TCP/IP and SNA networks. If the printer is in an SNA network, IP PrintWay uses the Coax Printer Support feature of Infoprint Server Transforms to transform the line data to the SCS or DSC/DSE format supported by the printer.

A midsize retailer runs UNIX applications that have been ported to OS/390 or z/OS UNIX System Services. Until now, the applications have printed business statements to PostScript printers controlled by a print server running on a UNIX system. Now, the retailer wants to use a local higher-speed AFP printer, such as the IBM 3130 printer, for more efficient printing. Here is how this retailer can use Infoprint Server components and the Infoprint Server Transforms (in yellow) to meet its requirements:

Printing OS/390 or z/OS UNIX System Services Data on AFP Printers

1. The UNIX user logs onto OS/390 or z/OS UNIX System Services using the rlogin function. 2. Using the OS/390 or z/OS UNIX System Services printing commands provided with Infoprint Server, the UNIX applications print directly to the Print Interface component. 3. The Print Interface component automatically calls the Infoprint Server Transforms to convert PostScript or PDF documents to AFP format. 4. The Print Interface component creates output data sets on the JES spool. 5. PSF for OS/390 selects the output data sets from the JES spool and prints them on an AFP printer. If the retailer has more than one AFP printer, the first available printer can print the data sets.

A large production printing company uses a word processor running on Windows workstations to prepare its manuals. It then uses IBM AFP printers attached to the OS/390 or z/OS system, such as the IBM Infoprint 60 or the IBM Infoprint 4000 printer, to print the manuals.

Here is how this company can use Infoprint Server components (in yellow) to develop and print from a Windows environment:

Creating and Printing AFP Documents from Windows

1. From a Windows workstation, a writer prepares a manual using a word processor and then submits the manual for printing using the standard print-submission method provided with the word processor. The writer selects an IBM AFP printer attached to the z/OS system, and the AFP Printer Driver for Windows associated with the printer creates an output file in AFP format. 2. The Infoprint Port Monitor for Windows automatically transmits the output file across the TCP/IP LAN to the Print Interface component of Infoprint Server running on the OS/390 or z/OS system. 3. The Print Interface component creates an output data set on the JES spool.4. PSF for OS/390 selects the print job from the JES spool and directs it to the selected IBM AFP printer.

Introducing The OS/390 HTTP Server

•Read pages

•Execute Applications•Secure data and session•Multi-site support•Balance web workload•Exploit OS/390 scalability

WebsphereApplication

Server

Connectors

UNIX progs

Servlet

HTTP Server for OS/390

CICSIMS

DB2

Internet

IBM PS/2 Laptop

Client

IBM PS/2

TCP/IPFTP

TelnetHTTP

Firewall

Thinkpad

Servlets

html

CGIs

UNIX AS

OS/390HTTPServer

OS/390WASServerWorld-wide webWorld-wide web

OS/390 Web Server and TCP/IP Architecture

G/R

H H

G/R G/R

G/R

G/RG/R

G/R G/R G/R

The Internet Hardware Environment

Company ANetwork

Company BNetwork

ISP AndRegional Network

Backbone Network

H

G/R

H

G/R