SPARTA News


Sparta logo


August 2016


SPARTA President’s Corner

contributed by Randy Springs


We received word this afternoon that Tommy Thomas, our friend and longtime SPARTA treasurer, passed away at his home yesterday.

A funeral service will be held Monday, August 1, 2016 at 11 a.m. at Rock Spring Baptist Church. Burial will follow in the Rock Spring Baptist Church Cemetery in Pittsboro, NC.

The family will receive friends at Clements Funeral Home in Durham on Sunday, July 31, 2016 from 6:00 p.m. to 8:00 p.m.

Here is a link to his obituary.

Out of respect for Tommy, we have cancelled the August 2 meeting of SPARTA. Our next meeting will be August 30 for the Durham Bulls baseball game, where we will remember Tommy’s love for this event and his dedication to our group. Please remember the family in your thoughts and prayers over the next few weeks.


We'll send out a notice later about how to get tickets for the August 30th game.


Randy Springs
BB&T



Future Speakers

(subject to change)


August 2, 2016 - Cancelled


August 30, 2016 (Special Date) - Durham Bulls at the DBAP to Remember Tommy Thomas


We need ideas and volunteers for future speakers. Presentations don’t have to be fancy, just informative and interesting. Even a 5 or 10 minute talk can start an interesting interaction. Contact Ron Pimblett by phone as noted below.



2016-2017 SPARTA

Board of Directors


Randy Springs - President

BB&T                  (919) 745-5241

3200 Beechleaf Court, Suite 300

Raleigh, NC 27604


Ron Pimblett - Vice President

MDI Data Systems 919-426-6518

866-634-3282

Raleigh, NC 27609


Mike Lockey -  Secretary

Guilford Co. Information Services  336-641-6235

201 N. Eugene St.

Greensboro, NC 27401


Tommy Thomas - Treasurer

LabCorp                  336-436-4178

3060 S. Church St.

Burlington, NC 27215


Ed Webb -  Communications Director

SAS Institute Inc.  919-531-4162

SAS Campus Drive

Cary, NC 27513



Meetings


Meetings are scheduled for the first Tuesday evening of each month (except no meeting in January), with optional dinner at 6:15 p.m. and the meeting beginning at 7:00 p.m.


These monthly meetings usually are held at LabCorp’s Center for Molecular Biology and Pathology (CMBP) near the Research Triangle Park (see last page). Take I-40 to Miami Boulevard and go north. Turn right onto T.W. Alexander Drive. Go about a mile or so. Then turn right into LabCorp complex and turn Left to the CMBP Building (1912 T.W. Alexander Drive). In the lobby, sign in as a visitor to see Tommy Thomas. Tommy will escort you to the conference room.


Call for Articles


If you have any ideas for speakers, presentations, newsletter articles, or are interested in taking part in a presentation, PLEASE contact one of the Board of Directors with your suggestions.


Newsletter e-Mailings


The SPARTA policy is to e-mail a monthly notice to our SPARTA-RTP Group. The newsletter is posted to the website about five (5) days before each meeting so you can prepare. The SPARTA-RTP Group is maintained by Chris Blackshire; if you have corrections or problems receiving your meeting notice, contact Chris at chrisbl@nc.rr.com.


July 2016 “CBT Tape” Shareware Online


The directory and files from the latest CBT tape V491 (dated July 6, 2016) are available from www.cbttape.org.


If you need help obtaining one or more files, contact Ed Webb at SAS (see Board of Director’s list for contact info).


Minutes of the July 12, 2016 Meeting


•Meeting was called to order at 7:00 PM by Randy Springs, the SPARTA President.


•The meeting was held at a LabCorp conference room in RTP, N.C.


•Twelve (12) people were present of which Ten (10) are 2016 members.


•Everyone in the room introduced themselves, told where they worked, and briefly described their job functions or their job hunting challenges.


•The minutes for the June meeting were approved as published in the July 2016 newsletter.


•The Treasurer's report was read by Tommy Thomas. The current balance of $405.89 was approved as read.



OLD BUSINESS


•Articles are needed for this newsletter. If you want to write an article for this newsletter, please contact Ed Webb. Keep in mind that you don't really need to write the article, it can be an article that you read that you would like to share with the membership.


•The SPARTA Web site is available at http://www.spartanc.org. Please send any comments or suggestions about the Web page to Mike Lockey. Be sure to check the Web site every once in a while to see any new or changed information.


•Tommy reminded everyone to leave the LabCorp conference room clean.


•Future Speakers and Topics (subject to change based on internal politics, budget, the weather):



Date

Company

Speaker

Topic

August 2, 2016

EMC

Mike Fishman

Architecting Data Protection

August 30, 2016
Special Date

Baseball night

Tommy’s Spit Ball

Fun at the Park

Oct 4, 2016

Various

SHARE Attendees

Share Atlanta Information

November 1, 2016

TBD

December 6, 2016

TBD



If you have suggestions about speakers and topics, contact Ron Pimblett.


•The next SPARTA monthly meeting will be on Tuesday, August 2, 2016 at LabCorp in RTP.


•Food for the August 2 meeting will be BarBQ.


•The 2016 dues are due ($30) starting in March 2016. Please pay Tommy Thomas.


•Thanks to LabCorp and Tommy Thomas for hosting the meeting.


•There are currently 66 people on the SPARTA-RTP email list (no change from April).


•Send any e-mail address changes to Chris Blackshire so he can update the SPARTA-RTP Listserv. You will be added by the moderator (Chris = SPARTA-RTP-owner@yahoogroups.com) sending you an invitation to Join the list.


• We need to start planning for a new meeting place when Tommy retires in 2017.



NEW BUSINESS


• Tommy Thomas will handout tickets for the Aug 30 Durham Bulls baseball game at the Aug 2 meeting or email Tommy for the electronic version.

• The Business portion ended about 7:50 PM.

PRESENTATION


• IBM HTTP Server: Migration To Apache User Experience by Ed Webb of SAS

• Agenda

- Our Environment
- IBM HTTP Server Domino Timeline at SAS
- Resources for Migration
- What Does an HTTP Server Do?
- IHSA Setup
- IHSA Configuration
- IHSA Setup for MVSDS
- IHSA Setup for “Public” Security
- IBM HTTP Server Domino Instance at SAS
- IBM HTTP Server Apache Instance at SAS
- IBM HTTP Server Apache Logs at SAS
- IBM HTTP Server Apache on z/OS 2.2
- IHSA Migration Challenges
- Some thoughts about IBM HTTP Server from Marna Walle

Our Environment
- SAS Product Build and Test is Our Real Production
- - zBC12 for Production, Sandbox, Licensing LPARs
- - z13 for Product Development and Testing LPARs
- - - 5 CPs
- - - 2 zIIPs (zAAP-enabled)
- Small Shop, Small Staff (10 in 2014, 5 in 2016)
- Big Data so Big SYSRES and Big DLIB Volumes
- SYSRES libraries and file systems are not SMS-managed
- SYSRES data sets are indirectly cataloged (except VSAM)
- 2 Sysplexes Running z/OS in One GRS Ring
- - Production Sysplex with One LPAR
- - Test Sysplex with One LPAR
- - -System Programmer “Sandbox”
- - zBC12 Only
- 1 Sysplex Running z/OS in a GRS Star
- - Development System with Four LPARs
- - - One LPAR is Primarily for System Programmer Use
- - z13 (3 LPARs)
- - zBC12 (1 LPAR)
- z/OS 2.2 at SAS
- - Include$ RACF, DFrmm, DFhsm, DFdss, DFSort, RMF, Print Support Facility and Fonts
- - Include$ HLASM Toolkit, C/C++, COBOL, FORTRAN, PL/1, Pascal, WebSphere MQ
- - Includes Ported Tools (all features; IBM HTTP Apache server)
- - Java (2 versions, 4 releases, two flavors of each = 8 Java FMIDs), XML V10
- - Includes z/OSMF (and its “Liberty Profile” WAS)
- - Include$ JES3 (for use by z/OS guests under z/VM)
- - Monthly RSU APPLY

IBM HTTP Server Domino Timeline at SAS
- Domino Go WebServer (DGW)
- - March 1998 (DGW 4.6.1)
- - - Early Implementation
- - June 1999 (DGW 5.0)
- - - Upgrade
- - February 2000 (DGW 5.1)
- - - Just another upgrade
- IBM HTTP Server 5.x powered by Domino (IHSD)
- - March 2001 (DGW 5.3)
- - - Migration relatively smooth
- - - Revised our file structure to run multiple HTTP Servers for SAS Product NLS (Native Language) Testing
- IHSA 7.0
- - November 2008 (z/OS V1R10)
- - - IBM Ported Tools for z/OS HTTP Server
- - - - FMID HHAP700
- - - - No Charge product
- - - Used it to test IPv6 with SAS product offerings
- IHSA 8.5
- - February 2014 (IHSA 8.5.5 CBPDO on z/OS V2R1)
- - - IBM Ported Tools for z/OS HTTP Server
- - - - FMID HHAP85P
- - - - UI28569 IHSA 8.5.5.6 (available July 2015)
- - - Migration from IHSD began slowly and continues

Resources for Migration
- Online Books
- - IBM HTTP Server on z/OS: Migrating from Domino-powered to Apache-powered
- - IBM HTTP Server - Powered by Apache User’s Guide
- - z/OS HTTP Server Planning… (IHS Domino)
- Sample Configuration Files
- - z/OS 2.1 or earlier (IHS Domino) /usr/lpp/internet/samples/config/httpd.conf
- - z/OS 2.1 with Ported Tools IHS Apache feature /usr/lpp/IHSA/V8R5/conf/httpd.conf.default
- - z/OS 2.2 IHS Apache feature /usr/lpp/ihsa_zos/conf/httpd.conf.default
- IBM HTTP Server powered by Domino
- - Installed on z/OS 2.1 or z/OS 1.13
- - Up and Running
- - - Customized for your shop
- IBM HTTP Server powered by Apache feature of IBM Ported Tools for z/OS
- - Installed on z/OS 2.1 or z/OS 1.13
- - - CBPDO or
- - - ServerPac
- - - UI28569 Available July 2015
- - Time to setup our Apache Server

What Does an HTTP Server Do?
- Deconstructs the URL (Universal Resource Locator) or URI (Universal Resource Identifier)
- HTTP or HTTPS and Domain Name and Port
- - http:// and www.apple.com and its port :80 (default, rarely specified)
- - Directs TCPIP to the HTTP server of your choice via IP Address from the Domain Name Server and the specified or implied Port
- Parses the Resource Locator or Identifier
- - Takes implied or specified value and determines what to do
- - - Provides a Default first page from a particular file, OR
- - - www.apple.com goes to a default first page (no resource provided)
- Takes explicit parameters and finds a Program or file to handle
- - www.apple.com/support becomes https://support.apple.com

IHSA Setup
- Based on “Sample Real World Process” in Redpaper
- Define a configuration directory
- - Used our existing /web/ which has its own File System
- - Defined a subdirectory (mountpoint) with its own FS
- - - /web/server30
- - Created and mounted the hlq.WEB.SERVER30.image file system at /web/server30
- Define a userid for the IHSA Server
- - Used our existing WEBADM one in our IMWEB Group
- - - Marked PROTECTED (NOPASSWORD NOOID) - Create an HTTP Server instance
- - su - webadm
- - cd /usr/lpp/IHSA/V8R5/bin
- - ./install_ihs/web/server30 8840 (8840 is listen port)
- Define a Started Task Profile for the IHSA Server
- - RDEFINE STARTED IMWEBS30.* STDATA(USER(WEBADM))
- - SETROPTS RACLIST(STARTED) REFRESH
- Create a Started Task Procedure in SYS1.PROCLIB
- - Based on SHAPJCL2(HAPBPROC) [altered for this slide]

//IMWEBS30 PROC ACTION='start',
// DIR='/web/server30',
// CONF='conf/httpd.conf'
//* To end this server, S IMWEBS30,ACTION='stop' Restart is =‘graceful’
//IHS EXEC PGM=BPXBATCH,MEMLIMIT=512M,
// PARM='SH &DIR/bin/apachectl-k &ACTION -f &CONF -DNO_DETACH',
//STDOUT DD PATH='&DIR/logs/proc.output',
// PATHOPTS=(OCREAT,OAPPEND,OWRONLY),
//* PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP)
//STDERR DD PATH='&DIR/logs/proc.errors',
// PATHOPTS=(OCREAT,OAPPEND,OWRONLY),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP)
// PEND

- Start the HTTP Server
- - S IMWEBS30
- - Multiple Address Spaces are created, most are children to handle requests
- Verify the IHSA Server http://s390devt.mvs.sas.com:8840/index.html
- Example screen displayed (Becomes the webpage at /web/server30/htdocs/index.html)
- Check the IHS Domino Server (sample displayed) http://s390deva.mvs.sas.com

IHSA Configuration
- Based on “Chapter 5: Migration” in Redpaper
- Our Goal for Migration: Do What We Do Now
- - No SSL, No SMF
- - No Application Changes –Required z/OS Services
- - - CGIUTILS
- - - CGIPARSE
- - - MVSDS
- What’s Ours in the IHSD Configuration File?
- - Compared our /web/server1/httpd.conffile with the IHSD sample in /usr/lpp/internet/samples/config/httpd.conf
- - Used ISPF 3.17 and its COMPare command
- Enable Services in IHSA (uncomment in httpd.conf)
- - # Enable SAF (RACF) Security
- - - LoadModule authnz_saf_module modules/mod_authnz_saf.so
- - # Enable support for z/OS Modify Commands
- - - LoadModule zos_cmds_module modules/mod_zos_cmds.so
- - Add directive to shipped httpd.conffor MVSDS
- - - # allow the server to display z/OS data sets
- - - LoadModule mvsds_module modules/mod_mvsds.so
- Existing Services in IHSD
- - #Enable addition logs
- - - AccessLog /web/server1/logs/httpd-log
- - - ErrorLog /web/server1/logs/httpd-errors
- Enable Services in IHSA
- - #Enable additional logs
- - -CustomLog logs/referer_logreferer
- - - CustomLog logs/agent_logagent
- •“URL and File Mapping Directives”
IBM HTTP Server powered by IBM HTTP Server powered by
Domino Apache
Pass Alias
Exec ScriptAlias
Map Rewrite
Redirect Redirect
Fail Deny
Proxy ProxyPass
- PASS Directive in IHSD
- - Pass /BonusPak2/* /usr/local/BonusPak2/*
- - Pass /BonusPak/* /usr/local/BonusPak2/bookdemo/*
- ALIAS Directive in IHSA
- - Alias /BonusPak2/ "/usr/local/BonusPak2/"
- - Alias /BonusPak/ "/usr/local/BonusPak2/bookdemo/"
- EXEC Directive in IHSD
- - Exec /BonusCGI2/* /usr/local/BonusPak2/cgi-bin/*
- - Exec /BonusCGI/* /usr/local/BonusPak2/bookdemo/cgi-bin/*
- ScriptAliasDirective in IHSA
- - ScriptAlias /BonusCGI2/ "/usr/local/BonusPak2/cgi-bin/“
- - ScriptAlias/BonusCGI/ "/usr/local/BonusPak2/bookdemo/cgi-bin/"
- Redirect Directive in IHSD
- - Redirect /secure/* https://s390devt.mvs.sas.com:443/*
- - Redirect /insecure/* http://s390devt.mvs.sas.com:80/*
- Redirect Directive in IHSA
- - Redirect permanent /secure/ https://s390devt.mvs.sas.com:443/
- - Redirect permanent /insecure/ http://s390devt.mvs.sas.com:8840/
- ASCII and EBCDIC Considerations
- - IHS Domino and “rough” Apache equivalents
DefaultFsCp CharsetSourceEnc
DefaultNetCp CharsetDefault
AddLanguage AddLanguage
AddCharSet AddCharSet
AddType AddType
- DefaultFsCp and DefaultNetCpDirectives in IHSD
- - DefaultFsCp IBM-1047 # En_US/ (English EBCDIC)
- - #DefaultNetCp - network code page for ASCII text
- - DefaultNetCp ISO8859-1 # En_US
- CharsetSourceEnc and CharsetDefaultin IHSA
- - Provided by IBM in httpd.conf
- - LoadModule charset_lite_module modules/mod_charset_lite.so
- -
- - CharsetSource EncIBM-1047
- - CharsetDefaultI SO8859-1
- -

- AddTypeDirective in IHSD
- - AddType .ief image/ief binary 1.0 # ImageExchange
- - AddType .jpg image/jpeg binary 1.0 # JPEG
- - AddType .JPG image/jpeg binary 1.0
- AddType Directive in IHSA
- - Not needed for these filetypes
- - Look in mime.typesfile in /CONF/
- - - image/ief...ief
- - - image/jpeg...jpeg jpg jpe

IHSA Setup for MVSDS
- Based on “New Features” in Redpaper
- Implement MVSDS functions in IHSA
- - # allow the server to display z/OS data sets
- -
- - # Treat URL's as dataset names
- - MVSDS ON
- - # Data sets often lack file extensions
- - DefaultType text/plain
- - # Allow PDS listings
- - MVSDSIndexes On
- Implement MVSDS Security in IHSA
- - AuthName zosMVSDSViewer
- - AuthType Basic
- - AuthBasicProvider saf
- - Require valid-user
- - SAFRunAS %%CLIENT%%
- - AuthSAFExpiration "EXPIRED! oldpw/newpw/newpw"
- - AuthSAFReEnter "Enter new password one more time"
- - CharsetSourceEnc IBM-1047
- - CharsetDefault ISO8859-1
- -

- MVSDS Security in IHS Domino
- - Protection MVS_Logon { } Protect /MVSDS/* MVS_Logon %%CLIENT%%
- Security Prompt from IHS Apache says zosMVSDSViewer (sample displayed)
- MVSDS Displays PDS Directory
- - Click the Member Name to view the member
- - Shows ISPF member statistics
- - - Directory Listing of 'CPAC.C (listing displayed)
- http://s390devt.sas.com:8840/MVSDS/’cpac.PGMDIR.pdf(QM000895)’
- - Hat graphic sample displayed

IHSA Setup for “Public” Security
- Based on “Chapter 5: Migration” in Redpaper
- Implement “Public” Security in IHSA
- - ScriptAlias /bin-public/ "/dept/iss/web/sww/bin-public/"
- -
- - - AllowOverride None
- - - Options None
- - - Order allow,deny
- - - Allow from all
- - -

- Check the IHS Apache Server (graphic displayed)
- - http://s390devt.sas.com:8840/

IBM HTTP Server Domino Instance at SAS

- Pathname . : /web/server1
SYSZFS.WEB.SERVER1.DEVA
Filename Type Permission Owner Group
--------------- ------- --------------- --------- -------
. Dir rwxr-xr-x WEBADM IMWEB
.. Dir rwxr-xr-x WEBADM IMWEB
cgi Dir rwxr-xr-x WEBADM IMWEB
SYSZFS.WEB.SERVER1.CGI.DEVA
httpd.conf File rwxr-xr-x WEBADM IMWEB
httpd.envvars File rw-r--r-- WEBADM IMWEB
httpd-pid File rw-r--r-- BPXROOT SYS1
ics_pics.conf File rw-r--r-- WEBADM IMWEB
javelin.conf File rw-r--r-- WEBADM IMWEB
lgw_fcgi.conf File rw-r--r-- WEBADM IMWEB
logs Dir rwxr-xr-x WEBADM IMWEB
SYSZFS.WEB.SERVER1.LOGS.DEVA
mvsds.conf File rw-r--r-- WEBADM IMWEB
pub Dir rwxr-xr-x WEBADM IMWEB
SYSZFS.WEB.SERVER1.PUB.DEVA
reports Dir rwxr-xr-x WEBADM IMWEB
SYSZFS.WEB.SERVER1.REPORTS.DEVA
rexx Dir rwxr-xr-x WEBADM IMWEB
SYSZFS.WEB.SERVER1.REXX.DEVA
sec Dir rwx------ SNOJRH2 SYS1
SYSZFS.WEB.SERVER1.SEC.DEVA
servlets Dir rwxr-xr-x WEBADM IMWEB
SYSZFS.WEB.SERVER1.SERVLETS.DEVA
socks.conf File rw-r--r-- WEBADM IMWEB

IBM HTTP Server Apache Instance at SAS

- Pathname . : /web/server30
SYSZFS.WEB.SERVER30.DEVA
Filename Type Permission Owner Group
--------------- ------- --------------- --------- -------
. Dir rwxrwxr-x WEBADM IMWEB
.. Dir rwxr-xr-x WEBADM IMWEB
.31bit Syml rwxrwxrwx BPXROOT IMWEB
bin Dir rwxr-xr-x WEBADM IMWEB
build Dir rwxr-xr-x WEBADM IMWEB
cgi-bin Dir rwxr-xr-x WEBADM IMWEB
conf Dir rwxr-xr-x WEBADM IMWEB
error Dir rwxr-xr-x WEBADM IMWEB
example_module Syml rwxrwxrwx BPXROOT IMWEB
htdocs Dir rwxr-xr-x WEBADM IMWEB
icons Dir rwxr-xr-x WEBADM IMWEB
include Dir rwxr-xr-x WEBADM IMWEB
lib Dir rwxr-xr-x WEBADM IMWEB
logs Dir rwxr-xr-x WEBADM IMWEB
man Syml rwxrwxrwx BPXROOT IMWEB /usr/lpp/IHSA/V8R5/man
modules Dir rwxr-xr-x WEBADM IMWEB
notices Syml rwxrwxrwx BPXROOT IMWEB
properties Dir rwxr-xr-x WEBADM IMWEB
readme Syml rwxrwxrwx BPXROOT IMWEB IHSA Service Changes reports
readme.txt Syml rwxrwxrwx BPXROOT IMWEB
version.signature File rwxr-xr-x WEBADM IMWEB IBM HTTP Server 8.5.5.6
HAPBB001.zip Syml rwxrwxrwx BPXROOT IMWEB
HAPBE001.sh Syml rwxrwxrwx BPXROOT IMWEB
IBM Syml rwxrwxrwx BPXROOT IMWEB /usr/lpp/IHSA/V8R5/IBM

- Pathname . : /web/server30/conf
Filename Type Permission Owner Group
--------------- ------- --------------- --------- -------
httpd.conf File rwxr-xr-x WEBADM IMWEB
httpd.conf.default File rwxr-xr-x WEBADM IMWEB
httpd.conf.orig File rwxr-xr-x BPXROOT IMWEB
mime.types File rw-r--r-- WEBADM IMWEB
mime.types.default Syml rwxrwxrwx BPXROOT IMWEB
postinst.properties File rw-r--r-- WEBADM IMWEB

- Pathname . : /web/server30/logs
Filename Type Permission Owner Group
--------------- ------- --------------- --------- -------
access_log File rw-r--r-- WEBADM IMWEB
agent_log File rw-r--r-- WEBADM IMWEB
error_log File rw-r--r-- WEBADM IMWEB
httpd.pid File rw-r--r-- WEBADM IMWEB
postinst.log File rw-r--r-- WEBADM IMWEB
proc.errors File rw-rw-r-- WEBADM IMWEB
proc.output File rw-rw---- WEBADM IMWEB
referer_log File rw-r--r-- WEBADM IMWEB

IBM HTTP Server Apache Logs At SAS

- /web/server30/logs/access_log
10.17.15.76 --20/Jun/2015:11:35:31 -0400 "GET /MVSDS/%27SSD.ZOSV2R01.CNTL($$$$DEVA)%27 HTTP/1.1" 401 475
10.17.15.76 -snosew 20/Jun/2015:11:35:41 -0400 "GET /MVSDS/%27SSD.ZOSV2R01.CNTL($$$$DEVA)%27 HTTP/1.1" 200 273699
10.17.15.76 --20/Jun/2015:11:35:41 -0400 "GET /favicon.ico HTTP/1.1" 404 283
10.17.15.76 -snosew 20/Jun/2015:11:46:50 -0400 "GET /MVSDS/%27SSD.ZOSV2R01.CNTL($DEVA) HTTP/1.1" 404 303
10.17.15.76 --15/Jul/2015:17:13:24 -0400 "GET /bin-test/nfsmtptlkHTTP/1.1" 401 475
10.17.15.76 -snosew 15/Jul/2015:17:13:29 -0400 "GET /bin-test/nfsmtptlkHTTP/1.1" 200 11227
10.17.15.76 -snosew 15/Jul/2015:17:13:36 -0400 "POST /bin-test/nfsmtptlkHTTP/1.1" 200 4509

- /web/server30/logs/error_log
–Sat Jun 20 10:07:17 2015 notice IBM_HTTP_Server/8.5.5.5 (Unix) configured --resuming normal operations
–Sat Jun 20 11:35:41 2015 error client 10.17.15.76 File does not exist: /web/server30/htdocs/favicon.ico
–Sat Jun 20 11:46:50 2015 error client 10.17.15.76 (47)EDC5047I An invalid file name was specified as a function parameter. (errno2=0xC00B028E): Unable to open dataset 'SSD.ZOSV2R01.CNTL($DEVA)
–Wed Jul 15 17:13:36 2015 error client 10.17.15.76 cgiparse: Error: Both QUERY_STRING and CONTENT_LENGTH not defined or invalid
–Sat Jul 18 11:11:56 2015 error (122)EDC5122I Input/output error. (errno2=0x052C00B6): apr_socket_accept: (client socket)
–Sat Jul 18 11:12:16 2015 notice caught SIGTERM, shutting down

- /web/server30/logs/proc.errors
- - httpd: illegal option – k
- - - Usage: /web/server30/bin/httpd -d directory -D name -f file
- - - -C "directive" -c "directive"
- - - -k start|restart|graceful|graceful-stop|stop
- - - -v -V -h -l -L -t -S
- - Options:
-D name : define a name for use in directives
-d directory : specify an initial ServerRoot
-f file : specify an alternate ServerConfigFile
- - Sat Jun 20 10:07:15 2015 warn The ScriptAlias directive in /web/server30/conf/httpd.confat line 600 will probably never match because it overlaps an earlier Alias.
- - postinst: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
- - postinst: Couldn't find perl interpreter in path, using default /usr/bin/perl

IBM HTTP Server Apache on z/OS 2.2
- IBM HTTP Server 8.5 in z/OS Ported Tools
- - Based on Apache 2.2
- - /usr/lpp/IHSA/V8R5 is path to IBM-provided material (code, samples)
- IBM HTTP Server 9.0 in z/OS 2.2
- - Based on Apache 2.4
- - /usr/lpp/ihsa_zos is path to IBM-provided material
- Unmounted IHSD File Systems
- Altered names of IHSD File Systems
- Defined New IHSA File Systems for Server1
- - Hlq.WEB.SERVER1.sysname mounted at /web/server1
- Added mountpoints for /htdocs and /logs
- - Hlq.WEB.SERVER1.HTDOCS.sysname mounted at /web/server1/htdocs
- - Hlq.WEB.SERVER1.LOGS.sysname mounted at /web/server1/logs
- Created a New HTTP Server instance for z/OS 2.2
- - su - webadm
- - cd /usr/lpp/ihsa_zos/bin
- - ./install_ihs /web/server1 80 (80 is listen port)
- What’s Ours from the IHSA 8.5 Configuration File
- - Compared our new /web/server1/conf/httpd.conffile with the IHSA 8.5 file in /web/server30/conf/httpd.conf
- - Used ISPF 3.17 and its COMParecommand
- - Used ISPF MakeDatato update the new server1 httpd.conf
- IBM HTTP Server 8.5 in z/OS Ported Tools
- - httpd.conf
- - - Order allow,deny
- - - Allow from all
- IBM HTTP Server 9.0 in z/OS 2.2
- - httpd.conf
- - - Require all granted

IHSA Setup Continued
- Create a Started Task Procedure in SYS1.PROCLIB
- - Based on SHAPJCL3(HAPCPROC) [altered for this slide]
//* To end this server, S IHSASRV1,ACTION='stop'
//IHSASRV1 PROC ACTION='start',
// DIR='/web/server1',
// CONF='conf/httpd.conf'
//IHS EXEC PGM=BPXBATCH,MEMLIMIT=512M,
// PARM='SH &DIR/bin/apachectl-k &ACTION -f &CONF -DNO_DETACH',
//STDOUT DD PATH='&DIR/logs/proc.output',
// PATHOPTS=(OCREAT,OAPPEND,OWRONLY),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP)
//STDERR DD PATH='&DIR/logs/proc.errors',
// PATHOPTS=(OCREAT,OAPPEND,OWRONLY),
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP)
// PEND

IHSA Migration Challenges
- Log Management
- - IHSA not as automated as IHSD
- - Combination of conffile statements and external automated processes
- - - #Log Rotation in IHS Apache(IBM Education tutorials 2015)
- - - # CustomLog "|bin/rotatelogs logs/access_log 3600" common
- - Not yet done at SAS

Some thoughts about IBM HTTP Server from Marna Walle
- A strongly suggested migration path if you are using IBM HTTP Server powered by Domino.
- - 1. Are you affected? Use the “as is” health check from http://www-03.ibm.com/systems/z/os/zos/installation/HTTP_Health_Checker.html
- - - This check will simply tell you if you are using IBM HTTP Server powered by Domino.
- - 2. While on z/OS V1.13 or z/OS V2.1:
- - - Install IBM Ported Tools V1.3 HTTP Server (level 8.5.5, Apache level 2.2).
- - - Migrate from IBM HTTP Server powered by Domino to the HTTP Server 8.5.5.
- - - Use Redbook: IBM HTTP Server on z/OS: Migrating from Domino-powered to Apache-powered (REDP- 4987)
- - - You can run the Domino and Apache servers side by side on z/OS V1.13 or V2.1.
- - - - z/OS Infoprint Server still needs the Domino server prior to z/OS V2.2!
- - 3. When installing z/OS V2.2:
- - - Migrate to IBM HTTP Server 9.0 (in the z/OS V2.2 base, Apache level 2.4).
- - - Use “Upgrading to 2.4 from 2.2” http://publib.boulder.ibm.com/httpserv/manual24/upgrading.html
- - - Refer to http://www-01.ibm.com/support/knowledgecenter/SSEQTJ_8.5.5/com.ibm.websphere.ihs.doc/ihs/cihs_upgrading2.html
for the general process on how to move from 8.5.5 to 9.0 (although the documentation does not yet discuss z/OS or 9.0).
- - - Configure z/OS InfoprintServer (InfoprintCentral), PKI, and Library Server to use the new z/OS V2.2 HTTP Server.
- - - Take advantage of the migration accommodation for “dual” IHSA (8.5.5 and 9.0), if necessary. Refer to materials to be provided at a later date for important usage details.

• Contact Information
Ed Webb
Technical Lead, Mainframe Support
Senior Systems Programmer
SAS Institute Inc.
SAS Campus Drive
Cary, North Carolina 27513
(919) 531-4162

Website: www.sas.com


• The meeting ended about 9:00 P.M.


Treasurer’s Report for July 2016

contributed by Tommy Thomas


The balance in the account is $359.47 as of July 4, 2016.


SPARTA Financial Report
3/01/2016 through 7/19/2016


INCOME


Opening Balance

97.47

Total Deposits


Donation

0.00

Other

29.55

Dues

560.00

TOTAL INCOME

$687.02



EXPENSES


Food

170.43

Web Site

0.00

Petty Cash

230.00

Bank Service Charge

0.00

TOTAL EXPENSE

$400.43



BANK BALANCE

286.59

PETTY CASH 

72.88

TOTAL CASH

$359.47



Items of Interest



SPARTA Schedule and Menu for 2016

contributed by Tommy Thomas and Chris Blackshire


Aug 2, 2016 - BarBQ
Aug 30, 2016 - Durham Bulls (your choice of food at the game)
Oct 4, 2016 - Pizza
Nov 1, 2016 - Chicken
Dec 6, 2016 - Subs



One More Time: SHARE Atlanta Agenda and App Are Ready for Use

contributed by Ed Webb


Though the updated App has been available since mid-July, the Atlanta Conference database just became available this past week. In the App, click the refresh "loop" at the bottom of the first screen and Atlanta should download.

See the all of the Atlanta registration and hotel details at the SHARE Atlanta website.


Search the App Store and Google Play for "SHARE, Inc." to get the App. And yes, it works better than the San Antonio version.



zWhat? or z/What??

contributed by Ed Webb


"The IBM taxonomy and associated naming process is obscure and arcane, but quite interesting to those who have watched it evolve over the years. Pay attention, this may be on the test!

Name That Mainframe

Mainframe product line names used to be related to significant hardware architecture changes. In the beginning (1964), there was System/360, aka S/360 (well, OK, there were plenty of IBM machines before that, but we’re starting at the birth of IBM’s single hardware line, merging and replacing their separate “business” and “scientific” machines).

S/360 offered 24-bit addressability (in a 32-bit architecture), supporting up to 16 megabytes of memory (theoretically), and ranged from the Model 30, at 34,500 instructions per second, to the Model 75, with a whopping 1 million instructions per second—presumably the origin of the term MIPS. (For purists, yes, there was also the Model 20, but it was crippled, and should not be considered a “real” S/360.) The “theoretically” above is because nobody could afford 16MB of memory back then, not at over $2M per megabyte (per http://www.jcmit.com/memoryprice.htm; that’s about $15M per megabyte in 2016 dollars).

So began the evolution. S/360 begat S/370, which included virtual memory hardware support. By 1980, the 3033 offered 26-bit addressing for the high rollers, but was still a System/370 machine. 1983 saw the 370/XA architecture on the 3081, with 31-bit addressing (and mainframe folks still must respond to, “Surely you mean 32-bit?” from squatty-box people—most of whom had not been born yet, and for whom 16-bit addressability was then state-of-the-art). 370/XA evolved into ESA/370 on the 3090 and then ESA/390 on the ES/9000, both of which were more advanced versions of 31-bit addressing."

Learn more in this article by Philip H. Smith III at Enterprise Tech Journal.

You say ‘CICS,’ I say ‘CICS’

contributed by Ed Webb


"“Say ‘shibboleth’!” was the last order an outsider received before mispronouncing it and consequently being terminated with extreme prejudice during a critical conflict in Biblical times.

Today, we are less prone to execute those who say a word wrong, but the word “shibboleth” has come to refer to those words that indicate group membership by being properly pronounced.

On the mainframe, we have quite a few such jargon terms. Some of them are instant “gotcha’s” like “VTAM” and “DASD.” Some of them show how much distributed computing influence a person has, such as “SQL” or which word someone uses to clarify the first six letters of the alphabet (e.g. “able” vs “alpha”).

But there’s one special word on the mainframe that actually tells you more about what historical and linguistic part of the mainframe ecosystem a person comes from: CICS.

Now, if, upon seeing CICS you immediately subvocalized “kicks” in your mind’s ear, you are probably a mainframer from an English-speaking country. BUT: if you spelled it instead, perhaps sounding something like, “see ah see ayiss,” you are likely to be an American mainframer, because roughly half of all American mainframers prefer to spell this term rather than putting their foot into it.

As someone whose first mainframe responsibility was as a CICS systems programmer, I’ve paid attention to this linguistic conundrum for a long time, and I’ve started to refine some theories about the nature and origin of our naming of the Customer Information Control System."


See the rest of Reg Harbeck's blog entry at SHARE.


RESTful APIs Unlock the Value of z/OS Assets

contributed by Ed Webb


"If you work on the mainframe using z/OS and haven't heard of RESTful APIs, you need to wake up and smell the coffee. Seriously, even though RESTful APIs are still a fairly new thing, they're already essential. If you don't know about them, ask the people on the distributed side of your business -- who I can assure you already rely upon them -- to help bring you up to speed.

In March I wrote about IBM's use of RESTful APIs in z/OSMF to manage software installations. Since then, JSON and RESTful APIs have been part of all my face-to-face discussions with customers, the vast majority of whom have no idea about RESTful APIs.

The simplest way to explain RESTful APIs is to tell you what they can do. Imagine a newbie developer with no z/OS experience enabling some mainframe assembler programs that provide browser-based access to data. I'd imagine this but I don't have to, because I've seen it with my own eyes. And the young developer learned this in a day."


See the rest of Troy L Coleman's Enterprise Systems article here.



Humor


Programmers

contributed by Chris Blackshire


A young Programmer and his Project Manager board a train headed through the mountains on its way to Wichita. They can find no place to sit except for two seats right across the aisle from a young woman and her grandmother. After a while, it is obvious that the young woman and the young programmer are interested in each other, because they are giving each other looks.

Soon the train passes into a tunnel and it is pitch black. There is a sound of a kiss followed by the sound of a slap. When the train emerges from the tunnel, the four sit there without saying a word.

The grandmother is thinking to herself, "It was very brash for that young man to kiss my granddaughter, but I'm glad she slapped him."

The Project manager is sitting there thinking, "I didn't know the young tech was brave enough to kiss the girl, but I sure wish she hadn't missed him when she slapped me!"

The young woman was sitting and thinking, "I'm glad the guy kissed me, but I wish my grandmother had not slapped him!"

The young programmer sat there with a satisfied smile on his face. He thought to himself, "Life is good. How often does a guy have the chance to kiss a beautiful girl and slap his Project manager all at the same time!"

The Most Confusing Password

contributed by Chris Blackshire


I was in a couple’s home trying to fix their Internet connection.

The husband called out to his wife in the other room for the computer password.

“Start with a capital S, then 123,” she shouted back.

We tried S123 several times, but it didn’t work. So we called the wife in.

As she input the password, she muttered, “I really don’t know what’s so difficult about typing Start123.”

Murphy's Laws of Computing

contributed by Chris Blackshire


1. When computing, whatever happens, behave as though you meant it to happen.

2. When you get to the point where you really understand your computer, it's probably obsolete.

3. The first place to look for information is in the section of the manual where you least expect to find it.

4. When the going gets tough, upgrade.

5. For every action, there is an equal and opposite malfunction.

6. To err is human . . . to blame your computer for your mistakes is even more human, it is downright natural.

7. He who laughs last probably made a back-up.

8. If at first you do not succeed, blame your computer.

9. A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

10. The number one cause of computer problems is computer solutions.

11. A computer program will always do what you tell it to do, but rarely what you want to do.


Membership Information



Don’t Forget the Next SPARTA Meeting


Tuesday, August 30, 2016

7 p.m.


Special Location: Durham Bulls Athletic Park


Check out this link for directions: http://www.dbulls.com/stadium/directions.html


Fee Food: Whatever You Buy


Program:

Remember Tommy Thomas with Triple-A Baseball

Speaker: Durham Bulls vs. Columbus Clippers








SPARTA News

P.O. Box 13194

Research Triangle Park, NC  27709-3194


First Class Postage


SPARTA Corporate Sponsors:

DTS Software
                              logo