VS Web Server Release 01.00.00 Customer Software Release Notice Copyright, Getronics 2000 May 2000 Disclaimer of Warranties and Limitation of Liabilities The staff of Getronics has taken due care in preparing this document. However, nothing contained herein modifies or alters in any way the standard terms and conditions of the Getronics purchase, lease, or license agreement by which the product was acquired, nor increases in any way Getronics liability to the customer. In no event shall Getronics or its subsidiaries be liable for incidental or consequential damages in connection with or arising from the use of the product, the accompanying document, or any related materials. DOCUMENTATION LICENSE Copyright (c) 2000 Getronics, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation. A copy of the license is included in the section entitled "GNU Free Documentation License". PROGRAM LICENSE Copyright (c) 2000 Getronics, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. CONTENTS PREFACE Documentation License ii Program License ii INTRODUCTION 2 CHAPTER 1 Enhancements 3 Enhancements 3 CHAPTER 2 Hardware and Software Prerequsites 4 Hardware 4 Software 4 CHAPTER 3 Problems Corrected 5 CHAPTER 4 Restrictions and Special Considerations 6 CHAPTER 5 Media Contents 10 CHAPTER 6 Software Installation 14 CHAPTER 7 Software Operation 26 Files Used or Created During Operation 26 Recovery from System Crash 27 Regular Maintenance 28 Software Diagnosis 28 Support Aids 29 WEBMON 29 WEBMON PFKEYS 30 WEBMON Screen Fields 31 WEBREORG 34 PREFACE This customer software release notice (CSRN) provides information specific to Release 1.00.00 of VS Web Server. This notice is intended for system and networking administrators who will maintain Release 1.00.00 of the VS Web Server software. It gives an overview of the product, discusses its hardware and software requirements, explains enhancements since the previous release, discusses special considerations for its use, and lists the product's media contents. Finally, there is a chapter about software operation. The following publications are referenced within this CSRN or are suggested as prerequisite reading. * Wang Systems Networking VS Network Configuration Guide (715- 0165) * DMS/TX Reference manual (800-1128-01) * VS TCP/IP Operations Guide, Release 1.6 (715-0915B) * VS TCP/IP Configuration Guide, Release 1.8 (715-0900C) * VS System Operator's Guide (715-0418C) * VS TCP API Programmer's Guide, Release 1.6 (715-4620) * VS TCP/IP 1.8 Enhancements (715-5292) INTRODUCTION The VS Web Server product provides standard Hypertext Transfer Protocol (HTTP) service for VS computer systems equipped with 802.3 or X.25 data links. The VS Web Server product consists of the Server Daemon (SERVD), the HTTP Daemon (HTTPD), the support program WEBADMIN and several utility programs. SERVD and HTTPD form the core of the VS HTTP Server. WEBADMIN is a configuration editor that is used to configure the VS Web Server operating environment. WEBMON is a utility that is used to monitor VS Web Servers in operation. WEBREORG is a file reorganization utility that converts files from VS FTP receipt format to a format suitable for efficient delivery by VS Web Server. HTTP is the protocol of the World Wide Web. Client programs using HTTP on any platforms may formulate and send requests for documents to VS Web Server and receive corresponding text and binary documents in reply. The VS Web Server configuration editor WEBADMIN consists of a PACE application which creates and maintains information in the VS Web Server database. Refer to the VS Web Server Configuration Guide for more information about WEBADMIN and configuring VS Web Server. CHAPTER 1 ENHANCEMENTS This chapter lists enhancements made to this version of VS Web Server and discusses special considerations that apply to the configuration, operation, and administration of this release of the software. The enhancements are the major improvements that have been made to the product since its previous release. The special considerations are notes of special interest about the software or required hardware. ENHANCEMENTS This is an initial release of the software; therefore there are no enhancements. CHAPTER 2 HARDWARE AND SOFTWARE PREREQUSITES The VS Web Server software is customer installable. Before the software can operate, however, the components listed in this section must be installed. HARDWARE VS Web Server runs on any VS system configured for VS TCP/IP. * For 802.3 networks, a VS LAN controller (50V76 or 70V76 depending on the VS system) is required. * For X.25 networks, a VS 128K Telecommunications Controller (VS-TC1 or a VS-6550) can be used on any VS. For more information on prerequisites of VS TCP/IP, refer to the VS TCP/IP Configuration Guide and Customer Software Release Notices. SOFTWARE VS Web Server requires VS TCP/IP Standard Components, Release 1.85 or greater. VS TCP/IP Services are recommended. PACE 2.20 or PACE 2.20 Runtime is required for configuration of VS Web Server release 1.00.00. NOTE: PACE 2.20 Runtime is shipped with this product. CHAPTER 3 PROBLEMS CORRECTED None. This is an initial release. CHAPTER 4 RESTRICTIONS AND SPECIAL CONSIDERATIONS This section describes considerations and restrictions for the configuration and operation of systems running VS Web Server software. 1. The following software needs to be installed on the VS prior to installing the VS Web Server software: * VS TCP/IP Standard Components Refer to VS TCP/IP Customer Software Release Notices for information on prerequisites for VS TCP/IP. * PACE 2.20 or PACE 2.20 Runtime (for configuration only) WEBADMIN makes use of VS PACE 2.20 or the VS PACE Runtime, Version 2.20 to manipulate the VS Web Server configuration database. NOTE: PACE 2.20 Runtime is shipped with this product. 2. In WEBADMIN the screens behave according to the standards of PACE AB programs. 3. The following services or features are not available to users of VS Web Server, Release 1.00.00: * HTTP PUT method * Entity body in HTTP GET method * HTTP authentication (user IDs, passwords, realms) * HTTP cookies * CGI fields: * Remote Host * Remote Ident * Remote User * Path Info * Path Translated * HTTP "Keep-alive" connections * HTTP 1.1 "chunked" data transfer 4. Due to a special condition of PACE 2.20, WEBADMIN may not be used to add records to the configuration database if it is run while the VS Web Server is running. To avoid corrupting the configuration database, WEBADMIN must be run while VS Web Server is not running. If this restriction is not observed, PACE will assign a Record Sequence Number (RSN) of zero to the new record. In some of the database tables an RSN of zero will cause the record to be mistaken for the parent of another record or records that have a foreign key field containing a null value. If the foreign key field is part of a relationship on the path of a viewcopydown field, PACE will detect a path error and the table will become unusable from viewtables. While the resulting error appears serious, no irreversible damage occurs, and the tables contained in the file can be restored to full function by deletion of the record containing the zero RSN. 5. The VS system does not have to be re-IPLed for changes to the VS Web Server configuration to take effect. In all cases, stopping and restarting VS Web Server will cause all VS Web Server configuration changes to take effect. In some cases, changes are effective immediately. In general, Server and Instance configuration fields are read only at startup of VS Web Server, while other configuration records are read each time they are needed. Therefore, Server and Instance parameters will not take effect until the next startup of a VS Web Server, while changes to Path Maps, MIME Types and IP Filters will take effect immediately. 6. Server File Open Modes in Server Configuration (WEBADMIN) are not available for inspection by VS Web Server programs before opening the configuration files unless Server File Redirection records exist for all the Instances of a Server. In the absence of access to the Open Mode settings via Redirection records, VS Web Server will revert to the default of opening configuration files in INPUT or IO mode. IF REDIRECTION RECORDS EXIST FOR ONE OR MORE BUT NOT ALL INSTANCES OF A SERVER, THE RUNNING OF INSTANCES THAT DO AND DO NOT HAVE REDIRECTION RECORDS MAY RESULT IN FILE POSSESSION CONFLICTS AND CANCELLATION OF BACKGROUND SERVER SUBTASKS. Use the following rules to ensure coherent control of Server File Open Modes: INPUT/IO - No special action is required, and Redirection records may be present or not. This is the default set of Modes. SHARED - There are two ways to signal VS Web Server to use SHARED mode: * Create Server File Redirection (LOCATOR) records for all defined Instances of the Server and specify SHARED in Server configuration * Use the global MODEROSH and MODERWSH "flag" files in library @HTTP@ on the system volume to signal SHARED mode to all VS Web Servers If Redirection records are used, they must exist for all defined Instances of the Server that is to use SHARED mode for opening configuration files. Redirection records contain viewcopydown or "reflected" copies of the Server File Open Mode parameters specified in Server configuration. Changing the Mode parameters in Server configuration automatically reflects those settings in the Redirection records for the Server's Instances. It is not necessary that Redirection records actually specify any redirection. Redirection records may be created with blank redirection fields solely for the purpose of making Open Mode parameters available outside the main configuration files. If MODEROSH and MODERWSH "flag" files are used, their effect is global and affects all VS Web Servers and Instances. The MODE flag files override the Mode parameters in Server configuration. MODE files are provided in the distribution media in the form of prototype files XODEROSH and XODERWSH in library @HTTP@ on the system volume. To activate them, rename or copy them, changing the first letter of the filename to "M". To deactivate them, rename them, changing the first letter back to "X" or delete them. Each flag file contains a brief explanation of how flag files work. Try not to delete the last copy of a flag file. Renaming is safer. If neither method is used, VS Web Server will open its configuration files in INPUT or IO mode regardless of the parameter values in Server configuration. 7. To remove the subtasks of a VS WEB Server instance, run in foreground and cancelled, it is necessary to log off the workstation from which the instance was run. 8. WEBADMIN error messages are very generic in nature. For example, "Cannot Insert. Duplicate Key" is displayed if a Server Instance is defined with a duplicate Procname Root or ITM Port Root, and the duplicate field blinks. 9. The time zone of the system in which VS Web Server runs must be known to VS Web Server. Outbound HTTP messages usually contain a Date header, and many contain a Last-Modified header. HTTP calls for universal date/time stamps in Greenwich Mean Time (GMT). To compute the GMT equivalent of local time, the local time zone of the system must be known. VS Web Server takes the time zone from the name of the file in library @TZ@ on the system volume. The naming convention used to encode the hours and minutes of offset from GMT is explained in the VS Web Server Configuration Guide and in the file TIMEZONE in library @HTTP@ on the system volume. NOTE: Daylight Savings Time adjustments are not made automatically. 10. Binary image files should be reorganized before they can be served up by VS Web Server. If you wish to make a VS file of any type available in binary form for Web service, you must first convert it to VS Image format, then reorganize it with WEBREORG. 11. The userid that runs VS Web Server in foreground using the xxxSERVE procedure or submits it to background using the xxxSTART procedure must have a high Subtask Quota setting, preferably "UNL" (unlimited). See Appendix A of the VS Web Server Configuration Guide for more information on Subtask Quota requirements and how to check or set it. CHAPTER 5 MEDIA CONTENTS This chapter provides a list of the files contained in Release 1.00.00 of the VS Web Server product. Table 5-1 lists the media contents of the VS Web Server Self-Extracting MEG archive distribution, Release 1.00.00. Table 5-1. Media Contents File File File Name Version Class File Description ________ ________ _____ ___________________________________ Library = VSWS100 DEMEG312 03.12 @ Used to De-MEG VS Web Server components FIND 07.52.02 @ VSSUB GETPDBV 01.00.00 @ Used by INSTALL GPL 2 $ GNU General Public License INSTALL 01.00.00 $ Installation procedure for VS Web Server READFDR 07.52.05 @ VSSUB VSWS100A 01.00.00 $ MEG file archive of VS Web Server (see Table 5-2.) VSWSCSRN 01.00.00 $ This Customer Software Release Notice Table 5-2 lists the media contents of the MEG file archive 'VSWS100A' for the VS Web Server, Release 1.00.00 product. In the table, Protection Class represents the value that may optionally be set to restrict write/delete access by non-privileged users. Changing the protection class of these files may affect the operational characteristics of VS Web Server on your system. Version numbers for most files may be found by displaying the first record of the file or by using the SHOVERZN utility. Some files, particularly Flag Files and other text files, may not have version numbers embedded within them. Table 5-2. Media Contents File File File Name Version Class File Description ________ ________ _____ ___________________________________ Library = @HTTP@ FOOTER n/a $ Sample Server Message Footer HTTPD 01.00.00 @ HTTP Daemon MIMEPICK n/a @ Used by WEBREORG PROCINST 01.00.00 @ Used by INSTALL SERVD 01.00.00 @ Server Daemon SETVOL 01.00.00 @ Used by INSTALL TCP 01.03.00 $ TCPIP toolbox procedure TIMEZONE 01.00.00 $ Time Zone file WEBMON 01.00.00 @ VS Web Server Monitor WEBREORG 01.01.00 @ Web file reorganization utility XLOSE n/a $ Flag File XODE n/a $ Flag File prototype XODEROSH n/a $ Flag File XODERWSH n/a $ Flag File XRITERRL n/a $ Flag File ZZZADMIN n/a $ Procedure Template ZZZMON n/a $ Procedure Template ZZZMON2 n/a $ Procedure Template ZZZREORG n/a $ Procedure Template ZZZSERVE n/a $ Procedure Template ZZZSTART n/a $ Procedure Template ZZZSTOP n/a $ Procedure Template ----------------------------------------------------------------------- Library = @HTTPAPI (Application Program Interface library) COBFIGS $ Figurative Constants COBLINK $ Sample Linkage, Using COBPARSE $ Sample POST argument parsing COBWSTOR $ Working Storage for arg parse SUPPORT $ Sample PACE HLI CGI subroutine TRANNOTE $ Application note for TRANURL TRANURL @ Subroutine described in TRANNOTE ----------------------------------------------------------------------- Library = CSRNLIB (Customer Software Release Notice library) VSWSCSRN $ VS Web Server CSRN ----------------------------------------------------------------------- Library = @@HTTP## (PACE application library) CONFIG IPFILTER LOCATOR MENU MIMEPICK MIMES PATHMAP ----------------------------------------------------------------------- Library = @@HTTP#3 (PACE application library) @DBMSG MIMEPICK ----------------------------------------------------------------------- Library = @@HTTP#5 (PACE application library) PATHMAP ----------------------------------------------------------------------- Library = @@HTTP#A (PACE application library) @IPFILTR @LOCATOR @MIMES @SERVCFG @SERVMAP ----------------------------------------------------------------------- Library = @@HTTP#D (PACE application library) @ABQRY@ @DBSSL @DDBRG @PACEDDO @PACEDDS @PACEDEF @PACEOC @PACEOLC @PACEREF @QRYSSL ----------------------------------------------------------------------- Library = @@HTTP#F (PACE application library) @DBMSG MIMEPICK ----------------------------------------------------------------------- Library = @@HTTP#J (PACE application library) COPYPATH HDRUPD IPRETR IPUPD LOCATUPD MIMEPICK ----------------------------------------------------------------------- Library = @@HTTP#K (PACE application library) MIMEPICK ----------------------------------------------------------------------- Library = @@HTTP#Z (PACE application library) CONFIG IPFILTER LOCATOR MENU MIMEPICK MIMES PATHMAP ----------------------------------------------------------------------- CHAPTER 6 SOFTWARE INSTALLATION This chapter provides you with a procedure for installing the VS Web Server, Release 01.00.00 software. The following chapter discusses certain features of the software's operation after it is installed. SOFTWARE INSTALLATION To install the VS Web Server software on your system, follow these steps: NOTE: You must have VS security administrator rights on the system onto which you are installing VS Web Server. The INSTALL procedure expects that the VS Web Server files have already been restored to @HTTP@ on the system volume and to the @HTTP PACE database libraries on another volume of your choice. The files must be restored from the distribution media before running INSTALL. If this is a re-installation, ensure that no users are running VS Web Server. xxxSTOP will terminate a VS Web Server where "xxx" is the short name given to the Server during installation or subsequent generation of Server procedures. Be sure to stop all VS Web Servers that may be running. If this is a new installation, ensure that there is no @HTTP@ library on the system volume and no libraries beginning with @@HTTP# on the volume where you plan to install the configuration database. If any conflicting libraries exist, you must resolve the conflict before proceeding. NOTE: IF YOU HAVE PREVIOUSLY INSTALLED VS WEB SERVER BETA 4.1 AND WISH TO PRESERVE YOUR CONFIGURATION DATABASE, BACK UP LIBRARY @HTTP@ FROM THE SYSTEM VOLUME AND @@HTTP#+ FROM THE @HTTP DATABASE VOLUME BEFORE INSTALLING VS WEB SERVER 1.00.00. For convenience, you may also back up the five "@" Server configuration files shown in the Files section of PACE Manager for the @HTTP database to another disk. After completing the new install, move them back to @HTTP on the system volume. NOTE: IF YOU HAVE PREVIOUSLY INSTALLED VS WEB SERVER ALPHA OR PRE-4.1 BETA YOU WILL HAVE TO RECONSTRUCT THE SERVER CONFIGURATION AFTER INSTALLING VS WEB SERVER 1.00.00. To aid in doing this, make reports (PF15 Output) or screen prints of all the configuration screens before proceeding. NOTE: IF THIS IS JUST A SIMPLE RE-INSTALL, BACKING UP YOUR CONFIGURATION INFORMATION IS ADVISED, BUT NOT REQUIRED. In any of the above cases, you are strongly advised to delete the @HTTP database (or HTTP or other database if an Alpha version), the @@HTTP#A library, and any Web Server procedures and configuration files before proceeding. Ensure that the VS system you are installing to supports DMSTX. The file DMSTX must be in the system library on the system volume. 1. Log on to the system as a VS System Administrator. 2. Run GENEDIT. At the System Options Main Menu, the DMS/TX option must be set to YES. At the System Options/DMS Options screen, the 'Use SPECIAL I/O mode' option must be set to YES. If it is not, it will be necessary to change it to YES and IPL the system before proceeding. 3. Make sure the PACE Runtime library has already been installed. (If you received your copy of the VS Web server on a VS formatted tape from SDC go to step 4. Otherwise, if your copy was downloaded from the Internet as a .zip archive file proceed to step 6.) 4. Mount the tape containing the VS Web Server software, and set the following values: a. VOLUME = Volume name (VSWS10) b. LABEL = NL (for TAPE) c. Mode = EX 5. Run BACKUP with the following parameters to restore the VSWS100 library to a suitable VS volume: a. VOLUME = VSWS10 b. LIBRARY = VSWS100 c. DEVICE = TAPE d. FUNCTION = RESTORE e. DUPFILES = PROMPT When Backup is complete, proceed to step 15. 6. If you received your distribution copy of the VS Web Server as a Zip archive file, then perform the following steps (lightspeed users may choose a somewhat different approach): 7. Use WinZIP, PKzip, or other suitable ZIP archive extractor, to decompress the ZIP archive. 8. Extract the file 'VSWS100.vse' to the hard drive on your PC. 9. Using FTP, transmit the file 'VSWS100.vse' to your VS system as VS file name 'VSWS100' (the VS file system does not support 8.3 file extensions). Remember to use binary mode for the file transfer. 10. From the VS, log on and run the VS program 'FTP'. 11. Select 'FTP File Conversion' from the menu. 12. Enter the input and output file, library, and volume names, and select 'Program' as the output file type. 13. Once you have converted the file 'VSWS100' to VS Program file format, exit the FTP utility and run the 'VSWS100' program, created by the FTP conversion utility in step 12, from the command processor. The following screen should appear: ************************************************************************************ * * * Wang VS GETPARM v 7 Parameter Reference Name: PARAMS * * Message Id: 0000 * * Component: UNMEG * * Information Required by VSWS100 * * Active Subprogram is VSWS100 * * _______________________________________________________________________________ * * Self-extracting MegaFile Unpacker 3.20b * * * * * * Package : VS Web Server - http://www.vswebcenter.com * * Version : 01.00.00 Reference : 000523 * * * * * * Please specify destination for package OUTVOL = ______ * * * * * * * * Press ENTER to proceed or pfkey 16 to exit * * * * * * * * * * * * * * * ************************************************************************************ 14. Enter the name of the volume you wish to De-MEG the VS Web Server installation software to, then press 'ENTER'. 15. Run the procedure INSTALL in Library VSWS100 on the volume where the VS Web Server installation software was copied to. The following screen appears (actual screens may differ slightly from those shown here): ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * *** VS Web Server Install Procedure *** * * * * * * The VS Web Server is Free Software distributed under * * the terms of the GNU General Public License. Press * * 'PF1' to view a copy of the GPL. Please read the * * license carefully before proceeding. * * * * * * Do you agree with the terms of the GPL license: ___ * * (Enter 'YES' or 'NO') * * * * * * * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Proceed, * * 'PF1' - Display GPL License, * * 'PF14' - Display CSRN, or * * 'PF16' - Exit. * * * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ 16. You must enter 'YES' to acknowledge that you agree with the terms of the GNU license. It is recommended that you first press 'PF1' to read the license. The following screen that appears requests confirmation of the volumes used for the VS Web Server application and VS PACE database. ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * *** VS Web Server Install Procedure *** * * * * * * This procedure will install the VS Web Server onto * * your system. Please refer to the CSRN for complete * * installation instructions. * * * * * * * * VS Web Server Volume : SYS754 * * PACE Database Volume : PUBLIC * * * * * * * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Install, * * 'PF7' - Build Procs Only, * * 'PF14' - Display CSRN, * * 'PF16' - Back up one step. * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ 17. The VS Web Server Volume name is displayed as information only, to inform you where the application library '@HTTP@' will be located. If this is a first installation or a complete reinstallation of the VS Web Server software, review and correct, if necessary, the PACE Database volume name, then press 'ENTER'. Otherwise, if you are running INSTALL solely to create VS Web Server procedures, press PF7 and skip to step 13 below. INSTALL attempts to locate the PACE install volume by examining the PACE Catalog. If the PACE Catalog is not found or if no entry is found in within the catalog for @P0220, INSTALL will display a blank PACEVOL. After review and correction, when the volume names are correct, press ENTER. If a prior installation of the @HTTP@ library is found on the VS Web Server application volume, the following screen will appear: ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * *** VS Web Server Install Procedure *** * * * * * * If you wish to save copies of your older VSWS files * * to a save library you may do so by entering the * * necessary information in the fields below. * * * * * * * * Save files to Volume : VOL021 in Library : @HTTPSAV * * * * * * * * * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Save existing files, * * 'PF1' - Skip this step, * * 'PF14' - Display CSRN, or * * 'PF16' - Go back one step. * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ 18. If you wish to save the pre-existing copy of the VS Web Server Application, set the volume and library names to the desired values and press 'ENTER'. 19. If this is a re-run of INSTALL or if an earlier version of VS Web Server is present on the system, the following screen may appear: ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * W A R N I N G !! * * * * * * * * The VS Web Server database has already been installed. * * * * Installing the database again will DESTROY your * * existing VS Web Server configuration. Enter 'YES' to * * re-install the database. Otherwise this step ONLY will * * be skipped and the remaining steps will be processed. * * * * * * INSTALL = NO_ * * * * * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Acknowledge, * * 'PF14' - Display CSRN, * * 'PF16' - Back up, or * * 'PF32' - Exit. * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ If you are sure you wish to do a complete install, set INSTALL = YES. If you are only running INSTALL to create procedures for VS Web Server software already fully installed, set INSTALL = NO. Press ENTER. If you specify INSTALL = YES, the install procedure will copy the configuration database data files from library @@HTTP#A on the database install volume to library @HTTP@ on the system volume. If you already have configuration data in @HTTP@, it will be overwritten by this step. If you are re-running INSTALL as part of the initial installation of VS Web Server, perhaps because an earlier run was aborted for one reason or another, then there will be no configuration information at risk, and so you should set INSTALL = YES. 20. If you are re-running INSTALL for any reason and the VS Web Server configuration database has already been catalogued in PACE, the following screen will appear: ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * W A R N I N G !! * * * * * * * * VS Web Server database has been previously cataloged. * * * * To avoid errors, be sure the @HTTP database is not * * currently cataloged. Use PACE manager to REMOVE @HTTP * * if necessary. Enter 'YES' to catalog the @HTTP database. * * Otherwise this step in the installation will be skipped. * * * * * * CATALOG = NO_ * * * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Proceed, * * 'PF1' - Skip this step, * * 'PF14' - Display CSRN, or * * 'PF16' - Back up one step. * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ This screen means that INSTALL remembers having run this step before. It does not mean that PACE shows the @HTTP database in its catalog, although that might be the case. If you are unsure, check in PACE from another workstation window. If you know for sure that the @HTTP database was fully and correctly catalogued in a previous run of INSTALL, you may set CATALOG = NO. If you know for sure that the @HTTP database is not in the PACE catalog, you may set CATALOG = YES. If you are unsure, run PACE and examine the catalog for the presence of an @HTTP database. 21. At this point the one-time installation and cataloguing have been completed or skipped, according to the choices you made in earlier screens. INSTALL now enters the optional phase of generating VS Web Server procedures, signified by the following screen: ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * *** VS Web Server Install Procedure *** * * * * * * * * * * * * * * Do you wish to create any VS Web Server start/stop * * procedures at this time? * * * * * * * * * * * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Create Procs, * * 'PF1' - Skip Procs, * * 'PF14' - View CSRN, or * * 'PF16' - Go back one step. * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ If you wish to create VS Web Server procedures, press 'ENTER'. Otherwise, press PF 16 to exit from the INSTALL procedure. If this is a first install, you should press 'ENTER' and proceed to create at least the WEBADMIN procedure. You may re-run INSTALL at any time to create new or additional procedures, using PF7 on the initial screen to skip database installation. 22. Procedure Creation first solicits the name of the VS Web Server for which you wish to create procedures, and a short name that can be used as a meaningful prefix in naming those procedures. ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * *** VS Web Server Install Procedure *** * * * * * * Procedure Creation * * * * Enter a likely server name and abbreviation: * * * * SERVER = DEMO____ SHORT = DEM * * * * The short name will be used to construct procedure names * * that include meaningful words such as START and STOP. * * * * * * * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Proceed, * * 'PF14' - View CSRN, or * * 'PF16' - Go back one step. * * * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ The Server you specify need not exist yet in the VS Web Server configuration database. If this is a first installation and you can reasonably anticipate the first Server you will define later, you may specify it here. The short name should be chosen to be recognizably associated with the Server name, and should also be used later in defining the Procname Root of the Server Instances. The short name should not, however conflict with the various service prefixes used in VS system software, such as WSN, TCP, etc. After specifying the two fields, press ENTER. 23. INSTALL will construct four specific and three general candidate procedure names. The first four are for procedures to be generated to control the Server you specified in the previous screen. The next three are general procedures to be generated for configuring VS Web Server, for monitoring any VS Web Server, and for reorganizing consecutive and image files. ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * * * Procedures for use with server VSWS * * * * Conflict Build ProcName Template Description * * x DEMSERVE ZZZSERVE Runs VS Web Server VSWS * * x DEMSTART ZZZSTART Submits VS Web Server VSWS * * x DEMMON__ ZZZMON2 Monitors VS Web Server VSWS * * x DEMSTOP_ ZZZSTOP Stops VS Web Server VSWS * * * * x WEBADMIN ZZZADMIN General Server Admin & Config * * x WEBMON__ ZZZMON Monitors any VS Web Server * * x WEBREORG ZZZREORG Reorganizes files ftp'd to VS * * * * Job Class for Submit of WWWSERVE by WWWSTART: Z * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Build Procs, * * 'PF1' - Re-Evaluate, * * 'PF8' - Overwrite, or * * 'PF16' - Back up one step. * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ NOTE: Do not overlook the Job Class field near the bottom of the screen. This is the Job Class that will be used by the xxxSTART procedure for submitting the xxxSERVE procedure to Background. See item 24 below for the requirements for the Background Task Initiator(s) associated with the Job Class. Job Class will only have an effect if the xxxSTART procedure is flagged for building in the Build column. Any conflicts between the candidate procedure names and procedures already existing in the system library will be noted in the column headed "Conflicts." Conflicts will also be flagged if the short name you selected matches any of the common service prefixes used by VS system software, whether or not such procedures presently exist in the system library. PF 1 returns to the previous screen to allow respecification of the Server and/or short names. Candidate procedure names are modifiable. It is recommended, however, that you use the names as offered, using PF 1 to return to the previous screen to modify the short name if necessary to eliminate conflicts. The column headed "Build" contains flags you may modify to generate or not generate the corresponding procedures. A non-blank signifies procedure generation, while a blank signifies no procedure generation. Any line whose Build flags is set to blank will be omitted from the name conflict test and the corresponding procedure will not be generated. If this is a first installation and you are unsure of the name you will give your first Server, simply blank the Build flags for the first four, Server-specific procedures. The second four are general and required for configuration and setup of any Server. In any case, you should place a nonblank in the Build column for procedure WEBADMIN, as that is the procedure you will use to define VS Web Servers. The ENTER key will cause the procedures flagged in the Build column to be built in the system library only if there are no name conflicts. The ENTER key will not cause any procedures to be built if any conflicts are shown or are found in the automatic re- evaluation before building commences. This is a protection against too easily overwriting valuable procedures in your system library. PF 8 will re-evaluate the names on the screen for conflicts, without building any procedures. Shift-PF 10 (PF 26) will build the procedures flagged in the Build column even if conflicts exist, overwriting the files of the same names found in the system library. In no case, however, will INSTALL overwrite program files - only procedures. When you are satisfied with the selection of procedures and their names, press ENTER to build the procedures. 24. Upon completion of the procedure build, the following screen will appear, indicating completion of the INSTALL procedure. ************************************************************************************ * * * *** VS Continuation Engineering *** * * Date: 05/24/00 Version: 01.00.00 * * * * C O M P L E T E D * * * * Installation of the VSWS has completed. After this * * install procedure has exited, you may wish to delete the * * temporary files in library VSWS100 on volume VOL021. * * * * You may re-run this INSTALL procedure at any time to * * create new system and/or server specific procedures. * * Use 'PF7' to bypass the installation and proceed * * directly to the Build Procedures section. * * * * If this was a first time install, you should now build * * your VS Web Server configuration. Run the WEBADMIN * * utility to define your system and build your path maps. * * _______________________________________________________________________________ * * Please Select : 'ENTER' - Run WEBADMIN, * * 'PF14' - Display CSRN, or * * 'PF16' - Exit. * * * * * * Copyright (c) Getronics, Inc., 2000 * * * ************************************************************************************ 18. The normal scenario for running a production VS Web Server is to submit it to Background using its generated xxxSTART procedure. The program so submitted is SERVD, the Server Daemon. SERVD communicates with the VS TCP/IP Stack, invokes a number of subtasks specified in the Server configuration, and maps memory in common with its subtasks. Although SERVD does not presently use the PACE subsystem, it is recommended that the Background Task Initiator of the Job Class you specified in Procedure Creation be configured for sufficient Modifiable Data Area (MDA) to run PACE applications. An MDA of 2048K or 2556K will probably be sufficient in most systems. Note: DO NOT MAKE THE MDA HIGHER THAN NECESSARY. Excessively high MDA may reduce available code space to a level that prevents SERVD from running. See Appendix A of the VS Web Server Configuration Guide for more information on MDA requirements and how to check or set MDA. 19. The userid that runs VS Web Server in foreground using the xxxSERVE procedure or submits it to background using the xxxSTART procedure must have a high Subtask Quota setting, preferably "UNL" (unlimited). See Appendix A of the VS Web Server Configuration Guide for more information on Subtask Quota requirements and how to check or set it. CHAPTER 7 SOFTWARE OPERATION The procedures WEBADMIN, WEBMON and WEBREORG are automatically created during the install process (unless you elect not to generate them) and placed in the system library on the system volume. They run the respective programs which reside in library @HTTP@ on the system volume. WEBMON and WEBREORG run their programs transparently, allowing the procedures to be run from other procedures while retaining the ability to target GETPARMs in those programs with ENTER or DISPLAY statements in the calling procedures. Additional procedures xxxSERVE, xxxSTART, xxxMON and xxxSTOP may also be created during the install process and/or on subsequent runs of the INSTALL procedure. "xxx" is the short server name given during the INSTALL dialogue to the VS Web Server for which those procedures are created. For more information about VS Web Server procedures, refer to the VS Web Server Configuration Guide. FILES USED OR CREATED DURING OPERATION During the normal operation of VS Web Server and/or related maintenance activities, the following files are used: File Library Volume Description @CRITERR @HTTP@ system Critical Error Log @IPFILTR @HTTP@ system IP Filter configuration file @LOCATOR @HTTP@ system Server File Redirection @MIMES @HTTP@ system MIME Types configuration file @SERVCFG @HTTP@ system Server configuration file @SERVMAP @HTTP@ system Path Maps configuration file WEBADMIN @SYSTEM@ system VS Web Server Configuration Admin WEBMON @SYSTEM@ system VS Web Server Monitor WEBREORG @SYSTEM@ system Reorg utility for consecutive files xxxSERVE @SYSTEM@ system Runs VS Web Server xxx xxxSTART @SYSTEM@ system Submits xxxSERVE to background xxxSTOP @SYSTEM@ system Stops VS Web Server xxx xxxMON @SYSTEM@ system Monitors VS Web Server xxx During normal operation of WEBADMIN, the configuration editor, the following files are used on the system, VS Web Server database install, or PACE volumes. File Library Volume Description CONFIG @@HTTP## websrv CONFIG PACE AB program CONFIG @@HTTP#Z websrv CONFIG PACE screenfile IPFILTER @@HTTP## websrv IPFILTER PACE AB program IPFILTER @@HTTP#Z websrv IPFILTER PACE screenfile LOCATOR @@HTTP## websrv LOCATOR PACE AB program LOCATOR @@HTTP#Z websrv LOCATOR PACE screenfile MENU @@HTTP## websrv MENU PACE AB program MENU @@HTTP#Z websrv MENU PACE screenfile MIMES @@HTTP## websrv MIMES PACE AB program MIMES @@HTTP#Z websrv MIMES PACE screenfile PATHMAP @@HTTP## websrv PATHMAP PACE AB program PATHMAP @@HTTP#Z websrv PATHMAP PACE screenfile WEBADMIN @@HTTP## websrv WEBADMIN program and PACE runtime WEBADMIN @@HTTP#Z websrv WEBADMIN PACE screenfile WEBADMIN @SYSTEM@ system Admin startup procedure @PACEDEF @@P0220D system PACE database data definition @PACEDEF @@HTTP#D system @HTTP database data definition @PACEDDO @@HTTP#D websrv @HTTP database data dictionary @PACECAT @PACE@ system PACE database catalog CASEFLIP @@P0220D system PACE file PACE @@P0220D system PACE startup procedure PACEFRM @@P0220D system PACE file PACEMSG @@P0220D system PACE Message file -or- PACEMSGX @@P0220D system PACE Message file (Indexed+) PACERTL @@P0220D system PACE Runtime SSL During normal operation of WEBADMIN, a temporary file is created for database rollback recovery. It is deleted automatically upon normal termination of WEBADMIN. The file is: File Library Volume Description @dddduuu @@HTTPB websrv DMS/TX BIJ for the @HTTP database where: dddd is a unique four digit number uuu is the user's three character logon id During normal operation of any VS Web Server, temporary BIJ files such as the example above may be created during SERVD startup and by each HTTPD subtask while it is running, depending on the Server File Open Modes in effect. INPUT/IO mode selection will not presently result in the creation of any BIJ files because no configuration files are presently opened in IO mode. SHARED/SHARED will result in the creation of BIJ files, as all the configuration files are enabled for rollback recovery. Note: The total number of open files may be reduced by selecting INPUT/IO Open Modes in Server configuration. HTTPD subtasks must open @MIMES. They will only open @IPFILTR if IP Filtering is enabled. They will only open a BIJ file if SHARED mode is specified for the Server. RECOVERY FROM SYSTEM CRASH If WEBADMIN is terminated abnormally due to a system crash, standard DMS/TX rollback recovery is required. Failure to perform this recovery may result in abnormal operation of VS Web Server. The general rule of reorganizing files not properly closed should be followed prior to DMS/TX rollback recovery. If any VS Web Server is terminated abnormally due to a system crash, recovery will only be necessary to the extent that files may have been open in SHARED or IO mode. VS Web Server presently opens no configuration files in IO mode, only in INPUT or SHARED mode. Specifying INPUT/IO in Server configuration will greatly reduce the need for recovery in the event of system failure. CGI programs may open application data files outside the control of VS Web Server. It is your responsibility to keep track of the data libraries accessed by CGI programs for the purposes of performing standard file reorganizations and DMT/TX rollback recovery, if applicable, on such files. Add the @HTTP@ library to your list of libraries to be scanned after a crash for indexed files not properly closed. As a rule, detection and reorganization of files not properly closed should precede DMS/TX Softcrash Recovery. That is because Softcrash Recovery requires the files being recovered to be structurally sound. It rolls back transactions but cannot repair damaged file structure. REGULAR MAINTENANCE VS Web Servers may create the file @CRITERR in @HTTP@ on the system volume and add records to it when Critical Errors occur. This file should be purged periodically by deleting it. If there have been no problems with VS Web Server and no abnormal terminations, this file may be discarded. VS Web Server TCP/IP traffic also generates entries in the TCP/IP log. See the VS TCP/IP documentation for information on such logging and the periodic purging required. Regular maintenance should include periodic reorganization of the VS Web Server configuration files in @HTTP@ on the system volume. Whenever changes are made to the VS Web Server configuration, the files may become more and more fragmented (a side effect of VS indexed files). This reduces the efficiency with which information is retrieved from the files and takes up valuable disk space. Potentially, the maximum number of extents for a VS index file could be exceeded if the file is not periodically reorganized. VS Web Server configuration files should be backed up periodically. Since backups of system volumes are performed less frequently at most sites than backups of other volumes, consideration should be given to backing up the configuration files to another volume that is itself a participant in regular backups. Unlike the requirement in VS TCP/IP that the configuration file and library be unique in the system, copies of the VS Web Server configuration files in @HTTP@ may be made and kept on other volumes without regard to file or library names. SOFTWARE DIAGNOSIS If VS Web Server should crash, a dump file will be created in the print library on the work volume of the user who started the tasks. Contact the Getronics Customer Support Center for disposition of the dump file and to determine what other diagnostic materials will be needed to determine the problem. Before looking at dumps though, display the @CRITERR file in @HTTP@ on the system volume. VS Web Server components attempt to write critical error information to that log before terminating. If background SERVD or HTTPD tasks have terminated, the @CRITERR file may provide clues. If there is no applicable information in @CRITERR, try duplicating the problem by running SERVD in foreground or both SERVD and a single copy of HTTPD in foreground in test mode (no subtasks). Should WEBADMIN or xxxSERVE be run after a system crash without first performing the recovery process described in the "Recovery from System Crash" section, a program check will likely occur. This program check is generated by the PACE run-time system and will indicate that the @HTTP database needs to be recovered. To correct the situation, perform the recovery process and re-run the desired function. SUPPORT AIDS VS Web Server includes the following administrative programs to help configure and monitor VS Web Servers: WEBMON - Provides the facility to monitor a VS Web Server while in operation. WEBREORG - Reorganizes consecutive and image files received via VS FTP for use with VS Web Server. WEBREORG auto-detects all the common types of ASCII and binary Web files and offers a MIME Type picklist to override its determination. WEBREORG features include full date/time stamping, either by current date/time or file date, with optional update of file modification date, suppression of date/time stamp to prevent network and browser caching, and automatic MIME Type determination. Convenience includes optional input file replacement by the output file. Reorganization of files that are already standard VS files is NOT supported except in the cases of files already reorganized by WEBREORG, REORGCON or REORGIMG. Otherwise, input files MUST be 2024-byte ASCII files or 1-byte image files as created by VS FTP. Binary image files should be reorganized before they can be served up by VS Web Server. If you wish to make a VS file of any type available in binary form for Web service, you must first convert it to VS Image format, then reorganize it with WEBREORG. WEBMON WEBMON allows you to see what a VS Web Server is doing while it is running. On startup, WEBMON solicits the name of the VS Web Server to be monitored. Custom xxxMON procedures generated by INSTALL are preconfigured to target specific servers. WEBMON is entirely non-destructive except that it offers a PF Key option to shut down a Server Instance and a hidden GETPARM to shut down one or all Instances of a Server. WEBMON imposes no overhead on the Web Server being monitored. Multiple copies of WEBMON may be run, allowing more than one user to monitor one or more Servers. Following is an example of a WEBMON monitor screen: ************************************************************************************ * *** WEBMON - VS Web Server Monitor, Ver 01.00.00 (c) GetronicsWang Co. 1999 *** * * * * Server: DEMO TCP Port: 80 Total Events: 14,051 * * Instance: 1 ITM Root: de1 Event Max: 2 * * Server Date: 990917 * * Heartbeat: 18084365 (running) * * Min Conns: 32 32 Max Run Time Since IdleTime Last * * Cur Listens: 32 1+01:47:29 16:21:14 09:58:17 08:10:16 * * Cur Connects: 0 4 Tot 09-16-99 09-17-99 * * Redirects@ 26 0 CPU Time * * 00:06:46 (0.4377%) * * Modules: SERVD TCPMGR * * Versions: 01.00.00 01.00.00 * * * * Records File Library Volume BlkInUs BlkAloc Ext * * Server Log: NO DEMOLOG SCSI5 * * ProcessTrace: NO (no file) * * RawInp Trace: NO (no file) * * * * Enter) Refresh * * 1) Baseline /Revert 5) Next * * 2) First * * 3) Last * * 4) Prev 12) Shut Down 16) Exit * ************************************************************************************ Shown are some of the Server and Instance configuration parameters, for convenience, and statistics and status of the Instance under observation. Following are descriptions of the PF keys and screen fields: WEBMON PFKEYS Enter) Refresh Refreshes the screen. Refresh is not automatic. The screen is also refreshed following a PF2, 3, 4 or 5 navigation to another Instance. 1) Baseline /Revert PF 1 establishes a baseline for certain of the statistics, setting them to zero. Subsequent Refresh operations will show statistics since the baseline was established. PF 17 (Shift-PF-1) will revert to the full current statistics. Note: Displaying another Instance will revert from the baseline to full current statistics. Baselines of Instances not presently displayed will not be preserved. 2) First Displays the first defined Instance for the Server. 3) Last Displays the last defined Instance for the Server. 4) Prev Displays the previous defined Instance. 5) Next Displays the next defined Instance. 12) Shut Down Shuts down the Server Instance or all Instances of the Server. A confirmation screen is displayed, where pressing ENTER will shut down the displayed Instance, or PF 8 will shut down all defined Instances of the Server. 16) Exit Terminates monitoring and exits from the WEBMON utility. WEBMON SCREEN FIELDS Server The name of the Server being monitored. Server name is defined in Servers & Instances in WEBADMIN. TCP Port The TCP Port number on which this Instance of the Server listens for incoming connections. Total Events The total number of TCP/IP events handled by this Instance since it started. Instance The number of this Instance. ITM Root The Intertask Message Port root for this Instance. Event Max The maximum number of events reported by TCP/IP in any one Event Control Block. Server Date The date maintained by this Instance. If the Instance is running, the Server Date will be current, and is one component of determining whether the Instance is running. If an instance has not been run or started, this field will contain zeros. Heartbeat The time of day maintained by this Instance. If the Instance is running, the Heartbeat will be current and will update frequently. It is the other component of determining whether the Instance is running. If an instance has not been run or started, this field will contain zeros. To the right of the Heartbeat number is the Instance status, in parentheses. Status is determined by the currency of the Heartbeat. Min Conns The Minimum Connections for which this Instance is configured. Max The Maximum Connections for which this Instance is configured. In Release 1.00.00 of VS Web Server, Minimum and Maximum must be the same number. Run Time The number of days, hours, minutes and seconds this Instance has been running. Days are suppressed unless nonzero, in which case they will be separated from hours by a plus sign ("+"). Since The time and date since which the Instance has been running. Idle Time The number of days, hours, minutes and seconds this Instance has been idle. Days are suppressed unless nonzero, in which case they will be separated from hours by a plus sign ("+"). Last The time and date of the last traffic handled by this Instance. Cur Listens The current number of TCP Listens being held by this Instance. A Listen is a potential connection. Cur Connects The current number of active TCP connections being managed by this Instance. An active connection is one that has been received and accepted for processing and not yet closed and recycled into a Listen. Tot The total number of TCP connections that have been handled by this Instance since it started. Redirects@ The threshold at which this Instance will redirect overflow traffic to other Instances, followed by the total number of redirections performed (unlabeled). CPU Time The total CPU time in days, hours, minutes and seconds, followed by the percent of total CPU in parentheses. Modules The versions of the major modules in the VS Web Server Daemon programs. Presently, only the modules in the SERVD Server Daemon are shown - HTTPD module versions are not shown. Server Log, Process Trace, Raw Input Trace The status and details of the log files in use by this Server. YES/NO Indicates whether or not a log is active Records The number of records presently contained in the log file. If the log file is not active, this number is accurate. If the log file is active, this number reflects the number of records returned by READFDR plus the number added by this instance since opening the log file. File The file name of the log file. Library The library where the log file is located. Volume The volume on which the log file is located. BlkInUs The number of blocks presently in use in the log file. If the log file is not active, this number is accurate. If the log file is active, this number may not reflect the current blocks in use. BlkAloc The number of blocks allocated in the log file. This number should be accurate regardless of whether the log file is active or not. Ext The number of extents used by the log file. This number should be accurate regardless of whether the log file is active or not. WEBREORG WEBREORG is a Web file reorganization utility that handles both consecutive and binary image files. In addition, it detects most file types by their content and performs MIME typing. WEBREORG embeds HTTP Content-Type, Content-Length and Last-Modified headers in the output file and can replace the input file with the output file. Determinations made by WEBREORG are optionally displayed for review and correction. WEBREORG reorganizes consecutive files from the 2024-byte, variable- length uncompressed format written by VS FTP to a 2024-byte, variable, COMPRESSED format. This saves disk space. HTTP Content-Type, Content- Length and Last-Modified headers are embedded in the output file and are used by VS Web Server to formulate complete HTTP headers for the file when delivered to a requestor. WEBREORG reorganizes binary image files from the 1-byte, fixed, uncompressed format written by VS FTP for binary files to a 2024-byte, variable, NOT COMPRESSED format. This is REQUIRED for VS Web Server to deliver a binary file. HTTP Content-Type, Content-Length and Last- Modified headers are embedded in the output file and are used by VS Web Server to formulate complete HTTP headers for the file when delivered to a requestor. WEBREORG GETPARMS OPTIONS STAMP 3 YES/NO Generate date/time stamp CURRENT 3 YES/NO Use current date/time REFRESH 3 YES/NO Refresh existing stamp TIMEZONE 5 +hhmm Hours, minutes from GMT REVIEW 3 YES/NO Review determinations INPUT FILE 8 filename LIBRARY 8 library VOLUME 6 volume REPLACE 3 YES/NO Replace input file REVIEW FILE 8 (non-modifiable) LIBRARY 8 (non-modifiable) VOLUME 6 (non-modifiable) LENGTH var (non-modifiable) OFILE 8 filename Output file OLIBRARY 8 library Output library OVOLUME 6 volume Output volume FILECLAS 1 file class File protection class OWNER 3 userid Owner of output file MIMETYPE 64 mime type MIME Type of file FILEDATE 10 date File datestamp FILETIME 8 time File timestamp Pf2 forces current date/time in FILEDATE, FILETIME Pf3 forces current owner and class in OWNER, FILECLAS Pf14 presents a picklist of MIME Types -END-