OM OMCS/z Web Server INSTALLATION & OPERATION GUIDE. OMCS/z Web Server Version 1.0

Transcription

1 OM OMCS/z Web Server INSTALLATION & OPERATION GUIDE OMCS/z Web Server Version 1.0 December 2012

2 LICENSED MATERIAL COPYRIGHT Australian Systems Engineering Pty. Ltd This material always remains the property of Australian Systems Engineering Pty. Ltd. and must be used only in accordance with the terms of the agreement under which it is supplied. Manual and Product identifiers. This manual is identified by a publication number, OM , combined with a revision level number (sometimes called a dash level) -1. The licensed software product, of which this manual is a part, is identified by a Product Name or Product Acronym and an Edition Number. Edition numbers are made up of a Version number and a Release number within that version. The material in this manual is intended to be used with OMCS/z Web Server Version 1 Release 0 and later editions of that product. The edition number may appear in licensed material in abbreviated forms like the following: V1R0, and V1.0. From time to time ASE may issue replacements for, or additions to, the pages in this manual. Each time the entire manual is replaced by a later version then the revision level (the dash level) part of the publication identifier will be increased by 1. Related Publications none Published by Australian Systems Engineering Pty. Ltd. 126A Gillies Street, Fairfield VIC 3078 Australia website: help@ase.com.au

3 OMCS/z Web Server - Introduction Contents CONTENTS...3 INTRODUCTION...5 PART 1 - INSTALLATION GUIDE...7 CHECK PREREQUISITES...7 ALLOCATE NEW LIBRARIES...7 Sample JCL for allocating the new libraries...8 DEFINE NEW LIBRARIES TO SMP/E...8 SMP/E INSTALLATION OF OMCS/Z WEB SERVER...8 PART2 - CONFIGURATION AND OPERATION GUIDE...9 CREATING THE OMCS/Z WEB SERVER STARTED TASK JCL PROCEDURE...9 Using the supplied sample as a starting point...9 OMCS/Z WEB SERVER CONFIGURATION...10 General rules for configuration dataset statements...10 Configuration statements...10 BINDRETRYCOUNT...10 BINDRETRYTIME...10 DATABASE...11 LISTENQUEUE...11 LOG...11 PAGESIZE...11 PASSTIMEOUT...11 PORT...12 RESOURCEDIR...12 SECURITY...12 DATABASE PROCESSING...12 STOPPING THE OMCS/Z WEB SERVER...12 RUNNING MORE THAN ONE OMCS/Z WEB SERVER...12 CONTACTING ASE FOR SUPPORT :...13 OM copyright 2012 ASE page 3

4 OMCS/z Web Server - Installation Guide page 4 copyright 2012 ASE OM

5 OMCS/z Web Server - Introduction Introduction Part 1 of this manual provides guidance for the installation of the OMCS/z Web Server. Part 2 of this manual describes the configuration and operation of the OMCS/z Web Server. ASE's support for this product began when you first requested that the install material be supplied to you. If at any subsequent time you find that the material in this or any other OMCS manual is confusing, inadequate or incorrect, or if you encounter any problem with the supplied machinereadable material or get unexpected results from the installed product, please call ASE for support. OM copyright 2012 ASE page 5

6

7 OMCS/z Web Server Installation Part 1 - Installation Guide The OMCS/z Web Server is part of OMCS 2.9 and the first version is delivered by PTF ASP1285. The following list summarises the tasks required to install the web server. Check prerequisites. The install materials must be downloaded from the ASE web site and transferred to your z/os system before installation can proceed. Allocate new libraries Two new libraries are required for OMCS/z Web Server. Defining the new libraries to SMP/E Define the new libraries to SMP/E with DDDEF entries. SMP/E Installation of OMCS/z Web Server The standard RECEIVE, APPLY and ACCEPT process is used to install PTF ASP1285. Check Prerequisites OMCS/z Web Server requires ASE Cross Product Services. This is FMID ZSEX100 and may already be installed. If ZSEX100 is not installed yet, you must obtain it from ASE and install it. Allocate New Libraries OMCS/z Web Server introduces two new libraries. The datasets must be created before the installation can proceed. Note that the lowest level of the dataset name must be as shown - this is required by SMP/E. However, the higher levels may be whatever the installation requires (eg. SYS3.CPUA.ASERES or ASE.ASERES). The following table shows the actual amount of space used by each dataset after a typical installation. Library RECFM LRECL BLKSIZE number of tracks number of directory blocks ASE.AASERES VB ASE.ASERES VB OM copyright 2012 ASE page 7

8 OMCS/z Web Server Installation Sample JCL for allocating the new libraries //ALOCDSN EXEC PGM=IEFBR14 //* //AASERES DD DSN=ASE.AASERES,DISP=(,CATLG), // DCB=(RECFM=VB,LRECL=4096,BLKSIZE=0), <- system-determined blksize // SPACE=(TRK,(5,5,10)), // UNIT=SYSDA,VOL=SER= <- insert the desired DASD volume //ASERES DD DSN=ASE.ASERES,DISP=(,CATLG), // DCB=(RECFM=VB,LRECL=4096,BLKSIZE=0), <- system-determined blksize // SPACE=(TRK,(5,5,10)), // UNIT=SYSDA,VOL=SER= <- insert the desired DASD volume Define New Libraries to SMP/E Define the new libraries with DDDEF entries. Here are some sample DDDEF statements. Adjust the target and distribution zone names for your site. SET BDY(TGT) /* set to target zone */ /* */ /* new DDDEFs for target zone */ /* */. UCLIN. /* */ ADD DDDEF(AASERES) /* dlib resource lib */ DATASET(ASE.AASERES) /* */ SHR. /* */ ADD DDDEF(ASERES) /* target resource lib */ DATASET(ASE.ASERES) /* */ SHR. /* */ ENDUCL. /* */ SET BDY(DLB) /* set to DLIB zone */ /* */ /* new DDDEFs for distribution zone */ /* */. UCLIN. /* */ ADD DDDEF(AASERES) /* dlib resource lib */ DATASET(ASE.AASERES) /* */ SHR. /* */ ADD DDDEF(ASERES) /* target resource lib */ DATASET(ASE.ASERES) /* */ SHR. /* */ ENDUCL. /* */ SMP/E Installation of OMCS/z Web Server Finally, install PTF ASP1285. There may be fixes and enhancements to OMCS/z Web Server since PTF ASP1285 was produced. Check with the ASE web site and download and install any new PTFs that are relevant. page 8 copyright 2012 ASE OM

9 OMCS/z Web Server Configuration and Operation Part2 - Configuration and Operation Guide The remaining installation tasks consist of the following activities : OMCS load library must be APF authorised. Depending on the configuration, OMCS/z Web Server may need to verify that userids and passwords are correct. To be able to do that the load library must be APF authorised. Creating the OMCS/z Web Server started task JCL procedure. OMCS/z Web Server uses a started task to perform its functions. A sample catalogued JCL procedure is supplied in the.asesamp library as member ZSEWSJCL. OMCS/z Web Server configuration. Specify the configuration for the OMCS/z Web Server. A sample configuration file is supplied in the.asesamp library as member ZSEWSCFG. Support Our support for this product began when you first requested that the install material be supplied to you. If at any subsequent time you find that the material in this or any other OMCS manual is confusing, inadequate or incorrect, or if you encounter any problem with the supplied machine-readable material or get unexpected results from the installed product, please contact ASE for support. See the inside cover of this manual for contact details. Creating the OMCS/z Web Server Started Task JCL Procedure Using the supplied sample as a starting point A sample OMCS/z Web Server catalogued JCL procedure is provided as member ZSEWSJCL in the ASESAMP install library. The items to be tailored are :- //STEPLIB DD DISP=SHR,DSN=your.ASELIB // DD DISP=SHR,DSN=TCPIP.SEZATCP The first DD statement specifies the full name of the ASELIB dataset that was updated by SMP/E. If that library is in the linklist, it may be omitted from the JCL. The second DD statement specifies the SEZATCP load library. If that library is in the linlist, it may be omitted from the JCL. If both of these load libraries are in the linklist, the STEPLIB DD statement may be omitted entirely. If STEPLIB is specified, remember that all libraries in the STEPLIB concatenation must be APF authorised. OM copyright 2012 ASE page 9

10 OMCS/z Web Server Configuration and Operation //SYSIN DD DISP=SHR,DSN=... The SYSIN DD statement points to a dataset containing the OMCS/z Web Server configuration. A sample is provided in the.asesamp library as member ZSEWSCFG. Refer to the next section for configuration details. OMCS/z Web Server can run as a started task or as a batch job. OMCS/z Web Server Configuration General rules for configuration dataset statements The control, statements are generally case-insensitive. Both the name and value may be in mixed case. Any exceptions to this are noted in the configuration statement descriptions. For example, SECURITY=RACF, security=racf and Security=RaCf are all valid. Any blank lines in the configuration are ignored. Comments are preceded by the characters /* Configuration statements The sample configuration provides an annotated example of a working configuration. The sample may be found in the.asesamp library as member ZSEWSCFG. BINDRETRYCOUNT If the server cannot bind to the listen port, it will retry according to the BINDRETRYCOUNT and BINDRETRYTIME settings. BINDRETRYCOUNT specifies how many times to retry the bind before gving up. Sometimes the listen port may be unavailable for a short time when the web server hase been stopped and immediately restarted. If not specified, it will default to 20. For example: BINDRETRYCOUNT=20 /* BIND RETRY COUNT BINDRETRYTIME If the server cannot bind to the listen port, it will retry according to the BINDRETRYCOUNT and BINDRETRYTIME settings. BINDRETRYTIME specifies how long to wait in seconds between retry attempts. Sometimes the listen port may be unavailable for a short time when the web server hase been stopped and immediately restarted. If not specified, it will default to 10 seconds. For example: BINDRETRYTIME=10 /* BIND RETRY TIME IN SECONDS page 10 copyright 2012 ASE OM

11 OMCS/z Web Server Configuration and Operation DATABASE One or more DATABASE statements must be specified to indicate which OMCS databases will be accessed by the server. Each statement must contain the dataset name of the database. The dataset name may optionally be followed by a short description which will be shown on the web pages. The description is case sensitive. For example: DATABASE=USER.ACCOUNTS.DBAS,Accounts The description may contain spaces or other special characters. For example: DATABASE=USER.ACCOUNTS.DBAS,Accounts Receivable DATABASE=USER.FRED.DBAS,Fred s database LISTENQUEUE This specifies how many web server requests can be queued up before further requests are rejected. If not specified, it will default to 5. Note that requests only queue up when the server is busy processing a request. For example: LISTENQUEUE=5 /* LISTEN QUEUE LENGTH LOG This controls how much detail is written to the SYSPRINT log. VERBOSE will produce a lot of detail about each transaction. TERSE produces much less detail. If not specified, it will default to TERSE. For example: LOG=VERBOSE PAGESIZE This specifies how many lines are presented on selection list web pages. If not specified, it will default to 60. For example: PAGESIZE=60 /* PAGE SIZE The value set here becomes the initial page size for new users. Once a new user has successfully logged on, they may change it. PASSTIMEOUT This specifies the password timeout interval in minutes. The user is forced to login again if his/her last request occurred more than the specified number of minutes ago. If not specified, it will default to 5 minutes. For example: PASSTIMEOUT=10 /* PASSWORD TIMEOUT IN MINUTES OM copyright 2012 ASE page 11

12 OMCS/z Web Server Configuration and Operation PORT This specifies the TCP/IP port that the web server listens on. If not specified, it will default to For example: PORT=8080 /* LISTEN PORT RESOURCEDIR This specifies where resources (images, applets, etc.) will be retrieved from. It must be the dataset name of the ASERES library created when the web server was installed. For example: RESOURCEDIR=sys9.aseres SECURITY This specifies the password validation method. NONE means that passwords are not validated and won t be solicited from the user. Only a valid userid is necessary to login. RACF means that the user must enter a password which will be validated by RACF. Note that the RACF option will NOT work if the load library is not APF authorised. If not specified, it will default to NONE. For example: SECURITY=NONE /* SECURITY METHOD Database Processing Each database specified in the configuration will be inspected for the presence of jobs and reports. The presence of a.jobdetl MASTER file is used to indicate that job output is available for viewing. The presence of a REPTVIEW /IRM file is used to indicate that reports are available for viewing. If neither of those files are present, the database is ignored. Stopping the OMCS/z Web Server OMCS/z Web Server can be stopped by issuing a P (STOP) command at a z/os console. Running more than one OMCS/z Web Server Multiple OMCS/z Web Server started tasks may run simultaneously. Each one must specify a different port number in its configuration. page 12 copyright 2012 ASE OM

13 OMCS/z Web Server Configuration and Operation Contacting ASE for support : If support of any kind is required, please always do the following first: 1. Send all details of the problem or requirement by to HELP@ASE.COM.AU. 2. Indicate the severity of the impact (high through low) by including the word SEV1, SEV2, SEV3 or SEV4 in the Subject: line of the ; If the impact is high (a SEV1 or SEV2) then, AFTER YOU HAVE SENT THE DESCRIBED IN POINT 1. ABOVE, please also do the following: 3. Call (03) (international: ) and leave the three-word message Urgent support required. No more than that, it will simply confuse our call centre staff as they are not technical people. OM copyright 2012 ASE page 13

14 Publication number: OM This manual serves as a reference source for users of the OMCS/z Web Server product. Please use this form to comment on the publication in terms of its organization or content with the understanding that ASE may use or distribute the information that you supply in any way that it believes appropriate without incurring an obligation to you. If you require further copies of this publication please order them through your ASE representative. If you require assistance in the installation, configuration or use of the OMCS/z Web Server product please contact ASE for support. Suggested aspects that might be addressed by your comments include: Clarity Accuracy Completeness Organization Examples Legibility Please give your name and address if you require a reply: name: Address: Occupation: Comments: