Progress SHADOW Z User Manual

Z/ENTERPRISE WEB SERVER

Administration Guide

Version 5

manual is also copyrighted and all rights are reserved. This manual may not, in whole or in part, be copied, photocopied, translated, or reduced to any electronic medium or machine-readable form without prior consent, in writing, from Progress Software Corporation.

The information in this manual is subject to change without notice, and Progress Software Corporation assumes no responsibility for any errors that may appear in this document.

The references in this manual to specific platforms supported are subject to change. A (and design), Actional, Actional (and design), Affinities Server, Allegrix, Allegrix (and design), Apama, Business

Empowerment, ClientBuilder, ClientSoft, ClientSoft (and Design), Clientsoft.com, DataDirect (and design), DataDirect Connect, DataDirect Connect64, DataDirect Connect OLE DB, DataDirect Technologies, DataDirect XQuery, DataXtend, Dynamic Routing Architecture, EasyAsk, EdgeXtend, Empowerment Center, eXcelon, Fathom, IntelliStream, Neon, Neon New Era of Networks, O (and design), ObjectStore, OpenEdge, PDF, PeerDirect, Persistence, Persistence (and design), POSSENET, Powered by Progress, PowerTier, ProCare, Progress, Progress DataXtend, Progress Dynamics, Progress Business Empowerment, Progress Empowerment Center, Progress Empowerment Program, Progress Fast Track, Progress OpenEdge, Progress Profiles, Progress Results, Progress Software Developers Network, ProVision, PS Select, SequeLink, Shadow, ShadowDirect, Shadow Interface, Shadow Web Interface, ShadowWeb Server, Shadow TLS, SOAPStation, Sonic ESB, SonicMQ, Sonic Orchestration Server, Sonic Software (and design), SonicSynergy, SpeedScript, Stylus Studio, Technical Empowerment, Voice of Experience, WebSpeed, and Your Software, Our Technology-Experience the Connection are registered trademarks of Progress Software Corporation or one of its subsidiaries or affiliates in the U.S. and/or other countries. AccelEvent, Apama Dashboard Studio, Apama Event Manager, Apama Event Modeler, Apama Event Store, AppsAlive, AppServer, ASPen, ASP-in-a-Box, BusinessEdge, Cache-Forward, DataDirect Spy, DataDirect SupportLink, DataDirect XML Converters, Future Proof, Ghost Agents, GVAC, Looking Glass, ObjectCache, ObjectStore Inspector, ObjectStore Performance Expert, Pantero, POSSE, ProDataSet, Progress ESP Event Manager, Progress ESP Event Modeler, Progress Event Engine, Progress RFID, PSE Pro, SectorAlliance, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, Sonic, Sonic Business Integration Suite, Sonic Process Manager, Sonic Collaboration Server, Sonic Continuous Availability Architecture, Sonic Database Service, Sonic Workbench, Sonic XML Server, The Brains Behind BAM, WebClient, and Who Makes Progress are trademarks or service marks of Progress Software Corporation or one of its subsidiaries or affiliates in the U.S. and other countries.

IBM is a registered trademark of IBM Corporation. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Any other trademarks or service marks contained herein are the property of their respective owners.

DataDirect Shadow for ODBC includes: Software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http:/www.openssl.org/).

Software Foundation. All rights reserved. The names, "Ant", "Axis", "crossdb" "Xalan," "wsfx", "wsif" "poi," "Xalan", "Tomcat", "lucene", "Xerces" and/or "Apache Software Foundation" must not be used to endorse or promote products derived from the Product without prior written permission. Any product derived from the Product may not be called "Apache", nor may "Apache" appear in their name, without prior written permission. For written permission, please contact apache@apache.org.

Software developed by The Legion Of The Bouncy Castle (http://www.bouncycastle.org). Copyright © 2000 -2006. Software developed by The Cryptix Foundation Limited. Copyright © 1995-2005. All rights reserved. Software developed by The Hypersonic SQL Group. Copyright © 1995-2000. Software developed by Free Software Foundation, Inc. Copyright (C) 1991, 1999.

Chapter 1: Shadow z/Enterprise Web Server - An Overview . . . . . . . . . . . . . . . . . . 1-1

What is Shadow z/Enterprise Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Why Use It? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Shadow z/Enterprise Web Server Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Threading Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Product Capabilities and Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Fast, Simple Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Easily Understandable (Native MVS Web Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

High Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Comprehensive Management, Monitoring, and Control Capabilities . . . . . . . . . . . . . . . . . . 1-6

Extreme Scalability Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Top-Notch Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

How Shadow z/Enterprise Web Server Is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Optional Shadow Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Executing IMS Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Comparison Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Executing CICS Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Chapter 2: Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

An Overview of the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

How Shadow z/Enterprise Web Server Processes Transactions. . . . . . . . . . . . . . . . . . . . . . . . 2-1

When the URL Matches a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

When the URL Does Not Match a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Using Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Structure of a Rule (Event Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Creating, Enabling, and Accessing a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Creating the Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Enabling the Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Accessing the Rule Using a Web Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Deploying Shadow z/Enterprise Web Server at Your Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Setting Up the Mainframe Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Setting up the Client Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Chapter 3: The Shadow Event Facility (SEF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

What It Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Event Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Event Procedure Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Event Procedure Rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Shadow z/Enterprise Web Server Administration Guide iii

Start-up Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Event Procedure Data Set Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Enabling Event Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Enabling and Disabling Event Procedure Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Structure of an Event Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Event Procedure Header Statement (Required). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Process Section Header Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Header-Only Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

SEF Event Procedure Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

WWW Event Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

REXX Dynamic Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Global Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

GLVEVENT Temporary Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Event Related Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Event Procedure Return Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Accessing SEF Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Controlling SEF from a Batch Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Return Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Chapter 4: Defining Event Procedure Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Different Event Procedure Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Authorization (ATH) Event Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

How ATH Event Procedures Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

ATH Event Procedure Criterion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

ATH Event Procedure Header Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

ATH Event Procedure Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

ATH Event Procedure Return Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

ATH Event Procedure REXX Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

ATH Event Procedure Access Type Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Command (CMD) Rule Event Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

How CMD Rule Event Procedures Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

CMD Rule Event Procedure Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

CMD Rule Event Procedure Criterion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

CMD Rule Event Procedure Header Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

CMD Rule Event Procedure Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

CMD Rule Event Procedure Return Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Special Considerations for STOP Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

CMD Rule Event Procedure REXX Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Exception (EXC) Event Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

How EXC Event Procedures Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

EXC Event Procedure Criterion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

EXC Event Procedure Header Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

EXC Event Procedure Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

EXC Event Procedure Return Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

EXC Event Procedure REXX Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Global Variable (GLV) Event Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

How GLV Event Procedures Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

GLV Event Procedure Criterion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

GLV Event Procedure Header Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

GLV Event Procedure Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

iv Shadow z/Enterprise Web Server Administration Guide

GLV Event Procedure Return Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

GLV Event Procedure REXX Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Time-of-Day (TOD) Event Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

How TOD Event Procedures Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

TOD Event Procedure Criterion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

TOD Event Procedure Header Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

TOD Event Procedure Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

TOD Event Procedure Return Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

TOD Event Procedure REXX Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Type (TYP) Event Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

TYP Event Procedure Criterion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

TYP Event Procedure Header Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

TYP Event Procedure Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

TYP Event Procedure Return Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

TYP Event Procedure REXX Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

WWW Event Procedure Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

What Are WWW Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

How WWW Rules Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

WWW Rule Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

Syntax of WWW Rule Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

WWW URL-to-Rule Matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

WWW Rule Header Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

WWW Rule Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32

WWW Event-Related Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

Chapter 5: Web Transaction Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

About Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Userid Prompting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Controlled Transaction Paradigm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Levels of Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

MVS Security Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Client Authorization (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Effective Userid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Security Option Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Distributed Transaction Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

The Master Ruleset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Subordinate Rulesets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Security Attributes Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Security Processing Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Implementing Distributed Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Specifying Web Transaction Security Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

WWW Header Statement Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Configuring Secure Sockets Layer (SSL) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

WWW Header Security Parameters and Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

AUTHREQ ( YES | NO | LOCK ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

RUNAUTH( NONE | CLIENT | proxy-id ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

RESOURCE (string ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

SSL( NO | COND | YES | LOCK | LOCKCOND ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Shadow z/Enterprise Web Server Subsystem Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Setting Limits for the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

v Shadow z/Enterprise Web Server Administration Guide

Protecting Subsystem Command and Control Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Chapter 6: Writing Web Transactions in REXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Shadow/REXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

/*REXX Process Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

/*REXX Statement Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Coding the Process Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Shadow/REXX Built-in Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Chapter 7: File Serving Using the Shadow z/Enterprise Web Server . . . . . . . . . . . 7-1

UNIX File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

MVS File System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Files Supported Directly by Shadow z/Enterprise Web Server. . . . . . . . . . . . . . . . . . . . . . . . . 7-2

File Sharing and Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

How Shadow z/Enterprise Web Server Handles Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Building File Serving WWW Rules Using FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Coding a FILE Process Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

/*FILE Transaction Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

/*FILE Statement Keyword Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Parsing URLs to Supply Missing FILE Keyword Values. . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Inline File Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Examples of /*FILE Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Chapter 8: HTML Extension Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

HTML Extension Facility Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Insert Variable Text Into the Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

HTTP Response Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Conditional Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Iteration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Other Control Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Merging Data From Other Server Facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Scope of the HTML Extension Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Text Format Data Members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

MIME Content Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

HTML Extension Processing Enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Shadow z/Enterprise Web Server File Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Execution Time Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Limits on Various Syntactical Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Rules for Coding HTML Extension Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

HTML Extension Statement Escape Delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

No Continuation of Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Single Statement Per Source Record (Except Text Insertions) . . . . . . . . . . . . . . . . . . . . . 8-6

Mixed Case Coding Allowed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Reserved Words Not Valid as Variable Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Using Statement Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Run-time Operand Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

HTML Extension Text Insertion Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

HTML Extension Run-time Condition Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

IF Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

ELSE Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

vi Shadow z/Enterprise Web Server Administration Guide

ENDIF Statement Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

Condition Statement Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

HTML Extension Iteration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

Using Named Iteration Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

DO Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13

LEAVE Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

NEXT Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

ENDDO Statement Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

Operation of Iterative Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

Iterative Group Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Other HTML Extension Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

DATE Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

TIME Statement Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

EXIT Statement Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

DB2 Result Set Cursor Advance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

HTTP Response Control Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

HTML Extension Merge Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

Interface with /*EXECSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

Special /*EXECSQL Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

Chapter 9: Automated State Management Facility (ASMF) . . . . . . . . . . . . . . . . . . . 9-1

What is a Stateless Protocol?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Persistent Session Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

What is ASMF?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Why Use ASMF? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

What Constitutes State Information? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Transmitting State Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Server-Side State Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Using HTTP Cookies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Using HTML Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Using State Information Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

State Information Set Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

State Information Set Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

GLVSTATE Variable Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

Collection Control Variable Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10

Collection Status Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

Using COOKIE-Type Information Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13

How Cookies Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14

Creating a COOKIE-type Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

The “Official” HTTP Cookie Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Possible Anomalies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Making HTTP Cookies Work Reliably . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Some Suggestions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Chapter 10: Executing User Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

/*PROGRAM Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Executable Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Where is CGI? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Location of Program Load Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Coding /*PROGRAM Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Shadow z/Enterprise Web Server Administration Guide vii

Using Other REXX Interpreters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Executing a Non-Shadow/REXX Interpreter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

Run-Time Environments of Non-Shadow/REXX Interpreters. . . . . . . . . . . . . . . . . . . . . . 10-5

APIs for Non-Shadow/REXX Interpreters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Writing C/370 Web Transaction Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Writing COBOL Web Transaction Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Writing PL/I Web Transaction Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Chapter 11: Writing DB2-Based Web Applications . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Shadow/REXXTOOLs DB2/SQL Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

/*EXECSQL Process Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Operation of /*EXECSQL Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Coding /*EXECSQL Process Sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

SQL Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

/*EXECSQL Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Chapter 12: Shadow AutoHTML for IMS/TM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

AutoHTML Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Setting Up AutoHTML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Setting Up Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Generating the Default Format Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Generating the Default HTML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Making the Formats Available to Shadow z/Enterprise Web Server . . . . . . . . . . . . . . . . 12-6

Enabling the Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Testing the Shadow Supplied IMS Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Generating Maps/HTML from Custom Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Generating the HTML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10

Making the Formats Available to Shadow z/Enterprise Web Server . . . . . . . . . . . . . . . 12-12

(Optional) Customizing the Rule(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12

The /*EXECIMS Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13

(Optional) Customizing Your HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

Editing the HTML File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

Making the File Available to Shadow z/Enterprise Web Server . . . . . . . . . . . . . . . . . . . 12-18

Rule Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

The IMS Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18

The KEYBOARD Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-19

The IMSINIT Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21

The IMSENTRY Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-21

Chapter 13: Shadow AutoHTML for CICS/TS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

How it Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Installing the AutoHTML for CICS/TS Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Understanding the Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Getting Started Using BMS Source Members. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5

Step 1. Defining the Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5

Step 2. Creating the Customization Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10

viii Shadow z/Enterprise Web Server Administration Guide

Step 3. Connecting a BMS Mapset to Customization Orders. . . . . . . . . . . . . . . . . . . . . 13-20

Step 4. Generating HTML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28

Step 5. (Optional) Generating HTML Template Load Modules . . . . . . . . . . . . . . . . . . . 13-29

Step 6. Refreshing HTML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32

Getting Started Using Non-BMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33

Step 1. Defining the Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34

Step 2. Creating the Customization Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-37

Step 3. Connecting a Transaction ID to Customization Orders . . . . . . . . . . . . . . . . . . . 13-47

Step 4. Generating HTML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-55

Step 5. Refreshing HTML. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-58

Executing a CICS Transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-59

The Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-59

The URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-59

The Web Browser Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-59

Chapter 14: Shadow Data Mapping Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Data Mapping Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

The ISPF Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Map Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Map Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

Map Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7

Map Copy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10

Map Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11

Generate RPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11

Map Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15

HTML Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16

Using Data Maps in Client Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17

Chapter 15: Using Shadow Interface for ADABAS . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Obtaining Data from a Single ADABAS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Merging Output in the Data Mapping Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Making the SQL Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

Executing the Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

Using SDADEX and SDADDM to Obtain Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

Using SDADEX to Extract ADABAS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5

Using SDADDM to Import ADABAS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-16

Using Table Definitions for SDADEX Output and SDADDM Input . . . . . . . . . . . . . . . . . 15-17

Using Table Joins to Obtain Data from Multiple ADABAS Files . . . . . . . . . . . . . . . . . . . . . . 15-20

Dynamically Building an ADABAS Data Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-22

Using Cursor Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-22

Identifying and Authenticating ADABAS Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23

Losing Client Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23

Using Tracing to Identify Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23

Compatibility with Other Software AG Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-24

Shadow z/Enterprise Web Server Administration Guide ix

Chapter 16: Using the Shadow Interface for VSAM . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Obtaining Data from a VSAM File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Maintaining Output in the Shadow Data Mapping Facility . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Making the SQL Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Using the Shadow Data Mapping Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5

Defining VSAM Data Set Maps to the Shadow Data Mapping Facility. . . . . . . . . . . . . . . 16-5

Designating the Alternate Indexes for a VSAM Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7

Defining Multiple VSAM Logical Records Within the Same Physical File. . . . . . . . . . . . . . . . 16-8

Chapter 17: Using the OS/390 UNIX OpenEdition

Hierarchical File System (HFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Setting up HFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

OpenEdition and HFS Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

OpenEdition Security Subsystem (RACF) Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Started-task Userid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Default Runtime Userid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

Server Start-up Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

OEHFS Parameter (Required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

HFSAUTHMODE Parameter (Required) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4

DOCUMENTROOT Parameter (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4

SEFV31COMPATIBLE Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

Ruleset Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

HFSROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5

HFSROOT vs. DOCUMENTROOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

WWW Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6

URL Criterion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7

PATH Keyword Operand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7

WELCOMEPAGE Keyword Operand. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7

Displaying the Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7

Appendix A: Trace Browse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Trace Browse Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Order of Trace Browse Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

The Trace Browse Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Using the Specification Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Using the PROFILE Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Positioning Trace Browse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Changing Trace Browse Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Displaying Extra Columns of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Trace Browse Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Using Labels in the MSGNO Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

Locating Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Using the FIND Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Finding Character Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Finding With DISPLAY Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Row Information Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17

Printing Trace Browse Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17

x Shadow z/Enterprise Web Server Administration Guide

Appendix B: Trace Browse Archival Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

What It Is. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

How It Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

DIV Data Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Event Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Trace Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Archival Facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Message Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Configuring Automatic Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Using the Trace Browse Archival Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

Appendix C: Starting a Test Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Setting Up Shadow Server to Run under TSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Test Copies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Using the Debugging Control Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Using the Code/370 Debug Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Appendix D: Server Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Appendix E: Supported SMF Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Units of Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

SMF Type 05 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

SMF Type 06 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3

Appendix F: Language Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

Appendix G: Processing Web Transactions and URLs . . . . . . . . . . . . . . . . . . . . . . G-1

Uniform Resource Locators (URL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1

How the Web Server Handles URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2

Handling Inbound Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2

Supported URL Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2

Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3

Special Characters and URL Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3

Rescanning to a New URL Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4

Rescan Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4

Error Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4

FLUSH Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4

Shadow/REXX Return Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4

Other WWW Transaction Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5

Recovery From Server Detecte d Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5

Transaction Level Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-6

A Word About HyperText Transfer Protocol (HTTP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-7

TCP/IP Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-8

Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-8

Transport Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-8

Internet Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-10

Network Interface Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-10

Appendix H: Transaction Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . H-1

Shadow z/Enterprise Web Server Administration Guide xi

xii Shadow z/Enterprise Web Server Administration Guide

About this Publication

This book contains user information about the Shadow z/Enterprise Web Server™. This guide expands on the concepts and information presented in the Shadow z/Enterprise Web Server Getting Started Guide. If you do not find the information in this manual, refer to the Getting Star ted Guide or one of the publications in the related set of manuals.

How this Publication is Organized

This book contains the following chapters:

 Chapter 1, “Shadow z/Enterprise Web Server - An Overview,” provides an introduction

to Shadow z/Enterprise Web Server by reviewing information covered in the Shadow z/Enterprise Web Server Getting S tarted Guide and covering additional info rmation on

re-scanning to a new URL, error recovery, flush requests, and more in-depth information on HTTP and TCP/IP.

 Ch ap te r 2, “Qu ick Start,” provides a summary about Shadow z/Enterprise Web

Server’s event based architecture that matches incoming URLs to predefined event procedures or rules.

 Chapter 3, “The Shadow Event Facility (SEF),” covers the structure of an event

procedure (header statements an d process sections), the different types of variables, and how to control SEF from a batch environment.

 Chapter 4, “Defining Event Procedure Types,” covers the different event procedures

types, what they do, how they work, and the valid syntax for each.

 Chapter 5, “Web Transaction Security,” covers security parameters and subsyste m

security.

 Chapter 6, “Writing Web Transactions in REXX,” covers the syntax for coding /*REXX

process sections.

 Chapter 7, “File Serving Using the Shadow z/Enterprise Web Server,” discusses

supported files, how Shadow z/Enterprise Web Server han dles files, and how to build WWW rules using /*FILE.

 Chapter 8, “HTML Extension Facility,” covers the rules for coding HTML extension

statements, run-time condition checking, iteration statements, and merge processing.

 Chapter 9, “Automated State Management Facility (ASMF),” covers state information,

which provides the ability to “remember” information at the end of a client/server interaction if the information has some bearing on a future anticipated interaction.

 Chapter 10, “Executing User Programs,” describes the basics of the /*PROGRAM

process section, such as what programs can be executed, where they must reside, and how to code the process section; discusses the use of other REXX interpreters; and covers instructions related to writing transaction programs in C/370, COBOL, and PL/I.

 Chapter 11, “Writing DB2-Based Web Applications,” covers the operation and coding

of the /*EXECSQL process section. It also covers SQL statements for the /*EXECSQL

Shadow z/Enterprise Web Server Administration Guide xiii

section. The Shadow/REXXTOOLs DB2/SQL interface is discussed in the HTML online documentation and the Shadow z/Enterprise Web Server Programming Reference Guide.

 Chapter 12, “Shadow AutoHTML for IMS/TM,” discusses how to use the Shadow

AutoHTML™ for IMS/TM feature. This chapter includes a discussion of how to format the /*EXECIMS section. The Shadow z/Enterprise Web Server Installation Guide covers how to configure the system so you can use Shadow AutoHTML.

 Chapter 13, “Shadow AutoHTML for CICS/TS,” discusses how to use the Shadow

AutoHTML™ for CICS/TS feature. This chapter details the installation and configuration required, the administration of the Shadow AutoHTML for CICS/TS feature, and the steps required to execute a CICS transaction.

 Chapter 14, “Shadow Data Mapping Facility,” discusses the data mapping facility,

including how it works, what it does, and its various related ISPF pane ls.

 Chapter 15, “Using Shadow Interface for ADABAS,” covers the new add-on

component to Shadow z/Enterprise Web Server that provides reliable, high performance access to ADABAS data from the desktop.

 Ch ap te r 16 , “Us ing the Shadow Interface for VSAM,” covers the new add-on

component to Shadow z/Enterprise Web Server that provides reliable, high performance access to VSAM data.

 Chapter 17, “Using the OS/390 UNIX OpenEdition Hierarchical File System (HFS),”

covers support for the OS/390 UNIX System Services Hierarchical File System (HFS).

 Appendix A, “Trace Browse,” covers the different features of the Trace Browse

Facility, such as how it works, changing columns (or displaying extra columns), and locating messages.

 Appendix B, “Trace Browse Archival Facility,” discusses the basics of the Trace

Browse Archival Facility, how it works, handling backups and extracts, and configuring automatic backups.

 Appendix C, “Starting a Test Version,” covers using the debugging control screen,

setting up the server to run under TSO, and using the code/370 debug tool.

 Appendix D, “Server Error Codes,” lists the different server error codes and their

descriptions.

 Appendix E, “Supported SMF Fields,” explains the records that are written by Shadow

z/Enterprise Web Server whenever a URL is executed (Offset, Field Name, Field Type/Value, and Description ).

 Ap pe nd ix F, “Language Codes,” lists the country codes and the language.  Appendix G, “Processing Web Transactions and URLs,” includes information on

Internet protocols, application layer protocols, the client/server roles in HTTP, what is a URL, how the Web server handle URLs, what happens when a match is made to an inbound request, and when and why a rescans to a new URL occurs.

 Ap pe nd ix H, “Transaction Status Codes,” provides a list of internal Shadow

transaction status codes.

xiv Shadow z/Enterprise Web Server Administration Guide

Shadow Products and Publications

For a comprehensive list of the current Shadow product, visit the following website:

http://www.datadirect.com/solutions/mai nframes/index.ssp

You can access and download all of the current Shadow publications by navigating within this website to the following location:

http://www.datadirect.com/products/shad ow/documentation/ index.ssp

xv Shadow z/Enterprise Web Server Administration Guide

Working with Shadow Support

Shadow Support provides a number of ways for you to obtain assist ance fo r our product s. All product support inquiries are handled by the same support group, regardless if you are a trial or a licensed customer. The following are available support options:

Support Option

E-mail To contact Shadow Support via

How to Access How it Works This Option is Best for:

e-mail, please use the following link:

shadowsupport@datadirect. com

E-mail is available for receipt 24 hours a day, 7 days a week and is answered between 9AM-7PM CST Monday through Friday.

Phone To contact Shadow Support,

please visit the following Web site and select the “Phone” link:

http:// www.datadirect.com/ support/contactus/phone/ index.ssp

Internet To access Internet Shadow

Support, please visit the following Web site:

http:// www.datadirect.com/ support/index.ssp

E-mail goes to the support queue, which is continuously monitored by a staff of crossfunctional technical experts. It is answered in the order it is received. It is logged in the support database and assigned a trouble ticket number for tracking purposes.

During normal working hours you will be transferred to a technical expert within the Customer Support group. Y ou may be required to page a support person via our phone mail system after hours.

The DataDirect Technologies Website is maintained to provide current, relevant materials to support our customers. Links to a searchable Knowledge Base and various technical tips are available from the DataDirect Technologies Website. In addition, software updates and product documentation can be downloaded from the Web site. The DataDirect Technologies Website also allows you to track open support incidents.

This type of support is excellent for low to medium priority requests. It is a proven method for providing further information on critical problems that may have been phoned in. E-mail is a convenient way of sending us a list of lower priority items you have collected at a time that is convenient for you.

This type of support is best for high priority requests and initial installation questions. Use this option for any obvious system errors or anytime you need the most rapid reply to your question.

This option provides immediate access to documentation, updated client-side Drivers, and our product Knowledge Base. The Knowledge Base is a collection of questions answered by Customer Support. Use this option to answer your own questions or to get a better understanding of what customers ask on an ongoing basis.

Account Manager

To contact your Sales Representative (U.S.),please visit the following Web site and select the “Phone” link:

http:// www.datadirect.com/

Your Sales Representative is your account manager. This person is ultimately responsible for your complete satisfaction with the Shadow product.

support/contactus/phone/ index.ssp

xvi Shadow z/Enterprise Web Server Administration Guide

Contact your Sales Representative for pricing information, contract details, password renewal, or if you feel your needs are not being met.

CHAPTER 1:

Shadow z/Enterprise Web Server - An Overview

The Shadow z/Enterprise Web Server allows you to unite the power of the Internet with the rich resources of legacy System 390/MVS applications and data to fully exploit the growing revolution in eBusiness. Topics include:

What is Shadow z/Enterprise Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Why Use It? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Shadow z/Enterprise Web Server Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

How It Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Threading Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Product Capabilities and Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Fast, Simple Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Easily Understandable (Native MVS Web Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

High Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Comprehensive Management, Monitoring, and Control Capabilities . . . . . . . . . . . . . 1-6

Extreme Scalability Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Top-Notch Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

How Shadow z/Enterprise Web Server Is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Optional Shadow Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Executing IMS Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Comparison Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Executing CICS Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

What is Shadow z/Enterprise Web Server

Shadow z/Enterprise Web Server is a native MVS Web server that provides controlled access to MVS data and applications using a Web browser, such as Netscape Navigator™ or Internet Explorer™. It does not require an intermediate server, nor is it limited to simple file transfers or screen scraping. Shadow z/Enterprise Web Server is an MVS transaction processor product designed specifically to connect MVS resident resources to the World Wide Web (WWW).

How It Works

Shadow z/Enterprise Web Server is an OS/390-based product that is installed and initiated as a started task within OS/390. Once installed, Shadow z/Enterprise Web Server “listens” for Web client sessions (URLs), inbound from the Internet or an intranet. Each inbound session is assigned to a thread, an individu al un it of work in OS/ 39 0 that is used for authorization, data access, transaction access, monitoring, and control.

The URLs from the client are matched against pre-defined rules, or event procedures, established within Shadow z/Enterprise Web Server to enforce a controlled-transaction paradigm. Because Shadow z/Enterprise Web Server can access all standard

Shadow z/Enterprise Web Server Administration Guide 1-1

Shadow z/Enterprise Web Server - An Overview

OS/390 functions, rules ensure that only pre-approved actions can be taken by users. Rules process the URLs and return HTML or binary data via HTTP to the client.

Why Use It?

eCommerce began with a scattering of consumer-oriented Web-based retail sites. But innovation and the redesign of business models has take n e Comme rce beyon d its simple beginnings to create a new definition of what it means to exploit the powers of the Internet or intranet. The Web is changing the way the world does business. For those who can exploit it creatively, the rewards can be enormous:

 In cr ea se d pr odu c tivit y  Reduced expenses  Increased efficiency of business processes  Strategic advantage over competitors

Shadow z/Enterprise Web Server Architecture

Shadow z/Enterprise Web Server uses a simple two-tier architecture that provides direct Web-to-mainframe access, thus eliminating the need for mid-tier Web servers. The result is a comprehensive access environment for integrating System/390 and the Internet. By eliminating the need for gateways:

 Production is enhanced.  Learning curves are lowered.  There are no performance bottlenecks.  It uses maximum throughput and fast response time, regardle ss of th e nu m be r of

users.

 There is higher availability of data.  There is no gateway to purchase, install, or maintain.  There are no additional components to fail.  The IT investment in legacy systems is preserved.

How It Works

A key component of the Shadow event-based architecture is the concept of an event procedure, or rule. Rules are site-defined actions to be taken by Shadow z/Enterprise Web Server in response to inbound URLs. Once a rule is defined using the Shadow Event Facility™ (SEF) component, it may be made immediately available for execution.

Rules, typically defined by a designated Webmaster, can perform a variety of processing roles, such as:

 Ru n a SQL statemen t.  Execute CICS programs, IMS transactions, or TSO/E command procedures.  Transmit authorized OS/390 files to the client.  Execute customized REXX-language scripting procedures.  Execute customer-written programs in COBOL, PL/I, or C.  Execute powerful built-in facilities that provide turnkey access to data files or existing

OS/390 applications.

Figure 1–1 illustrates the basic architecture of Shadow z/Enterprise Web Server.

1-2 Shadow z/Enterprise Web Server Administration Guide

Shadow z/Enterprise Web Server Architecture

Figure 1–1. The Basic Architecture for Shadow z/Enterprise Web Server

Accessing Rules Using URLs

Web browsers use URLs (Uniform Request Locators) to access Web resources. The following is a URL:

http://www.neonsys.com:80/NEON /SAMPDATA/htxother .htm

The first portion of the URL identifies the TCP/IP address of the OS/390 system and the port assigned to Shadow z/Enterprise Web Server. When an HTTP (Hypertext Transfer Protocol) request arrives, the second part of the URL is passed to Shadow z/Enterprise Web Server, which compares the URL to a list of pre-defined rules, or event procedures, created in the Shadow Event Facility (SEF). Table 1–1 shows how Shadow z/Enterprise Web Server handles URLs.

Table 1–1. How Shadow z/Enterprise Web Server (SWS) Handles URLs

Discarded once it arrives at the port SWS matches this to a rule (event procedure)

http://www.neonsys.com:80 /NEON/SAMPDATA/htxother.htm

When a match is found, Shadow z/Enterprise Web Server executes the associated event and the results are returned from the OS/390 system to Shadow z/Ente rprise Web Server, which converts the information into an HTML data stream before sending the results back to the client. Relational tables may be formatted as HTML tables. Additionally, Shadow z/ Enterprise Web Server supports all standard MIME (Multimedia Internet Mail Extension) file types for transfer to the client.

Shadow z/Enterprise Web Server Administration Guide 1-3

Shadow z/Enterprise Web Server - An Overview

Distributed Transaction Administration

To facilitate administration and to prevent accidental or malicious misuse of security related parameters, Shadow z/Enterprise Web Server provides both a master list of event procedures and the ability to create subordinate lists. This allows diverse groups to still have responsibility for writing and maintaining Web transactions definitions, which can be grouped by application, user community, resou rce requirements, or by any breakdown that offers administrative convenience.

Controlled Transaction Paradigm

Shadow z/Enterprise Web Server provides another point of control. This is known as the controlled transaction paradigm and ensures that only desired access is provided to users. Execution privileges may be granted at the event level, DBMS level, OS/390 level, or transaction level.

Threading Architecture

Inside the Shadow z/Enterprise Web Server address space, there are two dedicated listener threads (TCBs) for communication processing. One thread handles IBM TCP/IP; the other handles Interlink TCP/IP. These threads are responsible for all inbound session requests.

Inbound session requests are handled by binding a socket to a well-known port number and then establishing a listen queue. The TCP/IP communication thread then issues an accept for each inbound session request. A unique child thread (attachment TCB) is created for every inbound session request and is dedicated to the sessio n an d kept for as long as the session is active.

There are several reasons for this architectural decision:

 Minimize CPU overhead  Offer parallel processing  Maximize scalability  Use existing security  Offer isolation  Simplify accounting  Improve manageability

CPU overhead

The overhead of thread creation, user authentication, transaction program initiation, and database thread allocation is incurred only once . After all the initialization steps have been completed, a direct path is available for passing database requests from the client application directly to the host database. This approach is now recommended by IBM as the most efficient way of communicating with DB2, enhancing both capacity an d response time.

Parallel processing

The creation of a dedicated thread for each client application allows Shadow z/Enterprise Web Server to exploit the multiprocessing and multiprogramming capabilities of IBM mainframes and OS/390. Over a period of many years, IBM has steadily expanded the

1-4 Shadow z/Enterprise Web Server Administration Guide

Product Capabilities and Benefits

multiprocessing capabilities of its hardware and the multiprogramming facilities of its software. These capabilities can be exploited only by products that create multiple units of dispatchability (TCBs or SRBs).

Scalability

The dedicated thread approach provides the highest degree of scalability for the client/ server computing environment. Because Shadow z/Enterprise Web Server creates threads for all client sessions, rather than using the services of CICS or IMS, it avoids scalability issues inherent in those subsystems. The only limits are those physical constraints imposed by OS/390 or the subsystem itself (i.e., DB2 thread limits).

Security

Shadow z/Enterprise Web Server creates an ACEE control block for each client support thread. This ACEE is initialized with the current userid provided by Shadow z/Enterprise Web Server on behalf of the client. This approach ensures that all client actions ha ve been authenticated by the existing security system.

Isolation

Multiple threads may be active concurrently without affecting each other. In addition, both OS/390 and DB2 provide task-level resource cleanup. This mean s that if a thre ad fails, a ll related OS/390 and DB2 resources are released automatically and any da tabase changes are rolled back automatically without affecting other threads.

Accounting

OS/390 tracks resource utilization by threads. Because one and only one thread is responsible for all work done on behalf of the client, the dedicated server thread is charged for all of the resources used by the client. Shadow z/Enterprise Web Server creates standard SMF records that detail usage by subsystem and user connection.

Manageability

Threads are the smallest unit of dispatchability and control in the OS/390 environment. Threads are also the fundamental unit of DB2 connectivity. Shadow z/Enterprise Web Server exploits its dedicated threads to implement several automated and manual controls. These controls include a CPU throttling facility and a thread cancellation mechanism.

Product Capabilities and Benefits

Shadow z/Enterprise Web Server provides direct Web access to MVS with several capabilities and benefits.

Fast, Simple Implementation

Implementation of Shadow z/Enterprise Web Server is quick and easy. No intermediate server is required, and programming requirements on the host are kept to a minimum through the use of supplied functions and capabilities. Existing programs and transactions

Shadow z/Enterprise Web Server Administration Guide 1-5

Shadow z/Enterprise Web Server - An Overview

can be executed, often with no changes to the transaction code. IT departments can take advantage of browser or “thin client” application development and leverage the lower cost of application development and maintenance with high quality OS/390 data and business access logic.

Easily Understandable (Native MVS Web Server)

Shadow z/Enterprise Web Server is a native MVS Web server. It is not UNIX-based, nor is it derived from early UNIX Web server source code implementations. Sh adow z/Enterprise Web Server was designed on MVS for MVS. This means your systems programmers do not need to spend hours researching unfamiliar system configuration options or adding new and unfamiliar security control paradigms to your configuration. Users, developers, and security administrators already know which security limits are imposed and how they are configured and administered.

High Performance

Shadow z/Enterprise Web Server was built with high performance as a key consideration in all aspects of product development. The performance characteristics of Shadow z/ Enterprise Web Server are maintained whether a few or tens-of-thousands of users are using the software. This is possible because there are no built-in bottlenecks, such as mid-tier Web servers, or other architectural limitations.

Comprehensive Management, Monitoring, and Control Capabilities

To ensure speedy development, you need rapid access to detailed diagnostics. Shadow z/Enterprise Web Server provides a detailed monitoring and trace facility for end-to-end diagnostics and rapid resolution of development problems and a diagnostic facility. Together, the Shadow z/Enterprise Web Server product’s trace and the Shadow Diagnostic Facility provide the most complete, powerful, and flexible set of administration tools available in the OS/390 middleware arena.

The Trace Facility

Shadow z/Enterprise Web Server incorporates an extensive trace facility that is implemented by adding trace records to a trace buffer maintaine d in virtual storage . Trace operations are performed entirely with memory-to-memory instructions, and nothing is written to disk until the session is complete, at which point the trace information is automatically saved on disk. This approach combines the performance advantages of memory-to-memory tracing with the non-volatility of standard disk storage.

Trace records are created for a wide variety of events in the Shadow z/Enterprise Web Server address space. Specifically, trace records are written for SQL operations, IMS calls, CICS calls, communication events (LU 6.2, TCP/IP, and messages), thread attach and detach events, RPC events, message events, and errors (abends). It is even possible for an RPC to add its own trace messages to trace records for diagnostic purposes.

The Shadow Diagnostic Facility

The Shadow Diagnostic Facility (SDF), an ISPF application shipped with Shadow z/ Enterprise Web Server, provides an interface to the controls and diagnostics. Using this facility, administrators can reset controls, view, filter, and search the trace data, and

1-6 Shadow z/Enterprise Web Server Administration Guide

display all currently active users. This display can also be used to reconstruct the session of any currently active user or, with authorization, to terminate any active session.

The Shadow Diagnostic Facility includes a security mechanism that allows you to restrict what each user can do with SDF.

Extreme Scalability Capabilities

Shadow z/Enterprise Web Server offers extreme scalability, whether users number in the hundreds or hundreds-of-thousands by providing unparalleled ability to maintain response times within pre-established services levels as numbers of users grow. End-to-end multithreaded capabilities exploit all available hardware and operating system facilities for processing on the client and server components.

Extreme scalability ensures that applications will perform as designed both today and in the future, adapting easily to volume increases and new technologies that accompany internal and external corporate change. Multiple address space load balancing, workload management, and dynamic thread pooling enable high volume user access. The result is that you can leverage single-platform applications, participate in e-business opportunities, engage in personalized marketing, and provide a global workgroup environment quickly and easily.

How Shadow z/Enterprise Web Server Is Used

Top-Notch Security

Shadow z/Enterprise Web Server supports a full range of System/390 security systems, such as RACF, ACF2, and Top Secret, to validate userids and passwords p rovided e ither directly by the user or via LAN authentication mechanisms. The ability to use existing security is of paramount importance in protecting OS/390-MVS assets and ensuring rapid application development. Shadow z/Enterprise Web Server supports the highest client/ server security standard in practical use today: Secure Socket Layer (SSL). The support of SSL and GSK SSL meets the most demanding security needs in the industry.

How Shadow z/Enterprise Web Server Is Used

Shadow z/Enterprise Web Server is being used in a growing number of enterprises around the globe to bring the resources and power o f the main fram e to Web applications.

 A worldwide shipping firm uses Shadow z/Enterprise Web Server to allow employees

to access its OS/390 applications and data from any port that has a telephone line.

 A major university allows students to retrieve curriculum and grade infor mation and to

 One of Europe’s largest insurance companies uses Shadow z/Enterprise Web Server

for intranet applications and external investment management programs.

 One of the world’s largest aircraft manufacturers uses Shadow z/Enterprise Web

Server to browser-enable its employee time-keeping system.

Whenever production Web applications for OS/390 are required with a need for minimal development time and maximum security, companies are finding the most efficient and cost-effective solution to be Shadow z/Enterprise Web Server.

Shadow z/Enterprise Web Server Administration Guide 1-7

Shadow z/Enterprise Web Server - An Overview

Connection

3270 Terminal

VTAM

IMS MPP

Optional Shadow Interfaces

The optional Shadow Interface™ components for DB2, IMS/DB, IMS/TM, CICS/TS, VSAM, ADABAS, and Natural simplify, speed, and streamline your access to OS/390 resources. In most cases, the Shadow Interfaces provide a method to execute legacy programs from Web browsers without any modification to the host code. Existing OS/390based applications can be executed, returning data in HTML format. This functionality allows you to reuse existing business and access logic that is at the heart of many production applications today.

Shadow Interfaces eliminate the need for coding remote procedure calls (RPCs) on the host and, when used with the Data Mapping Facility (DMF), display the results in the format you designate, without the need to sort or parse returned data. With Shadow Interfaces, you gain the speed and simplicity of a desktop tool, cut development time significantly, increase productivity, and reduce time to market for applications.

Shadow z/Enterprise Web Server can be used with interfaces for:

 DB2, IMS/DB, and ADABAS databases  IMS and CICS transactions  VSAM data  Natural programs  Sequential files and PDSs  RPC stored procedures for data sources such as:

− IDMS

− Oracle for the System/390

− CA Datacom

− CA Sapphire

− Total

− M204

Executing IMS Transactions

Shadow z/Enterprise Web Server provides access to IMS transactions across the Internet using Web browsers.

Figure 1–2. Executing an IMS Transaction on a 3270 Terminal

The Figure 1–2 shows IMS on a 3270 Terminal while Figure 1–3 shows the same transaction using a Web browser and Shadow z/Enterprise Web Server.

1-8 Shadow z/Enterprise Web Server Administration Guide

Executing IMS Transactions

TCP/IP

Web Browser

SWS

IMS

Figure 1–3. Executing an IMS Transaction Using the Shadow z/Enterprise Web Server

You can use an (optional) interface, such as a program (Shadow/REXX, COBOL, PL/1, C, C++ or Assembler) or a non-program interface (Data Mapping or RPC) to retrieve the information.

Comparison Table

Table 1.

3270 Terminal Web browser

1. The form is filled-in on screen. Press the appropriate key to transmit.

2. 3270 screen loads data into the buffer and passes it to the connection using LU2 protocol. The information is then passed onto VTAM.

3. VTAM passes data to IMS. 3. TCP/IP passes messages to SWS.

4. IMS identifies the transaction code from the message and schedules the appropriate message processing program (MPP).

5. MPP receives the message from IMS and processes the transaction.

6. MPP passes the results back to IMS. 6. SWS passes the results to TCP/IP.

7. IMS passes the message to VTAM , which passes it back to terminal via connection using LU2 protocol.

8. Results are displayed on the screen. 8. Results are displayed on the screen.

1. The form is filled-in on screen. Press Enter to transmit.

2. Web browser puts data into a string (URL) and passes it to TCP/IP using HTTP.

4. SWS strips the destination information and matches the remaining value against a sitedefined WWW rule (event procedure). The transaction is scheduled for processing.

5. The event procedure is processed.

7. TCP/IP passes the information back to the PC using HTTP protocol.

Once Shadow z/Enterprise Web Server is installed, the only setup task is to define an event procedure for each IMS transaction invoked through the Shadow z/Enterprise Web Server.

Shadow z/Enterprise Web Server Administration Guide 1-9

Shadow z/Enterprise Web Server - An Overview

EXCI

Web Browser

SWS

CICS

Pro-

gram

TCP/IP

AutoHTML

Shadow z/Enterprise Web Server provides a feature known as Shadow AutoHTML™, which generates a base level of HTML for rapid deployment of a first generation Web application. The base HTML can be modified to further enhance the application by using standard point and click Web development tools.

Executing CICS Transactions

Shadow z/Enterprise Web Server provides access to CICS transactions across the Internet using Web browsers. without involving any modifications to the CICS code. This means existing CICS programs can be executed and data returned in easily form atted HTML.

From one URL, many existing physical CICS programs can be accessed to create one new “logical” view of the data.

For CICS access, Shadow z/Enterprise Web Server uses technology known as the Transaction Server for CICS, which connects to CICS via an EXCI (External CICS Interface).

Summary

Shadow z/Enterprise Web Server is the product of choice for uniting the power of the Internet with the rich resources of legacy System 390/MVS applications and data to fully support IT initiatives in e-commerce and e-engineering. With Shadow z/Enterprise Web Server, you’re assured of the scalability, security, performance, reliability, and control to confidently combine the Internet and OS/390 data and applications.

Many enterprises use Shadow z/Enterprise Web Server to:

 Web-enable mainframe applications without custom coding  Support e-initiatives by enabling global information-sharing without a gateway  Leverage existing production infrastructures and in-house System/390 expertise  Speed time to market by installing in less than one day, without on-site assistance or

interruption of operations

Figure 1–4. Executing a CICS Transaction

1-10 Shadow z/Enterprise Web Server Administration Guide

Summary

 Combine mainframe performance, reliability, security, and control while exploiting the

cost-effectiveness and eBusiness opportunities of the Internet

 Provide automatic generation of HTML for CICS and IMS transactions  Accommodate up to hundreds of thousands of users with no performance degradation

or downtime

 Eliminate the need for gateway hardware, software or application coding  Keep data on System/390 with no migration or loss of data integrity  In co rp or at e ce nt ra lize d, fully inte ra ctiv e on lin e mo nit or ing , co nt ro l, and dia gnos tics

capabilities

 Speed and simplify development of new and composite applications

Shadow z/Enterprise Web Server Administration Guide 1-1 1

Shadow z/Enterprise Web Server - An Overview

1-12 Shadow z/Enterprise Web Server Administration Guide

CHAPTER 2:

Quick Start

A key component of the Shadow z/Enterprise Web Server is its even t based architecture that matches incoming URLs to predefined event procedures or rules. These rules are site -defined actions that allow you to perform a variety of processing roles. Topics include:

An Overview of the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

How Shadow z/Enterprise Web Server Processes Transactions. . . . . . . . . . . . . . . . . . . 2-1

When the URL Matches a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

When the URL Does Not Match a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Using Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Structure of a Rule (Event Procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Creating, Enabling, and Accessing a Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Creating the Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Enabling the Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Accessing the Rule Using a Web Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Deploying Shadow z/Enterprise Web Server at Your Site . . . . . . . . . . . . . . . . . . . . . . . 2-14

Setting Up the Mainframe Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Setting up the Client Side. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

An Overview of the Process

Before the information/procedure can be accessed on the mainframe, a “rule” must be created and enabled on the mainframe. To access the rule from the PC, use your Web browser and send the appropriate URL.

Rule

(Event Procedure) A rule is a member within an MVS PDS data set that contains executable procedures.

URL

This is the acronym for Uniform Resource Locator. URLs:

 Identify the Internet service protocol, such as HTTP or FTP  Specify the location of a file on the World Wide Web, network, or hard drive

Shadow z/Enterprise Web Server uses URLs to access rules. The following is a URL:

http://www.neonsys.com/NEON/SAM PDATA/htxother.htm

How Shadow z/Enterprise Web Server Processes Transactions

Unlike other Web servers, Shadow z/Enterprise Web Server does not attempt to match the URL to an MVS file system entity. Instead, it looks up the URL value in a list of WWW rule event procedure definitions.

Shadow z/Enterprise Web Server Administration Guide 2-1

Quick Start

Executes

WWW Rule

Event

Matches

SWS

Client (Web Browser)

1,2

6,7

Tip: Naming Data Sets

Name the members in the data sets to correspond to the URL. That way, you can easily find the rule to edit.

For example, “/NEON/SAMPDATA/htxother.htm” would be stored in the SAMPDATA file with HTXOTHER as one of the members.

Shadow z/Enterprise Web Server processes the URL

http://www.neonsys.com/NEON/SA MPDATA/htxother.ht m

as shown in Table 2–1.

Table 2–1. How Shadow z/Enterprise Web Server (SWS) Handles URLs

Discarded once it arrives at the port SWS matches this to a rule (event procedure)

http://www.neonsys.com / NEON/SAMPDATA/htxot her.htm

When the URL Matches a Rule

Figure 2–1 shows what happens when the URL finds a matching rule.

Figure 2–1. Finding a match on an inbound request

1. The client uses a Web browser and sends the URL to Shadow z/Enterprise Web Server.

2. Shadow z/Enterprise Web Server stores the inbound input URL ( then creates the current URL by stripping the destination information (address).

3. It uses the current URL (stored in the against the event procedure rule.

WWW.INPUTURL),

WWW.CURRENTURL) as the criteria to match

2-2 Shadow z/Enterprise Web Server Administration Guide

4. When the match is made, the rule is executed. (This process is discussed in detail later.) The results can be buffered before being sent back to Shadow z/Enterprise Web Server.

5. Shadow z/Enterprise Web Server receives the results and creates the HTTP header.

6. Shadow z/Enterprise Web Server sends this information to the client without altering the information.

+ 386 hidden pages

Progress SHADOW Z User Manual

Contents

What is Shadow z/Enterprise Web Server

How It Works

Why Use It?

Shadow z/Enterprise Web Server Architecture

How It Works

Threading Architecture

Product Capabilities and Benefits

Fast, Simple Implementation

Easily Understandable (Native MVS Web Server)

High Performance

Comprehensive Management, Monitoring, and Control Capabilities

Extreme Scalability Capabilities

How Shadow z/Enterprise Web Server Is Used

Top-Notch Security

Optional Shadow Interfaces

Executing IMS Transactions

Comparison Table

Executing CICS Transactions

Summary

An Overview of the Process

How Shadow z/Enterprise Web Server Processes Transactions

When the URL Matches a Rule